Hi Guys,
Since yesterday i cant log in into my 2 Admin oxwall accounts.
PLEASE HELP
1 account says "Parsor Error" and 500 error below sometimes and doesnt log me in and another says 500 error as below:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="font:18px Tahoma;">
Error 500<br />Internal Server Error.
</body>
</html>
We build. You grow.
Get best community software hereStart a social network, a fan-site, an education project with oxwall - free opensource community software
500 Error Plus Parsor Error [Answered] | Forum
Team Alia
Jul 16 '13
Webmaster.
Parse error usually appear when you add third party javascript that is not compatible with the .js used in Oxwall's core functionalities.
1. Enable DEBUG mode in config.php and try to log in again. Any errors instead of 500 one?
2. Check your server's error logs?
3. If nothing helps, provide admin panel username and pass. I will be glad to troubleshoot this issue for you.
Parse error usually appear when you add third party javascript that is not compatible with the .js used in Oxwall's core functionalities.
1. Enable DEBUG mode in config.php and try to log in again. Any errors instead of 500 one?
2. Check your server's error logs?
3. If nothing helps, provide admin panel username and pass. I will be glad to troubleshoot this issue for you.
Webster Molaudi
Jul 17 '13
Hi Aliia,
I have restored my back up and the site works fine, do you think maybe it might have been a plugin i installed ?
I have restored my back up and the site works fine, do you think maybe it might have been a plugin i installed ?
Webster Molaudi
Jul 18 '13
Hi Paul,
I think it s the plugin, i still get 500 error every now and then :( Okay thanks for the help
I think it s the plugin, i still get 500 error every now and then :( Okay thanks for the help
@Webster, it is possible it was a plugin, but without the error mode report it would be impossible to say 100% it could have been a DB fault that was fixed with a restore
