MODx Bug/Feature Tracker and Feature Requests
Welcome to the MODx CMS Tracker. Please choose the appropriate project from the drop down menu and provide as much information as possible regarding your server environment and browser. Thanks!
FS#728 — Documents cannot be published with a publish date
Attached to Project —
MODx
Opened by Andy Shellam (andyccn) - Sunday, 24 December 2006, 06:44AM
Last edited by Paul Gregory (PaulGregory) - Thursday, 11 January 2007, 05:58PM
Opened by Andy Shellam (andyccn) - Sunday, 24 December 2006, 06:44AM
Last edited by Paul Gregory (PaulGregory) - Thursday, 11 January 2007, 05:58PM
| Task Type | Bug Report |
|---|---|
| Category | Core Distribution |
| Status | Not a Bug |
| Assigned To |
Garry Nutting (garryn) |
| Operating System | Linux |
| Severity | Low |
|---|---|
| Priority | Normal |
| Reported Version | 0.9.5 |
| Due in Version | 0.9.7 |
| Due Date | Undecided |
| Percent Complete |
|
Details
In 0.9.5 -1. Create a document
2. Set the publish status to Yes, and publish date to Now
3. Save
-- document is saved as unpublished, with Now as published date --
4. Click publish document from document's context menu
-- document is published, but with no published date
5. Edit the document
6. Set published to Yes - leave date as is ('Now' from point 2 above)
7. Save
-- document is unpublished with published date set --
8. Edit the document again
9. Set published to Yes - leave date as is ('Now' from point 2 above)
10. Save
-- Document is now saved as published with publish date --
As you can see, quite a pain just to get a published date in the document!!
I also think that when you 'Publish document' from the doc's context menu, it should set the 'publish date' to Now automatically.
This task depends upon
This task blocks these from closing
It does this already, but the 'published date' is actually "publishedon". Andy, use publishedon instead of pub_date and you'll be fine.
"pub_date" is the datetime at which the publication status should change, and at which point the date should be removed - ie a future tense. An embargo date, if you will.
The actual bug in the above 10 step method is that a date that has passed somehow stays in the "pub_date" field if you publish it in a particular way.
You are not alone in expecting pub_date to be a date that is kept; this confusion is not helped by the total absence of the publishedon date in the manager, and the fact that the pub_date is tantalisingly editable but publishedon is not (unless you write a module).
However, those are separate issues.
I am therefore closing this bug because it is not a bug.
The bug is in itself the fact that the correct published date is not shown in the manager - what I'm expecting is that "published date" when you preview a document shows the published date as in the "published date" field when you edit a document.
Also when you edit a document and set a "published date" of "now" - even though "published" is ticked, it still unpublishes the document when you save it. That is the bug.
The date on which a document is published is not currently shown in the manager at all; that's not the bug that you described.
Your second point assumes that "now" works instantly. It does not. "Now" is actually an entirely pointless publication date. You are not supposed to set a publication date that has passed.
Telling MODx that a page is to be published at a given time and that a page is published... these are contradictory settings.
Yes, it could be argued that the system should identify that the date has passed and switch to published automatically, but that should remove the date.
To repeat: the publication date field is not what you are seeing, you are seeing an "action date".