tag:help-archives.hannonhill.com,2010-02-09:/discussions/bug-reports/2689-error-in-page-submission-and-approval-processCascade CMS: Discussion 2015-08-25T20:04:09Ztag:help-archives.hannonhill.com,2010-02-09:Comment/376644442015-08-17T11:41:42Z2015-08-17T11:41:42ZError in page submission and approval process<div><p>Hi Joel,</p>
<p>Unfortunately, I am not seeing any errors within the log file
you attached; however, this behavior does sound familiar.</p>
<p>What I believe you are seeing is due to a situation in which
somehow a draft was entered into a workflow and each time the
workflow was canceled the draft became a duplicated asset in the
system.</p>
<p>I believe that removing the drafts of the person who created the
duplicate asset (ie the person in your admin group) should help fix
this issue. When you have a moment, please do the following:</p>
<ul>
<li>Record the most recent changes made to the duplicated page,
because they will be lost when the draft is removed</li>
<li>Log into Cascade Server as this person (or have them log in);
or use the login as user feature if you are running 7.14+</li>
<li>Discard all the user's drafts (at least for this specific
page)</li>
<li>Log into Cascade Server as another user, such as yourself, and
update the correct pages with the most recent content</li>
</ul>
<p>Please let us know if you continue to experience issues after
removing the draft, or if you have any additional questions.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/376644442015-08-17T13:46:15Z2015-08-17T13:46:15ZError in page submission and approval process<div><p>That seems to have fixed it. I had the user that submitted the
workflow delete her drafts associated with this page and when she
deleted one, the other disappeared, too.</p>
<p>I had her redo the changes and resubmit the page and all seems
well now.</p></div>Joel Traugertag:help-archives.hannonhill.com,2010-02-09:Comment/376644442015-08-17T14:04:00Z2015-08-17T14:04:00ZError in page submission and approval process<div><p>Thank you for following up, Joel, I am glad to hear clearing the
drafts did the trick.</p>
<p>I was able to locate a few older discussions that mentioned this
behavior and I did notice we logged some potential improvements
internally to help avoid this situation in the future.
Unfortunately, the majority of these discussions ended with
monitoring things to see if the issue occurred again and no
specific steps to reproduce were identified.</p>
<p>That being said, let's continue monitoring things over the nest
week and, if you encounter this issue again, try to gather some
steps to reproduce the behavior so we can try to narrow things down
a bit.</p>
<p>I will make a note to follow up next week, but please let me
know if you run into the issue again or have any questions in the
meantime.</p>
<p>Thanks!</p></div>Ryan Griffith