"Send for review" user error

[user@domain.invalid]

Contribute 3 Windows

A user was supposed to send an edited page for review via e-mail.
Instead, they sent it to their whole Contribute group. Unfortunately,
they are the only one in that group who still has Contribute.

Now she can't edit the page because the page is supposedly under review.

How do I as administrator get the page out of review and allow her to
send it for review the proper way?

Charles "Chas" Belov

[stockholmsyndrome]

This might help you out its taken from this DevNet article
[url]http://www.adobe.com/devnet/contribute/articles/rd_app_collab.html[/url]

Understanding the Approval Workflow in Contribute

Contribute 3 uses the following folders to manage the approvals workflow:

* _mm/Ct2004/messaging/users contains a folder for each Contribute user
for whom the administrator has enabled approval permission. Each user's folder
is populated with a series of XML files that identify which drafts the user has
within the system.
* WIPMetaData contains a series of files that maintain the draft history
and the current location of the draft within the approval system (WIP stands
for work in progress).
* _notes stores draft information such as the draft status, submitter's
name and e-mail address, and the date the file was last published, if relevant.
* MMWIP: For each file in the approval system, Contribute generates a
random folder name (such as 05bc0cac08b41e55) and a random filename (such as
92874f9967a24cdd.htm), which represent the draft document as it passes through
the approval system.

When a reviewer views a documet, Contribute creates a LCK (lock) file for the
page within the website folder structure and a CHK file in the WIPMetaData
folder. These files indicate that the file is in use by the recipient and
tracks changes made to the file.

Once the draft is finally published on the website, the random folder and file
used to track it is removed from the MMWIP root folder.

[user@domain.invalid]

stockholmsyndrome wrote:

> This might help you out its taken from this DevNet article
> [url]http://www.adobe.com/devnet/contribute/articles/rd_app_collab.html[/url]
>
> Understanding the Approval Workflow in Contribute
>
> Contribute 3 uses the following folders to manage the approvals workflow:
>
> * _mm/Ct2004/messaging/users contains a folder for each Contribute user
> for whom the administrator has enabled approval permission. Each user's folder
> is populated with a series of XML files that identify which drafts the user has
> within the system.
> * WIPMetaData contains a series of files that maintain the draft history
> and the current location of the draft within the approval system (WIP stands
> for work in progress).
> * _notes stores draft information such as the draft status, submitter's
> name and e-mail address, and the date the file was last published, if relevant.
> * MMWIP: For each file in the approval system, Contribute generates a
> random folder name (such as 05bc0cac08b41e55) and a random filename (such as
> 92874f9967a24cdd.htm), which represent the draft document as it passes through
> the approval system.
>
> When a reviewer views a documet, Contribute creates a LCK (lock) file for the
> page within the website folder structure and a CHK file in the WIPMetaData
> folder. These files indicate that the file is in use by the recipient and
> tracks changes made to the file.
>
> Once the draft is finally published on the website, the random folder and file
> used to track it is removed from the MMWIP root folder.
>

Thanks,
That was helpful.
I was able to come up with a fix from that info.
Charles "Chas" Belov

[user@domain.invalid]

[email]user@domain.inva[/email]lid wrote:

> stockholmsyndrome wrote:

> Thanks,
> That was helpful.
> I was able to come up with a fix from that info.

Just in case anyone else runs up against this.

I removed the LCK file, removed the various temp files, then edited and
published the page as a different user. That cleared things up,
although they lost their (fortunately small) amount of work.

If they needed to save the work, I would get it from their local files.

Charles "Chas" Belov