I've spent the last two days checking on every portion of Prestashop, trying to figure out how to restore zip-code based shipping functionality, and at the very least, install a flat-rate shipping fee so we don't get gouged by our own website.
I checked various websites, and found very little help; the only responses I see say things about the difficulty.
I tried using modules for shipping and tested out their demos but was just as confused by them, and getting the same errors (in cart, it says any area code is not a region that can be shipped to).
Here's my original thread: https://www.prestashop.com/forums/topic/460500-shipping-carriers-deleted-shipping-functionality-caput-urgent/
Related
I've gotten a message that my site may be knocked off of Google Merchant Center due to "Inaccurate availability (due to inconsistent availability between the landing page and checkout pages on your website)".
This affects only a small amount of products (only around 0.3% of my 40,000-ish products), so I know it's not an engine issue. After asking Google to recheck the results, they came back with the same error, but with a completely different list of products with no overlap, so I know it's not a problem on the individual product level.
There's no geo-locking on these products, and Google says that the problem exists on US IPs.
Nearly all of the errors look like this:
Value on the landing page - v:out_of_stock
Value in the data feed - v:in_stock
Performing an audit on the products in question shows that none of them have been out of stock for weeks, so the data feed is correct.
None of Google's suggested common issues (geolocking, buy button not working, product can't be shipped to an address, products not available country-wide) seem to apply. The country Google checked this on was a US-based IP.
I'm running out of ideas here, does anyone have any other suggestions?
The answer turned out to be something silly for my site, but I'm posting the answer here just in case this helps someone else.
Google's crawler was setting their country to be Andorra and attempting to check out using the US site. This is obviously not a good representation of the US experience. Google advised us that this was a mistake on their crawler's part, and that we would pass the next audit without any modifications. So if you're here looking for a solution, the absolute best advice I can give you is to find a phone number for Google Merchant Center and give them a call because the error may not be on your end at all.
Update: We passed the audit with no changes made on our part.
I have an online shop in development, all went well until I decided to do SEO on the shop. After this, if I chose a product variation from front-end it just redirects me to a random product.
This picture describes the first state. The default product load.
This picture describes what is happening after you select a variation. As you can see the product name stays the same, but the link indicates that a totally different product is displayed.
If I have the debug mode enabled when selecting a variation it throws "An error occurred while processing your request" and in the request file I can see that besides some errors (Deprecated: array_key_exists(): Using array_key_exists()) it shows the request for a different product.
I can't understand why this is happening, so I am in dying need of your help.
That's the way Prestashop 1.7 works :
First time a customer lands in a multi-variation page, the default attribute will be loaded,
URL will show only the ID product.
Once you choose an attribute , an AJAX call will refresh the page
with the current attribute and URL will change with id_product-id_product_attribute value.
Not sure what you mean by "random product" as in both of your examples I see an attribute
being selected.
Anyway there are several (paid) modules to change this behaviour in a better SEO perspective,
this is definitely one of the most famous :
https://addons.prestashop.com/en/url-redirects/16633-pretty-urls-seo-friendly-url-remove-ids-numbers.html
EDIT: Just noticed that the ID product is different in the two screenshot, this could be related to some DB issues with attribute too, you should check if you have some not coherent values between id_product and id_product_attribute(s)
I found a fix for this. Apparently or appeared because I was using the duplicate function for uploading products. I don't know why but on some products it makes this behavior.
I've spent over 12 hours to find a explanation for this and I was unable to find one. The PrestaShop forum straight up banned me for posting this topic.
My advice is to NOT USE PRESTASHOP it's and old sistem and full of bugs, the support is expensive and I get the impression that even they don't understand their system.
If you find yourself in this situation, know this. Don't duplicate and upload products using "add new" function.
And I can't state this enough, do yourself a favour and don't use Presta, with all the expenses the time to invest and what the product looks like at the end of the road, is just a waste of time. Even after you finish is guaranteed to break in 1-2 years, any updates will break your store and you will need to invest even more more to fix it. It's an old, slow and buggy CMS. It's days are numbered.
Thanks a lot for help.
Best regards, Daniel.
We are using Orocommerce version 3.
We have setup a number of differnent product categories and assigned products to these. We have also defined the permissions so that certain groups and cusotmers should not be able to see some of the products via the front end of the site.
When testing the site using two different cusotmers one which should and one which should not see the product when using the search and the product SKU both are able to view and potentially buy the product.
This only appears to be happening for certain products, which is odd.
We have reviewed the documentation here: Oro Docs and feel we have followed it correctly.
Has any one come acrooss this before, what options do we have solve this?
Approx 2 years ago, I wrote a custom plugin that checks order items in the cart for specific requirements. If the requirements are not met, it displays an error and does not allow the customer to check out. This code has been working well for approx 2 years. Recently the code broke. It must have been due to the recent WooCommerce upgrades, as we hadn't touched the code in ages. I spent a while debugging it and this is what I found:
wc_add_notice doesn't do anything anymore. When I changed it to wc_print_notice, it displays the error notice.
In the past, when I used wc_add_notice on the cart or checkout page, it would display the error message and not allow the user to continue to checkout. Now that I am using wc_print_notice, it only displays the error message, but it does allow the user to continue. I spent a long time working on this today and I can't figure out how to stop the user from continuing to check out.
Any suggestions..?
And, does anyone know where I can read documentation of the WooCommerce upgrade changes related to my issue?
Thanks!
PS: If you want to see code samples, here are 2 articles which I found today, that display sample code doing exactly what my code does:
https://www.sitepoint.com/minimum-checkout-requirements-in-woocommerce/
https://gist.github.com/kloon/4545677
I am working on a client site and the majority of what they sell is fabric sold by the yard, with a minimum of .25 yards per purchase.
The client INSISTS that he wants the end user to enter a decimal into the quantity field to order the amount of fabric she wants and so far I haven't been able to talk him out of this requirement.
They currently use Miva because it supports this particular requirement (through a module). I'd prefer not to work with Miva if I can help it, so I'm turning to you guys!
So far, I've found two additional options for handling decimal quantities:
Magento
Zen Cart
Anyone know of any other options? I'm open to anything right now (hosted, open source, whatever), just want to see all the options for this one specific weird requirement.
Thanks!
You could go for TYPO3 Multishop. Also open source and with a tiny adjustment it supports decimals as quantity input. You can see it in action on the following web page:
http://www.bbms.nl/webwinkel/
More information about TYPO3 Multishop can be found here:
http://typo3multishop.com/