This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 28th of September to Sunday 4th of October 2020.

Core Weekly banner

General messages

Dear developers,

The past week has been filled with lot of interesting events!

First, PHP 8.0 Release Candidate 1 has been delivered and is available for testing. Obviously, we suggest helping the test of this version as this is the future of PHP.

Secondly, Hacktoberfest has started on the 1st of October. But the very first days of the event have been complicated: the event experimented a huge spam contributions wave. The consequences of this spam are that the rules of Hacktoberfest changed on the 3rd of October: projects now need to opt-in for the event and Pull Requests must be either merged, approved, or labeled ‘hacktoberfest-accepted’ to be accepted as a participation.

The PrestaShop team has decided to opt-in to this event so your (valid) contributions will be acknowledged as participations for this edition of the Hacktoberfest!

Finally, the QA team is still running the test campaign on the Release Candidate 1 build delivered the week before.

Releases

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

Code changes in the ‘develop’ branch

Core

Back office

  • #21277: Fixed call for Windows PrestaShop Components, by @Progi1984
  • #21264: Clean a bit class AdminController. Thank you @ksaandev
  • #21250: Fix left sidebar while onboarding is on, by @NeOMakinG
  • #21223: Introduce namespaces in adapter - Update, Validate, Repository. Move recent services.. Thank you @zuk3975
  • #21166: Change default ‘Erase previous images’ button state to no. Thank you @aleksiuno
  • #21121: Make Module manager error notifications fixed. Thank you @Sinepel
  • #21117: Use ProductCustomizationFieldUpdater service in CustomizationFieldHandlers. Thank you @zuk3975
  • #20830: Introduce SetAssociatedProductAttachmentsCommand and AssociateProductAttachmentCommand. Thank you @zuk3975
  • #20544: Add RemoveAllAssociatedProductSuppliersCommand. Thank you @zuk3975
  • #19982: Add order internal notes. Thank you @ks129

Front office

Tests

Code changes in the ‘1.7.7.x’ branch

Back office

  • #21203: Build assets for 177, by @jolelievre
  • #21195: Replaced SQL query to fetch modules hooked on stat hook by Hook function to have a singl Source of Truth, by @matks
  • #21190: Add missing security annotation on new 177 routes, by @jolelievre

Installer

Tests

Code changes in the ‘1.7.6.x’ branch

Installer

Code changes in modules, themes & tools

Changes in developer documentation

Cross-selling module

Core Weekly Generator tool

Wishlist block module

PrestonBot

  • #106: Add link to explain types and categories, by @eternoendless
  • #105: Don’t search wording for ME PRs + add label even when only existing wording has been found, by @atomiix

Check payment module

Custom text module

Order Notifications on the Favicon module

Google Analytics module

  • #80: Clean file GoogleAnalyticActionLib.js from useless comments. Thank you @prestaforum

Dashboard Products module

Product Comments module

Faceted search module

PHP Developer Tools

Docker images

PrestaShop Specifications

The PrestaShop open source project

  • #37: Create a list of modules and themes, by @ttoine

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @okom3pom, @ThanasisMpalatsoukas, @ksaandev, @Progi1984, @nesrineabdmouleh, @PierreRambaud, @matks, @prestaforum, @PululuK, @pablopolyte, @SimonGrn, @NeOMakinG, @eternoendless, @dependabot[bot], @zuk3975, @boubkerbribri, @ttoine, @SebSept, @jolelievre, @atomiix, @Quetzacoalt91, @dali-rajab, @aleksiuno, @SD1982, @Sinepel, @sergioregueira, @davidglezz, @unlocomqx, @LouiseBonnard, @ks129!

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!