Paul Kaiser

Yes, you can do this.
1. You would have to have Content Scheduler plugin activated.
2. For each Post or Page you want to expire, you will need to set two custom fields:
a. _cs-enable-schedule (This must be set to “Enable”)
b. _cs-expire-date (This must be set to a date/time string in the format of 2011-04-24 20:58:00, that is YYYY-MO-DA HH:MM:SS)

FYI, the underscore (_) at the beginning of the field names makes them NOT show up in the custom field editor on your Post Edit page, so you won’t be able to see their values in the custom fields box — you’ll have to see them in the Content Scheduler box.

I hope this helps,
Paul K

Hi Tessina,
Glad you like the concept of Content Scheduler.
I’m fixing a large issue right now affecting PHP 5.2 users.
After that, I’ll consider adding the “remove tags” request.
Thanks for your input, and take care.
Paul K

I’ve been looking at some significant differences between PHP 5.2.x and 5.3.x. I want to make the plugin work with 5.2.x, and have changed my development environment to let me do so. I wouldn’t encourage your host to move to PHP 5.3. This fix is a priority for me, for sure.
Thanks,
Paul

Kevupton: Actually, I need the PHP version, rather than phpmyadmin. You probably use cPanel with BlueHost, and can probably check in the lower-left corner to discover program versions on the server. (I really should put a troubleshooting tab in CS to help folks with this, but that doesn’t help you at present…)

Vernon: Indeed, another PHP 5.2.x not working. THANKS for your info!

It is possible for another plugin to cause Content Scheduler (CS) to fail, but that has been ruled out for most folks. For the scheduling problem, you can rule that out by deactivating CS and then reactivating it, but not activating other plugins AFTER CS.

The potential for other plugins to mess up scheduling is their improper use of a custom time period for checking. They can accidentally remove all custom time periods, such as Content Scheduler’s “CS User Configured” period.

Hmm… I just got an idea.
Paul

Greetings Vernon, and anyone else still having problems getting content to expire. I’m spending a lot of time trying to figure out a solution — my plugin is following the rules, and many folks use it with success, but still too many are having problems.

It is possible this is related to PHP version 5.2. I haven’t seen any installs using PHP version 5.3 with a problem yet. However, I need a bit more data to draw that conclusion and try to make it work.

Please, if you cannot get Content Scheduler to work, get me the following info:
1. WordPress version.
2. Content Scheduler version.
3. PHP version on your server.
4. Your web host, if applicable (e.g., Hostgator, Dreamhost, etc.)

I sincerely want to fix this problem and move on to taking feature requests for the community.

Take care,
Paul Kaiser

I’m having similar problems with my plugin Content Scheduler. Some people have no problems at all. Other people cannot get it to work at all. Still others have it just begin working out of the blue with no rhyme or reason why.

I haven’t done anything funky — I just followed the the rules on how to schedule wp-cron jobs. I’ve looked at your plugin, Post Expirator, too, and we’re both handling the scheduling in the same way.

I am beginning to see that folks on PHP 5.2 may be the ones having issues, and with PHP 5.3 they have none. My dev install (XAMPP) is 5.3 so I need to roll back PHP to test.

Anyway, I thought I’d share, because it seems people are having the same issues with both of our plugins, even though their WP Scheduled posts are working.

Good luck, and I hope you’ll share any info you might come up with in solving this. I know I will.
Paul K

Hi Ricardo,
I’m not sure if you’ve noticed, but I did add localization support in recent versions of Content Scheduler. I also found the following resource for those who want to translate plugins:
https://urbangiraffe.com/articles/translating-wordpress-themes-and-plugins/
I’m still working on reports of Content Scheduler not executing properly on some systems.
Anyway, if you end up translating anything, please let me know.
Take care,
Paul

I’m publishing a separate, smaller plugin called “Content Scheduler BLOCKS” that will help you do this.
A similar plugin by someone else is at:
https://www.ads-software.com/extend/plugins/scheduled-content/
But, it looks like maybe that only has an “on” attribute, not sure.
Content Scheduler BLOCKS will let you use shortcodes to:
1. Surround content you want with a “start” date.
2. Surround content you want with a “stop” date.
3. Surround content you want with both a “start” and “stop” date.
For instance, I used it to “start/stop” an image of our old Mayor and “start/stop” an image of our incoming Mayor — that way I was able to schedule it a few days ahead of time so I could go on vacation.
Anyway, I’ll release Content Scheduler BLOCKS in a few days — hopefully it will help you.
— Paul

Just a few minutes ago, I released Content Scheduler 0.9.5. The main change for this version is i18n support. I’m *pretty sure* I did it right.

Please let me know of any translations you do, and of any problems you run in to that might indicate I didn’t handle i18n correctly.

Cheers,
Paul

Hi Erik, (and anyone else…)
I’m finishing i18n today, while trying to figure out why some folks can’t get their posts to expire. I don’t have a multisite setup for testing right now. Would you be willing to test it out if I send you a copy with multisite support, to speed things along?
Thanks,
Paul

Hi Juri,
I apologize for missing this forum post. Thanks for checking out Content Scheduler.
— I could easily make the default expiration time configurable. Let me know if you’re still needing this, and I can move that in for this next version (0.9.5)
— Multiple expiration settings, by category and such: That feature is part of the paid version of the plugin I’m working on. It’s fairly nifty, as you can set up expiration “profiles” and then assign those to different categories and/or posts. The paid version is still being tested, though.

Please let me know if it would still be helpful for me to add the expiration time default in version 0.9.5.
Take care,
Paul

Hi MrVictor,
Thanks for trying Content Scheduler.
You poked me in to getting a move on with i18n support. I’m working on it right now. I did run in to an issue, because some of the options are stored as English string values. I’m changing version 0.9.5 to replace those string values with integers. It’s all behind the scenes, but I’m just trying to do things the “right” way.

Also struggling with some users not able to get their posts to expire. I’m assuming you’re not having such issues? A real vexing issue, that I’m trying hard to fix ASAP.

Thanks again,
Paul

Hi Nikolas and moxie,
Thanks for checking out Content Scheduler, and for sharing some nice ideas.
* Auto expire every post by certain amount:
— This is certainly doable.
* Different expirations for different categories:
— This can be done, as well. It is a feature I’m adding to a paid version, though.

As I write this reply, I’m working on proper i18n support, and trying to figure out why some people cannot get posts to expire on their setups. Once I get these problems worked out, I’ll see about adding your requests.

Thanks again,
Paul

Hey, goodlookinlondon, I see you got it working properly on your site. Can you share what you had to do?
Take care.

See if Content Scheduler plunging will do the trick. (self promo)