Community Support Forums

JUst to let you know when upgrading to the latest version I upgraded s2member plugin, then it told me to upgrade pro.

I had the server set on 128mb memory limit so the auto upgrade failed, telling me to do it via ftp.

However, after uploading the pro plugin via ftp I couldn;t log in.
When trying to change password I got


Fatal error: Class 'c_ws_plugin__s2member_pro_remote_ops' not found in /home/xxxxxx/public_html/wp-content/plugins/s2member/includes/classes/registrations.inc.php on line 50


To resolve this, I deleted the pro plugin again, then it let me reset my password. While logged in, I uploaded pro again, but it did not activate.

Instead, I changed my server settings to 256 memory limit and did it the auto way. Anyone on shared hosting who does not control the server settings wouldn't have access to this, so may struggle with the above things when uploading via ftp.

Cheers

Thanks for the feedback! I'll let Jason know about this.

Thanks for reporting this important issue.

Code: Select all

Fatal error: Class 'c_ws_plugin__s2member_pro_remote_ops' not found in /home/xxxxxx/public_html/wp-content/plugins/s2member/includes/classes/registrations.inc.php on line 50

Hmm, this would indicate to me that your FTP upload did not fully succeed the first time. Am I missing something? You mentioned 256M memory. How did that improve your installation experience exactly? You mean it allowed you to upload it through WordPress?

It's not saying the file cannot be found from the upload, it's saying "on line 50"
This error refers to something on line 50 in that file, like many php errors.

To upload via wordpress requires 256mb of php memory, not all servers allow this, but as we are also a hosting company I adjusted this. After writing the above post I remembered people on shared hosting can sometimes overide php memory by using a php.ini file in their wordpress folder.

p.s. it may just have been a kink on my upload, so I really only came here and contributed the solution to the forum incase anyone else hit the same problem at all.

Thanks for sharing it.

So you don't have a problem now, is that correct?

no, my problem is solved, I changed my server settings to 256 memory limit and did it the auto way from the wp admin.

Great.

Cool, thanks for sharing this.