[jira] Created: (OFBIZ-870) Shipping Settings in XML don't match Presented Options in New Order Shipping Options

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

[jira] Created: (OFBIZ-870) Shipping Settings in XML don't match Presented Options in New Order Shipping Options

Nicolas Malin (Jira)
Shipping Settings in XML don't match Presented Options in New Order Shipping Options
------------------------------------------------------------------------------------

                 Key: OFBIZ-870
                 URL: https://issues.apache.org/jira/browse/OFBIZ-870
             Project: OFBiz (The Open for Business Project)
          Issue Type: Bug
          Components: order
         Environment: Professionally Hosted Solution: Dedicated Debian Linux. 1Gb RAM, Dual Core 2.016 GHz Intel Processor, RAID.
            Reporter: Peter Watson


I am having an odd problem;

The shipping configuration settings in the xml (storeShipping.xml) do not match what the order process presents as the shippings options.

1. The settings in 'Catalog > Stores > Shipping >' show 8 different methods (estimateID | method) which I had setup in the xml file (/hot-deploy/store/data/storeShipping.xml).

2. The order entry shipping options do not have the same 8 settings, they have the original 4 settings that were there before I actually made the changes. So when you are in the order entry processyou see the original settings not the new settings that I have added.

3. I did use the 'Web Tools > XML Import to import this file'. But the settings don't seem to have been 'activated', do I need to run a service update...and if so would that affect my other custom settings to do with product layout and other related settings?

I do have some screenshots, that illustrate this scenario.


Not sure is this is a known issue or simply an erroneous error. Would appreciate some feedback.



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

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (OFBIZ-870) Shipping Settings in XML don't match Presented Options in New Order Shipping Options

Nicolas Malin (Jira)

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

Jacopo Cappellato closed OFBIZ-870.
-----------------------------------

    Resolution: Invalid

Could we move this discussion to the mailing list? I don't think there is a bug here, so it is just a mettar of configuration.


> Shipping Settings in XML don't match Presented Options in New Order Shipping Options
> ------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-870
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-870
>             Project: OFBiz
>          Issue Type: Bug
>          Components: order
>         Environment: Professionally Hosted Solution: Dedicated Debian Linux. 1Gb RAM, Dual Core 2.016 GHz Intel Processor, RAID.
>            Reporter: Peter Watson
>
> I am having an odd problem;
> The shipping configuration settings in the xml (storeShipping.xml) do not match what the order process presents as the shippings options.
> 1. The settings in 'Catalog > Stores > Shipping >' show 8 different methods (estimateID | method) which I had setup in the xml file (/hot-deploy/store/data/storeShipping.xml).
> 2. The order entry shipping options do not have the same 8 settings, they have the original 4 settings that were there before I actually made the changes. So when you are in the order entry processyou see the original settings not the new settings that I have added.
> 3. I did use the 'Web Tools > XML Import to import this file'. But the settings don't seem to have been 'activated', do I need to run a service update...and if so would that affect my other custom settings to do with product layout and other related settings?
> I do have some screenshots, that illustrate this scenario.
> Not sure is this is a known issue or simply an erroneous error. Would appreciate some feedback.

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