Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 30th of March to Sunday 05th of April 2020. General messages As you will see at the end of this core-weekly, some work is ongoing in order to simplify the release process of modules in the open source project. A quick update about PrestaShop’s GitHub issues and pull requests: 63 new issues have been created in the project repositories; 66 issues have been closed, including 18 fixed issues on the core; 186 pull requests have been opened in the project repositories; 229 pull requests have been closed, including 198 merged pull requests. Code changes in the ‘develop’ branch Core #18374: Fix BO - Order - Wrong declination reference displayed on pack composition. Thank you @PululuK Back office #18366: Grid row delete confirmation modal - Shop parameters > Contacts, by @sowbiba #18365: Grid row delete confirmation modal - International > Taxes, by @sowbiba #18364: Grid row delete confirmation modal - Advanced parameters > Webservice, by @sowbiba #18363: Grid row delete confirmation modal - Advanced parameters > DB > Backups, by @sowbiba #18361: Grid row delete confirmation modal - Advanced parameters > Team > Profiles, by @sowbiba #18360: Grid row delete confirmation modal - Advanced parameters > Team > Employees, by @sowbiba #18359: Grid row delete confirmation modal - Advanced parameters > Emails, by @sowbiba #18358: Grid row delete confirmation modal - Shop parameters > Traffic SEO > SEO URLs, by @sowbiba #18357: Grid row delete confirmation modal - International > Localization > Currencies, by @sowbiba #18356: Grid row delete confirmation modal - International > Localization > Languages, by @sowbiba #18355: Grid row delete confirmation modal - Design > Pages, by @sowbiba #18325: Grid row delete confirmation modal - Catalog > Brands > Brands, by @sowbiba #18324: Grid row delete confirmation modal - Catalog > Brands > Addresses, by @sowbiba #18323: Grid row delete confirmation modal - Catalog > Suppliers, by @sowbiba #17972: Wrong declination reference displayed on pack composition. Thank you @PululuK #17765: Fix shipping price in orders demo, by @marionf #17467: Category admin jumps to home when deleting a category.. Thank you @PululuK #17436: Update BO theme/default webpack to v4.41 and its dependencies, by @NeOMakinG #16763: Add stylelint and correct every errors of BO new-theme, by @NeOMakinG Front office #18226: ApplyProductCalculation and ProductlazyArray variable mismatch. Thank you @jonasburneika Web services #16710: Add webservice to OrderCartRule with endpoint order_cart_rules. Thank you @Daxtermania Tests #18408: Functional tests - Add ‘Confirmation delete modal’ to tests files, by @boubkerbribri #18394: Functional tests - Add ‘Confirmation delete modal’ to tests design pages, by @boubkerbribri #18392: Functional tests - Add ‘Confirmation delete modal’ to tests languages, by @boubkerbribri #18389: Functional tests - Add ‘Confirmation delete modal’ to tests currencies, by @boubkerbribri #18386: Functional tests - Add ‘Confirmation delete modal’ to tests Seo and Url, by @boubkerbribri #18384: Functional tests - Add ‘Confirmation delete modal’ to tests profiles, by @boubkerbribri #18383: Functional tests - Fix delete modal for tests employees, by @boubkerbribri #18381: Functional tests - Fix delete modal for tests taxes, by @boubkerbribri #18380: Functional tests - Add ‘Confirmation delete modal click’ to tests Db backups, by @boubkerbribri #18377: Functional tests - Add ‘Confirmation delete modal click’ to tests contact and web service, by @boubkerbribri Code changes in the ‘1.7.7.x’ branch Core #18234: Fix guest to customer transformation issue, by @matthieu-rolland #17561: Allow cyrilic domain names in email addresses, by @atomiix Back office #18419: Fix currency symbol in orders list, by @sowbiba #18416: Fix overflow on main-menu and adjust workaround on last items in menu, by @NeOMakinG #18373: Avoid date time split in Grids, by @jolelievre #18347: Hide order preview stock location column if empty, by @atomiix #18334: Add FancyBox in create order page details button, by @jolelievre #18326: Fix messages block in order view page. Thank you @zuk3975 #18305: Fix count query with customer filter, by @atomiix #18205: [BO] Add Product on Order : Use previous cart rather than creating a new one, by @Progi1984 #17927: Wrong prices in edit order with secondary currency, by @sowbiba #17864: Extract order products to separate query. Thank you @zuk3975 #17850: Rework OrderRefundCalculator to use Number. Thank you @zuk3975 Tests #18401: Functional tests - Filter delete and delete with bulk actions email. Thank you @nesrineabdmouleh #18375: Functional tests - Product settings enable/disable stock management. Thank you @nesrineabdmouleh #18371: Functional tests - Order settings enable/disable terms of service. Thank you @nesrineabdmouleh #18369: Functional tests - Add test ‘Sort cms pages’, by @boubkerbribri #18367: Functional tests - Add tests helper card for brands and suppliers, by @boubkerbribri #18350: Functional tests - Add test ‘Bulk update orders status’, by @boubkerbribri #18342: Functional tests - Add test ‘Filter stocks by category’, by @boubkerbribri #18332: Functional tests - Wait for navigation in go to maintenance tab function, by @boubkerbribri #18313: Functional tests - CRUD sql query. Thank you @nesrineabdmouleh #18311: Functional tests - Add new client filter to order test, by @boubkerbribri #18308: Functional tests - Add test ‘Check delivery slip downloaded from list’, by @boubkerbribri Code changes in modules, themes & tools Contact informations module #31: Add PR template, and enable release drafter, by @jolelievre #28: Enable Release Drafter, by @matks #27: Add GitHub PR template, by @matks Visits and Visitors #6: Enable Release Drafter, by @matks #5: Add GitHub PR template, by @matks Available quantities #10: Enable Release Drafter, by @matks #9: Add GitHub PR template, by @matks Shop search #6: Enable Release Drafter, by @matks #5: Add GitHub PR template, by @matks Sales and orders #11: Enable Release Drafter, by @matks #10: Add GitHub PR template, by @matks Registrations statistics modules #6: Enable Release Drafter, by @matks #5: Add GitHub PR template, by @matks Product details #13: Enable Release Drafter, by @matks #12: Add GitHub PR template, by @matks Registered customer information #4: Enable Release Drafter, by @matks #3: Add GitHub PR template, by @matks Visitors origin #4: Enable Release Drafter, by @matks #3: Add GitHub PR template, by @matks Newsletter #5: Enable Release Drafter, by @matks #4: Add GitHub PR template, by @matks Visitors online #10: Enable Release Drafter, by @matks #9: Add GitHub PR template, by @matks Stats Dashboard #13: Enable Release Drafter, by @matks #12: Add GitHub PR template, by @matks Browsers and operating systems #8: Enable Release Drafter, by @matks #7: Add GitHub PR template, by @matks Data mining for statistics #9: Enable Release Drafter, by @matks #8: Add GitHub PR template, by @matks #6: CO: Fix for mysql duplicated id for guest account registration - guest is duplicated if it has multiple customer accounts. Thank you @fkwakkenbos Catalog evaluation #13: Enable Release Drafter, by @matks #12: Add GitHub PR template, by @matks Catalog statistics #7: Enable Release Drafter, by @matks #6: Add GitHub PR template, by @matks Carrier distribution #4: Enable Release Drafter, by @matks #3: Add GitHub PR template, by @matks Best vouchers #5: Enable Release Drafter, by @matks #4: Add GitHub PR template, by @matks Best suppliers #4: Enable Release Drafter, by @matks #3: Add GitHub PR template, by @matks Best-selling products #4: Enable Release Drafter, by @matks #3: Add GitHub PR template, by @matks Best manufacturers #4: Enable Release Drafter, by @matks #3: Add GitHub PR template, by @matks Best customers #10: Enable Release Drafter, by @matks #9: Add GitHub PR template, by @matks Best categories #5: Enable Release Drafter, by @matks #4: Add GitHub PR template, by @matks Search engine keywords #7: Enable Release Drafter, by @matks #6: Add GitHub PR template, by @matks Wire payment module #49: Enable Release Drafter, by @matks #48: Add GitHub PR template, by @matks #46: Hide goods reservation text for empty days value. Thank you @rmilecki Social Follow module #18: Enable Release Drafter, by @matks #17: Add GitHub PR template, by @matks Share Buttons module #36: Enable Release Drafter, by @matks #35: Add GitHub PR template, by @matks Search Bar module #17: Enable Release Drafter, by @matks #16: Add GitHub PR template, by @matks Main menu module #31: Enable Release Drafter, by @matks #30: Add GitHub PR template, by @matks Language selector #16: Enable Release Drafter, by @matks #15: Add GitHub PR template, by @matks #13: Uninstall module used on PS 1.6 before using this one, by @Quetzacoalt91 #12: Added iso code. Thank you @patryk-uszynski Image slider #48: Enable Release Drafter, by @matks #47: Add GitHub PR template, by @matks #34: Dir constant. Thank you @MathiasReker #30: Lossless compression. Thank you @MathiasReker Featured products #24: Enable Release Drafter, by @matks #23: Add GitHub PR template, by @matks #17: Lossless compression. Thank you @MathiasReker Order Notifications on the Favicon #11: Enable Release Drafter, by @matks #10: Add GitHub PR template, by @matks Email subscription module #53: Enable Release Drafter, by @matks #52: Add GitHub PR template, by @matks Customer data privacy block #16: Enable Release Drafter, by @matks #15: Add GitHub PR template, by @matks Custom text #38: Enable Release Drafter, by @matks #37: Add GitHub PR template, by @matks Customer “Sign in” link #18: Enable Release Drafter, by @matks #17: Add GitHub PR template, by @matks #13: Lossless compression. Thank you @MathiasReker Customer account links #23: Enable Release Drafter, by @matks #22: Add GitHub PR template, by @matks Cross-selling #9: Enable Release Drafter, by @matks #8: Add GitHub PR template, by @matks Check payment #30: Enable Release Drafter, by @matks #29: Add GitHub PR template, by @matks Category tree links #31: Enable Release Drafter, by @matks #30: Add GitHub PR template, by @matks #25: Lossless compression. Thank you @MathiasReker Banner #17: Enable Release Drafter, by @matks #16: Add GitHub PR template, by @matks Pages not found #9: Enable Release Drafter, by @matks #8: Add GitHub PR template, by @matks Google Sitemap module #133: Enable Release Drafter, by @matks #132: Add GitHub PR template, by @matks Simple HTML table display #8: Enable Release Drafter, by @matks #7: Make license SPDX compliant, by @atomiix #6: Add GitHub PR template, by @matks NVD3 Charts #8: Enable Release Drafter, by @matks #7: Add GitHub PR template, by @matks Dashboard Trends #24: Enable Release Drafter, by @matks #23: Add GitHub PR template, by @matks Dashboard Products #22: Enable Release Drafter, by @matks #21: Add GitHub PR template, by @matks Dashboard Goals #18: Enable Release Drafter, by @matks #17: Add GitHub PR template, by @matks Dashboard Activity module #18: Enable Release Drafter, by @matks #17: Add GitHub PR template, by @matks Contact Form #37: Enable Release Drafter, by @matks #36: Add GitHub PR template, by @matks PS Cleaner module #44: Enable Release Drafter, by @matks #43: Add GitHub PR template, by @matks Classic-rocket theme #146: Minor Typo on checkout.tpl block offcanvas_modals?. Thank you @dvdwalker Core Weekly Generator tool #28: Adding a few modules to the list, by @ttoine Link list #81: Revert “Automatic tab with Symfony route”, by @Progi1984 #80: Add GitHub PR template, by @matks #70: Automatic tab with Symfony route, by @jolelievre Theme customization #24: Add GitHub PR template, by @matks Product Comments module #53: Add GitHub PR template, by @matks PSGDPR #82: Add GitHub PR template, by @matks #80: Update translation key. Thank you @netraagal #79: Update readme to add multistore compatibility, by @marionf #78: Prevent deleting data when non-existing customer, by @Matt75 #75: Fix error 500 on controller FrontAjaxGdpr. Thank you @pablopolyte #74: Add missing checkbox on order confirmation form. Thank you @daresh #73: Fix Trying to get property of non-object. Thank you @pablopolyte #66: Fix duplicate html element id. Thank you @davidglezz #64: GDPR isn’t working if the module have multiple form on same page. Thank you @PeeyushAgrawalWebkul #17: Remove usage of $link in customerAccount.tpl. Thank you @nenes25 OnBoarding #61: Merge dev into master, by @matks #60: Add GitHub PR template, by @matks Customer reassurance block #43: optimize translation, by @matthieu-rolland Changes in developer documentation #496: Minor typo on Embedding a template in the theme section. Thank you @dvdwalker Shopping cart module #58: Add GitHub PR template, by @matks #21: Fix ps_shoppingcart.js removing cart menu from header. Thank you @alexej-d Faceted search module #167: Add GitHub PR template, by @matks PrestaShop Specifications #70: Create Order Page View.md. Thank you @MatShir Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @Progi1984, @jolelievre, @matks, @sowbiba, @NeOMakinG, @boubkerbribri, @dvdwalker, @nesrineabdmouleh, @ttoine, @atomiix, @PululuK, @matthieu-rolland, @zuk3975, @jonasburneika, @netraagal, @marionf, @Matt75, @pablopolyte, @daresh, @micka-fdz, @rmilecki, @Daxtermania, @MatShir, @davidglezz, @PeeyushAgrawalWebkul, @Quetzacoalt91, @MathiasReker, @nenes25, @alexej-d, @fkwakkenbos, @patryk-uszynski! Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub! If you want to contribute to PrestaShop with code, please read these pages first: Contributing code to PrestaShop Coding standards …and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you! Happy contributin’ everyone! View the full article
  3. Today
  4. Once again, open source CMSs Security leads shared knowledge together last February at an event organized by Google in Munich. Lightning talks & Security technologies After spending the first evening with stakeholders and meeting the newcomers over a few beers, the attendees and I spent two days at Google’s Munich office and Information Security Hub (ISH) to talk about what we have achieved since last year and about what’s coming. And of course we learned a lot about each other. We had lightning talks as well as conferences about multiple technologies focusing on security and data privacy. Similarly to last year, components like Strict Content Security Policy, Trusted Types and Scripting Policy were again discussed and brought to the forefront. Cross-Origin Resource Policy (CORP), Cross-Origin-Embedded-Policy and Securer Contexts are still strongly recommended to enhance isolation and mitigate side-channel attacks. We discovered the interesting OpenSK as a Tock OS application, an open-source security key to be used for multi-factor authentication. We talked again about the potential of PSR-9 and PSR-10 PHP Standards Recommendations, but sadly no real progress has been done since last year. Snyk gave us a talk about Javascript Prototype Pollution which reminds us that we must pay close attention to all dependencies we use, even if they are widely trusted. It is mandatory to keep them as up-to-date as possible, even if this introduces BC Breaks. And lastly, we attended an interesting talk about the Virus Total API, which is used to cluster and classify potential malware on the web. Breakout Sessions Breakout sessions were organised for the rest of the time, allowing participants to share ideas and experiences about many different themes related to the summit. Here’s what we discussed about. Rapid Detection and prevention Content Management Systems (CMSs) are used by most websites in the world and the number of attacks targeting them keep increasing every year. Therefore, the ability to quickly detect attacks and to respond accordingly as swiftly as possible has been identified as a high priority for everyone. On PrestaShop’s side, the project maintainers have decided to greatly encourage communication and contribution regarding security issues. For this, we approached YesWeHack to set up a Bug Bounty program. This will help us detect more security issues and respond more quickly through security releases. Automatic updates It is a well-known fact that the main risk for a software is its age. Keeping it updated is mandatory as it will considerably reduce the risk of having unpatched security issues. Even if at a given time there are no known issues, nobody can predict the future. 0-day vulnerabilities on PHP, Apache, Nginx and the like could be discovered at any time. Keeping your software up-to-date also enhances your chances of being compatible with the latest security systems, protocols, or encryption versions you might need in case you need to upgrade quickly to patch a security issue. However, updating a CMS is not without risk, especially when you use custom themes or modules, modules that don’t follow best practices or if backward-incompatible changes have been introduced in the latest versions. We know that the Autoupgrade module has received little attention lately, and that this has had and impact in the PrestaShop ecosystem. Everyone knows how important and necessary it is for the community. During the summit, we spent a lot of time talking about the self upgrade process, and we will surely take time this year to make improvements for this topic! Disclose + Distribute + Query security bulletins in a standardized way? At the beginning of the year, we experienced a major security incident which demonstrated that we needed to improve our security process. For example, we wanted to report the incident as an official CVE. The root cause was similar to CVE-2017-9841 but with a slightly different context (involving CGI/FastCGI). We tried to reach out to CVE authority in order to either update the entry or create a new one. However, as of June 2020, we have not received an answer yet. Since PSR-9 and PSR-10 are not yet enforced, PrestaShop maintainers decided to start using one of the latest GitHub features: GitHub Advisories. After many weeks of use, the maintainer team has been receiving positive feedback from the community about us being more transparent on security issues. A big up to the community! That said, the Core team will never go as far as disclosing how to reproduce (and exploit) security issues. You will never find any scripts in advisories or in CVE declared by PrestaShop. This is to avoid making hackers’ work easier. Obviously this is not perfect, and it will never be. But we learn from the past, and we will do our best to listen to the community and improve how we work. PrestaShop release schedule will follow PHP ecosystem release schedule PrestaShop 1.7.7 will be compatible with PHP 7.3. In order to achieve this, some dependencies PrestaShop relies on had to be upgraded. This change introduced a few BC Breaks, either because the upgraded dependency contains BC breaks or because it dropped compatibility with older PHP versions. We expect PHP 7.4 to require new dependency upgrades and BC breaks, and so on with next PHP versions. Moreover, the PHP core team plans to release versions more often in the next years. This means, in the future, many operating systems and software vendors will have no other choice than to follow their tech ecosystem, or stay behind. PrestaShop is not an exception. Consequently, we expect future PrestaShop versions will have to be released more often and introduce breaking changes more often as well. We hope that well-known developers from the PHP community, such as the maintainers of Composer, will attend the next summit so we can work together on this topic. Lighthouse score for security LightHouse is an automated tool from Google that provides metrics which can be used to improve the quality of web pages. However, it is missing features on security area. It was suggested that the first thing Google could do would be to integrate security.txt or securityheaders.io in Chromium as to allow people to submit security reports directly from their browser as they browse the web. Maybe even adding a JavaScript scanner inside Lighthouse, and show outdated libraries? Whatever it is, Google is working on very interesting things for this year 2020 :) Other sessions Unfortunately, we did not have enough time to attend all breakout sessions but there were also discussions around security tools, APIs, funding security improvements, static analysis and two-factor authentication. Thanks I would like to say thanks to Google for organizing the event and to all participants as well for being active and passionate about improving security. Spending time with security folks has been very interesting. We all know we need to work together to make the web safer. View the full article
  5. Past hour
  6. Bonjour à toute la communauté Prestashop. Je cherche à supprimer sur mon site le bouton "voir le modèle" Est-ce que quelqu'un aurait une solution. Par avance merci www.sneakeasy.fr
  7. Muchas gracias ventura. Pero cuando intento guardar la consulta me sale un error: Error indefinido "checkedForm" Estado mirando y dicen que puede ser un bug de la version del presta antigua, pero que en las versiones nuevas esta solucionado, no se por que me sale si yo tengo la tengo la 1.7.5.0
  8. Nein, nur falls du nichtessentielle Cookies (Werbetracker etc) verwendest! Grüsse Whiley
  9. Dann warten wir mal ab, ob da dann tatsächlich auf 19 zurückgegangen wird.....
  10. unbelievable but yes, it´s developed by Prestashop....and this is the answer after 15 minutes Tweet post Hola, thank you for contacting our team. First of all we apologize for the abnormally long response time. In this period of containment and teleworking, we are under-staffed while the number of support tickets has increased dramatically. This unfortunately results in a highly disrupted processing time. I am transferring this thread to the Billing team who will deal with your refund request. Saludos, Adrien Servicio de atención al cliente - PrestaShop Addons INCREDIBLE!!! and more, they publish that at this time (COVID-19) Prestashop is the best platform for e-commerce!!!!!!!! If you don´t have capacity to attend actual's user, how you will attended new ones???
  11. Welche Preise werden bei einer Steueränderung beibehalten? Brutto oder Netto? Ich hoffe mal die Nettopreise.....
  12. J'ai ça qui apparait depuis l'update à la 1.7.6.5 quand je tente de modifié mes catégories (j'ai toujours pas fait le changement du fichier product-price.tpl comme personne ne me donne de réponse, pas même le support prestashop... ça sens vraiment l'arnaque ce truc) Une erreur inattendue s'est produite. [PrestaShop\PrestaShop\Core\Domain\Category\Exception\CategoryException code 0] Est ce que quelqu'un sait de quoi il s'agit ? J’essaie juste d'ajouter des mots clé à mes catégories. En remerciant celui ou celle qui répondra.
  13. Error also shown 30, increase it maximum value for to let run the PHP script.
  14. @PrestaServicePro the max_execution_time is set on 30 at the moment. that doesnt fix the problem
  15. Bonjour, Quelqu'un sait où modifier le core pour faire en sorte que les réductions liées à un groupe ne soit appliqué que sur les produits n'ayant pas déjà une réduction (specific price)? Merci
  16. salve, purtroppo io voglio tornare a zero, e il numero attuale è 7. Se imposto su 1 o su 0, mi dice che il numero è errato, mi fa partire solo da un numero superiore. Io voglio tornare a 0
  17. J'ai essayé avec cette règle mais ça ne fonctionne pas... Options +FollowSymLinks RewriteEngine on #blog RewriteRule ^([0-9]+)_([a-z-]+).html$ jhpcmsblog/post/$1_$2.html?page_type=post [L]
  18. the problem is not in practice but what is realistic, for example get a .it domain and try and use it, it won't work...so you need to get .it domain registrar approval...in your scenario you are not using cctlds to target a country, so switching to it.yourdomain add no real value and is disconcerting to visitor, i.e. there is change they notice, any notice during visitor experience not direcly related to product purchase is bad. ok, so you gave example, now let me give you a 'best in class' example of how to multiplex same/different content across multiple languages/countries. https://azure.microsoft.com/ now notice the lang-country...no need for multishop, no need for additional domain names, no subdirectory(very old school). I had my team develop that sometime ago https://prestashopaddons.prestaheroes.com/en-us/prestashop-geo-localization-solutions/google-international-friendly-url so to answer everyones answer, multstore by country 1) lost seo juice 2) has been replaced by new best practice lang-country....imagine now...you have es pack....it's es-es...but imagine some brains creating module that for ps where es-es, now dynamically change to es-(country dependng on geo)...now imagine google.com.ar (argentina) visitor seeing es-ar, bots indexes by country then localize.... I'm not just a legend here...
  19. Today
  20. In this case you need to copy tables from module Mail alerts to the new store, and then migrate the information from the module (the module has a button in the configuration to migrate the data, but the data has to be in the same database).
  21. Hi, I know how to set address phone to required in back office but, is it possible to set the customers phone number to be required, but not the delivery recipient phone number to be required?
  22. A site I set up for a client is having an ongoing issue with large carts freezing the site. If a lot of products are placed into the cart sometimes the cart freezes or throws an error 500. The site stays locked until that cart is deleted. I'm using PHP 7.0 on the hosting and the site runs smoothly other than this. This is using PrestaShop version 1.7.5.0 Does anyone have ideas I can look into? I've searched through forums but cannot find what I'm looking for. Thanks all!
  23. Buna, in folderul vei gasi fisierul: /modules/ps_cashondelivery/ps_cashondelivery.php la linia 94 vei gasi: if ($this->hasProductDownload($params['cart'])) { va trebui sa o schimbi cu aceasta: if ($this->hasProductDownload($params['cart']) || $params['cart']->getOrderTotal() > Tools::convertPrice(5000, $params['cart']->id_currency)){ ar trebui sa o comentezi linia veche iar sub .. sa o pui pe cea noua: //if ($this->hasProductDownload($params['cart'])) {
  24. I've generated a basic skeleton from PS module validator, installed it and now I'm trying to put it's configuration page link to the BO side-menu. I've read the documentation, I went through some threads online but I can't find out what I am doing wrong. This is the code: class MyCustomModule extends Module { protected $config_form = false; public function __construct() { $this->name = 'mycustommodule'; $this->tab = 'administration'; $this->version = '1.0.0'; $this->author = 'John Doe'; $this->need_instance = 0; $this->tabs = array( array( 'name' => 'My custom module', 'class_name' => 'AdminMyCustomModule', 'visible' => true, 'parent_class_name' => 'AdminCatalog', )); /** * Set $this->bootstrap to true if your module is compliant with bootstrap (PrestaShop 1.6) */ $this->bootstrap = true; parent::__construct(); $this->displayName = $this->l('My Custom Module'); $this->description = $this->l('Lorem ipsum dolor sit amet.'); $this->ps_versions_compliancy = array('min' => '1.7', 'max' => _PS_VERSION_); } ... } Of course I've reset the module, even tried uninstalling and installing it again. My new menu tab just doesn't appear. Thank you.
  25. Buenas! Tengo un prestashop multitienda con un B2B en una y un B2C en otra. Quiero cambias los textos de las traducciones de por ejemplo la página de inicio de sesión, quiero que cada tienda tenga su texto. Lo he probado, però si lo cambio para una, se cambia también la otra. Sabéis si hay alguna manera de hacerlo? Gracias! Maite
  26. Hola Edison , si es lo que había pensado en desarrollar pero no tengo grandes conocimientos en programación. Lo que si he podido ver es que la propia plantilla te da la opción de cambiar la opción de contar por producto o por combinación. Hay que ir a CONFIGURACIÓN > Parámetros de la tienda > Configuración de Productos > Productos (general) > Descuentos por cantidad basados en: y cambiar de Productos a Combinaciones. Con esto hace el cálculo para los descuentos como quiero. Gracias a todos.
  27. Muy buenas mi gente, otra vez aquí con otra duda. Querría crear las urls en silo; paginaweb.com/zapatillas/rojas en vez de paginaweb.com/zapatillas rojas De que manera podría crear categorías y subcaterogias dentro de una Url?? Muchas gracias a todos por vuestros comentarios.
  1. Load more activity
×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More