on chrome canary:
same adventure-child:
192.168.0.16/wptest: wp3.9, Adventure3.8
norikoguide.pepper.jp/norikoshop: wp3.8.4,
on chrome canary:
same adventure-child:
192.168.0.16/wptest: wp3.9, Adventure3.8
norikoguide.pepper.jp/norikoshop: wp3.8.4,
“min-device-width” did not work.
functions.php in adventure-child:
if ( get_theme_mod(‘title_size_setting’) != ‘4.0’ ) echo ‘ @media only screen and (min-width: 361px) {.header h1 {font-size:’ . get_theme_mod(‘title_size_setting’) . ‘em;}}’ . “\n”;
worked O.K.
To increase upload_max filesize in migrating database.
/etc/php5/apache2# gksudo gedit php.ini
upload_max_filesize = 10M
post_max_size = 10M ;not necessary just fun.
service apache2 restart
<?php if (strpos($_SERVER[‘HTTP_USER_AGENT’],”MSIE 8″)) {
header(“X-UA-Compatible: IE=8”);} ?>
This will make IE8 fix to standard IE8 display mode.
If any(absolutely any!) file that take part in construction of the code of final HTML-page(the one to be sended to client) has encoding with BOM – final HTML-page WILL BE UTF-8-BOM. That is: you whole site should NOT contain even 1 file with BOM.
1. migrate database from japantourguide.lolipop.jp.
2. FFFTP uploads.
3. FFFTP adventure-child.
Firefox: everything fine.
IE8: content background and sidebar background O.K. Footers O.K.
header: arrangement no good. Fixing is O.K.
content: CR generates extra blank lines.
wordpress version 3.7.4.
4. Commentout extra in functions.php.
<?php /*if (strpos($_SERVER[‘HTTP_USER_AGENT’],”MSIE 8″)) {
header(“X-UA-Compatible: IE=7”);} */?> .
(Note that IE enhancer plugin is not introduced)
Almost resemblance of IE8 to Firefox.
The difference or defect:
content has no left margin. Sidebar has no right margin.
Font size looks larger.