Home → Bug Reports →

Error in page submission and approval process

• Edit

Joel Trauger

14 Aug, 2015 09:36 PM

A user submitted a page for approval and it went into the workflow. One of the people in our administration group approved the page and now a second asset with a similar name has appeared in the folder. No one in the administration group, not even the site admin user account, can access that asset.

I'm attaching the log file as cascade (1).log.

The error occured around 4:20 PM CST

• cascade__1_.log 3.75 KB

1. 1 Posted by Ryan Griffith on 17 Aug, 2015 11:41 AM

   

   Hi Joel,

   Unfortunately, I am not seeing any errors within the log file you attached; however, this behavior does sound familiar.

   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.

   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:

   • Record the most recent changes made to the duplicated page, because they will be lost when the draft is removed
   • 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+
   • Discard all the user's drafts (at least for this specific page)
   • Log into Cascade Server as another user, such as yourself, and update the correct pages with the most recent content

   Please let us know if you continue to experience issues after removing the draft, or if you have any additional questions.

   Thanks!

   • Edit

2. 2 Posted by Joel Trauger on 17 Aug, 2015 01:46 PM

   

   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.

   I had her redo the changes and resubmit the page and all seems well now.

   • Edit

3. 3 Posted by Ryan Griffith on 17 Aug, 2015 02:04 PM

   

   Thank you for following up, Joel, I am glad to hear clearing the drafts did the trick.

   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.

   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.

   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.

   Thanks!

   • Edit

4. Ryan Griffith closed this discussion on 25 Aug, 2015 08:04 PM.