Support Forum

SP causes Graphene theme to not display sidebar and footer is huge

DA Dave
Dave
Member
Member since Oct 2011
119 posts
Dec 15, 2011 · 9:26 am · Edited

OK, decided to actually take the plunge last night! Loaded 4.5 and imported the PHPBB database. Had to do the process twice as it wouldn’t complete on the first try.

I already had a “forum” page so I struggled through getting that straightened out and finally got the forum viewable to the public. Using the CSS only theme. Lots of work still to do, but mostly creating groups and moving forums.

However, the addition of SP causes the sidebar not to load. The actual space is there, but no widgets appear. Also the page footer is HUGE! laugh It’s at least a full page in size all by itself. I’ve messed around with this for about 9hrs and haven’t been able to come to a solution. Any ideas?

Simple:Press version: 5.0.0
Simple:Press build: 7474
Simple:Press release type: Beta
WordPress version: 3.3
MySQL version: 5.1.56
PHP version: 5.3.8
PHP memory limit: 160M

WP active plugins:
ad-injection
add-link-to-facebook
akismet
archives
better-wp-security
contact-form-7
google-sitemap-generator
hide-trackbacks
mobile-smart
paypal-donations
redirection
rss-digest
seo-automatic-links
sexybookmarks
simple-press
tpc-memory-usage
wp-dbmanager
wp-dtree-30
wp-jquery-lightbox
wp-mailinglist
wp-pagenavi
wp-super-cache
wp-to-twitter
yet-another-related-posts-plugin

SP active plugins:
admin-bar
captcha
google-sitemap
gravatar-cache
plupload
private-messaging
report-post
subscriptions
syntax-highlighting
watches

6 Answers

New Answer
YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Dec 15, 2011 · 12:05 pm

we have issues with Graphene before.
At the bottom of this thread – https://simple-press.com/support-forum/sp5-plugin-topics/widget-plugin-makes-content-disappear/page-2/ – there is a possible fix for a related issue. Read the post as the fix is conditional! But it would be worth trying that on your site as well to see if it helps.

either way – also look at the wp integration admin panel as there are a couple of options down the bottom that might also help which are designed to try and workaround themes that play tricks with Wp content filtering as I believe Graphene does.

As an extra note we have also had trouble with the sexybookmarks plugin before now and SEO Smart Links. If any of the buttons/links don’t work see if these are culprits.

DA Dave
Dave
Member
Member since Oct 2011
119 posts
Dec 16, 2011 · 10:06 am

I had previously tried all combinations of the Filter, Loop, and Load buttons without success.

I added the code suggested in the referenced thread. No luck. I then tried all combinations of the buttons and still no luck. I also disabled both SexyBookMarks and SEO smartlinks.

Here are some screen shots – pretty weird as it works about 20% of the time and is all wonky the other 80%.
dct-1.jpgdct-2.jpgdct-3.jpgdct-4.jpgdct-5.jpg

dct-1.jpg dct-2.jpg dct-3.jpg dct-4.jpg dct-5.jpg
DA Dave
Dave
Member
Member since Oct 2011
119 posts
Dec 16, 2011 · 10:44 am

I think I may have found the culprit. Interesting is that I had the same plugin running on my test setup and it didn’t have that effect. I’ll update later!

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Dec 16, 2011 · 10:47 am

OK one thing at a time. The sidebar. You said in the first first ’causes the sidebar not to load’ and later suggested it might be loading but at the bottom. The fix I asked you to try was for no sidebar ever which is not the same thing. So which is it? If we are talking about it being displaced then this is going to be a CSS issue of some sort.

The loss of forum integrity half way through a post is a little different and might come down to the content although I would need to see it test that theory.

So that goes for both really – need to see it for myself.

DA Dave
Dave
Member
Member since Oct 2011
119 posts
Dec 19, 2011 · 6:23 pm

OK, the issue was with a WP plugin named ad-injection. I disabled ads in the content area of pages and it was an immediate fix.

It really had me stumped because I had that plugin running on my test setup to make sure it was compatible with WP3.3 and SP5.0.

Sorry for the alarm and confusion, but (again) you help is above reproach!