WordPress.org

Ready to get started?Download WordPress

Forums

Simply Poll
Update Returned Errors and Plugin Deactivated (11 posts)

  1. kirkward
    Member
    Posted 2 years ago #

    I used the automatic updater to install version 1.4 and received a warning and an error regarding line 12. The plugin was automatically deactivated.

    I have reverted to stable version 1.3.4 and the plugin has returned to an operable state.

    http://wordpress.org/extend/plugins/simply-poll/

  2. WolfieZero
    Member
    Plugin Author

    Posted 2 years ago #

    On it now.

    Thanks for posting.

  3. WolfieZero
    Member
    Plugin Author

    Posted 2 years ago #

    1.4.1 should be up now.

  4. kirkward
    Member
    Posted 2 years ago #

    Getting closer. LOL

    Plugin activated, however ...

    (1) Polls, Settings and Add New links all returned blank (all white) pages when clicked, and
    (2) My one existing poll is not showing.

    Will revert to 1.3.4 again. Looking forward to your fix. The plugin fits a big need I have.

  5. WolfieZero
    Member
    Plugin Author

    Posted 2 years ago #

    Odd. I cannot seem to replicate the issue... let me give this another go and I'll get back to you

  6. kirkward
    Member
    Posted 2 years ago #

    Correction ...

    Before reverting, I did a second automatic update, and the poll appears to be functioning properly.

    Polls page, Settings page and Add New page all appear correctly. The poll is displaying properly on the WordPress front end.

    Have no idea what caused the interim problem.

  7. kirkward
    Member
    Posted 2 years ago #

    Odd. I cannot seem to replicate the issue... let me give this another go and I'll get back to you

    Maybe something didn't close properly on the first update. I did the second update because when I went to my "Plugins >> Show All," there was another notice to update.

  8. WolfieZero
    Member
    Plugin Author

    Posted 2 years ago #

    I've done a second install on an active blog (that didn't have it previously) and it worked so might of just been blip.

    Thanks a bunch for your help though! Been most useful.

  9. kirkward
    Member
    Posted 2 years ago #

    Possibly the update from 1.3.4 to 1.4.1 had a bug, while the re-update from 1.4.1 to 1.4.1 cleared the problem.

    Thanks for the fix. Bye

  10. WolfieZero
    Member
    Plugin Author

    Posted 2 years ago #

    Good point, I'll give that ago

  11. WolfieZero
    Member
    Plugin Author

    Posted 2 years ago #

    Nope, didn't seem to cause any issues...

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic