what is odd is the content of your media. For example,
0000000 G I F 8 9 a 364 001 s \0 367 \0
0000020 \0 \0 \0 \0 \0 | 315 \0 ~ 320 \0 203 322 \0 212 000
0000040 \0 214 331 \0 220 332 \0 d 270 \0 [ 245 \0 u 301 \0
0000060 225 335 \0 222 334 \0 230 336 \0 226 340 \0 231 340 \0 233
or
0000000 211 P N G \r \n 032 \n \0 \0 \0 \r
0000020 I H D R \0 \0 001 220 \0 \0 001 217 \b 006 \0 \0
0000040 \0 r ? 206 202 \0 \0 \0 004 s B I T \b \b \b
0000060 \b | \b d 210 \0 \0 \0 \t p H Y s \0 \0 \n
0000100 360 \0 \0 \n 360 001 B 254 4 230 \0 \0 \0 037 t E
0000120 X t S o f t w a r e \0 M a c r o
0000140 m e d i a F i r e w o r k s
As you can see, there are 4 spaces at the begining of your files that should not be here.
The gif file had also other errors and could not be displayed, but the transparent png with
the black divers displayed correctly when I removed the leading 4 spaces. I don't think
your problem comes from php 7 upgrade.
The same 4 spaces also appear at the begining of your html files
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://w
Something is outputing those 4 spaces before DW starts to output its answer.
What I suspect, is there is a file, somewhere that
starts wiht " <?php" instead
of "<?php", or maybe,
ends in "?> " instead of "?>". (such files should really
end in "", but that is anoter matter). And, there could be multiple files starting with
" <?php", or any other combination of course. It could certainly be something else,
but the spaces before or after the php tag are the usual suspects. What puzzles
me is that in this case, you should see that kind of warnings in the logs :
Warning: Cannot modify header information - headers already sent
Anyway, here are the actions you can try :
1st of all. Change back your conf directory to non writeable, if that's your habits. DW works fine with conf directory non writeable.
then try this to find files that end with "?> "
cd ......./conf
grep '\?> *$' *
if there is any answer, edit the corresponding file and remove the spaces after the ?>
Then, try that to find files that start with " <?php"
grep '^ *<?php' *
if there is answer, edit the corresponding file and remove the leading spaces.
Again, I don't really expect an aswer...
also, run the same grep command in inc and lib/exe directory. Eventually, add a -r option to the grep command. There could be files that match. Remember you are only interrested in files that start with "space then <?php" or end in "?> traling spaces". If those patterns happen in the midlle of the file, don't change anything.
No result ? deactivate all unnecessary plugins