• hi there,

    last upgrade generate a fatal error and plugin can′t be activated

    • This topic was modified 1 week, 4 days ago by faninja.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Janilyn T

    (@janilyn409)

    Hi @faninja ,

    Our developers have released a new update. Please update to version 2.1.3 and clear caches before checking again. We will wait for your feedback.

    Best regards.

    Thread Starter faninja

    (@faninja)

    Hi @janilyn409

    Fatal error still remains at upgrade 2.1.3

    where i get the 2.1.1 version ?

    Plugin Support Janilyn T

    (@janilyn409)

    Please make sure you check it in an Incognito tab and clear the caches from both your site and browser.

    You can get version 2.1.1 at the end of this page as a workaround: https://www.ads-software.com/plugins/wpc-buy-now-button/advanced/

    If possible, please provide us with some images of the issues on your site. I will check and report to our developers.

    Best regards.

    Hi Team

    The issue is still the same: “Version 2.1.3 a fatal error and plugin can′t be activated.” we have followed clearing cache as well

    • This reply was modified 4 days, 4 hours ago by shenal92.
    Thread Starter faninja

    (@faninja)

    @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.

    Thanks.

    Plugin Support Janilyn T

    (@janilyn409)

    Hi @faninja ,

    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.

    Best regards.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.