WordPress.org

Ready to get started?Download WordPress

Forums

Live Countdown Timer
[resolved] Broken when updating settings (6 posts)

  1. callumw
    Member
    Posted 3 years ago #

    In: Settings | Live Countdown
    I tried updating the time and text color and get an error message:

    Warning: unserialize() expects parameter 1 to be string, array given in /home/mydomain.com/public_html/wp-content/plugins/live-countdown-timer/live-countdown-timer.php on line 167

    It wasn't working so I stopped/restarted the plugin and I see that the colour change took, but the date etc reset to defaults.
    I changed them and got the same error message although it it seems to be working on my site. Don't want to touch it now in case it breaks it again :)

    CW

  2. tcampmany
    Member
    Posted 3 years ago #

  3. Ciprian Turcu
    Member
    Plugin Author

    Posted 3 years ago #

    A new version is available. Update and let me know if you have any more issues with it.
    Thanks.

  4. callumw
    Member
    Posted 3 years ago #

    It almost works.

    I set the widget active and selected "More Options"
    Entered all the details and it worked perfectly.

    I then tried to change the widget title and got an error:
    Warning: unserialize() expects parameter 1 to be string, array given in /home/mydomain/public_html/wp-content/plugins/live-countdown-timer/live-countdown-timer.php on line 83

    The widget which was working now shows the corrected title, but now no timer. Only the following error message:
    Warning: mktime() expects parameter 4 to be long, string given in /home/mudomain/public_html/wp-content/plugins/live-countdown-timer/calculateTime.php on line 7

    And it reset all the custom options back to default

    If I reset the "More Options" again it all shows perfectly.
    Looks like it's just changing the widget title that breaks it.

    Hope that's useful
    CW

  5. Ciprian Turcu
    Member
    Plugin Author

    Posted 3 years ago #

    I'm fixing it today. Thanks

  6. kwikone
    Member
    Posted 3 years ago #

    If you look at: this one there is the fix that works for me.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic