[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22753#action_22753
]
Philipp Bärfuss edited comment on MAGNOLIA-2741 at 5/25/09 4:59 PM:
--------------------------------------------------------------------
There should not be any difference. At least I am not aware of any. This is a
normal dialogs.
was (Author: pbaerfuss):
There should not be any difference. At least I am not aware of any. This
are common none sophisticated dialogs.
> Different behavior of uuidLink Control in STK and 'classic' templating
> ----------------------------------------------------------------------
>
> Key: MAGNOLIA-2741
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2741
> Project: Magnolia
> Issue Type: Bug
> Components: core
> Affects Versions: 4.1
> Environment: Mg 4.1, Tomcat 6, Windows XP, Firefox
> Reporter: Giancarlo Berner
> Assignee: Philipp Bärfuss
>
> There is a strange behavior with the uuidLink control and I am not sure if I
> am missing something here.
> If I use dialog
> /modules/standard-templating-kit/dialogs/paragraphs/links/stkInternalLink
> within the STK and I select a link, it stores the UUID of the link, which is
> actually what I expect. However, if I copy the dialog into the regular
> templating folder and use it with one of my own paragraphs, the dialog stores
> the PATH of the selected link.
> This leaves me with the impression that the dialog's SAVE might act different
> than the SAVE within the STK or there is something else I am missing (perhaps
> a property to select to store PATH or UUID).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
