Follow-up

I consulted the codex for out-of-memory errors and added the line to my wp-config file, but I still get the fatal error when I attempt to activate the simple press plugin.

I’ll append the initial reply from my hosting service below.  They confirm my system meets the minimum requirements and my memory levels are set well above 64k.

Thanks!

Hello,

That error specifies that the memory limit of 256MB, which is an extremely
high limit and equal to about a third of your total RAM, has been exhausted
and that the file functions.php requested 72 more bytes. The issue I am seeing
here is that the memory limit is not set to 256, but only 128MB, which is
still very high. I searched through the site for what could be increasing this
limit but have not come back with any sources.

I also created an info.php page to see what was being recognized as the memory
limit and that showed me 128MB as well.

I have verified that this server meets the specifications you listed:

PHP 5.3.25
GD installed

MySQL 5.0.96

Please provide me a way to recreate the error you are seeing.

Best Regards,

64k??  assume you mean 64M… and assuming you dont have a bunch of other stuff running (you mentioned disabling other plugins) thats more than enough…   WP recommends 48 or 64M, but we have run in 32M on minimal installs before…

but we do have a fair number of folks running simple press on multisite so its not unique to that…  but just to be clear, you are running at least wp 3.6, right?  you mentioned wpmu but it hasnt been called that in quite a few versions (now called multisite by wp devs)…

and you put it in the standard wp plugins folder (vs mu-plugins)?  and tried to activate it on the main site?

assume you mean 64m

Yes, I meant to say “64m”.  It had been a long day

My hosting service has since confirmed that I’ve got ample memory, so that shouldn’t be the problem.

you are running at least wp 3.6, right?

Yes, it’s a brand-new installation of the very latest and all updates have been run.

and you put in the standard wp plugins folder (vs mu-plugins)? and tried to activate it on the main site?

I’ve only have one site site installed at the moment and I’ve tried both activating the plug-in on network wide and on the one site.  I also tried the install on a different multi-site network (on the same server) and got the same result.

As for trying a different upload location, I’ll have to explore that more.  I’ve always uploaded my programs to the network folder and then decided whether or not to activate them at the network level or at the site level.

For future reference, are you saying also that Simple:Press cannot be activated network-wide?  Please let me know as it’s relevant to my future plans.

Thanks!

I am afraid we need to wait for Mr Papa to answer the MS question.

I am curious what line of code (and in which function) you have for line 3847 of the functions.php file however.

Another follow-up:

I’m a paid wpmudev.org member too, and both wpmudev.org and Jim at tripawds.com speak glowingly of using Simple:Press in the multisite network.

As a follow-up question, could an errant install on the first try interfere with subsequent attempts?

On my first try I installed Simple:Press via the WP uploader and didn’t realize that an FTP upload was recommended until after I got the first fatal error.  I deleted the Simple-Press plug-in directory and re-uploaded it via FTP only to get the same fatal errors.

If this might be relevant, any ideas how to ensure a previous unsuccessful installation is removed?

Thanks!

Yellow Swordfish said
I am afraid we need to wait for Mr Papa to answer the MS question.

I am curious what line of code (and in which function) you have for line 3847 of the functions.php file however.

I’m fairly new at this an haven’t looked under the hood inside my functions.php folder before.  If you tell my how, particularly how to identify the function, I’ll try and report back.

Thanks!

I’m waiting to hear back from my hosting service, but the good folks at WPMUDev feel that this is a garden variety resources issue even though I have 256m allocated to PHP. 

They’ve suggested that try allocating 512m and see if that makes a difference.

I’ll report back!

Thanks!

Yellow Swordfish said

I am afraid we need to wait for Mr Papa to answer the MS question.

I am curious what line of code (and in which function) you have for line 3847 of the functions.php file however.

Here’s my hosting company’s answer to your question.  Hopefully it will provide some insights to those more knowledgeable than I.

Per their request, I’ve also again tried activating the plug-in with the greatly increased memory limits, but we’re still getting the same fatal error.

Thanks!

__________

> Line 3847 is:
> 
>                       $trace = debug_backtrace( false );
> 
> Here is the line in more context:
> 
> function wp_debug_backtrace_summary( $ignore_class = null, $skip_frames =
> 0, $pretty = true ) { if ( version_compare( PHP_VERSION,
> '5.2.5', '>=' ) ) $trace =
> debug_backtrace( false ); else $trace = debug_backtrace();
> 
>         $caller = array();
>         $check_class = ! is_null( $ignore_class );
>
> If you are receiving the same memory_limit error, some component of
> WordPress may be overriding the memory_limit directive in wp-config.php -
> possibly even the component you're trying to install.
> 
> I have adjusted the memory_limit by a different mechanism. You can
> confirm that memory_limit is set to 512M for the site by visiting:
> 
> http://problem-with-post-edit-buttonearyeforums.com/info.php
> 
> Please try the installation again and let me know how it goes. Thank you!
> 
> Regards,

want to ask again on wp version… This is 3.6.1, right?  and not the 3.7 beta version…

128M should be plenty, so don’t think we need to try to add more memory…

yes, Jim and many others from wpmudev use simple press so we just need to understand what is going on locally here with you..

just to make sure I am understanding..  this is the first and initial activation of simple press, right?

One thing simple press still does is try to use blogs.dir for different network site storage…  wp multisite no longer really uses blogs.dir for new installs but old installs still use it…  and we have not had any issues with using the older storage location on new installs (we will change it soon)…  and that would be on install, not activation… and not likely to cause a memory issue…  kind of grasping at straws so throwing it out there…

when simple press gets activated, we dont really do anything… almost no code is included or run…  until we run our install which requires a direct user action…  so that is why checking to make sure this is on activation and not install…

>>  want to ask again on wp version… This is 3.6.1, right?  and not the 3.7 beta version…

Confirmed, running 3.6.1, not 3.7 Beta.

>> this is the first and initial activation of simple press, right?

Yes, this is my first installation of Simple:Press (in a a brand new WP site at that) but as noted above, I erred in attempting to use the WP uploader on the very first try, so I deleted the plugin and directory and uploaded via FTP.

The only other options I can think of at this point is (1) re-installing WP and SP from scratch, or (2) sending you the log-on credentials so you can look at the site directly.

Let me know which approach you think best.

Thanks!

so yes, please go ahead and delete simple press and reupload via ftp… and try again…

if that still has the issue, we can take a look and see if we can glean anything, but activation doesnt even involved simple press other than reading in the main file…  but we can look…  just pm the admin details to both myself and yellow swordfish… be sure to link back to this topic in the pm too so we know what its about…

Thanks, will do on both and report back shortly.

we will be here!

OK, I deleted the plug-in and reloaded it via FTP.  Unfortunately, I’m still getting the same fatal error when I go to activate the plugin.

I’ll PM my log-in credentials momentarily.  Feel free to experiment, it’s a brand new site with nothing to lose.

Thanks!