blog-posts Posted March 15, 2019 Share Posted March 15, 2019 This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 04th to Sunday 10th of March 2019. General messages Dear Developers, An important step for the PrestaShop open source project has been completed last week and it is available today: the nightly builds and tests dashboard. This is a new dedicated website: https://nightly.prestashop.com/. Each night, a new build is created with the newly merged code. Then, the automatic tests are run for this build, and a report is created. Those tests are different from the suite on Travis: they cover more features of PrestaShop, and may require several hours to complete. That’s why we don’t execute them on each pull-request, for instance. It will help contributors to improve the quality of PrestaShop. For now, you will see that many tests are failing. This will be improved and corrected during the weeks before the code freeze. And of course, your help is welcome 😀 A quick update about PrestaShop’s GitHub issues and pull requests: 60 new issues have been created in the project repositories; 73 issues have been closed, including 9 fixed issues on the core; 35 pull requests have been opened in the project repositories; 36 pull requests have been closed, including 29 merged pull requests. Code changes in the ‘develop’ branch (for v1.7.6.0) Core #11783: Migrate customers searching via ajax. Thank you @sarjon #12251: Improve version, by @eternoendless #12570: Add Drag & Drop styling for category position column. Thank you @sarjon #12749: 9 duplicates removed from array in getProductAttributeWhitelist(). It…. Thank you @toslan #12766: Remove duplicated CLDR service, by @matks #12803: Fallback on language code when locale is empty, by @Quetzacoalt91 #12808: Deprecate Cart::addExtraCarriers(), by @eternoendless #12810: Install ps_faviconnotificationbo automatically, by @eternoendless #12841: Add deprecation notice for hook actionAjaxDieBefore, by @eternoendless Back office #12505: Improve error handling in migrated controllers. Thank you @sarjon #12610: Taxes Options configuration form migration. Thank you @zuk3975 #12717: Adds re-usable rewrite link copier service. Thank you @tomas862 #12730: Error 500 in product catalog when short description is too long. Thank you @rblaurin #12751: Fix saving shop association in migrated add/edit forms. Thank you @rokaszygmantas #12784: Add module main class parse error to log message. Thank you @teemumantynen #12787: adds legacy links to all meta page routes. Thank you @tomas862 #12838: Update ProductSpecificPrice.php. Thank you @metineren Front office #12748: Remove obsolete P3P policy. Thank you @MathiasReker #12753: Allow ipv6 to be used in htaccess redirects, by @Quetzacoalt91 Installer #12666: Delivery slips fails when upgrading to 1.7.5. Thank you @rblaurin Web services #12836: Fixes http 500 when trying to get the images of a product with no images . Thank you @mowcixo Tests #12793: Allow Travis phpHigh build to fail as it is an informative check, not…, by @matks #12804: Use string value for CSRF token in DeliveryControllerTest, by @matks Code changes in modules, themes & tools Circuit breaker #26: Ease configuration of calls using all usual HTTP methods, by @mickaelandrieu Auto upgrade #285: Use raw trans to avoid " being displayed, by @Quetzacoalt91 #286: Allow ipv6 to pass the maintenance check, by @Quetzacoalt91 #288: Do not reset theme anymore when already active (prevent hooks to be reset), by @Quetzacoalt91 #290: Do not display exception when running unit tests, by @Quetzacoalt91 Changes in Documentation #224: Add documentation on legacy controllers, by @eternoendless Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @mowcixo, @rblaurin, @sarjon, @tomas862, @toslan, @zuk3975! 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