11 Comments

  1. Jeffrey

    “The plugin is perfect for seasonal widgets, temporary sales/promotions, events, live chat buttons, and any other time/date-dependent content.” Wow, this is what I have been waiting for a long time. Thank you for sharing this. I am going to give it a try now.

    Report

  2. Jeffrey

    OK, I installed on my site and it works beautifully! The only thing you need to pay attention to is that it uses UTC time, and it took me some time to set it up correctly. I added a text widget on my site and set it to be visible until this Friday, and I will see if it will go away on Saturday.

    Report

    • Martin Stehle

      @Jeffrey: After I have read the documentation of WordPress’ time functions I can confirm that you are right saying the plugin uses UTC. In the next version of the plugin the local blog time (as set on the general settings page) will be considered instead of UTC.

      Report

  3. Martin Stehle

    Sarah, thank you for your detailed article. I am the plugin author and open for all new aspects of the plugin.

    The option to select days of week is in progress.

    In the article you have mentioned the idea of an indefinite option for the end time of the widget display. What about to implement that as a checkbox?
    Because of technical limitations the highest and safest year number is 2037. What about instead of a checkbox a short text telling the user that he/she can give in a high number up to 2037 of year to realize “indefinite” visibility?

    Report

  4. Martin Stehle

    Jeffrey, the plugin does not use UTC, but the time of the server. So it seems your server uses UTC (and the plugin adopt that).

    Do you think the usage could be better? Any idea to improve the plugin is welcome.

    Report

    • Jeffrey

      Thanks for the explanation. I like the idea of using a checkbox for an indefinite option, instead of using textbox. By the way, why the highest number is 2037? Is it something related to PHP, WP, or MySQL?

      Report

  5. Sami Keijonen

    This Plugin seems really handy, gonna check it out and hopefully use it in some projects.

    Report

  6. Martin Stehle

    @Jeffrey: it is because of two things: how the current time is count and the operating system and applications which handle time data (like Apache, MySQL, PHP).

    You will find a very detailed (and understandable) explanation at Wikipedia “Year 2038 problem”: http://en.wikipedia.org/wiki/Year_2038_problem

    So the maximum time on 32-bit systems is 03:14:07 on Tuesday, 19 January 2038. Because a user of the plugin can type in a date after 19 January 2038 an error can occur. So in the plugin I set the maximum valid year value to 2037 to allow dates up to December 31, 2037 and to avoid a more complicated check for a date like “January 19, 2039”.

    Could that answer your question understandable?

    Report

  7. Jeffrey

    @Martin, thank you so much for your detailed explanation. I learned something new today. :-)

    Report

  8. Martin Stehle

    All your ideas and wishes are now implemented in the new plugin version 2.0. If you find them useful I would be glad if you would leave a review in the WordPress plugin page.

    Report

Comments are closed.

%d bloggers like this: