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

Comments

fgm’s picture

Version: 7.x-3.0 » 7.x-3.x-dev
Assigned: Unassigned » fgm
Priority: Major » Normal

Confirmed: 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.

fgm’s picture

Status: Active » Needs review
StatusFileSize
new5.19 KB

Suggested patch.

fgm’s picture

Status: Needs review » Fixed

Fixed in today's dev version.

fgm’s picture

Version: 7.x-3.x-dev » 6.x-3.x-dev
Status: Fixed » Patch (to be ported)
StatusFileSize
new24.22 KB

Tentative backport for D6.

fgm’s picture

Status: Patch (to be ported) » Needs review

Setting to Needs Review for bot.

Status: Needs review » Needs work

The last submitted patch, 0001-Issue-1733594-fixed-infinite-grace-not-being-honored.patch, failed testing.

fgm’s picture

Version: 6.x-3.x-dev » 7.x-3.x-dev
Status: Needs work » Fixed

Apparently the QA bot can no longer run D6 tests. Backport committed with test on 6.x-3.x-dev too.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.