Changeset 730365
- Timestamp:
- 06/23/2013 02:00:27 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
the-events-calendar-housekeeper/tags/1.2.0/readme.txt
r714128 r730365 13 13 == Description == 14 14 15 Developed to work with The Events Calendar 3.0, this plugin allows for expired events to be automatically vacuumed up rather than leaving them to clutter up your database. 16 _If you are still using The Events Calendar 2.x then you should use [this older version of Housekeeper](http://downloads.wordpress.org/plugin/the-events-calendar-housekeeper.1.0.3.zip)_, 17 noting that it still has some minor bugs and of course remembering that awesome people use the latest and greatest. 15 Developed to work with _The Events Calendar 3.0,_ this plugin allows for expired events to be automatically vacuumed up rather than leaving them to clutter up your database. 18 16 19 17 * Configurable: clean up events almost as soon as they have expired or enforce a buffer period of 1 week upto 6 months … … 21 19 22 20 By default, the plugin schedules clean-up tasks to run once a day and limits itself to handling a maximum of 100 events at any one time. This can be adjusted programmatically for special cases. 21 22 Can't get it to work? Check out the FAQs in the first instance and if that doesn't work feel free to post on the 23 [plugin support forum](http://wordpress.org/support/plugin/the-events-calendar-housekeeper). 23 24 24 25 = Author = … … 36 37 == Frequently Asked Questions == 37 38 39 = How do I enable garbage collection? = 40 41 Visit _Events > Settings > Housekeeping_ ... if you can't see this tab then make sure you have activated the plugin, first of all! Remember also that the current version of 42 _Housekeeper_ is built to work with The Events Calendar 3.0. If for example you are using a much older version then it may not work. 43 44 = I have enabled garbage collection but nothing happens! = 45 46 Assuming the expiry criteria is being met then this could be a problem where local loopbacks are not allowed within your hosting environment. _Housekeeper_ relies on something called 47 "Scheduled Tasks" so that it can work its magic in the background, as it were. However not all hosting environments are conducive to this. If you think that might be the problem then 48 check in with your hosting provider and/or search for "alternative cron solutions". 49 38 50 = How are recurring events handled? = 51 39 52 Any instances of recurring events meeting the _Expiry Criteria_ are deleted - those instances not meeting the criteria are preserved. This seemed like the most logical way to approach recurring events but any other ideas are welcome. 40 53 41 54 = What if the wrong events are deleted? = 55 42 56 That's completely possible for a variety of reasons. First of all, ensure your server and WordPress date/time settings are correct. Second, but more importantly, back-up before you use it and then keep on backing-up, frequently and often. 43 57 You _should_ be doing this anyway - and remember! - a back-up is useless unless you know how to restore it. … … 47 61 48 62 = Does an event expire after it has started or after it has ended? = 63 49 64 In the eyes of this plugin an event has expired after it has started and this is flagged up in the settings tab. That may not always be ideal - and for those cases you 50 65 can adjust the expiry criteria appropriately or just deactivate this plugin. 51 66 52 67 = I found a bug = 68 53 69 Please post details on the forum. Better yet, post a fix and add appropriate details. This is free and open source software and comes with no guarantees, so bear that 54 70 in mind first of all. 55 71 56 72 = I need help! = 73 57 74 Feel free to post on the support forum, but remember that support is not guaranteed (nor is the plugin) ... after all, it's free. 58 75
Note: See TracChangeset
for help on using the changeset viewer.