• Edit productsExportToGoogle form to constrain the country code that getting it from defaultLocaleString field of ProductStore entity (before it was a combobox that select by user).
• Add the new type of GoodIdentificationType entity that relate to Google Base Id including GOOGLE_ID_en_US, GOOGLE_ID_en_GB, GOOGLE_ID_de for identify each productStore with its language.
• Add the Google Base Auto Update function.
• Add the new filter of GoogleBaseAdvanceSearch including ACTIVE_PRODUCT, GOOGLE_SYNCED and DISCONTINUED_PRODUCT.
• Add allowRecommended option for add the recommended attribute to Google Base such as QUANTITY, COLOR, YEAR_MADE etc.
• Add the Google Base help.
A contribution of Antwebsystems employees M and Ton2
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1081270 13f79535-47bb-0310-9956-ffa450edef68
Two reasons to this:
# we are not sure the descriptionFieldName is alwayd of the form formName_descriptionFieldName
# anyway we need a form name for call_fieldlookup3 and call_fieldlookup2 just above in htmlFormMacroLibrary.ftl.
While at it, I also removed all question marks in ${uiLabelMap.ProductIncludeSubCategories}? occurrences, it's already in the labels
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1056731 13f79535-47bb-0310-9956-ffa450edef68
Rohit reported a bug in the jQuery implementation (ecommerce):
The find button is not working in the 'googlebase' application. The 'googlebase' application has a page using which u can to search for product to be submitted to google base. the find button is not submitting the page at all.
Sascha: This issue was related to the Lookup Call. The Form in Google Base hadn't a 'name' tag, so the form could not be found. I changed the target by name to a target by Id call (which is better anyways).
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1056701 13f79535-47bb-0310-9956-ffa450edef68
BJ: when there is an error, the control servlet looks for an error path in <param-name>allowedPaths</param-name>
it does not find one throwing an exception which buries the orginal error.
instead of changing the code it is just easier to add the /error: path.
then the real error gets reported correctly.
JLR: This will maybe help to better understand some errors on demo servers, and can't hurt
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@954135 13f79535-47bb-0310-9956-ffa450edef68
<copyright>Copyright 2001-.* The Apache Software Foundation</copyright>
<copyright><year>.*</year><holder>Apache Foundation</holder></copyright>
<copyright><year>.*</year><holder>Apache Foundation.</holder></copyright>
<owner>Copyright 2001-.* The Apache Software Foundation</owner>
Less to update every year!
Thanks to BJ 1st effort at "update files from 2009 to 2010" (https://issues.apache.org/jira/browse/OFBIZ-3783) - OFBIZ-3783
Note: there are been a lot of efforts in 2009: there are plenty of data dated from this year!
I hope I did not broke anything (should not, but of course I did not try all changes...) Anyway, this can be easily reverted...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@948846 13f79535-47bb-0310-9956-ffa450edef68
Following points were there in my mind before doing this change.
-- AFAIK ofbiztest@yahoo.com email doesn't exists.
-- Bounce email issue if you have enabled Javamail container. This drastically slow down your system performance.
-- Now anyone can use ofbiztesting@gmail.com account settings for Sendmail, Javamail container etc.
-- Send mail service triggered again and again with failure message on console if any of the email not found bccAddress inside ProductStoreEmailSettings entity. Again slow speed of your development machine.
-- Please let me know where to share the password of this account? Dev list?
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@938446 13f79535-47bb-0310-9956-ffa450edef68
Recently multi store support for Ebay has been implemented. For the multi store support we need ProductStore > ProdCatalog > ProductCategory association. For EBay we define specific categories of type EBAY_CATEGORY, only those products that are associated to an EBay category are eligible for eBay export. In the current implementation there is no proper prodCatalogCategoryTypeId which can be used to associate eBay category to ProdCatalog, one way to associate an eBay category to ProdCatalog is as a PCCT_BROWSE_ROOT category, thus we have two categories associated to the catalog as BROWSE_ROOT, the other one is for online store. Technically, this is wrong, a catalog should be associated with only one browse root category. Due to this wrong association the eBay category doesn't show up on the advance search page of EBAY webapp, instead online store's browse root category is shown which may also contain those products which are not meant to be exported to eBay. So this category associations need to be fixed, and following is how this can be resolved:
1. Create a new ProdCatalogCatagoryType PCCT_EBAY_ROOT
2. Define a worker method in CatalogWorker to derive the top level (root) ebay category
3. Now in the advance search form, first look for top level ebay category associated to the selected catalog
* If found, derive sub category list of the top level ebay category and display, else display the top level ebay category itself
* If not found, derive the top level browse root category (PCCT_BROWSE_ROOT) and display the sub category list for it
Thanks Parimal Gain for the contribution.
Special thanks to Mridul Pathak (Zone of Sharp Mind :-)) for discussing implementation plans & providing wonderful notes.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@832713 13f79535-47bb-0310-9956-ffa450edef68
Changes includes following:
1) Created new search form for eBay and GoogleBase - It was not good to update *advancesearch*.ftl file present inside catalog component. Now it will be easy to maintain separate file for future deployments.
2) Restricted productStoreId and prodCatalogId field to search.
3) Added webSite drop-down on "Export to eBay" and "Export to GoogleBase" page.
4) Select webSite to get the webSiteUrl.
Thanks Parimal for your contribution - this will surely help the community.
Special thanks to Mridul, Rishi, Chirag, Deepak & Me :-) for discussing requirement and also special thanks to Jacopo for the notes and discussion on requirements.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@831534 13f79535-47bb-0310-9956-ffa450edef68
I was planning to wait longer, but I can't wait more. I have added a lot of small trivial changes in this patch and they are blocking me to go further on other issues...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@813307 13f79535-47bb-0310-9956-ffa450edef68
Following things are done in this commit:
1) Added new entity GoogleBaseConfig and reading the values from there. Also kept option to read configuration values from property file.
2) Added new ProductCategoryType record for Google Base - Thanks Jacopo for your suggestion on this.
3) Prepared data for demo purpose in DemoProduct.xml file - This demo contains the association of few product with Google Category.
4) Also prepared demo data for GoogleBaseConfig entity.
5) Provided option to have default value of webSiteUrl on the GoogleExport form - for this refer productsExportToGoogle.groovy file.
Thanks Pranay for discussing few things with me in b/w this phase of development.
In next Commit I will provide UI for GoogleBaseConfig entity(CRUD operations) so it will be easy for end user to update values in this entity easily instead of moving to webtools and do the needful.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@809552 13f79535-47bb-0310-9956-ffa450edef68