[jira] [Commented] (OFBIZ-7945) Webpos Keyboard Shortcut keys does not work correctly
[ https://issues.apache.org/jira/browse/OFBIZ-7945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410487#comment-15410487 ] Vishal Chhabria commented on OFBIZ-7945: Will provide patch for it soon. > Webpos Keyboard Shortcut keys does not work correctly > - > > Key: OFBIZ-7945 > URL: https://issues.apache.org/jira/browse/OFBIZ-7945 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/webpos >Reporter: Vishal Chhabria >Priority: Trivial > > Keyboard shortcut keys doesn't work properly in web pos - > e.g > 1) Clicking on F11(Subtract Quantity) removes all items from the cart. > 2) Clicking on F10 (Add Quantity) decreases the quantity of the item. > And this unexpected behaviour can be found in some other keys as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7945) Webpos Keyboard Shortcut keys does not work correctly
Vishal Chhabria created OFBIZ-7945: -- Summary: Webpos Keyboard Shortcut keys does not work correctly Key: OFBIZ-7945 URL: https://issues.apache.org/jira/browse/OFBIZ-7945 Project: OFBiz Issue Type: Bug Components: specialpurpose/webpos Reporter: Vishal Chhabria Priority: Trivial Keyboard shortcut keys doesn't work properly in web pos - e.g 1) Clicking on F11(Subtract Quantity) removes all items from the cart. 2) Clicking on F10 (Add Quantity) decreases the quantity of the item. And this unexpected behaviour can be found in some other keys as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7719) Not able to select Vitrual Product in WebPos
[ https://issues.apache.org/jira/browse/OFBIZ-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7719: --- Attachment: OFBIZ-7719.patch Used jquery().val() instead of .update() method to set values in variant selection box. > Not able to select Vitrual Product in WebPos > > > Key: OFBIZ-7719 > URL: https://issues.apache.org/jira/browse/OFBIZ-7719 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/webpos >Reporter: Vishal Chhabria > Attachments: OFBIZ-7719.patch > > > Following JS error occurs on selecting virtual product in WebPos: > Uncaught TypeError: jQuery(...).update is not a function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7719) Not able to select Vitrual Product in WebPos
[ https://issues.apache.org/jira/browse/OFBIZ-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7719: --- Description: Following JS error occurs on selecting virtual product in WebPos: Uncaught TypeError: jQuery(...).update is not a function > Not able to select Vitrual Product in WebPos > > > Key: OFBIZ-7719 > URL: https://issues.apache.org/jira/browse/OFBIZ-7719 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/webpos >Reporter: Vishal Chhabria > > Following JS error occurs on selecting virtual product in WebPos: > Uncaught TypeError: jQuery(...).update is not a function -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7719) Not able to select Vitrual Product in WebPos
Vishal Chhabria created OFBIZ-7719: -- Summary: Not able to select Vitrual Product in WebPos Key: OFBIZ-7719 URL: https://issues.apache.org/jira/browse/OFBIZ-7719 Project: OFBiz Issue Type: Bug Components: specialpurpose/webpos Reporter: Vishal Chhabria -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7709) Party Search doesn't consider Billing Addres and Shipping Address checkbox in WebPos
[ https://issues.apache.org/jira/browse/OFBIZ-7709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7709: --- Attachment: OFBIZ-7709.patch This Issue was use of incorrect method to check value of checkboxes. > Party Search doesn't consider Billing Addres and Shipping Address checkbox in > WebPos > - > > Key: OFBIZ-7709 > URL: https://issues.apache.org/jira/browse/OFBIZ-7709 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/webpos >Reporter: Vishal Chhabria > Attachments: OFBIZ-7709.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7709) Party Search doesn't consider Billing Addres and Shipping Address checkbox in WebPos
Vishal Chhabria created OFBIZ-7709: -- Summary: Party Search doesn't consider Billing Addres and Shipping Address checkbox in WebPos Key: OFBIZ-7709 URL: https://issues.apache.org/jira/browse/OFBIZ-7709 Project: OFBiz Issue Type: Bug Components: specialpurpose/webpos Reporter: Vishal Chhabria -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7457) Ebay store account throws Unwanted Exception
[ https://issues.apache.org/jira/browse/OFBIZ-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7457: --- Summary: Ebay store account throws Unwanted Exception (was: Ebay store account throws ) > Ebay store account throws Unwanted Exception > > > Key: OFBIZ-7457 > URL: https://issues.apache.org/jira/browse/OFBIZ-7457 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria > > Steps to regenerate - > 1) Go to /ebaystore/control/main > 2) Select any account and click on submit. > Following error occurs on submit - > ERROR rendering error page [/error/error.jsp], but here is the error text: > org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen > [component://ebaystore/widget/EbayAccountScreens.xml#EbayPersonalInformation]: > java.lang.IllegalArgumentException: Error calling service with name > getEbayUser: org.ofbiz.service.GenericServiceException: Service [getEbayUser] > target threw an unexpected exception (org/apache/log4j/SimpleLayout) (Error > calling service with name getEbayUser: > org.ofbiz.service.GenericServiceException: Service [getEbayUser] target threw > an unexpected exception (org/apache/log4j/SimpleLayout)) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7457) Ebay store account throws Exception
[ https://issues.apache.org/jira/browse/OFBIZ-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7457: --- Summary: Ebay store account throws Exception (was: Ebay store account throws Unwanted Exception) > Ebay store account throws Exception > --- > > Key: OFBIZ-7457 > URL: https://issues.apache.org/jira/browse/OFBIZ-7457 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria > > Steps to regenerate - > 1) Go to /ebaystore/control/main > 2) Select any account and click on submit. > Following error occurs on submit - > ERROR rendering error page [/error/error.jsp], but here is the error text: > org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen > [component://ebaystore/widget/EbayAccountScreens.xml#EbayPersonalInformation]: > java.lang.IllegalArgumentException: Error calling service with name > getEbayUser: org.ofbiz.service.GenericServiceException: Service [getEbayUser] > target threw an unexpected exception (org/apache/log4j/SimpleLayout) (Error > calling service with name getEbayUser: > org.ofbiz.service.GenericServiceException: Service [getEbayUser] target threw > an unexpected exception (org/apache/log4j/SimpleLayout)) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7457) Ebay store account throws
Vishal Chhabria created OFBIZ-7457: -- Summary: Ebay store account throws Key: OFBIZ-7457 URL: https://issues.apache.org/jira/browse/OFBIZ-7457 Project: OFBiz Issue Type: Bug Reporter: Vishal Chhabria Steps to regenerate - 1) Go to /ebaystore/control/main 2) Select any account and click on submit. Following error occurs on submit - ERROR rendering error page [/error/error.jsp], but here is the error text: org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen [component://ebaystore/widget/EbayAccountScreens.xml#EbayPersonalInformation]: java.lang.IllegalArgumentException: Error calling service with name getEbayUser: org.ofbiz.service.GenericServiceException: Service [getEbayUser] target threw an unexpected exception (org/apache/log4j/SimpleLayout) (Error calling service with name getEbayUser: org.ofbiz.service.GenericServiceException: Service [getEbayUser] target threw an unexpected exception (org/apache/log4j/SimpleLayout)) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7451) Update Blog summary throws database exception when characters exceeds more than 255 characters
[ https://issues.apache.org/jira/browse/OFBIZ-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337818#comment-15337818 ] Vishal Chhabria commented on OFBIZ-7451: I think, there should be validation check at service or ui level to restrict summary length to 255 characters. > Update Blog summary throws database exception when characters exceeds more > than 255 characters > -- > > Key: OFBIZ-7451 > URL: https://issues.apache.org/jira/browse/OFBIZ-7451 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7451) Update Blog summary throws database exception when characters exceeds more than 255 characters
Vishal Chhabria created OFBIZ-7451: -- Summary: Update Blog summary throws database exception when characters exceeds more than 255 characters Key: OFBIZ-7451 URL: https://issues.apache.org/jira/browse/OFBIZ-7451 Project: OFBiz Issue Type: Bug Reporter: Vishal Chhabria -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7435) Create Custreq from CommEvent shows error on screen
[ https://issues.apache.org/jira/browse/OFBIZ-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7435: --- Attachment: OFBIZ-7435.patch Updated Path of groovy script. > Create Custreq from CommEvent shows error on screen > --- > > Key: OFBIZ-7435 > URL: https://issues.apache.org/jira/browse/OFBIZ-7435 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria > Attachments: OFBIZ-7435.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7435) Create Custreq from CommEvent shows error on screen
Vishal Chhabria created OFBIZ-7435: -- Summary: Create Custreq from CommEvent shows error on screen Key: OFBIZ-7435 URL: https://issues.apache.org/jira/browse/OFBIZ-7435 Project: OFBiz Issue Type: Bug Reporter: Vishal Chhabria -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7407) Hovering over logo section show layout setttings markup in Tomahawk theme
[ https://issues.apache.org/jira/browse/OFBIZ-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337633#comment-15337633 ] Vishal Chhabria edited comment on OFBIZ-7407 at 6/18/16 7:36 AM: - Display companyName instead of layout setting markup. was (Author: vishal.chhabria): Display companyName on title of ofbiz section. > Hovering over logo section show layout setttings markup in Tomahawk theme > - > > Key: OFBIZ-7407 > URL: https://issues.apache.org/jira/browse/OFBIZ-7407 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria >Priority: Minor > Attachments: OFBIZ-7407.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7407) Hovering over logo section show layout setttings markup in Tomahawk theme
[ https://issues.apache.org/jira/browse/OFBIZ-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7407: --- Attachment: OFBIZ-7407.patch Display companyName on title of ofbiz section. > Hovering over logo section show layout setttings markup in Tomahawk theme > - > > Key: OFBIZ-7407 > URL: https://issues.apache.org/jira/browse/OFBIZ-7407 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria >Priority: Minor > Attachments: OFBIZ-7407.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7407) Hovering over logo section show layout setttings markup in Tomahawk theme
[ https://issues.apache.org/jira/browse/OFBIZ-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7407: --- Summary: Hovering over logo section show layout setttings markup in Tomahawk theme (was: Hovering over logo section show layout setttings markup in tomahawk theme) > Hovering over logo section show layout setttings markup in Tomahawk theme > - > > Key: OFBIZ-7407 > URL: https://issues.apache.org/jira/browse/OFBIZ-7407 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7407) Hovering over logo section show layout setttings markup in tomahawk theme
[ https://issues.apache.org/jira/browse/OFBIZ-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7407: --- Summary: Hovering over logo section show layout setttings markup in tomahawk theme (was: Hovering over logo section show layout setttings markeup in tomahawk theme) > Hovering over logo section show layout setttings markup in tomahawk theme > - > > Key: OFBIZ-7407 > URL: https://issues.apache.org/jira/browse/OFBIZ-7407 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7407) Hovering over logo section show layout setttings markeup in tomahawk theme
Vishal Chhabria created OFBIZ-7407: -- Summary: Hovering over logo section show layout setttings markeup in tomahawk theme Key: OFBIZ-7407 URL: https://issues.apache.org/jira/browse/OFBIZ-7407 Project: OFBiz Issue Type: Bug Reporter: Vishal Chhabria Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7328) Promotion is applied multiple times in case of Order Flat Amount action
[ https://issues.apache.org/jira/browse/OFBIZ-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7328: --- Description: Steps to regenerate - Create a promotion with condition - > cart subtotal greater than equal to zero. action - > Order Amount Flat - 10 Expected - 10 $ should be deducted from cart. Actual - Promotion keeps on applying unless cart amount reaches 0 > Promotion is applied multiple times in case of Order Flat Amount action > --- > > Key: OFBIZ-7328 > URL: https://issues.apache.org/jira/browse/OFBIZ-7328 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria > > Steps to regenerate - > Create a promotion with > condition - > cart subtotal greater than equal to zero. > action - > Order Amount Flat - 10 > Expected - 10 $ should be deducted from cart. > Actual - Promotion keeps on applying unless cart amount reaches 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7328) Order Flat Amount action is applied multiple times in promotion
Vishal Chhabria created OFBIZ-7328: -- Summary: Order Flat Amount action is applied multiple times in promotion Key: OFBIZ-7328 URL: https://issues.apache.org/jira/browse/OFBIZ-7328 Project: OFBiz Issue Type: Bug Reporter: Vishal Chhabria -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7328) Promotion is applied multiple times in case of Order Flat Amount action
[ https://issues.apache.org/jira/browse/OFBIZ-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7328: --- Summary: Promotion is applied multiple times in case of Order Flat Amount action (was: Order Flat Amount action is applied multiple times in promotion) > Promotion is applied multiple times in case of Order Flat Amount action > --- > > Key: OFBIZ-7328 > URL: https://issues.apache.org/jira/browse/OFBIZ-7328 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine
[ https://issues.apache.org/jira/browse/OFBIZ-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7008: --- Attachment: OFBIZ-7008.patch Updated productPromoId. > Support to add condition for Geo Location in Promo Engine > - > > Key: OFBIZ-7008 > URL: https://issues.apache.org/jira/browse/OFBIZ-7008 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Trunk >Reporter: Vishal Chhabria >Assignee: Mridul Pathak >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-7008.patch, OFBIZ-7008.patch, OFBIZ-7008.patch, > OFBIZ-7008.patch, SampleData.xml > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7294) Quick Init Datawarehouse link on BI Application does not work
[ https://issues.apache.org/jira/browse/OFBIZ-7294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria closed OFBIZ-7294. -- Resolution: Invalid Not an issue, it calls quickInitDatawarehouse service and updates the data. > Quick Init Datawarehouse link on BI Application does not work > - > > Key: OFBIZ-7294 > URL: https://issues.apache.org/jira/browse/OFBIZ-7294 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria > > Clicking on "Quick Init Datawarehouse" link on BI -> Quick Start Guide > section redericts user to the same page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7294) Quick Init Datawarehouse link on BI Application does not work
[ https://issues.apache.org/jira/browse/OFBIZ-7294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7294: --- Description: Clicking on "Quick Init Datawarehouse" link on BI -> Quick Start Guide section redericts user to the same page. > Quick Init Datawarehouse link on BI Application does not work > - > > Key: OFBIZ-7294 > URL: https://issues.apache.org/jira/browse/OFBIZ-7294 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria > > Clicking on "Quick Init Datawarehouse" link on BI -> Quick Start Guide > section redericts user to the same page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7294) Quick Init Datawarehouse link on BI Application does not work
[ https://issues.apache.org/jira/browse/OFBIZ-7294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7294: --- Summary: Quick Init Datawarehouse link on BI Application does not work (was: Quick Init Datawarehouse link on BI Application does not redirect user to service engine) > Quick Init Datawarehouse link on BI Application does not work > - > > Key: OFBIZ-7294 > URL: https://issues.apache.org/jira/browse/OFBIZ-7294 > Project: OFBiz > Issue Type: Bug >Reporter: Vishal Chhabria > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7294) Quick Init Datawarehouse link on BI Application does not redirect user to service engine
Vishal Chhabria created OFBIZ-7294: -- Summary: Quick Init Datawarehouse link on BI Application does not redirect user to service engine Key: OFBIZ-7294 URL: https://issues.apache.org/jira/browse/OFBIZ-7294 Project: OFBiz Issue Type: Bug Reporter: Vishal Chhabria -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine
[ https://issues.apache.org/jira/browse/OFBIZ-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7008: --- Attachment: OFBIZ-7008.patch Updated patch with proper productPromoRuleId which caused the errors while loading data. > Support to add condition for Geo Location in Promo Engine > - > > Key: OFBIZ-7008 > URL: https://issues.apache.org/jira/browse/OFBIZ-7008 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Trunk >Reporter: Vishal Chhabria >Assignee: Mridul Pathak >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-7008.patch, OFBIZ-7008.patch, OFBIZ-7008.patch, > SampleData.xml > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine
[ https://issues.apache.org/jira/browse/OFBIZ-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303783#comment-15303783 ] Vishal Chhabria commented on OFBIZ-7008: [~mridul.pathak] I am on it. I will fix the tests and provide the updated patch. > Support to add condition for Geo Location in Promo Engine > - > > Key: OFBIZ-7008 > URL: https://issues.apache.org/jira/browse/OFBIZ-7008 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Trunk >Reporter: Vishal Chhabria >Assignee: Mridul Pathak >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-7008.patch, OFBIZ-7008.patch, SampleData.xml > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine
[ https://issues.apache.org/jira/browse/OFBIZ-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244154#comment-15244154 ] Vishal Chhabria commented on OFBIZ-7008: Attached the updated patch with demo data. Also, made some improvements in code. Steps to test - For Promotion "Free Shipping in Utah state". 1) Upload sample data attached with the ticket. 2) Add items to cart either form ecommerce or ordermgr. 3) In the check process select/add shipping address with state as UT. Discount should be applied with amount equal to shipping cost. > Support to add condition for Geo Location in Promo Engine > - > > Key: OFBIZ-7008 > URL: https://issues.apache.org/jira/browse/OFBIZ-7008 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Assignee: Mridul Pathak >Priority: Trivial > Attachments: OFBIZ-7008.patch, OFBIZ-7008.patch, SampleData.xml > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine
[ https://issues.apache.org/jira/browse/OFBIZ-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7008: --- Attachment: OFBIZ-7008.patch > Support to add condition for Geo Location in Promo Engine > - > > Key: OFBIZ-7008 > URL: https://issues.apache.org/jira/browse/OFBIZ-7008 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Assignee: Mridul Pathak >Priority: Trivial > Attachments: OFBIZ-7008.patch, OFBIZ-7008.patch, SampleData.xml > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine
[ https://issues.apache.org/jira/browse/OFBIZ-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7008: --- Attachment: SampleData.xml Attached sample data for promotion 'Free Shipping in Utah state'. > Support to add condition for Geo Location in Promo Engine > - > > Key: OFBIZ-7008 > URL: https://issues.apache.org/jira/browse/OFBIZ-7008 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Assignee: Mridul Pathak >Priority: Trivial > Attachments: OFBIZ-7008.patch, SampleData.xml > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine
[ https://issues.apache.org/jira/browse/OFBIZ-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244117#comment-15244117 ] Vishal Chhabria commented on OFBIZ-7008: Working on sample data for this feature. I will attach the sample data and provide steps to test it. > Support to add condition for Geo Location in Promo Engine > - > > Key: OFBIZ-7008 > URL: https://issues.apache.org/jira/browse/OFBIZ-7008 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Priority: Trivial > Attachments: OFBIZ-7008.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine
[ https://issues.apache.org/jira/browse/OFBIZ-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-7008: --- Attachment: OFBIZ-7008.patch Attached patch for the feature. > Support to add condition for Geo Location in Promo Engine > - > > Key: OFBIZ-7008 > URL: https://issues.apache.org/jira/browse/OFBIZ-7008 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Priority: Trivial > Attachments: OFBIZ-7008.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7008) Support to add condition for Geo Location in Promo Engine
Vishal Chhabria created OFBIZ-7008: -- Summary: Support to add condition for Geo Location in Promo Engine Key: OFBIZ-7008 URL: https://issues.apache.org/jira/browse/OFBIZ-7008 Project: OFBiz Issue Type: New Feature Reporter: Vishal Chhabria Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6940) New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in ProductStoreShipmentMeth entity
[ https://issues.apache.org/jira/browse/OFBIZ-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-6940: --- Attachment: (was: OFBIZ-6685.patch) > New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in > ProductStoreShipmentMeth entity > - > > Key: OFBIZ-6940 > URL: https://issues.apache.org/jira/browse/OFBIZ-6940 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Priority: Trivial > > New price type "SHIPPING_ALLOWANCE" can be used in the scenarios where > default/list prices are comprehensive of the 'Shipping Cost' quota, this > price type can help user to set the Shipping Allowance cost he has included > in the the product's default/list price and then modify actual shipping cost > by reducing the allowance cost from it. > minimumPrice field can be used to set the the lowest rate for a particular > shipping type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6940) New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in ProductStoreShipmentMeth entity
[ https://issues.apache.org/jira/browse/OFBIZ-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-6940: --- Attachment: OFBIZ-6685.patch Attached the patch for Shipping Allowance implementation. Details - 1) Updated ShippingEstimateWrapper constructor to calculate the total allowance amount for all the products in a particular Shipgroup. 2) Change loadEstimates() signature to loadEstimates(BigDecimal totalAllowance) to accept the total allowance of a shipgroup. 3) Modified ShippingEvents.getShipGroupEstimate() method to reduce the shippingAllowance amount from actual Shipping Cost. Also, made changes to check if the totalShipping is greater than minimumPrice for a particular shipping option. > New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in > ProductStoreShipmentMeth entity > - > > Key: OFBIZ-6940 > URL: https://issues.apache.org/jira/browse/OFBIZ-6940 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Priority: Trivial > Attachments: OFBIZ-6685.patch > > > New price type "SHIPPING_ALLOWANCE" can be used in the scenarios where > default/list prices are comprehensive of the 'Shipping Cost' quota, this > price type can help user to set the Shipping Allowance cost he has included > in the the product's default/list price and then modify actual shipping cost > by reducing the allowance cost from it. > minimumPrice field can be used to set the the lowest rate for a particular > shipping type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6940) New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in ProductStoreShipmentMeth entity
[ https://issues.apache.org/jira/browse/OFBIZ-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-6940: --- Attachment: OFBIZ-6940.patch > New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in > ProductStoreShipmentMeth entity > - > > Key: OFBIZ-6940 > URL: https://issues.apache.org/jira/browse/OFBIZ-6940 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Priority: Trivial > Attachments: OFBIZ-6940.patch > > > New price type "SHIPPING_ALLOWANCE" can be used in the scenarios where > default/list prices are comprehensive of the 'Shipping Cost' quota, this > price type can help user to set the Shipping Allowance cost he has included > in the the product's default/list price and then modify actual shipping cost > by reducing the allowance cost from it. > minimumPrice field can be used to set the the lowest rate for a particular > shipping type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6940) New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in ProductStoreShipmentMeth entity
[ https://issues.apache.org/jira/browse/OFBIZ-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201247#comment-15201247 ] Vishal Chhabria commented on OFBIZ-6940: Uploaded correct patch, thanks [~jacopoc] for pointing it out. > New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in > ProductStoreShipmentMeth entity > - > > Key: OFBIZ-6940 > URL: https://issues.apache.org/jira/browse/OFBIZ-6940 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Priority: Trivial > Attachments: OFBIZ-6940.patch > > > New price type "SHIPPING_ALLOWANCE" can be used in the scenarios where > default/list prices are comprehensive of the 'Shipping Cost' quota, this > price type can help user to set the Shipping Allowance cost he has included > in the the product's default/list price and then modify actual shipping cost > by reducing the allowance cost from it. > minimumPrice field can be used to set the the lowest rate for a particular > shipping type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6940) New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in ProductStoreShipmentMeth entity
[ https://issues.apache.org/jira/browse/OFBIZ-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-6940: --- Description: New price type "SHIPPING_ALLOWANCE" can be used in the scenarios where default/list prices are comprehensive of the 'Shipping Cost' quota, this price type can help user to set the Shipping Allowance cost he has included in the the product's default/list price and then modify actual shipping cost by reducing the allowance cost from it. minimumPrice field can be used to set the the lowest rate for a particular shipping type. > New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in > ProductStoreShipmentMeth entity > - > > Key: OFBIZ-6940 > URL: https://issues.apache.org/jira/browse/OFBIZ-6940 > Project: OFBiz > Issue Type: New Feature >Reporter: Vishal Chhabria >Priority: Trivial > > New price type "SHIPPING_ALLOWANCE" can be used in the scenarios where > default/list prices are comprehensive of the 'Shipping Cost' quota, this > price type can help user to set the Shipping Allowance cost he has included > in the the product's default/list price and then modify actual shipping cost > by reducing the allowance cost from it. > minimumPrice field can be used to set the the lowest rate for a particular > shipping type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6940) New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in ProductStoreShipmentMeth entity
Vishal Chhabria created OFBIZ-6940: -- Summary: New ProductPriceType 'SHIPPING_ALLOWANCE' and a new minimumPrice field in ProductStoreShipmentMeth entity Key: OFBIZ-6940 URL: https://issues.apache.org/jira/browse/OFBIZ-6940 Project: OFBiz Issue Type: New Feature Reporter: Vishal Chhabria Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6685) changeProductionRunStatus service does not honor the StatusValidChange
[ https://issues.apache.org/jira/browse/OFBIZ-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103059#comment-15103059 ] Vishal Chhabria edited comment on OFBIZ-6685 at 1/16/16 8:00 AM: - [~deepakdixit] I think few improvements are need in your patch. Update the patch with following changes - 1) Passed statusId 'PRUN_DOC_PRINTED' as hidden paramater when user 'Confirm' any Production Run. Currently, no statusId is passed and service returns error when we Confirm Production Run. 2) Set statusId as mandatory parameter for the service as no record is found for ValidStatusChange with StatusId="null", service will always return error if no statusId is passed so IMO statusId should be mandatory in that case. 3) Changed request-name 'changeProductionRunStatusToPrinted' to changeProductionRunStatus to make it generic and can be called from anywhere to change the production run status, also removed request changeProductionRunStatusToClosed as I do not find this request being called from anywhere. 4) Added data for ValidStatusChange. was (Author: vishal.chhabria): [~deepakdixit] I think few improvement as required in your patch, I have update the patch with following changes - 1) Passed statusId 'PRUN_DOC_PRINTED' as hidden paramater when user 'Confirm' any Production Run. Currently, no statusId is passed and service returns error when we Confirm Production Run. 2) Set statusId as mandatory parameter for the service as no record is found for ValidStatusChange with StatusId="null", service will always return error if no statusId is passed so IMO statusId should be mandatory in that case. 3) Changed request-name 'changeProductionRunStatusToPrinted' to changeProductionRunStatus to make it generic and can be called from anywhere to change the production run status, also removed request changeProductionRunStatusToClosed as I do not find this request being called from anywhere. 4) Added data for ValidStatusChange. > changeProductionRunStatus service does not honor the StatusValidChange > --- > > Key: OFBIZ-6685 > URL: https://issues.apache.org/jira/browse/OFBIZ-6685 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Attachments: OFBIZ-6685.patch, OFBIZ-6685.patch > > > As per current implementation changeProductionRunStatus does not honor the > StatusValidChange, There are hard coded check in changeProductionRunStatus > service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6685) changeProductionRunStatus service does not honor the StatusValidChange
[ https://issues.apache.org/jira/browse/OFBIZ-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103059#comment-15103059 ] Vishal Chhabria edited comment on OFBIZ-6685 at 1/16/16 7:59 AM: - [~deepakdixit] I think few improvement as required in your patch, I have update the patch with following changes - 1) Passed statusId 'PRUN_DOC_PRINTED' as hidden paramater when user 'Confirm' any Production Run. Currently, no statusId is passed and service returns error when we Confirm Production Run. 2) Set statusId as mandatory parameter for the service as no record is found for ValidStatusChange with StatusId="null", service will always return error if no statusId is passed so IMO statusId should be mandatory in that case. 3) Changed request-name 'changeProductionRunStatusToPrinted' to changeProductionRunStatus to make it generic and can be called from anywhere to change the production run status, also removed request changeProductionRunStatusToClosed as I do not find this request being called from anywhere. 4) Added data for ValidStatusChange. was (Author: vishal.chhabria): [~deepakdixit] I have attached a patch with below mentioned improvements - 1) Passed statusId 'PRUN_DOC_PRINTED' as hidden paramater when user 'Confirm' any Production Run. Currently, no statusId is passed and service returns error when we Confirm Production Run. 2) Set statusId as mandatory parameter for the service as no record is found for ValidStatusChange with StatusId="null", service will always return error if no statusId is passed so IMO statusId should be mandatory in that case. 3) Changed request-name 'changeProductionRunStatusToPrinted' to changeProductionRunStatus to make it generic and can be called from anywhere to change the production run status, also removed request changeProductionRunStatusToClosed as I do not find this request being called from anywhere. 4) Added data for ValidStatusChange. > changeProductionRunStatus service does not honor the StatusValidChange > --- > > Key: OFBIZ-6685 > URL: https://issues.apache.org/jira/browse/OFBIZ-6685 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Attachments: OFBIZ-6685.patch, OFBIZ-6685.patch > > > As per current implementation changeProductionRunStatus does not honor the > StatusValidChange, There are hard coded check in changeProductionRunStatus > service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6685) changeProductionRunStatus service does not honor the StatusValidChange
[ https://issues.apache.org/jira/browse/OFBIZ-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Chhabria updated OFBIZ-6685: --- Attachment: OFBIZ-6685.patch [~deepakdixit] I have attached a patch with below mentioned improvements - 1) Passed statusId 'PRUN_DOC_PRINTED' as hidden paramater when user 'Confirm' any Production Run. Currently, no statusId is passed and service returns error when we Confirm Production Run. 2) Set statusId as mandatory parameter for the service as no record is found for ValidStatusChange with StatusId="null", service will always return error if no statusId is passed so IMO statusId should be mandatory in that case. 3) Changed request-name 'changeProductionRunStatusToPrinted' to changeProductionRunStatus to make it generic and can be called from anywhere to change the production run status, also removed request changeProductionRunStatusToClosed as I do not find this request being called from anywhere. 4) Added data for ValidStatusChange. > changeProductionRunStatus service does not honor the StatusValidChange > --- > > Key: OFBIZ-6685 > URL: https://issues.apache.org/jira/browse/OFBIZ-6685 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Attachments: OFBIZ-6685.patch, OFBIZ-6685.patch > > > As per current implementation changeProductionRunStatus does not honor the > StatusValidChange, There are hard coded check in changeProductionRunStatus > service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6708) Missing userLogin error on party profile screen when 1st content is non public
[
https://issues.apache.org/jira/browse/OFBIZ-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Chhabria updated OFBIZ-6708:
---
Attachment: OFBIZ-6708.patch
Here is the patch for the reported issue.
I digged around this issue and found that request used to render the content is
/content/control/stream. So, when user is logged in to Party Manager app but
not in Content Manager, no userLogin was found in the session which was causing
this issue. I have added externalKeyParam in the request and content is being
rendered properly now.
> Missing userLogin error on party profile screen when 1st content is non public
> --
>
> Key: OFBIZ-6708
> URL: https://issues.apache.org/jira/browse/OFBIZ-6708
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Hans Bakker
>Priority: Minor
> Attachments: OFBIZ-6708.patch
>
>
> When a party 1st non content public the serveObjectData event is called in
> party profile screen and it misses the userLogin in session.
> This was implemented with
> [r1199681|http://svn.apache.org/viewvc?view=revision&revision=1199681] ([see
> this|http://svn.apache.org/viewvc/ofbiz/trunk/applications/party/widget/partymgr/ProfileScreens.xml?r1=1199681&r2=1199680&pathrev=1199681])
> which is a back hack. I guess the idea was if a "Logo Image URL" was
> assigned to a party like "Company" it should be displayed in the profile
> screen, that works w/o error in the log. But when you have a party 1st non
> content of other type for other parties (like admin for instance) it does not
> make sense, and show an error in log.
> {code}
> [java] 2015-11-03 12:05:12,856 |ttp-bio-8443-exec-11 |DataEvents
>|E| null
> [java] org.ofbiz.service.ServiceAuthException: User authorization is
> required for this service: genericContentPermission
> [java] at
> org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:356)
> ~[ofbiz-service.jar:?]
> [java] at
> org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:227)
> ~[ofbiz-service.jar:?]
> [java] at
> org.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:88)
> ~[ofbiz-service.jar:?]
> [java] at
> org.ofbiz.content.data.DataEvents.serveObjectData(DataEvents.java:139)
> [ofbiz-content.jar:?]
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[?:1.8.0_51]
> [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_51]
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_51]
> [java] at java.lang.reflect.Method.invoke(Method.java:497)
> ~[?:1.8.0_51]
> [java] at
> org.ofbiz.webapp.event.JavaEventHandler.invoke(JavaEventHandler.java:92)
> [ofbiz-webapp.jar:?]
> [java] at
> org.ofbiz.webapp.event.JavaEventHandler.invoke(JavaEventHandler.java:78)
> [ofbiz-webapp.jar:?]
> [java] at
> org.ofbiz.webapp.control.RequestHandler.runEvent(RequestHandler.java:759)
> [ofbiz-webapp.jar:?]
> [java] at
> org.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:476)
> [ofbiz-webapp.jar:?]
> [java] at
> org.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:213)
> [ofbiz-webapp.jar:?]
> [java] at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
> [servlet-api-3.0.jar:?]
> [java] at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> [servlet-api-3.0.jar:?]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> [tomcat-7.0.64-catalina.jar:7.0.64]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> [tomcat-7.0.64-catalina.jar:7.0.64]
> [java] at
> org.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:324)
> [ofbiz-webapp.jar:?]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> [tomcat-7.0.64-catalina.jar:7.0.64]
> [java] at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> [tomcat-7.0.64-catalina.jar:7.0.64]
> [java] at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> [tomcat-7.0.64-catalina.jar:7.0.64]
> [java] at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> [tomcat-7.0.64-catalina.jar:7.0.64]
> [java] at
> org.apache.catalina.
[jira] [Comment Edited] (OFBIZ-5919) CatalogUrlServlet should return a 404 HTTP status if the category or product does not exist
[ https://issues.apache.org/jira/browse/OFBIZ-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942271#comment-14942271 ] Vishal Chhabria edited comment on OFBIZ-5919 at 10/3/15 12:59 PM: -- IMO, 404 should be returned in case any url or request does not exist but /ecommerce/products/product-id is used to find the product with given productId. So I think this is the correct behaviour and CatalogUrlServlet should not return 404 HTTP status if any product is not found. was (Author: vishal.chhabria): IMO, 404 should be returned in case any url or request does not exist but /ecommerce/products/product-id is used to find the product with given productId. So I think this is the correct behaviour and CatalogUrlServlet should not return 404 HTTP status if any product is not found with any Id. > CatalogUrlServlet should return a 404 HTTP status if the category or product > does not exist > --- > > Key: OFBIZ-5919 > URL: https://issues.apache.org/jira/browse/OFBIZ-5919 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ecommerce >Affects Versions: Release Branch 12.04, Release Branch 13.07, Trunk >Reporter: Jacques Le Roux > > To test: > http://demo-trunk-ofbiz.apache.org/ecommerce/products/dropShip/dropShip1-err > Doesn't work: Says catalog not found, but the acces_log shows http status 200. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5919) CatalogUrlServlet should return a 404 HTTP status if the category or product does not exist
[ https://issues.apache.org/jira/browse/OFBIZ-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942271#comment-14942271 ] Vishal Chhabria commented on OFBIZ-5919: IMO, 404 should be returned in case any url or request does not exist but /ecommerce/products/product-id is used to find the product with given productId. So I think this is the correct behaviour and CatalogUrlServlet should not return 404 HTTP status if any product is not found with any Id. > CatalogUrlServlet should return a 404 HTTP status if the category or product > does not exist > --- > > Key: OFBIZ-5919 > URL: https://issues.apache.org/jira/browse/OFBIZ-5919 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ecommerce >Affects Versions: Release Branch 12.04, Release Branch 13.07, Trunk >Reporter: Jacques Le Roux > > To test: > http://demo-trunk-ofbiz.apache.org/ecommerce/products/dropShip/dropShip1-err > Doesn't work: Says catalog not found, but the acces_log shows http status 200. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
