April 2, 2014 at 6:27 pm #98187
Found the issue...
Different browsers on different OS's can sometimes ignore bad HTML.
The problem is with your Facebook code. Viewing the source, you have a
<head>section. This is creating two body classes when it's rendered by the browser and Genesis relies on adding body classes for colors and layout. While mobile browsers, and apparently on Mac browsers, overlook this error, it breaks on PC browsers.
The offending code is this:
It's probably in the Genesis > Theme Settings > Header Scripts section. Remove that <div> and the <head> won't end prematurely and should render properly.
Edit: If it's not a script added to the theme settings, it's probably a Facebook plugin of some kind. If so, deactivate any FB plugin you have.April 2, 2014 at 6:31 pm #98189TomParticipant
OK, I'll jump in, if I can help...
From W3C CSS Validator, results show 79 errors and 129 warnings. The majority seem to be related to a plugin called "A10 Imaio" installed. Can you deactivate this plugin, clear your cache ? (or temporarily deactivate Quick Cache) Actually for a shor time, could you deactivate as many plugins as you're comfortable with? That might help elimnate potential problem sources.
April 2, 2014 at 6:33 pm #98190
Hi Tom, thanks for popping over here! He did all of that and I suggested the A10 Imaio which is some type or mobility plugin. Even with the deactivated plugins, it still looks that way.
Love coffee, chocolate and my Bella!April 2, 2014 at 6:41 pm #98191
Has to be the <div> in the <head>. You can't do that. The browser, some at least, will think that is the beginning of the <body>. Looking at the source on a PC, you'll see there are no body classes are being added because of that.April 2, 2014 at 9:36 pm #98207
Hello Dave and Tom... thank you for checking it out for me. As for the header script section in Genesis/Theme settings, I haven't put anything in there. Also, like Anitac has mentioned, I've also disabled all plugins and still rendered the same outcome on a PC. Oddly enough, I also have another blog on the same domain where I too installed the Genesis/MetroPro theme and it's doing the same thing. http://RandallRussell.com/slf Orange on PCs yet blue (Correct color) on my Mac and iPhone.
I've logged a support ticket... and I can't imagine that I'm the only one experiencing this issue? I wonder if it's some sort of server setting... where my site is hosted? GVO http://gogvo.com I've checked with the support them there and they say to check with the theme developer. It's a mystery! As for digging into the code for the <div> in the <head> section... not sure where to even begin to look for that. I would assume some .php file?April 2, 2014 at 10:08 pm #98211
Each of the sites have an invalid body tag of:
Followed by a
<body>tag with no classes.
Your main site has the
<body style>tag in the middle of the
<head>which is then closed by the browser. That is followed by code that is supposed to be in the
<head>, but isn't, after the
Your other site has the
<body style> tag followed immediately by the
The common plugin I see on both is the a10-imaio plugin. I know you've said you deactivated it, but it's still showing active, so be sure to deactivate that plugin and clear any caches.April 2, 2014 at 10:36 pm #98218
@kingengr I am still up. I am Eastern Time. If you want, go to my website, use the contact and send me an administrator user id and password. I'll log in and check it out.
Love coffee, chocolate and my Bella!April 2, 2014 at 10:40 pm #98219
I see several things that aren't deactivated. Get that info to me and I'll log in.
Love coffee, chocolate and my Bella!April 2, 2014 at 11:12 pm #98224
Hello there, sorry, didn't see that I was getting a response. Yes, I reactivated the plugins earlier after discovering that the issue still remained even after I deactivated them. As of this time, I've deactivated all plugins on both sites.April 2, 2014 at 11:31 pm #98226
Very odd. I see no plugins are active now, but doing an Inspect Element on your page still shows two <body> tags. Again, strangely, only one <body> tag is in the actual source code.
I noticed that your div.footer-widgets and footer.site-footer are outside of the div.site-container when they should be inside. Don't know if this is causing the issue (it shouldn't), but it is incorrect.
Did a W3C validation and noticed a stray quote in your "Track with me" text widget code, on the Google+ link, in the img element after the closing slash. Remove that quote at the end and see if it has any effect:
<a rel="author" href="https://plus.google.com/u/0/+RandallRRussell/about"><img src="http://randallrussell.com/wp-content/uploads/2014/03/randall-russell-google-48x48.png" border="0" alt="" /"></a>April 2, 2014 at 11:36 pm #98228
I am in his account. There's some bad code in there. I think he's been hacked.
Love coffee, chocolate and my Bella!April 2, 2014 at 11:39 pm #98230
Forgive my ignorance Dave... but how can you tell what plugins I have and if they are active or not? Thx again for you both digging in and trying to fix this issue.April 2, 2014 at 11:43 pm #98231
I think you should reinstall WordPress all together because your Login Screen and your widgets page don't look right. You had some malicious code in the top of the functions.php file. I would do a fresh install of WordPress and start over. It's not the theme.
Love coffee, chocolate and my Bella!April 2, 2014 at 11:43 pm #98232
No worries. I enjoy trying to figure out strange issues like this that seem to have no rhyme or reason. It's always just a process of elimination.
We can tell what is active and being loaded by looking at the source code. We can't know what is not active. Your source code is clean right now (except for the stray quote I mentioned earlier) but as @anitac mentioned, there could always be something loaded in the backend through PHP (a hack or other bad code) and we can't determine that without getting into your account.April 2, 2014 at 11:45 pm #98233
We can "reveal the source" and use Firebug for Firebug or other developer tools that are in the browsers. But we cannot see inside say your functions.php, your home.php or other files of that nature or your core WordPress files.
Love coffee, chocolate and my Bella!April 2, 2014 at 11:46 pm #98234
So how would I go about reinstalling wordpress w/o losing all of my data/posts, etc?April 2, 2014 at 11:49 pm #98235
You can go to Tools > Export and Export your content. Then go to Genesis > Export and export that file. Go to your host, reinstall WordPress. Then import both of those files. But... use a FRESH copy of the theme. You said you just purchased it. Did you purchase it directly from Studiopress?
Love coffee, chocolate and my Bella!April 2, 2014 at 11:49 pm #98236
I use to run Optimize Press 1.6... then upgraded to the newer 2.0. Then I found out about Genesis las week and went with that theme. Also, before 2.0 I had my site at GoDaddy then moved it over to GVO. Also, remember that my other site is doing the same thing. randallrussell.com/slfApril 2, 2014 at 11:51 pm #98237
Are both sites on GVO?
Love coffee, chocolate and my Bella!April 2, 2014 at 11:52 pm #98238
Yes Anatia... purchased directly from StudioPress.
Ah... ok, I'll look into the Export features. Thank you again for your assistance... both of you! You have been a blessing!
Yes, both are GVO... SLF is directly in the root of public. They have been structured this way for over two years.
- The forum ‘General Discussion’ is closed to new topics and replies.