Page 1 of 1

Blank Page

PostPosted: July 4th, 2010, 10:20 am
by snelson2678
Every time I activate s2Members My whole site goes blank. I checked my error logs and don't see anything???

Re: Blank Page

PostPosted: July 6th, 2010, 9:00 am
by snelson2678
I have been tinkering and I know see some error logs:
[Tue Jul 06 06:35:19 2010] [error] [client 64.61.122.42] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 338916116 bytes) in /home/charityw/public_html/members/wp-includes/functions.php on line 2956, referer: http://members.socialmediaschools.com/members-forum/

When I deactivate the s2Members the site works fine. How Much memory is required by the plugin?

Re: Blank Page

PostPosted: July 7th, 2010, 4:03 pm
by drbyte
Change hosting company and all your nightmares will go a way

Re: Blank Page

PostPosted: July 7th, 2010, 4:09 pm
by Jason Caldwell
Yea, either change hosting providers, or try uploading s2Member via FTP, instead of activating it directly through WordPress. Memory is usually NOT an issue once s2Member is installed. The memory intensive routine is the installation itself. WordPress has to hold all of your existing plugins in memory, then unzip the entire s2Member distribution, and hold that in memory... all of that tends to go over a shared hosting allowance.

The solution is to use FileZilla and login via FTP.
Upload the /s2member folder to your /wp-content/plugins/ directory.

Re: Blank Page

PostPosted: July 7th, 2010, 7:02 pm
by snelson2678
Yes but I can upload and install. The blank pages don't occur until after activated. Does that make sense?

Re: Blank Page

PostPosted: July 7th, 2010, 7:34 pm
by Jason Caldwell
Gotchya. We'll, my guess is that you have a LOT of plugins running?

67108864 = 64 Megabytes. So ( although I can't be sure ), it sounds like you have enough plugins running together at the same time, that s2Member is pushing you over the edge of the 64MB limit imposed by your php.ini file. You can try adding this to your /wp-config.php file and see if it fixes the problem.

Code: Select all
define(’WP_MEMORY_LIMIT’, ’128M’);

That will double your current limit. If you're on shared hosting, this may not work though. Shared hosting usually has hard-coded limits that cannot be changed without upgrading your hosting plan.

s2Member is not a memory hog though, it just sounds like you're hitting an overall memory limit because of plugins. Think of it like this. If you walk around the grocery store and place lots of items in the basket, eventually, the basket gets very heavy. You need the basket, and everything in it, but there needs to be a stronger person there to push it now. That's what happens with lots of plugins.

For every plugin that you install, you add more code to WordPress. If you add enough code, eventually, you will hit a memory limit, because WordPress has to include so much data into every processing routine that it performs. Ultimately, you have to put your WordPress installation on a diet ( drop a few plugins ), or get a bigger server with more power/RAM to handle what you need it to run.

Re: Blank Page

PostPosted: July 8th, 2010, 5:46 am
by wollix
I have the same problem. My WP 3.0 installation is fresh clean. I worked around and everything works.
But now, i dont realize what happens, the Member Site is blank.

What should i do?????

Re: Blank Page

PostPosted: July 8th, 2010, 6:05 am
by Jason Caldwell
I see. If one or both of you "wollix" and/or "snelson2678" can provide me with a WP Dashboard login to your installation, I'll have a look for you; and try to offer a solution. You can contact me privately through this form. http://www.s2member.com/contact/

Re: Blank Page

PostPosted: July 16th, 2010, 1:31 am
by Jason Caldwell
Update on this investigation.

With s2Member Pro, we were able to reproduce this bug, running on GoDaddy shared hosting. The problem has to do with the ionCube loader, and/or the Zend Optimizer that is required to run s2Member Pro. On GoDaddy shared hosting, there is a lengthy delay with any update to the php.ini file, which can cause "the white screen of death" temporarily during the transition.

In our testing ( thus far ), the bug does NOT have anything to do with s2Member Pro, but rather, with the delay in server configuration updates on the shared hosting platform offered by GoDaddy.

Possible solution: After updating your php.ini file, wait approximately 1 hour before re-testing your installation. If the problem persists, please contact GoDaddy Support for further assistance.