blog-posts Posted March 2, 2020 Share Posted March 2, 2020 This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 24th of February to Sunday 1st of March 2020. General messages Dear developers, Since last week, multiple release processes have started : Next patch version for 1.7.6.x (v1.7.6.4) is now complete, QA team will test the build this week. Next PS 1.7 minor version (v1.7.7.0) is now frozen ! 🎉️ ☃️ A quick look at the work done on 1.7.7: 196 issues have been fixed 796 pull requests have been merged What a huge amount of work! This version is currently under heavy testing by the QA team. Following the tests report, we will fix all major issues in order to be able to deliver a Beta 1.7.7.0 build. A quick update about PrestaShop’s GitHub issues and pull requests: 70 new issues have been created in the project repositories; 64 issues have been closed, including 6 fixed issues on the core; 93 pull requests have been opened in the project repositories; 106 pull requests have been closed, including 72 merged pull requests Code changes in the ‘develop’ branch Core #17785: Fix X-Forwarded-For not supported properly. Thank you @davidglezz Code changes in the ‘1.7.7.x’ branch (for v1.7.7.0) Back office #17884: Use constant for reduction type in CatalogPriceRuleGridDataFactory. Thank you @zuk3975 #17796: Fix new wording without domain, by @eternoendless #17752: Add Prev/Next order button in the Order page. Thank you @tdavidsonas88 Tests #17872: Functional tests - Invoices > Other options - delete check legal free text from scenario. Thank you @nesrineabdmouleh #17836: Funtional tests - Fix employee faker, by @boubkerbribri #17829: Functional tests - Shop Parameters> General enable/disable display brands. Thank you @nesrineabdmouleh #17828: Functional tests - Shop Parameters> General enable/disable display suppliers. Thank you @nesrineabdmouleh #17824: Functional tests - Fix sending emails in nightly, by @boubkerbribri #17795: Functional tests - Payment>Preferences Configure currency restriction. Thank you @nesrineabdmouleh #17779: Functional tests - Add new tests ‘Sort categories’ and ‘Change category position’, by @boubkerbribri #17775: Functional tests - Customer settings enable/disable send email after registration. Thank you @nesrineabdmouleh #17772: Functional tests - Add test ‘Sort Addresses’, by @boubkerbribri #17762: Functional tests - Add test ‘Import localization pack’, by @boubkerbribri #17754: Functional tests - Product settings display remaining quantity in product page. Thank you @nesrineabdmouleh #17746: Restore GA for PHP CS Fixer, by @matks #17699: Functional Tests - Product settings choose quantity discounts based on. Thank you @nesrineabdmouleh Code changes in the ‘1.7.6.x’ branch (for v1.7.6.4) Core #17846: Fix exception thrown when editing a customer with a bad email address, by @atomiix Back office #17711: Fix a bug on safari where SEO preview on create page was not updated, by @NeOMakinG Code changes in modules, themes & tools Changes in developer documentation #474: Update theme translation documentation, by @eternoendless #473: Update allowed licenses for modules, by @Quetzacoalt91 #470: Improve guidelines, by @eternoendless #468: Fix bad LayoutInterface namespace. Thank you @dheerajwebkul #463: Add a definition of what is a module compatible multistore, by @marionf #461: Add a paragraph about compatible licenses, by @ttoine Share Buttons module #34: Replace http with https for socials URLs, by @khouloudbelguith #32: Clean license headers and readme, by @matks #31: Update readme to add multistore compatibility, by @marionf #30: Bump to version 2.1.0, by @PierreRambaud #21: Multiline whitespace before semicolons. Thank you @MathiasReker #18: Short array syntax. Thank you @MathiasReker Prestonbot #91: Fix unexpected label creation, by @eternoendless Block Reassurance module #42: Fix bad license header for CategoryFetcher.php, by @matks #41: Update readme to add multistore compatibility, by @marionf #38: Add Symfony 5 support. Thank you @mvorisek About Multistore compatibility Product Team member @marionf spent a lot of time working on the topic “What means ‘a module is multistore compatible’ ?” and went through all of native PrestaShop modules to clarify their status and wrote it into the README.md of these modules (see for example the Block Reassurance module). Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @eternoendless, @khouloudbelguith, @Quetzacoalt91, @zuk3975, @nesrineabdmouleh, @atomiix, @boubkerbribri, @marionf, @matks, @davidglezz, @dheerajwebkul, @jolelievre, @tdavidsonas88, @ttoine, @NeOMakinG, @PierreRambaud, @mvorisek, @MathiasReker! 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! View the full article Link to comment Share on other sites More sharing options...
Recommended Posts