[jira] Created: (OFBIZ-1155) problem with 2 <content tags in a screen definition

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (OFBIZ-1155) problem with 2 <content tags in a screen definition

Nicolas Malin (Jira)
problem with 2 <content tags in a screen definition
---------------------------------------------------

                 Key: OFBIZ-1155
                 URL: https://issues.apache.org/jira/browse/OFBIZ-1155
             Project: OFBiz
          Issue Type: Bug
          Components: content
    Affects Versions: SVN trunk
            Reporter: Hans Bakker
             Fix For: SVN trunk


When we have the following screen definition:

<screen>
    <section>
        <actions>
               <set field="contentId" from-field="parameters.contentId"/>
        </actions>
        <widgets>
                <content content-id="adv-menu"/>
                <content content-id="${contentId}"/>
       </widgets>
    </section>
</screen>

then the second contentId will display the first time when not in the cache yet. If the content is in the cache it will not display anymore.

Attached patch solves this problem. It is tested with the ecommerce frontend display and with the cmssite special component.

This issue is to be sure that the attached patch is correct. Comments welcomed.

If no objections i will commit this patch in 3 days.


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (OFBIZ-1155) problem with 2 <content tags in a screen definition

Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Bakker updated OFBIZ-1155:
-------------------------------

    Attachment: modelscreenwidget.patch

fixes the problem

> problem with 2 <content tags in a screen definition
> ---------------------------------------------------
>
>                 Key: OFBIZ-1155
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1155
>             Project: OFBiz
>          Issue Type: Bug
>          Components: content
>    Affects Versions: SVN trunk
>            Reporter: Hans Bakker
>             Fix For: SVN trunk
>
>         Attachments: modelscreenwidget.patch
>
>
> When we have the following screen definition:
> <screen>
>     <section>
>         <actions>
>                <set field="contentId" from-field="parameters.contentId"/>
>         </actions>
>         <widgets>
>                 <content content-id="adv-menu"/>
>                 <content content-id="${contentId}"/>
>        </widgets>
>     </section>
> </screen>
> then the second contentId will display the first time when not in the cache yet. If the content is in the cache it will not display anymore.
> Attached patch solves this problem. It is tested with the ecommerce frontend display and with the cmssite special component.
> This issue is to be sure that the attached patch is correct. Comments welcomed.
> If no objections i will commit this patch in 3 days.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (OFBIZ-1155) problem with 2 <content tags in a screen definition

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Bakker updated OFBIZ-1155:
-------------------------------

    Component/s:     (was: content)
                 framework

> problem with 2 <content tags in a screen definition
> ---------------------------------------------------
>
>                 Key: OFBIZ-1155
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1155
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: SVN trunk
>            Reporter: Hans Bakker
>            Assignee: Hans Bakker
>             Fix For: SVN trunk
>
>         Attachments: modelscreenwidget.patch
>
>
> When we have the following screen definition:
> <screen>
>     <section>
>         <actions>
>                <set field="contentId" from-field="parameters.contentId"/>
>         </actions>
>         <widgets>
>                 <content content-id="adv-menu"/>
>                 <content content-id="${contentId}"/>
>        </widgets>
>     </section>
> </screen>
> then the second contentId will display the first time when not in the cache yet. If the content is in the cache it will not display anymore.
> Attached patch solves this problem. It is tested with the ecommerce frontend display and with the cmssite special component.
> This issue is to be sure that the attached patch is correct. Comments welcomed.
> If no objections i will commit this patch in 3 days.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (OFBIZ-1155) problem with 2 <content tags in a screen definition

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Bakker reassigned OFBIZ-1155:
----------------------------------

    Assignee: Hans Bakker

> problem with 2 <content tags in a screen definition
> ---------------------------------------------------
>
>                 Key: OFBIZ-1155
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1155
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: SVN trunk
>            Reporter: Hans Bakker
>            Assignee: Hans Bakker
>             Fix For: SVN trunk
>
>         Attachments: modelscreenwidget.patch
>
>
> When we have the following screen definition:
> <screen>
>     <section>
>         <actions>
>                <set field="contentId" from-field="parameters.contentId"/>
>         </actions>
>         <widgets>
>                 <content content-id="adv-menu"/>
>                 <content content-id="${contentId}"/>
>        </widgets>
>     </section>
> </screen>
> then the second contentId will display the first time when not in the cache yet. If the content is in the cache it will not display anymore.
> Attached patch solves this problem. It is tested with the ecommerce frontend display and with the cmssite special component.
> This issue is to be sure that the attached patch is correct. Comments welcomed.
> If no objections i will commit this patch in 3 days.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (OFBIZ-1155) problem with 2 <content tags in a screen definition

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Bakker closed OFBIZ-1155.
------------------------------

    Resolution: Fixed

attached patch implemented in rev: 557859

> problem with 2 <content tags in a screen definition
> ---------------------------------------------------
>
>                 Key: OFBIZ-1155
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1155
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: SVN trunk
>            Reporter: Hans Bakker
>            Assignee: Hans Bakker
>             Fix For: SVN trunk
>
>         Attachments: modelscreenwidget.patch
>
>
> When we have the following screen definition:
> <screen>
>     <section>
>         <actions>
>                <set field="contentId" from-field="parameters.contentId"/>
>         </actions>
>         <widgets>
>                 <content content-id="adv-menu"/>
>                 <content content-id="${contentId}"/>
>        </widgets>
>     </section>
> </screen>
> then the second contentId will display the first time when not in the cache yet. If the content is in the cache it will not display anymore.
> Attached patch solves this problem. It is tested with the ecommerce frontend display and with the cmssite special component.
> This issue is to be sure that the attached patch is correct. Comments welcomed.
> If no objections i will commit this patch in 3 days.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.