This reverts commit 17eb2e4cf7bfba4e6a6b62117aa8d64cd5774c5e.
It does not work when using <<target="javascript:........>>
I could change those cases but it's easier and safer to simply revert back to
target-type!
Thanks: James for report
(OFBIZ-11587)
All files have been migrated to asciidoc format and help link now point
to the html file generated from the asciidoc files
In the global Help Docbook index tree, remove all points about
Ebay and add a short page with a link to the new help
Remove docbook help files for Ebay
================================
Redundant options at select filter on find screens
================================
Thanks Deepak N and Renuka for your contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1758032 13f79535-47bb-0310-9956-ffa450edef68
jleroux: I suspected it was only a matter of replacing "${bsh" by "${groovy" in *.xml. But I had not the guts to get into 11(!) sub tasks.
So, in Eclipse, I simply did a S/R in *.xml and compared parts of my changes with some Pierre's most "complex" patches respectively product, ebaystore, projectmgr and scrum.
They were totally similar (just revisions number changed) so here is the whole.
I will later improve these changes by removing HTML entities when possible, this is a bit more delicate because in some cases the XML schema are not complete (or/and for other still obscure to me reasons) and if you simply replace HTML entities by simple code (eg &Amp; by &) you get issues in logs when the XML parser cross them...
Note: only menus, screen and forms are changed here.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1682118 13f79535-47bb-0310-9956-ffa450edef68
Summary: The purpose of this patch is to address the following:
1. Provide a standardized set of image width and height specs for page layout in ofbiz. This gives ofbiz a uniform look throughout as it applies to image display.
2. Preserve the aspect ratio of the image when using these standardized image sizes.
3. One place to make styling modifications (eg. css file).
4. Decouple styling from code (eg. java,ftl,xml,html,jsp,etc).
Regarding including the real image size, the width/height attributes in <img> specifies the boundary of the image when shown on the page. If you need to specify the real size of the image, the server code would have to perform the determination. Afterwards, you can include the actual dimensions of the image in the title attribute of <img>
Details:
Manually specifying the image width and height does help with preserving the layout of a page regardless of the image size to be shown. The challenge with this method is that the image shown on the page in question may be distorted if the aspect ratio of the image differed from that of the width and height attributes of <img>. This basically forces the person uploading the image to be more vigilant about image aspect ratios.
The purpose is to harmonize on the display size of images with a standardized set of width/height constraints in which an image must fit and preserve the aspect ratio of images.
Currently the source files (eg. ftl, xml) either manually specifies the width or height of a displayed image (ie widget <image> and html <img> tag). The problem with specifying only one constraint is that an image can affect the layout of the page if the user uploads an image where the aspect ratio could be large.
Some ftl and xml files specify both the width and the height. The problem with this is that if the aspect ratio of the image in question does not match that of the width and height of the <img> tag, the image would be displayed distorted.
The solution was to create a standardized set of CSS styles that both configure the displayed image size and preserve the image aspect ratio (eg. thumbnail size, medium size and large size). Of course, the developers can further define or modify the styles to suit their need.
By using CSS, one can change the size of displayed images without having to tamper with the ftl and/or xml files. This helps to reduce potential bugs that come with modifying the ftl and xml files. The existing way of doing things is to go through each ftl or xml file in question and manually modify the width and/or height of the <image> and/or <img> tag.
The question about the "border" around images. If you do not wish to have a border around the image, just remove it from the CSS style. It's that easy No need to change anything else. Ie. configuration to the image is done on the CSS style and not on the <image>, <img> tag.
NB: The current patch does not apply to all displayed images. I have only made appropriate modifications to widget <image> and html <img> tags that have either specified the width and/or height. There are numerous <image> and <img> tags spread all over the project that do not specify dimensions. I would have to modify them as I encountered them when I could see where and how they are displayed on the screen. Note that these images would not be affect by this patch.
jleroux: despite my efforts I was not able to check all screens. But I think it's ok
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1296782 13f79535-47bb-0310-9956-ffa450edef68
one more patch to fix following issues in ebay and ebayStore components
1 Fixed issue of set complete order status in ebay when we complete order in ofbiz.
2 Created record of OrderPaymentPreference in PAYMENT_RECEIVED status.
3 Updated qty of cart item, if same product is adding again in cart during import order from ebay.
4 Set transactionId in cart.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1063265 13f79535-47bb-0310-9956-ffa450edef68
- add button to save listing xml data when export to ebay and we will use this xml data for function auto relist (For function relist we will patch again next week becuase It not finnish yet now.)
- changed shipping options to selectbox
- item themes and descriptions in create listing screen
- add button to verify listing before export.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@923223 13f79535-47bb-0310-9956-ffa450edef68
- function to reserve product in ofbiz inventory when posted on Ebay
- function load products and quantity to ebay store inventory
- Add new EnumerationType call EBAY_INV_RESERVE for reserve product from inventory
- help screens.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@904006 13f79535-47bb-0310-9956-ffa450edef68
- updated export categories function to export and update categories on eBay store.
- updated export categories screen display only catalog in store.
- updated export categories help screen.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@903049 13f79535-47bb-0310-9956-ffa450edef68
- function auto relist item and screen
- Get feedback data from ebay site and save into ofbiz.
- Add rate pictures into framework/images/webapp/images
- screen for show awaiting feedback and recent feedback from buyer
- help screens are provided
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@902716 13f79535-47bb-0310-9956-ffa450edef68
- function Add ofbiz categories in ofbiz store to eBay categories also add new items in every categories to eBay categories.
- Add field 'apiServerUrl' to EbayConfig entity and add ebay sdk lib to ebay component.
- function load data ebay store setting (basic information,theme etc.) from ebaystore
- function create new account for add your ebay account which is already registered on ebay site (using for access to your ebay store)
- Screen for show your ebay profile
- help files for ebay store functions
using the Ebay api
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@900410 13f79535-47bb-0310-9956-ffa450edef68
-- 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/specialpurpose@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/specialpurpose@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/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