Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember Troubleshooting › Latest version won't activate – getting fatal error
Tagged: fatal error, WP eMember
- This topic has 8 replies, 2 voices, and was last updated 14 years, 9 months ago by
amin007.
-
AuthorPosts
-
February 8, 2011 at 10:55 am #2667
Duck
ParticipantHi,
I have just uploaded the latest version of WP emember to our website but can not get it to activate and end up with the following error when I try:
Fatal error: Class ‘Config’ not found in /home/leath3rc/public_html/leather_data_01/wp-content/plugins/wp-eMember/eMember_installer.php on line 51
For you information our server is running PHP 5.2.16 and it is WordPress 3.0.4.
Would really appreciate your help with this.
Many thanks,
Duncan.
February 9, 2011 at 3:51 am #28830amin007
ParticipantHi, Please get another fresh build of eMember from here and you shouldn’t see this error:
February 9, 2011 at 7:00 pm #28831Duck
ParticipantThank you I will download new versions and try again.
February 9, 2011 at 7:52 pm #28832Duck
ParticipantHave just uploaded a fresh build of the plugin to the site but getting the same error when I try to activate it.
As a test I have uploaded the same plugin build to another server and it activated without error. This server is running PHP 5.2.14, same WordPress version.
February 10, 2011 at 3:49 am #28833amin007
ParticipantDid you completely delete the eMember on the server where you are trying to activate? To me it sounds like the update didn’t really overwrite the files. Please delete any “wp-eMember” folder from your server’s plugins directory then do a fresh install.
February 12, 2011 at 4:18 pm #28834Duck
ParticipantThank you! I did as you instructed and all works fine now.
*edit see next post*
February 12, 2011 at 4:50 pm #28835Duck
ParticipantHave another problem now, the plugin is active and seems to be working correctly however I am unable to create membership levels. When I try I get an error: ‘Membership Level “Free” couldn’t be created due to error.’
Any ideas as to the problem?
February 13, 2011 at 3:26 am #28836amin007
ParticipantI have sent you an email to get site access so I can check this out.
February 14, 2011 at 4:14 am #28837amin007
ParticipantTurned out that the database prefix in WordPress was changed from the default one to a 45 character long random name. MySQL only allows 64 characters for the table names. The membership table name together with the wordpress database prefix was going over this mark.
-
AuthorPosts
- You must be logged in to reply to this topic.