- Fixed the resize function can resize any format flie
- Fixed share image screen to get host from contentURL (if it has content)
- Fixed product detail screen in ecommerce
- Create the function for set default image to product content screen
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1087599 13f79535-47bb-0310-9956-ffa450edef68
Orig. Msg.:
Was just running round the ecommerce site when I noticed that both
jquery-1.4.2.min.js and jquery-ui-1.8.6.custom.min.js are served when loading
/ecommerce/ pages? Isn't that rather excessive and only jquery-1.4.2.min.js
should be called?
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1073901 13f79535-47bb-0310-9956-ffa450edef68
I figured out the problem with the footer appearing in
the center (below product) on ProductDetail. There was a </div>
missing at the very bottom of:
OFBIZ_HOME/specialpurpose/ecommerce/webapp/ecommerce/catalog/productdetail.ftl
</div>
</div> <----- ADD additional closing DIV.
Product detail now correctly renders.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1073639 13f79535-47bb-0310-9956-ffa450edef68
When the user selects a shipping option and moves to the next step and then comes back to the "Shipping Options" step the previously selected value is not selected on the screen. This is because in the ftl a comparison is made between shippingMethod and chosenShippingMethod. chosenShippingMethod is being escaped so the values will never match. The solution is to use wrapString on chosenShippingMethod.
# Add a product to the cart
# login as any user I used "admin"
# Checkout Step "Shipping Address" (Step 1: Where shall we ship it?)
* Click Next
# Checkout Step "Shipping Options" (Step 2: How shall we ship it?)
* Choose "UPS Air"
* Click Next
# Checkout Step "Payment Options" (Step 3: How shall you pay?)
* Click "Browser" back button, in my code had a request that directed back a step, but this shows the issue
# ISSUE: Now "UPS Air" is no longer selected, after my patch it will be
JLR: this was only with modified code, but it makes sense and can't hurt. I will not backport though
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1068286 13f79535-47bb-0310-9956-ffa450edef68
If I cancel an order item from ecommerce. I get, the below error displayed on the page.
The Following Errors Occurred:
Unable to cancel order line : WSCO11640 / 00001 / null
There have been a discussion about it in this thread http://markmail.org/message/dfkudyvbksvls333
How it works: you can cancel an order item if you create it or have the ORDERMGR_CREATE or ORDERMGR_UPDATE permissions (I added the later to Sascha's patch, else the order manager would be annoyed ;o)
I think this makes sense, because AFAIK there are no other UIs than
https://demo-trunk.ofbiz.apache.org/ordermgr/control/editOrderItems?orderId=...
and
https://demo-trunk.ofbiz.apache.org:8443/ecommerce/control/orderstatus?orderId=...
to cancel an order item. So nobody should be able to bypass his/her permissions... Of course, let me know if you think I could have missed something, thanks
Note also that we had to remove fullPath="true" in <@ofbizUrl>cancelOrderItem</@ofbizUrl> (orderitems.ftl), to avoid InsecureFormPostToSecureRequest error. I don't think it raises any security issues though, has it's done from a javascript call with hidden orderItemSeqId parameter.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1059180 13f79535-47bb-0310-9956-ffa450edef68
The reason for the bug was that the request was called with an additional orderId get parameter. But the orderId was still in the parameter map so the request handler created with these two orderIds a orderId List. These list couldn't be interpreted from the groovy script(because a string was expected). The result was the error message.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1058488 13f79535-47bb-0310-9956-ffa450edef68
Rohit reported a bug in the jQuery implementation (ecommerce):
With the jQuery branch being merged into the trunk, 2 new issues have been identified in the onepagecheckout, and they are:
1) the remove item link does not work in the shoppingcart panel, and
2) the cart is not updated if cart quantity is changed or promo codes are entered.
There was also a caching problem in IE.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1056672 13f79535-47bb-0310-9956-ffa450edef68
This cames from Adam's advice: http://markmail.org/message/kai5lfvlnsz7xwki
Sascha comes to this solution
The Idea is to have a method which takes a JSON Object with uiLabel Resources and label entries and returns the resolved labels in a JSON Object which can be used directly in the JS Code.
The advantage of this way, is that we have only one Ajax request which reads all labels. The alternative is an Ajax request for each label, which simplify the request (because you haven't to create a complex JSON Object) but is very expansive.
* Replaces all JS alerts with the new fancy error boxes
* Adds a few uiLabels
I simply fixed some typos. I did not test all cases but did a good review.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1056497 13f79535-47bb-0310-9956-ffa450edef68
In: specialpurpose/ecommerce/webapp/ecommerce/order/orderheader.ftl:123
<#assign pmBillingAddress = creditCard.getRelatedOne("PostalAddress")>
is missing the ?if_exists causing errors in some cases.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1056072 13f79535-47bb-0310-9956-ffa450edef68
To reproduce:
* add two associated products to a main product, both with "Complementary or Cross-Sell" association type
* view the main product in ecommerce
Expected behaviour: the two associated products are listed near the bottom of the page
Actual behaviour: two products are listed at the bottom of the page, but only one of them is an associated product. The other is the main product.
The problem is caused by the value of a freemarker variable changing at a point where other freemarker code assumes the variable does not change. The execution path is complicated.
The patch fixes the problem by saving the value of the key variable into another variable, and restoring it later. However I do wonder if there is a better solution.
JLR: I did not try to find a better solution
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1042411 13f79535-47bb-0310-9956-ffa450edef68
Added screenlet styles to the ecommain.css
Added several missin screenlet-body tags.
This allows better and more omogeneus rendering when mixing together FTL and screenlet widgets.
To be continued...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1042133 13f79535-47bb-0310-9956-ffa450edef68
This patch adds several closely-related features, intended to improve the display of products and their images in the ecommerce webapp.
When additional images for a product are uploaded via the Catalog, the scaled versions that were already being created in service addAdditionalViewForProduct are now recorded as ProductContent. This makes them easily available for use elsewhere.
New ProductContentType values were added to identify these content types. The obviously consistent string to use for these was too long, and so I had to choose something less consistent, but shorter and hopefully still clear. I used XTRA instead of ADDITIONAL.
The sizes to which additional images are rescaled has been changed, so they better fit in the ecommerce display. Relevant sizes in productdetail.ftl have been updated to match these sizes.
The ecommerce product display now uses the scaled additional images if available, rather than relying on the web browser to scale the images.
When displaying a single product in ecommerce, the main image is larger than the additional images. Hovering over an additional image displays a larger version in place of the main image.
Clicking on an additional image displays a popup with a detailed version of the image.
To use the new features, one or more large images (suggest at least 600x600) should be attached as additional images to a product, using the form on the bottom of the content tab for a product in Catalog. Viewing the product in ecommerce should then exhibit the above behaviour.
I have tried to maintain backwards compatibility, so that products with the old-style use of additional images will continue to display as they did previously. This means some of the code is not as streamlined as it might be.
JLR: You might prefer to keep the old ImageProperties.xml values...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1042024 13f79535-47bb-0310-9956-ffa450edef68
Anne: some screen widgets set the field title-property instead of titleProperty. This causes errors in the logs, and means that the page title is not being set.
While preparing this patch, I discovered the labels referred to by some of these titleProperties were not available in Order component. However the missing ones were in Ecommerce. So I copied the missing ones to OrderUiLabels.xml.
JLR: instead of copying labels in OrderUiLabels.xml, I moved them to CommonUiLabels.xml: less and more consistent changes in the future.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1037559 13f79535-47bb-0310-9956-ffa450edef68