[MGNLDMS-132] Dms query paragraph dialog is overridden by sitedesigner dialog of the same name Created: 13/Aug/08  Updated: 03/Jul/14  Resolved: 28/Jan/09

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.2.5
Fix Version/s: 1.3

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-2597 Provide a QueryTask - to operate on n... Closed
depends upon MAGNOLIA-2359 Prevent dialog, paragraph and templat... Closed
duplicate
is duplicated by MGNLDMS-136 Magnolia Samples - DocumentList Parag... Closed
is duplicated by MGNLDMS-149 sample document p broken Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

If you bootstrap the samples, website.help.xml for example, you get the "openwfe" page, listing documents from the dms. This works until one edits the dialog, at which point the link property's original value ("/openwfe") gets substituted by its uuid.
Since dms.jsp tries to get this node using Content node = MgnlContext.getHierarchyManager("dms").getContent(link);, it stops working as soon as the property becomes a uuid.

Furthermore, the query then does SELECT * FROM nt:base WHERE jcr:path like 'ad2e97ab-bca5-4681-bb00-f6151e7e5803/%' and extension = 'pdf' which also obviously returns no results.



 Comments   
Comment by Magnolia International [ 13/Aug/08 ]

Hmm - somehow this happened on demoAuthor, but I can't reproduce it on my machine: here the link property does not get substituted !?

Comment by Jan Haderka [ 02/Sep/08 ]

I managed to reproduce this on fresh installation. Once I delete paragraph and create it again, I'm not able to reproduce it any more.

Comment by Jan Haderka [ 02/Sep/08 ]

Indicates most likely problem with the samples rather then with the control itself.

Comment by Jan Haderka [ 05/Sep/08 ]

The cause of the issue is the fact that that both dms and sitedesigner define dialog called dmsParagraph and while DMS-dmsParagraph defines "link" to use link control, SD-dmsParagraph defines "link" property to use uuidLink control. Do we rename paragraph in DMS or in SD to solve this?
Also perhaps we should issue a warning when there are multiple dialogs or paragraphs of same name ...

Comment by Magnolia International [ 10/Sep/08 ]

Right. Created MAGNOLIA-2359 for this. Leaving this open until we implement a solution so that others running into the issue can understand it as well.

Comment by Magnolia International [ 28/Jan/09 ]

Dialog renamed from dmsParagraph to dmsQuery, update tasks take care of the renaming, and warn in case of usage (since usage might be related to Sitedesigner, we can't just go and change the property)

Fixed for 1.3 (trunk) and 1.2.7 (branch).
Updating to DMS 1.2.7 will require magnolia-core-3.6.4

Generated at Mon Feb 12 00:48:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.