Roach PHP is a complete web scraping toolkit for PHP and Laravel projects.

The post Complete Web Scraping toolkit for PHP appeared first on Laravel News.

---

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

With the release of PrestaShop 1.7.8, we expanded PrestaShop multistore capabilities to Symfony forms in order to build a reusable form component to make configuration forms multishop-compatible.

Multishop affects a lof ot PrestaShop behaviors and components. One aspect of this feature is that user can use configuration forms to set different values for different shops, which is dealt with using shop contexts.

What does this mean

In a configuration form, a merchant can set different values for three different shop contexts, in this order of inheritance:

• All shops context
• Group shop context
• Single shop context

When a value is not set for a context, it inherits the value of the parent context. Consequently, the “All Shops” context values can be considered default values.

Product designers listened to merchants feedback and were told this mechanism was not obvious, and it was not easy to see at a glance which form fields were modified or not for the current context in the back-office.

We wanted to build something new to make this feature easier to use.

Our target

We set ourselves two main criteria:

• Improve existing User Experience for better understanding

• Make the technical implementation as reusable as possible on existing and future configuration forms, to make sure external contributors and module developers can easily reuse it.

Building multistore configuration forms

User interface

After numerous merchant interviews, UX designers team created mock-ups, then Product owners worked out how it should behave and wrote it down as specifications in accordance with users feedback.

Here is how a multistore compatible configuration form looks like since Prestashop 1.7.8:

As you can see, a checkbox appears before multistore compatible fields. When it’s not checked and the field is greyed out, it means that the value is inherited from a parent context. When it’s checked, the value is overridden. In our screenshot example we can see that:

• The “Enable store” and “Maintenance IP” fields are greyed out, and their checkboxes are unchecked: it means their values are inherited from the parent context (“All shops” context in this case)
• The field “Custom maintenance text” is not greyed out, and its checkbox is checked: it means its value is overriding the parent context, this value is specifically defined for this context (single shop context in this case)

In “All shops” and group context, if a child context has a field that is overridden, a dropdown is displayed next to it and informs whether the value is overridden or not for each context:

Here, we are looking at the dropdown for the field “Maintenance IP”, in “All shops” context, and we are given these pieces of information:

• the shop called “Awesome store” has an overriden value for this field, that is to say a customized value
• the shop called “Shop 2” inherits the value from this context (127.0.0.1)

As you see, we did not fully reinvent the feature, we kept the concept of checkboxes, but we tried to make clearer what it does with the dropdowns and by graying fields when they inherit their value from the parent context.

Looking at the technical implementation

On the technical side, these visual elements had to be reusable and easily implementable, without having to copy HTML or rethink the logic in the backend.

All the work of knowing if the value of a field is inherited or not, and saving the submitted value only for the right context should be done only once, and easily reused by external contributors.

For this purpose, we decided to take advantage of Symfony form extensions. To add the new checkboxes and multistore dropdowns on a configuration form, a developer simply needs to extend our multistore extension and configure each multishop field with its related configuration name, see the maintenance configuration form as an example.

Then we added multistore helper methods for Configuration classes, to make saving data for the right context a breeze (depending on which checkboxes are checked). See how the new updateConfigurationValue method is used here.

Finally, we created a new multistore Javascript component, which only needs to be instantiated in order to make the multistore form reactive. You can see it in action in the multistore example module.

Friendly reminder :)

As most of you may know, PrestaShop is open source, which means you are more than welcome to contribute ! Multistore’s technical documentation can be found here, there’s also a module example showing you how you can make your configuration forms multistore compatible in your own modules.

Feedback is always appreciated, so don’t hesitate to contact us on one of our Slack channels, see you soon !

With the increase in demand for technology and quality assurance, companies are looking to improve their products day by day. For many time and workforce are limited, so companies are interested in solutions that automate their day-to-day work.

The post What Makes Automated Application Monitoring so Important? 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 24th to Sunday 30th of January 2022.

General messages

Dear developers,

The first month of this year draws close, and much has already been done!

If you wish to see a bit of this month achievements, just join us for next session of public demonstration from the maintainers team. It will be streamed live on Wednesday, February 2, 2022, at 4 pm CET. See you then!

Releases

• PrestaShop: 1.7.8.3
• Ps_emailalerts module: v2.3.1

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

• 67 new issues have been created in the project repositories;
• 64 issues have been closed, including 33 fixed issues on the core;
• 83 pull requests have been opened in the project repositories;
• 69 pull requests have been closed, including 58 merged pull requests.

Code changes in the ‘develop’ branch

Core

• #27234: Fix regexp of “id_product_attribute” keyword in product route. Thank you @saulaski
• #26773: Get specific prices: let mysql optimize the query.. Thank you @lmeyer1
• #26748: Instead of testing each hook if it is active, query once and cache.. Thank you @lmeyer1

Back office

• #27457: Remove NotBlank constraint on CreditSlipOptionsType, by @matks
• #27421: Improve products return controller. Thank you @okom3pom
• #25992: Fix mail templates. Thank you @lmeyer1
• #25464: Product multishop prices, by @jolelievre

Installer

• #26588: checkSelectPrivilege must check privileges for both InnoDB and MyISAM. Thank you @onlime

Tests

• #27460: Functional tests - Fix nightly 25/01/2022. Thank you @nesrineabdmouleh
• #27059: Functional tests - Add new test ‘Check invoice’. Thank you @nesrineabdmouleh

Code changes in the ‘1.7.8.x’ branch

Back office

• #27429: Add text nowrap to link btn inside grids, by @NeOMakinG
• #27389: Fix bad display of progress bar for bulk actions. Thank you @mparvazi
• #27333: Fix bad display of scrollbar for sidebar menu in RTL. Thank you @mparvazi
• #27330: Fix default value for Jquery colorpicker, by @sowbiba
• #27296: Add class on light display layout and remove padding top, by @NeOMakinG
• #27257: Hide default spin buttons for input number. Thank you @mparvazi
• #27236: Fix customer grid data factory. Thank you @rsoulard-prolaser
• #27225: Improve CMS edit page footer. Thank you @Hlavtox

Front office

• #27376: Fix an unclear alert. Thank you @rsoulard-prolaser
• #27374: Fix wrong array_slice arguments, by @atomiix

Code changes in modules, themes & tools

Faceted search module

• #604: Bump chai from 4.3.5 to 4.3.6. Built by @dependabot[bot]
• #602: Bump chai from 4.3.4 to 4.3.5. Built by @dependabot[bot]
• #601: Bump mocha from 9.1.4 to 9.2.0. Built by @dependabot[bot]
• #600: Bump @babel/core from 7.16.10 to 7.16.12. Built by @dependabot[bot]
• #599: Bump webpack from 5.66.0 to 5.67.0. Built by @dependabot[bot]
• #593: Fix strip_tags error messages during value escaping.. Thank you @FongWan

Docker images

• #287: Add 1.7.8.3 image, by @Progi1984

Customer reassurance block module

• #346: Bump mini-css-extract-plugin from 2.5.2 to 2.5.3. Built by @dependabot[bot]
• #345: Bump webpack-cli from 4.9.1 to 4.9.2. Built by @dependabot[bot]
• #344: Bump @babel/core from 7.16.10 to 7.16.12. Built by @dependabot[bot]
• #343: Bump webpack from 5.66.0 to 5.67.0. Built by @dependabot[bot]

Wishlist block module

• #159: Improved Github Action (Support PHP 5.6 => 8.1), by @Progi1984

Contact Form module

• #59: Added Github Action for PHP (and support PHP 5.4 => 8.1), by @Progi1984

Dashboard Goals module

• #28: Added Github Action for PHP (and support PHP 5.4 => 8.1), by @Progi1984

Banner module

• #42: Added Github Action for PHP (and support PHP 5.4 => 8.1), by @Progi1984

Changes in developer documentation site

• #10: Update docsearch configuration, by @eternoendless

Changes in developer documentation theme

• #10: Update to new Docsearch v3 and fix native search when docsearch is disabled, by @eternoendless

Changes in developer documentation sources

• #1275: Fixed minor typos in the documentation for CI/CD. Thank you @Om3n31
• #1271: Fix Minor typos in the documentation in update CI/CD. Thank you @Om3n31

New Front-office theme

• #165: Fix noUiSlider for RTL. Thank you @mparvazi
• #163: Fix empty script error in browser console. Thank you @mparvazi
• #158: Fix products sort order dropdown in Search page. Thank you @mparvazi
• #157: Fix input number UI. Thank you @mparvazi
• #156: Using Vazir font for shops in RTL language. Thank you @mparvazi
• #155: Using sass:math for noUiSlider . Thank you @mparvazi

Wire payment module

• #67: Fixed hook function name for hook displayPaymentReturn, by @Progi1984

Prestashop UI Kit

• #182: Bump node-fetch from 2.6.1 to 2.6.7. Built by @dependabot[bot]
• #181: Bump nanoid from 3.1.22 to 3.2.0. Built by @dependabot[bot]

User documentation landing page

• #182: fix(deps): bump node-fetch from 2.6.1 to 2.6.7. Built by @dependabot[bot]
• #181: fix(deps): bump nanoid from 3.1.24 to 3.2.0. Built by @dependabot[bot]

Stylelint browser compatibility plugin

• #14: Bump postcss from 8.2.10 to 8.2.13. Built by @dependabot[bot]
• #13: Bump nanoid from 3.1.23 to 3.2.0. Built by @dependabot[bot]

Stylelint configuration

• #24: Bump nanoid from 3.1.25 to 3.2.0. Built by @dependabot[bot]

Email Alerts module

• #102: Fix undefined locale error when creating order from BO, by @kpodemski
• #101: Release 2.3.1, by @kpodemski

Cash on delivery module

• #40: Remove deprecated hook and update to 1.0.7, by @Progi1984

Links list module

• #142: Hide Best Sales link if feature is disabled. Thank you @saulaski

---

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @dependabot[bot], @Progi1984, @nesrineabdmouleh, @matks, @eternoendless, @Om3n31, @mparvazi, @kpodemski, @NeOMakinG, @okom3pom, @rsoulard-prolaser, @atomiix, @FongWan, @sowbiba, @saulaski, @Hlavtox, @lmeyer1, @onlime, @jolelievre!

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!