Leaderboard

8.2, dar în ambele cazuri este mai bine să faci o instalare curată și să migrezi datele. În orice caz, dacă faci o instalare curată sau actualizezi, dezactivează modulele personalizate, treci la tema clasică și fă o copie de rezervă înainte de orice acțiune.

@Nickz Ich werde jetzt Thirtybees austesten. Ich habe die Nase im Moment von Prestashop voll. Seit der PHP Version3 (?) arbeite ich damit, aber so viele Probleme und auftretende Fehler habe ich noch nie in einem Script erlebt. Ob ich da etwas falsch mache oder nur derjenige bin der das Pech hat ausgerechnet den Punkt zu treffen, an dem ein Fehler sitzt - ich weiß es nicht. Ich habe auch im Moment keinerlei Antrieb mehr, noch mehr Arbeitszeit in dieses System zu investieren. Dank an alle, die versucht haben mir zu helfen! Norbert

We have some developers working under Windows 10 and 11, with Wamp or Xamp, and it works normally. First all, if you have antivirus as said @El Patron deactivate it when running sites, or put in white list apache, mysql, mariadb, php executables. Change realpath_cache_size size in php.ini to a large value like: realpath_cache_size = 5M Also make sure you mariadb or mysql settings are corrects especially for innodb.

Um Gottes willen, nicht auch noch erhöhen, 8.2 ist schon nicht kompatibel, da funktioniert zwar vieles, aber es treten halt auch Fehler auf, Prestashop 8.2 läuft maximal mit PHP 8.1!

Salut! NU UPGRADE. Fa-i site-ul de la 0, recomandarea mea, mergi pe ultima versiune de la 8. Dupa aceea, preluare de date din cel vechi in cel nou. (comenzi, cosuri, clienti....etc).

Guten Tag Norbert Erstmals wäre es sinnvoll den Titel Deines Beitrages so zu ändern, dass man versteht um was es geht. Weil generelles geplärre ist einfach nicht hilfreich. Wenn Du ohnehin neu startest, lade Dir gleich die Version 9 hoch, die 1-Click-Upgrade funktion ist da nicht immer erfolgreich. Grundsätzlich wenn Du ein Problem mit ein Theme, Modul, Override oder einen fiver Programmierer hast, wird der immer sowohl per FTP als auch per User als Admin zugreifen müssen, denn er muss sich ja die Originalfiles ansehen. Wenn Du Dich in Prestashop nicht auskennst, ist für Dich ohnehin Feierabend. Also kannst Du dem Programmierer gleich FTP zugang geben. Mach zuerst ein Backup von der DB + Webspace auf Deinem server, und hoffe dass alles gut geht. Du hast eh keine Alternativen. Also fangen wir nochmals neu an: Welche PS hast Du, welches Theme hast Du, und was genau willst Du eigentlich machen. Schicke ein Link bitte von Deinem Shop, sonst sind wir hier alle blind unterwegs.

Hi this is a basic edition?

There are no defined standards for this. It really depends on the organization or platform. I’ve personally lost access to downloads on popular platforms like ThemeForest as well, when items were disabled or removed by the sellers. Usually, the free support period (3–6 months) is considered sufficient time to download the module and keep a backup on your end. Ideally, you should keep the backup with you.

I developed the module “Merge Carts – Prevent Lost Shopping Carts on Login” that elegantly and efficiently solves this issue. If a customer adds items as a guest and then log in, this module intelligently merges the old saved cart with the new cart. The module “Merge Carts” fixes the default behavior of replacing one cart with the other upon login. Simply no more lost carts. Get the module — The module “Merge Carts” is available at: https://addons.prestashop.com/en/social-login-connect/96287-merge-carts-prevent-lost-shopping-carts-on-login.html Demo — You can try the demo at: https://www.bulletproof.se/_demos/mergecarts/ (btw, the demo is darn easy to use. It's got some cool features, and it's super easy to create an account and log in). Video — I explain the logic of how PrestaShop handles carts and how the module “Merge Carts” will fix it in this video: https://youtu.be/mXKQUnPAjw8

Solved! Posting the fix in case it can help somebody in a similar situation. There was an update of MariaDB on the servers, and this issue might have been related to it. Using the debug mode on the backend page it threw an 500 error related to the blockwishlist module. Hosting support fixed it. After that the dashboard was accesible but the 500 error kept popping up in the order panel, related to the paypal module. That got fixed when i uninstalled it. I assume it will get fixed when I get the updated version to reinstall. After that I cleared the prestashop caché using the terminal in cpanel. In any case, the error was related to some updates on the server and some modules broke and crashed the dashboard and other pages on the backend.

I think PS1.6 supports PHP7.1 only, while Prestashop8 requires PHP7.2 onwards. So I believe a direct upgrade will not be possible using the 1Click upgrade.

First is make a backup ( better is to have full copy, clone and test update there ). Also disable all custom modules and switch to classic theme before. You can have issues after update with opening orders, client pages. That can be fixes in data base. To be honest is better to install clean 8.2 and migrate the data. As most probably theme and custom modules wont work on new version, so even if your update will be completed you need to start from scratch.

Buenos días, Con todo el respeto, pero creo que estás equivocado o leyendo mal. En primer lugar, aquí no se está hablando de una solución gratuita, si no de un modulo de un pago único. En segundo lugar, has visto los precios de esas "míseras" subscripciones? Eres autónomo o una pyme? Si lo eres sabrás que hoy en día para todo hay que pagar una "misera" suscripción, suma suma suma y hablamos de lo que duele otra "misera" suscripción. En tercero, todo lo que sea impuesto por ley y que obligue a hacer algo debería estar subvencionado o ser gratuito ya que es una obligación, no un derecho al que acogerse si uno quiere, por lo que el propio gobierno debería poner a disposicion las herramientas de una forma sencilla y gratuita para que todas las empresas, incluidas autónomos y pequeñas empresas, puedan ajustarse a la normativa sin arruinarse en el camino. Y es que no es una "misera" suscripción más, es que esto es constante y no deja crecer ni respirar a autónomos y pequeños comercios entre unas cosas y otras... "Acaban" de salir dos normativas, la factura electrónica y la obligatoriedad de que las webs dispongan de un "simple botoncito" que permita cambiar todo el estilo de la web y alguna que otra funcionalidad para que sea accesible a todos los públicos, y cuando no es una es otra, y hay que pagar por todo (a nivel fiscal, a digital, a nivel social... Dentro de poco hasta por respirar), y si suben los precios pierden clientes por k el servicio/producto es caro, y competir con las grandes empresas ya es casi imposible y lo que no está impuesto hay que hacerlo "obligatoriamente" si quieres salir adelante. Mi madre, por ejemplo, que tiene una empresa familiar de limpieza de portales con tres empleados y que tiene un crecimiento muy moderadoDespués de todos los pagos (IRPF, autónomos, material, sueldos, seguridad social, iva, gastos de web, empresa de riesgos laborales, empresa de seguro laboral, abogado, gestoría, ditgitales, "míseras" suscripciones, etc etc etc) después de un año de trabajo tiene un beneficio neto de 3000€ y por ello tiene que pagar 900€ de impuesto de sociedades de ese beneficio... Pues si, cualquier nueva "misera" suscripción duele y más si es por algo impuesto. Y ella intenta no defraudar, ser legal y lo declara todo, pero es que de verdad que no lo ponen fácil, viendo esto luego nos sorprendemos de que haya empresas que hagan cosas en B ... Y si te dejas un pago sin hacer por qué no tenías dinero te acribillan a intereses (k ni un banco usurero llega a ellos) y como no pagues es tu perdición y a las grandes empresas le perdonan más de la mitad de las deudas que tienen para que paguen algo... Mucho apoyar al comercio local y todo eso que queda tan bonito pero luego a la hora de la verdad ....

Rendez-le vide au lieu de null. OU effectuez une sauvegarde de la table d'adresses et exécutez la requête suivante dans la base de données. UPDATE `ps_address` SET address2 = '' WHERE address2 IS NULL; Assurez-vous que le préfixe de la table est correct dans la requête en fonction de votre préfixe d'installation.

Utilisez PHPMyAdmin et accédez aux tables de devises. Vérifiez la valeur dans la colonne « précision ». Il doit s'agir de valeurs entières comme 1 ou 2, etc. Ou essayez d'installer avec une autre version locale (États-Unis, etc.). Ajoutez ensuite la devise ultérieurement.

Téléchargez depuis la page de configuration du module et installez-le sur la source Prestashop.

Hola Puse ese post

En los assets puedes encontrar el XML correspondiente: https://github.com/PrestaShop/PrestaShop/releases/tag/8.2.3

Using SMTP OR the default server email? If SMTP, have you checked if there are no restrictions on the "from email ID". "From email ID" is the same on PS8 & 9?

Vérifiez la base de données pour la table ps_address et voyez si address2 a des valeurs NULL dans les adresses.

little late for the party but since you answered 6 months later, then I will have elementor as part of theme is helpful. I've had many great successes using Leo Themes in the past, before warehouse, panda, transformer...they originally came from Joomla, which is a 'very' good platform, still is but not as popular as it once was. https://www.leotheme.com/prestashop/themes.html

https://prestaheroes.com/blogs/mysql-optimization/how-to-calculate-the-right-innodb_buffer_pool_size-for-prestashop-on-mysql-8-0

En estos momentos no nos queda más opción que este tipo de servicios

De estos sitios ya hay muchos, pero es lo que hablamos, en todos los casos tienes es una opción de pago mensual.

welcome to community tested looool ps_checkout has been a nightmare, I made a lot of money with client intakes of broken checkout...we just removed it...you should consider the same unless ps has no other option for the payment gateway you use.... Yep—this is a real bug in the latest ps_checkout update (rolled out around Aug 22–25, 2025). Multiple shop owners are reporting the exact same crash on the Back-Office/FO with this stack trace pointing at the module’s English XLIFF file: modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf (XLIFF parser: “source element not expected”, Error 1871). prestashop.com+1 Here’s the quickest way to get the site back up and keep ps_checkout usable: Restore access (if you’re locked out): via FTP/SSH, temporarily rename the module folder: modules/ps_checkout → modules/ps_checkout.off (site comes back). prestashop.com Target the bad file only: put the module folder name back to ps_checkout, then delete this file: modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf. Several users confirm the module will run without that file. prestashop.com Clear cache: delete var/cache/prod (and var/cache/dev if present). Reload Back-Office and test checkout. Why it breaks (short version) The shipped en-US XLIFF is not schema-valid for what Symfony’s XliffFileLoader expects in PS 8/9—hence the “[ERROR 1871] … source element not expected” crash during cache warm-up. Removing or replacing that one file avoids the fatal. prestashop.com let us know how that works for you!

Hola te adjunto el modulo que necesitas de la version 8.2.1 @DaniMH ps_edition_basic.zip

@SchmidtSon I had a similar problem, on Prestashop 1.7.7.8 . I solved it by editing the file classes/hook.php, in lines 483 - 484: $results = Db::getInstance(_PS_USE_SQL_SLAVE_)->executeS( 'SELECT h.id_hook, h.name as h_name, title, description, h.position, hm.position as hm_position, m.id_module, m.name, active Just changed active by h.active, like this: $results = Db::getInstance(_PS_USE_SQL_SLAVE_)->executeS( 'SELECT h.id_hook, h.name as h_name, title, description, h.position, hm.position as hm_position, m.id_module, m.name, h.active

Hello, just a note for 1.7.7.x search a lot time for find this almost all admin files chanced src/Core/Grid/Query/OrderQueryBuilder.php find private function getCustomerField() { return 'CONCAT(LEFT(cu.`firstname`, 1), \'. \', cu.`lastname`)'; } replace private function getCustomerField() { return 'CONCAT(cu.`firstname`, \' \', cu.`lastname`)'; } bests...

This problem is most of the times related to SSL issues. If you have HTTP to HTTPS redirects enabled while there is some other setting which redirects a https request to an http webpage, hen you will get this error. For example, if you have HTTP to HTTPS redirects enabled, but you have a setting in .htaccess which redirects like this: Redirect 301 * http://<DOMAIN_NAME>.com/ Or if you see some other settings in there which redirects to a http page. That's most commonly related to this issue in my opinion. Next is if you for example use Cloudflare. Cloudflare has 4 SSL options: 1. "Off (Not Secure)" 2. "Flexible" 3. "Full" 4. "Full (Strict)" What SSL setting should I use? This setting controls how Cloudflare’s servers connect to your origin for HTTPS requests. We recommend enabling the Full SSL (Strict) setting if possible. Common use cases for each are: Off: No visitors will be able to view your site over HTTPS; they will be redirected to HTTP. Flexible SSL: You cannot configure HTTPS support on your origin, even with a certificate that is not valid for your site. Visitors will be able to access your site over HTTPS, but connections to your origin will be made over HTTP. * Note: You may encounter a redirect loop with some origin configurations. Full SSL: Your origin supports HTTPS, but the certificate installed does not match your domain or is self-signed. Cloudflare will connect to your origin over HTTPS, but will not validate the certificate. Full (strict): Your origin has a valid certificate (not expired and signed by a trusted CA or Cloudflare Origin CA) installed. Cloudflare will connect over HTTPS and verify the cert on each request. And last one you can check is for when you get this error while you did just install Prestashop. 1. Try to log in to the backend via: https://<my-domain.com>/Backoffice/index.php 2. In PrestaShop Backend, click Shop Parameters (under Configure) > General. 3. Click "Yes" next to Enable SSL and click Save to apply the changes. 4. Then click "Yes" next to Enable SSL on all pages and click Save to apply the changes.

Prestashop 1.7 Ürünü Yıldızlarla Beğenme ve ürüne yorum ekleme Modülü. https://mypresta.eu/modules/advertising-and-marketing/free-product-reviews-comments.html

Wow this forum is so alive, thank you Prestashop!