We are based in Europe with a GMT+1/GMT+2 time zone - support replies may be delayed due to time zone differences with your country.
- This topic has 7 replies, 1 voice, and was last updated 4 years, 2 months ago by
.
-
Posts
-
Hi,
I installed this plugin – https://bit.ly/372wPFP – it is apparently not working well with the Post Pay Counter pro plugin. The Speaker plugin is working fine with all of the other plugins on the website and I have quite a few of plugins installed, but as soon as I activate Post per pay pro I get this error – There has been a critical error on this website. I can refresh the website and use it for a moment but it gives of this error once in a while and it´s getting very frustrated as it can happen after I´ve finished an article and just hit the publish button and so on, thereby loosing the article. So I have no other choice than disabling the Post per pay plugin as I need the other plugin so I can offer those who need to listen to the text on the website have to have that option. I have deactivated the Post per pay plugin for now as I can´t work on the website while it´s doing this.Thank you!
Hi,
I cannot access the link. Either way, can you get some insights from your server logs? Any error we can work with?
A nice day,
StefanoWhere can I possible get those logs?
On a shared hosting, you’d most likely have to ask your host. On an Apache server, they usually live in /var/log/apache2/error.log, for example
There are no error logs for today or any day from the Apache server so I can´t give you any. I can give you access and you can reactivate the plugin and see what happens?
I sure can look, but if the errors are hidden from the visitor and only logged in the back (as it looks like, by your description), I wouldn’t be able to understand much. Maybe you can try to reactivate the plugin, have the error happen, deactivate it and hear from your host, mentioning that you would expect an error to have occurred at [TIME YOU TRIED]?
As I understand it, the errors that they see, are the same ones that I can see, so if I don´t see anything, then the host can´t see it either unfortunately. Shame that one of the most important plugins for my website is acting up of all the plugins that I have there :/
Well, that shouldn’t be the case. It is customary to hide errors from the frontend, since you don’t want visitors to see them, but they should still be logged somewhere. It is bad practice not to do so (it has to do with server configuration, not plugin-related), because then issues are virtually impossible to troubleshoot. Maybe your host can help in making sure logging is enabled? :/
- The topic ‘There has been a critical error on this website’ is closed to new replies.