Someone will tell me if I am posting this in wrong location. This seems similar if not the same issue as http://drupal.org/node/344138 (Displaying list of scheduled nodes (contrib)), but I can't see that the solution is built into the current version of Scheduler.
The issue - Having created a node, set scheduled date for a point in the future, say two days after date of publishing, and then published node, the node creator has no way of seeing a list of any and all scheduled nodes that s/he has created and which have not yet reached the scheduled date . Necessary of course in case they wish to further edit the node in the meantime. I would have thought it essential that they can view a list of their scheduled nodes. And because it seems such a basic requirement, I am thinking that I am missing something blatantly obvious (to all but me!).
Instruction would be greatly appreciated
Ed
Comments
Comment #1
ebyrne41 commentedComment #2
jonathan1055 commentedHi Ed,
You've got a good point there. If the user does not have authority to go to /admin/content/node then they can't see their unpublished nodes. It's amazing that no-one has mentioned this before. Maybe most people who are scheduling nodes have been granted 'administer nodes' permission. Also I've been using the Content Management Filter module http://drupal.org/project/cmf which allows users to see all their own nodes, including unpublished nodes, without granting them 'administer nodes' permission. I've found this module very useful (and it is my excuse for not spotting this little omission :-)
I think we should provide the ability for users to see their own unpublished nodes. Maybe a new tab in the 'my account' page, similar to the content we display in /content/node/scheduler but filtered just for the user's own.
Comment #3
eric-alexander schaefer commentedACK
Comment #4
ebyrne41 commentedThanks Jonathan for that. I have started using the Content Management Filter as prompted by you, and glad to report to does the necessary. Scheduled and unpublished posts now visible to user. Hopefully the module can be worked on to show a user all their nodes as you suggest.
Comment #5
eric-alexander schaefer commentedIt definately will, but we need the D7 version out first. Postponing as a reminder.
Comment #6
MacaroniDuck commentedsubscribe.
This is definitely needed as the CMF module allows a user to access the content list for ALL users. We need the ability for users to see only their own content.
Comment #7
jonathan1055 commentedHi MacaroniDuck,
There are two ways to use CMF and not all users have to get the full list. If you give them only the permission "view user content list" the they cannot get to the full admin page but they can get a filtered list in the 'my account' page showing only their own nodes.
But I agree that it will definitely need to be added as an enhancement to Scheduler. I was just pointing out that CMF can help users in the short term until we get it done.
Jonathan
Comment #8
MacaroniDuck commentedJonathan,
I'm utilizing Drupal Commons for a social networking site http://tuga.unpluggedgaming.org As such, users are given permission to "access user profiles" for the purposes of networking. This apparently also grants them access to view that person's CMF tab which then allows them to access all of their content. Since we are using Organic Groups, allowing people to form private groups, this is problematic since, if we implement CMF, a user can see another users private group within the CMF tab (i.e. not private any more). If you're aware of something I'm missing or some other way I can hide the CMF tab from them (barring employing PHP code), I'd greatly appreciate it as it would solve a huge headache for me!
Rob
Comment #9
jonathan1055 commentedYes, I see the problem. You are correct in that if a user has both 'access user profiles' and 'view user content list' permissions then they will be able to see the other users nodes.
I thought I would get down to making the proper scheduler solution, and a patch is attached, against the 6.x dev of 3rd March. I know that we'll need to do this in D7 first, but seeing as you are running D6 I thought you might like to try it.
Also attached are four screen shots:
Eric, if you think I am on the right lines to a solution here, I'll proceed to do a D7 version.
Comment #10
MacaroniDuck commentedWow, that was insanely fast. Had I known you'd be able to pull something together that quickly, I would have held off implementing something in Views that I found http://blog.urbaninsight.com/2010/09/custom-access-control-drupal-views
Still, when I get an opportunity I will apply your patch so you can get some feedback on. Many thanks!
Comment #11
jonathan1055 commentedYou're welcome. I knew it would not be too difficult, but didn't want it to interfere with our concentration on D7.
Can you leave the status as 'Needs Review' please? I want the other folks who work on Scheduler, especially Eric of course, to see that it is ready for looking at. Thanks
Comment #12
MacaroniDuck commentedOddness. I certainly didn't intend to change the status and don't even recall hovering my mouse over the area such that I might have hit it accidentally. Gremlins.
Comment #13
eric-alexander schaefer commentedLooks good (the patch). I like how you reused admin/content/node/scheduler. Very nice. Has anybody else tested it yet?
Comment #14
jonathan1055 commentedI've made one correction - when an admin user is viewing another users profile the scheduled tab should show that users scheduled items. The patch above always showed the current logged-in users content. This only has any effect for admin users or those with 'administer nodes' permission, because ordinary users do not even get the 'scheduled' tab when viewing other peoples profile pages.
Here are patches for D6 and D7. I'd understand if you do not want to commit this to D7 until after 1.0. But on the other hand, it is entirely separate from the inner workings of scheduler and so will not affect any processing or testing done so far.
Comment #15
eric-alexander schaefer commentedI want to put out 1.0 any minute now and I don't want it to be bananaware. There will be a 1.1 as soon as we get some of the other features rolling...
Comment #16
eric-alexander schaefer commentedWorks fine.
D7: http://drupalcode.org/project/scheduler.git/commit/607d950
D6: http://drupalcode.org/project/scheduler.git/commit/734d2d8