New Extension: Auto Expire
Development and Programming
I have just put the finishing touch to my second publicly released extension for EE 1.6.x and EE 2
You can grab a copy from GitHub: Auto Expire for EE 1.6.x Auto Expire for EE 2.x
Description Auto Expire adds the ability to any weblog to automatically expire new entries. It adds a predefined amount of time to the entry date. If an expiration date has already been set, that date will be used as the expiration date.
Usage 1.6.x After installing Auto Expire it’s settings are available at ‘Weblog Administration › Weblog Management › Edit Weblog Preferences > Weblog Posting Preferences’. I know it’s a bit hidden, but it seemed the most logical place to put them to me. (Screenshot)
Usage 2.x After installing Auto Expire you alter the channel settings on the extension settings page.
Changelog 2.x Auto Expire 2.2 - Added the ability to change the status of an entry on expiration.
Let me know what you think about it and if it could use some improvements.
Greetz, Wouter
Would love an EEE2 version, any chance, even for a fee?
Many thanks Lee
I was already planning on one for EE2.
I’ll see if I can free up some time to get it out as soon as possible.
Greetz, Wouter
Thanks so much. I’m planning to use it on a classified section of a site I run to expire ads after a month.
All the best Lee
Hi Lee,
I’m pleased to announce that I just finished the EE2 version of Auto Expire (updated first post).
I had to do a little overhaul in the usage of the extension since EE2 doesn’t allow the control panel HTML to be altered, so you have to set your preferences in the extension settings now.
I haven’t done a full bug testing session yet, but I haven’t found any so far… Let me know if you find any.
Greetz, Wouter
Much appreciated. If you are still open to requests, having Been There ported to 2.X would be killer for me. In any case, thanks for your work.
Much appreciated. If you are still open to requests, having Been There ported to 2.X would be killer for me. In any case, thanks for your work.
That shouldn’t be too much of a problem… I will look at it later today.
Greetz, Wouter
Hi Russ,
just wanted to let you know that Been There! is now also available for EE2. I updated the Been There thread.
Greetz, Wouter
Hey Wouter, huge thanks for auto expire. Do you have a PayPal account, I’d like to buy you a beer.
Hey Wouter, huge thanks for auto expire. Do you have a PayPal account, I’d like to buy you a beer.
You really don’t have to, but if you insist… I do enjoy a good glass of wine 😊
My PayPal account is: wouter at baseworks dot nl
Greetz, Wouter
Hi Wouter, any chance you could make the status of the entry change to closed when an article expires?
Best wishes Lee
Hi Lee,
I’ll see if I can put this in. It won’t be “live” as in the true sense of the word, because you’d need a cron job that would check if there are any entries that are expired, but I could close the entries when they are fetched from the weblog and they are expired.
I’ll look into it.
You were working with the EE2 version, right? In that case I’ll start with editing that one.
Greetz, Wouter
yes I’m an EE2er. Thanks for this!
First up congratulations on what looks like another great add-on. Was just wondering something though :
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.
I’m thinking that this might be useful on a site I’m currently working on but I’d need to set a specific status for the entry upon expiring it as the this is used for tracking purposes.
Best wishes,
Mark
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.
If the latter then when you try to enable the extension you get an error. Upon changing the name to contain the _ext.php at the end then all seems fine.
Best wishes,
Mark