Version 2.0.5 not working

  • Was so happy to see that development had resumed on this plugin, but after upgrading to the latest version was disappointed to find it just isn’t working. At all.

    Posts are not expiring, no notifications are being sent, and all expiration dates set by previous versions of this plugin have been changed to December 31, 1969.

    I had a previous version working thanks to an edit suggested in this forum, but when I tried to apply that fix to v2.0.5 it threw a fatal error.

    Hoping this can be resolved…this plugin is extremely useful, when it works. I appreciate all the efforts that have gone into it!

    https://www.ads-software.com/plugins/content-scheduler/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Paul Kaiser

    (@freakingid)

    Greetings,

    Are there any more details about the error you received?
    Also, are you by chance using a custom date format or custom time format on your site?

    Let me know; we’ll get you fixed up.

    Thanks,
    Paul

    Thread Starter New Hope Church

    (@new-hope-church)

    Thanks so much for the speedy reply! No other details or error messages, it just stopped working and reset all existing expiration dates to 12/31/1969.

    We are using a standard date format (F j, Y) but a custom time format (g:iA). Note the only deviation here is that there is no space between the time and the AM/PM.

    In the meantime I’ve gone back to a backup copy I had of 1.0 that included the edit suggested here, and things are working for now. However, this has now messed up all the expiration dates again, changing them to a string of numbers that probably represent a date. I’m in the process of changing those back, but if an impending update of Content Scheduler might fix this, I won’t take the time to make all these manual changes.

    Thanks again!

    Plugin Author Paul Kaiser

    (@freakingid)

    I am sorry your expiration dates got messed up. I’m about to release version 2.0.6 which will not cause that problem any more, but there isn’t a way to automatically go back and fix yours now.

    Just a quick explanation on my mistake:
    * New version of CS stores expiration date/time as a unix timestamp, in UTC timezone. This is much more reliable no matter where your site’s server / timezone are set.
    * Date/time were previously just stored as a string, so when you activate the new CS, it migrates those strings to unix timestamps.
    * I did not consider the effect of users having custom date / time formats. This confused PHP when I attempted to do this migration. Others got 1/1/2000 as their resulting date / time.

    So, the best I can do at this point is release 2.0.6 and hope it doesn’t take you forever to re-add your desired expiration date / times.

    Look for 2.0.6 probably tomorrow (Friday 1/16.)

    Thanks for (hopefully) understanding,
    Paul

    Thread Starter New Hope Church

    (@new-hope-church)

    Of course, Paul! Thanks again for your good work.

    Hello Paul,
    I also have problem with 2.0.5. When you go back and update a specific post the existing expiration dates is reset to 01/01/2000! Is it possible to fix?

    Plugin Author Paul Kaiser

    (@freakingid)

    Man, I said I’d push 2.0.6 like a week ago, and didn’t get it done. Sorry gang.
    The code is done, but I need to test a few more things before pushing.

    Take your time Paul – its an excellent piece of work you done!

    Thread Starter New Hope Church

    (@new-hope-church)

    I’m with MoMiro…your work is appreciated and we understand you have other priorities!

    Hi Paul,

    Know its been a few months, but just wondering if 2.0.6 is coming out? Just had to do the same as New Hope Church and downgrade to v1.0.0 of the plugin.

    Otherwise, loving your work boss ?? thanks for making a great plugin.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Version 2.0.5 not working’ is closed to new replies.