Bug 1007188 - Error message when setting tags on new content specs
Error message when setting tags on new content specs
Status: CLOSED CURRENTRELEASE
Product: PressGang CCMS
Classification: Community
Component: Web-UI (Show other bugs)
1.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 1.2
Assigned To: Lee Newson
mmurray
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-12 01:26 EDT by mmurray
Modified: 2013-11-07 21:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-07 21:10:44 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Error message window (13.20 KB, image/png)
2013-09-12 01:26 EDT, mmurray
no flags Details

  None (edit)
Description mmurray 2013-09-12 01:26:44 EDT
Created attachment 796620 [details]
Error message window

Description of problem:
When creating new content specs in the web-UI, get error message if don't save changes in stages and then have to start over.

Version-Release number of selected component (if applicable):
Build 201309081012

How reproducible:
100%

Steps to Reproduce:
1. Click 'create spec'
2. Paste spec in 'content spec' tab (don't save yet)
3. Click 'tags'
4. Pick writer and click 'add' (e.g., JBDS, Assigned Writer, mmurray)
5. Error message:
"Uncaught exception was detected. Redirecting you to the home page.
Exception: Exception caught: The displayed collection item to reference a valid entity and have a valid tags collection."

Work around:
At step 2, after pasting content spec text click save. Then add tags and save again.
Comment 1 Lee Newson 2013-09-12 03:08:53 EDT
Fixed in Build 201309121600.

This version is currently live on PressGang Next.
Comment 2 Lee Newson 2013-11-07 21:10:44 EST
This was released as part of 1.2.

Note You need to log in before you can comment on or make changes to this bug.