Completes in screens the changes done in forms at r1741873. I then replaced few form lists by grids, where it was possible to do it with regexp.
Also complete StatsForms.xml to use only grids and "searchList" form in ecommerce ContentForms to NOT use grid (not called in screen)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1742196 13f79535-47bb-0310-9956-ffa450edef68
Pierre Smits: When loading data into OFBiz without the manufacturing component the process ends unsuccessful.
Deepak: Entity related error should be fixed under OFBIZ-6760, apart from it there are dependency of ecommerce demo data on manufacturing demo data.
jleroux: Duplicating those data (present in Manufacturing) into ecommerce is indeed a smart solution. If they are already loaded (like OOTB) they will not be loaded twice. If they are not there they will be loaded.
Conclusion: sometimes duplication is smart (especially with OFBiz data) and this is a good way to introduce independency between components...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1731665 13f79535-47bb-0310-9956-ffa450edef68
================================
There are three sets of dimensions in the Product entity.
(productHeight, shippingHeight), (productWidth, shippingWidth), (productDepth, shippingDepth) but in case of weight, there is another set of dimension field weight and productWeight which are inconsistent in nature.
Fix this thing and correct all instances of this in the framework.
=================================
Thanks Suraj for reporting the issue and providing the patch for the same. Thanks Jacopo and Pierre for discussing the issue with Suraj.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1720900 13f79535-47bb-0310-9956-ffa450edef68
It would be better if we have most of the demo product data in product or maybe in order component. Because almost all what can be done concerning ordering in ecommerce can also be done in order manager from which anyway ecommerce depends on
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1662093 13f79535-47bb-0310-9956-ffa450edef68
Introduces inventory data for GC-002 to have the amount field showing at ecommerce/gift-card-reload-GC-002-p. This field depends on ProductFacility.lastInventoryCount column
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1652814 13f79535-47bb-0310-9956-ffa450edef68
ContentServicesComplex.getAssocAndContentAndDataResourceCacheMethod was not using the passed contentId in condition list, and also was not using the ContentAssocDataResourceViewFrom/To view entity to get the result. Thanks to Deepak Dixit for the patch.
Misc minor cleanups (removed commented out code) and some small formatting fixes.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1643061 13f79535-47bb-0310-9956-ffa450edef68
======================================================
There is incomplete set of ShipmentMethodType an CarrierShipmentMethod data. Also carrierServiceCode is not present for all CarrierShipmentMethod records.
Add all shiiping options along with carrierServiceCode for carriers FEDEX, UPS, USPS and DHL.
======================================================
Thanks Arun for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1642413 13f79535-47bb-0310-9956-ffa450edef68
We are also proposing to add the following fields:
ProductSubscriptionResource.gracePeriodOnExpiry
ProductSubscriptionResource.gracePeriodOnExpiryUomId
Subscription.gracePeriodOnExpiry
Subscription.gracePeriodOnExpiryUomId
This will allow the runServiceOnSubscriptionExpiry to trigger the service in SubscriptionResource.serviceNameOnExpiry only after
nowTimeStamp >= Subscription.thruDate + Subscription.gracePeriodOnExpiry.
This provides flexibility in managing the triggering of the deprovisioning service, similar to the flexibility in automatic subscription extensions enabled by Subscription.canclAutmExtTime for runSubscriptionAutoReorders.
jleroux:
I replaced tabs by spaces
Will commit the change in serviceResult.ftl apart
Slightly reformatted SubscriptionServices.runServiceOnSubscriptionExpiry()
Slightly reformatted and added comment in services_subscription.xml for the 2 new services
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1597235 13f79535-47bb-0310-9956-ffa450edef68
See Purchase Order #DEMO10090 in the Order Managaer application, where the order are to be approved.
Try to click on the link;
Shipments Nbr 9998 Packing Slip
----------------------------------------------
Then the following error is shown:
----------------------------------------------------------
The Following Errors Occurred:
Problems with the response writer/output stream: org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen [component://product/widget/facility/ShipmentScreens.xml#PackingSlip.fo]: java.lang.IllegalArgumentException: Operator must be EQUALS or NOT_EQUAL when right/rhs argument is NULL (Operator must be EQUALS or NOT_EQUAL when right/rhs argument is NULL )
-----------------------------------------------------------
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1512376 13f79535-47bb-0310-9956-ffa450edef68
When you used a content as template, the content.serviceName value used to call the context populate service before rendering.
I propose to replace serviceName field by customMethodId and use customMethod pattern for more flexibility.
serviceName field is kept for backward compatibility
Thanks to Scott and Adrian for support
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1379937 13f79535-47bb-0310-9956-ffa450edef68
idea where those bad digest password values came from. Really, I have
no clue. Everything worked in testing. I'm very confused. I have
verified that I can log in now with the demo accounts. Sorry about the
breakage.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1334173 13f79535-47bb-0310-9956-ffa450edef68