Leaderboard

Salut, Vous pouvez faire ce qui suit: Résolu de cette manière: 1) Effacez le cache à l'aide de la commande appropriée dans Paramètres avancés> Performances 2) activer le débogage (paramètres avancés> performances) 3) Rechargez ou ouvrez la section Modules (Modules> Module Manager) 4) Effacez le contenu du dossier / var / cache / (en utilisant FTP) IMPORTANT: vous devez supprimer les dossiers / dev et / prod (via FTP) 5) Supprimer le mode de débogage C'est tout. Revenez à la section Modules et essayez de désactiver ou de désinstaller un module, cela devrait fonctionner. Remarque: parfois en activant le mode de débogage, nous pouvons recevoir une page d'erreur avec la liste des exceptions. Cela rend impossible de voir le back-office. Dans ce cas, il est nécessaire d'éditer manuellement le fichier de configuration à la ligne 29: /config/defines.inc.php De: define define('_PS_MODE_DEV_', true); à: define('_PS_MODE_DEV_', false); Faites-moi savoir si cela fonctionne!

Happy that I could help. In case you need further advice - that's why the forum is there Good luck!

Bonjour à tous Sur PS 1.7.5.0, impossible de changer l'ordre des moyens de paiements. En changeant l'ordre sur Positions, ça ne change rien sur le FO (thème classic). => les modules de paiements sont affichés dans l'ordre des ID de module. J'ai regardé dans la bdd, la table hook_module a bien enregistré les bonnes positions. Je n'ai pas trouvé à quel endroit dans le code, cet ordre est oublié. Si vous avez une solution, je suis preneur ! Rien vu sur le bug tracker à ce sujet

Hi, you can try this module: https://www.prestashop.com/forums/topic/513306-module-accessories-in-add-to-cart-popup/ Or maybe this one:https://addons.prestashop.com/en/cross-selling-product-bundles/16122-cross-selling-in-modal-cart.html Just letting you know that I have nothing to do with these modules, just found then for you, so you can use the accessories feature of Prestashop for this. Kind regards, Leo

Hi, Who build that custom module?

Hi, I'm glad that it worked out, you can mark the thread as solved by prefixing the name of the thread with [SOLVED] Kind regards, Leo

Díky za přístup. Ok, máš to hotové. 😎 2 minuty 😉

Well, this one is pretty simple. A user interacting with your store is unlikely to give you a fake email. If he has the intention to buy something, why should he give you the wrong email when in the end, you have his mail address? If you're operating an online community, that is a very different topic because, in that case, you have nothing to identify a user, and then email verification makes sense.

Why not? Distance between key words plays no role in the Prestashop search algorithm. And as all products have the same weight for those keywords the determining factor becomes the way they happen to be stored.

Amazing!! Thanks you @Daniel Tengler

for some time, last few years we moved several clients to elastic search, here are addon'S for 1.6 https://addons.prestashop.com/en/search?search_query=elastic&compatibility=1.6.1&

First of all, that "2" in "Mavic 2" won't work. Prestashop has a minimum length of 3 positions. The logical approach would be to increase the search weight of the main product. But of course that will be hard when you have the weight for description, tags, etc set to zero.

Hola mira que la web trabaje en php 7.3

Bonjour Il ne faut pas installer PrestaShop via le module en 1 clic d'ovh mais plutôt manuellement. Voici un guide qui pourrait vous aider https://www.prestashop.com/fr/blog/installer-prestashop ou pour ovh https://docs.ovh.com/fr/hosting/installer-manuellement-prestashop/

Hi, I've solved the problem by just removing the news.yml file in "src/PrestaShopBundle/Resources/config/services/adapter/" if you get an error after removing that file replace the whole src map from Prestashop 1.7.6.9 download. When you restore your server the files are overwritten but new created files will stay on your server.

I've never done this before and so it took me sometime to figure it out, but I did manage to finally get a cron job setup and working for 1.7.6 that updates the exchange rate once per day. So for anyone else new to this, this is what I found. 1. I discovered that there is a "cron_currency_rates.php" file in the "admin" directory which I used my hosts file manager to find. 2. In my hosts cpanel I created a cron job pointing to this file that runs once per day. I just selected the once per day common option available in my cpanel. 3. It did not work until I added a "secure_key" to the end of the command, i.e. /usr/bin/php /home/USER/domains/DOMAIN/public_html/admin/cron_currency_rates.php secure_key=SECURE KEY GOES HERE. Your exact location will likely be different.There must be a space before "secure_key". 4. I had to figure out how to find my "secure_key" and so I realized that in the "cron_currency_rates.php" there is this code that creates the key and compares it against the key passed in during step 3: $secureKey = md5(_COOKIE_KEY_.Configuration::get('PS_SHOP_NAME')); 5. First, I put my store in maintenance mode. Then, to find this key I created this code: print_r("secure_key="); print_r(md5(_COOKIE_KEY_.Configuration::get('PS_SHOP_NAME')) ); Then I put it in the "index.php" file in the "admin" directory just after the line: require _PS_ADMIN_DIR_.'/../config/config.inc.php'; This displayed the "secure_key" just above the header on my dashboard 6. I copied the key and replaced the "SECURE KEY GOES HERE" in step 3. Then I went back to the "index.php" and DELETED the code in step 5. I now have a working cron job that updates the exchange rate once per day. Hope this helps someone.

The project Core Web Vitals from Google has announced that loading time and performance will have an impact on the website ranking in search results. Google mentions lazy loading in their suggestions. Lazy loading will be available on Classic Theme in version 1.7.8 thanks to Progi1984 and it will definitely improve both user experience and loading time on your site! What is lazy loading ? Lazy loading is a technique that defers loading of non-critical resources at page load time. Instead, these non-critical resources are loaded only when needed. For example, images which are at the bottom of the page are less critical than images at the top of the page and should consequently be loaded later. This feature used to be provided by third party plugins or modules but is now supported natively in all modern browsers. How can I enable native lazy loading on my theme ? Browsers use the loading attribute on the <img> tag to defer loading of images that are off-screen until the user scrolls near them. Consequently on all your <img> tags, you must set a loading attribute with value lazy. And it’s done. What browsers support this feature ? This information can be found on multiple sources, such as “Can I Use”. In 2020, native lazy loading is enabled on 68% of used browsers. And if the feature is not active on the browser, images will be loaded as usual. PrestaShop Classic Theme performance analysis At first, we considered using Lighthouse which is an open-source, automated tool for improving the quality of web pages. But after a few attempts, we encountered an issue in Lighthouse that prevented us to do so. It turns out the detection of lazy loading images is only performed in heavy pages (min 5000px). Core developer Progi1984 chose to use the Google Chrome console and its Network tab in order to show you the performances evolution before and after lazy loading usage. This test is based on the New Products page with 50 products (and so 50 images minimum) per page. The benchmark is performed on develop and lazyloading branches. First scenario is performed against develop branch. Two measures are performed: the first on desktop mode with no throlling the second on emulated device “iPad Pro” mode with Fast 3G throlling Second scenario happens on lazyloading branch. Two measures are performed again: the first on desktop mode with no throlling the second on emulated device “iPad Pro” mode with Fast 3G throlling A gain of 21% to 28% can be observed with lazyloading. You are left to imagine the possible gains for users who browse your websites all around the world, with different connections profiles. Conclusion As a developer or theme provider, implementing this feature is a very good investment. The implementation is easy and the gain is huge is all we have to say. View the full article

Updated New Version V4 WhatsappV4.zip

HI guys I've had the same problem. It seems to be due to a wrong cache. Solved in this way: 1) Clear the cache using the appropriate command in Advanced parameters> Performance 2) enable debugging (Advanced parameters> Performance) 3) Reload or open the Modules section (Modules> Module Manager) 4) Clear the contents of the / var / cache / folder IMPORTANT: you must delete both / dev and / prod folders 5) Remove the debug mode That's all. Go back to the Modules section and try to deactivate or uninstall a module, it should work. Note: sometimes enabling the debug mode we may receive an error page with the list of exceptions. This makes it impossible to see the back office. In this case it is necessary to edit manually the configuration file al line 29: /config/defines.inc.php From: define('_PS_MODE_DEV_', true); to: define('_PS_MODE_DEV_', false); Tested on Prestashop 1.7.6.4

Bonjour, J'ai été confronté au même problème (toujours pas corrigé dans la version 1.7.6.4. ) Pour ceux que ça intéresse, il existe une solution quasi officielle (puisqu'elle a été publiée sur Github) : https://github.com/PrestaShop/PrestaShop/pull/15632 Il faut mettre à jour breadcrumb.tpl : <nav data-depth="{$breadcrumb.count}" class="breadcrumb hidden-sm-down"> <ol itemscope itemtype="http://schema.org/BreadcrumbList"> {block name='breadcrumb'} {foreach from=$breadcrumb.links item=path name=breadcrumb} {block name='breadcrumb_item'} {if not $smarty.foreach.breadcrumb.last} <li itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> <a itemprop="item" href="{$path.url}"><span itemprop="name">{$path.title}</span></a> <meta itemprop="position" content="{$smarty.foreach.breadcrumb.iteration}"> </li> {elseif isset($path.title)} <li> <span>{$path.title}</span> </li> {/if} {/block} {/foreach} {/block} </ol> </nav>

Hi, For optimization issues you should add the file in the "javascript" block instead of the "page_content_container" block. {block name='javascript_bottom' append} <script src="https://assets.calendly.com/assets/external/widget.js"></script> {/block}

Hi. I was forced to turn on basic stock management so that the PS system would display "out of stock" and "in stock" icons. Now I was wondering if there is a way to prevent the system from deducting inventory quantities after a sale? For example, right now, if I have a product quantity of 10 and a customer orders 1, the stock then is 9. And so forth until it reaches 0 and is "out of stock". My store does not have an inventory. All sales get passed on to a fufillment service, so I would like to DISABLE the -1 that happens after a sale. Right now my work-around is to set quantity for every product to a high number like 9999 which will take a long time to sell out. Then if my fulfillment centre says they ran out of a particular product, I will manually set it to 0 so that it says "Out of Stock". Does this make sense? Does anyone have alternative strategies to share, when using a third party fulfillment service? Is there a setting in PS somewhere that I did not see that will control whether sales deduct stock quantities automatically or not? Thank you! PS 1.6.1.9

exécutez cette requete sql dans votre phpmyadmin DROP TABLE IF EXISTS `ps_paypal_capture`; CREATE TABLE `ps_paypal_capture` ( `id_paypal_capture` int(11) NOT NULL AUTO_INCREMENT, `id_order` int(11) NOT NULL, `capture_amount` float NOT NULL, `result` text NOT NULL, `date_add` datetime NOT NULL, `date_upd` datetime NOT NULL, PRIMARY KEY (`id_paypal_capture`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

themes\classic\templates\_partials\header.tpl Find <div class="col-md-2 hidden-sm-down" id="_desktop_logo"> <a href="{$urls.base_url}"> <img class="logo img-responsive" src="{$shop.logo}" alt="{$shop.name}"> </a> </div> Replace <div id="_desktop_logo"> <a href="{$urls.base_url}"> <img class="logo img-responsive" src="{$shop.logo}" alt="{$shop.name}"> </a> </div> and add style css in file - theme.css #_desktop_logo { text-align: center } #_desktop_logo a{ display: inline-block; }

Tak tento problém je nakonec dohledatelný v opravách, ale zatím jen pro dev strom toho modulu viz https://github.com/PrestaShop/ganalytics/pull/91 má to více uživatelů přesto oprava zatím nebyla uvolněna do masteru... prostě presta Pokud to váš problém vyřešilo odkažte na opravu z vašeho PR na gitu případně ho uzavřete.

I had this same problem but solved it by NOT using an underscore in the Link Rewrite field. e.g. instead of share_the_love_for_prestashop_1_6 try share-the-love-for-prestashop-1-6 It solved it for me.