[jira] [Created] (OFBIZ-9220) Employment Applications in Party manager does not list any record even if they exist.
Aditya Sharma created OFBIZ-9220: Summary: Employment Applications in Party manager does not list any record even if they exist. Key: OFBIZ-9220 URL: https://issues.apache.org/jira/browse/OFBIZ-9220 Project: OFBiz Issue Type: Bug Components: party Reporter: Aditya Sharma Assignee: Aditya Sharma Steps to reproduce: 1. Go to party manager. 2. Find party Company (or any party) and navigate to Employment Application tab. 3. Now create Employment Application from Add Employment Applications. It will show newly created Employment Application. 4. Navigate to Employment Application again list is not updated with newly created Employment Application (in fact it never has any Employment Application listed even it exists). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-7535) Broken page renders while click on Submit button
[ https://issues.apache.org/jira/browse/OFBIZ-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-7535: - Attachment: OFBIZ-7535.patch Problem: Submit button on ListEmploymentApps form has no check to hide when no record in List Solution: 1.ListEmploymentApps form list records by using PerformFind service. 2. PerformFind service returns listSize, used it on button for attribute use-when. Button is only visible when listSize>0. 3. EditApplicationApp screen directly included ListEmploymentApps form due to on empty list UI get disturbed so included that into a screenlet. > Broken page renders while click on Submit button > > > Key: OFBIZ-7535 > URL: https://issues.apache.org/jira/browse/OFBIZ-7535 > Project: OFBiz > Issue Type: Bug > Components: party >Reporter: Ankush Upadhyay >Assignee: Divesh Dutta >Priority: Minor > Attachments: OFBIZ-7535.patch > > > Steps to reproduce: > 1. Go to party manager. > 2. Find party Company and navigate to Employment Application tab. > 3. Now if there is no existing application and Submit button visible then > click on submit button. > 4. Broken page renders with error message " > :ERROR MESSAGE: > org.ofbiz.webapp.event.EventHandlerException: No rows to process" > Ideally system should hide submit button if there is no application to > process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-8457) Create new Return page required fields validations are not working correctly
[ https://issues.apache.org/jira/browse/OFBIZ-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-8457: - Attachment: OFBIZ-8457.patch Problem: 1. EditReturn form creates ReturnHeader with createReturnHeader service. 2. createReturnHeader service uses getPartyAccountingPreferences to get login user's preference to useInvoiceIdForReturns. 3. getPartyAccountingPreferences has partyIdTo as required fields. Solution: PartyIdTo field is made required. > Create new Return page required fields validations are not working correctly > > > Key: OFBIZ-8457 > URL: https://issues.apache.org/jira/browse/OFBIZ-8457 > Project: OFBiz > Issue Type: Bug > Components: order >Reporter: Sanjay Yadav >Assignee: Avnindra Sharma > Attachments: OFBIZ-8457.patch, ReturnOrderPageValidations.PNG > > > Steps to recreate: > 1. Go to Order Manager. > 2. go to Returns. Create new return page will open > 3. Do not fill any field and click on submit button. > Actual - Field validations messages are not working correctly. Please refer > attachment. > Expected - correct validation message should appear for all required fields. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-7759) Link in LookupContent causes unwanted behaviour
[ https://issues.apache.org/jira/browse/OFBIZ-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-7759: - Attachment: OFBIZ-7759.patch > Link in LookupContent causes unwanted behaviour > --- > > Key: OFBIZ-7759 > URL: https://issues.apache.org/jira/browse/OFBIZ-7759 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Aditya Sharma >Priority: Minor > Labels: content, locale, lookup > Attachments: OFBIZ-7759.patch > > > How to reproduce : > - Log in the Content component > - Go to the Content tab > - In the search form, open the lookup of the field ' Owner Content Id ' > - Click on the search button > - In the result list, click on a button link in the column 'Data Resource Id' > - The form to edit the Content will be displayed (a whole OFBiz seems to be > accessible from this new page) > - Close the lookup. > - Try to reopen it, it doesn't show anything anymore. > The only hint I've found for explaining this problem is that the request to > open the lookup is somehow changed. > At first it is : > https://localhost:8443/content/control/LookupContent > But then it becomes : > https://localhost:8443/content/control/LookupLocale > The other lookup seems unusable too after that. > Did you already encounter this kind of problem before ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-7759) Link in LookupContent causes unwanted behaviour
[ https://issues.apache.org/jira/browse/OFBIZ-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942622#comment-15942622 ] Aditya Sharma commented on OFBIZ-7759: -- Problem: 1. Lookup dialog for ownerContentId uses "ListLookupContent" form to list Content records. 2. "ListLookupContent" form extends "ListContent" form for all the fields. 3. As fields dataResourceId and ownerContentId are extended fields they creates a link to Edit pages. Solution: First of all it is a lookup to select ownerContentId so as the pattern followed in other lookups in OFBiz it should not have any links to Edit page. If links are removed there will not be the problem as well. Apart from that added 'widget-style="smallSubmit"' to contentId according to the uniform pattern followed. Link to edit ownerContentId shows contentId in description rather than ownerContentId in "ListLookupContent" form updated that too. > Link in LookupContent causes unwanted behaviour > --- > > Key: OFBIZ-7759 > URL: https://issues.apache.org/jira/browse/OFBIZ-7759 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Aditya Sharma >Priority: Minor > Labels: content, locale, lookup > Attachments: OFBIZ-7759.patch > > > How to reproduce : > - Log in the Content component > - Go to the Content tab > - In the search form, open the lookup of the field ' Owner Content Id ' > - Click on the search button > - In the result list, click on a button link in the column 'Data Resource Id' > - The form to edit the Content will be displayed (a whole OFBiz seems to be > accessible from this new page) > - Close the lookup. > - Try to reopen it, it doesn't show anything anymore. > The only hint I've found for explaining this problem is that the request to > open the lookup is somehow changed. > At first it is : > https://localhost:8443/content/control/LookupContent > But then it becomes : > https://localhost:8443/content/control/LookupLocale > The other lookup seems unusable too after that. > Did you already encounter this kind of problem before ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9279) Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find Content page
Aditya Sharma created OFBIZ-9279: Summary: Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find Content page Key: OFBIZ-9279 URL: https://issues.apache.org/jira/browse/OFBIZ-9279 Project: OFBiz Issue Type: Bug Reporter: Aditya Sharma Assignee: Aditya Sharma How to reproduce : 1. Log in the Content component 2. Go to the Content tab. https://localhost:8443/content/control/findContent 3. In the search form, open the lookup of the field ' Owner Content Id ' 4. Click on any of the table header links to sort the table. Results will be displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9279) Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9279: - Attachment: screenshot-1.png > Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9279 > URL: https://issues.apache.org/jira/browse/OFBIZ-9279 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Owner Content Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9280) Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9280: - Attachment: screenshot-1.png > Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9280 > URL: https://issues.apache.org/jira/browse/OFBIZ-9280 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Data Resource Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9280) Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find Content page
Aditya Sharma created OFBIZ-9280: Summary: Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find Content page Key: OFBIZ-9280 URL: https://issues.apache.org/jira/browse/OFBIZ-9280 Project: OFBiz Issue Type: Bug Reporter: Aditya Sharma Assignee: Aditya Sharma How to reproduce : 1. Log in the Content component 2. Go to the Content tab. https://localhost:8443/content/control/findContent 3. In the search form, open the lookup of the field ' Data Resource Id ' 4. Click on any of the table header links to sort the table. Results will be displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-7759) Link in LookupContent causes unwanted behaviour
[ https://issues.apache.org/jira/browse/OFBIZ-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950790#comment-15950790 ] Aditya Sharma commented on OFBIZ-7759: -- Thanks Jacques :) > Link in LookupContent causes unwanted behaviour > --- > > Key: OFBIZ-7759 > URL: https://issues.apache.org/jira/browse/OFBIZ-7759 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Aditya Sharma >Priority: Minor > Labels: content, locale, lookup > Fix For: Release Branch 14.12, Release Branch 15.12, Upcoming > Release, Release Branch 16.11 > > Attachments: OFBIZ-7759.patch, OFBIZ-7759.patch > > > How to reproduce : > - Log in the Content component > - Go to the Content tab > - In the search form, open the lookup of the field ' Owner Content Id ' > - Click on the search button > - In the result list, click on a button link in the column 'Data Resource Id' > - The form to edit the Content will be displayed (a whole OFBiz seems to be > accessible from this new page) > - Close the lookup. > - Try to reopen it, it doesn't show anything anymore. > The only hint I've found for explaining this problem is that the request to > open the lookup is somehow changed. > At first it is : > https://localhost:8443/content/control/LookupContent > But then it becomes : > https://localhost:8443/content/control/LookupLocale > The other lookup seems unusable too after that. > Did you already encounter this kind of problem before ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9280) Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942132#comment-15942132 ] Aditya Sharma commented on OFBIZ-9280: -- Problem: 1. Lookup dialog for dataResourceId uses "ListLookupDataResource" form to list Data Resource records. 2. "ListLookupDataResource" form extends "ListDataResource" form for all the fields. 3. Sort-field is set to true in "ListDataResource" form for all the fields. 4. Sort-field adds hyperlink to "LookupResource" . 5. When clicked link it moves to a new page and doesn't renders the response in the Lookup dialog. Solution: First of all it is a lookup to select DataResourceId so as the pattern followed in other lookups in OFBiz it should not have any sort-fields.To set it false, it should be overridden. If all fields needs to be overridden it is better not to extend "ListDataResource" form and add these fields right away. Apart from that added 'widget-style="smallSubmit"' to dataResourceId according to the uniform pattern followed. > Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9280 > URL: https://issues.apache.org/jira/browse/OFBIZ-9280 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Data Resource Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9280) Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9280: - Attachment: OFBIZ-9280.patch > Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9280 > URL: https://issues.apache.org/jira/browse/OFBIZ-9280 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9280.patch, screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Data Resource Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9301) CMS shows error screen on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9301: - Attachment: screenshot-1.png > CMS shows error screen on clicking Find button > -- > > Key: OFBIZ-9301 > URL: https://issues.apache.org/jira/browse/OFBIZ-9301 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: screenshot-1.png > > > Steps to regenerate : > 1. Log in to Content component > 2. Go to the CMS tab or directly go to > https://localhost:8443/content/control/CMSContentFind > 3. Click on "Find" submenu or directly go to > https://localhost:8443/content/control/AdminSearch > 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9300) Strange behaviour of Keyboard Shortcuts in WebPos
Aditya Sharma created OFBIZ-9300: Summary: Strange behaviour of Keyboard Shortcuts in WebPos Key: OFBIZ-9300 URL: https://issues.apache.org/jira/browse/OFBIZ-9300 Project: OFBiz Issue Type: Bug Reporter: Aditya Sharma Assignee: Aditya Sharma Steps to regenerate: 1. Navigate to https://localhost:8443/webpos/control/main. 2. Use Keyboard Shortcuts specified there. 3. From "Pay Pin" all are working for its subsequent operation.For example when you click on "Pay By CC" or use shortcut F7 it will perform Checkout which is next operation in the list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9301) CMS shows error screen on clicking Find button
Aditya Sharma created OFBIZ-9301: Summary: CMS shows error screen on clicking Find button Key: OFBIZ-9301 URL: https://issues.apache.org/jira/browse/OFBIZ-9301 Project: OFBiz Issue Type: Bug Components: content Reporter: Aditya Sharma Assignee: Aditya Sharma Steps to regenerate : 1. Log in to Content component 2. Go to the CMS tab or directly go to https://localhost:8443/content/control/CMSContentFind 3. Click on "Find" submenu or directly go to https://localhost:8443/content/control/AdminSearch 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OFBIZ-9300) Strange behaviour of Keyboard Shortcuts in WebPos
[ https://issues.apache.org/jira/browse/OFBIZ-9300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma closed OFBIZ-9300. Resolution: Duplicate > Strange behaviour of Keyboard Shortcuts in WebPos > - > > Key: OFBIZ-9300 > URL: https://issues.apache.org/jira/browse/OFBIZ-9300 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma > > Steps to regenerate: > 1. Navigate to https://localhost:8443/webpos/control/main. > 2. Use Keyboard Shortcuts specified there. > 3. From "Pay Pin" all are working for its subsequent operation.For example > when you click on "Pay By CC" or use shortcut F7 it will perform Checkout > which is next operation in the list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9300) Strange behaviour of Keyboard Shortcuts in WebPos
[ https://issues.apache.org/jira/browse/OFBIZ-9300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953407#comment-15953407 ] Aditya Sharma commented on OFBIZ-9300: -- I just missed that out. I will always keep that in mind while creating a new ticket. Thanks Jacques :) > Strange behaviour of Keyboard Shortcuts in WebPos > - > > Key: OFBIZ-9300 > URL: https://issues.apache.org/jira/browse/OFBIZ-9300 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma > > Steps to regenerate: > 1. Navigate to https://localhost:8443/webpos/control/main. > 2. Use Keyboard Shortcuts specified there. > 3. From "Pay Pin" all are working for its subsequent operation.For example > when you click on "Pay By CC" or use shortcut F7 it will perform Checkout > which is next operation in the list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9280) Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952529#comment-15952529 ] Aditya Sharma commented on OFBIZ-9280: -- Hi Jacques, I took various other references of List forms from ofbiz but can't find one with sortable in Lookup. When we make a field as sort true, it adds to table headings and always opens up to a new page. So its better to remove sort as its support may not be applicable to a lookup dialog. If I am missing something, please guide me with that. > Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9280 > URL: https://issues.apache.org/jira/browse/OFBIZ-9280 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Jacques Le Roux > Attachments: OFBIZ-9280.patch, OFBIZ-9280.patch, screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Data Resource Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-7759) Link in LookupContent causes unwanted behaviour
[ https://issues.apache.org/jira/browse/OFBIZ-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950233#comment-15950233 ] Aditya Sharma commented on OFBIZ-7759: -- Thanks Jacques for giving your precious time to it. I will update the patch. :) > Link in LookupContent causes unwanted behaviour > --- > > Key: OFBIZ-7759 > URL: https://issues.apache.org/jira/browse/OFBIZ-7759 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Aditya Sharma >Priority: Minor > Labels: content, locale, lookup > Attachments: OFBIZ-7759.patch > > > How to reproduce : > - Log in the Content component > - Go to the Content tab > - In the search form, open the lookup of the field ' Owner Content Id ' > - Click on the search button > - In the result list, click on a button link in the column 'Data Resource Id' > - The form to edit the Content will be displayed (a whole OFBiz seems to be > accessible from this new page) > - Close the lookup. > - Try to reopen it, it doesn't show anything anymore. > The only hint I've found for explaining this problem is that the request to > open the lookup is somehow changed. > At first it is : > https://localhost:8443/content/control/LookupContent > But then it becomes : > https://localhost:8443/content/control/LookupLocale > The other lookup seems unusable too after that. > Did you already encounter this kind of problem before ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9280) Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15951996#comment-15951996 ] Aditya Sharma commented on OFBIZ-9280: -- Thanks Jacques for the review :) I will update all my previous patches too with latest revision. > Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9280 > URL: https://issues.apache.org/jira/browse/OFBIZ-9280 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Jacques Le Roux > Attachments: OFBIZ-9280.patch, screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Data Resource Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9280) Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9280: - Attachment: OFBIZ-9280.patch Updated patch according to latest revision. > Sort Links in Lookup for Data Resource Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9280 > URL: https://issues.apache.org/jira/browse/OFBIZ-9280 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Jacques Le Roux > Attachments: OFBIZ-9280.patch, OFBIZ-9280.patch, screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Data Resource Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9279) Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952641#comment-15952641 ] Aditya Sharma commented on OFBIZ-9279: -- Thanks Jacques :) > Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9279 > URL: https://issues.apache.org/jira/browse/OFBIZ-9279 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Fix For: Release Branch 14.12, Release Branch 15.12, Upcoming > Release, 16.11.02 > > Attachments: OFBIZ-9279.patch, screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Owner Content Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9279) Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9279: - Attachment: OFBIZ-9279.patch Problem: 1. Lookup dialog for ownerContentId uses "ListLookupContent" form to list Content records. 2. "ListLookupContent" form extends "ListContent" form for all the fields. 3. Sort-field is set to true in "ListContent" form for all the fields. 4. Sort-field adds hyperlink to "LookupContent" . 5. When clicked link it moves to a new page and doesn't renders the response in the Lookup dialog. Solution: First of all it is a lookup to select ownerContentId so as the pattern followed in other lookups in OFBiz it should not have any sort-fields.To set it false, it should be overridden. If all fields needs to be overridden it is better not to extend "ListContent" form and add these fields right away. Apart from that added 'header-row-style="header-row-2"' to form. > Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9279 > URL: https://issues.apache.org/jira/browse/OFBIZ-9279 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9279.patch, screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Owner Content Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9279) Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find Content page
[ https://issues.apache.org/jira/browse/OFBIZ-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952655#comment-15952655 ] Aditya Sharma commented on OFBIZ-9279: -- Sure Jacques.I will create a new ticket for it and rectify that too. > Sort Links in Lookup for Owner Content Id causes unwanted behaviour on Find > Content page > > > Key: OFBIZ-9279 > URL: https://issues.apache.org/jira/browse/OFBIZ-9279 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Fix For: Release Branch 14.12, Release Branch 15.12, Upcoming > Release, 16.11.02 > > Attachments: OFBIZ-9279.patch, screenshot-1.png > > > How to reproduce : > 1. Log in the Content component > 2. Go to the Content tab. https://localhost:8443/content/control/findContent > 3. In the search form, open the lookup of the field ' Owner Content Id ' > 4. Click on any of the table header links to sort the table. Results will be > displayed on a new unstyled window closing the Lookup dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9310) On setting verbose true, UtilHttp.getParameterMap() method prints username and password in logs
Aditya Sharma created OFBIZ-9310:
Summary: On setting verbose true, UtilHttp.getParameterMap()
method prints username and password in logs
Key: OFBIZ-9310
URL: https://issues.apache.org/jira/browse/OFBIZ-9310
Project: OFBiz
Issue Type: Bug
Reporter: Aditya Sharma
Assignee: Aditya Sharma
In UtilHttp.getParameterMap(HttpServletRequest request, Set
nameSet, Boolean onlyIncludeOrSkip) method, following line of code prints
username and password in logs when verbose is set to true.
if (Debug.verboseOn()) {
Debug.logVerbose("Made Request Parameter Map with [" +
paramMap.size() + "] Entries", module);
Debug.logVerbose("Request Parameter Map Entries: " +
System.getProperty("line.separator") + UtilMisc.printMap(paramMap), module);
}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (OFBIZ-9308) CMS shows error screen on Product Search
[ https://issues.apache.org/jira/browse/OFBIZ-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963975#comment-15963975 ] Aditya Sharma commented on OFBIZ-9308: -- Thanks Jacques :) > CMS shows error screen on Product Search > > > Key: OFBIZ-9308 > URL: https://issues.apache.org/jira/browse/OFBIZ-9308 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Jacques Le Roux > Fix For: Upcoming Release > > Attachments: OFBIZ-9308.patch, screenshot-1.png > > > Steps to regenerate: > 1. Go to Content component (https://localhost:8443/content/control/main) > 2. Click on CMS tab (directing to > https://localhost:8443/content/control/CMSContentFind) > 3. Click on Search Products subtab (directing to > https://localhost:8443/content/control/ProductSearch) > 4. Provide a Lucene Query and Click submit. > 5. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9309) Ecommerce component showing error screen on searchContent from showcontenttree page
[ https://issues.apache.org/jira/browse/OFBIZ-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963826#comment-15963826 ] Aditya Sharma commented on OFBIZ-9309: -- Thank you for the kind words Jacques. :) > Ecommerce component showing error screen on searchContent from > showcontenttree page > --- > > Key: OFBIZ-9309 > URL: https://issues.apache.org/jira/browse/OFBIZ-9309 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Reporter: Aditya Sharma >Assignee: Jacques Le Roux > Fix For: Upcoming Release, 16.11.02 > > Attachments: OFBIZ-9309.patch, screenshot-1.png, > screenshot-2-whenNoIndex.png > > > Steps to reproduce: > 1.Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) > 2.Click on any of the Content from "Browse Content" section of left panel.It > will be directed to > https://localhost:8443/ecommerce/control/showcontenttree?contentId=STORE_POLICIES=STORE_POLICIES > 3. Click on Search, it directs to > https://localhost:8443/ecommerce/control/searchContent?siteId=STORE_POLICIES > 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9308) CMS shows error screen on Product Search
[ https://issues.apache.org/jira/browse/OFBIZ-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9308: - Attachment: (was: OFBIZ-9308.patch) > CMS shows error screen on Product Search > > > Key: OFBIZ-9308 > URL: https://issues.apache.org/jira/browse/OFBIZ-9308 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: screenshot-1.png > > > Steps to regenerate: > 1. Go to Content component (https://localhost:8443/content/control/main) > 2. Click on CMS tab (directing to > https://localhost:8443/content/control/CMSContentFind) > 3. Click on Search Products subtab (directing to > https://localhost:8443/content/control/ProductSearch) > 4. Provide a Lucene Query and Click submit. > 5. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9308) CMS shows error screen on Product Search
[ https://issues.apache.org/jira/browse/OFBIZ-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9308: - Attachment: OFBIZ-9308.patch Problem: 1. "ProductSearch" request directs to "ProductSearch" screen in LuceneScreens.xml. 2. On ProductSearch screen, "SearchProducts.groovy" script prepares and hits a search query to Lucene. 3. "BooleanQuery" class is used to match documents with other boolean query combinations. 4. BooleanQuery object is initialised with Its default constructor. 5. With Lucene 5.4.0, this constructor is deprecated. OFBiz migrated to Lucene 6.3.1: OFBIZ-8316 Solution: >From Lucene 5.4.0 default constructor is deprecated and a new inner class >Builder is created for queries. Refer OFBIZ-9301 for detailed explanation. > CMS shows error screen on Product Search > > > Key: OFBIZ-9308 > URL: https://issues.apache.org/jira/browse/OFBIZ-9308 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9308.patch, screenshot-1.png > > > Steps to regenerate: > 1. Go to Content component (https://localhost:8443/content/control/main) > 2. Click on CMS tab (directing to > https://localhost:8443/content/control/CMSContentFind) > 3. Click on Search Products subtab (directing to > https://localhost:8443/content/control/ProductSearch) > 4. Provide a Lucene Query and Click submit. > 5. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9308) CMS shows error screen on Product Search
[ https://issues.apache.org/jira/browse/OFBIZ-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9308: - Attachment: OFBIZ-9308.patch > CMS shows error screen on Product Search > > > Key: OFBIZ-9308 > URL: https://issues.apache.org/jira/browse/OFBIZ-9308 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9308.patch, screenshot-1.png > > > Steps to regenerate: > 1. Go to Content component (https://localhost:8443/content/control/main) > 2. Click on CMS tab (directing to > https://localhost:8443/content/control/CMSContentFind) > 3. Click on Search Products subtab (directing to > https://localhost:8443/content/control/ProductSearch) > 4. Provide a Lucene Query and Click submit. > 5. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9309) Ecommerce component showing error screen on searchContent from showcontenttree page
[ https://issues.apache.org/jira/browse/OFBIZ-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9309: - Attachment: OFBIZ-9309.patch Problem: 1. "searchContent" request directs to "searchContent" screen in ContentScreens.xml. 2. On searchContent screen, "/ecommerce/groovyScripts/content/Search.groovy" script prepares and hits a search query to Lucene. 3. "BooleanQuery" class is used to match documents with other boolean query combinations. 4. BooleanQuery object is initialised with Its default constructor. 5. With Lucene 5.4.0, this constructor is deprecated. OFBiz migrated to Lucene 6.3.1: OFBIZ-8316 Solution: >From Lucene 5.4.0 default constructor is deprecated and a new inner class >Builder is created for queries. Refer OFBIZ-9301 for detailed explanation. > Ecommerce component showing error screen on searchContent from > showcontenttree page > --- > > Key: OFBIZ-9309 > URL: https://issues.apache.org/jira/browse/OFBIZ-9309 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9309.patch, screenshot-1.png > > > Steps to reproduce: > 1.Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) > 2.Click on any of the Content from "Browse Content" section of left panel.It > will be directed to > https://localhost:8443/ecommerce/control/showcontenttree?contentId=STORE_POLICIES=STORE_POLICIES > 3. Click on Search, it directs to > https://localhost:8443/ecommerce/control/searchContent?siteId=STORE_POLICIES > 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9309) Ecommerce component showing error screen on searchContent from showcontenttree page
[ https://issues.apache.org/jira/browse/OFBIZ-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962057#comment-15962057 ] Aditya Sharma commented on OFBIZ-9309: -- Additional changes: Moved code to open of index files inside try-catch block as it may give ScreenRendering error when no index found. Attaching screenshot for the case. Updated error message from UILabel. > Ecommerce component showing error screen on searchContent from > showcontenttree page > --- > > Key: OFBIZ-9309 > URL: https://issues.apache.org/jira/browse/OFBIZ-9309 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9309.patch, screenshot-1.png > > > Steps to reproduce: > 1.Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) > 2.Click on any of the Content from "Browse Content" section of left panel.It > will be directed to > https://localhost:8443/ecommerce/control/showcontenttree?contentId=STORE_POLICIES=STORE_POLICIES > 3. Click on Search, it directs to > https://localhost:8443/ecommerce/control/searchContent?siteId=STORE_POLICIES > 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9309) Ecommerce component showing error screen on searchContent from showcontenttree page
[ https://issues.apache.org/jira/browse/OFBIZ-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9309: - Attachment: screenshot-2-whenNoIndex.png > Ecommerce component showing error screen on searchContent from > showcontenttree page > --- > > Key: OFBIZ-9309 > URL: https://issues.apache.org/jira/browse/OFBIZ-9309 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9309.patch, screenshot-1.png, > screenshot-2-whenNoIndex.png > > > Steps to reproduce: > 1.Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) > 2.Click on any of the Content from "Browse Content" section of left panel.It > will be directed to > https://localhost:8443/ecommerce/control/showcontenttree?contentId=STORE_POLICIES=STORE_POLICIES > 3. Click on Search, it directs to > https://localhost:8443/ecommerce/control/searchContent?siteId=STORE_POLICIES > 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (OFBIZ-9309) Ecommerce component showing error screen on searchContent from showcontenttree page
[ https://issues.apache.org/jira/browse/OFBIZ-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962057#comment-15962057 ] Aditya Sharma edited comment on OFBIZ-9309 at 4/9/17 7:29 AM: -- Additional changes: Moved code to "open index files" inside try-catch block as when not handled it may give ScreenRendering error when no index found. Attaching screenshot for the case. Updated error message from UILabel. was (Author: aditya.sharma): Additional changes: Moved code to open of index files inside try-catch block as it may give ScreenRendering error when no index found. Attaching screenshot for the case. Updated error message from UILabel. > Ecommerce component showing error screen on searchContent from > showcontenttree page > --- > > Key: OFBIZ-9309 > URL: https://issues.apache.org/jira/browse/OFBIZ-9309 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9309.patch, screenshot-1.png, > screenshot-2-whenNoIndex.png > > > Steps to reproduce: > 1.Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) > 2.Click on any of the Content from "Browse Content" section of left panel.It > will be directed to > https://localhost:8443/ecommerce/control/showcontenttree?contentId=STORE_POLICIES=STORE_POLICIES > 3. Click on Search, it directs to > https://localhost:8443/ecommerce/control/searchContent?siteId=STORE_POLICIES > 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9318) Create New Quote button is duplicated on View Quote page
Aditya Sharma created OFBIZ-9318: Summary: Create New Quote button is duplicated on View Quote page Key: OFBIZ-9318 URL: https://issues.apache.org/jira/browse/OFBIZ-9318 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Release Branch 16.11 Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Minor Attachments: screenshot-1.png Steps to regenerate: 1. Go to Order component (https://localhost:8443/ordermgr/control/main) 2. Click on Quotes submenu (directing to https://localhost:8443/ordermgr/control/FindQuote) 3. Click on Find button. 4. Click on any quoteId (directing to https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001) 5. Create New Quote button is duplicated. With OFBIZ-7841, to make it consistent Create New Quote button added to menu bar so we can remove the other button. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9318) Create New Quote button is duplicated on View Quote page
[ https://issues.apache.org/jira/browse/OFBIZ-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9318: - Attachment: screenshot-1.png > Create New Quote button is duplicated on View Quote page > > > Key: OFBIZ-9318 > URL: https://issues.apache.org/jira/browse/OFBIZ-9318 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > Attachments: screenshot-1.png > > > Steps to regenerate: > 1. Go to Order component (https://localhost:8443/ordermgr/control/main) > 2. Click on Quotes submenu (directing to > https://localhost:8443/ordermgr/control/FindQuote) > 3. Click on Find button. > 4. Click on any quoteId (directing to > https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001) > 5. Create New Quote button is duplicated. > With OFBIZ-7841, to make it consistent Create New Quote button added to menu > bar so we can remove the other button. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9320) User should be notified with success message on subscribing newsletter from ecommerce
Aditya Sharma created OFBIZ-9320: Summary: User should be notified with success message on subscribing newsletter from ecommerce Key: OFBIZ-9320 URL: https://issues.apache.org/jira/browse/OFBIZ-9320 Project: OFBiz Issue Type: Improvement Components: ecommerce Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Minor Steps to regenerate: 1. Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) 2. In Sign Up For Contact List section from the left panel, select contactList for Newsletter. 3. Fill out email and Click on subscribe button. There is no success message displayed to end user stating success of the action. At Service level, success message should also be there in the result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9320) User should be notified with success message on subscribing newsletter from ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9320: - Attachment: OFBIZ-9320.patch Problem: 1. On clicking "Subscribe" button for Anonymous User, it hits signUpForContactList request. 2. "signUpForContactList" request call "signUpForContactList" service. Solution: Added uiLabel for success message in MarketingUiLabels and used the new uiLabel in "signUpForContactList" service by passing it to ServiceUtil.returnSuccess() method. > User should be notified with success message on subscribing newsletter from > ecommerce > - > > Key: OFBIZ-9320 > URL: https://issues.apache.org/jira/browse/OFBIZ-9320 > Project: OFBiz > Issue Type: Sub-task > Components: ecommerce >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > Attachments: OFBIZ-9320.patch > > > Steps to regenerate: > 1. Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) > 2. In Sign Up For Contact List section from the left panel, select > contactList for Newsletter. > 3. Fill out email and Click on subscribe button. > There is no success message displayed to end user stating success of the > action. > At Service level, success message should also be there in the result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9310) On setting verbose true, UtilHttp.getParameterMap() method prints username and password in logs
[
https://issues.apache.org/jira/browse/OFBIZ-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968931#comment-15968931
]
Aditya Sharma commented on OFBIZ-9310:
--
Thanks Jacques :)
> On setting verbose true, UtilHttp.getParameterMap() method prints username
> and password in logs
> ---
>
> Key: OFBIZ-9310
> URL: https://issues.apache.org/jira/browse/OFBIZ-9310
> Project: OFBiz
> Issue Type: Sub-task
>Reporter: Aditya Sharma
>Assignee: Jacques Le Roux
> Fix For: Release Branch 14.12, Release Branch 15.12, Upcoming
> Release, 16.11.02
>
> Attachments: OFBIZ-9310.patch
>
>
> In UtilHttp.getParameterMap(HttpServletRequest request, Set
> nameSet, Boolean onlyIncludeOrSkip) method, following line of code prints
> username and password in logs when verbose is set to true.
> if (Debug.verboseOn()) {
> Debug.logVerbose("Made Request Parameter Map with [" +
> paramMap.size() + "] Entries", module);
> Debug.logVerbose("Request Parameter Map Entries: " +
> System.getProperty("line.separator") + UtilMisc.printMap(paramMap), module);
> }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (OFBIZ-9310) On setting verbose true, UtilHttp.getParameterMap() method prints username and password in logs
[
https://issues.apache.org/jira/browse/OFBIZ-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Sharma updated OFBIZ-9310:
-
Attachment: OFBIZ-9310.patch
Removed the line that prints "Request Parameter Map Entries" as it may print
username and password entered by user when verbose set to true. It may not be a
grave concern for staging environment as verbose are not logged there but it is
still unethical to print such details.
> On setting verbose true, UtilHttp.getParameterMap() method prints username
> and password in logs
> ---
>
> Key: OFBIZ-9310
> URL: https://issues.apache.org/jira/browse/OFBIZ-9310
> Project: OFBiz
> Issue Type: Bug
>Reporter: Aditya Sharma
>Assignee: Aditya Sharma
> Attachments: OFBIZ-9310.patch
>
>
> In UtilHttp.getParameterMap(HttpServletRequest request, Set
> nameSet, Boolean onlyIncludeOrSkip) method, following line of code prints
> username and password in logs when verbose is set to true.
> if (Debug.verboseOn()) {
> Debug.logVerbose("Made Request Parameter Map with [" +
> paramMap.size() + "] Entries", module);
> Debug.logVerbose("Request Parameter Map Entries: " +
> System.getProperty("line.separator") + UtilMisc.printMap(paramMap), module);
> }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (OFBIZ-9321) User should be notified with success message on Send Report by Mail from View Quote page
[ https://issues.apache.org/jira/browse/OFBIZ-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9321: - Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-9329 > User should be notified with success message on Send Report by Mail from View > Quote page > > > Key: OFBIZ-9321 > URL: https://issues.apache.org/jira/browse/OFBIZ-9321 > Project: OFBiz > Issue Type: Sub-task > Components: order >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > > Steps to regenerate: > 1. Go to Order component (https://localhost:8443/ordermgr/control/main) > 2. Click on Quotes submenu (directing to > https://localhost:8443/ordermgr/control/FindQuote) > 3. Click on Find button. > 4. Click on any quoteId (directing to > https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001) > 5. Click on Send Report by Mail button. (directing to > https://localhost:8443/ordermgr/control/EditQuoteReportMail?emailType=PRDS_QUO_CONFIRM=CQ0001) > 6. Fill SendTo, SendCC and Note and Click Submit button. > 7. On success, user should be notified with success message as "Email is > scheduled". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9329) User should be notified with success message on successful completion of any action
Aditya Sharma created OFBIZ-9329: Summary: User should be notified with success message on successful completion of any action Key: OFBIZ-9329 URL: https://issues.apache.org/jira/browse/OFBIZ-9329 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Release Branch 16.11 Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Minor On performing any action, user should be notified with the success message if the action has been performed successfully. Listing actions with no alert messages delivered on success and will be creating sub-tickets for the same. Ecommerce: 1. Subscribe to Newsletter: OFBIZ-9320 2. Add to Cart: 3. Create/Update Shopping List: 4. Last Categories > Clear: Order Manager: 1. Update Quote: 2. remove Quote Role: 3. Send Report by Mail from View Quote: OFBIZ-9321 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9320) User should be notified with success message on subscribing newsletter from ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9320: - Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-9329 > User should be notified with success message on subscribing newsletter from > ecommerce > - > > Key: OFBIZ-9320 > URL: https://issues.apache.org/jira/browse/OFBIZ-9320 > Project: OFBiz > Issue Type: Sub-task > Components: ecommerce >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > > Steps to regenerate: > 1. Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) > 2. In Sign Up For Contact List section from the left panel, select > contactList for Newsletter. > 3. Fill out email and Click on subscribe button. > There is no success message displayed to end user stating success of the > action. > At Service level, success message should also be there in the result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-9251) Add support for 'set-if-null' and 'set-if-empty' attributes on screens for set element.
[ https://issues.apache.org/jira/browse/OFBIZ-9251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma reassigned OFBIZ-9251: Assignee: Aditya Sharma > Add support for 'set-if-null' and 'set-if-empty' attributes on screens for > set element. > --- > > Key: OFBIZ-9251 > URL: https://issues.apache.org/jira/browse/OFBIZ-9251 > Project: OFBiz > Issue Type: Improvement >Reporter: Aditya Sharma >Assignee: Aditya Sharma > > "set-if-null" controls if field can be set to null and "set-if-empty" > controls if field can be set to an empty value. Both these attributes are > supported by "set" element of simple-method and similar support should be > there on the screen. > As stated in the discussion: > http://ofbiz.markmail.org/thread/hembr4hiabgwr7cs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9319) ScreenRenderException on sending report by mail from View Quote page
[ https://issues.apache.org/jira/browse/OFBIZ-9319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9319: - Attachment: screenshot-1.png > ScreenRenderException on sending report by mail from View Quote page > > > Key: OFBIZ-9319 > URL: https://issues.apache.org/jira/browse/OFBIZ-9319 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > Attachments: screenshot-1.png > > > Steps to regenerate: > 1. Go to Order component (https://localhost:8443/ordermgr/control/main) > 2. Click on Quotes submenu (directing to > https://localhost:8443/ordermgr/control/FindQuote) > 3. Click on Find button. > 4. Click on any quoteId (directing to > https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001) > 5. Click on Send Report by Mail button. (directing to > https://localhost:8443/ordermgr/control/EditQuoteReportMail?emailType=PRDS_QUO_CONFIRM=CQ0001) > 6. Fill SendTo, SendCC and Note and Click Submit button. > It shows a ScreenRenderException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9321) User should be notified with success message on Send Report by Mail from View Quote page
Aditya Sharma created OFBIZ-9321: Summary: User should be notified with success message on Send Report by Mail from View Quote page Key: OFBIZ-9321 URL: https://issues.apache.org/jira/browse/OFBIZ-9321 Project: OFBiz Issue Type: Improvement Components: order Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Minor Steps to regenerate: 1. Go to Order component (https://localhost:8443/ordermgr/control/main) 2. Click on Quotes submenu (directing to https://localhost:8443/ordermgr/control/FindQuote) 3. Click on Find button. 4. Click on any quoteId (directing to https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001) 5. Click on Send Report by Mail button. (directing to https://localhost:8443/ordermgr/control/EditQuoteReportMail?emailType=PRDS_QUO_CONFIRM=CQ0001) 6. Fill SendTo, SendCC and Note and Click Submit button. 7. On success, user should be notified with success message as "Email is scheduled". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (OFBIZ-9133) catalog/control/FindReviews does not render proper column data
[ https://issues.apache.org/jira/browse/OFBIZ-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923609#comment-15923609 ] Aditya Sharma edited comment on OFBIZ-9133 at 3/14/17 5:42 AM: --- Thanks Jacques Le Roux :) Thanks Wai for reporting the bug. Agreed to Jacques Le Roux that this issue may be specific to this form. The issue occurs only when same "field" has multiple conditions applied that too in "List" type form. was (Author: aditya.sharma): Thanks Jacques Le Roux :) Thanks Wai for the reporting the bug. Agreed to Jacques Le Roux that this issue may be specific to this form. The issue occurs only when same "field" has multiple conditions applied that too in "List" type form. > catalog/control/FindReviews does not render proper column data > -- > > Key: OFBIZ-9133 > URL: https://issues.apache.org/jira/browse/OFBIZ-9133 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Wai >Assignee: Jacques Le Roux > Fix For: Release Branch 13.07, Release Branch 14.12, Release > Branch 15.12, Upcoming Release, 16.11.02 > > Attachments: ofbiz-9133.patch, ofbiz-9133-Problem1.png, > ofbiz-9133-Problem2.png, ofbiz-9133-Solution.png > > > -go to https://localhost:8443/catalog/control/FindReviews > -find productId=GZ-2644 > -notice the table columns do not match the data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9133) catalog/control/FindReviews does not render proper column data
[ https://issues.apache.org/jira/browse/OFBIZ-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923609#comment-15923609 ] Aditya Sharma commented on OFBIZ-9133: -- Thanks Jacques Le Roux :) Thanks Wai for the reporting the bug. Agreed to Jacques Le Roux that this issue may be specific to this form. The issue occurs only when same "field" has multiple conditions applied that too in "List" type form. > catalog/control/FindReviews does not render proper column data > -- > > Key: OFBIZ-9133 > URL: https://issues.apache.org/jira/browse/OFBIZ-9133 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Wai >Assignee: Jacques Le Roux > Fix For: Release Branch 13.07, Release Branch 14.12, Release > Branch 15.12, Upcoming Release, 16.11.02 > > Attachments: ofbiz-9133.patch, ofbiz-9133-Problem1.png, > ofbiz-9133-Problem2.png, ofbiz-9133-Solution.png > > > -go to https://localhost:8443/catalog/control/FindReviews > -find productId=GZ-2644 > -notice the table columns do not match the data -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9301) CMS shows error screen on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961708#comment-15961708 ] Aditya Sharma commented on OFBIZ-9301: -- The problem must be present on other places too where Lucene is used. https://demo-trunk-ofbiz.apache.org:8443/ecommerce/control/searchContent So will create a separate ticket to update all the occurrences. > CMS shows error screen on clicking Find button > -- > > Key: OFBIZ-9301 > URL: https://issues.apache.org/jira/browse/OFBIZ-9301 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9301.patch, screenshot-1.png > > > Steps to regenerate : > 1. Log in to Content component > 2. Go to the CMS tab or directly go to > https://localhost:8443/content/control/CMSContentFind > 3. Click on "Find" submenu or directly go to > https://localhost:8443/content/control/AdminSearch > 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9301) CMS shows error screen on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9301: - Attachment: OFBIZ-9301.patch Problem: 1. "AdminSearch" request directs to "AdminSearch" screen in LuceneScreens.xml. 2. On AdminSearch screen, "Search.groovy" script prepares and hits a search query to Lucene. 3. "BooleanQuery" class is used to match documents with other boolean query combinations. 4. BooleanQuery object is initialised with Its default constructor. 5. With Lucene 5.4.0, this constructor is deprecated. OFBiz migrated to Lucene 6.3.1: OFBIZ-8316 Solution: >From Lucene 5.4.0 default constructor is deprecated and a new inner class >Builder is created for queries. References: https://lucene.apache.org/core/5_4_0/core/deprecated-list.html#constructor BooleanQuery Class documentation: https://lucene.apache.org/core/5_4_0/core/org/apache/lucene/search/BooleanQuery.html BooleanQuery.Builder Class documentation: https://lucene.apache.org/core/5_4_0/core/org/apache/lucene/search/BooleanQuery.Builder.html > CMS shows error screen on clicking Find button > -- > > Key: OFBIZ-9301 > URL: https://issues.apache.org/jira/browse/OFBIZ-9301 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9301.patch, screenshot-1.png > > > Steps to regenerate : > 1. Log in to Content component > 2. Go to the CMS tab or directly go to > https://localhost:8443/content/control/CMSContentFind > 3. Click on "Find" submenu or directly go to > https://localhost:8443/content/control/AdminSearch > 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9301) CMS shows error screen on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961743#comment-15961743 ] Aditya Sharma commented on OFBIZ-9301: -- Sure Jacques I will ensure that. Thanks for applying my patch :) > CMS shows error screen on clicking Find button > -- > > Key: OFBIZ-9301 > URL: https://issues.apache.org/jira/browse/OFBIZ-9301 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Jacques Le Roux > Fix For: Upcoming Release > > Attachments: OFBIZ-9301.patch, screenshot-1.png > > > Steps to regenerate : > 1. Log in to Content component > 2. Go to the CMS tab or directly go to > https://localhost:8443/content/control/CMSContentFind > 3. Click on "Find" submenu or directly go to > https://localhost:8443/content/control/AdminSearch > 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9308) CMS shows error screen on Product Search
Aditya Sharma created OFBIZ-9308: Summary: CMS shows error screen on Product Search Key: OFBIZ-9308 URL: https://issues.apache.org/jira/browse/OFBIZ-9308 Project: OFBiz Issue Type: Bug Components: content Reporter: Aditya Sharma Assignee: Aditya Sharma Steps to regenerate: 1. Go to Content component (https://localhost:8443/content/control/main) 2. Click on CMS tab (directing to https://localhost:8443/content/control/CMSContentFind) 3. Click on Search Products subtab (directing to https://localhost:8443/content/control/ProductSearch) 4. Provide a Lucene Query and Click submit. 5. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9308) CMS shows error screen on Product Search
[ https://issues.apache.org/jira/browse/OFBIZ-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9308: - Attachment: screenshot-1.png > CMS shows error screen on Product Search > > > Key: OFBIZ-9308 > URL: https://issues.apache.org/jira/browse/OFBIZ-9308 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: screenshot-1.png > > > Steps to regenerate: > 1. Go to Content component (https://localhost:8443/content/control/main) > 2. Click on CMS tab (directing to > https://localhost:8443/content/control/CMSContentFind) > 3. Click on Search Products subtab (directing to > https://localhost:8443/content/control/ProductSearch) > 4. Provide a Lucene Query and Click submit. > 5. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9309) Ecommerce component showing error screen on searchContent from showcontenttree page
Aditya Sharma created OFBIZ-9309: Summary: Ecommerce component showing error screen on searchContent from showcontenttree page Key: OFBIZ-9309 URL: https://issues.apache.org/jira/browse/OFBIZ-9309 Project: OFBiz Issue Type: Bug Components: ecommerce Reporter: Aditya Sharma Assignee: Aditya Sharma Steps to reproduce: 1.Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) 2.Click on any of the Content from "Browse Content" section of left panel.It will be directed to https://localhost:8443/ecommerce/control/showcontenttree?contentId=STORE_POLICIES=STORE_POLICIES 3. Click on Search, it directs to https://localhost:8443/ecommerce/control/searchContent?siteId=STORE_POLICIES 4. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-7759) Link in LookupContent causes unwanted behaviour
[ https://issues.apache.org/jira/browse/OFBIZ-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-7759: - Attachment: OFBIZ-7759.patch > Link in LookupContent causes unwanted behaviour > --- > > Key: OFBIZ-7759 > URL: https://issues.apache.org/jira/browse/OFBIZ-7759 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Aditya Sharma >Priority: Minor > Labels: content, locale, lookup > Attachments: OFBIZ-7759.patch, OFBIZ-7759.patch > > > How to reproduce : > - Log in the Content component > - Go to the Content tab > - In the search form, open the lookup of the field ' Owner Content Id ' > - Click on the search button > - In the result list, click on a button link in the column 'Data Resource Id' > - The form to edit the Content will be displayed (a whole OFBiz seems to be > accessible from this new page) > - Close the lookup. > - Try to reopen it, it doesn't show anything anymore. > The only hint I've found for explaining this problem is that the request to > open the lookup is somehow changed. > At first it is : > https://localhost:8443/content/control/LookupContent > But then it becomes : > https://localhost:8443/content/control/LookupLocale > The other lookup seems unusable too after that. > Did you already encounter this kind of problem before ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9318) Create New Quote button is duplicated on View Quote page
[ https://issues.apache.org/jira/browse/OFBIZ-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9318: - Attachment: OFBIZ-9318.patch Problem: 1. "ViewQuote" request directs to "ViewQuote" screen in QuoteScreens.xml. 2. On ViewQuote screen, it includes "QuoteSubTabBar" from OrderMenus.xml. 3. "QuoteSubTabBar" has a "Create New Quote" button. But as with OFBIZ-7841, to make it consistent Create New Quote button is added to menu bar. Solution: Removed the button to avoid redundancy. > Create New Quote button is duplicated on View Quote page > > > Key: OFBIZ-9318 > URL: https://issues.apache.org/jira/browse/OFBIZ-9318 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > Attachments: OFBIZ-9318.patch, screenshot-1.png > > > Steps to regenerate: > 1. Go to Order component (https://localhost:8443/ordermgr/control/main) > 2. Click on Quotes submenu (directing to > https://localhost:8443/ordermgr/control/FindQuote) > 3. Click on Find button. > 4. Click on any quoteId (directing to > https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001) > 5. Create New Quote button is duplicated. > With OFBIZ-7841, to make it consistent Create New Quote button added to menu > bar so we can remove the other button. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9318) Create New Quote button is duplicated on View Quote page
[ https://issues.apache.org/jira/browse/OFBIZ-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974055#comment-15974055 ] Aditya Sharma commented on OFBIZ-9318: -- Thanks Jacques :) > Create New Quote button is duplicated on View Quote page > > > Key: OFBIZ-9318 > URL: https://issues.apache.org/jira/browse/OFBIZ-9318 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Release, 16.11.02 > > Attachments: OFBIZ-9318.patch, screenshot-1.png > > > Steps to regenerate: > 1. Go to Order component (https://localhost:8443/ordermgr/control/main) > 2. Click on Quotes submenu (directing to > https://localhost:8443/ordermgr/control/FindQuote) > 3. Click on Find button. > 4. Click on any quoteId (directing to > https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001) > 5. Create New Quote button is duplicated. > With OFBIZ-7841, to make it consistent Create New Quote button added to menu > bar so we can remove the other button. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9351) Remove unnecessary field types
[
https://issues.apache.org/jira/browse/OFBIZ-9351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113894#comment-16113894
]
Aditya Sharma commented on OFBIZ-9351:
--
Thanks Deepak :)
> Remove unnecessary field types
> --
>
> Key: OFBIZ-9351
> URL: https://issues.apache.org/jira/browse/OFBIZ-9351
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Aditya Sharma
>Assignee: Deepak Dixit
>Priority: Trivial
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9351.patch, OFBIZ-9351.patch,
> OFBIZ-9351_plugins.patch
>
>
> As discussed in http://markmail.org/message/d2tpovewhtotukwa the "not empty"
> field types ("id-ne", "id-long-ne" and "id-vlong-ne") were initially added
> to implement validations on data. But, because the validations where only
> implemented in some place like webtools, it contradicts the distinction to be
> upheld on various layers. So it is better to remove these field types. So we
> will remove all those field types and will create sub tickets to replace them
> in entity definitions by corresponding "id" types.
> When replacing the "not empty" field types in entity definitions by
> corresponding "id" types we will add a *not-null="true"* attribute to "makes
> the field NOT NULL on the database (like primary key fields)" as explained in
> "not-null" documentation in fieldtypemodel.xsd. We will finally clean the
> documentation of the "not-null" in fieldtypemodel.xsd.
> Related Links:
> http://ofbiz.135035.n4.nabble.com/EntityEngine-field-types-td2251546.html
> http://markmail.org/message/otec62xiwkpjttkq
> A more vivid description:
> http://ofbiz.markmail.org/thread/c6ee3ewyo6jpik7k
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-9355) Replace fields with "id-ne", "id-long-ne" and "id-vlong-ne" by "id", "id-long" and "id-vlong" respectively which are not primary keys
[ https://issues.apache.org/jira/browse/OFBIZ-9355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113886#comment-16113886 ] Aditya Sharma commented on OFBIZ-9355: -- Thanks Deepak :) > Replace fields with "id-ne", "id-long-ne" and "id-vlong-ne" by "id", > "id-long" and "id-vlong" respectively which are not primary keys > - > > Key: OFBIZ-9355 > URL: https://issues.apache.org/jira/browse/OFBIZ-9355 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Deepak Dixit >Priority: Trivial > Fix For: Upcoming Release > > Attachments: OFBIZ-9355.patch, OFBIZ-9355_plugins.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9351) Remove unnecessary field types
[
https://issues.apache.org/jira/browse/OFBIZ-9351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113968#comment-16113968
]
Aditya Sharma commented on OFBIZ-9351:
--
Updated Entity Engine Guide
https://cwiki.apache.org/confluence/display/OFBIZ/Entity+Engine+Guide.
> Remove unnecessary field types
> --
>
> Key: OFBIZ-9351
> URL: https://issues.apache.org/jira/browse/OFBIZ-9351
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Aditya Sharma
>Assignee: Deepak Dixit
>Priority: Trivial
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9351.patch, OFBIZ-9351.patch,
> OFBIZ-9351_plugins.patch
>
>
> As discussed in http://markmail.org/message/d2tpovewhtotukwa the "not empty"
> field types ("id-ne", "id-long-ne" and "id-vlong-ne") were initially added
> to implement validations on data. But, because the validations where only
> implemented in some place like webtools, it contradicts the distinction to be
> upheld on various layers. So it is better to remove these field types. So we
> will remove all those field types and will create sub tickets to replace them
> in entity definitions by corresponding "id" types.
> When replacing the "not empty" field types in entity definitions by
> corresponding "id" types we will add a *not-null="true"* attribute to "makes
> the field NOT NULL on the database (like primary key fields)" as explained in
> "not-null" documentation in fieldtypemodel.xsd. We will finally clean the
> documentation of the "not-null" in fieldtypemodel.xsd.
> Related Links:
> http://ofbiz.135035.n4.nabble.com/EntityEngine-field-types-td2251546.html
> http://markmail.org/message/otec62xiwkpjttkq
> A more vivid description:
> http://ofbiz.markmail.org/thread/c6ee3ewyo6jpik7k
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-9351) Remove unnecessary field types
[
https://issues.apache.org/jira/browse/OFBIZ-9351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Sharma updated OFBIZ-9351:
-
Attachment: OFBIZ-9351.patch
Removed field types "id-ne", "id-long-ne" and "id-vlong-ne" from fieldtype*.xml
files in this patch.
> Remove unnecessary field types
> --
>
> Key: OFBIZ-9351
> URL: https://issues.apache.org/jira/browse/OFBIZ-9351
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Aditya Sharma
>Assignee: Deepak Dixit
>Priority: Trivial
> Attachments: OFBIZ-9351.patch, OFBIZ-9351.patch,
> OFBIZ-9351_plugins.patch
>
>
> As discussed in http://markmail.org/message/d2tpovewhtotukwa the "not empty"
> field types ("id-ne", "id-long-ne" and "id-vlong-ne") were initially added
> to implement validations on data. But, because the validations where only
> implemented in some place like webtools, it contradicts the distinction to be
> upheld on various layers. So it is better to remove these field types. So we
> will remove all those field types and will create sub tickets to replace them
> in entity definitions by corresponding "id" types.
> When replacing the "not empty" field types in entity definitions by
> corresponding "id" types we will add a *not-null="true"* attribute to "makes
> the field NOT NULL on the database (like primary key fields)" as explained in
> "not-null" documentation in fieldtypemodel.xsd. We will finally clean the
> documentation of the "not-null" in fieldtypemodel.xsd.
> Related Links:
> http://ofbiz.135035.n4.nabble.com/EntityEngine-field-types-td2251546.html
> http://markmail.org/message/otec62xiwkpjttkq
> A more vivid description:
> http://ofbiz.markmail.org/thread/c6ee3ewyo6jpik7k
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-9351) Remove unnecessary field types
[
https://issues.apache.org/jira/browse/OFBIZ-9351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112691#comment-16112691
]
Aditya Sharma commented on OFBIZ-9351:
--
Before committing the latest patch, patch in OFBIZ-9355 needs to be committed.
> Remove unnecessary field types
> --
>
> Key: OFBIZ-9351
> URL: https://issues.apache.org/jira/browse/OFBIZ-9351
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Aditya Sharma
>Assignee: Deepak Dixit
>Priority: Trivial
> Attachments: OFBIZ-9351.patch, OFBIZ-9351.patch,
> OFBIZ-9351_plugins.patch
>
>
> As discussed in http://markmail.org/message/d2tpovewhtotukwa the "not empty"
> field types ("id-ne", "id-long-ne" and "id-vlong-ne") were initially added
> to implement validations on data. But, because the validations where only
> implemented in some place like webtools, it contradicts the distinction to be
> upheld on various layers. So it is better to remove these field types. So we
> will remove all those field types and will create sub tickets to replace them
> in entity definitions by corresponding "id" types.
> When replacing the "not empty" field types in entity definitions by
> corresponding "id" types we will add a *not-null="true"* attribute to "makes
> the field NOT NULL on the database (like primary key fields)" as explained in
> "not-null" documentation in fieldtypemodel.xsd. We will finally clean the
> documentation of the "not-null" in fieldtypemodel.xsd.
> Related Links:
> http://ofbiz.135035.n4.nabble.com/EntityEngine-field-types-td2251546.html
> http://markmail.org/message/otec62xiwkpjttkq
> A more vivid description:
> http://ofbiz.markmail.org/thread/c6ee3ewyo6jpik7k
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OFBIZ-9581) Merge extended entity definition in data model component into the existing entity definition
Aditya Sharma created OFBIZ-9581: Summary: Merge extended entity definition in data model component into the existing entity definition Key: OFBIZ-9581 URL: https://issues.apache.org/jira/browse/OFBIZ-9581 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: Trunk Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Minor Commonly used entities extended in data model component like UserLogin, UserLoginHistory, Visit etc can be merged to their existing definition only. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9508) Convert createPartyDataSource service to entity-auto
[ https://issues.apache.org/jira/browse/OFBIZ-9508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9508: - Affects Version/s: (was: Release Branch 16.11) > Convert createPartyDataSource service to entity-auto > > > Key: OFBIZ-9508 > URL: https://issues.apache.org/jira/browse/OFBIZ-9508 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Deepak Dixit >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-9508.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9465) Replace Inline Javascript with External Javascript
[ https://issues.apache.org/jira/browse/OFBIZ-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9465: - Attachment: OFBIZ-9465.patch OFBIZ-9465_example.patch Removed inline code for masking as well as added an example in Form Widget Examples. > Replace Inline Javascript with External Javascript > --- > > Key: OFBIZ-9465 > URL: https://issues.apache.org/jira/browse/OFBIZ-9465 > Project: OFBiz > Issue Type: Improvement >Reporter: Aditya Sharma >Assignee: Aditya Sharma > Attachments: OFBIZ-9465_example.patch, OFBIZ-9465.patch > > > As discussed in http://ofbiz.markmail.org/thread/ti54omjdt4fy662m inline > javascript for various macros like renderLookupField, > makeHyperlinkString,shortDateInput etc in HtmlFormMacroLibrary.ftl should be > replaced with a generic code written as external javascript. Generic > Javascript code should be written in OfbizUtil.js and appropriate classes or > identifiers should be used for applying that. Any additional data can be > passed with HTML 5 custom data attribute > (https://www.w3.org/TR/2011/WD-html5-20110525/elements.html#embedding-custom-non-visible-data-with-the-data-attributes). > As suggested by Jacques in https://s.apache.org/y8P1 will introduce > require.js for the split javascript files in a sub-task. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9493) Replace Masked Input Plugin with jQuery-Mask-Plugin.
Aditya Sharma created OFBIZ-9493: Summary: Replace Masked Input Plugin with jQuery-Mask-Plugin. Key: OFBIZ-9493 URL: https://issues.apache.org/jira/browse/OFBIZ-9493 Project: OFBiz Issue Type: Improvement Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Minor Current plugin Masked Input Plugin (http://digitalbush.com/projects/masked-input-plugin/) can be replaced with jQuery-Mask-Plugin (https://igorescobar.github.io/jQuery-Mask-Plugin/). * jQuery-Mask-Plugin has much better community support on GitHub while Masked Input Plugin is handled by Josh Bush on digitalbush.com. * jQuery-Mask-Plugin has 135 releases while Masked Input Plugin has very few releases yet. * Both the plugin has MIT license. Refer https://github.com/igorescobar/jQuery-Mask-Plugin for more features and other information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9494) Wrong repository links on FormWidgetExamples page
Aditya Sharma created OFBIZ-9494: Summary: Wrong repository links on FormWidgetExamples page Key: OFBIZ-9494 URL: https://issues.apache.org/jira/browse/OFBIZ-9494 Project: OFBiz Issue Type: Bug Components: example Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Trivial Steps to reproduce: 1. Go to example component (https://demo-trunk.ofbiz.apache.org/example/control/main) 2. Click on Form Widget Examples (https://demo-trunk.ofbiz.apache.org/example/control/FormWidgetExamples) Links for the file plugins/example/widget/example/FormWidgetExampleForms.xml are not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9308) CMS shows error screen on Product Search
[ https://issues.apache.org/jira/browse/OFBIZ-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089849#comment-16089849 ] Aditya Sharma commented on OFBIZ-9308: -- Changes reverted in revision:179477 [http://markmail.org/message/x5wjustjvpf3jyqv] Hence reopening > CMS shows error screen on Product Search > > > Key: OFBIZ-9308 > URL: https://issues.apache.org/jira/browse/OFBIZ-9308 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Jacques Le Roux > Fix For: Upcoming Release > > Attachments: OFBIZ-9308.patch, screenshot-1.png > > > Steps to regenerate: > 1. Go to Content component (https://localhost:8443/content/control/main) > 2. Click on CMS tab (directing to > https://localhost:8443/content/control/CMSContentFind) > 3. Click on Search Products subtab (directing to > https://localhost:8443/content/control/ProductSearch) > 4. Provide a Lucene Query and Click submit. > 5. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (OFBIZ-9308) CMS shows error screen on Product Search
[ https://issues.apache.org/jira/browse/OFBIZ-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma reopened OFBIZ-9308: -- > CMS shows error screen on Product Search > > > Key: OFBIZ-9308 > URL: https://issues.apache.org/jira/browse/OFBIZ-9308 > Project: OFBiz > Issue Type: Bug > Components: content >Reporter: Aditya Sharma >Assignee: Jacques Le Roux > Fix For: Upcoming Release > > Attachments: OFBIZ-9308.patch, screenshot-1.png > > > Steps to regenerate: > 1. Go to Content component (https://localhost:8443/content/control/main) > 2. Click on CMS tab (directing to > https://localhost:8443/content/control/CMSContentFind) > 3. Click on Search Products subtab (directing to > https://localhost:8443/content/control/ProductSearch) > 4. Provide a Lucene Query and Click submit. > 5. Screen renders with ScreenRenderingException -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9465) Replace Inline Javascript with External Javascript
[ https://issues.apache.org/jira/browse/OFBIZ-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9465: - Description: As discussed in http://ofbiz.markmail.org/thread/ti54omjdt4fy662m inline javascript for various macros like renderLookupField, makeHyperlinkString,shortDateInput etc in HtmlFormMacroLibrary.ftl should be replaced with a generic code written as external javascript. Generic Javascript code should be written in OfbizUtil.js and appropriate classes or identifiers should be used for applying that. Any additional data can be passed with HTML 5 custom data attribute (https://www.w3.org/TR/2011/WD-html5-20110525/elements.html#embedding-custom-non-visible-data-with-the-data-attributes). As suggested by Jacques in https://s.apache.org/y8P1 will introduce require.js for the split javascript files in a sub task. was:As discussed in http://ofbiz.markmail.org/thread/ti54omjdt4fy662m inline javascript for various macros like renderLookupField, makeHyperlinkString,shortDateInput etc in HtmlFormMacroLibrary.ftl should be replaced with a generic code written as external javascript. Generic Javascript code should be written in OfbizUtil.js and appropriate classes or identifiers should be used for applying that. Any additional data can be passed with HTML 5 custom data attribute (https://www.w3.org/TR/2011/WD-html5-20110525/elements.html#embedding-custom-non-visible-data-with-the-data-attributes). > Replace Inline Javascript with External Javascript > --- > > Key: OFBIZ-9465 > URL: https://issues.apache.org/jira/browse/OFBIZ-9465 > Project: OFBiz > Issue Type: Improvement >Reporter: Aditya Sharma >Assignee: Aditya Sharma > > As discussed in http://ofbiz.markmail.org/thread/ti54omjdt4fy662m inline > javascript for various macros like renderLookupField, > makeHyperlinkString,shortDateInput etc in HtmlFormMacroLibrary.ftl should be > replaced with a generic code written as external javascript. Generic > Javascript code should be written in OfbizUtil.js and appropriate classes or > identifiers should be used for applying that. Any additional data can be > passed with HTML 5 custom data attribute > (https://www.w3.org/TR/2011/WD-html5-20110525/elements.html#embedding-custom-non-visible-data-with-the-data-attributes). > As suggested by Jacques in https://s.apache.org/y8P1 will introduce > require.js for the split javascript files in a sub task. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9465) Replace Inline Javascript with External Javascript
[ https://issues.apache.org/jira/browse/OFBIZ-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9465: - Description: As discussed in http://ofbiz.markmail.org/thread/ti54omjdt4fy662m inline javascript for various macros like renderLookupField, makeHyperlinkString,shortDateInput etc in HtmlFormMacroLibrary.ftl should be replaced with a generic code written as external javascript. Generic Javascript code should be written in OfbizUtil.js and appropriate classes or identifiers should be used for applying that. Any additional data can be passed with HTML 5 custom data attribute (https://www.w3.org/TR/2011/WD-html5-20110525/elements.html#embedding-custom-non-visible-data-with-the-data-attributes). As suggested by Jacques in https://s.apache.org/y8P1 will introduce require.js for the split javascript files in a sub-task. was: As discussed in http://ofbiz.markmail.org/thread/ti54omjdt4fy662m inline javascript for various macros like renderLookupField, makeHyperlinkString,shortDateInput etc in HtmlFormMacroLibrary.ftl should be replaced with a generic code written as external javascript. Generic Javascript code should be written in OfbizUtil.js and appropriate classes or identifiers should be used for applying that. Any additional data can be passed with HTML 5 custom data attribute (https://www.w3.org/TR/2011/WD-html5-20110525/elements.html#embedding-custom-non-visible-data-with-the-data-attributes). As suggested by Jacques in https://s.apache.org/y8P1 will introduce require.js for the split javascript files in a sub task. > Replace Inline Javascript with External Javascript > --- > > Key: OFBIZ-9465 > URL: https://issues.apache.org/jira/browse/OFBIZ-9465 > Project: OFBiz > Issue Type: Improvement >Reporter: Aditya Sharma >Assignee: Aditya Sharma > > As discussed in http://ofbiz.markmail.org/thread/ti54omjdt4fy662m inline > javascript for various macros like renderLookupField, > makeHyperlinkString,shortDateInput etc in HtmlFormMacroLibrary.ftl should be > replaced with a generic code written as external javascript. Generic > Javascript code should be written in OfbizUtil.js and appropriate classes or > identifiers should be used for applying that. Any additional data can be > passed with HTML 5 custom data attribute > (https://www.w3.org/TR/2011/WD-html5-20110525/elements.html#embedding-custom-non-visible-data-with-the-data-attributes). > As suggested by Jacques in https://s.apache.org/y8P1 will introduce > require.js for the split javascript files in a sub-task. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9455) Required check missing for supplier product id and last price on Add Product Supplier page
Aditya Sharma created OFBIZ-9455: Summary: Required check missing for supplier product id and last price on Add Product Supplier page Key: OFBIZ-9455 URL: https://issues.apache.org/jira/browse/OFBIZ-9455 Project: OFBiz Issue Type: Bug Components: product Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Trivial Steps to reproduce: 1. Log in to Catalog component (https://demo-trunk.ofbiz.apache.org/catalog/control/main) 2. Go to the Products tab. (https://demo-trunk.ofbiz.apache.org/catalog/control/FindProduct) 3. Find a product and click on id link. (https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=WG-9943). 4. Click on Suppliers subtab.(https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductSuppliers?productId=WG-9943) 5. Click Create button on Add Product Supplier form. No required validation so an error message from the service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9456) Required check missing for Routing Task Name on Add Routing Task page
[ https://issues.apache.org/jira/browse/OFBIZ-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9456: - Attachment: OFBIZ-9456.patch Solution: EditRoutingTask form in RoutingTaskForms.xml does not have required check for Routing Task Name. Added Routing Task Name field with required-field-true. > Required check missing for Routing Task Name on Add Routing Task page > - > > Key: OFBIZ-9456 > URL: https://issues.apache.org/jira/browse/OFBIZ-9456 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Trivial > Attachments: OFBIZ-9456.patch, screenshot-1.png > > > Steps to reproduce: > 1. Log in to Manufacturing component > (https://demo-trunk.ofbiz.apache.org/manufacturing/control/main) > 2. Go to the Routing Task tab. > (https://demo-trunk.ofbiz.apache.org/manufacturing/control/FindRoutingTask) > 3. Click on New Routing Task > button.(https://demo-trunk.ofbiz.apache.org/manufacturing/control/EditRoutingTask) > 4. Click Create button on Add Routing Task page. > No required validation so an error message from the service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9455) Required check missing for supplier product id and last price on Add Product Supplier page
[ https://issues.apache.org/jira/browse/OFBIZ-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9455: - Attachment: OFBIZ-9455.patch Solution: AddProductSupplier form in ProductForms.xml uses auto-field-services for this field due to which there was no required check. Added supplierProductId and lastPrice fields with required-field-true. > Required check missing for supplier product id and last price on Add Product > Supplier page > -- > > Key: OFBIZ-9455 > URL: https://issues.apache.org/jira/browse/OFBIZ-9455 > Project: OFBiz > Issue Type: Bug > Components: product >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Trivial > Attachments: OFBIZ-9455.patch, screenshot-1.png > > > Steps to reproduce: > 1. Log in to Catalog component > (https://demo-trunk.ofbiz.apache.org/catalog/control/main) > 2. Go to the Products tab. > (https://demo-trunk.ofbiz.apache.org/catalog/control/FindProduct) > 3. Find a product and click on id link. > (https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=WG-9943). > 4. Click on Suppliers > subtab.(https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductSuppliers?productId=WG-9943) > 5. Click Create button on Add Product Supplier form. > No required validation so an error message from the service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9456) Required check missing for Routing Task Name on Add Routing Task page
Aditya Sharma created OFBIZ-9456: Summary: Required check missing for Routing Task Name on Add Routing Task page Key: OFBIZ-9456 URL: https://issues.apache.org/jira/browse/OFBIZ-9456 Project: OFBiz Issue Type: Bug Components: manufacturing Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Trivial Steps to reproduce: 1. Log in to Manufacturing component (https://demo-trunk.ofbiz.apache.org/manufacturing/control/main) 2. Go to the Routing Task tab. (https://demo-trunk.ofbiz.apache.org/manufacturing/control/FindRoutingTask) 3. Click on New Routing Task button.(https://demo-trunk.ofbiz.apache.org/manufacturing/control/EditRoutingTask) 4. Click Create button on Add Routing Task page. No required validation so an error message from the service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9455) Required check missing for supplier product id and last price on Add Product Supplier page
[ https://issues.apache.org/jira/browse/OFBIZ-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9455: - Attachment: screenshot-1.png > Required check missing for supplier product id and last price on Add Product > Supplier page > -- > > Key: OFBIZ-9455 > URL: https://issues.apache.org/jira/browse/OFBIZ-9455 > Project: OFBiz > Issue Type: Bug > Components: product >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Trivial > Attachments: screenshot-1.png > > > Steps to reproduce: > 1. Log in to Catalog component > (https://demo-trunk.ofbiz.apache.org/catalog/control/main) > 2. Go to the Products tab. > (https://demo-trunk.ofbiz.apache.org/catalog/control/FindProduct) > 3. Find a product and click on id link. > (https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=WG-9943). > 4. Click on Suppliers > subtab.(https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductSuppliers?productId=WG-9943) > 5. Click Create button on Add Product Supplier form. > No required validation so an error message from the service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9456) Required check missing for Routing Task Name on Add Routing Task page
[ https://issues.apache.org/jira/browse/OFBIZ-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9456: - Attachment: screenshot-1.png > Required check missing for Routing Task Name on Add Routing Task page > - > > Key: OFBIZ-9456 > URL: https://issues.apache.org/jira/browse/OFBIZ-9456 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Trivial > Attachments: screenshot-1.png > > > Steps to reproduce: > 1. Log in to Manufacturing component > (https://demo-trunk.ofbiz.apache.org/manufacturing/control/main) > 2. Go to the Routing Task tab. > (https://demo-trunk.ofbiz.apache.org/manufacturing/control/FindRoutingTask) > 3. Click on New Routing Task > button.(https://demo-trunk.ofbiz.apache.org/manufacturing/control/EditRoutingTask) > 4. Click Create button on Add Routing Task page. > No required validation so an error message from the service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9455) Required check missing for supplier product id and last price on Add Product Supplier page
[ https://issues.apache.org/jira/browse/OFBIZ-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079029#comment-16079029 ] Aditya Sharma commented on OFBIZ-9455: -- Thanks, Arun :) > Required check missing for supplier product id and last price on Add Product > Supplier page > -- > > Key: OFBIZ-9455 > URL: https://issues.apache.org/jira/browse/OFBIZ-9455 > Project: OFBiz > Issue Type: Bug > Components: product >Reporter: Aditya Sharma >Assignee: Arun Patidar >Priority: Trivial > Fix For: Upcoming Release > > Attachments: OFBIZ-9455.patch, screenshot-1.png > > > Steps to reproduce: > 1. Log in to Catalog component > (https://demo-trunk.ofbiz.apache.org/catalog/control/main) > 2. Go to the Products tab. > (https://demo-trunk.ofbiz.apache.org/catalog/control/FindProduct) > 3. Find a product and click on id link. > (https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=WG-9943). > 4. Click on Suppliers > subtab.(https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductSuppliers?productId=WG-9943) > 5. Click Create button on Add Product Supplier form. > No required validation so an error message from the service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9463) Required check missing for Routing Task Id and Sequence Num on Add Routing Task Assoc page
Aditya Sharma created OFBIZ-9463: Summary: Required check missing for Routing Task Id and Sequence Num on Add Routing Task Assoc page Key: OFBIZ-9463 URL: https://issues.apache.org/jira/browse/OFBIZ-9463 Project: OFBiz Issue Type: Bug Components: manufacturing Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Trivial Steps to reproduce: 1. Log in to Manufacturing component (https://demo-trunk.ofbiz.apache.org/manufacturing/control/main) 2. Go to the Routing tab. (https://demo-trunk.ofbiz.apache.org/manufacturing/control/FindRouting) 3. Click on any Routing Id link. (https://demo-trunk.ofbiz.apache.org/manufacturing/control/EditRouting?workEffortId=DEFAULT_ROUTING) 4. Click on Edit Routing Task subtab (https://demo-trunk.ofbiz.apache.org/manufacturing/control/EditRoutingTaskAssoc?workEffortId=DEFAULT_ROUTING) 5. Click Add a existing RoutingTask button. No required validation so an error message from the service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9465) Replace Inline Javascript with External Javascript
Aditya Sharma created OFBIZ-9465: Summary: Replace Inline Javascript with External Javascript Key: OFBIZ-9465 URL: https://issues.apache.org/jira/browse/OFBIZ-9465 Project: OFBiz Issue Type: Improvement Reporter: Aditya Sharma As discussed in http://ofbiz.markmail.org/thread/ti54omjdt4fy662m inline javascript for various macros like renderLookupField, makeHyperlinkString,shortDateInput etc in HtmlFormMacroLibrary.ftl should be replaced with a generic code written as external javascript. Generic Javascript code should be written in OfbizUtil.js and appropriate classes or identifiers should be used for applying that. Any additional data can be passed with HTML 5 custom data attribute (https://www.w3.org/TR/2011/WD-html5-20110525/elements.html#embedding-custom-non-visible-data-with-the-data-attributes). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9465) Replace Inline Javascript with External Javascript
[ https://issues.apache.org/jira/browse/OFBIZ-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma reassigned OFBIZ-9465: Assignee: Aditya Sharma > Replace Inline Javascript with External Javascript > --- > > Key: OFBIZ-9465 > URL: https://issues.apache.org/jira/browse/OFBIZ-9465 > Project: OFBiz > Issue Type: Improvement >Reporter: Aditya Sharma >Assignee: Aditya Sharma > > As discussed in http://ofbiz.markmail.org/thread/ti54omjdt4fy662m inline > javascript for various macros like renderLookupField, > makeHyperlinkString,shortDateInput etc in HtmlFormMacroLibrary.ftl should be > replaced with a generic code written as external javascript. Generic > Javascript code should be written in OfbizUtil.js and appropriate classes or > identifiers should be used for applying that. Any additional data can be > passed with HTML 5 custom data attribute > (https://www.w3.org/TR/2011/WD-html5-20110525/elements.html#embedding-custom-non-visible-data-with-the-data-attributes). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9456) Required check missing for Routing Task Name on Add Routing Task page
[ https://issues.apache.org/jira/browse/OFBIZ-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079056#comment-16079056 ] Aditya Sharma commented on OFBIZ-9456: -- Thanks, Arun :) > Required check missing for Routing Task Name on Add Routing Task page > - > > Key: OFBIZ-9456 > URL: https://issues.apache.org/jira/browse/OFBIZ-9456 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Reporter: Aditya Sharma >Assignee: Arun Patidar >Priority: Trivial > Fix For: Upcoming Release > > Attachments: OFBIZ-9456.patch, screenshot-1.png > > > Steps to reproduce: > 1. Log in to Manufacturing component > (https://demo-trunk.ofbiz.apache.org/manufacturing/control/main) > 2. Go to the Routing Task tab. > (https://demo-trunk.ofbiz.apache.org/manufacturing/control/FindRoutingTask) > 3. Click on New Routing Task > button.(https://demo-trunk.ofbiz.apache.org/manufacturing/control/EditRoutingTask) > 4. Click Create button on Add Routing Task page. > No required validation so an error message from the service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9494) Wrong repository links on FormWidgetExamples page
[ https://issues.apache.org/jira/browse/OFBIZ-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9494: - Attachment: OFBIZ-9494.patch Updated the URL path and instead of changing it at all places introduced a variable which is used everywhere so that in future same variable value should be changed instead of changing its redundant occurrences. > Wrong repository links on FormWidgetExamples page > - > > Key: OFBIZ-9494 > URL: https://issues.apache.org/jira/browse/OFBIZ-9494 > Project: OFBiz > Issue Type: Bug > Components: example >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Trivial > Attachments: OFBIZ-9494.patch > > > Steps to reproduce: > 1. Go to example component > (https://demo-trunk.ofbiz.apache.org/example/control/main) > 2. Click on Form Widget Examples > (https://demo-trunk.ofbiz.apache.org/example/control/FormWidgetExamples) > Links for the file plugins/example/widget/example/FormWidgetExampleForms.xml > are not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9497) Profile link for Lead not working properly in sfa component
[ https://issues.apache.org/jira/browse/OFBIZ-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9497: - Attachment: screenshot-1.png > Profile link for Lead not working properly in sfa component > --- > > Key: OFBIZ-9497 > URL: https://issues.apache.org/jira/browse/OFBIZ-9497 > Project: OFBiz > Issue Type: Bug >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Trivial > Attachments: screenshot-1.png > > > Steps to reproduce: > 1. Go to sfa component (https://demo-trunk.ofbiz.apache.org/sfa/control/main) > 2. Click on Lead link in submenu > (https://demo-trunk.ofbiz.apache.org/sfa/control/FindLeads) > 3. Apply filter and search Lead. > 4. Click ID link of any Lead > (https://demo-trunk.ofbiz.apache.org/sfa/control/viewprofile?roleTypeId=LEAD=DemoLead). > 5. Click on Profile link. > Profile page shows no information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9497) Profile link for Lead not working properly in sfa component
Aditya Sharma created OFBIZ-9497: Summary: Profile link for Lead not working properly in sfa component Key: OFBIZ-9497 URL: https://issues.apache.org/jira/browse/OFBIZ-9497 Project: OFBiz Issue Type: Bug Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Trivial Steps to reproduce: 1. Go to sfa component (https://demo-trunk.ofbiz.apache.org/sfa/control/main) 2. Click on Lead link in submenu (https://demo-trunk.ofbiz.apache.org/sfa/control/FindLeads) 3. Apply filter and search Lead. 4. Click ID link of any Lead (https://demo-trunk.ofbiz.apache.org/sfa/control/viewprofile?roleTypeId=LEAD=DemoLead). 5. Click on Profile link. Profile page shows no information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9494) Wrong repository links on FormWidgetExamples page
[ https://issues.apache.org/jira/browse/OFBIZ-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9494: - Affects Version/s: (was: Release Branch 15.12) (was: Release Branch 14.12) > Wrong repository links on FormWidgetExamples page > - > > Key: OFBIZ-9494 > URL: https://issues.apache.org/jira/browse/OFBIZ-9494 > Project: OFBiz > Issue Type: Bug > Components: example, exampleext >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-9494.patch > > > Steps to reproduce: > 1. Go to example component > (https://demo-trunk.ofbiz.apache.org/example/control/main) > 2. Click on Form Widget Examples > (https://demo-trunk.ofbiz.apache.org/example/control/FormWidgetExamples) > Links for the file plugins/example/widget/example/FormWidgetExampleForms.xml > are not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9497) Profile link for Lead not working properly in sfa component
[ https://issues.apache.org/jira/browse/OFBIZ-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9497: - Affects Version/s: Upcoming Release Trunk Release Branch 16.11 > Profile link for Lead not working properly in sfa component > --- > > Key: OFBIZ-9497 > URL: https://issues.apache.org/jira/browse/OFBIZ-9497 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, Upcoming Release, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-9497.patch, screenshot-1.png > > > Steps to reproduce: > 1. Go to sfa component (https://demo-trunk.ofbiz.apache.org/sfa/control/main) > 2. Click on Lead link in submenu > (https://demo-trunk.ofbiz.apache.org/sfa/control/FindLeads) > 3. Apply filter and search Lead. > 4. Click ID link of any Lead > (https://demo-trunk.ofbiz.apache.org/sfa/control/viewprofile?roleTypeId=LEAD=DemoLead). > 5. Click on Profile link. > Profile page shows no information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9497) Profile link for Lead not working properly in sfa component
[ https://issues.apache.org/jira/browse/OFBIZ-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9497: - Affects Version/s: Release Branch 14.12 Release Branch 15.12 > Profile link for Lead not working properly in sfa component > --- > > Key: OFBIZ-9497 > URL: https://issues.apache.org/jira/browse/OFBIZ-9497 > Project: OFBiz > Issue Type: Bug >Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12, > Upcoming Release, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-9497.patch, screenshot-1.png > > > Steps to reproduce: > 1. Go to sfa component (https://demo-trunk.ofbiz.apache.org/sfa/control/main) > 2. Click on Lead link in submenu > (https://demo-trunk.ofbiz.apache.org/sfa/control/FindLeads) > 3. Apply filter and search Lead. > 4. Click ID link of any Lead > (https://demo-trunk.ofbiz.apache.org/sfa/control/viewprofile?roleTypeId=LEAD=DemoLead). > 5. Click on Profile link. > Profile page shows no information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9497) Profile link for Lead not working properly in sfa component
[ https://issues.apache.org/jira/browse/OFBIZ-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9497: - Component/s: marketing > Profile link for Lead not working properly in sfa component > --- > > Key: OFBIZ-9497 > URL: https://issues.apache.org/jira/browse/OFBIZ-9497 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12, > Upcoming Release, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-9497.patch, screenshot-1.png > > > Steps to reproduce: > 1. Go to sfa component (https://demo-trunk.ofbiz.apache.org/sfa/control/main) > 2. Click on Lead link in submenu > (https://demo-trunk.ofbiz.apache.org/sfa/control/FindLeads) > 3. Apply filter and search Lead. > 4. Click ID link of any Lead > (https://demo-trunk.ofbiz.apache.org/sfa/control/viewprofile?roleTypeId=LEAD=DemoLead). > 5. Click on Profile link. > Profile page shows no information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9497) Profile link for Lead not working properly in sfa component
[ https://issues.apache.org/jira/browse/OFBIZ-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094632#comment-16094632 ] Aditya Sharma commented on OFBIZ-9497: -- Thanks [~pandeypranay] :) > Profile link for Lead not working properly in sfa component > --- > > Key: OFBIZ-9497 > URL: https://issues.apache.org/jira/browse/OFBIZ-9497 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Fix For: Upcoming Release > > Attachments: OFBIZ-9497.patch, screenshot-1.png > > > Steps to reproduce: > 1. Go to sfa component (https://demo-trunk.ofbiz.apache.org/sfa/control/main) > 2. Click on Lead link in submenu > (https://demo-trunk.ofbiz.apache.org/sfa/control/FindLeads) > 3. Apply filter and search Lead. > 4. Click ID link of any Lead > (https://demo-trunk.ofbiz.apache.org/sfa/control/viewprofile?roleTypeId=LEAD=DemoLead). > 5. Click on Profile link. > Profile page shows no information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9494) Wrong repository links on FormWidgetExamples page
[ https://issues.apache.org/jira/browse/OFBIZ-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094633#comment-16094633 ] Aditya Sharma commented on OFBIZ-9494: -- Thanks [~pandeypranay] :) > Wrong repository links on FormWidgetExamples page > - > > Key: OFBIZ-9494 > URL: https://issues.apache.org/jira/browse/OFBIZ-9494 > Project: OFBiz > Issue Type: Bug > Components: example, exampleext >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Fix For: Upcoming Release > > Attachments: OFBIZ-9494_16.patch, OFBIZ-9494.patch > > > Steps to reproduce: > 1. Go to example component > (https://demo-trunk.ofbiz.apache.org/example/control/main) > 2. Click on Form Widget Examples > (https://demo-trunk.ofbiz.apache.org/example/control/FormWidgetExamples) > Links for the file plugins/example/widget/example/FormWidgetExampleForms.xml > are not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9494) Wrong repository links on FormWidgetExamples page
[ https://issues.apache.org/jira/browse/OFBIZ-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9494: - Affects Version/s: Release Branch 14.12 Release Branch 15.12 > Wrong repository links on FormWidgetExamples page > - > > Key: OFBIZ-9494 > URL: https://issues.apache.org/jira/browse/OFBIZ-9494 > Project: OFBiz > Issue Type: Bug > Components: example, exampleext >Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12, > Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-9494.patch > > > Steps to reproduce: > 1. Go to example component > (https://demo-trunk.ofbiz.apache.org/example/control/main) > 2. Click on Form Widget Examples > (https://demo-trunk.ofbiz.apache.org/example/control/FormWidgetExamples) > Links for the file plugins/example/widget/example/FormWidgetExampleForms.xml > are not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9494) Wrong repository links on FormWidgetExamples page
[ https://issues.apache.org/jira/browse/OFBIZ-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9494: - Attachment: OFBIZ-9424_16.patch Patch specific to OFBiz16.11. > Wrong repository links on FormWidgetExamples page > - > > Key: OFBIZ-9494 > URL: https://issues.apache.org/jira/browse/OFBIZ-9494 > Project: OFBiz > Issue Type: Bug > Components: example, exampleext >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-9494.patch > > > Steps to reproduce: > 1. Go to example component > (https://demo-trunk.ofbiz.apache.org/example/control/main) > 2. Click on Form Widget Examples > (https://demo-trunk.ofbiz.apache.org/example/control/FormWidgetExamples) > Links for the file plugins/example/widget/example/FormWidgetExampleForms.xml > are not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9494) Wrong repository links on FormWidgetExamples page
[ https://issues.apache.org/jira/browse/OFBIZ-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9494: - Attachment: OFBIZ-9494_16.patch > Wrong repository links on FormWidgetExamples page > - > > Key: OFBIZ-9494 > URL: https://issues.apache.org/jira/browse/OFBIZ-9494 > Project: OFBiz > Issue Type: Bug > Components: example, exampleext >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-9494_16.patch, OFBIZ-9494.patch > > > Steps to reproduce: > 1. Go to example component > (https://demo-trunk.ofbiz.apache.org/example/control/main) > 2. Click on Form Widget Examples > (https://demo-trunk.ofbiz.apache.org/example/control/FormWidgetExamples) > Links for the file plugins/example/widget/example/FormWidgetExampleForms.xml > are not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9494) Wrong repository links on FormWidgetExamples page
[ https://issues.apache.org/jira/browse/OFBIZ-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9494: - Attachment: (was: OFBIZ-9424_16.patch) > Wrong repository links on FormWidgetExamples page > - > > Key: OFBIZ-9494 > URL: https://issues.apache.org/jira/browse/OFBIZ-9494 > Project: OFBiz > Issue Type: Bug > Components: example, exampleext >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-9494.patch > > > Steps to reproduce: > 1. Go to example component > (https://demo-trunk.ofbiz.apache.org/example/control/main) > 2. Click on Form Widget Examples > (https://demo-trunk.ofbiz.apache.org/example/control/FormWidgetExamples) > Links for the file plugins/example/widget/example/FormWidgetExampleForms.xml > are not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9494) Wrong repository links on FormWidgetExamples page
[ https://issues.apache.org/jira/browse/OFBIZ-9494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9494: - Affects Version/s: Trunk Release Branch 16.11 > Wrong repository links on FormWidgetExamples page > - > > Key: OFBIZ-9494 > URL: https://issues.apache.org/jira/browse/OFBIZ-9494 > Project: OFBiz > Issue Type: Bug > Components: example, exampleext >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Pranay Pandey >Priority: Trivial > Attachments: OFBIZ-9494.patch > > > Steps to reproduce: > 1. Go to example component > (https://demo-trunk.ofbiz.apache.org/example/control/main) > 2. Click on Form Widget Examples > (https://demo-trunk.ofbiz.apache.org/example/control/FormWidgetExamples) > Links for the file plugins/example/widget/example/FormWidgetExampleForms.xml > are not working. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9503) Fixed Asset Id field is below update button on EditInventoryItem page
[ https://issues.apache.org/jira/browse/OFBIZ-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9503: - Summary: Fixed Asset Id field is below update button on EditInventoryItem page (was: Fixed Asset Id is below update button on EditInventoryItem page) > Fixed Asset Id field is below update button on EditInventoryItem page > - > > Key: OFBIZ-9503 > URL: https://issues.apache.org/jira/browse/OFBIZ-9503 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Trivial > > Steps to reproduce: > 1. Go to Facility component > (https://demo-trunk.ofbiz.apache.org/facility/control/main) > 2. Select facility and click on submit button > (https://demo-trunk.ofbiz.apache.org/facility/control/EditFacility) > 3. Click on Inventory item in sub menu > (https://demo-trunk.ofbiz.apache.org/facility/control/EditFacilityInventoryItems?facilityId=WebStoreWarehouse) > 4. Click on id link of any inventory item > (https://demo-trunk.ofbiz.apache.org/facility/control/EditInventoryItem?inventoryItemId=9003=WebStoreWarehouse) > Fixed Asset Id field is below Update button -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9503) Fixed Asset Id is below update button on EditInventoryItem page
Aditya Sharma created OFBIZ-9503: Summary: Fixed Asset Id is below update button on EditInventoryItem page Key: OFBIZ-9503 URL: https://issues.apache.org/jira/browse/OFBIZ-9503 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Release Branch 16.11, Trunk Reporter: Aditya Sharma Assignee: Aditya Sharma Priority: Trivial Steps to reproduce: 1. Go to Facility component (https://demo-trunk.ofbiz.apache.org/facility/control/main) 2. Select facility and click on submit button (https://demo-trunk.ofbiz.apache.org/facility/control/EditFacility) 3. Click on Inventory item in sub menu (https://demo-trunk.ofbiz.apache.org/facility/control/EditFacilityInventoryItems?facilityId=WebStoreWarehouse) 4. Click on id link of any inventory item (https://demo-trunk.ofbiz.apache.org/facility/control/EditInventoryItem?inventoryItemId=9003=WebStoreWarehouse) Fixed Asset Id field is below Update button -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9519) User should be notified with success message on Update Quote page
Aditya Sharma created OFBIZ-9519: Summary: User should be notified with success message on Update Quote page Key: OFBIZ-9519 URL: https://issues.apache.org/jira/browse/OFBIZ-9519 Project: OFBiz Issue Type: Sub-task Components: order Affects Versions: Trunk Reporter: Aditya Sharma Assignee: Sonal Patwari Priority: Minor Steps to regenerate: 1. Go to Order component (https://localhost:8443/ordermgr/control/main) 2. Click on Quotes submenu (directing to https://localhost:8443/ordermgr/control/FindQuote) 3. Click on Find button. 4. Click on any quoteId (directing to https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001) 5. Click on Quote link from the submenu (https://localhost:8443/ordermgr/control/EditQuote?quoteId=CQ0001) 6. Make changes and Click on Submit button. No success message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9329) User should be notified with success message on successful completion of any action
[ https://issues.apache.org/jira/browse/OFBIZ-9329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-9329: - Description: On performing any action, user should be notified with the success message if the action has been performed successfully. Listing actions with no alert messages delivered on success and will be creating sub-tickets for the same. Ecommerce: 1. Subscribe to Newsletter: OFBIZ-9320 2. Add to Cart: 3. Create/Update Shopping List: 4. Last Categories > Clear: Order Manager: 1. Update Quote: OFBIZ-9519 2. remove Quote Role: 3. Send Report by Mail from View Quote: OFBIZ-9321 was: On performing any action, user should be notified with the success message if the action has been performed successfully. Listing actions with no alert messages delivered on success and will be creating sub-tickets for the same. Ecommerce: 1. Subscribe to Newsletter: OFBIZ-9320 2. Add to Cart: 3. Create/Update Shopping List: 4. Last Categories > Clear: Order Manager: 1. Update Quote: 2. remove Quote Role: 3. Send Report by Mail from View Quote: OFBIZ-9321 > User should be notified with success message on successful completion of any > action > --- > > Key: OFBIZ-9329 > URL: https://issues.apache.org/jira/browse/OFBIZ-9329 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Release Branch 16.11 >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > > On performing any action, user should be notified with the success message if > the action has been performed successfully. > Listing actions with no alert messages delivered on success and will be > creating sub-tickets for the same. > Ecommerce: > 1. Subscribe to Newsletter: OFBIZ-9320 > 2. Add to Cart: > 3. Create/Update Shopping List: > 4. Last Categories > Clear: > Order Manager: > 1. Update Quote: OFBIZ-9519 > 2. remove Quote Role: > 3. Send Report by Mail from View Quote: OFBIZ-9321 > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
