The post Laravel 9.26 Released appeared first on Laravel News.

Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

The post Import Laravel Vapor DNS to Cloudflare appeared first on Laravel News.

Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

The post Learn PestPHP From Scratch appeared first on Laravel News.

Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 15th to Sunday 21th of August 2022.

General messages

Dear developers,

PrestaShop 8 Beta 1 phase continues. Remember that you have time until September 5th, 2022, to test and report any issues you find.

Last week there was a significant update of the developer documentation that summarizes notable changes in PrestaShop 8. We highly recommend to check them.

Releases

• Ps_customersignin module: v2.0.5

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

• 52 new issues have been created in the project repositories;
• 23 issues have been closed, including 6 fixed issues on the core;
• 69 pull requests have been opened in the project repositories;
• 36 pull requests have been closed, including 28 merged pull requests.

Code changes in the ‘develop’ branch

Core

• #29367: Update the theme argument description. Thank you @PrestaEdit
• #29325: Fix exception message while removing configuration. Thank you @PrestaEdit

Back office

• #28872: [BO] : Class name must be allowed from controller in select render list column. Thank you @Amit-Kumar-Tiwari-Webkul

Code changes in the ‘8.0.x’ branch

Back office

• #29288: Restructurize horizontal migration Bridge directories. Thank you @zuk3975

Tests

• #28906: Functional tests - Fix CRUD address test on FO. Thank you @nesrineabdmouleh

Code changes in modules, themes & tools

Changes in developer documentation sources

• #1459: Remove tests-legacy. Thank you @PrestaEdit
• #1457: Remove extra -v of classname modifier output. Thank you @PrestaEdit
• #1456: Update theme argument description. Thank you @PrestaEdit
• #1454: Update theme argument description. Thank you @PrestaEdit
• #1453: Remove extra -v and update ouptput of classname modifier. Thank you @PrestaEdit
• #1452: Javascript file extension and import path changes since PS 8.0.0. Thank you @leemyongpakvn
• #1444: Update sql link, ts extensions, and branch links. Thank you @leemyongpakvn
• #1427: Documentation for BC Breaks and changes in 8.0, by @kpodemski

The PrestaShop open source project

• #115: Readme : Rendering the site locally. Thank you @okom3pom
• #113: Fix install script. Thank you @okom3pom
• #67: Update README, by @matks

Module Releases Monitor

• #13: Add PHP CS Fixer and run it in CI, by @matks
• #12: Add last release date, and last PR on main or master. Thank you @okom3pom

Hummingbird theme

• #363: customization modal fix. Thank you @JBLach

GDPR module

• #180: Bump version 1.4.3, by @kpodemski

Check payment module

• #60: Deleting unnecessary files. Thank you @okom3pom

Customer “Sign in” link module

• #47: bump version to 2.0.5, by @kpodemski
• #46: Release v2.0.5, by @kpodemski

Links list module

• #154: bump version to 5.0.5, by @kpodemski

Customer reassurance block module

• #436: Bump eslint from 8.21.0 to 8.22.0. Built by @dependabot[bot]

Faceted search module

• #698: Bump eslint from 8.21.0 to 8.22.0. Built by @dependabot[bot]

Traces

• #33: Sort alphabetically. Thank you @okom3pom

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @PrestaEdit, @okom3pom, @matks, @leemyongpakvn, @JBLach, @kpodemski, @jolelievre, @dependabot[bot], @zuk3975, @nesrineabdmouleh, @Amit-Kumar-Tiwari-Webkul!

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:

• Contributing code to PrestaShop
• Coding standards

…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!