PrestaShop Core Weekly – Week 10 of 2022

PrestaShop Core Weekly – Week 10 of 2022

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 7th to Sunday 13th of March 2022.

Core Weekly banner

General messages

Dear developers,

A bug was reported from users using Chrome latest version 99, the back-office login page display was incorrect. A fix has already been merged into 1.7.8.x branch by @NeOMakinG. Thank you everyone involved in the issue and discussion.

In the meantime, we merged the Pull Request that moved Classic theme out of the Core repository. Classic theme has now its own repository and is included inside PrestaShop through Composer (on develop branch).

Releases

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

Code changes in the ‘develop’ branch

Core

Back office

  • #27860: Added hooks for blockwishlist in classic theme, by @Progi1984
  • #27851: Simply Delivery Slip Form, by @Progi1984
  • #27848: Check href exists before replacing it in multistore header, by @atomiix
  • #27793: BO – Customer Page – Allow only positive number for Maximum number of payment days, by @Progi1984
  • #27720: MultiStore – Sell > Customer Service > Merchandise Return – Add Checkbox & Simplify Form, by @Progi1984
  • #27673: Remove ecotax field when the product is virtual, by @Progi1984
  • #27394: Improve Cart Rule Form Responsive footer, by @Progi1984
  • #27373: BO Migration Contact > Stores – Add command, command handler and behat tests for status toggle. Thank you @LouisAUTHIE
  • #27275: Move condition field from options to specifications tab, by @jolelievre

Front office

  • #27830: Fixes php notice because $result maybe false value. Thank you @buggyzap
  • #26854: Prevent customization modal open if qty changed in cart on classic, by @NeOMakinG
  • #26048: Check quantities at any point of checkout process. Thank you @Hlavtox

Tests

Code changes in the ‘1.7.8.x’ branch

Back office

  • #27843: Fix: login page float buggy on latest chrome version and long shop name problem, by @NeOMakinG
  • #27776: Stock field must be empty and still be considered as zero, by @jolelievre

Code changes in modules, themes & tools

PrestaShop Project Metrics

  • #27: Add webpage to display PR review comments data, by @matks
  • #26: Do not rely on current datetime for developer stats, by @matks
  • #24: Dont ignore weekend reviews, by @matks

Classic theme

Changes in developer documentation sources

  • #1313: fix(doc): updated modulefrontcontroller doc. Thank you @Dreimus
  • #1310: Update translation domains page, by @Julievrz
  • #1308: Adding information for using TinyMCE editor and FormattedTextareaType with prestashop UI kit and twig form. Thank you @Rizzen59

Issues Bot

Hummingbird theme

Nightly board

Core Weekly Generator tool

  • #119: Update mapping with new repositories and new names, by @matks
  • #118: Improve Core Weekly template with refs to PrestaShop 8, by @matks

Customer reassurance block module

Faceted search module

Docker images

Email Alerts module

  • #108: Release 2.3.3, by @Progi1984
  • #106: Fixed the hook listener for the hook actionProductAttributeDelete & Removed hooks actionProductOutOfStock & registerGDPRConsent as hook listeners are not defined, by @Progi1984

GDPR module

Auto Upgrade module

Wishlist block module

  • #163: Removed the hook displayProductAdditionalInfo as the hook listener is not defined, by @Progi1984

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @matks, @eternoendless, @Dreimus, @NeOMakinG, @Julievrz, @dependabot, @Progi1984, @PierreRambaud, @matthieu-rolland, @Robin-Fischer-PS, @atomiix, @mparvazi, @buggyzap, @nesrineabdmouleh, @amaury-hanser, @Rizzen59, @jolelievre, @bibips, @PrestaEdit, @LouisAUTHIE, @Hlavtox!

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!

This post is also available in: Norsk bokmål