Hey Jens,

Firstly, I’m seeing a lot of references to ‘cache’ in the console. Not sure if you have a cache activated but it’s worth mentioning that If you are, the forum page has to be excluded. Since the forum loads dynamically on one page caching it can cause all manor of problems.

Of course, this might also explain why these problems don’t occur (or at least aren’t noticeable) when a user is already logged in.

It’s definitely the first thing to check!

Hi Ike, 

thanks for the quick reply. 

I excluded the forum from caching (indeed, it wasn’t excluded before) and cleared the cache. However, this doesn’t seem to resolve the issues. For instance, I still get the same error message about a blocked script. 

Best

The first thing you need to do is to turn off all that ‘Rocket’ script ‘minification’. As far as I can see it is screwing lots of things up which it usually does in my experience. You also gain very little. 99% of the scripts loaded by SP are already ‘minified’. And with it turned on it is also impossible to see what is going on – and you have a lot of errors and script issues showing up in the console.

As a separate issue the only ‘slow loading’ of the forum page I saw was while the page accessed YouTube for some reason  – that slowed it down somewhat…

Hi Swordfish, 

thanks, I should have thought of that myself! Turning off minification solved the issue with the blocked javascript. 

I can check tonight if it solved any of the conflicts with other plugins, but I’m not sure these issues are related. Can you check now if you see any other problems?

There seem to be two script errors left in the console both caused by the ‘naMediaAd.js’ script. everythugn else seerms OK….

Ok, thanks! So the blocked JS is resolved now. 

Unfortunately, there is still a conflict with some others plugins. For instance, if I activate Jetpack, the WordPress Dashboard remains blank, so does the plugin page, the theme options etc.

The conflict may have something to do with our wordpress theme as well, since it installs two plugins (shortcodes and theme options panel). In any case, though, the issue does not occur when simple press is deactivated.

Unfortunately Jetpack is known for causing trouble for a lot of people not only running Simple:Press but also other plugins. Technically speaking yes, the issue doesn’t occur when Simple:Press is deactivated, but the issue is still there and could potentially affect the use of other plugins.

I think most notably recently problems have been related to the Jetpack stats which you can disable, although not having used it I can’t advise much more than that and I didn’t think it affected the admin panel, more the front end. Still might be worth a try.

Just out of interest to cover all bases have you asked the theme developer(s) as well?

The error log shows various errors of the following type: 

PHP Notice: Undefined variable: controlBackGroundHover in /var/www/vhosts/windowsunited.de/problem-with-post-edit-buttonttpdocs/wp-content/sp-resources/forum-themes/unified/styles/unified.php on line 131

[Thu Jul 02 08:58:43 2015] [error] [client 90.186.0.29] PHP Notice: Undefined variable: controlDisabledBackGround in /var/www/vhosts/windowsunited.de/problem-with-post-edit-buttonttpdocs/wp-content/sp-resources/forum-themes/unified/styles/unified.php on line 137

[Thu Jul 02 08:58:43 2015] [error] [client 90.186.0.29] PHP Notice: Undefined variable: controlDisabledColor in /var/www/vhosts/windowsunited.de/problem-with-post-edit-buttonttpdocs/wp-content/sp-resources/forum-themes/unified/styles/unified.php on line 138

[Thu Jul 02 08:58:43 2015] [error] [client 90.186.0.29] PHP Notice: Undefined variable: controlDisabledBorder in /var/www/vhosts/windowsunited.de/problem-with-post-edit-buttonttpdocs/wp-content/sp-resources/forum-themes/unified/styles/unified.php on line 139

[Thu Jul 02 08:58:43 2015] [error] [client 90.186.0.29] PHP Notice: Undefined variable: controlFieldsetBorder in /var/www/vhosts/windowsunited.de/problem-with-post-edit-buttonttpdocs/wp-content/sp-resources/forum-themes/unified/styles/unified.php on line 143

[Thu Jul 02 08:58:43 2015] [error] [client 90.186.0.29] PHP Notice: Undefined variable: controlFieldsetBackGround in /var/www/vhosts/windowsunited.de/problem-with-post-edit-buttonttpdocs/wp-content/sp-resources/forum-themes/unified/styles/unified.php on line 144

…and so on. You have any idea where this comes from and if it could have something to do with the plugin conflicts

those are notices, not errors… and harmless – certainly not anything conflicting with jetpack…  just  nuisances that get corrected as they show up…

is this an unmodified unified? and up to date (which version)?  and which overlay are you using…  so we can check on the notices for any needed cleanup…

Hi Mr. Papa, 

the Unified Version is 1.0.13 (I think it’s the most recent one, at least I don’t see any updates). The Overlay is “minimalist”. 

Yes – that’s the most recent version.

So – what are you left with? Just this admin problem when JetPack is activated? Is that it now?

If you actually get a blank page then I would expect an entry in the server side php error log – and I do mean an actual error – NOT a notice of a warning. SO if it is tripping the error code it might be useful to know what it says.

It might also be useful to know what components of JetPack are turned on. I don’t know if this is still the case but the last time I installed JetPack it had the disgraceful habit of automatically turning on many, many components by default whether you wanted them or not plus didn’t make it easy to deactivate them. So it would be worth ensuring that only those components you need are turned on and us, perhaps, knowing what they are.

Sorry for the late reply. 

I disabled all Jetpack modules except the ones we absolutely need: statistics and contact forms. The dashboard is fine now, but our theme options panel remains blank and there are minor problems with the editor. There are no php errors showing in the log file. 

I cannot really blame Simple Press, though. There seems to be a conflict between a whole set of plugins: Simple Press, Jetpack, WordPress SEO and PowerPress. I

If I disable anyone of those, the problems disappear. Unfortunately, we need them all. 

Thank you very much for the support. 

many, many users use simple press with jetpack and wordpress seo…  cannot comment on powerpress since I dont think I have heard of it before…  can you enlighten on what it is?

editor problems in simple press on front end?  its possible a theme or plugin is improperly using the editor (ie adding buttons to it)… the wp editor is designed to be used on front or back end, but some plugins assume only backend and hook into it wrong…

when you try to load the theme panel, with the browser console open, any errors reported?  if not, what is the xmlhttp response (should be able to expand a line that comes up when  you load page)..