I think you need to ask that question of your host as they are the only ones who can monitor the server direct and tell you why the site is not connecting.

If this is related to Simple:Press then they should be able to deduce the issue and then we might be able to work out what the actual problem might be.

Okay i deactivated all my plugins. So I could at least access the Backend. I can acrtivate anything. But as far as I activate SP and buddypress (nothing else) the whole thing hangs up. 

Okay. As it seems SP does somehow produce huge memoryleaks within my installation. I can activate all my plugins and it runs superb. As far as I activate SP after some actions the page runs out of memory (Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 71 bytes) ).

SP clean install – SP bpress import

Plugins: tags, blog-linking, buddypress

Memory leak? Why a memory leak? Why is this just not enough php RAM being allocated?

Unless you are seeing a repeated, looping error in the php error log which would be the first thing to perhaps double check on… well anything that is getting repeated over and over but not running our of memory of course.

I installed a “Memory Plugin” to see how much of the Memory is used. Without SP the installation (with all plugins except SP) uses 97MB RAM. When I activate it must cause some loop, because I get every 12 Seconds a message per mail, that the Memory has exeeded and the page runs slower and then doesnt respond at some point. SP alone with WP takes 60MB of RAM and the problem seems to occure when i activate SP. Dont know if its a matter of comaptibility or so…

I will reinstall my backup when i get home and then do a second test installation just for figuring out what went wrong :/

Semms to be sth about the buddypress plugin for SP as I found out now…

Ah – there has been some problem with this that one or two users had. Was it something to do with the activity log not being used perhaps? Steve can tell us exactly what it is but he wont be around until a little later on. I can also try a quick search of the forums here as I know it has come up.

I deleted everything from the activity stream already.

I´m dying over here about that….

The activity stream is a central tool of my com you know…

What I did try so far:

– re installed Buddypress

– re installes SP and reimported all the bbpress stuff

– emptied the activity table

– allocated in .htaccess more memory (from 128M to 256M)

– activated all Buddypress Options

– deactivated anything except SP+BP

– made a new DB and copied the whole DB and Files to another installation

My search suggests that the other person who seemed to havre this issue was not using the notifications module and that seemed to be the problem. i am unsure where we are with this – as I said  we need Steve {Mr Papa) to answer that one.

I read that. But also tried to activate anything. No effect.

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

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.

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…

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.