Support Forum
Support Forum
Offline
I read that. But also tried to activate anything. No effect.
Offline
Also tried now to set another theme and SP template..no effect.
The Memory error occurs, when I activate teh Buddypress plugin, but not instantly. When I activate a SP plugin (no matter which one) the page loads once and after 1 or 2 seconds a second time. That second load is, when the error occurs 
Offline
Well I was hoping that Steve might have had some ideas but clearly not.
So, bearing in mind that I personally have never used BuddyPress or spent any time with it (actually the two times I loaded it up and activated it it seemed to cause many issues and I just dumped it quickly again -but that was a quite a while back) and also bearing in mind that it seems this report is unique and therefore not a general issue experienced by all - it is going to somehow come down to a 'local ' site issue - configuration perhaps of something.
Hitting a memory issue with a second page load makes little sense however. Each page load is discreet and starts with a clean slate as far as the php processing memory is concerned. I think the first thing here is to study the php error log. If that is reporting fatal error due to memory being exhausted it might perhaps be inyeresting to know what was recorded before that event. At least one has to start somewhere.
 |
YELLOW
SWORDFISH
|
Offline
When activating DEBUG it always keeps saying
Notice: Undefined index: in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
does that say anything to you?
This one is coming always, even when the "Memory error" doesnt show up. When bp-plugin is active and I click somewhere in the Dashboard on another item or i call the Website the pages kepp blank, except this note.
I´m at the point where I think of goin back to bbp. I think I´ll try out one more thing now. I´ll make up a complete new installation of a WP Page with SP and BP only for testing. Can you tell me which tables I have to take over there? I guess
-wp_users
-wp_usermeta
-wp_post
- and all wp_sf...
Offline
Generally speaking you can ignore 'Notices'. Virtually all just clutter and a nuisance. Probably 'Warnings' as well. It is really just the errors we are looking for.
Having said that it might be worth clearling the auths cache. forum admin > toolbox > housekeeping - Reset Auths cache task.
|
YELLOW
SWORDFISH
|
Offline
Okay what about
Warning: Cannot modify header information - headers already sent by (output started at /www/problem-with-post-edit-buttontdocs/.../wp-content/plugins/simple-press/sp-api/sp-api-auths.php:31) in /www/problem-with-post-edit-buttontdocs/.../wp-content/plugins/simple-press/sp-startup/site/sp-ahah-handler.php on line 21
Offline
It's a chicken and egg thing. You get that warning because you have WP_DEBUG turned on which has already written to the display. WP_DEBUG can be useful but it gives blanket coverage and you can't turn Notices off. The error log file on the server is far more useful and accurate.
|
YELLOW
SWORDFISH
|
Offline
I have no access to the logfile, but I made up an own withinh my htaccess
[02-Apr-2014 09:34:04 UTC] PHP Notice: Undefined index: subscribe in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:04 UTC] PHP Notice: Undefined index: in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:04 UTC] PHP Notice: Undefined index: watch in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:04 UTC] PHP Notice: Undefined index: in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:05 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 523800 bytes) in /www/problem-with-post-edit-buttontdocs/..../wp-includes/formatting.php on line 2995
[02-Apr-2014 09:34:06 UTC] PHP Notice: Undefined index: subscribe in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:06 UTC] PHP Notice: Undefined index: in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:06 UTC] PHP Notice: Undefined index: watch in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:06 UTC] PHP Notice: Undefined index: in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:09 UTC] PHP Fatal error: Out of memory (allocated 419168256) (tried to allocate 71 bytes) in /www/problem-with-post-edit-buttontdocs/..../wp-includes/kses.php on line 1149
[02-Apr-2014 09:34:14 UTC] PHP Notice: Undefined index: subscribe in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:14 UTC] PHP Notice: Undefined index: in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:14 UTC] PHP Notice: Undefined index: watch in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:14 UTC] PHP Notice: Undefined index: in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:15 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 523800 bytes) in /www/problem-with-post-edit-buttontdocs/..../wp-includes/formatting.php on line 2995
[02-Apr-2014 09:34:19 UTC] PHP Notice: Undefined index: subscribe in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:19 UTC] PHP Notice: Undefined index: in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:19 UTC] PHP Notice: Undefined index: watch in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:19 UTC] PHP Notice: Undefined index: in /www/problem-with-post-edit-buttontdocs/..../wp-content/plugins/simple-press/sp-api/sp-api-auths.php on line 31
[02-Apr-2014 09:34:22 UTC] PHP Fatal error: Out of memory (allocated 419168256) (tried to allocate 71 bytes) in /www/problem-with-post-edit-buttontdocs/..../wp-includes/kses.php on line 1149
Offline
So nothing shows. Curious. Did you perform the reset of the auths cache by the way?
So the next question perhaps should be - do you have a lot of plugins active and is it actually possible that you genuinely are stretching the memory to breaking point? After all - WordPress itself tries to allocate 256MB these days just to run the admin side of things. While we can run SP in 64MB of allocated php memoery it is a push to do so and the moment other plugins get factored in things quickly go south.
So might the memory issue actually be genuine? And if not - why not?
|
YELLOW
SWORDFISH
|
Offline
I cleaned the Auth Cache.
I deactivated all Plugins. I said somwhere before, that a Memory tool shows me 96MB use when WP with all my plugins is active (without SP) when all Plugins are deactivated and SP in on it is 60MB use. When ALL plugins incl SP are active the usage is at 108MB. Thats why I thaught of a leak somewhere in the Buddypress<->SimplePress interface plugin.
All RSS