Issue 1592 - Approval of documents not possible for project owner
Summary: Approval of documents not possible for project owner
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Upgrade (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: stx123
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks: 2177
  Show dependency tree
 
Reported: 2001-08-31 16:05 UTC by Martin Hollmichel
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2001-08-31 16:05:59 UTC 
a developer of a project suggests a new document. The project owner sees only 
that there is a pending approval, but he don't get an checkbox offered to do 
this (the domain admin sees this button to approve this).
Comment 1 Unknown 2001-09-05 18:09:42 UTC 
Accepting.
Comment 2 Unknown 2001-09-07 18:18:23 UTC 
I reproduced this. As tester, I joined project "metrics," added a 
new article. I then logged in as myself (owner of metrics), saw 
that an article was waiting there for me to approve. Clicked on 
the hyperlink, read the article, etc., but was unable to approve or 
disapprove of it. I could delete or edit it, but not simply approve or 
disapprove it, as there was no box available for this purpose.
louis
Comment 3 Unknown 2001-09-18 00:19:20 UTC 
This has been fixed in the latest  (non-QA'd) version of 
SourceCast. In the meantime, there is a workaround.

Documents suggested at the top level of the document tree 
cannot be approved - in fact, they can be viewed by anyone 
without approval of the doc.

However, if the project owner clicks on any document at any 
lower-level directory in the tree that is pending approval, he will 
get the full list of pending docs and the ability to approve them - 
including any top-level docs.

My suggestion is for project owners to create sub-directories for 
their projects and inform anyone who might suggest docs to 
place them in those sub-directories, which will enable owners to 
approve.

I am going to mark this RESOLVED LATER, as this will be 
improved with OOo's eventual upgrade to 1.2.
Comment 4 stx123 2001-11-06 19:25:55 UTC 
Implemented in 1.2 or in the upcoming 1.1?
Comment 5 stx123 2001-11-06 19:26:22 UTC 
reassigned
Comment 6 Unknown 2001-11-13 03:58:43 UTC 
I created a test project and made myself the owner. I then added my 
testuser self as a member.

I logged is as a 'content developer' and suggested a new document.

I logged back in as the project owner and was able to approve the 
document. I've left this open so you can validate on your side.
Comment 7 stx123 2001-11-14 16:38:18 UTC 
fixed
Comment 8 stx123 2001-11-14 16:38:53 UTC 
verified on staging box
Comment 9 Unknown 2001-11-15 02:16:01 UTC 
closing as fixed.