Under
Administer > Content Management> Content
Please provide a listing under the "STATUS" column which would indicate "Not Published/Scheduled" instead of just "Not published".
It would be even better it said "Scheduled to publish on {date and time}"
Additionally if I can ask for one more thing: A block for Administrators which would list the first x scheduled posts in chronological order.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | content with scheduled tab.jpg | 165.76 KB | jonathan1055 |
Comments
Comment #1
AjK commentedThe page you are describing is rendered by Core and therefore a module (such as Scheduler) cannot change the table contents. However, there's always a way in Drupal ;)
I wrote a handbook page here that explains how to do what you want.
Comment #2
AjK commentedSetting this to "fixed" rather than "by design" as I want the issue visible for a while so that the originator sees it.
Comment #3
tcblack commentedGot it, thanks that did the trick!
Comment #4
(not verified) commentedComment #5
dropbydrop commentedPlease cooperate with core developers so the scheduled for publishing status appears.
Otherwise, drupal seems broken for the end-users. They can't get it why the CMS cannot show such status.
Thanks
Comment #6
jonathan1055 commentedExcuse me, but AjK has already said above that the page is created by core, and contrib modules cannot alter it, although the helpful handbook page shows how it can be done.
However, we do already have the functionality you want. There is a tab which Scheduler provides on the content page (both in D6 and D7) to list the nodes which are scheduled - see attached screen shot for D7
Jonathan
Comment #7
dropbydrop commentedThen we should open a ticket to core. thanks
Comment #8
jonathan1055 commentedWhen you have, please could you post a link to it in this thread. But I don't think there is actually anything wrong with core.
Leaving this open, so others can see it and correct me if I have mis-understood the issue.
Jonathan
Comment #9
eric-alexander schaefer commentedCore would need to provide means to set custom node states. I guess that's what dropbydrop wants to ask for in a ticket for core. Until this is resolved scheduler works as designed...