blog-posts

The PrestaShop project currently (September 2019) has 389 pull requests open and new Pull Requests are opened almost everyday. And this is only for the main repository. Other github repositories like the developer documentation, modules, docker images also have their share of pull requests waiting to be merged, raising the number of open pull requests to more than a thousand. All of these pull requests go through a thorough process which aims to provide a stable, consistent and reliable software that we all know under the name PrestaShop. Here is this process in details. Automatic tasks when you open a Pull Request When you submit a new Pull Request to the project repository https://github.com/PrestaShop/PrestaShop, a long journey starts. Continuous Integration We have set up two great tools on the project that help us verify the quality of contributions. The first tool is PrettyCI. This tool will look at your Pull Request and check whether the code-style is correct. If not, it will block the PR from being merged and tell you what is wrong. It might appear trivial, but having a unified code-style on the project actually helps a lot. It is a lot easier to work on a big codebase like PrestaShop if all code is written following the same conventions: snake_case or camelCase, how to write the phpDoc, when to use white spaces … it makes the code look like if it was written by a single developer. Just like reading a book with two different styles in it, having a codebase with different styles is making it harder to navigate. A unified code-style also makes the pull requests easier to review ! If PrettyCI states that your pull request has issues, you need to fix the issues by looking at PrettyCI output to understand what needs to be fixed. The second tool is Travis. Travis is a Continous Integration system that will look at the Pull Request and run several checks, be it code-style checkers, format checkers or automated tests, and provide us the result in the Pull Request. If something is wrong it will block the PR from being merged. This is a standard approach to ensure that new contributions in a codebase do not break existing features and behaviors. If Travis states that your pull request has issues, you need to fix the issues by looking at Travis output to understand what needs to be fixed. These tools are executed automatically for every Pull Request, so we know that every contribution has been checked. This is a great asset to help us ensure the quality of the project. In addition, we have also recently activated the new Github Actions on the develop branch, which now benefits from an additional php 7.2 syntax compliancy check. Prestonbot Prestonbot is a custom bot we have built that looks at all Pull Requests and try to help us manage the project. He does a lot of things ! For example he detects mistakes in the pull request description and add some labels to help us classify the pull requests and he also welcomes new contributors to the project :D . Read his story to learn more about him. If something is wrong, Prestonbot will write a comment in the pull request to tell you what to fix. The code review, a human task Now that all the bots have done their job, humans finally come on the stage! Your Pull Request will be reviewed by a Core maintainer. What do we check in code review? When a Core maintainer sees a pull request, they will review it and decide whether it should be accepted, if it needs changes, or if it cannot be accepted. The review process is quite thorough in order to make sure that PrestaShop codebase gets better with each contribution. Here is all the things we look for in a Pull Request, when reviewing it: Of course we start by checking that the code is correct. This means both from a behavior point of view as well as from a technical point of view. This is simply an assessment of the quality of the Pull Request code, just like it happens in a lot of software teams. We check the code works as intended, it uses the right functions, it handles expectable edge-cases, has no obvious vulnerabilities, scales well, etc. We also keep in mind that PrestaShop is a CMS and consequently must provide all the necessary extension points to allow developers to customize or extend its behavior. We also assess the readability of the code. There is a statement that says “when a code file is opened by a developer, 9 times out of 10 it will only to be read, not to be modified”. Because PrestaShop is a huge and complex codebase and because it has so many people reading through it, it is very important that its code is made as readable as possible. This is obtained by adding comments, carefully choosing function and variable names, and building an architecture that makes sense so it is easy to grasp and navigate for people who have never worked on it before. We also check that best practices are implemented into the Pull Request, be it standard conventions or practices like PSR or best security recommandations like the ones from OWASP. When people use PrestaShop to build a shop, it is likely that they will follow the practices they see implemented in the Core, so we try to think of the code we merge as an example that people will use. PrestaShop has grown huge over the years, both as a codebase and as a software. There are hundreds of features built in the software, and some are more commonly used than others. Some contributions sometimes need to be reworked because they did not take into account one of the less popular features of the software, or are not compatible with them. Common examples are the multi-store mode or the RTL (Right-To-Left) mode, two features that adress very specific needs and that many developers are not aware of. PrestaShop follows SemVer. This means that we strive not to introduce breaking compatibility changes when releasing minor and patch versions. Therefore, we make sure the Pull Request does not introduce such changes, as some developers submit pull requests without being aware of this constraint. We also have a vision of what PrestaShop should evolve to in order to follow the new trends in the software world. Although a big codebase like PrestaShop evolves slowly, we keep the future architecture and features we want to include in mind, and we check whether the Pull Request is following this direction. For example today PrestaShop relies heavily on jQuery for its frontend features, and we started introducing Vue.js. So if tomorrow we see a Pull Request that is using React.js we might refuse it in order to keep a consistency in the technology stack used for the project. So as you can see, in a Pull Request we review a lot of things! To do all of these checks, we do not only look at the code on Github. We sometimes pull the branch on our own computer to test and navigate the code in order to make sure all of these requirements are met. We discuss with other maintainers about parts we are not sure. We can even sometimes run benchmarks or audits for critical pieces of code. Some Pull Requests are very easy to review because they are related to a part of the code we know very well, other instead are very hard to review because they are related to a complex topic, a complex area of the code or have a huge global impact on the software that is very hard to estimate and assess. Reviews can take hours or days as we try our very best to make sure every contribution merged in the project meets the level of quality we want for it. Most of the time, if an issue is found during the review, the Core maintainer will provide feedback about the issue and requests the author to modify the parts of the Pull Request that cannot be accepted as they are. After the author of the Pull Request has implemented the requested changes, then the Pull Request can be approved and move forward to the next step. At this moment, this button becomes green: But it cannot be clicked yet… It is not only about code For some Pull Requests, we might look for help and ask people of the PrestaShop Product Team: We ask the UX design team to review changes that have a significant UX impact We ask the Product team to review changes that introduce a significant behavior modification (either an existing feature or a new feature) We ask the Content team to review Pull Requests that introduce wording changes (labels, titles, error and information messages) Once the Pull Request has been validated by all of the relevant people, it is finally verified by the QA team. The QA team will then make sure that the behavior of the proposed change is correct and that it does not produce any regressions (new errors). After the Pull Request has finally passed the QA validation, it is merged in the project and the author becomes (if they weren’t already) a contributor to this great open source project :) . Conclusion As you can see, the process between the submission of Pull Request and its merge is a long journey. This journey is not meaningless: the goal is to make sure we build a consistent and reliable software in the end, and when you consider the size of this project, it actually does not look too much! A downside of this long journey and the level of commitment it requires from both the reviewers and the authors is that some Pull Requests require a very long time to be reviewed. Also, we are actually not a big team. As of September of 2019, there are only 6 Core maintainers available to review more than 400 Pull Requests… this is why PrestaShop is currently hiring! We also are working on other ideas to bring more people in the maintainer team and to be able to review/merge everything, so we hope to get better in the following months. View the full article

Contributing to PrestaShop is not only about the code, it’s also about taking part in the PrestaShop translation project! This report tells you how the translations of the software evolved in August. Project news Emails are now available for translation Hello all, I hope summertime was fine for each of you. A lot happened on Crowdin lately: exceptionally, the 1.7.6 catalog has been pushed again to be finally completed. Indeed, a bug prevented email translation… which was quite annoying, sorry for this quick inconvenience. We worked hard on it and corrected it for PrestaShop 1.7.6.1. And that explains why fresh translatable strings have been pushed into Crowdin. Now you can now all translate both classic and modern emails! Crowdin cleaning Also, summer is a convenient time to do a bit of cleaning among our many contributions, that is why I went on all translation projects last month and removed all profiles that no longer contribute. But do not panic, this is not an arbitrary decision, it was based on the following criterion: both proofreaders and translators that have not been seen on the PrestaShop project for at least two years have been removed. Despite all our efforts to reach and motivate absent people, if you are one of those, please know you can still subscribe and start contributing again. We will be glad to have you back! Special thanks to newcomers Many people subscribe to the project(s) of their choice each month, but not so many start translating straightaway. For that reason, we would like to thank the ones that kind of rush into the effort immediately, aha! So lot of love to the dedicated anpezz, Lizette Garcia (lizette.garcia.glz), Nipsun Keittiö (lhotel53), Ramya Shantha Peiris (Ramzhead8899), Richard Rosario (shoptechmedia), and Stijn (stijn.bosman). See you soon on Crowdin… and PrestaShop. ;-) A few stats 59 members were active on the project this month. A total of 33,339 words have been translated and 20,497 validated. All this in 37 different languages. Thank you for your involvement! Top contributors A lot of you are working every day on Crowdin to have PrestaShop available in many languages, and we can’t thank you enough for your dedication! Here are the most active translators and proofreaders for August 2019. Top 10 translators in August: Translator Language # Words 1. webdvl (megashopba) Czech, Slovak 3,082 2. Martin (lord_dark) Polish 2,298 3. mousanajafi Persian 2,238 4. Tantely R. (rabtaray) Malagasy 2,233 5. 雅丶涵 (anglesgirlcn) Chinese Simplified 2,164 6. Laimonas Mituzas (laimonas) Lithuanian 1,827 7. DaoKakao Russian 1,636 8. Rodrigo Laurindo (rblaurin) Portuguese, Brazilian 1,614 9. Patrik Lindblom (extendus) Swedish 1,538 10. Jesús Ruiz (jruiz) Spanish 1,430 Top 10 proofreaders in August: Proofreader Language # Words 1. webdvl (megashopba) Czech, Slovak 3,128 2. DaoKakao Russian 1,949 3. Adeko Webdesign & Development (Adeko) Dutch 1,913 4. Monika (monikaraciunaite) Lithuanian 1,608 5. Rodrigo Laurindo (rblaurin) Portuguese, Brazilian 1,598 6. Enzo Ferrara (ferribbotte) Italian 1,564 7. Patrik Lindblom (extendus) Swedish 1,540 8. Jesús Ruiz (jruiz) Spanish 1,460 9. Ronny (rbuelund) Danish 1,208 10. Tantely R. (rabtaray) Malagasy 933 Congrats, and welcome to our new top contributors! Remember, you can see who’s been contributing to our translation project thanks to the Translators page. Complete translations Fully translated languages At the end of August 2019, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 31 languages: Bulgarian Catalan Croatian Czech Danish Dutch English Estonian French French, Canada German Greek Italian Indonesian Latvian Lithuanian Macedonian Norwegian Persian Polish Portuguese Portuguese, Brazil Romanian Russian Slovak Slovene Spanish Swedish Turkish Ukrainian Vietnamese For its part, PrestaShop 1.7.6 was fully available in 6 languages! Czech English French Portuguese, Brazil Slovak Swedish Languages with the best evolution In comparison with June 2019, the following languages had the best progress thanks to the translation community: Persian (+2% to reach 100% translated in 1.7) Malagasy (+1% to reach 1% approved in 1.7) Russian (+1% to reach 97% approved in 1.7) Thanks to all the contributors! Of course, this is highlighting the languages that made some progress with new translations; but it doesn’t mean that the languages that aren’t mentioned here aren’t active. Indeed, some editing and rewriting could be going on, but the percentage of translation wouldn’t be modified (since it’s working on strings that are already translated). So let’s not forget about the work of these proofreaders! Thank you too! Languages that need (more) proofreaders A translated string will not be available in PrestaShop as long as it is not validated. For this reason, it’s important we should keep a good level of validated strings vs. translated strings, to make sure everyone benefits from the latest translations! At the end of August 2019, some languages would still benefit from some proofreading: Spanish, Argentina (100% translated vs 16% validated in 1.6). Spanish, Venezuela (54% vs 17% in 1.6). Galician (94% vs 59% in 1.7). Chinese Simplified (95% vs 64% in 1.7). Tagalog (54% vs 24% in 1.6). If you wish to help to proofread what has been translated, please contact us with the language you’d like to proofread: just send an email to translation@prestashop.com. We need your help! If you haven’t joined us on Crowdin yet, it’s never too late! If you want to gather your fellow translators to work towards a better harmonization, start a glossary, or anything else, do let us know: we’ll include a word about it in the next monthly report. Do you have a question, a remark? Don’t hesitate to leave a comment. See you next month! View the full article

PrestaShop 1.7.6.1 is now available. This maintenance release fixes 26 issues reported on version 1.7.6.0. We suggest upgrading your shop quickly in order to benefit from this fixes. Of course, don’t forget to backup before. Main fixes In some circumstances prices would appear with 6 decimal digits (#14640) The “convert a guest into a customer” feature wasn’t working (#14639) It was possible to circumvent the BO token in some circumstances (Thanks Guillaume Lictevout) (#14671) The “erase all” button in the logs page wasn’t working (#14686) Mails weren’t completely translated/translatable (#14633) Links pointing to edit/view customers weren’t working on legacy pages like Quick Search (#14672) Prices in Czech would sometimes be displayed using the wrong formatting (#14657) Applying filters in the logs page would result in an error (#14785) Importing a theme would fail it if contained a translations directory with no files (#14960) The translation interface wasn’t working when using a theme other than classic (#14733 and #15133) Module translations edited through the new back office interface were being ignored by the module (#14932) Disabled categories were not being shown in the parent category tree when editing categories, resulting in an error (#14790) Accessing the suppliers page after an import would result in an error (#14908) Following steps in the checkout process were being disabled even when the theme didn’t include a “continue” button (#14846) Errors would occur when manipulating orders in some circumstances when working on a multishop environment (#14595 and #15144) Read the full changelog here. Important changes Following #15173 we had to modify CurrencyDataProviderInterface::findAll and add an optional parameter to be able to fetch all currencies regardless of the current shop context. This doesn’t break any previous use of the method since the parameter is optional, but it requires to update any class that implemented that interface. Following #15139, module translations are no longer attached to the currently active theme. If you want a different translation for each theme, you will have to edit the theme translations; this requires the specific wording to be physically present in the theme’s templates or else it won’t appear in the translation interface. Only theme translations are attached to a theme now, all other translations are now global. Acknowledgements Contributors to this patch version, from both the Core team and the community at large: Dheeraj Sharma, Franck Lefèvre, Jonathan Lelievre, Mathieu Ferment, Matthieu Rolland, Nesrine Abdmouleh, Pablo Borowicz, Pierre Rambaud, Priyank Desai, Roja45, Thomas Nabord and Šarūnas Jonušas. Thank you! Download PrestaShop 1.7.6.1 now! Since version 1.7.6.1 is a “patch” update to version 1.7.6.0, upgrading from any 1.7.6 version will be easy: features will work better, and modules & themes which worked fine on 1.7.6.0 will work just as well with 1.7.6.1. Upgrades from a standard 1.7.x version should work just as well. View the full article

Contributing to PrestaShop is not only about the code, it’s also about taking part in the PrestaShop translation project! This report tells you how the translations of the software evolved in July. Project news Special thanks to newcomers Many people subscribe to the project(s) of their choice each month, but not so many start translating straightaway. For that reason, we would like to thank the ones that kind of rush into the effort immediately, aha! So lot of love to the dedicated 雅丶涵 (anglesgirlcn), David Gonzalez (davidglezz), Enes Kumaş (Oritorius), fjutt, Jeppis, Juan Suarez (mydesignar), luciash d’ being (luciash), Ray Lei (joyawatchv88), tonyre, Val Vini (visar.mato), wmarquez, and zlgtz. See you soon on Crowdin… and PrestaShop. ;-) A few stats 38 members were active on the project this month. A total of 10,132 words have been translated and 4,838 validated. All this in 25 different languages. Thank you for your involvement! Top contributors A lot of you are working every day on Crowdin to have PrestaShop available in many languages, and we can’t thank you enough for your dedication! Here are the most active translators and proofreaders for July 2019. Top 10 translators in July: Translator Language # Words 1. Tantely R. (rabtaray) Malagasy 4,203 2. Enes Kumaş (Oritorius) Turkish 1,310 3. kristapskr Latvian 1,209 4. v88 Russian 475 5. Rodrigo Laurindo (rblaurin) Portuguese, Brazilian 302 6. mousanajafi Persian 295 7. Cha (cafetango) Chinese Traditional 232 8. Stamatis (breezer) Greek 172 9. Ardis Markss (ardis.markss) Latvian 161 10. YuCheng Hu (huyuchengus) Chinese Simplified 137 Top 10 proofreaders in July: Proofreader Language # Words 1. kristapskr Latvian 1,209 2. SeongHyeon Cho (jaymz9634) Korean 1,064 3. Rodrigo Laurindo (rblaurin) Portuguese, Brazilian 281 4. Cha (cafetango) Chinese Traditional 232 5. webdvl (megashopba) Czech, Slovak 219 6. Stamatis (breezer) Greek 172 7. Monika (monikaraciunaite) Lithuanian 172 8. Ardis Markss (ardis.markss) Latvian 161 9. YuCheng Hu (huyuchengus) Chinese Simplified 144 10. Jesús Ruiz (jruiz) Spanish 123 Congrats, and welcome to our new top contributors! Remember, you can see who’s been contributing to our translation project thanks to the Translators page. Complete translations Fully translated languages At the end of July 2019, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 31 languages: Bulgarian Catalan Croatian Czech Danish Dutch English Estonian French French, Canada German Greek Italian Indonesian Latvian Lithuanian Macedonian Norwegian Persian Polish Portuguese Portuguese, Brazil Romanian Russian Slovak Slovene Spanish Swedish Turkish Ukrainian Vietnamese For its part, PrestaShop 1.7.6 was fully available in 13 languages! Czech Danish English Estonian French Greek Italian Latvian Portuguese, Brazil Romanian Serbian Slovak Swedish Languages with the best evolution In comparison with June 2019, the following languages had the best progress thanks to the translation community: Latvian (+3% to reach 100% approved in 1.7) Malagasy (+3% to reach 4% translated in 1.7) Turkish (+3% to reach 100% translated in 1.7) Thanks to all the contributors! Of course, this is highlighting the languages that made some progress with new translations; but it doesn’t mean that the languages that aren’t mentioned here aren’t active. Indeed, some editing and rewriting could be going on, but the percentage of translation wouldn’t be modified (since it’s working on strings that are already translated). So let’s not forget about the work of these proofreaders! Thank you too! Languages that need (more) proofreaders A translated string will not be available in PrestaShop as long as it is not validated. For this reason, it’s important we should keep a good level of validated strings vs. translated strings, to make sure everyone benefits from the latest translations! At the end of July 2019, some languages would still benefit from some proofreading: Spanish, Argentina (100% translated vs 16% validated in 1.6). Spanish, Venezuela (53% vs 17% in 1.6). Galician (97% vs 61% in 1.7). Tagalog (54% vs 24% in 1.6). Chinese Simplified (96% vs 69% in 1.7). If you wish to help to proofread what has been translated, please contact us with the language you’d like to proofread: just send an email to translation@prestashop.com. We need your help! If you haven’t joined us on Crowdin yet, it’s never too late! If you want to gather your fellow translators to work towards a better harmonization, start a glossary, or anything else, do let us know: we’ll include a word about it in the next monthly report. Do you have a question, a remark? Don’t hesitate to leave a comment. See you next month! View the full article

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 29th of July to Sunday 04th of August 2019. General messages Dear Developers, Would you be interested to participate to Hacktoberfest 2019 with your contributions to the PrestaShop open source software? If yes, let’s get in touch via the comments, the forums or via Twitter. The best way to be prepared for Octocber: contribute your first pull request during the summer and learn how to do it well with the code review! A quick update about PrestaShop’s GitHub issues and pull requests: 76 new issues have been created in the project repositories; 54 issues have been closed, including 11 fixed issues on the core; 46 pull requests have been opened in the project repositories; 52 pull requests have been closed, including 35 merged pull requests. Code changes in the ‘develop’ branch Core #13830: Remove duplicate var in cart.php. Thank you @davidglezz #14601: Revert removed templates for mail dynamic contents, order mails mainl…, by @jolelievre #14949: Update Module.php docs on version property type. Thank you @zalexki Back office #13730: Admin Specific Price : wrong display. Thank you @123monsite-regis #14671: Make sure token is properly used in legacy context, by @PierreRambaud #14800: Add category to product CQRS command, by @matthieu-rolland #14872: Delete migrated AdminCmsController again, by @matks Front office #14786: Sprintf function broken in 1.7.6 for custom module templates. Thank you @roja45 Tests #14971: Trigger nightly report, by @PierreRambaud Web services #14899: Initialize container in WebService environment (bis), by @Progi1984 Code changes in the “1.7.6.x” branch (for v1.7.6.1) Core #14711: Update Decimal library to 1.2.0, by @eternoendless #14859: Move i18n.prestashop.net into https and remove unwanted file, by @PierreRambaud Back office #14914: Date picker calendar is shown in wrong place when rendered downwards in grid, by @PierreRambaud #14926: Fix logs filtering. Thank you @sarjon Front office #14710: Make last breadcrumb element not clickable, by @matthieu-rolland #14863: Prevent uninstall of Product Comments module. Thank you @templatin #14945: Fixed {firstname} typo in order customer comment mail in 1.7.6.x. Thank you @dheerajwebkul Web services #14953: Initialize container in WebService environment (Progi1984’s work on 1.7.7), by @matthieu-rolland Code changes in modules, themes & tools PrestaShop Specifications #13: Update Catalog-products-add-edit-basic-settings.md, by @marionf #14: Update Catalog-Products-add-edit-elements-in-all-tabs.md, by @marionf #15: Update, by @marionf #16: Update virtual product tab, by @marionf #17: Update shipping tab, by @marionf Faceted search #116: In faceted search, Manufacturers are displayed using ordering by id, instead of name, by @PierreRambaud #117: Remove unwanted curl, by @PierreRambaud #118: Repair collapse for sliders range, by @PierreRambaud #119: Number of product are not ok after selecting filters, by @PierreRambaud #120: Bump to 3.2.0, by @PierreRambaud #121: Release 3.2.0 , by @PierreRambaud PHP Coding Standards #10: Add PS_THEME_DIR, by @Quetzacoalt91 #11: Update bootstrap.php with another method for loading proper phpparser lib. Thank you @zalexki #12: Update constants in bootstrap.php. Thank you @zalexki QA nightly results #3: New insert system, by @SimonGrn #5: CSS tweaks, filename save, add GCP URL variable, add GA script, by @SimonGrn #6: update README with GCP URL, by @SimonGrn Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @123monsite-regis, @davidglezz, @dheerajwebkul, @eternoendless, @jolelievre, @marionf, @matks, @matthieu-rolland, @PierreRambaud, @Progi1984, @Quetzacoalt91, @roja45, @sarjo, @SimonGrn, @templatin, @zalexki! 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

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 22nd to Sunday 28th of July 2019. General messages Dear Developers, A new repository is now active with a very interesting and awaited content: specifications. Still a work in progress, the product management team from the PrestaShop company has started to publish specifications and other important information about “how it should works”. The target is to give more resources to developers and contributors in general. And of course, like all resources on the GitHub repositories, this is possible to add links to the specifications in issues and pull requests. This will ease the general project management. The URL to this new repository: https://github.com/PrestaShop/prestashop-specs A quick update about PrestaShop’s GitHub issues and pull requests: 77 new issues have been created in the project repositories; 56 issues have been closed, including 12 fixed issues on the core; 51 pull requests have been opened in the project repositories; 54 pull requests have been closed, including 40 merged pull requests. Code changes in the ‘develop’ branch Core #13712: Prepares Command API for migrating Order view page. Thank you @sarjon #13906: Update CLDR data to 35.1, by @eternoendless #14065: Migrates Shopping Carts view page. Thank you @sarjon Back office #12497: Fix issue with the link Manage tax rules in the pricing tab, by @khouloudbelguith #12903: Match multiline translation expressions in modules. Thank you @unlocomqx #13980: Execute displayAdminLogin hook without shop context. Thank you @idnovate #14805: Fix unclosed div tag. Thank you @sarjon Front office #14819: Fix create account sitemap link. Thank you @Thomas-lhuillier Tests #14670: Add Behat tests for Customer commands. Thank you @sarjon #14764: Install prestashop test with puppeteer, by @boubkerbribri #14815: Add a new smoke test: crawling BO, by @SimonGrn #14825: Fix some minor problems on the “crawling BO” smoke test, by @SimonGrn Install #14718: Remove codacy badge as we dont use it anymore, by @matks Code changes in the “1.7.6.x” branch (for v1.7.6.0) Core #14664: Update precision and numeric iso code of currencies, by @Quetzacoalt91 #14833: Bad currency format for Czech language, by @PierreRambaud Back office #14828: Cannot save the “No Picture Image” , by @PierreRambaud Install #14620: Init properly the Kernel on major manual upgrades, by @Quetzacoalt91 #14739: Keep Composer.lock file in release, by @jolelievre Code changes in modules, themes & tools PrestaShop Specifications #2: Catalog-Products-add-edit-elements-in-all-tabs.md, by @marionf #3: Add link to add/edit products spec, by @marionf #4: Create Catalog-products-add-edit-basic-settings.md, by @marionf #5: Add link to Add/edit products - basic settings, by @marionf #6: Update layout, by @marionf #7: Create Catalog-products-add-edit-quantities.md, by @marionf #8: Add link to quantities tab, by @marionf #9: Create Catalog-products-add-edit-virtual-products.md, by @marionf #10: Add link to virtual product tab, by @marionf #11: Create Catalog-products-add-edit-shipping.md, by @marionf Faceted search #114: Use texture and color attribute only when color_type is set, by @PierreRambaud #115: Faceted search bad currency format on 1.7.6, by @PierreRambaud Google Analytics #34: Uninstall module used on PS 1.6 before using this one, by @Quetzacoalt91 Live demo devices #8: Add Google Tag Manager, by @Quetzacoalt91 CsaGuzzleBundle #4: Update license headers and README to acknowledge this is a fork, by @matks CIPSJsonParser #2: Adding some containers to the party. Thank you @djodjo3 E-mail subscription form #36: Uninstall module used on PS 1.6 before using this one, by @Quetzacoalt91 Cron tasks manager #43: Comply to validator.prestashop.com rules, by @matks Changes in documentation #309: Added sf-params option to sf category, by @mickaelandrieu #311: add validation tip about loading external code. Thank you @zalexki #314: Correction of code remove the 2 times ->add(. Thank you @PrestaSafe Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @boubkerbribri, @djodjo3, @eternoendless, @idnovate, @jolelievre, @khouloudbelguith, @marionf, @matks, @mickaelandrieu, @sarjon, @SimonGrn, @PierreRambaud, @PrestaSafe, @Quetzacoalt91, @Thomas-lhuillier, @unlocomqx, @zalexki! 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

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 08th to Sunday 14th of July 2019. General messages Dear Developers, A change has been introduced in 1.7.6.0 in order to improve how currencies and carts are managed and displayed. And some bank payment modules are not working anymore. Unfortunately, this was not detected during the Beta and RC releases. An issue has been opened on GitHub, and after investigation, a solution has been proposed and tested. Please read this thread for details. TL;DR: the issue was actually not in the core, but in modules that were using a bad practice. And, that bad practice was working with previous versions of PrestaShop. Some payments modules developed by the PrestaShop company are concerned and the module team is currently working to fix them. Stay tuned for updates if you are concerned. A quick update about PrestaShop’s GitHub issues and pull requests: 92 new issues have been created in the project repositories; 71 issues have been closed, including 10 fixed issues on the core; 50 pull requests have been opened in the project repositories; 43 pull requests have been closed, including 31 merged pull requests. Code changes in the ‘develop’ branch Core #13983: Fix empty tag in webservice XML response. Thank you @pumamood #14246: Add doctrine filters applicator. Thank you @sarjon #14529: Fix position problem on a fresh install, by @PierreRambaud #14545: Remove english emails since they are generated now, by @jolelievre #14552: Use variable instead of recomputing, by @jolelievre #14560: Typo fix on bug issue template, by @PierreRambaud #14576: Merge 1.7.6.x to develop - 10/07/2019, by @matks #14592: Merge 1.7.6.x to develop - 11/07/2019, by @matks Back office #12997: [+] BO: add disable visual effect on translations. Thank you @francoispeyret #13529: Migrate Sell > Catalog > Monitoring listing action. Thank you @zuk3975 #14198: Add Commands/Queries Profiler tab. Thank you @sarjon #14249: Case-insensitive hook dispatching. Thank you @tomas862 #14308: #14302 : Duplicate Product in BO with several taxes (multishop). Thank you @202-ecommerce #14320: Introduces NumberMinMaxFilterType and IntegerMinMaxFilterType. Thank you @tomas862 #14525: Fix php warning in php 7.2 in case of JSON output. Thank you @202-ecommerce #14530: Use Preview link without option for seo preview, by @PierreRambaud Front office #14437: Translate aria-label in modal close button. Thank you @davidglezz #14507: Fix bug of FO translations with multiple resources and tpl inclusions. Thank you @202-ecommerce #14567: Remove image in about us cms page, by @marionf Tests #14508: Integrate Puppeteer to check links on FO and BO, by @mbadrani #14531: Remove another faulty e2e test from Travis, by @matks Code changes in the “1.7.6.x” branch (for v1.7.6.0) Core #14562: Update Changelog for v1.7.6.0 after RC2, by @jolelievre #14579: Fix many things that were supposed to be removed during build not being removed, by @eternoendless Back office #14532: Check if index.php file exists before ignoring it, by @jolelievre Code changes in modules, themes & tools Docker #167: Release 1760, by @jolelievre Live demo service #7: Revert “Adapt api domain regarding the current domain” and use env var in build, by @Quetzacoalt91 Mail alert #20: Uninstall module used on PS 1.6 before using this one, by @Quetzacoalt91 E-mail subscription form #34: Patch 1. Thank you @Codencode Auto Upgrade #329: Deploying v4.9.0 of the autoupgrade module, by @Quetzacoalt91 #331: Split upgrade & backup process, by @Quetzacoalt91 classic-rocket #73: Unclosed tag. Thank you @antoninblasco Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @202-ecommerce, @antoninblasco, @Codencode, @davidglezz, @francoispeyret, @pumamood, @sarjon, @tomas862, @zuk3975! 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

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 15th to Sunday 21th of July 2019. General messages Dear Developers, If you want to follow the work done on the upcoming patch release, please go on GitHub and watch the dedicated milestone for PrestaShop 1.7.6.1. You will see that some work has already been done (closed items). And of course, the work in progress is available too (opened items). A quick update about PrestaShop’s GitHub issues and pull requests: 123 new issues have been created in the project repositories; 67 issues have been closed, including 13 fixed issues on the core; 49 pull requests have been opened in the project repositories; 44 pull requests have been closed, including 32 merged pull requests. Code changes in the ‘develop’ branch Core #14089: Fix #14085 Shop url with port in header HOST. Thank you @202-ecommerce #14352: Move Cart secure_key setter at the right place, by @jocel1 #14691: Update version to 1.7.7.0, by @jolelievre Back office #14307: Fix manufacturers grid logo to not depend from shop context. Thank you @zuk3975 #14466: Fix saving of selected BO language. Thank you @rokaszygmantas #14540: Update Import controller to get errors for bad category import. Thank you @webmak #14543: Wrong path of products thumbnails in back office, by @matthieu-rolland #14605: Do not use encodeURIComponent with POST data, by @PierreRambaud #14613: Broken translation in module list page:, by @matthieu-rolland #14656: Fix editing shop association in Category and Manufacturer. Thank you @zuk3975 Front office #12880: Add breadcrumb to the new products page. Thank you @SebBareyre #12881: Add breadcrumb to the prices drop page. Thank you @SebBareyre #12882: Add breadcrumb to the best sales page. Thank you @SebBareyre #12883: Add breadcrumb to the suppliers page. Thank you @SebBareyre #13677: Submenu hides menu. Thank you @YeLnatSs #14214: Handle shoppingcart error returns properly - part 2, by @matks #14558: Implement Schema ItemList for products listing & Fix Schema Product, by @Progi1984 #14587: Fix issue when searching for long words in FO, by @matthieu-rolland Tests #14231: PHPUnit no expectation annotation. Thank you @MathiasReker #14287: Behat tests for Category. Thank you @sarjon #14593: First POM implementation, by @SimonGrn #14612: Update docker for puppeteer, by @boubkerbribri #14725: Move travis scope from 5.6 to 7.1, by @matks Web services #8769: WS: Auto generate link_rewrite and do not require it when creating ca…. Thank you @marekhanus Code changes in the “1.7.6.x” branch (for v1.7.6.0) Back office #14673: Fix Orders view page link to transform guest to customer, by @matks #14701: Fix log delete all action on Logs page, by @matks Code changes in modules, themes & tools Shopping cart #41: The modal “add to cart confirmation” is not displayed on error. Thank you @jf-viguier Decimal #5: Add support for exponential notation, by @eternoendless TranslationFiles #6: Add translations files for 1.7.7, update latest on 1.7.6, by @jolelievre Customer reassurance block #20: Major refactoring, by @Progi1984 #21: Some fixes for v4, by @matks classic-rocket #74: Remove bs class and add utilities + make the button more ergonomic on phone. Thank you @Kmoulun Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @202-ecommerce, @jf-viguier, @Kmoulun, @marekhanus, @MathiasReker, @rokaszygmantas, @sarjon, @SebBareyre, @webmak, @YeLnatSs, @zuk3975! 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

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 1st to Sunday 07th of July 2019. General messages Dear Developers, Last week was a very warm week, right? Did you find a solution to stay productive in your area? If week 26 was a small week considering the numbers of pull requests, week 27 is one of the biggest of this year ! Work on 1.7.7 has started on the develop branch, and the work to finish the 1.7.6 has been merged. Also, a lot of work has been done on modules. Well done! If week 26 was a small week considering the numbers of pull requests, week 27 is one of the biggest of this year! Work on the develop branch is very active again to prepare the 1.7.7, and the work to finish the 1.7.6 has been merged. Also, a lot of work has been done on modules. Well done! A quick update about PrestaShop’s GitHub issues and pull requests: 61 new issues have been created in the project repositories; 56 issues have been closed, including 12 fixed issues on the core; 59 pull requests have been opened in the project repositories; 78 pull requests have been closed, including 56 merged pull requests. Code changes in the ‘develop’ branch Core #14043: Check if Combination id is set before deleting Associations from data…. Thank you @kazeno #14403: Fix cookie collisions from PR # 14116 and improve overall security. Thank you @mvorisek #14425: Merge 1.7.6.x to develop - 28/06/2019 , by @matks #14459: Merge 1.7.6.x to develop - 03/07/2019, by @matks #14510: Merge 1.7.6.x to develop - 05/07/2019, by @matks Back office #10780: Custom error pages. Thank you @sarjon #13959: BO : JS files duplicated. Thank you @idnovate #14223: Bugfix: Fix unescaped dash in character group in regex. Thank you @mvorisek #14310: Adds missing fields validation in tax create/edit handlers. Thank you @zuk3975 #14450: Whitelist filters for the Logs Page. Thank you @Progi1984 Front office #14049: Allow template vars override in hook actionFrontControllerSetVariables, by @Matt75 #14263: Fix display voucher conversion between currencies, by @tomlev #14422: Refactor theme usage of product flags - apply DRY, by @matks #14452: Permit to buy a product without stock when other combination have stock and unavailable product attributes are not displayed. Thank you @Progi1984 Tests #14491: Disable Selenium Guest scenario as it fails randomly, by @matks Code changes in the “1.7.6.x” branch (for v1.7.6.0) Core #14438: Testing the factory with number and price specifications, by @PierreRambaud #14453: Update facetedsearch to 3.0.6, by @PierreRambaud #14503: Update changelog for 1.7.6.0 RC 2, by @matks Back office #14460: Ignore index.php files in Doctrine entities scanning, by @jolelievre Front office #14444: Check if selected address belongs to user, by @PierreRambaud Tests #14467: Remove unwanted e2e tests, by @PierreRambaud Code changes in modules, themes & tools Google sitemap #106: Do not call getIsset() with getValue(), by @Quetzacoalt91 #107: Add all images of a product to the sitemap, instead of only the cover image. Thank you @Pixep Nightly-board #9: Disable reports, by @PierreRambaud Gamification #61: Fix the deprecated create_function for PHP 7.2, by @eternoendless #67: Undefined variable when running in fancybox, by @PierreRambaud #68: Bump version to 2.3.1, by @PierreRambaud #69: Release 2.3.1, by @PierreRambaud Example Module Mailtheme #1: Update modules after changes from the core, use two different templat…, by @jolelievre #2: Update min version, by @jolelievre CsaGuzzleBundle #2: Allow PHP 7.1+ support with Guzzle 5. Thank you @Progi1984 Faceted search #94: Uninstall module used on PS 1.6 before using this one, by @Quetzacoalt91 #102: Make filter show limit working again, by @PierreRambaud #103: Fix facet display when there is only one filter, by @PierreRambaud #104: Split currency if a ; is present in the format string, by @PierreRambaud #105: Fix for cache problem when used as widget. Thank you @iqit-commerce #106: Bump to 3.0.6, by @PierreRambaud #107: Release 3.0.6, by @PierreRambaud #109: Fix ps_facetedsearch.tpl vars. Thank you @davidglezz #110: Do not use seoUrl if user do not want to use it, by @PierreRambaud #111: Fix ie11 compatibility, by @PierreRambaud #112: Bump to 3.1.0, by @PierreRambaud #113: Release 3.1.0, by @PierreRambaud Google Adwords #6: Deploy v2.0.0 of the gadwords module, by @Quetzacoalt91 #7: Fix typo error on module installation, by @apacios #8: Bump version to 2.0.1, by @Quetzacoalt91 #9: Deploy v2.0.1 of the gadwords module, by @Quetzacoalt91 Auto Upgrade #284: Display a notice if PHP is below v7.1, by @Quetzacoalt91 #325: Prepend and optimize autoloader, by @Quetzacoalt91 #326: Add PHPDoc & log when module switch the current theme, by @Quetzacoalt91 #327: Update logs around zip upgrade, by @Quetzacoalt91 #328: Bump version to 4.9.0, by @Quetzacoalt91 classic-rocket #51: Error alert is not shown on update cart error. Thank you @morfin Changes in documentation #269: Email theme generation documentation, by @jolelievre #299: Typo. Thank you @idnovate #300: Doctrine usage, services definition, modern tabs, by @jolelievre Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @davidglezz, @idnovate, @iqit-commerce, @kazeno, @morfin, @mvorisek, @Pixep, @Progi1984, @zuk3975! 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

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 24th to Sunday 30th of June 2019. General messages Dear Developers, Core weekly edition is a bit late, mainly due to beginning of the summer and the first vacations of the team. So, how is the 1.7.6.0 release? Tell us in the comments, now that you have a few experience with it. Some major issues have been identified, and a 1.7.6.1 release is already on track. A quick update about PrestaShop’s GitHub issues and pull requests: 77 new issues have been created in the project repositories; 29 issues have been closed, including 6 fixed issues on the core; 49 pull requests have been opened in the project repositories; 19 pull requests have been closed, including 16 merged pull requests. Code changes in the ‘develop’ branch Core #14116: do not set a cookie if it finally has not changed, by @jocel1 #14340: Merge 1.7.6.x to develop - 24/06/2019, by @matks Front office #14385: Fixed duplicated block name. Thank you @aleksiuno Code changes in the “1.7.6.x” branch (for v1.7.6.0) Core #14367: Update contributors and changelog for 1.7.6.0 RC 1, by @matks #14400: Wrong way to retrieve CLDR information, by @PierreRambaud Back office #14331: Handle bad theme error nicely, by @matks #14364: View button doesn’t have href, by @PierreRambaud #14401: Fix grid calendar, by @jolelievre Front office #14395: Classic theme force all type number to don’t have arrows , by @PierreRambaud Code changes in modules, themes & tools QANightlyResults #1: Little changes, by @PierreRambaud Gamification #65: Bump version to 2.3.0, by @PierreRambaud #66: Release 2.3.0, by @PierreRambaud Google Adwords #5: Rework of the whole module, by @apacios Changes in documentation #281: Documenting module creation part 1 - identifiable object form and grid hooks usage. Thank you @tomas862 #290: Add config/defines.inc.php configuration values, by @Quetzacoalt91 #298: Added Default section, by @mickaelandrieu Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @aleksiuno, @tomas862! 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

We are happy to announce PrestaShop 1.7.6.0 is officially available! It has been quite a journey to deliver this huge release, our biggest yet since 1.7.1.0. Six months of development, a six week-long Beta, two Release Candidates… Was it worth it? We absolutely think so, and hope that you will enjoy using it. In this version we focused on improving and bringing back important 1.6 features to merchants, and kept working on code quality and performance improvements. We have made important progress on the Symfony migration as well. Download PrestaShop 1.7.6.0 now! Be careful! If you plan to upgrade, we recommend you to use the version 4.9.0 of the 1-click upgrade module. You can upgrade it from the “Module Manager" tab, or if you don’t have it yet, find it in the “Module Catalog” tab in your BO. Changes This minor version is our biggest since 1.7.1. Here is 1.7.6 in numbers: 748 merged Pull Requests (vs 210 in 1.7.3, 260 in 1.7.4 and 448 in 1.7.5) 7349 files changed (294661 insertions, 107638 deletions) 4431 commits merged 249 issues fixed 108 people contributed, including 60 new contributors! New features Front office New design for transactional emails (optimized for mobile display), which strengthen the customer relationship and improve the shopping experience. Improved display of the price details (product price, shipping, taxes, etc.) at all key stages of the purchasing process to improve customer reassurance and conversions. New profile menu with direct access to resources (documentation, training, agencies, help center…). Updated version of the Product Comments module, with rich snippets. Available on 1.7.6+ versions. Fully refactored faceted search (for sorts and filters) on the categories and listings pages with the addition of a price slider. The new version is available for all 1.7.1+ versions. Improved Catalog mode: for showcase websites, you can now choose to display or to hide product prices. Improved currency management subsystem. This is the basis to allow more customization in the next versions, adding custom currencies for example. Improved SEO for products with combinations. Back office Manage and preview your transactional emails directly from a new back-office page: Email Theme. In order to gather all prices in the same place, a “Price (tax incl.)” column has been added to the product listing. In one glance, it is now possible to get both tax included and excluded prices for each product. New helper cards have been added on important pages to improve the software onboarding: Categories, Customers, Pages, Employees. Dynamic preview of search engine results have been added to more pages: Product page, Categories, CMS. The watermark module has been updated to 1.7 - thanks to the community. The module is available in the Module Catalog. Improved translation system for multilingual modules. The Design section of the back office has been reworked. Now you are able to have an overview of all design features (RTL, logos, favicon and theme) and manage them the way you want. Optimized back office administration on mobile devices. Major Bug Fixes Front Office Checkout used to proceed automatically from carrier selection to payment selection, it was an issue for some carrier modules requiring extra configuration steps in the carrier selection. Enhanced security checks for virtual goods. Previously anyone with the correct link (correct &key=… URL parameter) could download a virtual good. We fixed a longtime bug that was creating an error in discount calculation when adding a cart rule in a cart containing only virtual product. In the meantime, we also fixed a bug on carrier price calculation. Price is now calculated on the real order price and not the one including after a discount is applied DNI fields is now forced only for countries which require it Fixed the minimum order in the second currency bug - fixed by the community Core Themes are not reset anymore when already active (also prevent hooks to be reset) - fixed in the Autoupgrade module The technical side Technical improvements Nightly builds and nightly board are now available. Translation Manager of Back Office can now manage legacy translations of modules as well as symfony modules Added support for Doctrine Entities in modules (both Front and Back-office) Price computation is now covered by Integration tests powered by Behat (human-readable tests) New mail template system based on Twig, along with a new generation system which avoids downloading all the mail templates; will allow easier customization in the future versions New CLDR standard implementation: improved localization of prices and amounts, will allow creating custom currencies in future versions Support for multiple grids on the same page Performance: Improved employee authorization process Cache introduced when loading modules The number of SQL requests to get the employee authorizations has been significantly reduced Web services: Product customization is now reachable Product combination information in Pack content is now available New hooks displayProductActions (Product page, close to the “Add to cart” button) displayPersonalInformationTop (Checkout funnel, before the customer login form) additionalCustomerAddressFields (In CustomerAddressFormatter) actionProductFlagsModifier (Allows to customize product flags) Form hooks Kpi hooks Mail generator hooks: actionListMailThemes actionGetMailThemeFolder actionBuildLayoutVariables actionGetMailLayoutTransformations See all hooks in the DevDocs Improved hooks actionProductAdd now receives id_product_old when duplicating a product Breaking or risky changes The new CLDR implementation replaces the old one. Some breaking changes were needed: The Currency ObjectModel is now multilingual The IcanBoogie/CLDR library has been removed Calls to Tools::getCldr() throw a PrestaShopException The namespace “PrestaShop\PrestaShop\Core\Cldr” has been removed The CLDR files in the “/translations” directory have been removed Import: You no longer can just add categories to current categories with import to a force ID. You will have to set them all and the first will become the default_category.) Replaced library: PhpExcel (no longer supported) has been replaced by PHPSpreadsheet) Version comparison: AppKernel::MAJOR_VERSION is now “7” instead of “17” “1.2.4” is no longer greater than “1.2.3.4” (the latter is now interpreted as “2.3.4”) Endpoints other than index.php have been deprecated: All BO endpoints now require a token AdminModelAdapter.php now requires the Router in its constructor The following currencies are no longer available: BYR: Belarusian Ruble (2000–2016) LTL: Lithuanian Litas (end 2014-12-31) STD: São Tomé & Príncipe Dobra (end 2017-12-31) Other: Slashes are no longer removed from $_GET and $_POST variables src/Core/Addon/Module/ModuleManager.php::_construct() receives an instance of CacheClearerInterface instead of CacheClearer Permissions for files created by PrestaShop are no longer set to 0777. Permissions are now set to 0755 for directories and 0644 for files To prevent having jQuery included twice, It is no longer possible to add jQuery in BO controllers based on the new theme using addJquery() Error messages are no longer html escaped automatically PrestaShop ❤ Community PrestaShop is above all a community project: from the 108 committers who contributed to this release, 60 are new contributors. The vast majority of PrestaShop contributors are not directly affiliated with the PrestaShop company. A huge thanks to everyone involved in this version! Thank you again for helping improve the lives of more than 300,000 online merchants with ideas, improvements, and fixes! Download You can download PrestaShop 1.7.6.0 here: Download PrestaShop 1.7.6.0 now! PrestaShop 1.7.6 is also available through the 1-Click Upgrade module. Please use the v4.9.0 version of the module to avoid compatibility issues with PS 1.7.6. And don’t forget to give us your feedback in the comments or on Github! View the full article

Contributing to PrestaShop is not only about the code, it’s also about taking part in the PrestaShop translation project! This report tells you how the translations of the software evolved in June. Project news Summer goodies Before going on summer vacation, I’m glad to let you all know goodies are now being sent to the best translators – last session was in March. Go to your Crowdin profiles to check if you are among our top contributors for those last few months, we might need to send you a little something in order to thank you… and if you are, congratulations, it is time to have a look at your letterbox. ;-) Special thanks to newcomers Many people subscribe to the project(s) of their choice each month, but not so many start translating straightaway. For that reason, we would like to thank the ones that kind of rush into the effort immediately, aha! So lot of love to the dedicated alexandre.beyonds, bkmcrowdin, half Rockstar (snfxgsx), Harlas, Jose Marfil (mescalitog), JossVans, lucasgomezortiz, Marvin Licup (marvinlicup25), Patricia Marie Anunciacion (pmcagamboa), Peeyush Agrawal (Peeyush), Petr Blaha (blahapetaand), and Tantely R. (rabtaray). See you soon on Crowdin… and PrestaShop. ;-) A few stats 49 members were active on the project this month. A total of 25,565 words have been translated and 25,413 validated. All this in 35 different languages. Thank you for your involvement! Top contributors A lot of you are working every day on Crowdin to have PrestaShop available in many languages, and we can’t thank you enough for your dedication! Here are the most active translators and proofreaders for June 2019. Top 10 translators in June: Translator Language # Words 1. Zoran Tejic (zotamal) Serbian (Latin) 8,518 2. Svemirac Serbian (Latin) 3,736 3. Rivo Zängov (Eraser) Estonian 3,677 4. Tantely R. (rabtaray) Malagasy 2,267 5. Jash Technologie (jash_tech) Polish 818 6. Patricia Marie Anunciacion (pmcagamboa) Tagalog 769 7. half Rockstar (snfxgsx) Arabic 608 8. Cha (cafetango) Chinese Traditional 521 9. bkmcrowdin Swahili 454 10. SeongHyeon Cho (jaymz9634) Korean 397 Top 10 proofreaders in June: Proofreader Language # Words 1. Zoran Tejic (zotamal) Serbian (Latin) 9,084 2. Rivo Zängov (Eraser) Estonian 7,261 3. scienceangel Serbian (Latin) 3,501 4. SeongHyeon Cho (jaymz9634) Korean 1,830 5. Cha (cafetango) Chinese Traditional 1,224 6. webdvl (megashopba) Czech, Slovak 737 7. Gerardas (gerardas) Lithuanian 273 8. Enzo Ferrara (ferribbotte) Italian 247 9. Stamatis (breezer) Greek 244 10. Rodrigo Laurindo (rblaurin) Portuguese, Brazilian 240 Congrats, and welcome to our new top contributors! Remember, you can see who’s been contributing to our translation project thanks to the Translators page. Complete translations Fully translated languages At the end of June 2019, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 31 languages: Bulgarian Catalan Croatian Czech Danish Dutch English Estonian French French, Canada German Greek Italian Indonesian Latvian Lithuanian Macedonian Norwegian Persian Polish Portuguese Portuguese, Brazil Romanian Russian Slovak Slovene Spanish Swedish Turkish Ukrainian Vietnamese For its part, PrestaShop 1.7.6 was fully available in 7 languages! Czech Danish Estonian Portuguese, Brazil Slovak Serbian Swedish Languages with the best evolution In comparison with May 2019, the following languages had the best progress thanks to the translation community: Estonian (+11% to reach 100% approved in 1.7) Polish (+2% to reach 98% translated in 1.7) Korean (+2% to reach 98% approved in 1.7) Thanks to all the contributors! Of course, this is highlighting the languages that made some progress with new translations; but it doesn’t mean that the languages that aren’t mentioned here aren’t active. Indeed, some editing and rewriting could be going on, but the percentage of translation wouldn’t be modified (since it’s working on strings that are already translated). So let’s not forget about the work of these proofreaders! Thank you too! Languages that need (more) proofreaders A translated string will not be available in PrestaShop as long as it is not validated. For this reason, it’s important we should keep a good level of validated strings vs. translated strings, to make sure everyone benefits from the latest translations! At the end of June 2019, some languages would still benefit from some proofreading: Spanish, Argentina (100% translated vs 16% validated in 1.6). Galician (97% vs 61% in 1.7). Spanish, Venezuela (53% vs 17% in 1.6). Tagalog (54% vs 24% in 1.6). Chinese Simplified (96% vs 69% in 1.7). If you wish to help to proofread what has been translated, please contact us with the language you’d like to proofread: just send an email to translation@prestashop.com. We need your help! If you haven’t joined us on Crowdin yet, it’s never too late! If you want to gather your fellow translators to work towards a better harmonization, start a glossary, or anything else, do let us know: we’ll include a word about it in the next monthly report. Do you have a question, a remark? Don’t hesitate to leave a comment. See you next month! View the full article

Once again the PrestaShop community actively participated in the testing of the PrestaShop 1.7.6 Release Candidate. Thanks to your involvement, 3 regressions were identified and fixed. Our team is glad to announce PrestaShop 1.7.6.0 Release Candidate 2. If no new regression is reported in the next days, we will make the final version of 1.7.6.0 available by the end of next week (28). Fixed in this Release Candidate 2 Front Office: Issues with prices and currencies display in Dutch due to a bug in the method used to parse CLDR data. If you experienced some missing decimals that was the cause. We decided to take some time to verify everything is working well on the 40 main languages used on PrestaShop, and it does! More improvements on currency management will be shipped in the 1.7.7 version. On Firefox browser, duplicate arrows were displayed in the shopping cart product quantity field. Back Office: Grid display error on the Add/Edit Customer page introduced by a previous PR to allow this page to extend in width. Annotation driver settings improvement to ignore index.php files in Doctrine entities folder. Not a regression but a possible error case for modules using Doctrine Security: There was an issue in the checkout process that could be used to select any delivery address existing in the db when placing an order, not only the ones owned by the customer. The fix makes sure a customer can only use the addresses he owns and also prevents the address selection for an order to be done outside of the “confirm address” step. Changelog You can find all the details about this version in the Changelog. A huge thanks to everyone involved in testing and fixing issues during the RC1 phase, and especially sdwebdesign who helped us to identify this tricky prices display regression! If you are looking for more details about all changes and new features expected in 1.7.6, the 1.7.6 beta version release note is the perfect article for you to read! Download You can download PrestaShop 1.7.6 RC2 here: Download PrestaShop 1.7.6 RC2 now! How to help finish the 1.7.6 Your help will be very appreciated to finish the work on PrestaShop 1.7.6. Even if you are not a developer, your feedback has a lot of value. You can: Install it and test that there is no regression compared to the 1.7.5.2 version If possible, test with data imported from a real shop If you develop modules or themes, test them on this version Report bugs on GitHub (read how to report issues) Submit a bug fix by creating a pull request (read the contribution guidelines) If everything is working well, feel free to comment on this article to tell us, and share on social networks, we also need this kind of feedback! ;-) View the full article

This last year, the PS company has been facing a dilemma: how to dedicate 100% of the developers’ time to move forward faster on the 1.7 version of the open source project, something everybody agrees on. And, at the same time, provide more time for merchants still using the 1.6 version to get ready to upgrade, by keeping them safe in case of critical issue [after the official support ends on the 30th of June 2019[(https://www.prestashop.com/en/blog/maintenance-extension-prestashop-1-6). We have come up with a solution, thanks to the initiative and support of a few volunteers from the PrestaShop developer community: allowing them to take over the responsibility of maintaining PrestaShop 1.6.1.x beyond the end of official support. What does it mean? Put it simply, from the 1st of July 2019, the maintenance of PrestaShop 1.6.1.x is now being performed exclusively by volunteers. If a critical issue is discovered (we think mainly of security vulnerabilities), this team of volunteers will look for solutions from the community, work on it through a process of code review and extensive testing, in order to release a patch version to solve this critical issue. Those patch versions will not be officially issued by PrestaShop nor available on prestashop.com, instead, they will be available on a dedicated GitHub repository: https://github.com/PrestaShop/PrestaShop-1.6 On this repository, it will be possible to submit pull requests in order to fix critical issues to be shipped in a patch version for PrestaShop 1.6.1.x. Scope of the maintenance The volunteers and the PrestaShop company have agreed on the following objectives: Fix critical issues (like the recent spam attack on account creation form) or security issues Eventually, if this is considered possible, allow PrestaShop 1.6 to be run with PHP 7.2 Consequently, non critical issues and pull requests for the 1.6 version which are not related to one of those objectives will not be merged and will be archived. This will help the new maintainers stay focused on critical patch versions. If you find a security vulnerability in the software, the process stays the same: Don’t speak about it publicly immediately Instead, please send an email to security@prestashop.com with details about the issue, how to reproduce it, and any other interesting details You can of course submit a patch proposal in the email When the patch is approved and the release available, you can speak about it If you want to participate in making the 1.6.1.x work with PHP 7.2: Please open a pull request on the dedicated repository It will be reviewed by the maintainers, of course they might ask you more information and modifications in order to approve The aim is to write good code and use best practices, and avoid “sticking-plaster” Similarly to the main open source project repository, each pull request will have to be approved by two maintainers before being merged, in order to be sure that it is well written and that it is not introducing new problems. When a patch version has been tested and approved by the maintainers, a build will be released on GitHub with the help of developers from the PrestaShop company. The volunteers A short presentation of the volunteers: Olivier Le Corre, who started the discussion about this idea at the PS-Connect Lyon this Spring, a freelancer and long time active member of the ecosystem Maxime Varinard, from the software editor Vaisonet, a specialist on synchronization of PrestaShop with other information systems Krystian Podemski, Polish ambassador and freelancer, also a long-time and well-known member of the community Danoosh Miralayi, from iPresta team, the Iranian agency at the origin of the RTLimplementation for arab and persian languages in PrestaShop How to upgrade As eventual upcoming versions will not be official versions by the PrestaShop company, they will not be listed in the auto-upgrade module. However, it is possible to provide a zip of the installer to the auto-upgrade module and launch the upgrade anyway. And of course, other ways are available, like Migration Pro and manual updates. A usual, it is recommended to be careful before starting to update your website to the latest patch version: Backup your database and your files Test the update on a testing or pre production server If everything is fine, then update on the production environment If you don’t have the technical skills, do not hesitate to find an expert. Many freelancers and agencies know how to do that well. When will this maintenance stop When no volunteers will be available to maintain the 1.6 anymore, it will become obvious that this will be the real end. It will of course depend on many things: How fast merchants, freelancers and agencies migrate and adopt the 1.7 How many merchants choose to keep their shop on 1.6, for whatever reason. The most probable one is that some shops have been heavily modified to adapt the software to the business workflow and specificity, and are difficult to migrate in that state. How fast web hosting companies will force the use of new versions of PHP. How difficult it will be to eventually patch the legacy code to support new versions of PHP. View the full article

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 17th to Sunday 23rd of June 2019. General messages Dear Developers, A lot of work was done last week to be able to fix all known issues on the beta, and ship a release candidate of 1.7.6. A few regressions have been found on the RC1 and a RC2 should be built soon, stay tuned. A quick reminder for those in South West of France, next week the PrestaShop team and partners will in Bayonne’s PS-Connect. Let’s meet together before the summer vacations. A quick update about PrestaShop’s GitHub issues and pull requests: 68 new issues have been created in the project repositories; 58 issues have been closed, including 16 fixed issues on the core; 65 pull requests have been opened in the project repositories; 78 pull requests have been closed, including 47 merged pull requests. Code changes in the ‘develop’ branch Core #14232: string line ending. Thank you @MathiasReker #14233: dir constant. Thank you @MathiasReker #14273: CO: Fix Sql Error due do while not ended. Thank you @123monsite-regis #14286: Merge 1.7.6.x to develop - 19/06/2019, by @matks Tests #14109: Cover Webservice keys with Behat tests. Thank you @sarjon #14234: Add missing braces. Thank you @MathiasReker #14235: Remove unused imports. Thank you @MathiasReker Code changes in the “1.7.6.x” branch (for v1.7.6.0) Core #13795: Updates to Domain. Thank you @sarjon #13925: Add getter for current locale, by @eternoendless #14197: Update facetedsearch dependency, by @PierreRambaud #14284: Update to Faceted search 3.0.5, by @PierreRambaud #14300: &= prevents result to be a boolean, by @Quetzacoalt91 #14316: Reapply changes from PR switching on PHPSpreadsheet, by @Quetzacoalt91 #14324: Use Admin.Actions instead Admin.International.Help, by @PierreRambaud Back office #14220: Set schema form rendered when it contains no children, by @jolelievre #14239: Introduce the usage of Module user-displayable exceptions to handle module errors (part 2), by @matks #14242: Module form_rest() outside div, by @jolelievre #14248: Cannot use accented URL with arabic language, by @PierreRambaud #14259: Avoid bug when creating manually created a language, by @jolelievre #14290: Extend customer page, by @jolelievre #14292: Update php-cs-fixer to latest version. Thank you @MathiasReker Front office #14251: Fix categories wordbreak, by @jolelievre #14296: Fix carrier display in order confirmation email, by @jolelievre #14298: Fix english mail generation on fresh install, by @jolelievre #14309: Simplify the installation language to its minimum, by @jolelievre #14325: Refresh product flags on ajax call when product page is refreshed, by @matks Install #14225: Update facetedsearch cache, by @PierreRambaud #14243: Fix translation catalogue, by @eternoendless Tests #13999: Fix broken tests. Thank you @nesrineabdmouleh #14187: Minor fixes for E2E tests (adding pauses, adding async code, referencing blocking issues), by @SimonGrn #14219: Fix test Module ‘04_sort_module’ in suite full, by @boubkerbribri #14221: Fix “14_discount/3_check_vouchers_in_FO” in full campaign. Thank you @nesrineabdmouleh #14282: Fix download in E2E tests, by @PierreRambaud Code changes in modules, themes & tools Translation tools bundle Auto upgrade #322: Fix warning in 1.7 when settings file does not exist. Thank you @jf-viguier #323: Revert “Fix warning in 1.7 when settings file does not exist”, by @Quetzacoalt91 Gamification #63: Improve UI. Thank you @YeLnatSs Faceted search #97: Fix the display of wrong Availability count , by @PierreRambaud #98: Bump to 3.0.5, by @PierreRambaud #99: Realease 3.0.5, by @PierreRambaud Link list #67: Fix extra star in the link block form, by @jolelievre #68: Merge to master for v3.0.4, by @jolelievre Watermark #15: [MO] Watermark - compatibility with 1.7 and ability to upload jpg, png as watermark. Thank you @rblaurin #16: Add CONTRIBUTORS.md, by @matks #17: Version update to v2.0.0, by @jolelievre #18: Update contributors, by @jolelievre #19: Update contributors, by @jolelievre Changes in documentation #279: Reworking scale section and optimizations. Thank you @djodjo3 Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @123monsite-regis, @djodjo3, @jf-viguier, @MathiasReker, @nesrineabdmouleh, @rblaurin, @sarjon, @YeLnatSs! 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