Closed (fixed)
Project:
Classified Ads
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Feb 2007 at 07:00 UTC
Updated:
2 Sep 2011 at 08:21 UTC
Jump to comment: Most recent file
Comments
Comment #1
mcurry commentedDefinitely a bug I introduced in 1.5. You can use an older version or wait for the next release build (1.5.1)
Comment #2
mcurry commentedDrupal-5-1.5.1 release is here:
http://drupal.org/node/123403
Should fix the problem.
Comment #3
bsuttis commentedGreat, this fixes it. Thanks!
Comment #4
mcurry commentedThanks for the quick report. Sorry for the trouble.
Comment #5
(not verified) commentedComment #6
eric66 commentedI have exactly the same problem with version 6.x.2.0-alpha6, any sugestions on how to patch/fix it? Thanks in advance!
Comment #7
mcurry commentedComment #8
fgmThis is currently still true on 6.* and being worked on. Publishing rules were a bit approximative and we have been formalizing them recently.
Essentially, when the patch lands:
- on creation, if the author is not an admin forcing publishing manually, default node creation options will be applied
- on update, if the author resets the date in 'reset' or 'force" mode, node will be republished, unless author is an admin and sets the unpublished status manually on the "Publishing options" fieldset
- when saving, either from the UI or in code, any node with an expiration date set in the past will always be unpublished
Note: similar issue on #123416: When renewing ad, re-publish if it's expired and workflow is set to publish automatically.
Comment #9
fgmComment #11
fgm#9: unpublish_checkbox-123396-1.patch queued for re-testing.
Comment #13
St4t0 commentedBug confirmed.
Patch fixes this in the latest 6.x-3.x
Comment #14
fgmAll tests pass: committed to 6.x-3.x.
Needs to be ported to 7.x-3.x.
Comment #15
fgmPropagated to 7.x too.