Aaron Axelsen
Forum Replies Created
-
I have changed how some of this works in 2.0. If you are interested in testing see:
If you are interested in testing – see:
timezone handling is revamped in the 2.0.0 release – which I’m currently asking people to test.
For those of you who were interested in testing – please grab the version from the SVN trunk. http://downloads.wordpress.org/plugin/post-expirator.zip
I want to roll this out within the next few days. I have tested every upgrade scenario and post scenario that I can think of – so additional testers are welcome.
The only outstanding issue that I am still working on is:
– when checking default post categories, the categories of the epxiration box are also checked.
The changes included are:
* New: Improved debug calls and logging
* New: Added the ability to expire to a “private” post
* New: Added the ability to expire by adding or removing categories. The old way of doing things is now known as replacing categories
* New: Revamped the expiration process – the plugin no longer runs on an minute, hourly, or other schedule. Each expiration event schedules a unique event to run, conserving system resources
and making things more efficient
* New: The type of expiration event can be selected for each post, directly from the post editing screen
* New: Ability to set defaults for each post type (including custom posts)
* New: Renamed expiration-date meta value to _expiration-date
* New: Revamped timezone handling to be more correct with WordPress standards and fix conflicts with other plugins
* Fix: Removed kses filter calls when then schedule task runs that was causing code entered as unfiltered_html to be removed
* Fix: Updated some calls of date to now use date_i18n
* Fix: Most (if not all) php error/warnings should be addressed
* Fix: Updated wpdb calls in the debug class to use wpdb_prepare correctlyThis will be fixed in the 2.0 release that i’m working as fast as I can to button up – the entire way the back end work has been re-written.
MS or single installs? Anything else out of the ordinary on your installations?
Anything in the debug logs?
I believe I have a fix for this that will be in the 2.0 release (waiting to confirm its the best way to handle it) – hope to have that out in the not to distance future.
Just doing some cleanup and I’ll have to spend a couple days testing the upgrade path before releasing it to you guys to try out. Here is a sneak peak to date of whats changed:
* New: Improved debug calls and logging
* New: Added the ability to expire to a “private” post
* New: Added the ability to expire by adding or removing categories. The old way of doing things is now known as replacing categories
* New: Revamped the expiration process – the plugin no longer runs on an minute, hourly, or other schedule. Each expiration event schedules a unique event to run, conserving system resources and making things more efficient
* New: The type of expiration event can be selected for each post, directly from the post editing screen
* New: Ability to set defaults for each post type (including custom posts)
* Fix: Removed kses filter calls when then schedule task runs that was causing code entered as unfiltered_html to be removed
* Fix: Updated some calls of date to now use date_i18n
* Fix: Most (if not all) php error/warnings should be addressed
* Fix: Updated wpdb calls in the debug class to use wpdb_prepare correctlyForum: Hacks
In reply to: wp_cron calls to wp_update_post trigger ksesI have found that so far my best solution is to call kses_remove_filters before the wp_update_post call – and that seems to do the trick.
What I don’t know, is this the best way to handle it?
This will be changing in the new version – the guts are being re-written. I could easily adjust it so there is a separate function that does the expiration scheduling that you could just call with the correct variables for custom integration.
This will be fixed in the next release.
Can you give me some more information about your configuration/environment? I have been running this on 3.5.1 and have not seen this issue.
Furthermore, there are some big “under the hood” changes coming soon.
So – are you saying you are wanting to set a post to expire by just setting a value instead of using the meta box to configure it when editing the post?
Briefly – I can confirm the issue and it is related to kses. I will need to think through the best way to move forward with this one.