In order to avoid that the classfied node from being remove, i set the grace delay for expired ads to -1
But still, after the expiration date, during the cron, the node is removed.
Notice: in the node edit form, settings are set on: Keep current expiration date
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 0001-Issue-1733594-fixed-infinite-grace-not-being-honored.patch | 24.22 KB | fgm |
| #2 | 0001-Issue-1733594-infinite-grace-was-not-honored.patch | 5.19 KB | fgm |
Comments
Comment #1
fgmConfirmed: the current logic in _classified_scheduled_build_purge() incorrectly uses that parameter. As a simple workaround, just choose a very long grace delay instead of -1, like 365 for one year: the grace delay is expressed as a number of days.
Downgrading to normal since there is a simple workaround and it does not affect day-to-day operation.
Comment #2
fgmSuggested patch.
Comment #3
fgmFixed in today's dev version.
Comment #4
fgmTentative backport for D6.
Comment #5
fgmSetting to Needs Review for bot.
Comment #7
fgmApparently the QA bot can no longer run D6 tests. Backport committed with test on 6.x-3.x-dev too.