The first beta version for PrestaShop 1.7.3.0 is now ready for you to test and give feedback about!

We said it earlier, many times. Now it is the right time to announce proudly that we are close to releasing 1.7.3.0. Features and improvements have found their way to the 1.7 codebase, we are thrilled to let you have a look at it and play with it before everyone else!

However, note that it is a beta version, not a release candidate. Despite all the efforts we’ve been putting into this version these last months, it is not fully ready to be released. We are still debugging, improving, stabilizing it. And 4 tickets remain on the Forge :

BOOM-4110: Visual regressions on catalogue module page
BOOM-4319: RTL regressions
BOOM-4480: 1click upgrade from 1724 to 1730
BOOM-4448: BO - Page figée à la désinstallation d’un module

While we are working hard on it, we can’t wait to receive your feedback about the beta version! As usual, this period of testing and fixing is crucial, and it always goes with the help of any merchant, service provider, module developer or theme designer who can test it and let us know about their experience. An effective testing of the beta will indeed lead towards a proper release candidate.

Test PrestaShop 1.7.3.0 beta 1 now!

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!

A great thank you

First of all, it is important for us to thank you as much as possible for the contribution the community has done so far. As an open source software, we are always pleased to include in this project everyone who feels like participating, giving feedback and trying to make PrestaShop goes smartly further. Altogether.

In this case, about 190 PRs have been merged. Huge, right ? And all this with the impressive number of 52 contributors, 17 internal and 35 external. So let us give a warn and big thank you to :

Adonis Karavokyros, Alexandr Simonchik, AliShareei, Antonio Intagliata, Aymeric Auberton, Christian Kubitza, Code Utopia, comxd, Cristiano Verardi, Daniel, Danoosh, dariusakafest, David, Dickriven Chellemboyee, FrancMunoz, Gabriel Arama, iqit-commerce, Krystian Podemski, Mahdi Shad, Manfredi Petruso, Marcin Sągol, Marek Hanuš, MattLoyeD, maxime aknin, MDWeb, mehrshadz, Molka Djemal, nache, Presta Module, Shagshag, Tony Botalla, venditdevs, Yolandavdvegt, Yuri Blanc, Šarūnas Jonušas

What you need to know about PrestaShop 1.7.3.0

Of course, it includes all the fixes that were part of the 4 patch versions since the release of the 1.7.2.0 in July 2017. It brings the following main features:

• PrestaTrust
• Shipping delivery times
• Low stock alerts
• RTL stylesheet generation
• Bulk edition in stocks
• A product can now have multiple features of the same type
• Import/Export on Stock Overview page
• UI Kit, available in the Symfony pages
  • Bootstrap 4 alpha 5 > latest Bootstrap 4 beta 2
  • jQuery 3
• Symfony migration
  • Modules can now act as Symfony Bundles
  • Improved debug toolbar including hook information and more
  • 3 new pages migrated to Symfony (Modules Catalog, Performance, System Information)

And also:

• Icelandic localization
• Installer in Japanese
• Store schedules are now localized
• New hook on AdminCustomers view > Addresses actions
• Tools for building a release package of PrestaShop are included in the source code
• Sample configuration file for Nginx server

… and many bugfixes and performance improvements! Check the full changelog here.

How to give feedback about this beta

Have you found a bug? A curious behavior? An unexpected reaction? Please let us know!

Create a ticket on the 1.7 Forge project, and give us as much details as possible!

Final note

As you might have guessed, a lot of work went into this beta version, and there is still a lot of work to be done in order to get it ready for release. So help us, download and test it, because you too can help with pull requests for bugs that you noticed!

Test PrestaShop 1.7.3.0 beta 1 now!

Happy testing, and thanks again!

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 11th to Sunday 17th of December 2017.

General messages

Say hello to the 1.7.3 beta 1 version, available here and waiting for you to be tested! It is a first achievement towards a fully stabilized version, some features (like the RTL) are still under construction to be debugged. It is because we are still working on improving the 1.7.3 that we have decided to release a beta instead of a RC. Anyway, we would love to have your feedback on it, let us know on the Forge.

One last (great) information, the Crowdin community extends itself again last week, the Greenlandic project is now available for translation. Come and help us on it too!

Also, it is time for us to disclose the results of the survey submitted a month ago. We can’t wait learning about you people and drawing the right conclusions to head to a more pertinent devblog, useful for everybody who needs it. What a beautiful intention, right?

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

Core

• #8561: Make Symfony form management more robust, by @mickaelandrieu.
• #8566: Use official Smarty lib, by @quetzacoalt91.
• #8583: Add help for upgrade file, by @quetzacoalt91.
• #8606: Fixed newsletter registration date doc. Thank you @c100k!

Back office

• #8489: Improved Product pages templates management, by @mickaelandrieu.
• #8588: Add parameter to setMedia. Thank you @aw73!

Front office

• #8563: add FORCE INDEX to workaround https://bugs.mysql.com/bug.php?id=88671, by @jocel1.

Code changes in the ‘1.7.2.x’ branch (for v1.7.2.3)

Front office

• #8564: Hide the password in the confirmation email. Thank you @azouz-jribi!

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @aw73, @azouz-jribi and @c100k!

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 tickets and comments on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

• Contributing code to PrestaShop
• How to write a commit message

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Dear readers, followers, developers, translators, PrestaShopers from all sides, we call for your opinion about the devblog, you answered, thank you so much!

We must admit that we were quite eager for the results, as we know Build needs to evolved and be improved. Since we are convinced this change must come with you, as you are all the first involved in it, it seems important to us to ask for your opinion about it. Let’s turn Build into a more custom-made devblog!

About you

First, let’s have a look at the most important… Who are you, all Build followers? A simple question which brought a little surprise with the answer because we discovered that most of you are long-time followers, and it is something very nice to acknowledge! Indeed, 60% read Build since more than a year and this once a week. It’s quite a score, right?

Second important thing is that the readers are split up into 70% developers and 25% merchants. Not a really big surprise but still. Between the lines, it means we need to keep on writing about the PrestaShop software and its current/planned evolution to give you news about how it can work for you.

About Build

Same thing here, what we learned in this part is that Build is here to fulfill a need. In most cases, readers land on the devblog after a web research (63%) or via GitHub (20%). But the other answers are also interesting to study: social medias stand for 8% and the rest comes from PrestaShop itself. Let’s not forget that PrestaShop has been developing a lot of activities with its broad community (translation projects, forum, meetings, blogs, etc.), and this is what brings you here!

What for? First thing to know: there is 57% chance you read this because you want to develop PrestaShop. Or you want to get extra documentation on a possibility, feature or module. And the cherry on top is that more than 87% of you declared their visit on Build helpful. So blog posts here are pretty useful and constructive. In a nutshell, we need to keep a good level of information, assistance and achievement in our articles. It has to be our number one rule which needs to apply to each blog post.

What’s next

As for the future of Build, here are two clouds representing what kind of articles we need to keep and start, following the most used key words. First, the conclusion to draw is that we need to continue posting news about PRs merged, features we want to integrate in future releases. Roadmap is also one thing to maintain, and perhaps get clearer but we will see that later. In other words: what is the upcoming development for PrestaShop.

Originally, the point was also to let the community express itself. Build was a way, accessible to anyone interested, to write about PrestaShop and how to develop the software. But this possibility slowly disappears and it happens that today, when the question was asked whether you would like to write on the devblog, answer was no, up to 72%! But this does not mean you do not have expectations…

Among all the topics raised, the ones to focus on are development, features, modules, translation, documentation, practices and roadmap. In general, you look for precise and technical, sometimes shorter, information about the way you can use and develop PrestaShop. And about how our dev team is working, which is a very interesting subject we can easily emphasize.

Last but not least, it seems there is no need of a newsletter. Note the publication schedule: Monday is core weekly day, Wednesday is software day and Friday is fun day!

Again, thanks a lot for answering our survey, we are glad to have collected so many information and ideas to study, we will learn from it and tend to a brighter future. ;)

Remember I told you about weird blue elephpants? You got it, it was our dream team of developers that attended the AFUP’s annual conference in Paris! As agreed, they came back with a lot to share on Build. Here, @Quetzacoalt91 will told you about Nicolas Grekas and the lecture he gave at the PHP Forum:

Quality processes: the Symfony case

“You may have heard about Nicolas Grekas, a core team member of the Symfony project and CTO of Blackfire. We had the chance to see him last October in Paris where he presented the quality process in Symfony. He talked about several subjects, all around the maintainability of this huge project.

We have already borrowed some good ideas from them, and this is why you have to fill a table when you submit a pull-request on the PrestaShop project. Without it, we could still receive new pull-requests “without description”, sometimes even with a non-explicit title. Quite hard to guess what the contributor wants to fix in this case, right?

Anyway, several of the topics covered in this presentation were familiar to us. Not only because we have an open-source project in common, but also because we share a complex architecture: a main project with several dependencies gravitating all around it (in our case, modules).

Nicolas explained how they manage their dependencies (contributions & releases) in the main project. And that was really interesting! We learnt that we could keep an eye on the global activity using a single repository and then manage releases of each dependency using subtrees and read-only repositories.

We have to admit that sometimes we miss the PRs you submit on the native modules, there always contains good ideas to reproduce somewhere else when it works. So if one day you see some improvement to bring in our module management, you will know this presentation was one of the reasons. :)

Want to go further?

Here is a non-exhaustive list of what we saw:

Pull-request management

• How to make them easier to understand?
• What is required before merging a PR?

Applying changes application on all compatible Symfony versions

• Manual cherry picks by the merger

Release definition

• What can be included in a major / minor / patch version?

Note that the AFUP put videos of all lectures given at the last PHP Forum online, on their YouTube channel. How kind!

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 18th to Sunday 24th of December 2017.

General messages

Dear all, the PrestaShop team is happy to wish you a great, beautiful and fun Christmas time! As the holidays are coming, we would like to thank you once again for having made PrestaShop headway so much in 2017. One small step for each of you, one giant leap for the community!

Also, we are very glad to announce our QA Manager, @mbadrani, submitted a pull request a few days ago which consists of a test suite that will help validating features of the software. Mostly, it targets the non-regression of the core ones. It should be the starting point for automatizing tests, first for the QA team but also, we hope so, for the contributors next. What a huge saving of time it would be, right?

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

Core

• #8623: Merge 1.7.3.x into develop, by @eternoendless.
• #8625: Update README.md. Thank you @techhdan!

Back office

• #8611: Fixed bad display manufacturer when multishop. Thank you @okom3pom!
• #8617: Fix/suppliers block refresh, by @mickaelandrieu.

Test

• #8627: Temporarily disable PSFunctionalTests, by @eternoendless.
• #8629: Do no rely on external URL for tests (Returns different content), by @quetzacoalt91.

Code changes in the ‘1.7.3.x’ branch (for v1.7.3.0)

Core

• #8605: Specify version for all PS native modules, by @eternoendless.

Back office

• #8616: Fix dropdown buttons space, by @quetzacoalt91.

Test

• #8628: Temporarily disable PSFunctionalTests, by @eternoendless.
• #8630: Do no rely on external URL for tests (Returns different content) (1.7.3.x), by @quetzacoalt91.

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

Back office

• #7844: Fix Stock cover report stock out calculation. Thank you @marksull!

Front office

• #8579: FO: Split width of sumary invoice pdf. Thank you @casper-o!

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @casper-o, @marksull, @okom3pom and @techhdan!

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 tickets and comments on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

• Contributing code to PrestaShop
• How to write a commit message

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Ça y est, 2018 est là, bonne année à tous ! Et avec elle la loi de finances est entrée en vigueur. Comme un marchand averti en vaut deux, nouveau tour de table de l’article 88 de la Loi 2015-1785, à l’aube de son adoption.

ATTENTION

Ne sont pas concernés par les nouvelles dispositions entrées en vigueur le 1er janvier 2018 :

• Les personnes non assujetties à la TVA, notamment les auto-entrepreneurs,

• Les personnes qui n’éditent pas de factures avec le logiciel PrestaShop (ex. : les commandes de votre boutique sont gérées par PrestaShop mais les factures sont générées par un autre logiciel de type ERP),

• Les marchands qui ne font que du BtoB.

L’article 88

L’article 88 de la loi 2015-1785 du 29 décembre 2015 de finances pour 2016 est venu modifier l’article 286 du Code général des impôts et créer un nouvel article 1770 duodecies dont les dispositions entreront en vigueur le 1er janvier 2018.

Ces nouvelles dispositions ont pour objet de lutter contre la fraude à la TVA et obligent les marchands français à utiliser, à partir de janvier 2018, un logiciel de gestion ou de caisse satisfaisant à des conditions d’inaltérabilité, de sécurisation, de conservation et d’archivage des données en vue du contrôle de l’administration fiscale.

Le périmètre d’application de cette loi a fait l’objet de plusieurs rebondissements.

Pour mémoire :

• 15 juin 2017 : Communiqué de presse du Cabinet du ministère de l’action et des comptes publics selon lequel seuls les “logiciels de caisse” seraient concernés (la définition de logiciel de caisse n’est toutefois pas précisée)

• 27 septembre 2017 : publication d’un projet de loi de finances réduisant le périmètre aux seuls “logiciels de caisse”

• 17 octobre 2017 : Rejet d’une proposition d’amendement présentée à l’Assemblée Nationale le 17 octobre 2017 visant à « préciser le périmètre d’application de la loi de façon à recentrer le dispositif sur les seuls logiciels et systèmes de caisse et à exclure les logiciels de facturation, de comptabilité et de gestion qui relèvent chacun d’autres obligations légales. La suppression du renvoi à l’article 289 du CGI permet d’exclure du dispositif de certification ou d’attestation les transactions donnant lieu à l’émission d’une facture conforme, qu’elle résulte ou non d’une obligation réglementaire uniquement fiscale».

D’autres propositions d’amendements (N°II-574 et N°II-CF387) visant à limiter le périmètre d’application de ces nouvelles dispositions ont également été proposées. Ces derniers n’ont toutefois pas été soutenus.

PrestaShop est ainsi, à l’instar de tous les éditeurs de logiciel open source, confrontée à la mise en conformité de sa solution avec ces nouvelles dispositions. Elle prépare pour cela, et depuis plusieurs mois déjà, leur entrée en vigueur en développant un module intégré à sa solution qui fera l’objet d’une certification afin de permettre à ses utilisateurs d’être en parfaite conformité.

Le logiciel PrestaShop sera certifié grâce à l’intégration de ce module, de sorte que PrestaShop n’aura pas à délivrer d’attestation à ses utilisateurs.

La procédure de certification a été initiée auprès d’une organisation officielle mais, compte tenu des délais, la certification ne sera délivrée que dans plusieurs semaines.

Cela ne doit toutefois pas être une source d’inquiétude pour les utilisateurs de la solution PrestaShop. En effet, l’administration fiscale s’est engagée à accompagner les entreprises pendant douze mois, soit jusqu’au 31 décembre 2018.

Bien entendu PrestaShop informera les marchands dès la certification obtenue et le module disponible.

D’autres questions ? N’hésitez pas à consulter les différentes FAQ publiées sur le sujet !

Contributing to PrestaShop is not only about the code, it’s also about taking part in the PrestaShop translation project! This report tells you how the translations of the software evolved in December.

Project news

Happy new year

Bye 2017, hello 2018! As time goes by, the whole PrestaShop team wishes you a wonderful and happy new year we hope full of achievements, filled with magical words, translated everywhere, approved by all… to say it clear: a new year of joyful involvement! Another occasion to let you know how proud you can be of the work accomplished here every day, we are so grateful for that. So much. Each new month makes us see how far we progress altogether. For instance, version 1.7 gained four 100% completed languages in December, let’s keep heading in 2018!

A few stats

• 44 members were active on the project this month.
• A total of 108,345 words have been translated and 48,530 validated.
• All this in 16 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 December 2017.

Top 10 translators in December:

Top 10 proofreaders in December:

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

For its part, PrestaShop 1.7.3 was fully available in 19 languages!

Languages with the best evolution

In comparison with November 2017, the following languages had the best progress thanks to the translation community:

• Bosnian (+52% to reach 73% translated in 1.7)
• Chinese Simplified (+30% to reach 80% translated in 1.7)
• Chinese Traditional (+8% to reach 80% 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!

The list has quite evolved over the last few months, meaning that a lot of proofreading took place. It’s great!

At the end of December 2017, some languages would still benefit from some proofreading:

• Bosnian (73% translated vs 17% validated in 1.7).
• Chinese Simplified (80% vs 47% in 1.7).
• Portuguese, Brazil (100% vs 78% in 1.7).
• Korean (38% vs 17% in 1.7).
• Arabic (52% vs 37% 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. 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!

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the two last weeks, from Monday 25th of December 2017 to Sunday 07th of January 2018.

General messages

Dear community, we all hope your holidays went fine! As we did for the translators of PrestaShop last Friday, it is time to wish you all a very nice and happy new year. We bet it will be like a long procession of efficient pull requests, created for innovative projects you support and believe in! A wonderful developing year for you all, we are very proud to be part of your involvement, to make PrestaShop goes forward altogether!

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

Core

• #8581: CLDR specification entities, by @littlebigdev.

Front office

• #8636: An error on servers with PHP 7+. Thank you @tmmeilleur!

Back office

• #8645: Modify string for product page. Thank you @louisebonnard!

Code changes in the ‘1.7.3.x’ branch (for v1.7.3.0)

Core

• #8643: Removed duplicate line in upgrade file, by @eternoendless.

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

Front office

• #8445: Fix the sorting problem with a descending order in the products filtering page. Thank you @azouz-jribi!

Back office

• #8640: Move to httpS. Thank you @colonelmoutarde!
• #8644: Update AdminModulesController.php. Thank you @rubenmartins!

Web service

• #8647: Fix the update product web service. Thank you @azouz-jribi!

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @azouz-jribi, @colonelmoutarde, @rubenmartins and @tmmeilleur!

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 tickets and comments on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

• Contributing code to PrestaShop
• How to write a commit message

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Remember? @mickaelandrieu recently introduced the Symfony ecosystem and how it will help making more powerful modules. Going on with this idea, @toutantic will tell you more about Symfony 3 and PHP 5.6 that will both work together to improve PrestaShop.

Current situation of PrestaShop

Since november 2016 and the release of version 1.7.0, PrestaShop uses Symfony 2.8 for the back office and requires PHP 5.4+ to run.

We chose the version 2.8 of Symfony because, at the time, it was the current Long Time Support version of Symfony. PHP 5.4+ was the lowest requirement for Symfony 2.8 and, according to our numbers, most of existing PrestaShop installations were already running on a version of PHP above 5.4.

More than a year later, current LTS version for Symfony is 3.4, PHP 5.4 is no longer receiving any security patches and less than 10% of PrestaShop installs are on PHP 5.4 or below. In addition, bugfix support for Symfony 2.8 will end in november 2018 and security patches won’t be available after november 2019 (source).

Why choose Symfony 3.4 over 2.8?

As we keep working on moving more parts of PrestaShop to Symfony, we asked ourselves: why migrate to a soon-to-be-obsolete version of the framework? So we decided it would make sense to target Symfony 3.4 instead of 2.8. And as Symfony 3.4 requires PHP 5.5.9+, PrestaShop 1.7.4 will require PHP 5.6+ to run.

Since june 2015, PrestaShop is following a more semantic versioning scheme. And this is the part where you might wonder whether we are not breaking semantic versioning when changing dependencies requirements on a minor version.

According to the definition of semantic versioning, the answer is no: you can change dependencies version on a minor or even a patch version. But that is just the technical answer, what is important is that we are not breaking the existing shops. What used to work will still work.

You also wonder why we did not jump directly to Symfony 4.0? Here are our answers:

• v4 requires PHP 7.1, which is too big of a jump for many shops right now

• v3.4 has all the new features of v4, but it is an LTS version whereas v4 is not

What does it change?

Of course, we recommend that you run your PrestaShop install on the latest version of PHP. PrestaShop 1.7.0 to 1.7.3 is compatible with PHP 7.1 and PrestaShop 1.7.4 will be compatible with PHP 7.2.

And for PrestaShop developers, Symfony 3.4 and PHP 5.6 means that now you can use all the new features from PHP 5.5 and 5.6: generators, finally in try catch block or ::class for class name resolution and more.

Oui, l’e-commerce est concerné ! Dernier tour d’horizon de ce qui change pour les marchands :

NE SONT PAS CONCERNÉS :

• Les assujettis bénéficiant d’une franchise de taxe et ceux effectuant exclusivement des opérations ou des prestations exonérées de taxe sur la valeur ajoutée (notamment les auto-entrepreneurs, dès lors qu’ils ne dépassent pas le seuil fixé),

• Les personnes qui n’éditent pas de factures avec le logiciel PrestaShop (ex. : les commandes de votre boutique sont gérées par PrestaShop mais les factures sont générées par un ERP),

• Les marchands qui ne font que du BtoB.

En dehors de ces cas, toute personne assujettie à la TVA française qui enregistre les règlements de ses clients dans un logiciel ou système de caisse, qu’il s’agisse d’une personne physique ou morale, de droit privé ou de droit public, est concernée par les nouvelles dispositions.

L’article 88, qu’est-ce que c’est ?

L’article 88 de la loi 2015-1785 du 29 décembre 2015 de finances pour 2016 a modifié l’article 286 du Code général des impôts en y ajoutant un 3°bis prévoyant que :

« Lorsqu'elle enregistre les règlements de ses clients au moyen d'un logiciel de comptabilité ou de gestion ou d'un système de caisse, utiliser un logiciel ou un système satisfaisant à des conditions d'inaltérabilité, de sécurisation, de conservation et d'archivage des données en vue du contrôle de l'administration fiscale, attestées par un certificat délivré par un organisme accrédité dans les conditions prévues à l'article L. 115-28 du code de la consommation ou par une attestation individuelle de l'éditeur, conforme à un modèle fixé par l'administration »

Pour être conforme, le système ou logiciel doit ainsi satisfaire aux conditions d’inaltérabilité, de sécurisation, de conservation et d’archivage :

L’inaltérabilité doit garantir l’intégrité des données en empêchant l’accès de l’utilisateur à des fonctionnalités de modification/suppression des données validées.

La sécurisation doit garantir le traçage de l’ensemble des enregistrements des encaissements.

Les données enregistrées ne doivent ainsi plus pouvoir être modifiées sans que cela ne laisse de traces.

Afin de satisfaire à la condition de conservation, les données (ensemble des détails de chaque transaction et règlement) doivent pouvoir être conservées pendant 6 ans dans le logiciel ou dans une archive. Le logiciel ou système doit par ailleurs prévoir des clôtures dont les échéances sont cumulatives (journalière et mensuelle).

Cette loi introduit par ailleurs un article 1770 duodecies au Code général des impôts qui prévoit de sanctionner par une amende de 7.500 € le fait de ne pas justifier, par la production de l’attestation ou du certificat, l’utilisation d’un logiciel ou système satisfaisant aux conditions d’inaltérabilité, de sécurisation, de conservation et d’archivage des données. 

Cet article prévoit qu’en cas d’amende, l’assujetti dispose d’un délai de 60 jours à compter de la remise ou de la réception du procès-verbal pour se mettre en conformité avec l’obligation prévue au 3° bis du I de l’article 286.

Si passé ce délai l’assujetti ne s’est pas mis en conformité, il encourra alors une nouvelle amende de 7.500 €.

Ces nouvelles dispositions sont en vigueur depuis le 1er janvier 2018 mais le dispositif ne concerne désormais plus que les logiciels et systèmes de caisse.

La simplification de ce dispositif par une restriction de son périmètre avait déjà été annoncée par un communiqué de presse du Ministre de l’action et des comptes publics en date du 15 juin 2017.

Ainsi, l’article 105 de la loi n°2017-1837 du 30/12/2017 de finances pour 2018 a modifié le périmètre du dispositif établi par la loi 2015-1785 du 29 décembre 2015 de finances pour 2016.

Contrairement aux affirmations de certains blogs et articles, la nouvelle rédaction de l’article 286 3°bis du CGI n’exclut pas du périmètre d’application de ces nouvelles obligations les assujettis à la TVA qui éditent des factures mais seulement les personnes qui éditent des factures conformément à l’article 289 du CGI.

La FAQ communiquée par la Direction Générale des Finances Publiques (DGFIP) relative à l’obligation d’utiliser des logiciels ou systèmes de caisse sécurisés parue le 28 juillet dernier confirme par ailleurs que les acteurs du e-commerce sont bel et bien concernés par ces nouvelles dispositions :

PrestaShop prépare la mise en application de la loi depuis plusieurs mois et son module natif et gratuit est en cours de certification

Comme cela a été indiqué dans nos précédentes communications sur le sujet, PrestaShop prépare depuis plusieurs mois déjà la mise en application de ces dispositions.

Elle permettra à ses utilisateurs de s’y conformer grâce à la mise à disposition d’un module natif (donc gratuit) valable pour les versions 1.6 et 1.7 de la solution qui fait actuellement l’objet d’une procédure de certification.

La procédure de certification a été initiée mais la date de délivrance du certificat ne nous a pas encore été communiquée.

Cela ne doit toutefois pas être une source d’inquiétude pour les utilisateurs de la solution PrestaShop.

En effet, l’administration fiscale s’est engagée à accompagner les entreprises dans la première année d’application des nouvelles règles l’administration fiscale.

Par ailleurs, il a été indiqué que la mise en conformité des logiciels ou systèmes de caisse fera l’objet d’un examen bienveillant afin de tenir compte des circonstances particulières, sous réserve que l’assujetti justifie des diligences accomplies.

En effet, dans la FAQ parue le 28 juillet dernier, la DGFIP indique que « des consignes seront données aux agents de l’administration fiscale pour prendre en compte les circonstances particulières » de l’application de ces nouvelles dispositions :

Par conséquent, les utilisateurs de la solution PrestaShop devront indiquer, le cas échéant, leur intention d’installer le module dès lors que celui-ci sera disponible.

Dès lors que le module sera disponible, les utilisateurs de la solution PrestaShop ayant intégré le module et respectant les modalités de son utilisation n’auront pas besoin de se procurer une attestation auprès de PrestaShop.

En cas de contrôle par l’administration fiscale, le certificat affiché par le module vaudra attestation.

Des questions ? N’hésitez pas à consulter les FAQ publiées sur le sujet ou à nous envoyer un courriel à l’adresse suivant : article88@prestashop.com !

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 08th to Sunday 14th of January 2018.

General messages

Small week for pull requests, big one for communication! As we are moving fast towards the release, we are going deeper in our explanation of the changes to come. Indeed, @toutantic wrote about the migration towards the Symfony 3.4 framework here. Other important point was the law related to Article 88 which asks French merchants to get their billing system certified, in order to prevent fraud.

Also, the Crowdin monthly report is quite impressive for December. Come on everybody, get closer (just there) and have a look, it’s worth it! A lot of languages, such as Bosnian and Chinese, have increased their rate of completion really fast. If it goes on like this, we have good hope to see PrestaShop gaining more than twenty fully available languages very soon. Community is the real force!

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

Core

• #8399: Fix search relevance wrong sort order. Thank you @kershoc!
• #8458: Default AJAX Relevance search sort order is wrong. Thank you @sbordun!
• #8597: CLDR number formatter, by @littlebigdev.
• #8662: Moved CLDR to Core, by @littlebigdev.
• #8663: Merge 1.7.3.x into develop, by @eternoendless.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @kershoc and @sbordun!

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 tickets and comments on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

• Contributing code to PrestaShop
• How to write a commit message

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 15th to Sunday 21st of January 2018.

General messages

Hey, community, hope you’re all fine! There is not so many news to share since the last Core Weekly, but keep an eye on the devblog in the next few days, you might have a really nice surprise… ;-)

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

Core

• #8656: Fix services naming. Thank you @sarjon!
• #8667: CLDR currency (interface, entity and repository), by @littlebigdev.

Code changes in the ‘1.7.3.x’ branch (for v1.7.3.0)

Core

• #8657: Integrate RTL CSS generation in the core, by @eternoendless.

Back office

• #8659: Re-enable uglify on the new theme, by @eternoendless.

Installer

• #8670: Fix store hours migration, by @quetzacoalt91.

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

Core

• #8673: CO: Fix PHP Warning when updating category with multishop. Thank you @mcdado!

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @mcdado and @sarjon!

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 tickets and comments on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

• Contributing code to PrestaShop
• How to write a commit message

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

And here comes the nice surprise… 2018 is here, following the gregorian calendar, let us wish you a successful and happy new year again!

So thank you all for this huge year we spent together, on Crowdin or on GitHub, making PrestaShop so proud of its community. We have prepared this nice infographic to have a look at 2017, to see how PrestaShop moved forward and feel fine about it. You deserve to do so, enjoy it!

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 22nd to Sunday 28th of January 2018.

General messages

Good dev news here! Beside our final new year’s greetings, wonderfully illustrated here to highlight to work achieved in 2017, a great deal of pull requests has been merged last week. Clap your hands, there is no more open issue for the 1.7.3! In the meantime, we are making big progress on the Symfony framework. Stay tuned and be proud, this is coming and this will be huge!

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

Core

• #8683: Locale entity needs to aggregate Price Specifications (one by installed currency), by @littlebigdev.
• #8693: Number specification Repository, Locale Repository, by @littlebigdev.
• #8694: CO: Product name error if not english. Thank you @jorgevrgs!

Back office

• #8580: Added Back Office missing roles. Thank you @alexalouit!

Front office

• #8652: SEO - Add hreflang links for multilang pages, by @quetzacoalt91.

Code changes in the ‘1.7.3.x’ branch (for v1.7.3.0)

Core

• #8691: Add RTL generation for modules and some rtl fixtures. Thank you @danoosh!

Back office

• #8671: Fix visual regressions on Firefox, by @eternoendless.
• #8697: Added Back Office missing roles, by @eternoendless.
• #8702: Fix RTL visual glitches, by @eternoendless.
• #8704: Support Arabic numbers in the Product page, by @eternoendless.

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

Core

• #8429: CO : Icrease limit message chars . Thank you @okom3pom!
• #8695: [-] CO : FIX PHP 7.1 compatibility. Thank you @axometeam!

Back office

• #8233: Fix stock available after add product in order. Thank you @mounirboukhris!
• #8389: BO: Fix selecting a product does not work on Mac. Thank you @guillaumeg22!

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @alexalouit, @axometeam, @danoosh, @guillaumeg22, @jorgevrgs, @mounirboukhris and @okom3pom!

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 tickets and comments on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

• Contributing code to PrestaShop
• How to write a commit message

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

An Open Source community is more than just PR made by faceless strangers. In order to better understand the people who contribute time and skills to the PrestaShop project, we’re launching a series of interviews with contributors of all ranges. This week, meet Roberto Calisto!

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

Hello, my name is Roberto Calisto. I’m a 44 young man, married and father of two daughters. I am a Portuguese who take a lot of pride in the history of his little country and language. A language that is, for those who do not know, “only” the sixth most talked in the world.

I have made some academic study in philosophy and theology that opened my horizons to the complexity of the world and the humankind. I love travelling, photography also. I am passionate about history and really enjoy discovering new places and cultures.

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

Since about five years. I have been managing a PrestaShop store (Sapataria Rosita) and, since the beginning, I can see expressions are still missing translation in my language. And because I value the Portuguese, it did not make sense for me to have this language not yet completely translated. So when I was asked to help in this effort to finish the translation, I was very happy. I finished translating the last strings into Portuguese this month, it was a very good feeling: the honor to put “the cherry on the top of the cake”. Of course, I am aware that the result of the Portuguese being all translated was the joint effort of many other people.

What really motivates me is trying to do better every day, to make this daily effort in order to surpass myself. It sounds kind of stupid but I think this simple “translation job” has everything to do with the rest of our lives. Although it is difficult, I think it is possible to build a better future for humanity, and I like to think that, in history, I will be part of this imaginary list of unknown people who contributed a bit for that.

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

My advice is: do not give up. Remember you are not alone on this path. Unity is strength and your little contributions will make a great difference in the future. You are not translating; you are in fact contributing to a better future.

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

I have learned that when we “pull” for each other, we help one another and are happier. Because we got achievements that, alone, would be practically impossible for us.

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

Contributing to PrestaShop is not only about the code, it’s also about taking part in the PrestaShop translation project! This report tells you how the translations of the software evolved in January.

Project news

A more international translation

I must admit, it is quite stunning to see how the Crowdin PrestaShop project is growing. Each monthly report highlights bigger numbers than the previous one, we are now talking about hundreds of thousands of words translated, it has nothing to do with the ten thousands we used to get when I arrive. And this is the amazing part of dealing with such a large and dedicated community. Because every merchant can help and then enjoy the benefits of this massive involvement in completing the translation rates. After the interview of Roberto Calisto, who helps a lot with the Portuguese, here is another post about the translation of the software and what has happened lately.

A few stats

• 119 members were active on the project this month.
• A total of 274,918 words have been translated and 95,614 validated.
• All this in 19 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 January 2018.

Top 10 translators in January:

Top 10 proofreaders in January:

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

For its part, PrestaShop 1.7.3 was fully available in 22 languages!

Languages with the best evolution

In comparison with December 2017, the following languages had the best progress thanks to the translation community:

• Finnish (+72% to reach 74% translated in 1.7)
• Latvian (+43% to reach 69% translated in 1.7)
• Macedonian (+38% to reach 99% 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!

The list has quite evolved over the last few months, meaning that a lot of proofreading took place. It’s great!

At the end of January 2018, some languages would still benefit from some proofreading:

• Finnish (65% translated vs 0% validated in 1.7).
• Chinese Simplified (98% vs 46% in 1.7).
• Latvian (66% vs 24% in 1.7).
• Macedonian (100% vs 61% in 1.7).
• Portuguese, Brazil (100% vs 78% 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. 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!

PrestaShop 1.6.1.18 is now available. This maintenance release has seen 25 pull requests merged since version 1.6.1.17.

Continuing on our promise to support 1.6 with patch releases until October 2018, we are happy to deliver this new maintenance version. Please do upgrade to this latest and greatest version of PrestaShop 1.6!

Download 1.6.1.18 now!

As the version number indicates (as per our SemVer-like versioning), this is the 18th patch release for PrestaShop 1.6.1.0.

As usual, if you are currently running promotions leading to high traffic on your website, we recommend that you wait for the promotion to end before attempting any upgrade and technical change to your store.

We hope you enjoy this new release!

The changes

For a full list of changes, see the list of pull requests merged into the 1.6.1.x branch in this milestone

Here are some of the most notable changes that this version brings:

• Hide the password in the confirmation email
• Fix Stock cover report stock out calculation
• Fix stock available after add product in order
• Fix the update product web service
• Fix the blank page when no currency defined in the shop
• Fix the sorting problem with a descending order in the products filtering page
• Fix AdminController’s processDeleteImage() redirect after URL
• Update AdminModulesController.php
• … and more again!

The PrestaShop 1.6.1.18 changelog is available.

Because version 1.6.1.18 is a “patch” update to the 1.6.1.x branch, upgrading from that branch will be as smooth as silk for everyone: features will work better, and modules & themes which worked fine on 1.6.1.0 will work just as well with 1.6.1.17.

This release had 18 contributors, both from PrestaShop and from the community at large.

• @123monsite-regis
• @axometeam
• @Azouz-Jribi
• @Casper-O
• @ColonelMoutarde
• @eternoendless
• @gonssal
• @GuillaumeGBzh
• @hibatallahAouadni
• @marksull
• @matrixino
• @Matt75
• @mcdado
• @MounirBoukhris
• @okom3pom
• @prestamodule
• @RubenMartins
• @vschoener

A huge “thank you!” to each of the 14 outside contributors, who gave their time and knowledge for the benefit of the whole PrestaShop community! You too can contribute to the next version!

Let’s go, upgrade your store(s)! Upgrading from 1.6.1.x is completely safe; upgrading from a standard 1.6.0.x version should work just as well. Those upgrading from version 1.5, 1.4 or even 1.3 should take their time and pay attention to their modules, their theme and their custom modifications!

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 29th of January to Sunday 04th of February 2018.

General messages

… and it is here! Version 1.6.1.18 has arrived, standing ovation! We know you’ve been waiting quite some time for it, thanks for your patience. It contains more than twenty bug fixes, see the list here. Note that the 1.6 won’t be maintained after October 2018.

Also, the PrestaShop’s developer documentation is now online - it just needs to be completed! All the technical aspects of PrestaShop will be gathered here so that theme, module or core developers can use it whenever they need.

One more word. Last week was translation focused, first with the interview of Roberto Calisto, who has been a great help on the Crowdin Portuguese project, then with the monthly report. It throws very flattering light on the work accomplished so far because it is pure progress and involvement for now. How proud we are to gather such a community around!

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

Core

• #8674: Rename old paths of cache and logs for SF 3, by @quetzacoalt91.
• #8698: CLDR Data layers, by @littlebigdev.
• #8709: CO: OrderDetailsController should use Tools::getRemoteAddr() function instead of instead of $_SERVER[‘REMOTE_ADDR’]. Thank you @infiniweb!
• #8718: Renamed locale and currency data objects (no more use of “bag”), by @littlebigdev.

Back office

• #8604: Migration of page Shop Parameters > General > Maintenance, by @quetzacoalt91.
• #8613: [-] BO : Fixes AdminController’s processDeleteImage() redirect after URL. Thank you @gonssal!
• #8672: Move submit button to the right in sf forms, by @quetzacoalt91.

Installer

• #8668: IN: Allow to setup the shop with SSL by default using CLI installer. Thank you @devyk!

Code changes in the ‘1.7.3.x’ branch (for v1.7.3.0)

Core

• #8713: String to translate for 1.7.3, by @toutantic.
• #8719: Fix missing CLDR supplemental directory. Thank you @alegout!

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

Core

• #8536: Fixed for duplication of product which has both combinations and specific prices. Thank you @matrixino!
• #8682: Fix error 500, result of built-in function in write context. Thank you @vschoener!

Back office

• #8612: Fix AdminController’s processDeleteImage() redirect after URL. Thank you @gonssal!

Front office

• #8686: Fix the blank page when no currency defined in the shop. Thank you @azouz-jribi!

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @alegout, @azouz-jribi, @devyk, @gonssal, @infiniweb, @matrixino and @vschoener!

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 tickets and comments on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

• Contributing code to PrestaShop
• How to write a commit message

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Dear contributors, remember when, about two years ago, we presented you the Integration Fund? We even made an amazing video where we talk about this no less amazing Integration Fund. Well, we are still here and running, and for all this we would like to thank you.

Now, some of you may be wondering: “Integration Fund? Never heard of it!”. So if you’ve missed the previous articles, here is where you should go:

Integration Fund - Oct.2015
Integration Fund - Oct.2016

Feeling lazy? Don’t want to go through those old articles? We’ve got you covered, here’s a little reminder of what it is all about:

The Integration Fund is your chance to make your local ecommerce community flourish and to do something meaningful for your local emerchants while earning money.

It was created in June 2015 with the goal of developing our local offer of modules available on our platform Addons to answer the specific needs of numerous merchants all over the world.

The Integration Fund helps local developers create local modules by providing them funding.

In other words, if you have an idea of module that corresponds to a local need in your country of expertise, we are interested!

And you know what’s even better? The funded modules also benefit from additional visibility and have the “local recommended module” badge.

You have already done a lot!

And your local PrestaShop community still needs you!



There still are a lot of countries without the local modules available for the merchants to develop their stores.

In our TOP 40 of countries per number of stores for example, 18 of them are missing the local Shipping, Marketplace integration and Payment modules.

This represents a total of 45 000 stores that cannot operate to their full capacity, and that’s as many potential clients for you!

And think about the other countries too! Here are in orange all the countries missing specific modules.

So what are you waiting for? You have an idea of module for your country? Whether you have already worked with the Fund or not doesn’t matter. Start an application to the Integration Fund now!

And there’s more: In order for you to know all the best tips and information regarding ecommerce and what’s to come, we are launching a new column here in the devblog. It will focus on different regions of the world and will present you with the opportunities they represent.

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 05th of January to Sunday 11th of February 2018.

General messages

Hi folks! Since version 1.6.1.18 is released, we’ve spent last week focusing on a few things to have it work perfectly. Like the 1-Click Upgrade module which we’re now improving in order to have it using less memory and providing better error messages.

Also, we’ve build the release candidate of version 1.7.3 last Friday, all is now set for the final act, performed by our great QA team! As soon as they approve it, be sure that Build will spread the word. ;-)

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

Core

• #8722: CLDR Locale Cache data layer, by @littlebigdev.

Code changes in the ‘1.7.3.x’ branch (for v1.7.3.0)

Back office

• #8737: Fixed combination images selection, by @littlebigdev.

Front office

• #8739: Demo products, by @toutantic.

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 tickets and comments on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

• Contributing code to PrestaShop
• How to write a commit message

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!