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

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:

Top 10 proofreaders in August:

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:

For its part, PrestaShop 1.7.6 was fully available in 6 languages!

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

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

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:

Top 10 proofreaders in July:

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:

For its part, PrestaShop 1.7.6 was fully available in 13 languages!

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

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

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

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

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

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

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

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!

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

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:

Top 10 proofreaders in June:

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:

For its part, PrestaShop 1.7.6 was fully available in 7 languages!

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

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

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

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

Please note that it is not currently possible to perform an automatic upgrade from the Beta to the Release Candidate. Furthermore, it will not be possible to upgrade from this Release Candidate to the final release. If you perform an update of your test store to the RC version, you will need to rollback to your current version before being able to upgrade to the final 1.7.6.0.

Go download and install this RC version as a test store, either on your machine or your web hosting, then play with it – and give us your feedback! We need YOU to test this new version of PrestaShop.

Remember, this release candidate version is pre release software. Do not use it on your production shop!

New in the release candidate

Back Office:

• Introduced an easy way for hooked modules on entity pages to handle error display (a demo module is now finished and available here)

Front Office:

• Improved error messages displayed when spam protection rejects a customer subscription and you can now translate them specifically for a better user experience

Core:

• Module Faceted search version has been bumped to 3.0.5 which contains interesting bug fixes
• Watermark and Product comments modules have been integrated and can now be installed from the Module Catalog page in the back office
• Tips and Updates module (psaddonsconnect) has been updated to the 2.0.0 version
• We have replaced PHPExcel by PHPSpreadsheet in order to better handle XLS or XLSX files import

Changelog

100+ pull requests have been merged since the beta release and 50+ regressions have been fixed. Read the Changelog for details. A huge thanks to everyone involved in testing and fixing issues during the beta phase, and especially 202 ecommerce, OneDotIT and MartinF who helped us a lot during this period !

This brings us to more than 700 merged pull requests for the 1.7.6.0 milestone, it is definitely our biggest yet.

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 RC here:

Download PrestaShop 1.7.6 RC 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 Test the auto-upgrade plugin 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

General messages

Dear Developers,

While the last bugs and regressions are being fixed on the core in order to build a release candidate, you will notice that a lot of work has been done on modules too! And new versions of very popular native modules are coming :-)

Stay tune for the release candidate.

And of course, tomorrow, don’t forget to join the PrestaShop team and partners at the Madrid event.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 65 new issues have been created in the project repositories;
• 61 issues have been closed, including 18 fixed issues on the core;
• 81 pull requests have been opened in the project repositories;
• 62 pull requests have been closed, including 52 merged pull requests.

Code changes in the ‘develop’ branch

Core

• #14130: Merge 1.7.6.x to develop - 10/06/2019 [travis investigation - dont merge/close], by @matks
• #14133: Merge 1.7.6.x to develop - 10/06/2019, by @matks
• #14165: Fix phpdoc on module stuffs, by @Matt75
• #14178: Merge 1.7.6.x to develop - 12/06/2019, by @matks
• #14192: Merge 1.7.6.x to develop - 13/06/2019 , by @matks

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #13919: Tax must be returned depending on PS_TAX_DISPLAY only, by @PierreRambaud
• #13923: Make sure index exist before getting value for gift message, by @PierreRambaud
• #14134: Combine consecutive issets(), by @Quetzacoalt91

Back office

• #13869: Extract theme folder scanning into an external class FolderThemeScanner, by @jolelievre
• #13971: Update AdminStatsController.php. Thank you @ComonSoft
• #13984: Fix bo categories, by @jolelievre
• #14084: Fixes updating name and symbol for currency. Thank you @sarjon
• #14101: Fix missing permission roles. Thank you @202-ecommerce
• #14107: Do not allow the selection of any subcategories, by @PierreRambaud
• #14137: Adds missing form_rest in Shop Parameters > Preferences. Thank you @zuk3975
• #14152: Adjust employee avatar size. Thank you @zuk3975
• #14156: Add missing null check in EditCmsPageHandler. Thank you @zuk3975
• #14172: Add missing form_errors for identifiable object forms. Thank you @sarjon
• #14189: Fix manufacturer controller using wrong DomainException ns. Thank you @zuk3975

Front office

• #13370: Fix cart refresh after voucher removal, by @matks
• #14075: Fix: If Ask for birth date option is disabled, an exception is displayed in the FO. Thank you @OneDotIT
• #14138: Add comment in Customer registration form, add better error message, by @jolelievre
• #14163: Add missing quotes in error message, by @jolelievre
• #14166: Fix categories cover images which had an incorrect format, by @jolelievre
• #14180: Improve right block on cart and checkout page, by @PierreRambaud
• #14190: You need to be authenticated to play with addresses, by @PierreRambaud

Tests

• #13773: Fix international tests. Thank you @nesrineabdmouleh
• #13953: Fixing and moving tests design from broken to suite full, by @boubkerbribri
• #14151: Force disabling debug mode, by @PierreRambaud
• #14196: Last tests fixes (page migration, language settings), by @SimonGrn
• #14222: Fix steps for Virtual product, by @boubkerbribri

Code changes in modules, themes & tools

Translation tools bundle

• #61: Handle weird node parsing, by @matks
• #63: Improve test sample and empty arg check in node parser, by @matks

Auto upgrade

• #320: Add action option in command line upgrade doc, by @Quetzacoalt91

Circuit Breaker

• #31: Introduce more generic AdvancedCircuitBreaker, by @jolelievre
• #33: Update Readme, add release-drafter config, by @jolelievre
• #34: Merge develop to master for v3.0.0, by @jolelievre
• #35: Fix a few errors reported by phpqa, by @jolelievre
• #36: Fix psalm, by @jolelievre

Faceted search

• #86: Do not erase filter when multiple selection is not accepted, by @PierreRambaud
• #87: Make features great again, by @PierreRambaud
• #88: Select on multishop table instead product table, by @PierreRambaud
• #89: fix bug indexed prices. Thank you @hafkhami
• #90: Price indexing stopped working on PS1.7.5, by @PierreRambaud
• #91: Bump to 3.0.4, by @PierreRambaud
• #92: Release version 3.0.4, by @PierreRambaud
• #93: Make sure initial population is reset, by @PierreRambaud
• #95: Typo. Thank you @MathiasReker
• #96: Lossless compression. Thank you @MathiasReker

Product comments

• #33: Improve addons block (with CircuitBreaker), by @jolelievre
• #34: Merge dev to master for v4.0.0, by @jolelievre

Shopping cart

• #20: Fix cart modal when a customized product is added to cart. Thank you @unlocomqx

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @202-ecommerce, @ComonSoft, @OneDotIT, @sarjon, @unlocomqx, @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

Project news

Malagasy

Say hello to the Malagasy translation project! It is now on our radar screens and extends once again the scope of PrestaShop. Come on, Malagasy people, subscribe here and join rabtaray on stage to make this translation project grow.

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 Abdullah_OneDot, Jonas (jonasburneika), Leon H. (leon0824), malik.krak, Rytis (Mangustux), and Neha Patel (nirupateldm). See you soon on Crowdin… and PrestaShop. ;-)

A few stats

• 56 members were active on the project this month.
• A total of 63,533 words have been translated and 57,226 validated.
• All this in 32 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 May 2019.

Top 10 translators in May:

Top 10 proofreaders in May:

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 May 2019, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 31 languages:

For its part, PrestaShop 1.7.6 was fully available in 9 languages:

Languages with the best evolution

In comparison with April 2019, the following languages had the best progress thanks to the translation community:

• Serbian (Latin) (+23% to reach 100% translated in 1.7)
• Spanish (Mexico) (+2% to reach 55% approved in 1.7)
• Thai (+1% to reach 20% 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 May 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 (96% vs 61% in 1.7).
• Tagalog (52% vs 24% in 1.6).
• Chinese Simplified (100% vs 72% 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

General messages

Dear Developers,

This is the very last week to finish the beta tests and fix all discovered bugs and regression. Then, time for the first release candidate will come. The target is still to be able to release 1.7.6.0 at the end of June.

You can track the work being done with the dedicated 1.7.6 Kanban on GitHub. And if you want to help, just pick a task, write some code, and open a pull request.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 72 new issues have been created in the project repositories;
• 59 issues have been closed, including 11 fixed issues on the core;
• 40 pull requests have been opened in the project repositories;
• 48 pull requests have been closed, including 34 merged pull requests.

Code changes in the ‘develop’ branch

Core

• #14051: Merge 1.7.6.x to develop - 01/06/2019, by @matks

• #14099: Merge 1.7.6.x to develop - 06/06/2019, by @matks
• #14130: Merge 1.7.6.x to develop - 10/06/2019 [travis investigation - dont merge/close], by @matks
• #14133: Merge 1.7.6.x to develop - 10/06/2019, by @matks
• #14134: Combine consecutive issets(), by @Quetzacoalt91

Back office

• #13382: Change input type for specific price reduction. Thank you @YeLnatSs
• #13515: Migrate Sell > Catalog Brands & Suppliers > Suppliers view action. Thank you @zuk3975
• #13894: displayBackOfficeTop hook should be in nav container. Thank you @jf-viguier
• #13971: Update AdminStatsController.php. Thank you @ComonSoft
• #14004: Fix generate path thumbnail image. Thank you @dariusakafest

Front office

• #13383: Some UI improvements for Front-office. Thank you @YeLnatSs
• #14033: Introduce FO JS event showErrorNextToAddtoCartButton to handle shoppingcart error returns, by @matks

Tests

• #13790: Add Behat tests for Currency Domain. Thank you @sarjon

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #14027: Fix BC break on Toggle column parameter. Thank you @sarjon

Back office

• #13919: Tax must be returned depending on PS_TAX_DISPLAY only, by @PierreRambaud
• #13923: Make sure index exist before getting value for gift message, by @PierreRambaud
• #14008: adds missing form data arguments in hooks. Thank you @tomas862
• #14021: Improved error handling when theme is uploaded or activated. Thank you @tomas862
• #14028: Add explanations about SEO cards. Thank you @sarjon
• #14029: Missing legacy link for themes page. Thank you @tomas862
• #14084: Fixes updating name and symbol for currency. Thank you @sarjon
• #14091: Do not use specific prices when displaying price with tax in BO product catalog, by @Quetzacoalt91
• #14107: Do not allow the selection of any subcategories, by @PierreRambaud

Front office

• #14075: Fix: If Ask for birth date option is disabled, an exception is displayed in the FO. Thank you @OneDotIT
• #14079: Update Smarty comments to reflect related blocks. Thank you @prestamodule

Tests

• #14053: Add ‘disable dev shm usage’ to chrome options for headless chrome, by @boubkerbribri
• #14055: Using shm_size in docker File instead of ‘disable dev shm usage’ in chromeOptions , by @boubkerbribri
• #14060: Fix CLDR Unit tests, by @eternoendless

Code changes in modules, themes & tools

PrestaShop Coding Standards

• #7: Add autoload when phpstan is hidden behind symlink, by @Quetzacoalt91

Live demo devices

Docker Internal images

Faceted search

• #76: Create a better indexation and add tests, by @PierreRambaud
• #81: Bump to 3.0.3, by @PierreRambaud
• #84: Restore what happened on master branch, by @PierreRambaud
• #85: Release version 3.0.3, by @PierreRambaud

Changes in Documentation

• #285: Remove IIS from possible system environments, by @matks

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @ComonSoft, @dariusakafest, @jf-viguier, @OneDotIT, @prestamodule, @sarjon, @tomas862, @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

General messages

Dear Developers,

That was great to meet those of you who came in Paris for the PrestaShop Day. There was a developer space, and a technical track. Many technical questions and some issues were discussed, that is what opportunities to meet in real life are made for ;-)

After Paris, PrestaShop Day Madrid is planned in 2 weeks for June 18th and will gather more than 1,200 people at La Nave Madrid - experts, open source lovers, translators, merchants, partners, etc. You can use the promotionnal code “PSDMADRIDFORUM” to get your free ticket

That said, there is only one week left to finish the Beta of 1.7.6. Once all the bugs will be triaged and fixed, the work on the first release candidate will start. It means it is still time to test the beta, report issues and open pull requests.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 51 new issues have been created in the project repositories;
• 45 issues have been closed, including 13 fixed issues on the core;
• 53 pull requests have been opened in the project repositories;
• 34 pull requests have been closed, including 30 merged pull requests.

Code changes in the ‘develop’ branch

Core

• #14012: Merge 1.7.6.x to develop - 29/05/2019, by @matks

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #14010: Update some license headers that were outdated, by @matks
• #14011: Update outdated CSS assets, by @matks

Back office

• #13774: Includes missing theme & logo page validation handling for logo and icon images. Thank you @tomas862
• #13820: Fixes form_rest placing. Thank you @sarjon
• #13875: Added help property (backported from Symfony 4 framework). Thank you @tomas862
• #13916: Fixes saving private note about customer from order page. Thank you @sarjon
• #13956: Restore legacy controller and template files deleted late in beta, by @matks
• #14007: Fix currency precision from CLDR at install, by @tomlev
• #14030: Add missing legacy link for translations routes. Thank you @rokaszygmantas

Front office

• #13905: Step clickable and not - Checkout page. Thank you @YeLnatSs

Tests

• #13713: Fix product tests. Thank you @nesrineabdmouleh

• #13961: Giving write access to selenium-chrome container to download file in selenium-downloads volume, by @boubkerbribri
• #14002: Install poppler-utils in e2e-tests container and use endAll to delete Selenium sessions, by @boubkerbribri
• #14026: Adds missing pages to survival test. Thank you @sarjon

Code changes in modules, themes & tools

PrestaShop Coding Standards

• #6: Improve PHPStan use and explanation in Readme , by @Quetzacoalt91

Live demo devices

• #6: Interface feedbacks, by @Quetzacoalt91

Docker Internal images

• #26: Add temporary tag beta, by @Quetzacoalt91

Faceted search

• #70: Reindex multistore correctly, by @PierreRambaud
• #71: Add more tests for block search, by @PierreRambaud
• #72: filtering doesn’t filter between product attributes, by @PierreRambaud
• #73: Fix touch problem on mobile, by @PierreRambaud
• #74: Render as a widget if hook is not found during the callable stack, by @PierreRambaud
• #75: Fix warning on feature / attributes and fix slider for ps 1.7.5, by @PierreRambaud
• #77: Revert “Reindex multistore correctly”, by @PierreRambaud
• #78: Revert “Add more tests for block search”, by @PierreRambaud
• #79: Multistore, by @PierreRambaud
• #80: More tests, by @PierreRambaud

Changes in Documentation

• #274: Explain how to override a simple block instead of a whole file, by @PierreRambaud
• #277: Fix a typo : “your/you’re”, by @SimonGrn

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @nesrineabdmouleh, @rokaszygmantas, @sarjon, @tomas862, @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

View the full article

General messages

Dear Developers,

As you will see, the work on the upcoming 1.7.6 version is going on well, and the faceted search module is still needing some improvements.

The PrestaShop Developers Team is also working on content for the PSD Paris 2019: most of them have a talk or a workshop. And they are eager to meet your there.

A quick update about PrestaShop’s GitHub issues and pull requests

• 84 new issues have been created in the project repositories;
• 77 issues have been closed, including 18 fixed issues on the core;
• 62 pull requests have been opened in the project repositories;
• 54 pull requests have been closed, including 46 merged pull requests.

Code changes in the ‘develop’ branch

Core

• #13554: Prepares Command/Query API for migrating “Create order” page. Thank you @sarjon
• #13865: Merge 1.7.6.x to develop - 20/05/2019, by @matks
• #13932: Merge 1.7.6.x to develop - 23/05/2019, by @matks
• #13967: Merge 1.7.6.x to develop - 24/05/2019, by @matks

Front

• #13804: Fix #9763 smarty compilation ID multi shop / multi theme. Thank you @202-ecommerce

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #13885: Force array cache for doctrine, by @jolelievre

Back office

• #13690: Theme and logo page design fixes. Thank you @tomas862
• #13797: Adds missing legacy links for currency controller. Thank you @tomas862
• #13813: Fixes toggling Category status in Monitoring page. Thank you @sarjon
• #13840: Fix resetting sort and items per page on list filters reset action. Thank you @zuk3975
• #13847: Delete legacy AdminManufacturer controller. Thank you @zuk3975
• #13849: Deletes legacy AdminCms controllers. Thank you @zuk3975
• #13850: Deletes AdminModulesPositions legacy controller. Thank you @zuk3975
• #13852: Delete legacy AdminRequestSqlController. Thank you @zuk3975
• #13857: Missing legacy links fix for employess controller. Thank you @tomas862
• #13866: fix cart rule calculation for free gift, by @tomlev
• #13887: Fix saving customer with required fields. Thank you @sarjon
• #13910: Removes AdminPreferencesController. Thank you @zuk3975

Tests

• #13826: Enable global kernel for legacy compatibility for Behat tests, by @matks
• #13862: Improve E2E report, by @PierreRambaud
• #13864: Apply develop fix on 1.7.6.x branch, by @PierreRambaud
• #13886: Add missing migrated routes to survival-test. Thank you @zuk3975
• #13900: Fixing Download behavior in tests with docker, by @boubkerbribri

Code changes in modules, themes & tools

PrestaShop Coding Standards

• #3: Target master branch to always get the latest configuration, by @PierreRambaud
• #4: Fix php doc and make overwrite message more explicit, by @Quetzacoalt91
• #5: Update default phpstan config for level 1, by @Quetzacoalt91

Legal Compliance

• #41: Fix multilingual strings displayed in frontend hooks. Thank you @alexej-d
• #65: Bump version to 3.0.2, by @eternoendless

Translation tools bundle

• #57: Drop PHP 5 support, by @mickaelandrieu
• #60: Add test for extracting wordings with no domain, by @eternoendless

Faceted search

• #59: Repair custom order, by @PierreRambaud
• #60: Error while trying to index all missing prices., by @PierreRambaud
• #61: Run PhpStan on all 1.7 versions of PrestaShop, by @PierreRambaud
• #62: Bump version to v3.0.0, by @PierreRambaud
• #63: Fix missing visibility check, by @PierreRambaud
• #64: Bump to version 3.0.1, by @PierreRambaud
• #65: Release v3.0.1, by @PierreRambaud
• #66: Restore widgets methods, by @PierreRambaud
• #67: Bump to version 3.0.2, by @PierreRambaud
• #68: Release version v3.0.2, by @PierreRambaud
• #69: Only rebuild table while upgrading to prevent a fatal error with memory, by @PierreRambaud

Amazon payment

• #86: v2.3.0. Thank you @paeddl
• #87: v3.2.9. Thank you @paeddl

Firebase Authenticator for PrestaShop

• #10: Handle missing disabled attribute, by @Quetzacoalt91

Changes in Documentation

• #271: Update module-file-structure.md. Thank you @orangevinz
• #272: Update displaying-content-in-front-office.md. Thank you @orangevinz

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @202-ecommerce, @alexej-d, @orangevinz, @paeddl, @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

View the full article

At the PrestaShop Quality Assurance team (aka QA), we browse issues on GitHub all day long. As we go about doing that, we often come across messages from people who are annoyed about a bug taking a long time to be fixed, and saying “this is a major issue, why is it still not fixed?”, or “This bug is marked as minor but it should be major”. Everyone agrees that not all bugs can be fixed at once, and that the more critical bugs should be fixed first. The problem is that since this appreciation is subjective, any opinion will almost always be challenged by the people who are personally affected by that specific issue, and who want to get it resolved first.

In order to avoid frustration and misunderstandings, it was time to come up with a better, more formal and transparent definition for the criteria used to qualify issues’ severity, and how they should be applied.

The first thing to learn is that severity is to be distinguished from priority. Indeed, severity is used to measure the negative impact that a bug has on a system, a feature, a component or on the project development. It is usually defined by the QA team. As for the priority, it is used to organize all the tasks (bugs, improvements, features, technical tasks) that have to be done in order to meet the project’s deadlines.

Issue Severity Criteria

When a new issue is created, the first step is to understand what the problem is and then reproduce it. Once that work is done, the second step is to define the severity of that bug.

Four severity levels have been defined, as explained below.

Critical

The bug affects critical functionality or critical data and there is no workaround (no way to avoid it). A critical issue affects a very large percentage of users (> 60%) and matches at least one of the following:

• It can lead to data loss, introduce a security vulnerability or break the automatic end to end tests
• It prevents the essential shop operations or puts your business at great risk

Examples:

• Difficulty accessing the front office or back office (significant slowdown, error during installation or update, fatal error)
• Difficulty to globally manage categories, products or customers
• Difficulty to globally place and manage orders

A critical issue should result in a patch version that should be released as soon as possible. PrestaShop 1.7.2.5 is a good example: this patch release fixes two vulnerabilities affecting the Back Office.

Major

The bug affects major functionality or major data and there is a workaround, but it is not obvious or can be difficult to put in practice.

A major issue affects a large percentage of users (> 30%) and matches at least one of the following:

• It impacts law compliance
• It has a strong impact on the usability of the front-office / back-office or blocks another project
• It is an important problem but not necessarily blocking the main activity of the seller

Examples:

• Being unable to add, configure or delete a theme or a module
• Difficulty in operating a module properly
• Impacts the price the customer pays

Minor

The bug affects minor functionality or non-critical data and there is a reasonable workaround, even if it can be annoying when using your shop.

Examples:

• A tolerable slowdown
• A display problem that prevents users from doing something non-critical (eg: can’t click on an element that can be accessible in another way)
• An error message displayed in your back-office that can be dismissed
• Cloning a product doesn’t copy all of it’s data
• Inaccurate statistics

Trivial

The bug doesn’t affect any functionality or data. It does not impact productivity or efficiency. It is only an inconvenience without functional impact and it does not even need a workaround.

Examples:

• Cosmetic issues
• Wrong translation in a specific language: that can be solved on Crowdin
• Missing confirmation message after an action
• A link opened in the same tab instead of a new tab

Issue Prioritization

Assessing severity helps to prioritize issues but it is not the only criterion at stake. Given two equally severe issues, how to choose one over the other ?

At PrestaShop, prioritization is done by representatives of the Development team, the Product Management team, and the Quality Assurance team. Together, during regular meetings, we look at the new confirmed issues and we sort them.

One of the things we value a lot is making sure that a given bug does not damage PrestaShop’s image nor it affects the confidence merchants can have in PrestaShop. This factor is really important as it can durably damage the adoption of the project and its long-term survival.

We take special care and strive to make every version of PrestaShop better than the one before. Since no one wants to introduce new bugs while fixing other bugs, regressions (new bugs created accidentally when fixing or improving an existing feature) are usually prioritized higher than older bugs. By doing this, we can assure that the overall software stability is ever increasing.

In addition, we also study the issue’s technical complexity, that is, whether the bug is easy or complex to fix. In some cases we will choose to prioritize a smaller bug over a bigger one, not because we are lazy, but because a complex bug may require big technical changes which are not suitable until a later version. This may be because a would require applying backwards-incompatible changes (which are bad for module developers), or because it can be better addressed as a part of a larger project – there is no use fixing a bug if the whole feature is due to be revamped in the near future. Speaking of which, sometimes we will prioritize some bugs just because of the “opportunity cost” of fixing them together, as it’s usually easier to fix several bugs within the same component. For example, during the migration of a page to Symfony, the bugs of this page are prioritized higher in order to fix them all at once.

Finally, we pay attention to the business impact. Since we care a lot about PrestaShop users (merchants, agencies, developers …), we are eager to find a solution when it affects their sales proceeds. Or ours. After all, we need to eat as well, and we use PrestaShop too.

In the end, handling bugs requires two points of view: micro and macro. Severity analyzes the issue on its own, while Priority analyzes the issue in the context of the whole project.

If you encounter an issue, please create a bug report. And if you have a solution, do not be shy and submit a pull request with your fix. This way, issues have better chances to be solved quickly, for everyone!

View the full article

View the full article

General messages

Dear Developers,

PSD Paris 2019 is just next week, and there will be a dedicated space for developers :-)

The whole PrestaShop is eager to meet you there in real life. See you next week!

A quick update about PrestaShop’s GitHub issues and pull requests:

• 58 new issues have been created in the project repositories;
• 76 issues have been closed, including 18 fixed issues on the core;
• 55 pull requests have been opened in the project repositories;
• 42 pull requests have been closed, including 37 merged pull requests.

Code changes in the ‘develop’ branch

Core

• #13736: Replace all calls to $this->l() in controllers, by @eternoendless
• #13789: Merge 1.7.6.x to develop - 15/05/2019, by @matks
• #13803: Make the movement of the Grid columns really easy, by @mickaelandrieu
• #13818: Remove redundant condition in cart.php. Thank you @davidglezz

Back office

• #13593: Automated hooks discovery and updating hooks list in xml and sql files. Thank you @tomas862
• #13798: Change input type for imap password, by @marionf

Tests

• #13811: Download in headless mode in tests, by @boubkerbribri
• #13824: Update tests and package-lock, by @PierreRambaud
• #13827: Revert “Only run deploy if the triggered commit is recent”, by @PierreRambaud

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #13665: Final retail price is not displayed due to missing CLDR files, by @PierreRambaud
• #13766: Merge 1.7.5.2 into 1.7.6.x, by @eternoendless
• #13768: Merge beta release into 1.7.6.x, by @eternoendless
• #13778: Add new hooks for Symfony migrated pages in XML install file and SQL upgrade, by @matks
• #13808: Update Symfony to latest patch version to fix ICU version problem, by @PierreRambaud

Back office

• #13165: Fix multilanguage fields configuration. Thank you @sarjon
• #13722: Filter themes without override in email generation form, by @jolelievre
• #13763: Fix help sidebar display in Customers page. Thank you @sarjon
• #13764: Fixes customer view url in notifications bar. Thank you @sarjon
• #13765: Fix sql manager bulk actions. Thank you @sarjon
• #13768: Merge beta release into 1.7.6.x, by @eternoendless
• #13777: Incorrect translation arguments passed in cms page form. Thank you @tomas862
• #13779: Allow to overwrite theme mails if they have modules OR mail templates, by @jolelievre
• #13821: Fix manufacturers, taxes lists id filtering. Thank you @zuk3975

Front office

• #12891: Fix bug on block social in footer. Thank you @YeLnatSs
• #13780: fix displayed discount on tax excluded cart display, by @tomlev

Tests

• #13726: Moving tests High to full or to broken tests, by @boubkerbribri
• #13772: Correct usage of fixtures on behat tests for taxes, by @tomlev
• #13776: Improve tests orders and category, by @boubkerbribri
• #13831: Force report name, by @PierreRambaud

Code changes in modules, themes & tools

PrestaShop Coding Standards

• #1: Integrate php cs fixer, by @PierreRambaud
• #2: Add license in composer.json, by @PierreRambaud

Docker Internal images

• #25: Call localhost to trigger the cache generation, by @Quetzacoalt91

Live demo devices

• #5: Request periodically the shop before setting its URL in iFrame, by @Quetzacoalt91

Faceted search

• #57: Update cldr javascript library, by @PierreRambaud
• #58: Add phpunit tests and quality, by @PierreRambaud

Changes in Documentation

• #248: Add deprecation notice. Thank you @dennispw
• #265: Adds options form, identifiable object forms and grid hooks docs. Thank you @tomas862
• #267: Global Smarty vars updated. Thank you @d-roduit

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @d-roduit, @davidglezz, @dennispw, @sarjon, @tomas862, @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

View the full article

Having such a place was expected by many people in the community. There was no dedicated space last year: that was possible to speak standing, exchange, but not possible to work. But this year, we do!

That’s why for this edition, the dimension of the developer space will be as big as the PrestaShop booth, with plenty of tables to put your laptops and chairs to sit down. Developers, engineers, and tech people in general, whether you are you are freelancers or working for agencies or merchants, this is where and why you must come to the PSD Paris in two weeks. And of course, developers from the PrestaShop company will be here too.

This will be the best opportunity of the year to meet and work together. So, don’t forget your laptop!

And let’s fix some issues in the core, improve native modules, go ahead on promising new projects like classic-rocket, and merge as many pull requests as possible.

Can’t wait to see you there.

Information about the PSD Paris 2019:

• 4th of June, Palais Brongnart, Paris (map)
• Programm

Get your ticket with a 50% discount, use the code PSDPARISBUILD

View the full article

View the full article

By late 2018, as the end-of-life of PHP 5.6 approached, a great deal of shared hosting providers started dropping support for that version on their services and upgrading their clients, forcibly or otherwise, to an officially maintained PHP 7.x version. Our metrics show that during the last year, the number of active shops running PrestaShop 1.7 on a PHP 7 or greater has increased significantly and is now over 75%.

PHP version support roadmap
(green background: active support; orange background: security fixes only) - (Source)

Fast forward to 2019, the exceptionally long support period that PHP 5.6 benefited from is now over. As of May 2019, PHP is back on a shorter, three-year-long version lifecycle, consisting of a new minor release every year, with two years of active support and one year of security fixes only. As a result, the PHP community has started picking up speed as well, adopting new versions and dropping compatibility with older versions faster than ever.

PrestaShop is directly affected by this change. But how exactly?

PrestaShop has many dependencies, PHP being just one of them. Dependency management has two sides: the minimum supported version, and the maximum supported version. In our case, PrestaShop 1.7.6 supports all versions of PHP from 5.6 to 7.2, but not the latest 7.3. Why not? Some of the breaking changes introduced in that version affect libraries that PrestaShop depends on and has no control over, in particular Doctrine. In that specific case, the version of Doctrine where the fix was applied has dropped support for PHP 5, which puts us in the difficult situation of having to choose to either support older PHP versions or newer ones.

Doctrine is not the only library to stop supporting older PHP versions. Many other libraries like PHP-Parser and PhpUnit have dropped support for PHP 5 for a long time. Even some quality tools, like PhpStan, never supported it in the first place, preventing us from using them.

In the case of Symfony, while they dropped support for PHP 5 on Symfony 4, PrestaShop is based on the 3.4 long-term-support (LTS) version, which is unlikely to drop support for PHP 5 in the near future.

Symfony version support roadmap. (Source)

Even though Symfony is the exception, the PHP dependency problem is becoming an increasingly complex problem, and we had to make a choice. Many other PHP-based CMS are facing the same problems: Drupal dropped compatibility with PHP 5 back in March, while Wordpress, who has traditionally supported very old PHP versions, is now requiring at least 5.6 and will soon drop it as well.

Here is what has been decided

The upcoming PrestaShop 1.7.6.0 compatibility will stay unchanged. Starting from 1.7.7.0, and for every new minor or major version of PrestaShop, the PHP compatibility range will be decided as follows:

Lower bound – Defined by the most recent version among:

• The oldest PHP version supported by our main dependencies,
• The oldest PHP version whose official support is not over, or has not been over for more than a year at the time of final release of the PrestaShop version.

Upper bound – Defined by the oldest version among:

• The latest stable PHP version available at the time of the PrestaShop version’s feature freeze,
• The latest PHP version supported by our main dependencies (whichever is the lowest).

These rules will be applied in a “best effort” philosophy.

Example

Let’s say the feature freeze date for 1.7.7 was set to be in December 2019, with a final release in January 2020.

Oldest compatible PHP version

According to the chart above, the official support for PHP 7.0 ended in December 2018. Our first rule is that the oldest supported PHP version must be officially supported at the time of PrestaShop’s version feature freeze, or if it’s support has ended, it must not have been over a year ago. If the feature freeze is in December 2019, then official support for PHP versions equal or lower to 7.0 would have been over for more than a year, so they don’t conform to this rule.

Support for PHP 7.1 will be over by late 2019, but since it would have been for less than a year counting back from December, it would qualify to become the lower bound — but only as long as our main dependencies support it.

Latest compatible PHP version

PHP 7.4 is due for release in December 2019, probably after PrestaShop 1.7.7 feature freeze date, so it’s possible that not everything will be ready for it.

In that case, the upper bound will be PHP 7.3, which is the most recent PHP version supported by our dependencies.

This would mean that PrestaShop 1.7.7 will most likely be compatible from PHP 7.1 to PHP 7.3.

In conclusion, keeping up with newer PHP versions will not only allow developers to benefit from all the nice new language features, but it will also allow us to use newer, more recent libraries to make PrestaShop better and safer.

Next steps / How can you help

As stated previously, PrestaShop 1.7.7.0 will add support for PHP 7.3. A Pull Request dropping support for older PHP versions has already been created on GitHub.

Here are some things you can do to help:

• Join us on GitHub and Gitter to discuss this project
• Test the development branch of PrestaShop with PHP 7.3 (once the Pull Request above has been merged)
• If you are a module developer, start testing your modules with PHP 7.3
• Help us make sure that our Open Source Modules are working well with PHP 7.3

View the full article

View the full article

Project news

1.7.6 catalog ready for translation

Right on time! As you were told in the previous Crowdin Monthly, the 1.7.6 translation catalog is now available. Pushed on Crowdin last week, it works the same than usual: add comments to spot grammar mistakes, context or if it leads to some confusion so that it could be corrected for the 1.7.6 release!

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 lapakkita140, oaes, slicknux, taniacr, valterlo, and xabilar. See you soon on Crowdin… and PrestaShop. ;-)

A few stats

• 23 members were active on the project this month.
• A total of 13,642 words have been translated and 54,610 validated.
• All this in 21 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 April 2019.

Top 10 translators in April:

Top 10 proofreaders in April:

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 April 2019, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 31 languages:

For its part, PrestaShop 1.7.5 was fully available in 26 languages!

Languages with the best evolution

In comparison with March 2019, the following languages had the best progress thanks to the translation community:

• Albanian (+4% to reach 36% approved in 1.7)
• Serbian (Latin) (+2% to reach 77% approved in 1.7)
• Bengali (+2% to reach 43% 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 April 2019, some languages would still benefit from some proofreading:

• Spanish, Argentina (100% translated vs 0% validated in 1.7).
• Galician (100% vs 62% in 1.7).
• Spanish, Venezuela (53% vs 17% in 1.6).
• Chinese Simplified (100% vs 71% in 1.7).
• Tagalog (52% 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

View the full article

Hi Rodrigo! First, could you tell us a bit about yourself?

I am from Brazil, and I graduated from Unisul University, Santa Catarina with a bachelor’s degree in Computer Science. Since then I have compatibilized external programming work with the work in two own companies, Pacto Visual dedicated to web design and development specialized in Wordpress and PrestaShop. And Cia do Pedal dedicated to cycling products in which I developed the software and modules needed for the virtual store.

When and why did you get involved in contributing to the PrestaShop project? What motivates you?

I got in touch for the first time with PrestaShop in 2009 when I was looking for the best open source alternatives in e-commerce. PrestaShop, of course, was my choice, and I launched my first online shop months later. After that, I developed some PrestaShop modules for my own use and in my web agency, and more recently for sale in PrestaShop Addons. My contributions to the PrestaShop project were initially motivated by the need to have some improvements in the core to allow me to develop better modules, and also for a will to motivate people to use PrestaShop by making it even better.

Do you have any advice for first-time PrestaShop contributors?

If you use PrestaShop in your projects, you will want it to be the best. Contributing to PrestaShop you will help with this. You can make things happen. And PrestaShop has an important and receptive community that will always help you.

What’s the number one thing you’ve learnt by contributing to Open Source projects?

The best thing about a big open source project like PrestaShop is that you are not alone. You learn a lot while contributing, and can always count on great professionals to help you.

Thank you Rodrigo, we hope to see you more from you as PrestaShop evolves! :)

View the full article

General messages

Dear Developers,

In case you missed it, 1.7.6 beta has been released yesterday. It’s time to test it, to test your modules and themes with it, and open a new issue if needed. Also, of course, your help is welcome to fix issues.

Please add the date to your agenda: PSD Paris 2019 will be in a couple of weeks, the 4th of June 2019, at Palais Brongniart, Paris, France. Like each year, this is the opportunity for the PrestaShop ecosystem to meet together and learn what’s new with great talks and speakers.

And, also, this year, there will be a dedicated “developer area”. This will be the place to meet other tech people of the community, including the PrestaShop company developers. Come with your laptop, and let’s fix bugs and merge pull requests together. I will publish a dedicated news on the blog when more information will be available.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 60 new issues have been created in the project repositories;
• 129 issues have been closed, including 17 fixed issues on the core;
• 45 pull requests have been opened in the project repositories;
• 63 pull requests have been closed, including 45 merged pull requests.

Code changes in the ‘develop’ branch

Core

• #13707: Merge 1.7.6.x to develop - 07/05/2019, by @Quetzacoalt91
• #13711: Compare strictly value of hook name when getting modules registered on it, by @Quetzacoalt91
• #13755: Merge 1.7.6.x to develop - 10/05/2019, by @matks

Back office

• #13198: Create SF command to return routes with missing _legacy_link. Thank you @zuk3975
• #13219: ScrollIntoView if field is invalid, by @PierreRambaud

Front office

• #13387: Image in summary not limited. Thank you @YeLnatSs
• #13687: Update OrderReturn.php. Thank you @Codencode
• #13704: Fix exclude discounted products on CartRule, by @tomlev

Tests

• #13018: Only run deploy if the triggered commit is recent, by @PierreRambaud

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #13684: Wrong discount subtotal when customergroup is set to use ex taxes, by @tomlev
• #13735: Update native modules, by @eternoendless

Back office

• #13381: Use tinymce in migrated pages, by @matks
• #13481: Improve preview and test mail feature, improve and fix a few templates, by @jolelievre
• #13522: Fix core exceptions extending and add missing doc-blocks. Thank you @zuk3975
• #13623: Fix categories deleting in bulk action. Thank you @sarjon
• #13643: Fixes incorrect hook names for identifiable object forms.. Thank you @tomas862
• #13714: Seo preview on category & cms pages, by @PierreRambaud

Front office

• #13617: Fix not null voucher with free shipping producing php error, by @tomlev
• #13664: Remove id_attribute parameter from product link when it is equal to 0, by @jolelievre

Tests

• #13630: Fix Onboarding close method, by @boubkerbribri
• #13637: Add handling of the welcome modal and document the blocking issue for the last step, by @SimonGrn
• #13656: Fix for tests in order test suite, by @SimonGrn
• #13657: Fix the check of the success message when saving and deleting a currency. Thank you @nesrineabdmouleh
• #13661: Fix for test 4 of the order test suite after canonical url fix, by @SimonGrn
• #13667: Fix test Feature 1 create edit delete feature, by @boubkerbribri
• #13676: Add close welcome modal for tests Manufacturer, by @boubkerbribri
• #13680: Fix tests customer, by @boubkerbribri
• #13683: Add close welcome module for tests 10_modules, by @boubkerbribri
• #13686: Add close welcome module for tests 11_international, by @boubkerbribri
• #13693: Fix first test of the order test suite, by @SimonGrn
• #13696: Add welcome module for tests discount, by @boubkerbribri
• #13700: Fix test 3 of the shop parameters test suite, by @SimonGrn
• #13739: Fix after merge of PR tinymce, by @boubkerbribri

Install

• #13734: Update translations catalogue for 1.7.6, by @eternoendless
• #13738: Escape strings in installation assistant plus remove unwanted javascript, by @PierreRambaud

Code changes in modules, themes & tools

Auto upgrade

• #306: Handle folder var/cache in module, by @Quetzacoalt91
• #308: Avoid conflit with Psr\Log\LoggerInterface when loading core, by @Quetzacoalt91
• #311: Deploying v4.8.0 of the autoupgrade module, by @Quetzacoalt91

Link list

• #63: Protect autoload and update README and LICENSE, by @jolelievre
• #64: Release 3.0.3, by @eternoendless

Product Comments

• #29: Update version to 4.0.0, by @jolelievre
• #31: Fix release drafter indentation, by @jolelievre
• #32: Fix release drafter indentation, by @jolelievre

Faceted search

• #56: Update License & Readme file, by @PierreRambaud

Changes in Documentation

• #262: All calls to this hook don’t pass the $_POST object.. Thank you @manfield

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @Codencode, @manfield, @nesrineabdmouleh, @sarjon, @tomas862, @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

We are really happy to announce that we are close to releasing 1.7.6.0. This minor version (in the SemVer meaning of the term) brings important new features and improvements to the 1.7 codebase, and we can’t wait to receive your feedback!

This Beta release is a great opportunity for you to start working with it before we release a stable version. Go download and install this Beta version as a test store, either on your machine or your web hosting, then play with it – and give us your feedback! We need YOU to test this new version of PrestaShop.

If you find regressions compared to previous versions, please create an issue on Github to help us to make it stable more quickly.

Remember, this beta version is pre-release software. Do not use it on your production shop!

News & improvements

New features & improvements

• SEO optimization for combination products: all combinations now have the parent product’s URL as their canonical, accessing it no longer issues a redirection, displays the default combination #13009
• A “Price tax included” column has been added to the products list #11484
• A new “modern” template design & wording for transactional emails and a new email template generation system#13004

• Improved Catalog mode: it is now possible to choose to display#11688](https://github.com/PrestaShop/PrestaShop/pull/11688)
• Price & taxes project
  • Bug fixes
  • Front-office improvements: cart price details, add to cart pop up, order confirmation #13047

• New Theme & logo page design
• Improved mobile responsive in the Back-office #13049
• Improved employee profile menu in the Back-office #12707
  • Four new tabs added: Resources, Training, Find an expert and PrestaShop Marketplace
  • New contextual welcome messages
  • An avatar image is now displayed
• More Helpers cards and Empty states added to the BO

• We have fixed many Back-office / Front-office design bugs and made some integration improvements:
  • Fix bug on contact when mail is too long #12893
  • Fix labels display computing #13407
  • Fix label “Web only” #12872
  • Fix quantity placeholder issue in the Stock management page #10199
  • Fix image dimensions in Product Card view #10297
  • Limit carrier image size on checkout page #12892
  • Add modal-dialog-centered class to classic theme #10253

New & improved core modules

• Faceted search: The module has been massively refactored and new features have been added #52
• Customer reviews with rich snippets: new module available for 1.7.6
• Reassurance module: we made a major update of the module
• Image Slider module: fixed #10341

The technical side

Technical improvements

• Support of legacy translations of modules in Translations Manager of BO #11321
• Support for translation in modules’ twig templates
• Nightly builds and nightly board https://nightly.prestashop.com/
• Support of Doctrine for modules and annotated Entities (both Front and Back-office) #12564
• Price computation are now covered by Integration tests powered by Behat (human-readable tests) #12634
• 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
• Performance:
  • Improve employee authorization process
  • Cache introduced when loading modules
• Support of multiple grids on the same page
• New1.7.6_beta_banner_May19.jpg CLDR standard implementation: improved localization of prices and amounts, will allow creating custom currencies in future versions
• Web services:
  • Product customization is now reachable #11938
  • Product combination information in Pack content is now available #12329

Notable fixes

• Fixed minimum order in the second currency #9665
• Dni field is required if the associated country needs it #9891
• Calculate carrier price on the real order price #9540
• Cart rules not applied if the cart contains only virtual products #10264
• Hook reseted during upgrade #11873
• Catalog mode correctly hides prices and cart, a new option allows displaying prices while disabling orders #11688
• Enhanced security checks for virtual goods #12023
• The number of SQL requests to get the employee authorizations has been significantly reduced #12914
• Checkout doesn’t proceed automatically from carrier selection to payment selection #12456

The complete list of bugs fixed for 1.7.6.0 is available on Github.

Hooks

New hooks

• displayProductActions (Product page, close to the “Add to cart” button, #13103)
• displayPersonalInformationTop (Checkout funnel, before the customer login form, #13103)
• additionalCustomerAddressFields (In CustomerAddressFormatter, #9132)
• actionProductFlagsModifier (Allows to customize product flags, #11614)
• Form hooks
• Kpi hooks #12706
• Mail generator hooks (will be defined with Doc as well)
  • actionListMailThemes
  • actionGetMailThemeFolder
  • actionBuildLayoutVariables
  • actionGetMailLayoutTransformations

Improved hooks

• actionProductAdd now receives id_product_old when duplicating a product

Symfony Migration - new pages

• Catalog > Categories
• Catalog > Categories > Add new / edit category
• Catalog > Brand & Suppliers > Brands > Add new brand
• Catalog > Brand & Suppliers > Suppliers (will be hidden)
• Catalog > Brand & Suppliers > Brands
• Catalog > Brand & Suppliers > Brands > Add new brand address
• Catalog > Brand & Suppliers > Brands > View brand
• International > Localization > Currencies
• International > Localization > Currencies > Add new / edit currency
• International > Localization > Languages
• International > Localization > Languages > Add new / edit language
• International > Taxes > Taxes
• International > Taxes > Taxes > Add new / edit tax
• Design > Theme & Logo
• Design > Theme & Logo > Add new theme
• Design > Theme & Logo > Choose layouts
• Design > Pages
• Design > Pages > Add new / edit page
• Design > Pages > Add new / edit page category
• Advanced Parameters > Team > Employees
• Advanced Parameters > Team > Employees > Profiles
• Advanced Parameters > Team > Employees > Profiles > Add new profile
• Advanced Parameters > Team > Employees > Add new employee
• Advanced Parameters > Webservice > Add new webservice key
• Shop parameters >Traffic & SEO > SEO & URL > Add new / edit page
• Shop parameters > Contact > Contacts
• Shop parameters > Contact > Contacts > Add new / edit contact
• Customers > Customers
• Customers > Customers > Add new / edit customer
• Customers > Customers > View customer

Breaking or risky changes

• The new CLDR implementation replaces the old one #12999. 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. #10930)
• Replaced library:
  • PhpExcel (no longer supported) has been replaced by PHPSpreadsheet #11246)
• Version comparison #12251:
  • 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 #12708):
  • 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 #11962
  • src/Core/Addon/Module/ModuleManager.php::_construct() receives an instance of CacheClearerInterface instead of CacheClearer #12022
  • 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() #12716
  • Error messages are no longer html escaped #12788

Known Issues

Incomplete Improvements

• Better alert for customer creation and customer info edit forms #13640

Issues

• Some native modules wordings do not have domain #13476
• Bulk action & the Select all doesn’t work in the SQL manager page #13620
• BO - We can create a new customer successfully without setting required field “Partner offers” #13556
• ToggleColumn option name changed between 1.7.5 and 1.7.6 #13544
• Catalog > Monitoring > Empty categories list status toggling action not working #13541
• Message with gift wrapping option in order not display in back office #13478
• Strange behavior when we are moving the mouse under the “Status” label #12068
• Private comment in Order #13428
• New theme & logo page - Design fixes #13467
• Old admincustomer URL in notifications #13450
• Discount line not always removed during checkout #12969
• Vertically align the pagination system components #12392
• Help isn’t displayed on add customer page #13449
• An exception is displayed when we try to upload in the logo section with an image which has a not recognized format #13729
• Tax excl column in catalog page doesn’t take into account specific prices #13731

Download

You can download PrestaShop 1.7.6 beta here:  

Download PrestaShop 1.7.6 beta 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 it
• 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, comment this article to tell us, and share on social networks, we also need this feedback.

View the full article

View the full article

View the full article

General messages

Dear Developers,

The team is currently working on a Beta release. If you are interested to follow the work on the 1.7.6, below are three interesting links on GitHub:

• The 1.7.6 roadmap, this is a dedicated kanban used for the release’s project management
• The 1.7.6.0 milestone, where you can see what is currently open, and the work already closed (more than 800 items to date)
• You can also filter by type: issues (208 closed + open to date) or pull requests (635 closed + open to date)

If you want to compare, below are the equivalent links for two previous releases:

• 1.7.5.0 milestone, with 596 items, including 146 issues and 450 pull requests
• 1.7.4.0 milestone, with 260 pull requests; issues were still managed on the old forge at this time, that explains why there are no figures for issues.

So, now, you know how to check that PrestaShop 1.7.6.0 will be a huge release!

And that doesn’t include the work carried out for the modules: this is only for the core. You can find some inspiration from the links in the next section of this core weekly to track the work done on the entire project.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 42 new issues have been created in the project repositories;
• 42 issues have been closed, including 14 fixed issues on the core;
• 75 pull requests have been opened in the project repositories;
• 69 pull requests have been closed, including 62 merged pull requests.

Code changes in the ‘develop’ branch (for 1.7.7.0)

Core

• #13384: Adds naming convention linter. Thank you @sarjon
• #13595: Merge 1.7.6.x to develop - 29/04/2019, by @matks
• #13606: Fix phpdoc on Module class, by @Matt75
• #13621: Merge 1.7.6.x to develop - 30/04/2019, by @matks
• #13666: Merge 1.7.6.x to develop - 03/05/2019, by @matks

Back office

• #13571: Enable grid search button by default. Thank you @zuk3975

Tests

• #13495: Add behat tests for customer Commands and Queries (part 1), by @matks

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #13578: Automatically add dni field in Address format for countries which need it, by @jolelievre
• #13604: Forbid URLS to be added in customer names, by @PierreRambaud
• #13605: Add missing translation domains, by @matks
• #13609: Fixed dispatched hook on the Grid presenter, by @mickaelandrieu

Back office

• #13372: Add missing security annotations. Thank you @rokaszygmantas
• #13504: Fix backoffice translations for third-party modules, by @eternoendless
• #13563: Do not get data from null currency, by @Quetzacoalt91
• #13576: Fix deleting profile . Thank you @sarjon
• #13603: Add id for orders view page to ease E2E testing, by @matks

Front office

• #13407: Fix labels display computing, by @jolelievre
• #13440: Change checkout behaviour, by @jolelievre
• #13635: Fix product link should not include attribute parameter equals to zero, by @jolelievre

Tests

• #13502: Fix test Category suite full, by @boubkerbribri
• #13545: Fix test Employee Suite Full, by @boubkerbribri
• #13570: Fix broken selectors and logic for the test suite 9 (customer), by @SimonGrn
• #13588: Fixing some tests order, by @boubkerbribri
• #13597: Fix test 09_delivery_slips_pdf_and_options, by @boubkerbribri
• #13602: Fix for test 2 of the orders test suite, by @SimonGrn
• #13612: Fix test 05 create order without account, by @boubkerbribri
• #13615: Fix test Product suite full. Thank you @nesrineabdmouleh
• #13616: fix method to change quantity, by @SimonGrn
• #13651: Adding close welcome module in tests product, by @boubkerbribri
• #13659: Adding close welcome module in tests Attribute, by @boubkerbribri

Install

• #13471: Set null values when trying to retrieve the non-existing default shop, by @Quetzacoalt91

Code changes in the ‘1.7.5.x’ branch (for 1.7.5.2)

Core

• #13580: Fixed dispatched hook on the Grid presenter, by @mickaelandrieu
• #13599: Forbid URLS to be added in customer names, by @PierreRambaud

Tests

• #13583: Fix selector in E2E tests for addons catalog page and another one in the autoupgrade test. Thank you @nesrineabdmouleh

Code changes in the ‘1.6.1.x’ branch (for 1.6.1.24)

Core

• #13607: Forbid URLs to be inserted into Name fields, by @PierreRambaud

Code changes in modules, themes & tools

Auto upgrade

• #279: Apply fixes from phpstan reviews, by @Quetzacoalt91
• #300: Improve report of errors and fix notices, by @Quetzacoalt91
• #302: Display error when access is not granted, by @Quetzacoalt91
• #303: Enable php-cs-fixer on the project, by @Quetzacoalt91
• #305: Add Rollback explanation in readme, by @Quetzacoalt91
• #307: Improve configuration getter for image backup, by @Quetzacoalt91

Legal compliance

• #64: Unary operator spaces. Thank you @MathiasReker

OnBoarding

• #56: Fix theme & logo, by @PierreRambaud
• #57: Update module version, README and LICENSE, by @jolelievre
• #58: Version updated to v6.0.0, by @jolelievre

Improvements of readme and license files in modules repositories

• Banner #13: Update Readme & License, by @Quetzacoalt91
• Banner #14: Update Readme & License, by @eternoendless
• Check payment #23: Update Readme & License, by @Quetzacoalt91
• Check payment #24: Update Readme & License, by @eternoendless
• Wire payment #42: Update Readme & License, by @Quetzacoalt91
• Wire payment #43: Update Readme & License, by @eternoendless
• Category tree links #27: Update Readme & License, by @Quetzacoalt91
• Category tree links #28: Update Readme & License, by @eternoendless
• Product Comments #27: Update Readme, by @eternoendless
• Product Comments #28: Add Readme and License, by @eternoendless

Product Comments

• #26: New 4.0.0 version compatible with PrestaShop 1.7.6+, by @jolelievre

Emails SDK

• #12: Revert check vars. Thank you @Scritik

Docker

• #162: Add PrestaShop 1.7.5.2 & 1.6.1.24 , by @Quetzacoalt91

Changes in Documentation

• #250: Added docs for Kpi rows improvements, by @mickaelandrieu
• #260: Goodpratices, Technical Tools and New Technical Keys Steps. Thank you @Shiryu75
• #263: Add BO credentials in docker page, by @Quetzacoalt91
• #266: Core style theme.css priority should be 50 not 0. Thank you @rateforx

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @MathiasReker, @nesrineabdmoule, @rateforx, @rokaszygmantas, @sarjon, @Scritik, @Shiryu75, @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

View the full article

General messages

Dear Developers,

That was amazing to see the huge mobilization to find workarounds in a hurry, during the weekend, to fix the spam issue with the account creation form.

You will see in this core-weekly the pull requests that fix this issue. And, in case your missed it, two versions of PrestaShop have been released this morning: 1.6.1.24 and 1.7.5.2.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 43 new issues have been created in the project repositories;
• 49 issues have been closed, including 14 fixed issues on the core;
• 55 pull requests have been opened in the project repositories;
• 50 pull requests have been closed, including 36 merged pull requests.

Code changes in the ‘develop’ branch (for 1.7.7.0)

Core

• #13482: Merge 1.7.6.x to develop - 18/04/2019, by @matks
• #13542: Merge 1.7.6.x to develop - 23/04/2019, by @matks
• #13557: Merge 1.7.6.x to develop - 25/04/2019, by @matks

Back office

• #13152: Updates characters length for Category meta fields. Thank you @sarjon
• #13233: Enable ‘back’ GET parameter management. Thank you @tomas862
• #13454: Fix on product redirect in SEO tabs . Thank you @YeLnatSs
• #13472: Create SF command to list tactician commands and queries. Thank you @zuk3975
• #13572: Add FiltersSubmitButtonEnablerExtension to profiles page. Thank you @zuk3975

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #13540: Update upgrade scripts to PS 1.7.6.0, by @Quetzacoalt91
• #13560: Remove duplicate method call, by @eternoendless

Back office

• #13484: Fixes Categories grid filtering by position. Thank you @sarjon
• #13508: Enable ChoiceTree javascript in manufacturers form . Thank you @zuk3975
• #13528: Fix calendar overflow. Thank you @zuk3975
• #13535: Fix responsive showcase cards . Thank you @YeLnatSs
• #13547: Deprecate Language::installEmailsLanguagePack, by @jolelievre
• #13550: Add missing check in Manufacturer image uploader. Thank you @zuk3975

#Front office

• #13411: Hide tax label in front when tax display is disabled in the shop, by @jolelievre
• #13525: fix currency display on not existing language, by @tomlev

Tests

• #13503: FIx test Create Attribute Suite Full. Thank you @boubkerbribri
• #13534: Fix tests manufacturer. Thank you @boubkerbribri
• #13536: Fixes e2e broken selectors, by @mbadrani
• #13552: Fix tests International/localization and international/taxes. Thank you @boubkerbribri
• #13561: fix for tests 1 and 2 of the shop_parameters test suite, by @SimonGrn
• #13568: Fix tests 10_module Suite Full. Thank you @boubkerbribri
• #13581: fix test feature update. Thank you @ntiepresta

Code changes in the ‘1.7.5.x’ branch (for 1.7.5.2)

Core

• #13549: Forbid URLs to be inserted into Name fields, by @matks
• #13567: Improve name validation, by @eternoendless

Code changes in the ‘1.6.1.x’ branch (for 1.6.1.24)

Core

• #13559: Forbid URLs to be inserted into Name fields, by @matks
• #13574: Improve name validation, by @eternoendless
• #13581: fix test feature update. Thank you @ntiepresta

Code changes in modules, themes & tools

Auto upgrade

• #299: Init Kernel on UpgradeDB when upgrading to 1.7, by @Quetzacoalt91

UI kit

• #64: asset path in README.md, by @david-piatek

Classic Rocket

• #47: Update microdata-jsonld.tpl. Thank you @bhavikvaghani
• #48: Smarty Replace Warning. Thank you @bhavikvaghani

Preston Bot

• #80: Disable Classic Theme listener to stop assigning StarterTheme label, by @matks

Changes in Documentation

• #257: Document DTOs. Thank you @sarjon
• #259: Improve PHP compatibility chart, by @eternoendless

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @bhavikvaghani, @boubkerbribri, @ntiepresta, @sarjon, @tomas862, @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

These two security updates address a validation issue on the customer registration form, which is currently being exploited by spammers who were entering URLs as customer name.

This update mitigates the problem by preventing attackers to use URLs as names. However, as we discussed before, the best protection against this kind of attack still is to add a CAPTCHA module on your shop. You can find them on the Addons marketplace.

Important note

Once this update has been applied, customers won’t be able to register if their name contains a dot followed by a letter. For example, “John R.Hammond” won’t work, but “John R. Hammond” will.

There may already be customers on your shop with names like that. If that’s the case, next time they update their personal information, the form will require that they update their names manually either by removing dots, adding a space after any dot, or replacing all dots by spaces.

Additional information

Changes for 1.7.5.2:

• Core:
  • Bug fix:
    • #13599: Forbid URLs to be added in customer names
    • #13580: Fixed dispatched hook on the Grid presenter

Changes for 1.6.1.24:

• Core:
  • Bug fix:
    • #13607: Forbid URLs to be inserted into Name fields
    • #10859: Fixed keywords disappear from search index

Download PrestaShop now!

Contributors to this patch versions, from both the Core team and the community at large: Casper Olsen, Geoffray Warnants, Mathieu Ferment, Mickaël Andrieu, Nesrine Abdmouleh, Pablo Borowicz, Pierre Rambaud and Thomas N. Thank you!

A very special thank you to @doekia and @okom3pom who were really helpful regarding the best approach for this major issue.

Since version 1.7.5.2 is a “patch” update to version 1.7.5.1, upgrading from any 1.7.5 version will be easy: features will work better, and modules & themes which worked fine on 1.7.5.2 will work just as well with 1.7.5.1. Upgrades from a standard 1.7.x version should work just as well.

This the same for 1.6.1.24 regarding 1.6.1.x versions.

View the full article

View the full article

UX Challenge

Starting from this statement, one of the challenges PrestaShop has to address is consistency: with the variety of developers and modules comes the need to harmonise the interfaces in order to give our merchants the most fluid and consistent PrestaShop experience.

There are two things to take into account when it comes to harmonising interfaces: you may be familiar with the notion of UI (User interface) and UX (User experience). As a reminder, UI is the visual part of the interface: colors, buttons’ shapes, typography, spacing… On another hand, UX defines how the interface is meant to be used: architecture, navigation, wordings, interactions and many other aspects that reflect the ergonomy, usability and efficiency of the interface.

The UX guide

The goal of this document is to start establishing a certain pattern in the way merchants use their modules, so they don’t have to learn anew every time they get a new one. If merchants can get familiar with this pattern, it will result in a better clarity of the overall diversity of modules interfaces. The designer team and I wrote this document based on a representative sample of different modules from the marketplace, and a list of UX best practices that were the most relevant regarding our problematic.

This document is a first step in our ambition to provide more resources and help our community to develop easier and better.

We wish you a good reading, don’t hesitate to give us your feedback ;)

Download the UX guide in PDF

More

If you are interested to know more about UX and UI best practices, below are other interesting resources on the topic:

• Top 100 UX Design Tips from a User Experience Master
• The UX Design Checklist
• 10 Rules of Good UI Design to Follow On Every Web Design Project

View the full article

General messages

Dear Developers,

It seems that the progress on the 1.7.6 is going well. For the first time with the PrestaShop open source project, this is possible to test it with the [nightly builds], a lot of feedback is collected this way. So, there is no need to spend too much time on an Alpha release. In fact, this will give more time to the team to finish the upcoming 1.6.1.24 and 1.7.5.2 releases.

More news about the 1.7.6 in the next core-weekly.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 68 new issues have been created in the project repositories;
• 53 issues have been closed, including 24 fixed issues on the core;
• 65 pull requests have been opened in the project repositories;
• 55 pull requests have been closed, including 40 merged pull requests.

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #13353: Fixes default Customer group overriding. Thank you @sarjon
• #13402: Add new hooks of 1.7.6.0 in fixtures, by @Quetzacoalt91
• #13409: Do not call removed cldr lib, by @Quetzacoalt91
• #13430: Merge 1.7.6.x to develop - 16/04/2019, by @matks
• #13435: Fixes option for MaterialMultipleChoiceTableType. Thank you @sarjon
• #13461: Merge 1.7.6.x in develop, by @Quetzacoalt91
• #13470: Removes GetDefaultGroupHandler adapter . Thank you @sarjon

Back office

• #13351: Mail generator fixes, by @jolelievre
• #13367: Remove deactivated currencies from new CLDR, by @tomlev
• #13404: missing showcase card in cms page implementation. Thank you @tomas862
• #13429: Build outdated assets for 1.7.6.x, by @matks
• #13431: Fix parameters list in product lookup, by @Quetzacoalt91
• #13434: Remove material icons on SQL manager page, by @marionf
• #13439: Improvements on LegacyUrlConverter, “tab” alias, insensitive and prevent infinite redirection loop, by @jolelievre
• #13466: Brand and address export actions. Thank you @zuk3975
• #13477: Fix issue on order with free gift, by @tomlev

#Front office

• #13003: free shipping behat tests, by @tomlev
• #13261: Fix lang on currency install, by @tomlev

Tests

• #13464: Apply CS Fixer on 1.7.6.x, by @Quetzacoalt91

Code changes in the ‘develop’ branch (for 1.7.7.0)

Core

• #13189: Harmonize Grids naming. Thank you @sarjon
• #13236: Adds ajax support for @AdminSecurity annotation. Thank you @sarjon
• #13486: Fix coding style on develop, by @matks

Back office

• #13234: Add Showcase card in Categories page. Thank you @sarjon
• #13425: Border inside tabs when counter is empty. Thank you @YeLnatSs

Code changes in modules, themes & tools

Auto upgrade

• #297: Bump version to v4.7.0, by @Quetzacoalt91

Preston Bot

• #82: Fix tests and Travis pipeline, by @matks

Faceted search

• #52: Huge Refactoring, by @PierreRambaud
• #54: Enable Release Drafter, by @Quetzacoalt91
• #55: Add PHP checks on Travis, by @Quetzacoalt91

Translation tools

• #58: Add option to SmartyExtractor to allow it to include external module translations, by @eternoendless
• #59: Infer module domain for old legacy modules, by @eternoendless

Theme customization

• #12: Merge dev to master for 1.0.10, by @jolelievre

Changes in Documentation

• #232: Document CQRS. Thank you @sarjon
• #243: Documents Empty state feature of Grid. Thank you @sarjon
• #244: Documents Bulk actions for Grid component. Thank you @sarjon
• #245: Reusable custom Form Types reference. Thank you @zuk3975
• #252: Add hooks implemented in 1.7.6.0, by @Quetzacoalt91
• #253: Corrected a typo in head.md. Thank you @JePoste
• #254: Change many “http://” links by “https://”. Thank you @yannicka
• #255: Document domain exceptions. Thank you @rokaszygmantas

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @JePoste, @rokaszygmantas, @sarjon, @tomas862, @yannicka, @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

View the full article

View the full article

A lot of PrestaShop users approached us these past few days because they were experiencing spam issues. Indeed, a stream of spammers is currently exploiting PrestaShop in order to flood people under a mass of undesired emails, generated by the creation of fake new customer accounts.

Before getting more into details on how this spamming works and what to do to prevent it, we would like to say a big thank you to our community, especially on PrestaShop forum, who has been really active and helpful on this issue.

How are those spammers spamming?

All versions might be concerned, the spamming method affects all merchants the same way: spammers are exploiting the account creation forms, available on shop front-offices by replacing the first and/or last names with a malicious website URL. Here is how customer accounts look like on affected shops’ back offices:

Screenshots taken from the PrestaShop forum, thanks to those who shared them!

It has 2 major impacts :

• Merchants are flooded with undesired emails (caused by account creation notifications), therefore it might not only negatively impact their shop’s performance but also make merchants be flagged as spammers by some email domains and block them for future email sendings.

• When real email addresses are used, it sends a confirmation email to a real user including the spammer’s URL in it. We think it can be used for fake advertisement, or phishing if users click on this link.

What to do to prevent those spammers from spamming?

Well, the solution is the same for both 1.6 and 1.7 versions.

Because this attack is caused by massive account creations containing untrustworthy links, we took the decision to prevent people from writing anything that looks like a URL within the customer account creation form. And therefore it will be impossible to create a customer with an URL as the first name and/or the last name.

A patch is thus going to be released for versions 1.7.5.x and 1.6.1.x in order to mitigate the attack vector. Shops based on 1.6 will be able to retrieve this patch in the next 1.6.1.24 release - PR to come. As for PrestaShop 1.7, it will be included in the forthcoming 1.7.5.2 version. Have a look at the pull request here while waiting for the releases to upgrade your store.

What to do next?

We suggest deleting all fake accounts in your back office. Here are three steps to follow before their deletion, just to make sure you won’t be bothered again:

• remove spam accounts from your mailing lists
• go in the Customers page of your back office and select all these accounts
• finally, click on delete and check the option “I want my customers to be able to register again with the same email address. All data will be removed from the database.”

We strongly encourage all 1.6 and 1.7 merchants to upgrade to the latest version (1.7.5.2 and 1.6.1.24) as soon as it is released to benefit from this patch and prevent this kind of spam in the future.

We also recommend merchants to get a CAPTCHA solution to be able to fully protect your forms from spammers. See below for further information.

About CAPTCHAs

CAPTCHA stands for Completely Automated Public Turing test to tell Computers and Humans Apart, we are pretty sure you all already know about it. It is a great solution to protect your shop from robot attacks and, obviously, it was the first thing we thought about.

But it turns out it is also a tool that can be complicated to install and set up. Indeed, it either requires the merchant to configure third-party services or install PHP libraries that are not always available or easy to activate in the server.

For this reason, we choose to to leave you the choice to get a CAPTCHA for your store or not. Because it implies some configurations that not everybody will feel like doing it. You can find modules for that on our Addons marketplace.

We are aware that this kind of unfortunate situation can affect your business and for that we make a point of guaranteeing the security of all the PrestaShop stores. We are deeply involved in solving this issue as it is our number one priority today. Be sure that it will soon be fixed!

View the full article

General messages

Dear Developers,

The tests and debug phase of the 1.7.6 release has started: 134 issues have been created on the week after the code freeze. Some developers are already testing it on their infrastructure, opening issues, and submitting pull requests, and that is AWESOME!!!

Please continue like that, thank you very much for your feedback.

Oh, and this week, I went to the first edition of the PSconnect event in Lyon, France, with a few people of the PrestaShop company: business managers, product managers, our CEO and our CTO. That was a very interesting moment to discuss and collect feedback about the roadmap. Merchants, partners, agencies and freelancers confirmed that the project’s roadmap is on good tracks. There was also a very good feedback about 1.7.5, with many projects in production and scheduled migrations.

Find the next PrestaShop event in your area: https://www.prestashop.com/en/events

A quick update about PrestaShop’s GitHub issues and pull requests:

• 134 new issues have been created in the project repositories;
• 63 issues have been closed, including 12 fixed issues on the core;
• 74 pull requests have been opened in the project repositories;
• 46 pull requests have been closed, including 43 merged pull requests.

Code changes in the “1.7.6.x” branch (for v1.7.6.0)

Core

• #13246: Add missing hook description, by @eternoendless
• #13256: Fixes to Customer subdomain & controller. Thank you @sarjon

Back office

• #13144: Cms page fixes. Thank you @zuk3975
• #13251: Removes unnecessary return on update everywhere. Thank you @tomas862
• #13264: Restores deleted generatable_text_widget from template. Thank you @sarjon
• #13273: Fix domain errors, by @matks
• #13349: Make all grids responsive, by @eternoendless
• #13363: Fix syntax error in tpl, by @Quetzacoalt91

Tests

• #13356: Adds unit tests for FormHandlerFactory. Thank you @sarjon

Install

• #13223: Fix SQL syntax error in upgrade file to PS 1.7.6, by @Quetzacoalt91

Code changes in the ‘develop’ branch

Core

• #13119: Allow hookAdditionalCustomerFormFields and –AddressFormFields to modify fields positions. Thank you @rblaurin
• #13200: Add SecurityAnnotation linter. Thank you @sarjon
• #13222: Do not try to install an unsupported language, by @PierreRambaud
• #13232: [CO] Wrong calculation, free Gift. Thank you @123monsite-regis
• #13235: Update src folder license headers, by @matks
• #13237: Update tests folders license headers, by @matks
• #13238: Update themes folders license headers, by @matks
• #13239: Update js folder license headers, by @matks
• #13242: Add missing hook description for additionalCustomerAddressFields, by @eternoendless
• #13266: Merge 1.7.6.x to develop - 10/04/2019, by @matks
• #13359: Merge 1.7.6.x to develop - 11/04/2019, by @matks
• #13375: Merge 1.7.6.x to develop - 12/04/2019, by @matks

Back office

• #13162: Tax page fixes. Thank you @zuk3975
• #13221: Allow trans() to fall back on the legacy translation system when used with modules, by @eternoendless
• #13241: Grid extension to disable filters submit button when filters are empty. Thank you @zuk3975

Front office

• #13047: New design for prices and taxes. Thank you @YeLnatSs
• #13201: Fix search results if shop has non-default ‘visitor’ group and categories that are only accessible for the non-default visitor group. Thank you @fgschaefer
• #13218: Fix breadcrumb in search results page leads to 404 page, by @PierreRambaud

Code changes in modules, themes & tools

Auto upgrade

• #295: Add configuration file needed for Release Drafter, by @Quetzacoalt91
• #296: Deploying v4.7.0 of the autoupgrade module, by @Quetzacoalt91

Gamification

• #64: Various improvements, by @eternoendless

Theme customisation

• #8: Correcting button on responsive by adding a new css rule, by @apacios
• #11: Bump version 1.0.10, by @jolelievre

Docker

• #160: Make sure nightly images are built from PrestaShop develop branch, by @Quetzacoalt91

Amazon payments

• #84: v2.2.8. Thank you @paeddl
• #85: v3.2.7. Thank you @paeddl

Changes in Documentation

• #184: adds Identifiable object Forms documentation. Thank you @tomas862
• #239: Add deprecation notice about PS 1.7.6, by @Quetzacoalt91
• #240: How to extend grid with Javascript extensions. Thank you @zuk3975
• #242: Add “Insomnia” to test REST API. Thank you @yannicka
• #246: Fixed grammar and other small changes. Thank you @NathanGiesbrecht
• #247: Missing dollar sign, by @PierreRambaud
• #251: Update _index.md. Thank you @budhead

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @123monsite-regis, @budhead, @paeddl, @rblaurin, @sarjon, @tomas862, @yannick, @YeLnatS, @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

View the full article

View the full article

Project news

String freeze is comin’

… aaaaannnd PrestaShop 1.7.6 has entered code freeze, we are glad to inform you about this huge step we have just achieved! It means that string freeze is due as well, you can expect the new catalog to be pushed on Crowdin this week. Once this new translation branch created, it will be time for us to translate, correct and validate all fresh strings in order to get the most complete version for the 1.7.6 official release, planned for June. Let’s all make PrestaShop go in the right way… ready, set, go!

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 Guisardo. See you soon on Crowdin… and PrestaShop. ;-)

A few stats

• 13 members were active on the project this month.
• A total of 213,652 words have been translated and 7,802 validated.
• All this in 14 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 March 2019.

Top 10 translators in March:

Top 9 proofreaders in March:

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 March 2019, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 31 languages:

For its part, PrestaShop 1.7.5 was fully available in 25 languages!

Languages with the best evolution

In comparison with February 2019, the following languages had the best progress thanks to the translation community:

• Spanish, Argentina (+75% to reach 99% translated in 1.7)
• Korean (+3% to reach 98% approved in 1.7)
• Hebrew (+1% to reach 74% 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 March 2019, some languages would still benefit from some proofreading:

• Spanish, Argentina (99% translated vs 16% validated in 1.6).
• Galician (100% vs 62% in 1.7).
• Spanish, Venezuela (53% vs 17% in 1.6).
• Chinese Simplified (100% vs 71% in 1.7).
• Tagalog (52% 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

General messages

Dear Developers,

The code is frozen!!! 🍾️ 🎉️ ☃️

A quick look at the work done on 1.7.6:

• 120 issues have been fixed
• 521 pull requests have been merged

What a huge amount of work!

If you can’t wait for an Alpha build, don’t forget that you can use the nightly builds. And of course, test it with your infrastructure, your modules and themes, your data, your configuration. And then, please, let us know if you find something to fix: open an issue on GitHub.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 68 new issues have been created in the project repositories;
• 65 issues have been closed, including 16 fixed issues on the core;
• 42 pull requests have been opened in the project repositories;
• 58 pull requests have been closed, including 49 merged pull requests.

Code changes in the ‘develop’ branch (for v1.7.6.0)

Core

• #12708: Deprecate admin endpoints outside index.php, by @Quetzacoalt91
• #12926: Migration of Manufacturers view action. Thank you @sarjon
• #12941: Remove unnecessary return on update, by @eternoendless
• #12996: Domain improvements: naming and namespace. Thank you @sarjon
• #12999: Remove calls to old CLDR, by @Quetzacoalt91
• #13115: Fix strpos arguments order. Thank you @quasilyte
• #13141: Performance : avoid useless attributes queries. Thank you @123monsite-regis
• #13146: Fixes missing fields validation in Language command handlers. Thank you @sarjon
• #13208: Broken page when request a duplicate _legacy_link, by @PierreRambaud
• #13209: Properly set error headers, by @jocel1

Back office

• #12331: Migration of Theme & Logo page with style and ux improvements. Thank you @tomas862
• #12436: Introduces new File type input design for all new and migrated back-office pages . Thank you @tomas862
• #12707: New design for employee profile [Back-Office]. Thank you @YeLnatSs
• #12795: Brand address create/edit actions migration. Thank you @zuk3975
• #12931: Make footer on product page spreads itself when the menu is hidden. Thank you @dineshbadrukhiya
• #12974: Cms page category listing position update. Thank you @tomas862
• #12995: Migrate Cms page create/edit actions. Thank you @zuk3975
• #13033: Filter registered hooks in module possible hooks list. Thank you @unlocomqx
• #13048: Integrate mail generator, by @jolelievre
• #13088: Ensure translations are always saved with the selected theme in back office, by @mickaelandrieu
• #13093: Add missing label and delete legacy tax controller as it was migrated. Thank you @rokaszygmantas
• #13105: Validate theme zip file and show error messages. Thank you @rokaszygmantas
• #13108: Fix missing lang entries in Configuration. Thank you @rblaurin
• #13122: Fix notice when iso code does not exist in array, by @Quetzacoalt91
• #13123: Display shop path in Information page. Thank you @unlocomqx
• #13125: Add CMS page listing position update functionality. Thank you @tomas862
• #13145: fixes bug with incorrect errors display within the forms. . Thank you @tomas862
• #13157: Fix Add/Edit brand icon, by @matks
• #13158: Sets error bubbling inside the translatable type. Thank you @tomas862
• #13159: Remove ‘Constraint’ suffix from TypedRegex constraint and validator. Thank you @zuk3975
• #13161: Remove icons from Customers form. Thank you @sarjon
• #13164: Manufacturer page fixes. Thank you @zuk3975
• #13177: Fix notice undefined index: icon on Design -> Positions, by @Matt75
• #13199: Fix Profiles form twig template compatibility with twig v2, by @matks
• #13216: Enable help bar on suppliers page, by @PierreRambaud

Front office

• #12872: Fix label “Web only” . Thank you @YeLnatSs
• #13103: Introduce new hooks displayProductActions & displayPersonalInformationTop, by @Quetzacoalt91
• #13106: Checkout proceeds automatically go to latest step, by @PierreRambaud
• #13135: Add variable to tell if prices are tax included or not, by @eternoendless
• #13150: Add a missing space that could trigger an SQL error. Thank you @chrisvanberg
• #13171: Outdated assets, by @PierreRambaud

Tests

• #13127: Do not run tests with the StarterTheme anymore, by @Quetzacoalt91
• #13167: Move lint checks in GitHub action, by @Quetzacoalt91
• #13176: Allow to use date as parameter for nightly builds, by @PierreRambaud

Code changes in modules, themes & tools

Starter theme

• #240: Add deprecation notice in Readme, by @Quetzacoalt91

Legal Compliance

• #45: Fixed undefined array index declaration, by @mickaelandrieu

NVD3 Charts

• #6: Deploy v2.0.1 of the graphnvd3 module, by @Quetzacoalt91

Changes in Documentation

• #236: Fix paths of files and fold. Thank you @cr998
• #237: Docs for custom product flags. Thank you @kpodemski

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @123monsite-regis, @chrisvanberg, @cr998, @dineshbadrukhiya, @kpodemski, @quasilyte, @rblaurin, @sarjo, @tomas862, @unlocomqx!

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

View the full article

General messages

Dear Developers,

Code freeze has been postponed to this week because some critical work needed to be finished for the 1.7.6. Stay tuned for an announcement that will provide more information about a possible Alpha release.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 58 new issues have been created in the project repositories;
• 60 issues have been closed, including 21 fixed issues on the core;
• 57 pull requests have been opened in the project repositories;
• 65 pull requests have been closed, including 55 merged pull requests.

Code changes in the ‘develop’ branch (for v1.7.6.0)

Core

• #11321: Translation Manager of Back Office can now manage legacy translations of modules, by @mickaelandrieu
• #11730: Use of static instead of ClassName. Thank you @MathiasReker
• #11970: Unary operator spaces. Thank you @MathiasReker
• #11975: Space after semicolon. Thank you @MathiasReker
• #11977: Function declaration. Thank you @MathiasReker
• #12550: Improve the way VAT is managed for price calculation. Thank you @prestamodule
• #12967: Foward $locale to Translate::getModuleTranslation(), by @eternoendless
• #13008: Adds phpdoc on range objectmodel, by @Matt75
• #13035: Merge 1.7.5.x in develop, by @PierreRambaud
• #13057: Fixes search action configuration for grids. Thank you @sarjon

Back office

• #12214: Migrate “Advanced Parameters > Team > Employees > Add new employee” page. Thank you @rokaszygmantas
• #12523: Solved problem with texture upload when attribute has hex color. Thank you @kpodemski
• #12735: Brands create/edit migration. Thank you @zuk3975
• #12850: [BO] 11692 “Module Manager” tab should be the first tab in Modules Tab. Thank you @rblaurin
• #12914: Reduce number of SQL requests to get the employee authorizations, by @Quetzacoalt91
• #12928: Manage multi grids on same page, by @jolelievre
• #12981: Migration of “Design -> pages -> cms page listing” . Thank you @tomas862
• #13004: Integrate new modern theme (compiled from MJML), by @jolelievre
• #13012: Update Twig to v1.38, by @matks
• #13014: Final Migration of Categories page. Thank you @sarjon
• #13043: Fix to handle fancybox customer creation in Add an Order page, by @matks
• #13049: Fix BO scaling in mobile, by @eternoendless
• #13054: Escape all import output data, by @PierreRambaud
• #13063: Module Manager: Use categoryParentEnglishName instead category name, by @PierreRambaud
• #13066: Fix npm install not working anymore on new-theme, by @PierreRambaud
• #13067: Fix manufacturers ns typo’s and wrong typecasts in commands. Thank you @zuk3975
• #13076: Migrate Add/Edit Profiles page. Thank you @sarjon
• #13079: Fix visual glitches in new theme, by @eternoendless
• #13094: Fix product demo link_rewrite, by @marionf
• #13095: Update dashboard links, by @eternoendless
• #13104: Fix bad variable in Customers Add/Edit template, by @matks

Front office

• #11688: Manage catalog mode in list and products page, by @jolelievre
• #12391: 12040 broken authentication. Thank you @arnaudschaeffer
• #12892: limit carrier image size on checkout page. Thank you @YeLnatSs
• #12893: Fix bug on contact for mail too long. Thank you @YeLnatSs
• #12964: Wrong specific price refresh on product page with combinations, by @PierreRambaud
• #13009: Change product canonical url to parent, no more redirection, by @jolelievre
• #13081: Empty filter should not be shown, by @PierreRambaud

Tests

• #13052: Remove usage of TRAVIS_BUILD_DIR, by @PierreRambaud
• #13113: Fix typo on static, by @Quetzacoalt91

Installer

• #13069: Update demo features, by @marionf
• #13078: Revert “Delivery slips fails when upgrading to 1.7.5”, by @Quetzacoalt91

Webservices

• #12329: API and Products: Add missing combination IDs in the pack content, by @Quetzacoalt91

Code changes in modules, themes & tools

Circuit breaker

• #29: Downgrade Guzzle to v5, by @eternoendless
• #30: Merge version 2.0.0, by @eternoendless

Auto upgrade

• #293: Call CLDR update only if the class exists, by @Quetzacoalt91

Docker

• #156: Remove builds with PHP 5.5, by @Quetzacoalt91
• #159: Defines only made on true values, by @Quetzacoalt91

UI Kit

• #63: Use pixel-based breakpoints once again, by @eternoendless

MBO

• #87: Make MBO handle adding the Recommended modules button in pages, by @eternoendless

NVD3 Charts

• #4: Remove die() from the module, by @Quetzacoalt91
• #5: Bump version to 2.0.1, by @Quetzacoalt91

Shop Generator

• #3: add composer.lock and ignore config.yml + generated_data directory, by @PierreRambaud

Main Menu

• #20: Fix boom-3633, by @marionf

Changes in Documentation

• #223: Added docs on Grid templating customization, by @mickaelandrieu

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @arnaudschaeffe, @kpodemski, @MathiasReker, @prestamodule, @rblaurin, @rokaszygmantas, @sarjon, @tomas862, @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

View the full article

It combines many good practices in testing well working at Prestashop where we implemented different testing solutions for different projects and contexts. I invite you to have a look on our previous article to refresh your memory.

But what are E2E tests?

In order to test and validate each release we can consider three categories of tests, that includes:

• Unit tests, to check input/output of our functions, methods and classes.
• Integration tests, to check that individual features work well with others.
• End-to-end tests, to check that entire features work well in terms of user’s perspective.

The last one concerns the main topic in this article, we call it sometimes functional or acceptance tests but it refers to the same word: E2E tests.

The most important thing in testing software is to check that this is working for users. Well written E2E tests let you know if at least on piece of a feature (product page, front-office UI, database,…) is not working as expected. This is extremely valuable because it saves a lot of time by avoiding manual checks on each context and each time a change is made.

If you want to run the tests or have an overview of the current stack, this is explained on GitHub, in the Test’s readme.md.

Introduction to Puppeteer

Puppeteer is one of the most trending testing tools in the web development community and hopefully made it easier for you to test your websites.

Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol. Puppeteer runs everything in a headless (by default) Chrome instance, so you know you’ll be rendering things the same way you do in the Chrome browser, it is possible also to run it headfull. You can do anything that the tools can, and more, because now you have access to the objects that operate under the hood.

How Puppeteer tests look like ?

And now let’s see how we can control our browser with Puppeteer in Javascript through examples:

Example #1 - Take a simple screenshot in Prestashop Front Office: How can we take a screenshot of a prestashop page in less than 10 lines of codes? To begin create a new directory and use npm to install the Puppeteer library

mkdir prestashopTest
cd prestashopTest
npm install puppeteer

And now create a file prestasnapshot.js and copy/paste the code below:

const puppeteer = require("puppeteer")
const getPrestaShot = async () => {
  const browser = await puppeteer.launch()
  const page = await browser.newPage()
  await page.goto("http://fo.demo.prestashop.com/")
  await page.screenshot({ path: "prestashopsnap.png" })
  await browser.close()
}
getPrestaShot()

Run this script on your terminal with this command line

node prestasnapshot.js

Congrats you’ve just made your first script running on Front-Office page! Puppeteer could be also used as automation tool, so you can use it for long and recurrent manual tasks. Keep track on our next Pull requests we will share with you some interesting automation tests.

Strength of puppeteer

Puppeteer is really interesting for:

• Catching (non visual) JS errors and not only the presence of elements in a page while running a scenario

• Natively take screenshots and or create pdf document.
• Less NPM dependencies
• All-in-one puppeteer (chrome and all needed packages) no selenium-standalone server required (java, selenium-standalone, webdriver, chromedriver)
• Natively Headless <3 and work well with docker (no webdriver “Error: invalid session id”) Puppeteer launches Chromium in headless mode, but it’s also possible to launch Chromium in headfull mode by setting the ‘headless’ option when launching a browser:

const browser = await puppeteer.launch({headless: false}); // default is true

Why change?

Long story short: Sustainability

Since the official announcement of Chrome Headless, many of the industry standard libraries for automated testing have been discontinued by their maintainers like PhantomJS and Selenium IDE for Firefox which has been discontinued) due to lack of maintainers.

Puppeteer’s library is officially maintained from the Chrome DevTools team, with many contributions (see Contributing). This means it has a solid future. This also means it supports all modern JavaScript syntax available in Chrome (like async/await).

Main Selenium stack drawback

Tests:

• Lot of false flags
• Stack unstable (need many updates)
• The headless mode seems to have some difficulties

Installations and dependencies required:

• Selenium-standalone
• Java
• Chromedriver
• Xwebdriverio

The new Nightly Builds & Tests Dashboard

Aside from the classic tests, a new dashboard has been introduced recently with the automatic nightly builds. A report is joined when the testing suite was able to run. You can find it at this brand new URL: https://nightly.prestashop.com/

With a quick look, you can identify if tests have been done on a successful build, how much tests failed, and there is a link to download the entire report. Once a report is open in your browser, click on the left menu icon to use the filters. There, you can find code to improve, or tests to fix ;-)

Puppeteer + Mocha in our E2E stack architecture

E2E testing is traditionally not easy to maintain, but beginning to use Chrome headless made our tests more reliable, faster and simpler here @Prestashop. It is a real pleasure to test with Puppeteer and I recommend you to try it out on your Prestashop.

<3 From QA Team with love <3

View the full article

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 cinostroza, hairul123, Jaroslava, jpvapehiro, olcaykart, and santorosalvo. See you soon on Crowdin… and PrestaShop. ;-)

A few stats

• 24 members were active on the project this month.
• A total of 175,348 words have been translated and 7,421 validated.
• All this in 18 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 February 2019.

Top 10 translators in February:

Top 10 proofreaders in February:

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 February 2019, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 31 languages:

For its part, PrestaShop 1.7.5 was fully available in 24 languages!

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 February 2019, some languages would still benefit from some proofreading:

• Flemish (100% translated vs 0% validated in 1.6).
• Galician (100% vs 62% in 1.7).
• Spanish, Venezuela (53% vs 17% in 1.6).
• Chinese Simplified (100% vs 71% in 1.7).
• Tagalog (52% 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

General messages

Dear Developers,

This is the very last week to submit a pull request and make it approved: code freeze is due on Friday, 29th of March.

The work of the maintainers is currently focused on code review and merge, plus finalizing their current work. Don’t forget that each morning, you can download a fresh nightly build with the latest code merged in the PrestaShop open source project. That should help to build and test an Alpha release, hopefully next week.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 59 new issues have been created in the project repositories;
• 82 issues have been closed, including 9 fixed issues on the core;
• 39 pull requests have been opened in the project repositories;
• 43 pull requests have been closed, including 18 merged pull requests.

Code changes in the ‘develop’ branch (for v1.7.6.0)

Core

• #9337: Migrate “Brands” listing page (a.k.a manufacturers). Thank you @sarjon
• #11962: Do not stripslashes value from _GET & _POST, by @PierreRambaud
• #12940: Do not look for translations if no locale, by @matks
• #12956: Customization - improve phpdoc and constants usage. Thank you @Matt75
• #12959: Handle Tools curl timeout to ease debugging, by @matks
• #12960: DoctrineBuilderExtension uses YamlParser for its config, by @jolelievre

Back office

• #12641: Tax create/edit form migration. Thank you @zuk3975
• #12647: Migration of “Design -> pages -> add new / edit page category”. Thank you @tomas862
• #12705: Update OrderHistory to manage {followup} & {shipping_number} vars in all email templates, not only in in_transit template. Thank you @jf-viguier
• #12782: Fixes for migrated Categories add/edit actions. Thank you @sarjon
• #12897: Enable lite display for new theme, by @matks
• #12946: Fix issue in AdminCarrierWizardController::processRanges(). Thank you @Matt75
• #12971: Enable customers page. Thank you @sarjon

Front office

• #12564: Manage Doctrine entities from modules, doctrine available for front, modules autoload on front, by @jolelievre
• #12965: Fix wrong cart calculation when using cart rule with virtual products, by @tomlev

Tests

• #12634: Behat cart tests, by @tomlev

Code changes in modules, themes & tools

Circuit breaker

• #28: Improved Symfony implementation, by @mickaelandrieu

UI Kit

• #59: Adds possibility to display file name on file upload. Thank you @tomas862

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @jf-viguier, @Matt75, @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

View the full article

View the full article

View the full article

General messages

Dear Developers,

A quick reminder: code freeze for PrestaShop 1.7.6.x is due 29th of March 2019, at the end of next week. So, if you want to fix a critical bug or to add an important improvement in the next version, the time has come to finally make your pull request and ask for a merge. Don’t be shy ;-)

Then, in April, an alpha is going to be built, and the testing / debugging period will start.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 56 new issues have been created in the project repositories;
• 43 issues have been closed, including 6 fixed issues on the core;
• 52 pull requests have been opened in the project repositories;
• 60 pull requests have been closed, including 44 merged pull requests.

Code changes in the ‘develop’ branch (for v1.7.6.0)

Core

• #10406: Document and add tests to Faceted Search system, by @mickaelandrieu

Back office

• #12163: Migration of shop parameters->contact->contacts add new edit contact form. Thank you @tomas862
• #12423: Taxes list migration. Thank you @zuk3975
• #12644: Add margin between buttons on Traffic & SEO page, by @YeLnatSs
• #12699: Refacto addons store controller and handle addons failure, by @matks
• #12788: Remove html escaping of errors. Thank you @bilfeldt
• #12794: Add missing columns in products_import.csv. Thank you @rblaurin
• #12874: Fix Symfony console crash because of DocumentationLinkProvider service definition, by @jolelievre
• #12912: Fix Traffic and SEO route paths, by @matks
• #12945: Build assets, by @matks

Front office

• #10253: Add modal-dialog-centered class to classic theme, by @CaptainYouz
• #11943: Improve performance by avoiding parsing YAML files during ModuleManagerBuilder init, by @jocel1
• #12817: Robots should not index search content. Thank you @watou

Installer

• #12864: Remove ps_legalcompliance from composer.json , by @Quetzacoalt91

Tests

• #12902: [Backport from develop] Allow Travis phpHigh build to fail as it is an informative check, by @matks

Code changes in modules, themes & tools

Circuit breaker

• #27: Added symfony circuit breaker, by @mickaelandrieu

Auto upgrade

• #289: Remove PclZip from the project, by @Quetzacoalt91

Nightly Board

• #3: New theme, by @PierreRambaud
• #4: Gcloud configuration and change title name, by @PierreRambaud
• #5: Add Deploy command, by @PierreRambaud
• #6: Use a href instead of window.open, by @PierreRambaud

Amazon Payments

• #82: v3.2.6. Thank you @paeddl
• #83: v.2.2.7. Thank you @paeddl

Architecture Decision Records

• #3: Add Mixed use of composer and zip modules, by @eternoendless

Shopping cart

• #29: Doctrine indent. Thank you @MathiasReker
• #30: Improve indentation and whitespace. Thank you @MathiasReker
• #32: Multiline whitespace before semicolons. Thank you @MathiasReker
• #34: Cast spaces. Thank you @MathiasReker
• #35: Blank lines. Thank you @MathiasReker
• #37: New with braces. Thank you @MathiasReker

Legal Compliance

• #47: Single quote. Thank you @MathiasReker
• #48: Include. Thank you @MathiasReker
• #50: Improve type casting. Thank you @MathiasReker
• #51: Php unit set up tear down visibility. Thank you @MathiasReker
• #53: Php unit method casing. Thank you @MathiasReker
• #54: No alias functions. Thank you @MathiasReker
• #55: Dir constant. Thank you @MathiasReker
• #56: Improve imports. Thank you @MathiasReker
• #57: Multiline whitespace before semicolons. Thank you @MathiasReker
• #58: Logical operators. Thank you @MathiasReker

Changes in Documentation

• #226: Add deprecation notices, by @eternoendless
• #228: Fixed Naming Conventions devdocs sections. Thank you @lel-amri
• #229: Handle form error in product page. Thank you @jf-viguier
• #230: Clarified how the upgrade works, by @eternoendless

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @bilfeldt, @jf-viguier, @lel-amri, @MathiasReker, @paeddl, @rblaurin, @tomas862, @watou, @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

View the full article

View the full article

General messages

Dear Developers,

An important step for the PrestaShop open source project has been completed last week and it is available today: the nightly builds and tests dashboard. This is a new dedicated website: https://nightly.prestashop.com/.

Each night, a new build is created with the newly merged code. Then, the automatic tests are run for this build, and a report is created. Those tests are different from the suite on Travis: they cover more features of PrestaShop, and may require several hours to complete. That’s why we don’t execute them on each pull-request, for instance. It will help contributors to improve the quality of PrestaShop.

For now, you will see that many tests are failing. This will be improved and corrected during the weeks before the code freeze. And of course, your help is welcome 😀

A quick update about PrestaShop’s GitHub issues and pull requests:

• 60 new issues have been created in the project repositories;
• 73 issues have been closed, including 9 fixed issues on the core;
• 35 pull requests have been opened in the project repositories;
• 36 pull requests have been closed, including 29 merged pull requests.

Code changes in the ‘develop’ branch (for v1.7.6.0)

Core

• #11783: Migrate customers searching via ajax. Thank you @sarjon
• #12251: Improve version, by @eternoendless
• #12570: Add Drag & Drop styling for category position column. Thank you @sarjon
• #12749: 9 duplicates removed from array in getProductAttributeWhitelist(). It…. Thank you @toslan
• #12766: Remove duplicated CLDR service, by @matks
• #12803: Fallback on language code when locale is empty, by @Quetzacoalt91
• #12808: Deprecate Cart::addExtraCarriers(), by @eternoendless
• #12810: Install ps_faviconnotificationbo automatically, by @eternoendless
• #12841: Add deprecation notice for hook actionAjaxDieBefore, by @eternoendless

Back office

• #12505: Improve error handling in migrated controllers. Thank you @sarjon
• #12610: Taxes Options configuration form migration. Thank you @zuk3975
• #12717: Adds re-usable rewrite link copier service. Thank you @tomas862
• #12730: Error 500 in product catalog when short description is too long. Thank you @rblaurin
• #12751: Fix saving shop association in migrated add/edit forms. Thank you @rokaszygmantas
• #12784: Add module main class parse error to log message. Thank you @teemumantynen
• #12787: adds legacy links to all meta page routes. Thank you @tomas862
• #12838: Update ProductSpecificPrice.php. Thank you @metineren

Front office

• #12748: Remove obsolete P3P policy. Thank you @MathiasReker
• #12753: Allow ipv6 to be used in htaccess redirects, by @Quetzacoalt91

Installer

• #12666: Delivery slips fails when upgrading to 1.7.5. Thank you @rblaurin

Web services

• #12836: Fixes http 500 when trying to get the images of a product with no images . Thank you @mowcixo

Tests

• #12793: Allow Travis phpHigh build to fail as it is an informative check, not…, by @matks
• #12804: Use string value for CSRF token in DeliveryControllerTest, by @matks

Code changes in modules, themes & tools

Circuit breaker

• #26: Ease configuration of calls using all usual HTTP methods, by @mickaelandrieu

Auto upgrade

• #285: Use raw trans to avoid " being displayed, by @Quetzacoalt91
• #286: Allow ipv6 to pass the maintenance check, by @Quetzacoalt91
• #288: Do not reset theme anymore when already active (prevent hooks to be reset), by @Quetzacoalt91
• #290: Do not display exception when running unit tests, by @Quetzacoalt91

Changes in Documentation

• #224: Add documentation on legacy controllers, by @eternoendless

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @mowcixo, @rblaurin, @sarjon, @tomas862, @toslan, @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

General messages

Dear Developers,

It seems that we eventually found a proofreader for the devdocs ;-)

That is a very interesting kind of contribution: this is something that does not require coding skills, but this is still very valuable. The documentation is then more pleasant to read and to understand.

There are many activities that you can do if you want to help with the PrestaShop open source project, but you are not a developer:

• Telling that it’s great and recommanding it
• Planning events
• Writings documentation and tutorials, or producing videos to show how it works
• Helping with issue sorting, like for example identifying duplicates or asking for details
• Helping users on the forums and other websites were users ask question about the software

A quick update about PrestaShop’s GitHub issues and pull requests:

• 55 new issues have been created in the project repositories; ()
• 53 issues have been closed, including 5 fixed issues on the core;
• 59 pull requests have been opened in the project repositories; ()
• 48 pull requests have been closed, including 35 merged pull requests.

Code changes in the ‘develop’ branch (for v1.7.6.0)

Core

• #12346: Add Category form builder & handler. Thank you @sarjon
• #12498: Add showcase card for Suppliers list. Thank you @sarjon
• #12739: Revert to Webpack 2, by @PierreRambaud
• #12756: CO: Fix bug when create class override Address. Thank you @dariusakafest
• #12758: Added a Theme Enabler command, by @mickaelandrieu

Back office

• #10595: Migration of “Shop parameters >Traffic & SEO > SEO & URL > Add new / edit page” form. Thank you @tomas862
• #12622: Refactor AddonsStoreController to use annotations and some improvements, by @matks
• #12668: Fix help sidebar when adding/editing language. Thank you @sarjon
• #12706: Kpis list are now customizables using hooks, by @mickaelandrieu
• #12709: Refactor MetaController to secure search usage, by @matks
• #12711: BO the shipping cost becomes free if more than a half ordered. Thank you @LedCloud
• #12713: Enable usage of roles for Module Updates and Module Alerts pages and manage access, by @matks
• #12716: Prevent including jQuery in the new theme, by @eternoendless
• #12723: Patch to Issue #12500. Thank you @rblaurin
• #12761: BO: Remove timeout from product image upload. Thank you @JohnMidity

Front office

• #12696: fix missing coma in sql upgrade file, by @tomlev
• #12733: Changed the regex to force space and hyphen in postcode validation. Thank you @jojotjebaby

Localization pack

• #12747: Fix PhpDoc for AttributeGroupCore::getAttributes(). Thank you @BadPixxel

Tests

• #12488: Add a descriptif comment for the broken test “create_edit_delete_language”. Thank you @YosraAk
• #12490: TE: add a descriptif comment for the broken test “create_edit_delete_contact”. Thank you @YosraAk
• #12495: Add a descriptif comment for the broken test “installation language <> country “. Thank you @YosraAk
• #12678: Create virtual product. Thank you @ansar21mallouli
• #12679: Add some fixes to the campaign full. Thank you @YosraAk

Code changes in modules, themes & tools

Nightly Board

• #2: Create LICENSE, by @PierreRambaud

Mail alerts

• #18: php 7.2 compatibility fix. Thank you @kpodemski

Gammification

• #62: Stop including jQuery twice in 1.7, by @eternoendless

Changes in Documentation

• #213: Minor grammar corrections. Thank you @d-roduit
• #214: Minor grammar correction. Thank you @d-roduit
• #215: Minor Grammar Corrections. Thank you @d-roduit
• #216: Moved PrestaShop webservices outside of Components section, by @mickaelandrieu
• #217: Grammar + consistency corrections. Thank you @d-roduit
• #218: Minor orthographic corrections. Thank you @d-roduit
• #219: Grammar corrections. Thank you @d-roduit
• #220: Spelling corrections. Thank you @d-roduit
• #221: Update back-office.md. Thank you @arthtux

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @ansar21mallouli, @arthtux, @BadPixxel, @d-roduit, @dariusakafest, @JohnMidity, @jojotjebaby, @kpodemski, @LedCloud, @rblaurin, @sarjon, @tomas862, @YosraAk!

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

View the full article

View the full article

Winter is not coming, it is already here!

As a member of the Open Source community, a few weeks ago PrestaShop went to the coldest place on earth, even colder than Antarctica, even colder than Siberia: YES, we went to Chicago on January 30th 2019 (-40º C)

You’re all asking: “But what can we do on January in Chicago except eating Deep Dish pizza and drinking India Pale Ale?”

(Yes, it was pretty tasty!)

Well, there was a CMS Security Summit organized by Google, to which Prestashop was kindly invited!

Google had the great idea to welcome the main CMS open source projects such as Joomla, Wordpress, Drupal and so on alongside other players of the CMS ecosystem (like SiteGround, Symfony, among others) to have a face-to-face meeting with security specialists.

What we learned

First of all, you should know that 55% of the top 10 million websites are built on CMS platforms, and this number keeps growing.

As more and more websites are based on CMS technologies, maintainers are doing their best to make templating ever more powerful. One typical feature is allowing to change a page’s structure on the fly, for example, to add a custom field to a form.

Since the DOM tree is exposed to the user, DOM content and user input must be effectively monitored in order to prevent XSS attacks.

Google has been fairly successful at fighting these attacks by relying on Trusted Types, a set of typed objects that replace strings when representing HTML snippets, URLs, etc.

Compilation-time analysis on JavaScript code ensures that only these types are allowed to be used with various DOM APIs that can be exploited as DOM-based XSS sinks (el.innerHTML, location.href, ScriptElement.src and so on). Trusted Types are currently being used internally at Google, and will be built into browsers soon.

If you learn further about XSS attacks, I suggest having a look at Content-Security-Policy with Google, which describes it all.

If you are already familiar with CSP you can check if you have a strong mitigation using the CSP Evaluator

What do you think about this? Should we plan to integrate it in PrestaShop soon?

Third-party components and integrity control

In most systems, vulnerabilities often come from additional modules or themes that are not part of the core platform codebase.

In the case of PrestaShop, like other CMSs, it is really hard to audit what users are doing with their shop in terms of security: they are able to add custom modules, dependencies, a lot of things that cannot be controlled and secured by project maintainers.

In the Prestashop Addons Marketplace security process, each submitted module is thoroughly reviewed by our fantastic team. Each payment module is also pentested, even the ones not developed by the PrestaShop team.

Of course, we all know that even fantastic humans are error-prone: that is why PrestaShop invests in continually improving the automated Module validator. Other CMS are also considering static code analysis tools like scrutinizer or snyk. That is maybe something to add to our validation tools.

We are currently discussing about adding PHPStan and PHPQA to our modules, which are two really great tools to improve code quality.

Another improvement currently under consideration is to cryptographically sign modules or themes sold on the PrestaShop Marketplace, so that merchants can make sure they are legitimate and haven’t been modified by an attacker.

Vulnerability disclosures & rewards

This is known, there is no Bug Bounty program for the PrestaShop project… yet! But it can be a real issue:

• it can be hard for contributors to spot where they must go to report security issues
• some researchers need rewards to feel motivated enought to create a report

What kind of reward would you want? A tee-shirt? Money? Preston Plushies? Goodies?

Drupal is kind of the leader here: they have a Bug Bounty program, documentation about How to report a security issue and a CVE history. Drupal can be a good source of inspiration for PrestaShop here.

Moreover, since the group that creates PHP interoperability standards has reopened what they started for PSR-9 (Security Advisories) and PSR-10 (Security Reporting Process), it appears to be a good reason to take some time between two code reviews, think about a bug bounty program and write documentation about it.

One click upgrade or autoupgrade?

The best way to have a secure system is to stay up-to-date. Many people don’t care about upgrades, but they don’t realize that security fixes need to be applied as fast as possible, or else their shop is at risk!

Seeing things exclusively through an economic prism can be misleading: yes, upgrading may cost you money now. But think about what could be lost if an intruder comes, injects an XSS and steals your clients’ information, or adds a script that shuts shop off or deletes everything you had!

But, how to update a CMS when a lot of modules or a custom theme are already installed? How to avoid breaking something that we are not aware of? How to be sure that users and developers are following the best practices?

These are very difficult questions to which we still don’t have the answer. But we are working on it. If you encounter problems during upgrading your shop, send us your feedback!

Some CMSs already feature automatic self-updates that happen without any user interaction. At the summit, host providers called for all CMS to implement this feature as well.

What do you think? Should we add it? And would you be brave enough to enable it? Would you help us test it and debug it?

Tools and platform innovations

Security must be an important part of the whole development process.

All developers must take in consideration what will happen with the data they are handling. A big issue is that most tools for detecting vulnerabilities are proprietary, so obviously they won’t help developers to learn more about security by analyzing how they work.

As the community needs to be educated using tools, guides and documentation, it’s our duty as CMS maintainers to pave the way by creating a website, a platform or whatever, so that this information is freely available, A place where anyone can contribute and be a part of the open source security community.

About 30 people attended the summit in Chicago. Right after it, the Google team created a document summarizing what happened and a Google Group so that security folks can continue to discuss and share ideas!

I would like to thank the Google team for their excellent initiative and all the work they put in for this event. The CMS ecosystem’s security is going to change!

View the full article

General messages

Dear Developers,

Last week, a very big piece of work started two years ago has been merged into the “develop” branch: the CLDR implementation. It will allow the next versions of the PrestaShop project to manage well localization and display of units and currencies, by following the Unicode international standard used by many companies. As you can expect, a lot of code reviews and tests have been done, that’s why less pull requests have been merged than usual during the week.

Learn more about CLDR.

A quick update about PrestaShop’s GitHub issues and pull requests:

• 70 new issues have been created in the project repositories
• 46 issues have been closed, including 6 fixed issues on the core.
• 28 pull requests have been opened in the project repositories
• 33 pull requests have been closed, including 17 merged pull requests

Code changes in the ‘develop’ branch (for v1.7.6.0)

Core

• #10455: New CLDR implementation, by @tomlev
• #12559: Fix translations removing from db when Language is deleted. Thank you @sarjon
• #12598: Restore composer file, by @PierreRambaud

Back office

• #12046: TemplateMail generator, by @jolelievre
• #12465: Fixed duplicated id, by @mickaelandrieu
• #12563: Fixes error in admin panel when visiting a category that’s not under Index. Thank you @mowcixo
• #12597: Bug when switching language. Thank you @helgvor-stoll

Code changes in modules, themes & tools

Auto-upgrade

• #275: Do not upgrade PrestaShop when already on the last version , by @Quetzacoalt91
• #281: Deploy v4.6.0 of the autoupgrade module, by @Quetzacoalt91

Docker

• #154: Add PrestaShop 1.7.5.1, by @Quetzacoalt91

Changes in Documentation

• #195: Add recommendations in system requirements, by @Quetzacoalt91
• #196: Fix file name in template-inheritance example. Thank you @SharakPL
• #200: Add PositionUpdater component doc, and update columns references docs, by @jolelievre
• #201: Added tutorial on how to customize an existing Grid, by @mickaelandrieu
• #203: Add some migration conventions, by @matks
• #206: Fix Wrong method name. Thank you @nenes25
• #207: Change issues link. Thank you @nenes25

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @helgvor-stoll, @mowcixo, @nenes25, @sarjon, @SharakP! And a special thank to @tomlev for the CLDR implementation.

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

View the full article