Title: Florence ANDROLUS's Replies | WordPress.org

---

# Florence ANDROLUS

  [  ](https://wordpress.org/support/users/fandevelop/)

 *   [Profile](https://wordpress.org/support/users/fandevelop/)
 *   [Topics Started](https://wordpress.org/support/users/fandevelop/topics/)
 *   [Replies Created](https://wordpress.org/support/users/fandevelop/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/fandevelop/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/fandevelop/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/fandevelop/engagements/)
 *   [Favorites](https://wordpress.org/support/users/fandevelop/favorites/)

 Search replies:

## Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Cron event stuck for eight years; cannot delete](https://wordpress.org/support/topic/cron-event-stuck-for-eight-years-cannot-delete/)
 *  [Florence ANDROLUS](https://wordpress.org/support/users/fandevelop/)
 * (@fandevelop)
 * [4 months, 3 weeks ago](https://wordpress.org/support/topic/cron-event-stuck-for-eight-years-cannot-delete/#post-18826078)
 * Hello [@celeste-9](https://wordpress.org/support/users/celeste-9/),I’m delighted
   to hear that version 1.0.3 resolved the issue! It’s excellent news that the task
   has disappeared from WP Crontrol and, most importantly, that your error logs 
   are finally clean.The “Ghost Cron” was indeed stubborn, but it’s precisely for
   these kinds of complex cases that I developed this deep cleanup tool.Thank you
   so much for your patience and detailed feedback, which helped me refine the fix.
   If you found the plugin helpful, please leave a review; it greatly benefits the
   project!Best of luck with your site.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Cron event stuck for eight years; cannot delete](https://wordpress.org/support/topic/cron-event-stuck-for-eight-years-cannot-delete/)
 *  [Florence ANDROLUS](https://wordpress.org/support/users/fandevelop/)
 * (@fandevelop)
 * [4 months, 3 weeks ago](https://wordpress.org/support/topic/cron-event-stuck-for-eight-years-cannot-delete/#post-18824828)
 * Hi again [@celeste-9](https://wordpress.org/support/users/celeste-9/),
 * 
   I just switched to version 1.0.3 with a new deep detection tool. Based on your
   screenshots, it seems your 2017 task is a native WordPress cron job (Native WP
   Cron) stored in the wp_options table.This type of old task can sometimes prevent
   the scheduling system from updating (causing the could_not_set error you observed),
   because standard tools are hesitant to modify it if the data is incorrectly formatted.
 * What version 1.0.3 offers:
 * It attempts to identify these “ghost” tasks (you’ll see them labeled “Native”
   in the table).
   If detected, the cleanup button will force its deletion and attempt
   to rebuild a clean table to unblock your site.This is a very promising lead for
   resolving your problem, I hope. Please let me know how it goes!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Cron event stuck for eight years; cannot delete](https://wordpress.org/support/topic/cron-event-stuck-for-eight-years-cannot-delete/)
 *  [Florence ANDROLUS](https://wordpress.org/support/users/fandevelop/)
 * (@fandevelop)
 * [4 months, 3 weeks ago](https://wordpress.org/support/topic/cron-event-stuck-for-eight-years-cannot-delete/#post-18824345)
 *     ```wp-block-code
       Hi @celeste-9 ,Thank you for your detailed feedback. Your analysis was spot on: the previous version of the plugin was indeed too restrictive with the 90-day limit and was missing "orphan" tasks like yours dating back to 2017.I have just released version 1.0.2 of Fand Transient and Action Cleaner specifically to address this type of legacy blockage. Here is what I’ve improved for your specific case:Legacy Detection: The plugin no longer relies on the "last attempt" date (which is often empty for old bugs) but now uses the initial scheduled date. This finally allows it to track down and list your 2017 tasks.Invalid Date Cleanup: The plugin now forces the removal of rows with corrupted dates (like 0000-00-00) that often prevent WordPress from updating the cron array.Native Transient Purge: I have expanded the cleanup to include all expired transients, which should help unblock write operations in your wp_options table.What I recommend doing:Update the plugin to version 1.0.2.Go to the plugin settings page. You should now see your 2017 tasks appearing in the lists.Click the "Run Cleanup Now" button.This should force a purge of the actions related to woocommerce_send_queued_transactional_email and clear out the orphan logs bloating your database. If the could_not_set error persists after this, @lovingbro's suggestion about renaming the cron option would be the next step, but my plugin will have already handled the surgical deep cleaning.Let me know how it goes!
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[PPOM - Product Addons & Custom Fields for WooCommerce] les lignes “Add options” n’apparaissent plus dans les conditions](https://wordpress.org/support/topic/les-lignes-add-options-napparaissent-plus-dans-les-conditions/)
 *  [Florence ANDROLUS](https://wordpress.org/support/users/fandevelop/)
 * (@fandevelop)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/les-lignes-add-options-napparaissent-plus-dans-les-conditions/#post-18055352)
 * Bonjour
   Les champs pricematrix ne fonctionnent plus depuis la mise à jour. Je
   n’ai plus que le prix produit qui change avec la quantité au lieu de prendre 
   en compte le champ pricematrixCordialement,Florence AndrolusFan-develop
    -  This reply was modified 1 year, 9 months ago by [Florence ANDROLUS](https://wordpress.org/support/users/fandevelop/).

Viewing 4 replies - 1 through 4 (of 4 total)