blog-posts Posted October 2, 2019 Share Posted October 2, 2019 This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 19th of August to Sunday 25th of August 2019. A quick update about PrestaShop’s GitHub issues and pull requests: 75 new issues have been created in the project repositories; 78 issues have been closed, including 6 fixed issues on the core; 49 pull requests have been opened in the project repositories; 57 pull requests have been closed, including 47 merged pull requests. Code changes in the ‘develop’ branch Core #14951: Update PrestaShopCollection.php docs on getFirst method return type. Thank you @zalexki Back office #15005: Last visit date incorrect. Thank you @cirykpopeye #14873: Remove AdminManufacturer controller again, by @matks #14869: Removes AdminPreferencesController again, by @matks Front office #15055: Fix duplicate class attribute in HTML element. Thank you @asf-harlock #14727: Fix compile id {render} override issue on theme. Thank you @202-ecommerce #14539: Make email display dependant on configuration from ps_contactinfo module, by @matthieu-rolland Installer #15131: Fixed permanent redirection in installer, by @mickaelandrieu Tests #15206: Smoke tests - Fix the product selector in the FO. Thank you @nesrineabdmouleh #15163: Docker for test AutoUpgrade, by @boubkerbribri #15161: Remove another faulty e2e test from Travis, by @matks #15156: Adding new Test UpgradeShop with puppeteer, by @boubkerbribri #15155: Update expect usage in puppeteer tests, by @boubkerbribri #15151: All BO classes should inherit from BObasePage, by @boubkerbribri Code changes in the ‘1.7.6.x’ branch (for v1.7.6.1) Core #15132: Fix abstract service declaration, by @eternoendless Back office #15173: CLDR has access to all currencies regardless of the current shop, by @jolelievre #15139: Make module and email translations work again when using a theme other than classic, by @eternoendless Code changes in modules, themes & tools PrestaShop Specifications #68: Update README.md, by @colinegin #67: Update README.md, by @colinegin #66: Colinegin patch 7, by @colinegin #65: symfony migration, by @colinegin #64: Delete symfony-migration, by @colinegin #63: symfony-migration, by @colinegin #62: symfony-migration, by @colinegin #61: Update README.md, by @colinegin #59: Create symfony-migration, by @colinegin #58: Update README.md, by @colinegin #57: Update README.md, by @colinegin #56: Update theme-logo.md, by @colinegin #55: Update README.md, by @colinegin #54: theme-logo, by @colinegin #53: Ecotax specs in product add/edit page, by @marionf #52: Updates specs add / edit product, by @marionf #51: Update specs for product SEO tab, by @marionf #50: Specify errors message to add/edit product specs, by @marionf #49: Update add/edit product specs links, by @marionf #48: Add link to add/edit product specs, by @marionf #47: Add options tab to add/edit product specs, by @marionf #46: update faceted search specs, by @marionf #45: update faceted search specs, by @marionf #44: Update faceted seach specs, by @marionf #43: Update faceted search specs, by @marionf #42: Update specs of BO product page, by @marionf #40: Rename Prestashop.md to README.md, by @PierreRambaud Changes in developer documentation #327: Fix typo for ‘modules’ in 1.7/themes/getting-started/theme-organization. Thank you @hdasdoria Contact Informations module #13: Make email display in footer and contact us page configurable, by @matthieu-rolland Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @colinegin, @marionf, @hdasdoria, @nesrineabdmouleh, @jolelievre, @boubkerbribri, @matks, @eternoendless, @mickaelandrieu, @PierreRambaud, @asf-harlock, @cirykpopeye, @zalexki, @202-ecommerce, @matthieu-rolland! 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...
.png.022b5452a8f28f552bc9430097a16da2.png)
Recommended Posts