(OFBIZ-6110)
removed: marketing component related data in ecommerce plugin
removed: reference to marketing demo data in component.xml of ecommerce plugin
(OFBIZ-11333)
The Cookie Law is a piece of privacy legislation that requires websites to get consent from visitors to store or retrieve any information on their computer, smartphone or tablet. It was designed to protect online privacy, by making consumers aware of how information about them is collected and used online, and give them a choice to allow it or not.
The EU Cookie Legislation began as a directive from the European Union. Some variation on the policy has since been adopted by all countries within the EU.
The EU Cookie Legislation requires 4 actions from website owners who use cookies:
1. When someone visits your website, you need to let them know that your site uses cookies.
2. You need to provide detailed information regarding how that cookie data will be utilized.
3. You need to provide visitors with some means of accepting or refusing the use of cookies in your site.
4. If they refuse, you need to ensure that cookies will not be placed on their machine.
Used bsgdprcookies plugin to implement the feature. Thanks Deepak Nigam for initiating and providing initial patch. Thanks Deepak Nigam, Pierre Smits, Michael Brohl, Jacques Le Roux and Swapnil M Mane for inputs.
(OFBIZ-10858)
Issue 1:
1. Open https://demo-trunk.ofbiz.apache.org/ecomseo
2. Click on a category from the Categories section
3. Refresh the page
Actual:
1. Last Categories is blank
2. If we refresh the page then only the search category visible with the last
row blank with a bullet.
Issue 2:
1. Open https://demo-trunk.ofbiz.apache.org/ecomseo
2. Click on a category from the Categories section
3. Again, open the https://demo-trunk.ofbiz.apache.org/ecomseo in the new tab
Actual: 1st row is blank with searched categories
As per the initial observation, the issue persists for some specific categories
like Dropship Products, Account Activation and Services.
For all other categories, the last categories section is populated correctly.
So there could be some issue with the data.
jleroux: on Priya warning I modified the descriptions
Thanks: Rashi Dhagat for reporting, Priya Sharma for the fix
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk@1861904 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-10282)
Thanks to Arun Patidar for reporting and review.
Thanks to Suraj Khurana for providing patch for the improvement.
Thanks to Jacques for discussion and finalizing the work.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk@1830546 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-9322)
This is related to a commit in ofbiz-framework r1792866 in which data
that is removed in here is added to the framework. There is one modification
to the DemoPurchasing.xml file in which we added a UserLoginSecurityGroup which
is moved from DemoOrderPeopleData.xml because it has dependencies on security
data in ecommerce. Other than that, all data is simply deleted.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk@1792867 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-7766)
Currently, InventoryItemTypeId attribute is empty for all Product entity's demo
data. In real cases, there are products that are purely serialised
(like equipments) or purely non-serialised (like liquid).
Thanks: James Yong
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1775989 13f79535-47bb-0310-9956-ffa450edef68
In the following issue : OFBIZ-7922, there was a problem with the pagination of the Marketing Campaign list. Because there is not enough data in the demo, it was more difficult to find this bug.
To help the testing of this component, this adds some Marketing Campaign in the demo data (at least enough to unlock a second page of search).
jleroux: Actually you don't even have to add more data. The size of the list is defined by this property in widget.properties
# Default number of items to be displayed per page in a list form
widget.form.defaultViewSize=20
Locally you can change that by hand, clear caches, et voilà.
Now if we would like to have the same on demos we would need to have this property in the DB and use EntityUtilProperties.getPropertyNumber() to retrieve where it's done at the moment. Unfortunately EntityUtilProperties.getPropertyNumber() simply uses for the moment UtilProperties.getPropertyNumber() so it means more work than adding those data. But once done, it's for all (though you would still have to replace the calls where UtilProperties is used instead of EntityUtilProperties. I don't remember if we have an umbrella task ans subtasks for that. It seems though a long term work, because we have much properties likely to benefit from this possibility.
Another KISS option: maybe simply testing locally is sufficient ;)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1754657 13f79535-47bb-0310-9956-ffa450edef68
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