Leaderboard

ok, it works👍... Thanks again for the help

Hello, Ok, this makes more sense now. In your ps_facetedsearch module's configuration, in the template used, you are most likely having Search (experimental) checked in the Pages using this template: section. The problem seems to be the fact that ps_facetedsearch does not execute the actionSearch hook. If you uncheck that option, the default search class will be used in the search page, and this class does implement the hook, so you should start seeing the search keywords inserted into that table.

It is online again. I found that the problem was a bit wider. The new version - 1.36m - should solve it.

Hello, In PrestaShop9 you can still create an assets/css/custom.css file in the themes/<theme-name> directory, and, as you can see here, the FrontController will add it to the front store pages. The caching does seem to be handled a little bit different, especially for the Hummingbird theme. You will actually need to go to Advanced Parameters -> Performance and clear the cache, in order to see the changes. For speeding up development, you can disable the Smart cache for CSS (in the same Performance page) and on refresh you should see the changes.

@El plan de Dan Me parece inadecuado que, en lugar de moderar y aportar al foro, se utilice este espacio para atacar a PrestaShop y promocionar servicios personales. Yo estoy aquí para colaborar y ayudar a otros usuarios, no para entrar en conflictos. Le ruego que deje de dirigirse a mí de manera insistente, ya que me siento acosado y perseguido. Si tiene algún desacuerdo con PrestaShop, no lo traslade contra quienes participamos de buena fe en la comunidad. Mantengamos el foro como un lugar de respeto y apoyo mutuo, que es lo que realmente beneficia a todos los usuarios.

Bonjour, Je ne suis pas contre l’idée du Wall of Fame, mais alors vraiment pas en gros dans le menu général d’un backoffice de ecommerce, ça n’apporte rien pour le bizness, rien pour l’usage, ça surcharge le menu et nuis à l’UX pour rien. Et en termes de crédit pour les contributeurs, un énorme placard du genre a tendance à avoir tout l’effet inverse. Par ailleurs, je ne crois pas être le seul que ça ennuis : https://github.com/PrestaShop/ps_distributionapiclient/issues/62 Ne faites pas la bêtise de désactiver le module ps_distributionapiclient, si ça désactive le Wall of Fame, ça désactive aussi les mises à jour des modules natifs de Prestashop. Faites plutôt cette requête SQL pour le masquer : UPDATE ps_tab SET enabled = 0 WHERE class_name = 'AdminPsdistributionapiclient'; Vous pourrez toujours y accéder depuis cette url : https://votre-site.tld/adminrandom/modules/ps_distributionapiclient/top-contributors?_token=votretoken/ Et pour le réactiver : UPDATE ps_tab SET enabled = 1 WHERE class_name = 'AdminPsdistributionapiclient';

I also added if (strlen($params['expr']) < 5) { return; } to avoid strings under 5 characters that aren't meaningful for the site.

Hello, Oh, yes, that's how it was working in PrestaShop 1.7.x too. Both the preview and the search page will add entries to that table Glad I could help

Hello, Since this is experimental, you would expect things to be missing. You can manually fix it for now. You can edit modules/ps_facetedsearch/src/Product/SearchProvider.php and on line 197 add the following: \Hook::exec('actionSearch', [ 'searched_query' => $query->getSearchString(), 'total' => $productsAndCount['count'], 'expr' => $query->getSearchString(), ]); If it's inserting things twice, this means the hook is called twice, although it shouldn't. Did you add it for debugging somewhere in the code and forgot to remove it?

..it even writes two lines for research now 🙂 it seems he has to make up for lost time

Hello, displayHead is not needed. The statssearch module makes use only of the actionSearch and displayAdminStatsModule hooks Some things that you should watch for: 1. Check the `ps_hook` table and make sure that active is set to 1 for actionSearch. You can also add position 1 (to the same row) if it's not already set (SELECT * FROM `ps_hook` WHERE name = 'actionSearch';) 2. Make sure there are no overrides (or direct code changes) for controllers/front/listing/SearchController.php, src/Adapter/Search/SearchProductSearchProvider.php and modules/statssearch/statssearch.php. If there are, you should check the code for them in GitHub and make sure you are not touching the execution of the actionSearch hook

@willsmith79052 is exactly the correct Google only allows review markup when the rating refers to the primary topic of the page. @AcidLava maybe say thank you for his response? if you question someone's answer, especially on this topic, you could have easily find google's recommendations and that mixing reviews on non relevant page will get you penalized.

LOL, it's so funny. "E82CV371_2C" (model number of a product I sell) was mentioned in this thread and voila - when you search for "E82CV371_2C" you now get link to this thread on the first page of google results. Completely nonrelevant search result for anyone searching for "E82CV371_2C" who is interested in the product. Still, absolutely relevant product page in my eshop is not present in the search results. Hard to understand what's wrong with Google.

Let me know what problems you have with this module, and i am more then happy to help. (even though i guess you simply posted this to promote your own *paid* module)

I forgot, the best fishng lure? apple/amazon/little bit google....paypal instant pay. what is the best checkout? no checkout....when you pay with with instant payments, the automatically create account if none exists and updates orders after they pay via one of these 3 parties. it's not always easy in ps because you have to buy 3 modules (I don't use prestashop checkout as it can be limiting)...then on product/view cart/checkout(top) you offer instantpayments. then..we will wait to see if ps will update to offer agenic payments, i.e. via AI...however this is initially (last I heard) in US only.

When you download something from Github it automatically renames it to the branch you download it from, and in this case that is the "main" branch. But to answer your question, yes the version from Github and the first post of this topic are still the latest. I would advice you to simply download the the zip file from the first post.

I found the answer. exec() was not enabled on the server.

Merci Eolia. Ce que je ne comprends pas , c'est pourquoi le montant frais de port bugg alors que c'est quand même toujours la même adresse FRANCE

Hey Ritter,..italian here, but i manage international shops so it's the same everywhere. You need to create states inside a country...than you create a zone "Sicilia" and you assign states to this zone. If you import italian language maybe you get also states otherwise you have to create manually...But then you have also activate it in country address configuraion, i mean "It needs states?"...Yes. For Sicily zone you have to create 9 cities ( states)...check the picture i've attached Prestashop uses zone for calculate shipping so it's easy to configurate in alla countrries adding "states",,,but i can also filter by Zip-code is neccessary with a module, so the precision is even better because we have some states with different shipping costs!!:-))... i dont's speak Deutsch...let's see if understand..lol Hey Ritter, ich bin Italiener, aber ich betreue internationale Shops, daher ist es überall gleich. Du musst innerhalb eines Landes Bundesländer anlegen. Dann erstellst du eine Zone „Sizilien“ und weise dieser Zone die Bundesländer zu. Wenn du Italienisch importierst, werden die Bundesländer möglicherweise automatisch hinzugefügt. Ansonsten musst du sie manuell anlegen. Anschließend musst du sie aber auch in den Adresseinstellungen des Landes aktivieren. Ich meine, „Braucht es Bundesländer?“ … Ja. Für die Zone Sizilien musst du neun Städte (Bundesländer) anlegen. Sieh dir das beigefügte Bild an. PrestaShop verwendet Zonen zur Berechnung der Versandkosten. Daher ist es einfach, die Bundesländer in allen Ländern durch Hinzufügen von Bundesländern zu konfigurieren. Ich kann aber auch nach Postleitzahl filtern, was mit einem Modul erforderlich ist. Dadurch wird die Genauigkeit noch besser, da einige Bundesländer unterschiedliche Versandkosten haben! :-))

This question I felt needed a proper answer so I wrote a blog post based on my experience, I hope it helps. https://prestaheroes.com/blogs/prestashop-alerts/the-on-page-seo-checklist-for-modern-prestashop-stores

Why?

Just to toot my own horn for a second (because nobody else will, jajajaja)… here are two performance modules I built for in-house clients. They do one thing, and they do it extremely well: they add preloads for .css and .js directly in the page header, which significantly improves above-the-fold rendering. This isn’t magic or “voodoo” caching… you can Google all day about how preloads work, why they’re recommended by Google and the IETF, and why this method is one of the cleanest, most reliable ways to speed up initial render. CSS Pro https://prestaheroes.com/collections/prestashop-performance-modules-services-speed-up-your-store/products/csspro-eliminate-render-block-css JavaPro https://prestaheroes.com/collections/prestashop-performance-modules-services-speed-up-your-store/products/javapro-javascript-performance-manager

USE OF CCC: Be careful here. Make sure that on each page type (index, category, product, etc.) the theme###.css and theme###.js filenames are the same across all pages. (Check using “view source”.) If the filenames differ, then you should disable CCC for one or both. Otherwise you end up duplicating files that are already in the browser cache, which defeats the purpose of CCC. At one time I built a module to solve the .css side, but I could never fully resolve it for .js (not for lack of trying). I'm not suggesting you buy anything, but the documentation explains the CCC issue well and how to check whether it’s working as intended. yes, experiment with child theme but note: classic/hummingbird have just enough features to build a product catalog, define shipping, payments, discounts etc. But lacks extended feature you get with a high quality 3rd party theme from addons if you want a modern front end. have fun and back up back up back up.

El Patron - it's working and without declaring in theme.yml (maybe it's giving some advantage in something...) Enough what Andrei suggested and I tried it before asking, just was used to older ps versions when opening 'Inspect(Q)' in your browser, you see that some settings for element are used from 'theme.css' and some from 'custom.css'... And as just to try I put empty 'custom.css' file, loaded the shop and used 'Inspect' hoping to see that settings are coming from 'theme.css' and 'custom.css', I saw a css file loading from cache directory... With PS9 it uses css file from .../themes/classic/assets/cache/theme-86112d.css ... Think this file is a blend of 'theme.css' and 'custom.css'... It just comes a bit more complicated to edit the styling not knowing all the element names as this 'theme-xxx.css' ajusted for saving sapce removing all spaces and all settings sit in one line 119.. Think time came to learn making child theme 🤔

What is Social Media Markerting? How to get in to this?

"Warning: mysqli_connect(): Headers and client library minor version mismatch. Headers:30308 Library:30407 in /home/.../DC_Prestools_Suite/login1.php on line 381" That is a server problem. Not a Prestools problem. You should ask your hosting provider about that. They may have made an error while upgrading some php module. Quite probably your Prestashop installation suffers similar problems. The difference is that Prestools is built to bring out any problem immediately in the open so that it can be solved while Prestashop gives priority to giving the user a smooth experience while hiding problems - hoping that they are not serious. BTW: when you report errors in Prestools please do that for the latest version. That way your line numbers will match with what I see.

Σε ευχαριστω, αλλα το εχω φτιαξει .

Hello, Does anyone know how do I redirect the whole prestashop from domaninA.com.br to domainB.com.br using redirect 301. Using prestshop 1.6. I really have no ideia what i am doing here. First time doing this kind of thing. Really need baby steps here. If anyone can help Thank you.

If you sell unique products using store level review JSON-LD on every page can be risky for SEO. Google prefer product specific reviews on product pages. Best approach: Strong review schema > Homepage and about page Product review schema > Only on product pages Avoid duplicate or misleading structured data This keeps everything accurate for Google and helps build trust safely.

Multumesc frumos!!! FUNCTIONEAZA

Sorry for the basic question but I'm setting up a new site and want to get it right... Should the default product category be 'Home', so the page sits closer to the root? They will still be sorted into other categories for ease of navigation. I am under the impression that pages closer to the root perform better in search results. Hope someone can offer advice Thank you for any help!

Je suis d'accord sur le point 1, il est préférable de laisser les testeurs et experts se casser les dents sur les nouvelles version majeurs et surtout attendre que les développeurs de thème et module mettent à jour leurs productions pour les rendre parfaitement compatibles et optimisés pour la V9. Pour le point 2, je ne suis pas d'accord. Oui, une installation avec une version non supporté de PHP ne va pas s'arrêter du jour au lendemain mais à partir de moment où elle n'est plus supporté, il n'y a plus de patch de sécurité. Si une faille critique apparait, votre site devient vulnérable, avec les risques que ça implique sur son business (perte de commande en cours, toujours génial pour la facturation, interruption de service le temps de mettre à jour le site, envoie de spam en son nom, arnaque depuis le serveur, et l'image de marque, j'en parle même pas), et sur la confidentialité des données client (avec ce que ça implique du genre arnaque ciblé, etc). Et dans le cas présent, PHP8.1 n'auras plus de mises à jour critique (de sécurité) dans un mois. Pour rappel, des failles de sécurité, il y en a toutes les semaines. Et c'est aussi le cas sur Prestashop. Et quant aux hébergeurs qui font payer pour des version antique de PHP, il y a peut-être une raison ? Comme le fait d'avoir du support prolonger sur ces version, avec des patchs de sécurité maison ?

Ok, thanks, i though were stable versions as appeared in the normal update process. I just tried this in a test website so there were no problem, i restored the backup and i will wait for the future. Best regards.

El Patron, thanks for help, but presta 9 refuses from running properly on my linux machine (as I mentioned somewhere before even presta 9.0.0 was running fine on windows machine) mode rewrite is running. Think if this module would not be running my presta 8.2 on this same localhost (just other folder) will have problems, but it's running fine. .htaccess is in admin873... and in admin-api folders.... Always thought that it is a program (aka presta) is saying for Apache where to look for something. There's no login folder in admin folder so there's no chances to find it. And same Apache is looking for favicon file in wrong place and can't find it (another Apache or presta problem?)

⚽ CF Football Bypass for PrestaShop PrestaShop module that automates the switching between **Proxied** and **DNS Only** modes in Cloudflare when mass blocking is applied during football matches. The module obtains the [hayahora.futbol](https://hayahora.futbol/) feed and activates/deactivates the selected DNS records to keep your legitimate store accessible, with a configurable cooldown period before reactivating Cloudflare. --- 🚀 Quick Installation 1. Download the ZIP file from https://github.com/JoseManuelPedraja/cf-football-bypass-prestashop/releases 2. Copy the `cffootballbypass` folder to your PrestaShop modules directory. 3. From the PrestaShop **Back Office**, go to **Modules > Module Manager** and activate **CF Football Bypass**. 4. Configure the module in **Advanced Parameters > CF Football Bypass**, where you can adjust: - The check interval - The cooldown period after deactivating Cloudflare - The DNS records you want to manage --- ⚙️ Requirements - PrestaShop 8 or higher - Active Cloudflare account - Access to the Cloudflare API with permissions to manage DNS 📖 Documentation If you want to use an external cron, follow these steps: Add the following code to your .htaccess file located in var/www/public_html/modules/: <Files "cron.php"> <If "%{REQUEST_URI} =~ m#^/modules/cffootballbypass/cron\.php#"> Require all granted </If> </Files> GitHub cffootballbypass.zip

Simple, PrestaShop ne propose plus de version 9 open source installable, il faut se tourner vers les membres de la communauté ayant pris le temps d'en proposer des versions packagées vierges des modules tiers imposés par PrestaShop comme sur https://presta.zip/

--El Patron Thanks for the confirmation and overall support. Will move ahead with v.8. Be well.

I chyba tak zrobię. Właśnie próbowałem zrobić aktualizację do 9.0.1 i wyleciało w kosmos wszystko. Aktualizacja nieudana, ale przecież zrobiłem backup, nie? No nie, backup także nieudany i nie mam już dostępu do backendu ani do frontu. Co za szit.

Thirty Bees y PrestaShop tienen enfoques distintos. TB nació como un fork de PS 1.6 buscando más estabilidad, y es cierto que puede ser más ligero en algunos entornos. Pero también tiene una comunidad mucho más pequeña y menos soporte especializado, lo que en proyectos grandes puede ser un riesgo. PrestaShop, por su parte, sigue siendo el CMS más extendido en e‑commerce open source, con un ecosistema enorme de módulos y desarrolladores. Eso implica más opciones de integración, aunque también más dependencia de terceros. Al final, no se trata de que uno sea “misión imposible” y el otro “perfecto”, sino de valorar qué plataforma encaja mejor con las necesidades de cada negocio y con el soporte que se espera tener a largo plazo.

Hi! First, please make sure that the credit card payment option is activated in your paypal account directly, as well as that your account is eligible for this option and doesn't have any restrictions. Also, the option itself is present in the module only for several countries, such as the USA, Mexico, Brazil, Germany etc. If your country is not on the list, the option won't be present in the module separately. If this is not your case, I invite you to create a support ticket for us with more details: https://addons.prestashop.com/en/contact-us?id_product=1748 Regards, Daria 202-ecommerce

@ErnestQ both API level caching and front-end level/presentation layer caching are possible. We already implemented this API caching in our Pro version, this can be used on large catalogs. Also there is a report showing the throughput for API calling: https://www.binshops.com/prestashop-api#api-caching At presentation layer, we can do many tricks. We already used the React Cache Query https://www.binshops.com/docs/next-ecommerce/special-features.html#react-query so making it fast and preventing duplicate requests as a result fewer API calls. This makes it very fast for rendering already visited pages. This is enabled on our demo too you can test: https://react.binshops.com/ For SSR caching (like what you mentioned Varnish or other caching mechanisms), the storefront pages can easily be easily cached on Redis for first request SSR calls. I do not have benchmark for it right now, however all depends on the configurations and setup, but the road map is very clear for achieving a high speed storefront.

Hello, That is something that was introduced in PHP 8.2. Creating dynamic properties will result in warnings PrestaShop 8.x does not fully support PHP 8.2+ as you can see here The easiest way of fixing your problem is to downgrade to PHP 8.1

Hey, Here is the fastest and best performing Headless solution for PrestaShop: https://www.binshops.com/prestashop-headless-pwa you can check the performance with demo: https://react.binshops.com/

which version of ps? 9.0.0 or 9.0.1? if you cannot fallback to original ps version (restore) then one can only go forward, if on 9.0.0 then you can create a fresh 9.0.1 installation and use from addons migration pro, which can export 'most' of your shop data's, just noticed a 9.0.0 to 9.0.1 did not carry over groups, for most that is not issue unless you added groups. I'm still proving 9.0.1, but 9.0.0 is a NO GO! remember to always post exact ps and php version, it matters.

Olá. Aqui tem pra versao Prestashop 9 segun indica ali. https://github.com/pagseguro/pagseguro-modulo-prestashop

Hello, I just tested with PS 8.1.7 and it does work as expected. Can you add the following CSS code to admin/themes/default/css/overrides.css file: .bootstrap .page-head .page-title { color: green !important; } Then go to the dashboard page and hard reload the browser window (Ctrl + Shift + R or Ctrl + F5 in Chrome). At this point, the title of the page should be green, as shown in my screenshot below. For the new admin pages (the ones that do not follow the index.php?controller= URL pattern), you will need to create the admin/themes/new-theme/css/overrides.css file and add your custom styles there

I don't think that page is even working correctly. Got the same. As for icon. Did you look on the profile and verify the avatar image is there?

Hola, Necesito añadir un avatar / imagen de cliente en el perfil del cliente para luego mostrarlo en el frontend. ¿Conocéis algún módulo que cumpla estas funcionalidades? Gracias.

Thank you guys for the answer. i had checked the theme translation, unfortunally there are not this sentence...only the following: ---You must agree to our Terms of Service before going any further!--- I agree to the [terms of service] and [revocation terms] and will adhere to them unconditionally---. Hm...