@shenal92@janilyn409 , I had already cleared the cache and had checked for the same problem. It installs but doesn’t activate.
Trusting you, I cleared the cache again and updated the plugin. The site crashed again. Now I’m attaching the prints to see if you believe me.
I’m using version 2.1.1 which is stable and working very well. In fact, if you could make available a locked version 2.1.1 (which doesn’t ask for an update) I would be grateful, because every time an update gives a fatal error like this I have to go to the server to resolve it because the update with a fatal error takes the entire site offline.
Our developers have verified that the new update caused no fatal error on our dev site or test site at all. The fatal error was caused when there was a conflict. However, I assumed that the conflicting factor was still on your site. You need to find the source of the conflict or you will need to freshly reinstall our plugin by removing it and update the database, then get a new install.
As the fatal error is a technical issue, it’s required to check from the backend admin dashboard to find the source of conflicts. We are not allowed to ask for any further information from users on this forum so it is very hard to inspect from our end.
If the fatal error caused too much inconvenience for your site, you can kindly disable our plugin and consider an alternative.
Great news. I have got a response from our developers today that probably they have found the issue and fixed it with the latest version of this plugin. Please check back on our plugin to find the update.
After updating it, please clear the caches from your site and browser before checking again. This issue might be triggered due to the incompatibility with the older version of PHP on some sites. That is the reason why we could not confirm it on our test site until a user recently sent us details about the issue.
Thanks for your feedback. If you have any problem, feel free to reach out to us again.
It’s fortunate that we have been able to gather enough data about the issue to fix this. It’s quite hard to fidn the source of the issue at first though.
