Latest Update gives error
Quote from ceezed on February 8, 2018, 9:12 pmHi,
Whenever I create a new topic and press submit the page shows “The page isn’t working” “HTTP Error 500”. Then if I reload the same URL it shows the topic has been created.
I tried to disable the caching plugins, ssl, even cloudflare, change the theme but it didn’t fix.
Then, I rolled back to 1.7.1 still the error remained. Then, I rolled back to 1.7.0 and it’s working fine. Please fix this so I can update the plugin in future.
Hi,
Whenever I create a new topic and press submit the page shows “The page isn’t working” “HTTP Error 500”. Then if I reload the same URL it shows the topic has been created.
I tried to disable the caching plugins, ssl, even cloudflare, change the theme but it didn’t fix.
Then, I rolled back to 1.7.1 still the error remained. Then, I rolled back to 1.7.0 and it’s working fine. Please fix this so I can update the plugin in future.
Quote from Asgaros on February 8, 2018, 9:25 pmHello ceezed,
Error 500 is an internal server error. Without some more details it could be caused by everything. You can try to install an WordPress extension like Query Monitor or enable debug-mode in WordPress. This should generate some error messages-output which can help to find the cause for this problem.
Hello ceezed,
Error 500 is an internal server error. Without some more details it could be caused by everything. You can try to install an WordPress extension like Query Monitor or enable debug-mode in WordPress. This should generate some error messages-output which can help to find the cause for this problem.
Quote from quincybatten on May 4, 2021, 9:06 amThe error is too generic and does not tell you exact problem. What you need is to find out what is the real issue. If your site is serving a Internal Server Error, this can be caused by a number of things, such as:
- Errors in .htaccess files
- Server permission
- Server timeout
- Script timeout
- Or some other Web Server Issues
Normally, a permissions issue on the file (or files) would be one cause of the 500 Internal Server Error. The simple solution is to run chmod 644 on the problem file(s) or chmod 755 on the directories.
$ sudo chmod -R 777 /”your files location”
The best way to debug the error depends upon the server and what’s actually running at the time. Consider some debugging tips to help diagnose and fix common causes of this problem.
The error is too generic and does not tell you exact problem. What you need is to find out what is the real issue. If your site is serving a Internal Server Error, this can be caused by a number of things, such as:
- Errors in .htaccess files
- Server permission
- Server timeout
- Script timeout
- Or some other Web Server Issues
Normally, a permissions issue on the file (or files) would be one cause of the 500 Internal Server Error. The simple solution is to run chmod 644 on the problem file(s) or chmod 755 on the directories.
$ sudo chmod -R 777 /”your files location”
The best way to debug the error depends upon the server and what’s actually running at the time. Consider some debugging tips to help diagnose and fix common causes of this problem.