Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
Pages: 1
When changing items using a non-default pricing scheme, after clicking update item, I still get the error message:
Fatal error: Call to a member function hasBasePrice() on a non-object in /home/content/83/2320183/html/webtest/ttg-be/cart/application/models/PricingSchemeGroup.php on line 138
Offline
besides the error message, I notice that when I click on change, the new change page is displayed, but the correct product is no longer identified and the pull down menu reflects the incorrect product pricing scheme (it reverts back to the default scheme). When I originally add the image to the cart, the correct product and pricing scheme are displayed. This mismatch occurs when trying to change an image that uses pricing scheme specified by the Category meta data.
Perhaps this is why there is the error message after trying to change image.
Fatal error: Call to a member function hasBasePrice() on a non-object in /home/content/83/2320183/html/webtest/ttg-be/cart/application/models/PricingSchemeGroup.php on line 138
Last edited by Ken (2014-08-06 21:56:19)
Offline
Hi Ken, since you have changed your products, can you first reset your customer's shopping cart by visiting http://ioscapes.com/webtest/ttg-be/cart/?a=reset
After doing so, add items to the cart and see if the issue perists. If it does, please provide instructions for exactly which photo you added to the cart, the options chosen, and further steps to replicate the error.
Offline
Hi Ken, since you have changed your products, can you first reset your customer's shopping cart by visiting http://ioscapes.com/webtest/ttg-be/cart/?a=reset
After doing so, add items to the cart and see if the issue perists. If it does, please provide instructions for exactly which photo you added to the cart, the options chosen, and further steps to replicate the error.
I reset the cart and added two non standard items: FH-002-W and FH-015-P. The problem is still there as I described in earlier posts. Here are the details
1. FH-002-W, Product: Wide 1 X 2 proportion Image, Image Size: 9 X 18 inch cotton print
2. FH-015-P, Product: Panorama 1 X 3 proportion Image, Image Size: 8 X 24 inch cotton print
When I click on change for either item, the product has reverted to the default: Product: Standard 2 X 3 Proportion Image with the corresponding default pricing scheme.
When I renamed the default pricing scheme to standard and tried changing 1 or 2, then an error message appeared indicating the product was not available. So clearly when changing non default items, Cart is reverting back to the default pricing scheme.
Last edited by Ken (2014-08-07 00:07:09)
Offline
I wonder if the inability to handle multiple pricing is an issue with Cart 3.02, or is there a problem with TTG BE Admin version: 2.0.1., or is it a problem with the new Publisher 2.1, or is there a problem when I upgraded to the new versions?
Here is the link to my test gallery:
http://ioscapes.com/webtest/galleries/cart-test/
Any suggestions?
Last edited by Ken (2014-08-07 02:00:54)
Offline
All I can say is that it's working perfectly for me. There was a problem as described with the last version of the cart (not related to publisher or ttg-be), but this has been fixed and appears to be working when I visit your test gallery.
Offline
works for me too.
Rod
Just a user with way too much time on his hands.
www.rodbarbee.com
ttg-tips.com, Backlight 2/3 test site
Offline
All I can say is that it's working perfectly for me. There was a problem as described with the last version of the cart (not related to publisher or ttg-be), but this has been fixed and appears to be working when I visit your test gallery.
I agree, when I test it now, everything seems to work fine. Very strange, when I tested it repeatedly several hours ago, I encountered the problem as exactly described in my previous post. I even tried the test in two different browsers, making sure to delete the cache info. Thanks for checking it out, though I am perplexed why it was having issues a few hours ago.
Offline
Pages: 1