New Extension: Auto Expire
Development and Programming
Could this be made so that you can choose a status for each weblog from their status group that the entry would get set to upon being expired.
You’re in luck… because that’s exactly what I was working on and nearly finished btw… (see attached screenshot)
Oops also as a quick note meant to mention that it seems like the add-on (1.6.x) wants the language file to be called lang.auto_expire_ext.php instead of lang.auto_expire.php which is what the download contains.
thanks for the heads up, I’ll fix it as soon as I update the 1.6.x version.
As I said, I am nearly finished with the status change. Just checking if I missed anything now…
Greetz, Wouter
As I said, I am nearly finished with the status change. Just checking if I missed anything now…
Oops sorry I hadn’t seen it mentioned above. Must have skimmed that part. My apologies.
Can’t wait to give it a test with the status function in there too.
Best wishes,
Mark
Oops sorry I hadn’t seen it mentioned above. Must have skimmed that part. My apologies.
I mentioned it above the quote… so it wasn’t you… 😊
Okay… I’ve updated the EE 2.x version to automatically change the status of an expired entry to a status of your choosing. This happend on load… any load, be it CP or front-end. New version has been pushed to the GitHub repository.
Most of the work went into the update mechanism of the extension itself… never done that before, so it was a bit of trial and error.
Have fun with it and let me know if you find any bugs.
Brillant, thanks very much indeed!
Okay… I’ve updated the EE 2.x version to automatically change the status of an expired entry to a status of your choosing. This happend on load… any load, be it CP or front-end. New version has been pushed to the GitHub repository. Most of the work went into the update mechanism of the extension itself… never done that before, so it was a bit of trial and error. Have fun with it and let me know if you find any bugs.
Any chance of the 1.6.x version? 😉
That’s the one I was testing. I’m not really doing any real testing with 2.0 at the moment.
Best wishes,
Mark
It’ll be here soon™
Greetz, Wouter
It’ll be here soon™ Greetz, Wouter
Now that’s what I call exceptionally generous.
Can’t wait to see this one. Hope you have a great night.
Best wishes,
Mark
Hi Wouter, wondering if you zipped up the right set of files. Downloaded from git hub, installed and I see no difference. perhaps I’m doing something stupid - it’s been known 😊
I copied the files individually and it’s working. Now to test…
Got a nasty feeling it not quite working. Looks like the status is set to closed when an entry is created, not when the expiry time is reached. Also the Expiration Date in content/edit date tab is empty.
What did you download from the GitHub repository? The one in the Downloads section or just the new source?
Thanks for the download link. When I create a channel entry via the cp, expiration works as expected, but when I create a channel entry via a SAEF the status is immediately set to closed (even though the SAEF is setting the status to open). Is that anything in your lovely extension that might be causing this. Or should I work harder at tracking the SAEF problem down.
Cheers Lee
Thanks for the download link. When I create a channel entry via the cp, expiration works as expected, but when I create a channel entry via a SAEF the status is immediately set to closed (even though the SAEF is setting the status to open). Is that anything in your lovely extension that might be causing this. Or should I work harder at tracking the SAEF problem down. Cheers Lee
Now that you mention it… it might not even set the expiration_date when inserting an entry through an SAEF… I’ll have to look into that.
Greetz, Wouter
Cool, it was sending me mad.