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
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.
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
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?
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.
Okay tried sth different:
– took my wp_sf tables and wp_users, wp_usermeta and went to my testinstallation, where clean BP ans SP ran fine before. Made the inserts. Users and Forum seemed okay. But same issue on activating the plugin.
What does
Warning: Cannot modify header information – headers already sent by (output started at /www/problem-with-post-edit-buttontdocs/…./wp-content/sp-resources/forum-plugins/plupload/sp-plupload-plugin.php:59)
mean? It seems that this occurs very often when i look through the forum fuctions.
typically means multiple folks output header information… sometimes happens in error situations… but wont be the cause of memory issues – or at least very, very unlikely…
do you any other buddypress add on plugins active? and do you have any buddypress modules deactivated? there was an issue several versions where deactivating one module (cant remember this early what it was) could cause issues, but it was fixed in a previous version… and we couldnt get it deactivating others, but worth a look on your end…
Hey, Andy already told me and I also read it somwhere and tried it out (activating all BP Modules) with no effect. As I said I tried any possible combination of plugin activation and deactivation. I even set up a complete new page and imported teh SP tables and the WP users only, installes BP fresh and got the same error at the end. After nearly 2 days of searching and testing I´m a little tired and frustrated now.
The memory error does – as I said- not always occur instantly. Sometimes I only get a blank Admin Panel except of the Menu on the left with that Warnings and notices I posted. When I click several Items on the menu it always re- appears. And after 2 or 3 clicks comes the memory error.
I´m not a coder and do not really know about PHP. So I´m at the end of what I´m able to do. If one of you guys like, I´d in last instance give you a look at my page and my backend if that does help. I can do a complete backup before of files and data (as if I had not made enough in last 24 hrs 
) I coul also provide SQL Dump etc but my friends want a running page and thats my only wish.
As I already said before, my community is still forming, so I´d also consider “drastic” options but the forum threads and my blog posts as well as the user data must survive..
Steve – over to you for opinion. Any more ideas? This is clearly a one-off so can you recommend any data it might be worth getting a dump of? Any point in having site access? use of ashow/vshow?
Needless to say I have no other avenues I can think of to explore at the moment. Although I guess I could install BuddyPress but that will involve a steep klearning curve…
Hello guys,
I took the afternoon to setup a all new installation once more but this time chose obviously more carfully the tables to transfer to the new installation. I can say now, obviously the site with all plugins needed is running including SP and Buddypress. I dont really know what the issue was, but obviously its running now. The only occuring issue now is the one regarding to the “Achievements Beta Plugin”. Thanks so much fpor your patience and sorry I stole your time.
Now I can keep SP and my beloved Activity wall 
But dont be to euphoric…I will have other things to ask ^^
Best Regards Dave
Yeah, would be nice. But I really don´t know. I made this step yesterday as “last try” and very carefully chose the tables I imported from my livesite.