Upgrade 2.9.2 Bug??
-
I have an weird issue with the way the sidebar is behaving and I am beginning to wonder if it’s a bug.
Prior to the upgrade, the sidebar would lay nicely throughout the site including the single.php, archive.php, page.php, etc. pages. All those pages displays the sidebar too.
Since the upgrade to 2.9.2, the sidebar works fine throughout but what’s weird is when I make a new post. The sidebar displays fine via the blog default home page after the new post but what’s troubling is that when you click on the new article to view the entire page (single.php) the sidebar gets thrown over to the left at the bottom.
So in saying, when viewing the old posts (created before the upgrade) via the single.php page view they are still working fine thus displaying the sidebar where it’s suppose to. ONLY new post(s) is causing the sidebar to move down to the left and it only happens on the single.php page view. I have tested this again with new post with just one line of text with no formating and it still causes the same problem.
Below are links that are showing correctly and incorrectly after the upgrade:
Correct: blog home page – http://www.scrapnstamp.ca/blog/
Correct: blog full article (single.php page view) that was posted BEFORE the upgrade – http://www.scrapnstamp.ca/blog/promotions/welcome-to-our-new-website/
INCORRECT: blog full article (single.php page view) that was posted AFTER the upgrade – http://www.scrapnstamp.ca/blog/promotions/double-points-days/
According to the validator, the full post view seems to add an additional closing div tag in which I am unable to resolve (if that is the issue). All other errors are irrelevant to the problem.
I double checked my header/footer and they are correct. No extra opening tags or errors. However, I don’t think that is it because as you can see in my links above the posts works fine in one and not in the other.
Added info, I have used WP default template (version 2.9.0 I think) in which was renamed per WP document to have it listed as it’s own theme. Could anything have changed to the default header codes that needs to be carried over to my old 2.9.0 header?
I am not sure what else to look for.
Any help would be greatly appreciated.
The topic ‘Upgrade 2.9.2 Bug??’ is closed to new replies.