<!-- 
RSS generated by JIRA (9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b) at Mon Feb 12 01:48:33 CET 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Magnolia - Issue tracker</title>
    <link>https://jira.magnolia-cms.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-uk</language>    <build-info>
        <version>9.4.2</version>
        <build-number>940002</build-number>
        <build-date>19-01-2023</build-date>
    </build-info>


<item>
            <title>[MGNLETK-109] fckEditor: repository browser doesn&apos;t expand to linked node if working on multiple sites from one base domain</title>
                <link>https://jira.magnolia-cms.com/browse/MGNLETK-109</link>
                <project id="10290" key="MGNLETK">Extended Templating Kit (closed)</project>
                    <description>&lt;p&gt;The problem is, that the links don&apos;t get expanded if you request Magnolia via a domain which is not mapped to a sitedefinition.&lt;/p&gt;


&lt;p&gt;To reproduce, follow these steps:&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Case 1&lt;/b&gt;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Visit &lt;a href=&quot;http://demoauthor45.magnolia-cms.com/.magnolia/pages/adminCentral.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://demoauthor45.magnolia-cms.com/.magnolia/pages/adminCentral.html&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;Verify that in the site definition of demo-project the domain mapping does not equal &quot;demoauthor45.magnolia-cms.com&quot;&lt;/li&gt;
	&lt;li&gt;On the page /demo-project/about/subsection-articles/article edit a TextImage component and create an internal link to a page of the demo-project&lt;/li&gt;
	&lt;li&gt;Click OK and save the dialog&lt;/li&gt;
	&lt;li&gt;Reopen the dialog and edit the previously created link (notice that the prefixHandle got cut out)&lt;/li&gt;
	&lt;li&gt;Click on &quot;Browse Server&quot;&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Result: The tree is not expanded&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Case 2&lt;/b&gt;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Now verify that in the site definition of demo-project the domain mapping &quot;demoauthor45.magnolia-cms.com&quot; exists!&lt;/li&gt;
	&lt;li&gt;Reopen the dialog, edit the link and click on &quot;Browse Server&quot;&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Result: The tree is expanded, but only if you link to pages of the current website (crossdomain links don&apos;t expand the tree)&lt;/p&gt;

&lt;p&gt;Can&apos;t we just always save the link as absolute URIs without cutting out the handlePrefix like it is done when you select a document from dms instead of a page from website tree?&lt;/p&gt;

&lt;p&gt;Chris&lt;/p&gt;</description>
                <environment></environment>
        <key id="33947">MGNLETK-109</key>
            <summary>fckEditor: repository browser doesn&apos;t expand to linked node if working on multiple sites from one base domain</summary>
                <type id="1" iconUrl="https://jira.magnolia-cms.com/secure/viewavatar?size=xsmall&amp;avatarId=10883&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.magnolia-cms.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="6" iconUrl="https://jira.magnolia-cms.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="chunhua.liu">Chunhua Liu</assignee>
                                    <reporter username="cbalaguer">Christian Balaguer</reporter>
                        <labels>
                    </labels>
                <created>Thu, 24 Oct 2013 13:53:16 +0200</created>
                <updated>Wed, 27 Nov 2013 10:19:22 +0100</updated>
                            <resolved>Tue, 26 Nov 2013 13:31:26 +0100</resolved>
                                                    <fixVersion>2.0.15</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="72421" author="cbalaguer" created="Thu, 24 Oct 2013 13:55:31 +0200"  >&lt;p&gt;This ticket is related to the following tickets:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://jira.magnolia-cms.com/browse/MAGNOLIA-5250&quot; title=&quot;fckEditor: make repository browser site aware&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MAGNOLIA-5250&quot;&gt;&lt;del&gt;MAGNOLIA-5250&lt;/del&gt;&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;SUPPORT-2652&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="72845" author="had" created="Thu, 31 Oct 2013 13:17:06 +0100"  >&lt;p&gt;I&apos;m not sure it is correct to switch off the use of uri mappings. Did you try what happens with binary or page resources when referenced in the editor itself? I believe they have incorrect links now when you create links to own site content.&lt;/p&gt;

&lt;p&gt;Also for the test - please rather then &quot;extending&quot; existing test method, add new test method to make it easier to see the failures in the future. Right now if first test in the method fails, it would prevent other part from being executed thus hiding the test itself.&lt;/p&gt;</comment>
                            <comment id="73038" author="czimmermann" created="Fri, 1 Nov 2013 10:49:54 +0100"  >&lt;p&gt;Here is some reference: &lt;a href=&quot;http://documentation.magnolia-cms.com/display/DOCS/URI+mapping&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://documentation.magnolia-cms.com/display/DOCS/URI+mapping&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="73041" author="had" created="Fri, 1 Nov 2013 10:57:43 +0100"  >&lt;p&gt;and some more to the story:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;originally link editor transformer (LET) was not site aware. That was fixed (see linked ticket).
	&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
		&lt;li&gt;by site-aware I mean that it was not shortening URIs for links to the same site.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;once LET was site aware, issue arose with repository browser which could no longer open shortened path
	&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
		&lt;li&gt;this was fixed in another ticket (see linked ticket)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;this resulted in broken display of images (or content of other workspaces that were not working with site-mapping/url-shortening
	&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
		&lt;li&gt;again this was fixed in one of the linked tickets&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;and the current situation is that we have cross site links that are correctly generated, but repository browser is not able to resolve such links to full path and reopen the tree pointing to the correct content.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;That being said I think that issue needs to be fixed in Repository browser if possible to minimise space for any negative side effects.&lt;/p&gt;

&lt;p&gt;possible test cases:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;content in SiteA has a link to another page in SiteA ==&amp;gt; generated URI needs to be shortened. When reopening repo browser, right page needs to be selected.&lt;/li&gt;
	&lt;li&gt;content in SiteA has a link to DMS/Data binary ==&amp;gt; generated URI is correct and not shortened. When reopening repo browser, right binary needs to be selected.&lt;/li&gt;
	&lt;li&gt;content in SiteA has a link to uploaded binary ==&amp;gt; generated URI is correct and shortened. No repo browser.&lt;/li&gt;
	&lt;li&gt;content in SiteA has a link to content in SiteB ==&amp;gt; generated URI is correct and NOT shortened. When reopening repo browser, right page needs to be selected. (this is actually the use case described in this ticket itself)&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="73704" author="cheng.hu" created="Thu, 14 Nov 2013 06:13:55 +0100"  >&lt;p&gt;Moved from &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MAGNOLIA-5417&lt;/del&gt;&lt;/a&gt; to &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MGNLETK-107&lt;/del&gt;&lt;/a&gt; because fix is in ETK module. Previous commits are logged to &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MAGNOLIA-5417&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="73705" author="cheng.hu" created="Thu, 14 Nov 2013 06:52:58 +0100"  >&lt;p&gt;In Magnolia 5, the functionality no longer exists to jump to the tree location pointed to by a link in the editor when editing the link (&lt;em&gt;perhaps this is an oversight?&lt;/em&gt;). For example, in a &lt;em&gt;Text &amp;amp; Image&lt;/em&gt; component, create a link to a page in the tree using the &lt;em&gt;Link to Magnolia Page&lt;/em&gt; button. Open the link again using the &lt;em&gt;Link to Magnolia Page&lt;/em&gt; button. Regardless of whether domains are set correctly, the dialog does not jump to the page linked to in the tree.&lt;/p&gt;

&lt;p&gt;As a result, this bug is no longer reproducible on Magnolia 5.&lt;/p&gt;

&lt;p&gt;However, we have ported the changes from 2.0.15 to 2.x anyway because we believe it makes the logic of calculating an URI from a link more correct and also so that the logic for doing so is uniform between 4.5 and 5. &lt;/p&gt;</comment>
                            <comment id="73707" author="cheng.hu" created="Thu, 14 Nov 2013 07:59:50 +0100"  >&lt;p&gt;We changed the logic to calculate an URI from a link into the &lt;tt&gt;website&lt;/tt&gt; workspace in &lt;b&gt;&lt;tt&gt;ETKURI2RepositoryManager.getURI(Link uuidLink)&lt;/tt&gt;&lt;/b&gt;.&lt;/p&gt;

&lt;p&gt;Previously, the URI for all links are generated using the mappings defined in the site definition.&lt;/p&gt;

&lt;p&gt;After the change, if the link is to the &lt;tt&gt;website&lt;/tt&gt; workspace and the URI of the request context &lt;em&gt;does not&lt;/em&gt; match any of the domains listed in the site definition, then mappings defined in the site definition &lt;em&gt;are not&lt;/em&gt; applied. For links into any other workspace, and for links into the &lt;tt&gt;website&lt;/tt&gt; workspace where the request context &lt;em&gt;does&lt;/em&gt; match some domain listed in the site definition, mappings defined in the site definition &lt;em&gt;are&lt;/em&gt; applied just as before.&lt;/p&gt;</comment>
                            <comment id="73722" author="cheng.hu" created="Thu, 14 Nov 2013 10:42:15 +0100"  >&lt;p&gt;There is an issue caused by the fix above that we are aware of but think it is an issue with the existing code rather than our code.&lt;/p&gt;


&lt;p&gt;&lt;b&gt;How to reproduce the issue:&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;This assumes testing on the ee-bundle running in Eclipse with our code on localhost. The URI used to access demo-project is &lt;a href=&quot;http://localhost:8080/magnolia-enterprise-webapp/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8080/magnolia-enterprise-webapp/&lt;/a&gt;. &lt;/p&gt;

&lt;p&gt;In the &lt;em&gt;site definition&lt;/em&gt; for demo project, in /demo-project/domains/demo-project/, add the following properties and values:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;name = localhost&lt;/li&gt;
	&lt;li&gt;port = 9999&lt;/li&gt;
	&lt;li&gt;protocol = http&lt;/li&gt;
	&lt;li&gt;context = /magnolia-enterprise-webapp&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Note that the &lt;em&gt;port&lt;/em&gt; is &lt;em&gt;incorrect&lt;/em&gt;. Open the &lt;em&gt;about&lt;/em&gt; page at &lt;a href=&quot;http://localhost:8080/magnolia-enterprise-webapp/about.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8080/magnolia-enterprise-webapp/about.html&lt;/a&gt;, see that it &lt;em&gt;does not&lt;/em&gt; display correctly.&lt;/p&gt;

&lt;p&gt;Now change the domain definition by changing the &lt;em&gt;name&lt;/em&gt; property while keeping other properties the same:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;name = xyz&lt;/li&gt;
	&lt;li&gt;port = 9999&lt;/li&gt;
	&lt;li&gt;protocol = http&lt;/li&gt;
	&lt;li&gt;context = /magnolia-enterprise-webapp&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Open the &lt;em&gt;about&lt;/em&gt; page at &lt;a href=&quot;http://localhost:8080/magnolia-enterprise-webapp/about.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8080/magnolia-enterprise-webapp/about.html&lt;/a&gt;, see that it &lt;em&gt;does&lt;/em&gt; display correctly.&lt;/p&gt;


&lt;p&gt;&lt;b&gt;Reasoning for why this is a problem in the existing code:&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;In both cases above, our code correctly decides that the domain definition does not match the request context, and returns the &lt;em&gt;same&lt;/em&gt; URI from a link. That is, in both cases, our code returns the same thing.&lt;/p&gt;

&lt;p&gt;This means that changing the &lt;em&gt;name&lt;/em&gt; property causes some change in the existing code that causes the different results. However, simply changing the &lt;em&gt;name&lt;/em&gt; property should have no effect, because the &lt;em&gt;port&lt;/em&gt; property is always wrong and the domain definition should never affect anything in either case.&lt;/p&gt;


&lt;p&gt;&lt;b&gt;Theory as to what is wrong&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;One theory is that somewhere in the existing code, there is also a decision being made as to whether a domain definition applies to the current request context. However, that is only checking whether the &lt;em&gt;name&lt;/em&gt; matches, but does not check any of the other properties such as &lt;em&gt;port&lt;/em&gt; or &lt;em&gt;context&lt;/em&gt; or &lt;em&gt;protocol&lt;/em&gt;.&lt;/p&gt;


&lt;p&gt;&lt;b&gt;Possible fixes&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;One fix is that we can make our code emulate the incorrect behavior and decide that a domain definition matches when just the &lt;em&gt;name&lt;/em&gt; property matches. We have tried this and find that it solves the above problem. However, it may not address the real problem.&lt;/p&gt;

&lt;p&gt;The other fix is to find the place in the current code that decides whether a domain definition applies but only checks the &lt;em&gt;name&lt;/em&gt; property, assuming the theory is correct, and change it to also check the other three properties.&lt;/p&gt;</comment>
                            <comment id="74133" author="had" created="Wed, 20 Nov 2013 16:17:54 +0100"  >&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;making changes in &lt;tt&gt;ETKURI2RepositoryManager&lt;/tt&gt; is a change that will impact other parts of Magnolia. I think it is too far reaching for fixing this issue. Fix needs to happen much closer to the problem.&lt;/li&gt;
	&lt;li&gt;the domain checking in the code on branch can be simplified, rather then taking again domain, port and all other info, you should rely on &lt;tt&gt;site = ((ExtendedAggregationState) MgnlContext.getAggregationState()).getSite();&lt;/tt&gt; to give you already resolved site using whatever rules are set in &lt;tt&gt;SiteMappingFilter&lt;/tt&gt; so that the resolution is consistent. And last but not least. Imho the problem in editor is that the &quot;current&quot; request is to the editor (hence always pointing to the default site), while the mapping needs to be resolved between page that is being edited and target of the links. It&apos;s the fact that those 2 belong to different site that causes problems. It would seem to me that we check based on edited page (source of the link) which site we are on, rather then based on the target.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;All things said I would think fix should be located in custom RepoBrowserPage or in EditorLinkTransformer.&lt;/p&gt;</comment>
                            <comment id="74241" author="cheng.hu" created="Fri, 22 Nov 2013 14:16:06 +0100"  >&lt;p&gt;Moved from &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MGNLETK-107&lt;/del&gt;&lt;/a&gt; to &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MAGNOLIA-5510&lt;/del&gt;&lt;/a&gt; because fix is in core module. Previous commits are logged to &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MAGNOLIA-5417&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MGNLETK-107&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="74317" author="had" created="Mon, 25 Nov 2013 14:10:02 +0100"  >&lt;p&gt;After sleeping on it for few days, I realised there is still at least one extra case that this fix doesn&apos;t handle and that&apos;s the situation when you configure micro site (i.e. sub site of given site that has same domain name, but uses different path mapping in &lt;tt&gt;&amp;lt;site name&amp;gt;/mappings/website/handlePrefix&lt;/tt&gt;. While you could probably extend the code to check not only domain names, but also mapping, it just shows how brittle is the fix and how it would break every time we adjust mechanism for site resolution. &lt;br/&gt;
That being said I would suggest following:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;leave &lt;tt&gt;EditorLinkTransformer&lt;/tt&gt; that is in the main project untouched.&lt;/li&gt;
	&lt;li&gt;create new &lt;tt&gt;STKEditorLinkTransformer&lt;/tt&gt; that would exist in STK or ETK so it would be able to use site manager for resolving correct site&lt;/li&gt;
	&lt;li&gt;configure this new transformer to be used as editor transformer in &lt;tt&gt;ETKLinkTransformerManager&lt;/tt&gt;/&lt;tt&gt;MultiSiteLinkTRansformerManager&lt;/tt&gt;  (It&apos;s configured under &lt;tt&gt;config:/server/rendering/linkManagement&lt;/tt&gt;)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;And fix needs to be applied on both 4.5.x and 5.2.x branches.&lt;/p&gt;

&lt;p&gt;Sorry for not realising this is the proper course of action earlier.&lt;/p&gt;</comment>
                            <comment id="74456" author="had" created="Tue, 26 Nov 2013 21:58:45 +0100"  >&lt;p&gt;Perfect and again sorry, for having to redo it multiple times.&lt;/p&gt;

&lt;p&gt;Just one tiny detail - since fix is now in ETK/Multisite, you should move &amp;amp; clone the issue to their respective projects instead of keeping it in main project.&lt;/p&gt;</comment>
                            <comment id="74464" author="cheng.hu" created="Wed, 27 Nov 2013 03:10:42 +0100"  >&lt;p&gt;Moved from &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MAGNOLIA-5510&lt;/del&gt;&lt;/a&gt; to &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MGNLETK-109&lt;/del&gt;&lt;/a&gt; because fix is in ETK module. Previous commits are logged to &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MAGNOLIA-5417&lt;/del&gt;&lt;/a&gt;, &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MGNLETK-107&lt;/del&gt;&lt;/a&gt;, and &lt;a href=&quot;https://jira.magnolia-cms.com/browse/MGNLETK-109&quot; title=&quot;fckEditor: repository browser doesn&amp;#39;t expand to linked node if working on multiple sites from one base domain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MGNLETK-109&quot;&gt;&lt;del&gt;MAGNOLIA-5510&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="74519" author="czimmermann" created="Wed, 27 Nov 2013 10:19:22 +0100"  >&lt;p&gt;QA passed on bundle.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10030">
                    <name>Cloners</name>
                                                                <inwardlinks description="is cloned by">
                                        <issuelink>
            <issuekey id="34806">MULTISITE-9</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10160">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="32660">MAGNOLIA-5250</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10010">
                    <name>relation</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="34721">MGNLUI-2450</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_14166" key="com.okapya.jira.checklist:checklist">
                        <customfieldname>Acceptance criteria</customfieldname>
                        <customfieldvalues>
                            
        <checklist>
        <![CDATA[
                            




                
                                    <div class="o-completion" style="display: flex; flex-shrink: 0;"><span  class="aui-lozenge aui-lozenge-complete" style="font-size: 12px; font-weight: normal; display: flex; flex-direction: row; align-items: center;" ><span style="padding-right: 4px; vertical-align: middle;"><svg width="15" height="15" viewBox="0 0 15 15" xmlns="http://www.w3.org/2000/svg" fill="white"><path clip-rule="evenodd" d="m10.41037,3.42544l-7.86501,0c-0.72395,0 -1.31084,0.58688 -1.31084,1.31084l0,7.86508c0,0.7239 0.58689,1.3108 1.31084,1.3108l7.86501,0c0.724,0 1.3109,-0.5869 1.3109,-1.3108l0,-7.86508c0,-0.72396 -0.5869,-1.31084 -1.3109,-1.31084zm-7.86501,-0.65542c-1.08593,0 -1.96626,0.88032 -1.96626,1.96626l0,7.86508c0,1.0859 0.88033,1.9662 1.96626,1.9662l7.86501,0c1.086,0 1.9663,-0.8803 1.9663,-1.9662l0,-7.86508c0,-1.08594 -0.8803,-1.96626 -1.9663,-1.96626l-7.86501,0z" fill-rule="evenodd"/><path d="m5.09049,10.18526l-1.82767,-1.82766l-0.78479,0.78479l2.61246,2.61246l5.38758,-5.38754l-0.78483,-0.78479l-4.60275,4.60274z"/></svg></span><span>Empty</span></span></div>
                        ]]>
    </checklist>


                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10111" key="com.atlassian.jira.toolkit:reporterdomain">
                        <customfieldname>Company</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>namics.com</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10031" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 31 Oct 2013 13:17:06 +0100</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_12730" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_14151" key="com.atlassian.jira.toolkit:message">
                        <customfieldname>Docu info</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10246" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>MAGNOLIA-5448</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10061" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comm is not jira-dev</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10071" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last participant</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>mmuehlebach</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_13136" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            10 years, 12 weeks, 4 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10020" key="com.atlassian.jira.toolkit:attachments">
                        <customfieldname>Number of attachments</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10150" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname>Number of comments</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>14.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10011" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>cheng.hu</customfieldvalue>
            <customfieldvalue>cbalaguer</customfieldvalue>
            <customfieldvalue>czimmermann</customfieldvalue>
            <customfieldvalue>chunhua.liu</customfieldvalue>
            <customfieldvalue>had</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10833" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i001h3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10244" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>247</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10245" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="23">4.5.14</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_14145" key="com.intenso.jira.issue-templates:issue-templates-customfield">
                        <customfieldname>Template</customfieldname>
                        <customfieldvalues>
                            


                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_15131" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Time in Discovery</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10032" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_10003" key="com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker">
                        <customfieldname>Visible to</customfieldname>
                        <customfieldvalues>
                                    <customfieldvalue><![CDATA[dkummer]]></customfieldvalue>
        <customfieldvalue><![CDATA[raphaeljoss]]></customfieldvalue>
        <customfieldvalue><![CDATA[sbaur]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>