-- Error or Success message was not displaying for buziness time theme. Fixed this issue.
-- In case low ATP proper error message was not coming for any product while importing order to the system. It was redirecting the blank page with one line message, that was not verbose enough. Improved error message for this.
-- The leaf category id will be provided in category data so that ebay export works fine.(See the numeric value provided in ProductCategory record).
OFBiz jira is not responding at my end since last 2 hours so committing this patch.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@884869 13f79535-47bb-0310-9956-ffa450edef68
Implemented following points:
1) Created decorator for Ebay Configuration screens
2) Modified list and add Ebay configuration Form
3) Created Find Form
4) Crated menu and sub menu
5) Created Edit Ebay Configuration Screen
6) Modified Ebay Configuration screen with name FindEbayConfiguration
Thanks Parimal for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@835306 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@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@831534 13f79535-47bb-0310-9956-ffa450edef68
This will help to avoid the duplicate order being created in the system with the help of old screen for importing eBay orders.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@815248 13f79535-47bb-0310-9956-ffa450edef68
Following things are done in this patch:
-- Moved commonly used methods to EbayHelper.java file.
-- Created two main methods "readGetOrdersResponse" & "createShoppingCart" to read xml data coming from Ebay and then create order in OFBiz respectively.
-- Also provided sample response XML data that is being generated from Ebay.
-- Changed the UI in which first it was searching orders and then from the orders list we were importing orders.
Now we have only one screen available in which search criteria for order is provided & on the basis of that search criteria order gets imported in OFBiz.
-- Previous work for importing Orders(Not exactly order - it was transaction) is working fine OOTB.
Here are few things that I am thinking to do in this area soon:
-- Improve error handling code - code cleanup.
-- Provide scheduled service UI(or prepare demo data for scheduling job) in which the orders will be imported automatically in the system instead of searching and then importing done by end user. - Thinking the best way to handle it.
Thanks Rishi & Sumit for discussing few things/ issues in b/w the development of this pass.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@814560 13f79535-47bb-0310-9956-ffa450edef68
Here are few reason for this implementation:
-- In "GetSellersTransactions" itemId(ProductId in ebay) is provided in the OrderHeader.externalId field which doesn't seems correct.
-- Suppose we have Single Order created in eBay if some one wins the auction and in that order we have 3 order items.
Then "GetSellersTransaction" call creates three orders in OFBiz for all those three items that are associated with Single Ebay order.
In short "GetSellersTransaction" request treat three item as three transactions.
-- "GetOrders" call will return the list of orders on the basis of search criteria and then we will create(Import) the Order in OFBiz from the resultant list of orders.
-- Current implementation for "GetSellersTransactions" will remain as it is in trunk - as we don't know if someone might be using it in their custom projects.
Also did miscellaneous cleanup.
Thanks Jacopo for providing your notes for this implementation & also discussing issues in b/w development - as always your notes were awesome.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@813444 13f79535-47bb-0310-9956-ffa450edef68
-- Moved eBay configuration settings to a new entity - EbayConfig. Property file configuration support also exists in current code.
-- Also prepared the demo data for this new entity.
-- For default webSiteUrl prepared demo data in WebSite entity so we can show default value on the form.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@811645 13f79535-47bb-0310-9956-ffa450edef68
* export product images to eBay Action
* export a description based on content (a new product content type has been added for this purpose)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@809539 13f79535-47bb-0310-9956-ffa450edef68
[ \t]+$ => "" (empty)
Should be easier to review when committing changes with trailing spaces removed automatically by anyedit or such tool (please refer to http://docs.ofbiz.org/x/mg)
Of course this effort to remove trailing spaces has no functional implications.
Actually, I was doing a 1st commit and as it's long to upload, I got conflicts with r763135
In the meantime I did some refactoring also in *.java and *.groovy files :
){ => ) {
if( => if (
while( => while (
}else => } else
else{ => else {
switch( => switch (
try{ => try {
}catch => } catch
catch( => catch (
}finally{ => } finally {
So these changes are also in this commit, should not be a problem anyway.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@763175 13f79535-47bb-0310-9956-ffa450edef68
The ecommerce component is excluded from this commit.
These changes shouldn't break any layout. If you spot something wrong, let me know and I'll fix it.
I won't make any more maincss.css changes for a little while. I'll let the dust settle from these two commits, then I'll go through the file and physically remove the deprecated styles.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@627051 13f79535-47bb-0310-9956-ffa450edef68