- This topic has 3 replies, 2 voices, and was last updated 13 years ago by
.
-
Posts
-
Hi
I purchased the eMember plugin last week to control access to a support portal on our site. I installed on our staging server and it worked perfectly. I then installed on the live site and when you try login, a 500 server error appears in Chrome. In Firefox it is just a white screen. If you go to the login page again you will see that you are already logged in.
I have tried reinstalling the plugin as mentioned in other posts, and that did not work. I am running WordPress 3.0 on live (and 3.3.2 on staging). Due to the complexity of the site, it is not easy to upgrade without a lot of downtime, hence why it is still running on 3.0.
You can see the sign in screen here: http://www.exceedecommerce.com.au/support
username: testmember
password: test
Can you please provide me ideas on what I can do to fix this issue, as it is fairly urgent we get this running ASAP.
Thanks
Lance
I have contacted our server admin, and he couldn’t locate any specific errors. I have looked into the error log, and couldn’t find anything.
Are there any common issues I can advise the server admin to look at?
Thanks
Errors from an “Internal Server Error” only go to the server log (it is never shown anywhere on the screen). Usually it happens when you specified some rules to block certain actions from happening and then it can trigger that. It could also be a result from a combinations of actions conflicting. Here is what you can do:
1) Take a look at your server log so see what content it has
2) Do the action that triggers the 500 error
3) Now check the server log again for the additional details that went in there for this error.
Alternatively, try the following:
1) Load a fresh build of eMember:
https://support.tipsandtricks-hq.com/forums/topic/re-install-or-load-a-fresh-build-of-the-plugins
2) Do the plugin conflict test:
https://support.tipsandtricks-hq.com/forums/topic/test-to-identy-a-conflicting-theme-or-plugin
Also, enable debug in eMember settings and see what the last debug line is before it shows the error 500.
- You must be logged in to reply to this topic.