PrestaShop 1.7.3.1 is now available. This maintenance release fixes 17 issues reported on version 1.7.3.x.

Some of the most notable fixes are:

• Data sent to the front end is now filtered (learn more)
• General speed of the Back Office has been greatly improved (up to 3x faster!) #8780
• Improved Product page performance when there’s a high number of product combinations BOOM-2950
• The stock quantity for packs is now correctly calculated BOOM-4361

Download PrestaShop 1.7.3.1 now!

Here is the complete list of changes:

• Back Office:
  • New feature:
    • #8849: Add User club and UserVoice on BO link footer
  • Improvement:
    • #8664: Change employee icon
    • #8500: Make sure shop list in header is scrollable with lot of items
    • #8780: Improve BO speed by removing menu images
    • #8725: Replace Google+ link on BO footer by Youtube link
  • Bug fix:
    • #8925: Stop generating RTL css file for the default theme using SASS
    • #8921: Fixed CDN management in Performance page
    • #8871: Improved rendering of combinations in Product page
    • #8779: Little css override for modal title
    • #8631: Request module zip for upgrade ONLY when the version available is higher
    • #8714: Update loaded details from database on module action
    • #8696: Fix translation issue during language install
    • #8648: Fix modal backdrop not removed when uninstalling a module
    • #8618: Fix type warning in order detail
    • #8525: “No tax” price option is now well saved in admin product page
    • #8476: Fix customer search in new order form
    • #8234: Fixed bug on save specific price priority for specific product
• Front Office:
  • Bug fix:
    • #8873: Fix contactform module issues
    • #8856: Fixed undefined variables when an url is called in ajax
    • #8847: Override advertising module on classic template to fix image width
    • #8845: Fix search bar on header when it moves from hook and improve header structure #2
    • #7775: Resolve incompatibility between canonical redirections, attributes and product route not only containing rewrite
    • #8846: Fix menu width and submenu hover on header
    • #8522: Fixed specific price percentage rounding on front product page
• Core:
  • Improvement:
    • #8867: Rely on the right legacy container if available on modules
    • #8584: Update toCamelCase
    • #8795: Minor improvements during install
  • Bug fix:
    • #8922: Fixed access to Front Office container from modules
    • #8766: Show unit price within a tax in order confirmation e-mail
    • #8607: Fix pack stock issues
    • #8711: Default AJAX Relevance search sort order is wrong
    • #8803: Stop full object exposure on the front end
    • #8708: Debug of Tools::strReplaceFirst that do not correctly compare the return of strpos + PhpDoc
    • #8498: Fixed bug on reorder with free gift in the cart
    • #8543: Layout broken by cache clear
    • #8669: Make sure all adresses are reset on cart
    • #8462: Fix empty module return on actionEmailSendBefore breaks all email send
    • #8277: CustomerAddressFormatter states were queried without the status (active) check causing disabling states in BO useless
• Installer:
  • Improvement:
    • #8860: Make the dezipper great again
    • #8806: Sample products in FA
  • Bug fix:
    • #8913: Fix issue with pack in fixtures (installer)
    • #8891: Fix dezipper redirect
    • #8858: Include docs when creating zip build
• Tests:
  • New feature:
    • #8812: Delete product
    • #8829: Add script for screenshot display on Travis
  • Improvement:
    • #8881: Check the pagination of product in the Front Office
    • #8898: Check generated combinations table
    • #8903: Add some fixes to the script
    • #8813: Check the product discount in the Front Office
    • #8805: Reset module Welcome if the RESUME button does not exist
    • #8878: Check the appearance of tinymce field on the product page
    • #8854: Check the change of the default combination from the edition page
    • #8819: Fix sort product script
    • #8810: Check the total price in the shopping cart
    • #8815: Re-enable functional tests
  • Bug fix:
    • #8842: Fixed Travis build (update Chrome browser version)
    • #8746: Make file copy on ModuleSelfConfiguration mockable

Contributors to this patch version, from both the Core team and the community at large: 123monsite-regis, Alban L, Antonino Di Bella, Aurélien Pelletier, Bastien Bieri, Cristiano Verardi, Daniel, fatmaBouchekoua, fouratachour, hadrich-hatem, Hitasukha, Krystian Podemski, Maxime Morel-Bailly, MDWeb, Mehdi, Mehrshad, Mickaël Andrieu, neoteknic, Pablo Borowicz, Sarah Lorenzini, sbordun, Symeon, Thomas LEVIANDIER, Thomas Nabord, Wouter Verweirder, Yuri Blanc. Thank you!

Since version 1.7.3.1 is a “patch” update to version 1.7.3.1, upgrading from any 1.7.3 version will be easy: features will work better, and modules & themes which worked fine on 1.7.3.0 will work just as well with 1.7.3.1.
Upgrades from a standard 1.7.x version should work just as well, and those upgrading from older versions (1.6, 1.5, 1.4 or even older) should take their time and pay attention to their modules, their theme and their custom modifications!

As you are probably already aware, in a few weeks (May 25th of this year) the new european law on personal data protection will come into effect.

As an e-commerce software, our goal is to help merchants all around the world to sell their products while complying with legal regulations. This is why it is important for us to provide a tool which will allow your shop to become GDPR compliant.

Many are concerned about this new regulation (especially in view of possible financial penalties) and what PrestaShop plans to do about it. This article aims at providing answers to the most frequent questions we have received and sharing more details about our forthcoming actions.

What is GDPR?

The General Data Protection Regulation (GDPR) which will come into effect on May 25th aims at unifying regulations related to data privacy policies in the European Union. This text reinforces people’s rights and imposes a new accountability logic on entities involved by requiring them to take the necessary, appropriate measures to ensure a suitable level of security when processing personal data.

GDPR is intended to apply to all processing of personal data, whether automated or manual. Processing of data is defined as an operation or set of operations carried out and applied to personal data or data sets (e.g. Collection, storage, modification, extraction, viewing, use, communication, destruction, etc.).

Personal data comprises all information relating to a natural person and enabling that person to be directly or indirectly identified (E.g. full name, email address, IP address, telephone number, location data, consumer habits, etc.).

The main requirements of this law include:

• For the merchants’ customers
  • The right to access their personal data;
  • The right to data portability;
  • The right to obtain rectification and/or erasure of their personal data;
  • The right to give and withdraw consent.
• For the merchants
  • The obligation to keep a record of processing activities (especially for access, consent and erasure).

For more information, you can read our GDPR white paper here.

Who is concerned?

Given the extent of these concepts and your e-commerce business, it is highly likely that you process personal data. Furthermore, the GDPR affects not only every european companies, but also companies located outside of Europe which collect european citizens’ personal data. Needless to say that no merchant can avoid it and store compliance upgrade is not an option.

Modules which collect and stock personal data are also affected as they must be updated to be GDPR compliant, so module developers, this applies for you too!

What is PrestaShop doing to help you comply with GDPR?

In addition to the work being done to ensure our own compliance, we are currently developing new features to help both merchants and module developers comply with the main regulation’s requirements listed above.

More precisely, a specific GDPR module will bring those new features, available for 1.5, 1.6 and 1.7 versions. It should have no impact on the core software and should be compatible with most themes (custom ones included).

Our objective for this module is to handle customers’ personal data collected by the PrestaShop software, native modules and also community modules installed on PrestaShop stores. As a module developer, it will require some work on your side, but our module will bring the necessary tools to make updates easier :)

This module will provide new features for both store merchants and their customers and tools for modules’ developers to help them update their module for GDPR.

As a community developer

The GDPR module will provide:

• new hooks that will enable you to automatically add a new checkbox and a specific text on the front-office of your module (if needed);
• a new hook to select and display the personal data being collected by your module.

More information will be provided in a few days!

As a e-commerce merchant

PrestaShop’s official GDPR Module will allow merchants to:

1. Make it easier for their customers to give their consent by adding a consent confirmation checkbox to different forms of your store (account creation, newsletter subscription, etc.). You will be able to customize the consent request message for each checkbox and refer to the CMS page of your choice to give more information to your customers.
2. Easily manage your customers’ requests related to their personal data erasure and modification. If your customer requests to delete his account, you will be able to:
   • Download all of his invoices in one click (if he has any);
   • Delete his customer account and his personal data in one click;
   • If he has made one or several orders on your website in the past, they will be automatically transferred to a GDPR anonymous account. This will enable you to keep exact order results, reportings and accountability while deleting your customers’ personal data.
3. Keep track of the effective exercise of their right to access and manage their consent actions (obtainment and withdrawal) regarding marketing emails (newsletter).

As a customer

Eventually, the module will also allow customers to:

1. Manage access their personal data, as well as the portability of it (through a automatic download of a csv file including all their personal data collected on the website) – directly via their customer account.
2. Contact you through your contact form for erasure / modification purposes.

Our Official GDPR module - currently being developed by our team due for release at the beginning of May will be:

• Provided for free for all 1.7 versions
• Available as a paid plugin on the Addons PrestaShop marketplace for 1.5 and 1.6 versions.

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

General messages

Developers, we hear you! The hot topic at the moment is of course the RGPD and how to handle it with PrestaShop. Please take the time to read our article on the topic, published yesterday. And, of course, we are working on more content about it, including some examples.

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

Back office

• #8523: Migrate Logs page to Symfony, by @mickaelandrieu.
• #8637: Update back-office menu style, by @alegout.
• #8700: Admin permission detection of Role classe name. Thank you @123monsite-regis!
• #8757: Prevent using “¤” and “|” as customer name. Thank you @PierreJoube!
• #8814: Module tab new subtree, by @Quetzacoalt91.
• #8836: Replace Open Sans font with Vazir font for Farsi (BO default theme). Thank you @mehrshadz!
• #8837: Replace Open Sans font with Vazir font for Farsi (BO new theme). Thank you @mehrshadz!
• #8896: Optimize breadcrumb computation performances, by @jocel1.
• #8909: Allow autoloading in modules for services use in BO, by @mickaelandrieu.
• #8920: Migrate Shop Parameters -> Customer Settings. Thank you @sarjon!
• #8944: Hide Logs page, by @mickaelandrieu.

Core

• #8883: Migrate ShopParameters->General page. Thank you @rokaszygmantas!
• #8888: New Locale integration tests, by @LittleBigDev.
• #8929: Merge 1.7.3.1 into develop, by @eternoendless.

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

Back office

• #8762: Specific price created for a cart is displayed in the front end as the product price. Thank you @roja45!
• #8843: Minor install improvements, by @eternoendless.

Core

• #8679: Catch Throwable errors on CLI install and check Theme instance in context, by @Quetzacoalt91.

Front Office

• #8834: Adds missing Persian translations for data and samples. Thank you @mehrshadz!
• #8931: Out of stock message display only if customer can order the product, by @mickaelandrieu.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @123monsite-regis, @mehrshadz, @PierreJoube, @roja45, @rokaszygmantas, @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!

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

General messages

Last week, Pablo and many colleagues attended the PrestaShop Day in Madrid. More than 1,000 merchants, agencies, freelances and other enthusiasts gathered in La Nave conference center. We do hope you enjoyed it as much as we did, it was great, thanks! If you are French, don’t forget to register for PrestaShop Day Paris in June: this will be a great opportunity to learn what’s new about PrestaShop and discuss with the community. If you are in Lyon, there is a local event the 15th of May: Dejital Day. I will be there and I will enjoy meeting some of you in real life.

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

Back office

• #8918: Add unlimited timeout to dropzone configuration. Thank you @PrestaMagician!

Core

• #8600: Fix fatal on array_merge if query in addMissingProductFields returns no result, by @jocel1.
• #8882: Migrate import page. Thank you @sarjon!
• #8942: Tell if a currency is installed, get a list of installed currencies, by @LittleBigDev.
• #8960: Fixed undefined class constant. Thank you @GuillaumeKadolis!
• #8962: Properly handle set of the PK value in the EntityMapper, by @jocel1.

Test

• #8950: Fix regular tests, by @fatmaBouchekoua.
• #8961: Add some missing elements ids, by @fatmaBouchekoua.

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

Back office

• #8517: Fixed bug when using 2 swap in 1 form. Thank you @AliShareei!
• #8948: Fixed update of combinations, by @mickaelandrieu.

Core

• #8850: Fix profile permission array construction. Thank you @loicsapone!
• #8965: Fix theme install with prestatrust modules. Thank you @marionf!

Front Office

• #8940: Check product availability in order step, by @tomlev.
• #8946: Fix button show password height on Safari, by @eternoendless.
• #8951: fix error display on cart quantity edition, by @tomlev.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @AliShareei, @GuillaumeKadolis, @loicsapone, @PrestaMagician, @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!

You are a developer, you love PrestaShop and are passionate about open source? Maybe you are even already contributor to our project? Then what are you waiting for, let’s work together!

We are looking for people focused on producing quality code, meaning it should be readable, maintainable, tested and documented.

As Prestashop is an open source project, you be responsible for:

• Reviewing your colleagues or contributors code;
• Giving advice and providing constructive criticism;
• Participating in many discussions, whether on GitHub, Slack or Gitter;
• Fixing bugs without introducing new ones;

In order to maintain its technical leadership PrestaShop makes sure its developers devote time to training and sharing their knowledge with their colleagues.

Front-end developer:

• As a front-end developer, you will be responsible for intervening on PrestaShop’s backoffice user interface and on PrestaShop shops default themes.
• Vue.js is your favorite front-end framework!
• Read full description and apply

Back-end developer:

• As a back-end developer you will intervene on PHP/Symfony code and interactions with the relational database.
• Read full description and apply

You can find all our open positions and more details on PrestaShop’s Welcome to the Jungle page. Please feel free to share with your mates.

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

General messages

Dear contributors, many Pull Requests from the community have been merged last week and that’s great! In order to simplify the contributing experience, I would like to have your feedback on these questions:

• What are your current difficulties to submit a Pull Request on PrestaShop Core repository?
• What should we improve?
• What documentation is missing?
• Do you have other ideas?

Please, feel free to answer and discuss via the forum on this dedicated thread :-)

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

Back office

• #8830: Fix uninitialized $moreStepLabels in AdminImportController. Thank you @popstas!
• #8895: Allow override of every modern template, by @mickaelandrieu.
• #8908: Refactored Form Handling management, by @mickaelandrieu.
• #8916: Add tips in the back office to improve user experience. Thank you @sLorenzini!
• #8927: Remove default theme schemes (no longer used), by @eternoendless.
• #8933: [BO] Fix bug on saving store hours. Thank you @SebBareyre!
• #8945: Return default values when api is unavailable, by @Quetzacoalt91.
• #8947: Hooks for recommended modules & themes, by @Quetzacoalt91.
• #8979: Move administration page to proper location. Thank you @sarjon!

Front Office

• #8833: Hide empty list if all variations are out of stock. Thank you @PhpMadman!

Core

• #8831: Better handling of invalid modules from Addons API, by @mickaelandrieu.
• #8935: CLDR : Replace legacy number and price formatting, by @LittleBigDev.
• #8954: Allowed robots access to assets requierd to be mobile-friendly. Thank you @PhpMadman!
• #8959: Able to pass hook as a parameter. Thank you @DonNhh!
• #8970: Improved readability. Thank you @michaelKaefer!
• #8976: Set cache driver in container instead of env var CACHE_DRIVER, by @Quetzacoalt91.
• #8980: Remove deprecated message for DataCollectorInterface. Thank you @PierreRambaud!
• #8982: Merge 1.7.3.x into develop, by @eternoendless.

Tests

• #8939: Adaptation of the test for the version on the developed branch. Thank you @fouratachour!
• #8983: Parallelize builds. Thank you @PierreRambaud!

Install

• #8981: Set explicit version of MySQL in docker-compose.yml, by @Quetzacoalt91.

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

Back office

• #8752: Check product availability before validating orders, by @alegout.
• #8975: Fix broken “you must first create a new language” link in BO Translations, by @eternoendless.

Core

• #8973: Fixed undefined class constant, by @eternoendless.

Install

• #8949: Remove addition of . folder in release archives, by @Quetzacoalt91.

Localization Pack

• #8832: Update Iran tax rate. Thank you @mehrshadz!

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @DonNhh, @fouratachour, @mehrshadz, @michaelKaefer, @PhpMadman, @popstas, @sarjon, @SebBareyre, @sLorenzini !

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!

PrestaShop 1.7.3.2 is now available. This maintenance release fixes 17 issues reported on version 1.7.3.x.

Some of the most notable fixes are:

• Updating combinations wasn’t working with PHP < 7.1
• Installing a Theme with PrestaTrust modules was failing
• Various issues with product stock availability
• The “Install_prestashop.html” file was not visible on some systems

Download PrestaShop 1.7.3.2 now!

Here is the complete list of changes:

• Back Office:
  • Improvement:
    • #8834: Adds missing Persian translations for data and samples
  • Bug fix:
    • #8752: Check product availability before validating orders
    • #8975: Fix broken “you must first create a new language” link in BO Translations
    • #8965: Fix theme install with prestatrust modules
    • #8517: Fixed bug when using 2 swap in 1 form
    • #8948: Fixed update of combinations
    • #8762: Specific price created for a cart is displayed in the front end as the product price
• Front Office:
  • Improvement:
    • #8835: Replace Noto Sans font with Vazir font for Farsi in Classic theme
  • Bug fix:
    • #9005: Fix cannot order oos product even if it’s allowed
    • #8951: Fix error display on cart quantity edition
    • #8946: Fix button show password height on Safari
    • #8940: Check product availability in order step
    • #8931: Out of stock message display only if customer can order the product
• Core:
  • Bug fix:
    • #8973: Fixed undefined class constant
    • #8850: Fix profile permission array construction
    • #8679: Catch Throwable errors on CLI install and check Theme instance in context
• Installer:
  • Improvement:
    • #8843: Minor install improvements
  • Bug fix:
    • #8949: Remove addition of . folder in release archives
• Localization:
  • Improvement:
    • #8832: Update Iran tax rate

Contributors to this patch version, from both the Core team and the community at large: Alban L, AliShareei, GuillaumeKadolis, Loïc Sapone, Marion François, Mehrshad, Mickaël Andrieu, nigel, Nigel Helliwell, Pablo Borowicz, Sarah Lorenzini, Thomas LEVIANDIER, Thomas Nabord. Thank you! Six of you contributed for the very first time, warm welcome :-)

Since version 1.7.3.2 is a “patch” update to version 1.7.3.1, upgrading from any 1.7.3 version will be easy: features will work better, and modules & themes which worked fine on 1.7.3.x will work just as well with 1.7.3.2.
Upgrades from a standard 1.7.x version should work just as well, and those upgrading from older versions (1.6, 1.5, 1.4 or even older) should take their time and pay attention to their modules, their theme and their custom modifications!

Everybody must already know, there are a few steps to follow in order to make your module compliant with the General Data Protection Regulation (GDPR)

1. Add a consent confirmation checkbox if the module collects personal data
2. Allow users to ask for total removal of their personal data
3. Allow users to ask for a comprehensive export of their personal data owned by the site

The Official GDPR Compliance Module by PrestaShop will be available soon, and it provides you with 4 new hooks to help you meet these requirements.

Hook 1: Register your module into the GDPR module

$this->registerHook('registerGDPRConsent')

The first step is to register your module into our Official GDPR Compliance Module with the hooks. We recommend to do it during its install process:

/**
 * Executed at the install of your module
 *
 * @return void
 */publicfunctioninstall(){// register hook used by the module
if(parent::install()&&$this->registerHook('registerGDPRConsent')&&$this->registerHook('actionDeleteGDPRCustomer’)
        && $this->registerHook('actionExportGDPRData')
)
 {
        return true;
    } else { // if something wrong during installation return false
        $this->_errors[] = $this->l('Therewasanerrorduringtheinstallation.PleasecontactusthroughAddonswebsite.');returnfalse;}}

This operation is very simple but mandatory, so that the Official GDPR Compliance Module registers the list of modules it handles.

Hook 2: Delete customer personal data

$this->registerHook('actionDeleteGDPRCustomer’)

When a customer asks for his personal data to be removed from the store, the store owner can either accept or decline the request (for legal obligation requirement for instance). If the store owner accepts the customer’s request, all personal data collected by PrestaShop can be removed (with the “Delete” feature available in the module).

Furthermore, since nobody else knows your module better than you, we also allow you to hook your module to the data removal process in order to delete the personal data collected by your module.

This hook allows to delete the customer’s data and return true if everything went well. Obviously, the hook must return an array or a string encoded to json (json_encode function) of errors if not:

publicfunctionhookActionDeleteGDPRCustomer($customer){if(!empty($customer['email'])&&Validate::isEmail($customer['email'])){$sql="DELETE FROM "._DB_PREFIX_."popnewsletter_subcribers WHERE email = '".pSQL($customer['email'])."'";if(Db::getInstance()->execute($sql)){returnjson_encode(true);}returnjson_encode($this->l('Newsletter Popup : Unable to delete customer using email.'));}}

The Official GDPR Compliance Module triggers the deletion hook with the customer (array) as parameter.

HOOK 3: Export personal data

$this->registerHook('actionExportGDPRData')

Lastly, if a customer asks for an export of his personal data, this hook allows to select all his data and return them in a csv or pdf format. It works the same way as the deletion hook, but instead of removing data (delete from…) you need to return data to export in json:

publicfunctionhookActionExportGDPRData($customer){if(!Tools::isEmpty($customer['email'])&&Validate::isEmail($customer['email'])){$sql="SELECT * FROM "._DB_PREFIX_."popnewsletter_subcribers WHERE email = '".pSQL($customer['email'])."'";if($res=Db::getInstance()->ExecuteS($sql)){returnjson_encode($res);}returnjson_encode($this->l('Newsletter Popup : Unable to export customer using email.'));}}

If any error occurs, it returns the error. As for the hook 3, it must return an array or a string encoded to json (json_encode function) of errors.

Hook 4: Display user consent checkboxes

{hookh='displayGDPRConsent'mod='psgdpr'id_module=$id_module}

The hook must be used inside your module’s template files (.tpls). Calling this hook will simply display a checkbox + a text block. So place it where you need it. However please read the 2 requirements below :

• The hook must be inside a html form (<form></form>)
• You must smarty assign the module’s ID: $this->context->smarty->assign(array('id_module' => $this->id));

<formaction="{$urls.pages.index}#footer"method="post"><divclass="row"><inputclass="btn btn-primary float-xs-right hidden-xs-down"name="submitNewsletter"type="submit"value="{l s='Subscribe' d='Shop.Theme.Actions'}"><divclass="input-wrapper"><inputname="email"type="text"value="{$value}"placeholder="{l s='Your email address' d='Shop.Forms.Labels'}"aria-labelledby="block-newsletter-label"></div></div>
               {hook h='displayGDPRConsent' mod='psgdpr' id_module=$id_module}
           </form>

The Official GDPR Compliance Module provides an interface listing all the registered modules (using the hook 1). For each checkbox, you can define the text in multiple languages.

Good thing is, if the checkbox is not checked, the form cannot be submitted!

Extra information

$customer could be either an array equivalent to the Customer Object or simply an email. Why? Some modules can save personal data that aren’t coming from a regular PrestaShop Customer. In such cases, we provide the user’s email so you can still delete the data.

Once you have submitted your module and declared it is compliant with the law, our validation team:

• Checks the presence of hooks necessary to plug your module to the official GRPD module;
• Checks the hooks integrity, meaning checks that your code does not imply any PrestaShop data, but only data collected by your module.

Support & Questions

Do you have any questions?

• Comment this article to let us know
• If your modules are already on Addons, you can also get support via the Help Center.
• If you are developing custom modules that are not available on Addons, you can get support on the Forum.

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 30th of April to Sunday 6th of May 2018.

General messages

Did you notice? We are over 9,000 Pull Requests on GitHub, what an achievement! Congratulation to everyone who has created PRs in the history of the PrestaShop project. We really hope more and more contributors will join us… next step, 10.000? ;-)

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

Back office

• #8932: Fix display error on module selection list. Thank you @SebBareyre!
• #8995: Display the notification count on the proper tab, by @Quetzacoalt91.
• #9004: Fixed search on manufacturer’s name, by @mickaelandrieu.
• #9008: Use getBoolean() instead of get() when configuration is bool in Product Settings page. Thank you @sarjon!
• #9024: Merge 1.7.3.2 into develop, by @eternoendless.

Front office

• #8972: FO / Discount / Wrong variable use in loop for mobile. Thank you @timactive!
• #9016: Corrected email subscription form input type. Thank you @rdy4ever!
• #9017: Fix wrong parameter verification, allowing redirection to arbitrary URL, by @eternoendless.
• #9027: FO: Fixes wrong schema of “InStock” for Out of stock products. Thank you @rdy4ever!

Core

• #8767: Show prices within a tax if it’s needed. Thank you @kpodemski!
• #8985: Fixed order gets wrong status when ordered all qty of the product.. Thank you @LedCloud!
• #8996: New doc block for method, reduced code of method. Thank you @michaelKaefer!
• #8998: Create missing subfolders in folder override/classes. Thank you @dariusakafest!
• #9010: Check if template_vars if an array before merge in OrderHistory::sendEmail() . Thank you @serhatdurum!
• #9018: Add copyright information to the license., by @ttoine.
• #9020: Update to right name, markdown with links and more, by @ttoine.
• #9021: Create LICENCE.md, by @ttoine.
• #9022: Make bin/console executable, by @eternoendless.
• #9029: Revert CLDR integration, by @eternoendless.

Tests

• #8994: Update the Onboarding scenario, by @fatmaBouchekoua.
• #9030: Fix travis reporting build as succeeded when it fails. Thank you @PierreRambaud!
• #9032: Fix regular tests, by @fatmaBouchekoua.

Localization pack

• #8997: fix TVA rate. Thank you @atefBB!

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

Front Office

• #8835: Replace Noto Sans font with Vazir font for Farsi in Classic theme. Thank you @mehrshadz!
• #9005: Fix cannot order oos product even if it’s allowed, by @tomlev.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @atefBB, @dariusakafest, @LedCloud, @kpodemski, @mehrshadz, @michaelKaefer, @rdy4ever, @sarjon, @SebBareyre, @serhatdurum, @timactive !

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!

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 April.

Project news

Almost 30

We are slowly approaching the 30 fully completed projects. What an amazing job doing so far, be proud because you deserve it! Indeed, this daily joint effort allows us to make the community wider and closer to each need. We definitely passed the 25 available languages, for both 1.6 and 1.7 versions, so next step is naturally to reach 30. We are already the most international solution, compared to other softwares, and will stay as - business everywhere, without language barrier!

A few stats

• 52 members were active on the project this month.
• A total of 32,424 words have been translated and 15,019 validated.
• All this in 12 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 2018.

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

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

Languages with the best evolution

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

• Hindi (+11% to reach 23% approved in 1.7)
• Galician (+9% to reach 95% translated in 1.7)
• Korean (+8% to reach 62% 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 2018, some languages would still benefit from some proofreading:

• Chinese Simplified (100% translated vs 43% validated in 1.7).
• Filipino (80% vs 27% in 1.7).
• Korean (62% vs 27% in 1.7).
• Galician (95% vs 61% in 1.7).
• Spanish, Venezuela (62% vs 32% 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!

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

General messages

Core weekly 19

Dear all, the long-awaited GDPR module is released for PrestaShop 1.6.x and 1.7.x. Below is a brief summary of what is available and where to find it:

• If you run a 1.7 store, go directly in the back office of your shop, you can install it for free; please note that it will be integrated into the core with the 1.7.4.x version of PrestaShop
• If you run a *1.6** store, the module is available on the PrestaShop Addons marketplace with support, and it is visible in the back office of your shop
• If you run a 1.5 store, the module will be available soon on the Addons marketplace

A lot of feedback from the community has already been taken into account, thank you very much to everyone helping us to improve this very important feature.

The most notable change for the Core Weekly is that from now, the ‘develop’ branch regards the 1.7.5.x. So yes, it means that a 1.7.4.x branch has been created on the main repository.

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

Core

• #9035: Add package-lock.json file, by PierreRambaud.
• #9058: Removed call to Tools::array_replace(). Thank you michaelKaefer!
• #9059: Refactored Tools::switchLanguage function. Thank you michaelKaefer!
• #9061: Removed redundant checks and added docblock in Tools::getIsset function. Thank you michaelKaefer!

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

Back Office

• #8838: Fix tinymce RTL text direction. Thank you Danoosh!
• #8938: Display tabs on the module page with the generic method, by Quetzacoalt91.
• #9023: Avoid infinite redirects if unhandled exception during BO authentication, by eternoendless.
• #9040: Fix Smarty.class.php class not found, by PierreRambaud.

Front Office

• #8774: Ajax calls for product availability status in front refactored, by alegout.

Core

• #9048: Removed if statment, by mickaelandrieu.

Other

• #9038: Update pull request template, by eternoendless.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: Danoosh, michaelKaefer!

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 14th of May to Sunday 20th of May 2018.

General messages

Dear all, we would like to thank you for the huge amount of feedback about the GDPR module. Lots of comments on our blog posts, tweets, support tickets, etc. So much we can’t list everything here! In the open source world, we often say that a bug report is like a love letter. If so, we’re glad to see all this love for the PrestaShop project ;-)

I would like to assure you that our teams are doing their best to take everything into account and to improve the GDPR module consequently. In other words, you can expect some updates this week…

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

Core

• #9007: Migrate Shop parameters -> Order settings page. Thank you @rokaszygmantas
• #9056: Deprecate polyfill function array_replace(). Thank you @michaelKaefer
• #9062: Improved errors management if Dev mode is enabled. Thank you @michaelKaefer
• #9065: Dispatcher: Get request URI from Symfony’s Request. Thank you @michaelKaefer
• #9068: Refactor Cart::checkQuantities(). Thank you @michaelKaefer
• #9071: Refactor AbstractCartTest. Thank you @michaelKaefer
• #9072: Fixed typo bug. Thank you @michaelKaefer

Front Office

• #9069: fix gift wrapping fees, by @tomlev

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

Back Office

• #9044: Fix delivery time labels not displayed, by @PierreRambaud
• #9046: Reduced permission levels for theme edition, by @Quetzacoalt91
• #9051: Bad link in breadcrumbs in symfony pages, by @PierreRambaud
• #9074: Ordering product in BO doesn’t work, by @PierreRambaud
• #9081: Can’t enable maintenance mode, by @PierreRambaud
• #9084: Saved confirmation message isn’t displayed anymore in translation page, by @PierreRambaud
• #9086: fix template on attachment delete, by @tomlev

Front Office

• #9036: fix infinite loop on multiple vouchers, by @tomlev
• #9073: Fix gift wrapping fees added even if not checked, by @tomlev

Core

• #9054: Added missing use statment in AddonsCollection class. Thank you @nenes25
• #9076: Fixed duplicate carts in back office, by @PierreRambaud
• #9079: Added $result (from facet) in hook filterProductSearch. Thank you @Lathanao
• #9091: Update develop with 1.7.4.x changes, by @Quetzacoalt91

Install

• #9052: Fix error populating tables when installing in Greek, by @PierreRambaud

Tests

• #9070: Disable e2e tests related to Addons for 1.7.4.x, by @PierreRambaud

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

Back Office

• #9026: Fixed display error on back office module selection list, by @Quetzacoalt91

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @Lathanao, @michaelKaefer, @nenes25, and @rokaszygmantas!

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!

PrestaShop 1.7.3.3 and 1.6.1.19 are now available. Those maintenance releases fixes specific issues for the GDPR compliance.

Some of the most notable fixes are:

• Add GDPR compliance to native modules
• Fix some diplay errors

Download PrestaShop now!

Here is the complete list of changes for 1.7.3.3

• Back Office:
  • Bug fix:
    • #9026: Fixed display error on back office module selection list
• Front Office:
  • New feature:
    • #9099: Follow-up to: display GDPR consent checkbox in contactform
  • Improvement:
    • #9104: Add compliance to GDPR law for ps_emailsubscription module

Here is the complete list of changes for 1.6.1.19

• Back Office:
  • Bug fix:
    • #8785: Fix directory listing
• Front Office:
  • Improvement:
    • #9103: Add compliance to GDPR law for blocknewsletter, contact form and mail alerts

Contributors to this patch versions, from both the Core team and the community at large: Alban L, Florian Nolte, jGissinger, Mickaël Andrieu, Pablo Borowicz,and Sébastien Bareyre. Thank you! Four of you contributed for the very first time, warm welcome :-)

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

This the same for 1.6.1.19 regarding 1.6.1 version.

Almost all of our merchants have to comply with the law. That’s why we have released the GDPR official module by PrestaShop (1.6 and 1.7 live, 1.5 to be released very soon), helping merchants and contributors to comply with the law.

Do you have a PrestaShop version 1.7 store? The module is already available in your back-office

Introduction

As already explained on our Prestashop.com blog and on build.prestashop.com, the GDPR has and ready to be installed. It is also published on Github in the PrestaShop/psgdpr repository. For more information and help on how to use it, we invite you to consult the 1.7 user documentation.

Do you have a store in PrestaShop version 1.6? We have developed an official GDPR module, compatible with PrestaShop version 1.6. Installing this module on your store just takes a few clicks. See our Official GDPR Compliance by PrestaShop (1.6) module available on the PrestaShop Addons Marketplace. For any questions you may have related to its configuration, we invite you to consult the 1.6 user documentation and contact the Addons team for support.

Core changes

We also have had to update several core features and native modules so that they become compliant with the new law. Indeed, on those forms, a consent checkbox becomes mandatory to be able to send an email and/or a message : Contact form feature Newsletter subscription feature Email alert feature for out-of-stock products

To be able to update those native modules, we have had to modify their TPLs but also the classic theme as it overrides the modules. This is the reason why 2 new PrestaShop versions - dedicated to GDPR compliance are released:

• 1.7.3.3
• 1.6.1.19

We have published a dedicated release note if you need details.

What to do

If you are a theme developer

As a theme developer, you need to update your themes to add the same changes we applied on the native modules and on the classic theme, to be GDPR compliant.

To do so, add the following line in the module TPLs of your theme:

{ifisset($id_module)}{hookh='displayGDPRConsent'id_module=$id_module}{/if}

Just be sure you add it in inside a form.

If you need an example, just check on the PrestaShop Github in Theme folder > classic > modules > ps_emailsubscribtion how the classic theme has been updated to add a consent checkbox below the email field.

If you are a developer or a merchant

To be fully compliant, you need to install the GDPR module and apply updates on your store :

1/ For 1.7 stores

• Update the 3 following native modules : contactform, ps_emailsubscription and ps_emailalerts
• Update your store to the latest version (1.7.3.3) if you use the classic theme or update your custom theme with GDPR changes or add directly in your Theme folder (for each module) the line indicated above.

2/ For 1.6 stores

• Update the 2 following native modules : Blocknewsletter, mailalerts. The contact form is not a module in this version, so its update is directly brought by the GDPR module itself.
• Update your store to the latest version (1.6.1.19) if you use the classic theme or update your custom theme with GDPR changes or add directly in your Theme folder (for each module) the line indicated above.

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

General messages

Last week, a few updates have been done on the core, plus on some native modules. You might also have to update your theme. Guess what: this is still in order to improve the GDPR compliance of your PrestaShop store. You can read the details on Build:

• Update Your Store For GDPR
• Release Of PrestaShop 1.7.3.3 And 1.6.1.19

Now, the most interesting part of this news: if you live in Paris, or if you need a good reason to come in Paris, PrestaShop Day is in 2 weeks. We really hope to meet you there ;-)

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

Core

• #9037: Permit IDE completion with PHP doc. Thank you @MatthieuMota
• #9039: Ajax will never die, by @jocel1
• #9053: Add missing package-lock.json files, by @PierreRambaud
• #9064: Fixed list of activated modules, by @mickaelandrieu
• #9095: Fix translations order settings and remove unused templates. Thank you @rokaszygmantas
• #9096: Clean up service yml files. Thank you @sarjon
• #9098: CO: rename variable $producPropertiesCache (fix typo). Thank you @anegoda1995
• #9122: Add safety returns after ajaxRender calls, by @jocel1

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

Back Office

• #9028: Introduced re-usable authorization system, by @mickaelandrieu
• #9067: Refactor Controller class (minor changes). Thank you @michaelKaefer
• #9077: Update welcome module version, by @PierreRambaud
• #9102: Update BO theme to Bootstrap 4 final, by @eternoendless
• #9106: add a product removal confirmation. Thank you @khouloudbelguith
• #9113: Fix wrong css file on BO login page, by @eternoendless
• #9118: Fix BO login icons, by @eternoendless

Front Office

• #9080: Fix Punycode problem when register, by @PierreRambaud

Core

• #9050: Fix HookConfigurator: Filter certain non-arrays from theme.yml. Thank you @jsshandle
• #9055: The special offers are disappearing suddenly, by @PierreRambaud
• #9109: 1.7.4.x into develop, by @PierreRambaud
• #9115: 1.7.4.x into develop, by @PierreRambaud

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

Front Office

• #9099: Follow-up to: display GDPR consent checkbox in contactform. Thank you @florian-nolte
• #9104: Add compliance to GDPR law for ps_emailsubscription module. Thank you @Joukz

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

Front Office

• #9103: Add compliance to GDPR law for blocknewsletter, contact form and mail alerts. Thank you @Joukz

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @anegoda1995, @florian-nolt, @Joukz, @jsshandle, @khouloudbelguith, @MatthieuMota, @michaelKaefer, @rokaszygmantas, 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!

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 28th of May to Sunday 3rd of June 2018.

General messages

In Paris next week? Please come and meet us at the PrestaShop Day! All the PrestaShop team will be there, among which several developers and the CTO with whom you will be able to exchange on hot topics like 1.7.4 or the 1.6 to 1.7 migration. BTW, If you want an invitation, I have a few left. Ping me on Twitter, I am @ttoine and I will send you a coupon code via direct message. First come, first served.

Last minute news, I will be at Open Expo Europe in Madrid this week to speak about PrestaShop and open source. See you there?

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

Core

• #9121: Make commands from PrestaShop modules available in PrestaShop application, by @mickaelandrieu
• #9136: Use https in Employee not http. Thank you @okom3pom
• #9140: Update composer dependencies, by @mickaelandrieu
• #9143: Fix unknown key route error in customer settings page. Thank you @marionf
• #9146: Merge 1.7.4.x in develop, by @PierreRambaud

Front Office

• #9110: Make checkbox labels clickable on the classic theme. Thank you @rdy4ever

Tests

• #9125: Quantity tests, by @tomlev

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

Back Office

• #9082: Error while searching for a product, by @PierreRambaud
• #9089: Catch module theme installation error, add error message for invalid module, by @Quetzacoalt91
• #9117: Add theme custo, by @eternoendless
• #9143: Fix unknown key route error in customer settings page, by @marionf
• #9149: Error with quota fields, by @PierreRambaud
• #9151: Fix undefined method trans() when loggin on the marketplace from the module page, by @Quetzacoalt91
• #9151: Fix undefined method trans() when loggin on the marketplace from the module page, by @Quetzacoalt91
• #9157: State filter in catalog page doesn’t work, by @PierreRambaud

Front Office

• #9134: Fix undefined index on supplier page in FO, by @marionf

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @okom3pom, @rdy4ever!

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!

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 May.

Project news

1.7.4 is on its way

You were waiting for it and the dream is coming true now: strings of the future minor version have entered the Crowdin catalog, everybody clap your hands! As you might already know, a new folder called 1.7.4 has been created in Crowdin, it contains the current strings and the fresh new ones, attached to the forthcoming 1.7.4 version of the software… that just expect you to be taken care of! So go for it, make your language back in the game by translating or approving the new wording. ;-)

A few stats

• 35 members were active on the project this month.
• A total of 17,392 words have been translated and 11,532 validated.
• All this in 6 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 2018.

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

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

Languages with the best evolution

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

• Chinese Simplified (+15% to reach 58% approved in 1.7)
• Korean (+8% to reach 70% translated in 1.7)
• Estonian (+2% to reach 98% 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 May 2018, some languages would still benefit from some proofreading:

• Filipino (80% translated vs 27% validated in 1.7).
• Chinese Simplified (100% vs 58% in 1.7).
• Korean (70% vs 30% in 1.7).
• Spanish, Venezuela (53% vs 17% in 1.6).
• Galician (95% vs 61% 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!

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

General messages

Great news: we have never been so close to publish the 1.7.4 beta! Among its new features is the refactoring of the Auto Upgrade module, it is one of the key improvements we want to bring with this release. Help our dev team, have a look at it, test it and give us some feedback:

• Documentation is a public Google Doc, therefore it is open to feedback, it will help us improve it
• Download the 4.0.0-beta.1 version of the Auto Upgrade module on GitHub

** Please do not use it on a production website and of course, backup, backup, and backup first.**

To conclude, we hope to see you at the PrestaShop Day this Thursday. There is an “open source corner”, let’s meet and chat there. :-)

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

Core

• #8956: Add customization ID to cart ajax response and updateCart event data. Thank you @unlocomqx
• #9105: Check if key exists before checking the value. Thank you @andypieters
• #9154: Migrate Theme Catalog Page of Design Section. Thank you @michaelKaefer
• #9162: CO: The left and the right parts of assignment are equal. Thank you @lfluvisotto
• #9163: CO: Case mismatch in class/function/method call. Thank you @lfluvisotto

Back Office

• #9139: Migrate Sell > Orders > Delivery Slips, by @PierreRambaud
• #9171: Fixed namespace of Delivery Slips controller, by @mickaelandrieu

Front Office

• #9128: index.php file for controllers/front/listing/. Thank you @Seleda

Tests

• #9127: Buttons in product page, by @fouratachour
• #9147: Navigate between pages in catalog page, by @fatmaBouchekoua

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

Core

• #9156: Fix missing security event listeners registration. Thank you @sarjon
• #9167: Update native module versions, by @eternoendless

Back Office

• #8914: Improve header BO design, by @sLorenzini
• #9133: Regression with DatePicker and checkboxes on stock page (catalogue > stock), by @PierreRambaud
• #9160: Fix 500 while getting order total, by @PierreRambaud
• #9169: Fix product attachment list, by @tomlev

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

Front Office

• #9126: Control if customer is the owner of the selected order in contact form, by @PierreRambaud

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @andypieters, @lfluvisotto, @michaelKaefer, @sarjon, @Seleda, @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 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!

PrestaShop 1.7.4 is available for download. Please read important informations about it.

Done:

• All pull requests have been merged

New features:

• Improved back office design
  • Works better on mobile devices (all pages are accessible on mobile now!)
  • New menu, can be scrolled
  • Improved header (looks the same on legacy and symfon pages)
  • Based on Bootstrap 4 final
• Theme customization
• New pages migrated to symfony
  • Advanced Parameters > Administration
  • Advanced Parameters > Import
  • Shop Parameters > General
  • Shop Parameters > General > Maintenance
  • Shop Parameters > Product Settings
  • Shop Parameters > Customer Settings
• Added support for PHP 7.2
• SEO improvements
  • Add hreflang links for multilang pages #8652
  • Improved header tags in classic theme
• New functional tests (end to end)
• New switch component in symfony pages #8705
• Refactored cart calculation, including automated tests #8411
  • Improvements for developers
  • Improved hook profiler (shows more data about hooks) #8557 and #8910
  • Improved template structure for the BO Product page (easier to override) #8489
  • ObjectModel structure can now be modified by modules #8853
  • Modules can now add tabs in the menu of an existing page #8814
  • Services exposed by modules can now be autoloaded using composer #8909
  • New authorization system for symfony pages #9028
• New hooks
  • displayDahboardToolbarTopMenu #8947
  • displayAdminEndContent #8947
• Greatly improved performance in BO and FO when a lot of categories are used #8896
• New font for Farsi language
• Fixed broken install in Greek #9052

Todo:

• Check possible regression with RTL in BO
• Import MBO and welcome modules
• Create branch 1.7.4 for the starter theme

Known issues:

• Some wordings aren’t translated
• Upgrade 1733 -> 1740 is not working with current version of the Auto Upgrade module, however this is fixed in the upcoming version of this module (please read the last section of this article)
• Wrong link with “Recommended module” on symfony pages
• Theme custo install module is not working as expected
• The “Recommended modules” link in the header is also added by MBO module
• The puffin in the welcome module doesn’t appear
• When B2B mode is enable, the “Outstanding” menu is not displayed

Updated dependencies:

• Symfony 2.8 -> 3.4
• PHP 5.4 -> 5.6
• (BO) Bootstrap 4 beta 2 -> Bootstrap 4 final
• PrestaShop UI Kit 1.0

Details:

• List of merged PRs
• List of Issues

Download

You can download PrestaShop 1.7.4-beta1 on GitHub:

Download PrestaShop 1.7.4.0 beta 1 now!

How to help us to finish the 1.7.4

Your help will be very appreciated to finish the work on PrestaShop 1.7.4. Even if you are not a developer, your feedback has a lot of value.

You can:

• Install it and test it
• Report bugs on the forge
• To submit a bug fix, create a pull request
• If everything is working well, comment this article to tell us, and share on social networks, we also need this feedback ;-)

1-click upgrade module 4.0 beta

We have completely refactored the 1-click upgrade module. It’s better than ever, with automated tests, capability to upgrade your shop from previous versions, and gives out more detailed information in case of failure so we can keep improving it!

In addition, we have published a detailed documentation on how to migrate an existing shop to the latest version of PrestaShop.

The documentation: https://devdocs.prestashop.com/1.7/basics/keeping_up-to-date/

Improvements to the documentation are welcome! Learn how to contribute.

The plugin:

• Download the beta on GitHub: https://github.com/PrestaShop/autoupgrade/releases/tag/v4.0.0-beta.1

PRs are welcome on the GitHub repository

• Report issues on the forge

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

General messages

Dear Community members, did you already try the 1.7.4 beta? Well, you should! You can find all details about how to download it, development status, and of course, install it and test it. Just read this complete 1.7.4 beta article on the devblog.

Then feel free to give your feedback: via the comments of the article, a ticket on the forge or a pull request on GitHub.

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

Core

• #9182: Merge 1.7.4.x in develop, by @PierreRambaud
• #9190: Fixed DataConfigurationInterface PHPDoc, by @mickaelandrieu

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

Core

• #9188: Fix wrong test in left join condition, by @jocel1

Back Office

• #9173: Registered all namespaces in ModuleTemplateLoader class, by @mickaelandrieu
• #9175: Missing requirement message, by @Quetzacoalt91
• #9181: Use CustomerPreferencesFormHandler to handle specific tabs toggling for B2B mode, by @matks
• #9183: restore missing translation keys, by @tomlev
• #9189: Hide disabled level 3 tabs in the BO, by @Quetzacoalt91

Tests

• #9177: Update scripts on 1.7.4.x. Thank you @hadrich-hatem

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

Back Office

• #8724: PHP 7.2 compat - Fix fatal error. Thank you @enumag
• #8821: FIX PHP 7.1 compat in WebserviceOutputBuilder. Thank you @axometeam

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @axometeam, @enumag, @hadrich-hatem!

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!