This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 25th of February to Sunday 03rd of March 2019.
It seems that we eventually found a proofreader for the devdocs ;-)
That is a very interesting kind of contribution: this is something that does not require coding skills, but this is still very valuable. The documentation is then more pleasant to read and to understand.
There are many activities that you can do if you want to help with the PrestaShop open source project, but you are not a developer:
- Telling that it’s great and recommanding it
- Planning events
- Writings documentation and tutorials, or producing videos to show how it works
- Helping with issue sorting, like for example identifying duplicates or asking for details
- Helping users on the forums and other websites were users ask question about the software
A quick update about PrestaShop’s GitHub issues and pull requests:
- 55 new issues have been created in the project repositories; ()
- 53 issues have been closed, including 5 fixed issues on the core;
- 59 pull requests have been opened in the project repositories; ()
- 48 pull requests have been closed, including 35 merged pull requests.
Code changes in the ‘develop’ branch (for v220.127.116.11)
- #12346: Add Category form builder & handler. Thank you @sarjon
- #12498: Add showcase card for Suppliers list. Thank you @sarjon
- #12739: Revert to Webpack 2, by @PierreRambaud
- #12756: CO: Fix bug when create class override Address. Thank you @dariusakafest
- #12758: Added a Theme Enabler command, by @mickaelandrieu
- #10595: Migration of “Shop parameters >Traffic & SEO > SEO & URL > Add new / edit page” form. Thank you @tomas862
- #12622: Refactor AddonsStoreController to use annotations and some improvements, by @matks
- #12668: Fix help sidebar when adding/editing language. Thank you @sarjon
- #12706: Kpis list are now customizables using hooks, by @mickaelandrieu
- #12709: Refactor MetaController to secure search usage, by @matks
- #12711: BO the shipping cost becomes free if more than a half ordered. Thank you @LedCloud
- #12713: Enable usage of roles for Module Updates and Module Alerts pages and manage access, by @matks
- #12716: Prevent including jQuery in the new theme, by @eternoendless
- #12723: Patch to Issue #12500. Thank you @rblaurin
- #12761: BO: Remove timeout from product image upload. Thank you @JohnMidity
- #12696: fix missing coma in sql upgrade file, by @tomlev
- #12733: Changed the regex to force space and hyphen in postcode validation. Thank you @jojotjebaby
- #12488: Add a descriptif comment for the broken test “create_edit_delete_language”. Thank you @YosraAk
- #12490: TE: add a descriptif comment for the broken test “create_edit_delete_contact”. Thank you @YosraAk
- #12495: Add a descriptif comment for the broken test “installation language <> country “. Thank you @YosraAk
- #12678: Create virtual product. Thank you @ansar21mallouli
- #12679: Add some fixes to the campaign full. Thank you @YosraAk
Code changes in modules, themes & tools
Changes in Documentation
- #213: Minor grammar corrections. Thank you @d-roduit
- #214: Minor grammar correction. Thank you @d-roduit
- #215: Minor Grammar Corrections. Thank you @d-roduit
- #216: Moved PrestaShop webservices outside of Components section, by @mickaelandrieu
- #217: Grammar + consistency corrections. Thank you @d-roduit
- #218: Minor orthographic corrections. Thank you @d-roduit
- #219: Grammar corrections. Thank you @d-roduit
- #220: Spelling corrections. Thank you @d-roduit
- #221: Update back-office.md. Thank you @arthtux
Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @ansar21mallouli, @arthtux, @BadPixxel, @d-roduit, @dariusakafest, @JohnMidity, @jojotjebaby, @kpodemski, @LedCloud, @rblaurin, @sarjon, @tomas862, @YosraAk!
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!