I have certain roles that don't need access to "My workspace". They have access to submit one piece of content which they cannot edit after they submit it. So it shows up, and is silly for them. I made a patch.

CommentFileSizeAuthor
#4 workspace.module.dev_.patch10.83 KBhutch
#1 workspace.module.patch934 byteskenorb
workspace.module_access_own_workspace_perm.patch933 bytespearcec

Comments

kenorb’s picture

kenorb commented
StatusFileSize
new workspace.module.patch934 bytes

My version of patch for 6.x
You will be able to choose if user can access workspace or not.

UPDATE: The name of permission should be 'access own workspace', but whatever.

pdcarto’s picture

pdcarto commented

The 6.x patch works for me. It's been almost 20 weeks since it was posted. Is it time to role it into the release?

kenorb’s picture

kenorb commented
Status: Needs review » Reviewed & tested by the community
hutch’s picture

hutch commented
StatusFileSize
new workspace.module.dev_.patch10.83 KB

Here is a patch that collects the patch at the top of this thread, D6 version with a few other issues I ran across. It is on workspace-6.x-1.x-dev and has been in use on my server for awhile now.
Wether the maintainer of this module is still active I do not know.

frank ralf’s picture

frank ralf commented

Well, I think that the maintainer of this module is very well active: http://drupal.org/user/2375/track

But he might have been busy writing http://www.drupalbook.com ...

Seriously, I also think that there are quite some patches lying around that should be committed. What about registering yourself as a co-maintainer (http://drupal.org/node/59)?

Cheers,
Frank

jvandyk’s picture

jvandyk commented

Comaintainer(s) are welcome! :)

hutch’s picture

hutch commented

I am up for it! I already have a CVS account for the two modules I maintain so that's not a problem.
I have read and inwardly digested the comments at http://drupal.org/node/363367 "Best practices for co-maintaining projects", all very sensible.

Let me know what you think.

frank ralf’s picture

frank ralf commented

Hi Bob,

I have also applied for the job :-) Thanks for the link, I didn't know that. It's very helpful. Setting up a release coordination issue as described there (and can be seen on http://drupal.org/node/305468) might be useful.

Cheers,
Frank

hutch’s picture

hutch commented

I like the 'release coordination issue' concept, better than trawling for patches ;-)

I would like to see a fresh dev release though, so more people can test. The person who codes is *not* the best person to test, the coder 'knows too much'. Having said that I'm using the version in my latest patch in production, no problems so far.

frank ralf’s picture

frank ralf commented

I did it: http://drupal.org/node/441532

Frank

frank ralf’s picture

frank ralf commented
Assigned: pearcec » frank ralf
Status: Reviewed & tested by the community » Fixed

Patch applied to HEAD, see #441532: 6.x-1.x-dev.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.