| Summary: | Content duplicity check in "Multiple content selector" doesn't work properly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Tomas Kyjovsky <tkyjovsk> | ||||
| Component: | Site Publisher | Assignee: | Default User <jbpapp-maint> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.1.0.ER04 | CC: | epp-bugs, tkyjovsk | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.1.1.CR01 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-645 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
wcm 2.1.2-SNAPSHOT Nov-17
ecmdemo app
|
|||||
| Last Closed: | 2011-08-08 18:10:52 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Attachment: Added: one-item-selected-3-times.png Link: Added: This issue Cloned from JBQA-3980 Link: Removed: This issue Cloned from JBQA-3980 Link: Added: This issue is related to JBQA-3980 Related support issue: https://jira.exoplatform.org/browse/SPREDHAT-33 This issue is resolved in eXo https://jira.exoplatform.org/browse/ECMS-1939. Marking the Release Notes as "Not Yet Documented" pending the resolution of this JIRA. Release Notes Docs Status: Added: Not Yet Documented Release Notes Text: Added: A bug in the Content Duplicity Check in the multiple content selector has been corrected. The content selector now matches the target path of each selected node against those already selected and, if if a duplicate is found a warning is presented and the new node is rejected. This prevents users from selecting the same file more than once. Setting Release Note Ststus as Needs Info until JIRA is resolved. Release Notes Docs Status: Removed: Not Yet Documented Added: Needs More Info Release Notes Text: Removed: A bug in the Content Duplicity Check in the multiple content selector has been corrected. The content selector now matches the target path of each selected node against those already selected and, if if a duplicate is found a warning is presented and the new node is rejected. This prevents users from selecting the same file more than once. Added: A bug in the Content Duplicity Check in the multiple content selector has been corrected. The content selector now matches the target path of each selected node against those already selected and, if a duplicate is found a warning is presented and the new node is rejected. This prevents users from selecting the same file more than once. Release Notes Docs Status: Removed: Needs More Info Added: Documented as Resolved Issue |
project_key: JBEPP It is possible to select one content item more than once when 1) it is categorized in more categories 2) selecting the item once in a categorized drive ("acme", "classic" or "Events") and once in the "Managed sites" drive. In general this applies to situations when an item has more than one "path" in JCR repository.