• Resolved SpotlightWeb

    (@spotlightweb)


    Hello when updating to the latest version of the plugin, it fails. The error message is below. I have removed the path in my code and replaced it with /~/ for security reasons.

    Both the Constant Contact API and Constant Contact Form Designer become deactivated due to an error: Plugin file does not exist.

    The update process is starting. This process may take a while on some hosts, so please be patient.

    Enabling Maintenance mode…

    Updating Plugin Constant Contact API (1/2)
    Warning: fopen(/~/wp-content/plugins/constant-contact-api/form-designer.php): failed to open stream: No such file or directory in /~/wp-includes/functions.php on line 4004

    Warning: fread() expects parameter 1 to be resource, boolean given in /~/wp-includes/functions.php on line 4007

    Warning: fclose() expects parameter 1 to be resource, boolean given in /~/wp-includes/functions.php on line 4010

    https://www.ads-software.com/plugins/constant-contact-api/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Zack Katz

    (@katzwebdesign)

    What happens if you delete it first, then re-install it?

    Same issue here, except for my site went white screen of death – had to revert to previous version…
    I was upgrading from Version 2.4.1 to 3.1.3

    Plugin Author Zack Katz

    (@katzwebdesign)

    @dcooney What happens if you delete it first, then re-install it?

    I’m not sure. It happened on a client site, so I quickly reverted it for them. I will try this another approach on Monday.

    thanks for responding.

    jwurster

    (@jwurster)

    I had the same issue. I tried to follow your install old version but failed when I tried to deactivate it. So, I deleted the plugin folder. I then uploaded the old version. I activated it. It is now reactivated.

    I get the message that there is a new version for the plugin as well as the form designer plugin. Won’t activate again until the problem is resolved.

    jim

    Plugin Author Zack Katz

    (@katzwebdesign)

    I just released 3.1.4, which I believe should fix these issues. Thanks for reporting them – please let me know if the problem persists in 3.1.4!

    EngagingSchools

    (@engagingschools)

    Hi Zack,

    I am experiencing the same issue as dcooney. My site (engagingschools.org) is still down.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Error with Upgrade to’ is closed to new replies.