Hi all-
I don't see workflow.module in the main module list, and the specific project page only shows a 4.5.x release. I see in CVS one recent change was made, but I'm not sure if this is related to 4.6.x compat or what.
So basically my question is, how would/do I find out the status of this? Just install the CVS version and see if it works? I searched the site and didn't get any clear answers on current status (and the site's getting hammered or something, it's real slow)... am I missing something obvious or has workflow quietly slipped away to plan for bigger and later versions?
Would pulling the 4.5.x version and following the 'upgrading your moduless' steps at http://drupal.org/node/12347 be sensible?
I'm surprised the basic ability for posts to have draft/published status isn't a huge issue for many people - even Movable Type has had this for years! That's all I'm needing at this point; fancy triggers and actions would be nice someday, but the basics would suffice.
thanks for any help...
Would pulling the 4.5.x version and following the 'upgrading your moduless' steps at http://drupal.org/node/12347 be sensible?
That should be a good way to deal with it, it will teach you some drupal internals ;) looking at CVS : http://cvs.drupal.org/viewcvs/drupal/contributions/modules/workflow/ I saw that last version is 8 days old, so I don't know why a 4.6.x version hasn't been released. I guess that's because the maintainer ( John VanDyk ) is pretty busy working at the CCK (I can't stand the wait... see http://drupal.org/cck-status)
I'm surprised the basic ability for posts to have draft/published status isn't a huge issue for many people - even Movable Type has had this for years! That's all I'm needing at this point; fancy triggers and actions would be nice someday, but the basics would suffice.
I'm not sure you understood the objective of workflow module, it's not to provide draft/published status for node, this exists for a long time, the purpose was to provide a way to change the node status using the action module.
So check your drupal install, when you create a node, (if you get the right permissions of course), you can set it's status to published, promoted to front....
Regards
Nicolas
* Nicolas Tostin [2005-08-15 18:33]:
I'm not sure you understood the objective of workflow module, it's not to provide draft/published status for node, this exists for a long time, the purpose was to provide a way to change the node status using the action module.
So check your drupal install, when you create a node, (if you get the right permissions of course), you can set it's status to published, promoted to front....
Right, but in my case I have authors who need to be able to publish their own work - which as far as I can tell, only happens when I set the default to "Published" for the appropriate content types, since authors don't see the "Admin Options" that include "Publish" unless I give them free reign over the site ("administer nodes").
So if I set the default to be not published ("Published" unchecked), then they're kind of saving a draft, but can't publish it...
And if I'm wrong and this is possible with the current setup I have, it's *way* too complicated.
Thanks again for any help.
Right, but in my case I have authors who need to be able to publish their own work - which as far as I can tell, only happens when I set the default to "Published" for the appropriate content types, since authors don't see the "Admin Options" that include "Publish" unless I give them free reign over the site ("administer nodes").
Yes currently this is not possible and I fear that the workflow module can't allow it to you. I don't know why this hasn't been made up to now, but I'm sure there's a lot of demand, so maybe you can investigate a little node module and if you feel confortable, submit patches to allow this kind of permissions.
That's something I wanted for a long time (http://drupal.org/node/13129), but I never took the time to investigate it. My idea was to add some permissions as do flexinode : - per role - per node type - per vocabulary - per status (only authorized a role to pass a node from unpublished to published, then other get the right to promote to fron page...) - create others kind of status node (first draft, work copy... whatever ;) )
Well, now that I know better the Drupal internals, that seems not so difficult, but I didn't take the time to investigate the UI, and with so much permission, it can be pretty tricky.
Good luck for your investigation, feel free to contact me, and I hope you can get it.
Regards
Nicolas
* Nicolas Tostin [2005-08-16 17:17]:
Yes currently this is not possible and I fear that the workflow module can't allow it to you. I don't know why this hasn't been made up to now, but I'm sure there's a lot of demand, so maybe you can investigate a little node module and if you feel confortable, submit patches to allow this kind of permissions.
Well long ago I hacked it in, but made a HUGE mess as I didn't really know the drupal internals at all, which left me unable to upgrade that site, and/or put those changes into a new clean install. But I got this functionality! ;-)
I'm a bit more familiar now, so hopefully I can do it cleaner. Of course I need this *now*, but I'll try to figure out what's involved and do it cleanly.
I do suspect building on or with workflow is the way to go though - but maybe in my hurry a more basic "status only" module would be the way to go.
thanks again
Hi,
if this is not already posted as an issue, it might be a good idea to submit it as such.
Also, perhaps the discussion should at this point be moved to the drupal-devel list (since we're talking about possible ways to improve code :)
Best regards, Djun
On 16 Aug 2005, at 2:28 PM, Todd Grimason wrote:
- Nicolas Tostin [2005-08-16 17:17]:
Yes currently this is not possible and I fear that the workflow module can't allow it to you. I don't know why this hasn't been made up to now, but I'm sure there's a lot of demand, so maybe you can investigate a little node module and if you feel confortable, submit patches to allow this kind of permissions.
Well long ago I hacked it in, but made a HUGE mess as I didn't really know the drupal internals at all, which left me unable to upgrade that site, and/or put those changes into a new clean install. But I got this functionality! ;-)
I'm a bit more familiar now, so hopefully I can do it cleaner. Of course I need this *now*, but I'll try to figure out what's involved and do it cleanly.
I do suspect building on or with workflow is the way to go though - but maybe in my hurry a more basic "status only" module would be the way to go.
thanks again
--
toddgrimason*todd[ at ]slack.net
-- [ Drupal support list | http://lists.drupal.org/ ]
* puregin [2005-08-16 17:59]:
Hi,
if this is not already posted as an issue, it might be agood idea to submit it as such.
Also, perhaps the discussion should at this pointbe moved to the drupal-devel list (since we're talking about possible ways to improve code :)
Is it an issue though? John (who did/does most of workflow.module) told me there's currently no 4.6.x release of it because of problems with revisions, which I believe are undergoing significant changes. So I think it's a known issue.
As for improving or changing code... I've not yet looked at "how things are now" to suggest any possible changes. I just know what I need (yesterday) ;-) Perhaps after I spend some time with it i can propose something on drupal-devel, but at this point I'll just say something ignorant... (doesn't always stop me!)
-
Nicolas Tostin -
puregin -
Todd Grimason