This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 30th of November to Sunday 6th of December 2020.

Core Weekly banner

General messages

Dear developers,

In case you did not see it, PrestaShop 1.7.7.0 was released last week!

Note that if you plan on upgrading your shop to 1.7.7 and your current version is below 1.7.6 you need the latest version (v4.11.0) of the autoupgrade module.

As usual, it is recommended to be careful before starting to update your website to the latest version:

  • Backup your database and your files
  • Test the update on a testing or pre production server
  • If everything is fine, then update on the production environment

Following the early adoption of PrestaShop 1.7.7, some bug reports have been submitted about upgrade issues. The maintainer and QA team are all hands on deck exploring and fixing these issues.

If you notice issues with PrestaShop 1.7.7.0, you can report it on GitHub and go even further by submitting a pull request to help fix it!

Releases

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

Code changes in the ‘develop’ branch

Core

Back office

Front office

Installer

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Back office

  • #22191: Validate currency localized names, by @jolelievre
  • #22189: Trigger input when a predefined message is applied, by @Progi1984
  • #22101: Fix product selections when creating/updating tags, by @atomiix
  • #22099: Fix employee filter for the Logs page, by @atomiix
  • #22077: Create Order - Fix remove cart rule when amount is not reached, by @sowbiba
  • #22059: Add Payments block refresher - Refresh when product is added or removed from Order, by @sowbiba
  • #22028: Update out of stock mail wording, by @jolelievre
  • #21992: Make customer note TYPE_STRING instead of TYPE_HTML, by @atomiix
  • #21980: Fixed the error message for a combination with a min quantity for sale, by @Progi1984
  • #21568: Fixed in Create Order the update of cart rules when changing adress , by @Progi1984

Front office

Tests

Code changes in modules, themes & tools

Changes in developer documentation

  • #821: Fix typo front controller page, by @matks
  • #820: Add informations about the mail() method not being used anymore, by @atomiix
  • #819: Fix refund code example for Prestashop 1.7.6. Thank you @yannicka
  • #816: Document Autoupgrade module CLI and channels, by @matks
  • #772: More informations about migrating from 1.6. Thank you @kpodemski

Faceted search module

PrestaShop contributors website

OnBoarding module

Quality Assurance module

Auto Upgrade module

Product Comments module

Theme customization module

Cross-selling module

Shopping cart module

Docker images

Customer reassurance block module

Customer data privacy block module

Catalog statistics module

  • #104: Add another template for displayLeft/Right column hook, by @NeOMakinG

Google Analytics module

  • #66: Add tracking of cancelled orders. Thank you @Hlavtox

Performance project

Where to start contributing?

What about adding tracking number informations on Order Page? This is an idea suggested in May, and it is one of our good first issues.

Good first issues are a list of all beginner-friendly improvements and bugs to fix in the project. You can read more about this label on our article about it.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @matks, @atomiix, @Progi1984, @okom3pom, @NeOMakinG, @boubkerbribri, @PierreRambaud, @eternoendless, @matthieu-rolland, @jolelievre, @ksaandev, @zuk3975, @dependabot[bot], @yannicka, @sowbiba, @jeckyl, @Oksydan, @kpodemski, @JevgenijVisockij, @PululuK, @Hlavtox, @djodjo3!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

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

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

Happy contributin’ everyone!