El Patron

Moj odgovor: Če niste razvijalec ali programer, priporočam, da počakate na različico PrestaShop 9.0.1. Različica 9.0.0 je predstavljena kot pripravljena za produkcijo, vendar se v resnici obnaša kot javna beta – še vedno vsebuje odprte težave, ki vplivajo na stabilnost in združljivost z mnogimi moduli. Za vse, ki imajo delujočo trgovino, je bolje počakati na različico 9.0.1 (ali novejšo), preden nadgradite ali zaženete novo spletno mesto.

How is the surcharge stored today? Without knowing this it is difficult to provide feedback.

PrestaShop 9.0.0 is BETA, and should have never been portrayed as a stable relase, I never understand French open source, community tested without community, so many ruined upgrades or new users trying to build their business on 9.0.0, only to find base feartures do not work. rant over There is a Regression bug(s) in 9.0.x where new attribute groups do not show the Texture / Color input fields in the Back Office. The UI simply omits the controls needed to assign colors or textures. https://github.com/PrestaShop/PrestaShop/issues/38981 The attribute form UI has documented rendering problems (especially for “radio” or alternate attribute types) that hide or mis-handle expected fields. https://github.com/PrestaShop/PrestaShop/issues/39018 Once a texture is uploaded, you cannot remove it in 9.0.x, and the color field cannot be cleared, unlike in previous versions. https://github.com/PrestaShop/PrestaShop/issues/39397 These issues strongly suggest your problem is not due to your configuration or theme alone, but rather a core regression introduced in PrestaShop 9.0.0 and again, they should not have prompted people to use this, it's for developers only.

Friendly URLs were handy back in the day so customer service could easily read a product link over the phone — not really for SEO reasons. If you remove IDs completely, you’re using a module that changes PrestaShop’s core behavior, since this option isn’t part of the native SEO & URLs settings. From experience: There’s no real SEO benefit to removing IDs — Google handles canonical URLs just fine. It can create upgrade issues later if that module isn’t maintained or compatible. So, while it looks cleaner, it’s more of a cosmetic tweak than a performance or SEO improvement. I’d keep the native friendly URLs — stable, supported, and safe for future updates.

shopify and wp have already integrations for chatgpt. migrating ps to shopify using migrator pro works very well 75% of my historical clients have already moved to shopify...the others are in die hard prestashop...but not doing so well to be honest.

Hi @Heaven and Home PageSpeed insights is a great tool and they have association with https://www.webpagetest.org/ that will not only give you insights like PageSpeed but also give advoce pm how to fix. The biggest improvements come from configuring mysql, the first step is to enable slow query, here is blog on how to work with slow query. Here some general blog posts on mysql tuning. https://prestaheroes.com/blogs/mysql-optimization (improving mysql performance is first thing anyone should do, then look at how to tune the shop. Ok, so blocking is main issue with all PrestaShop because it does not support preloading of assets (.css/.js). Also many enable CCC of .js/.css but do not check that each page type has same filenames across page types, if different then each page type will have large load (see my .css unify module that fixes the issue. See here for my css/js preload modules which significantly improve above the fold page render. https://prestaheroes.com/collections/performance Hosting, well...nvme to ssd significantly improves performance, good hosting is key. For seo, which is dead except for meta title/description, you should only concern yourself with visitor experience, which is the most important for organic seo. That being said seo came back with AI...chatgtp support buying products from chatgtp and supports shopify and woocommerce (wp).

you forgot the attachment, also share module you are using. tip: You can often find issue using Chrome dev tools here is blog I created for debugging. There is section on Chrome dev tools where you can see if javascript is erroring for example.

Module Can Be Purchased Here. Demo Front Office Compatible PS7 PS8 (PS9 coming) MultiShop Expand Your Reach with Enhanced URL Localization Our Enhanced URL Localization module lets you scale your PrestaShop for true global success. Upgrade your URLs from the basic format: yourdomain/ISO Language Code/ to the more powerful: yourdomain/ISO Language Code-ISO Country Code/ What does this mean for your shop? Precise Localization: URLs are automatically identified and translated using ISO language and country codes, ensuring visitors see content tailored to their region. Optionally Enable Market Multiplexing: Serve the same language in multiple countries with unique URLs. Examples: en-ca, en-gb, en-us — es-es, es-us, es-ar Not selling internationally? You’ll still benefit: Clearly show your shop’s default country in the URL for visitor assurance. Give Google and other search engines explicit signals about your shop’s country for better SEO performance. Compatible with Google Sitemap: Just regenerate your Google sitemap to publish your new, international-ready URLs.

chatgpt can give real solutions if it has all the information..it's all about prompts so please know if someone uses chatgpt or other AI, they are still taking their time in helping. Also replying doesn't work is not helpful, how did it not work and did you find any you should not, nor should anyone else really be upgrading to 9.0.0, this is a beta version and has some base issues that will be fixed in 9.0.1. Wait for 9.0.1.

you should review your hosting php error log, google or ai on how to find it based on your hosting package, or via ftp root logs folder. if you have restore, this would be time to consider doing a restore. Then in future create subdomain of your 8.2.3, perform upgrade there first.

PrestaShop 9.0.0 is the first release to support this. We have our own checkout module that supports this since 2020. It's possible to create a patch for pre prestashop 9 but you would need to provide at 'least' your prestashop version for community to provide help.

those https above are ok. I suppose really only way now to pin point it is to disable 3rd party modules from performance page, first make a list of enabled modules. Cheek if problem still exists and if not then enable one by one until problem comes back. This will tell you which module if any is creating the issue. Also advanced --> information did you check which ps files changed?

If your hosting has Plesk, cPanel, or similar: → Look for Logs → PHP Error Log (sometimes called “Web Server Logs”). You can also check whether your installation has been modified unexpectedly. Go to Advanced Parameters → Performance. Scroll down and find the “Check Files” section (sometimes labeled “Check PrestaShop files integrity” or “Check if files have been modified”). PrestaShop will compare your core files against its original checksums. If files have changed in /controllers/, /classes/, or /modules/ and you didn’t modify them yourself, that’s a red flag. While this specific “delete product from catalog when removing from cart” behavior is unusual, it’s worth noting: Many PrestaShop stores have been hacked through outdated modules or themes, often exploiting insecure file uploaders or helper classes. This can allow attackers to: Inject malicious code into overrides, Replace controller files, or Hook scripts into events like cart updates (exactly what’s happening here). So if: You see unexpected file changes in Advanced Parameters → Performance, Or your PHP logs show suspicious includes or eval(), then treat this as a security incident — not just a bug. Me? if you want to stay with PrestaShop then use a tool like migrator pro and migrate to fresh copy of PrestaShop. I see that you have many topics on this same question. Or move your catalog to different ecommerce platform so you can get focus on selling rather then debugging

this is normal I did check that prestashop checkout does is hooked here normally, at least on a 9.0.0. to narrow down try the following: Disable all overrides (Advanced Parameters → Performance) and re-test. If the deletion stops, inspect override/classes/Cart.php, override/classes/Product.php, or any controller override. In Back Office go to Advanced Parameters → Performance. Under Debug mode, switch Enable Debug Mode to Yes and Save. Reproduce and collect the profiler data at the bottom of the footer of our website. This will provide a lot of insights you may not have already collected.

this looks legitimate. Did you check other hooks? Also enable debug mode and replicate issue and make sure to check error log in hosting.