The developer can add a custom filter to the virtual type Magento\Catalog\Model\Api\SearchCriteria\CollectionProcessor\ProductFilterProce5sor for supplier_id field. In the custom filter, the developer can apply the needed join and filter to the passed $collection. This is the recommended way to extend the search criteria for products using dependency injection and plugins. Verified References: [Magento 2.4 DevDocs] [Magento Stack Exchange]

In Adobe Commerce, when you need to add a custom filter for a non-EAV attribute stored in a standalone table, the most maintainable approach is to create a custom filter for ProductFilterProcessor. This processor allows for customized search criteria handling, which can be extended to include custom joins and filters without altering core functionality or relying on plugins and observers.

Why Custom Filter in ProductFilterProcessor is Preferred:

The ProductFilterProcessor within SearchCriteria\CollectionProcessor is specifically designed to handle filtering of product collections. By extending this with a custom filter, the developer can implement joins and filters on standalone tables.

This approach is modular and reusable, allowing any code that utilizes ProductRepositoryInterface to apply the supplier_id filter seamlessly.

Implementation of Custom Filter:

Define a custom filter class that implements the required logic to join the standalone table and apply the supplier_id filter.

Register this custom filter with a virtual type in di.xml for ProductFilterProcessor, so it can process the supplier_id as part of the search criteria.

Why Options A and C are Less Suitable:

Option A relies on an event observer, which is less modular and may have performance implications since it requires listening to every product collection load event.

Option C, while functional, involves modifying CollectionProcessorInterface::process(), which is more generic and not specifically tailored for product collection filtering.

References:

Magento Developer Documentation on Using Custom Filters in CollectionProcessor

Magento DevDocs on Dependency Injection and Virtual Types

To add file upload validation for a custom form field in the Adobe Commerce admin panel, which should restrict the file type to .pdf and limit the file size to 2 MB, the recommended approach is to include the validation parameters directly within the node in the form’s XML configuration. This ensures that the validation occurs on the client-side as well as server-side, providing immediate feedback to users before submission.

Option C is correct for the following reasons:

Adding Validation Inside <settings>:By placing the and tags within the node of the XML configuration, the system will enforce these restrictions directly within the form component. This method leverages Magento’s built-in support for validation settings, which ensures that only files matching the specified criteria (.pdf files of 2 MB or smaller) are accepted by the form.

Explanation: Magento UI components allow for client-side validation through the node, where attributes such as allowedExtensions and maxFileSize are used to control file upload constraints. This approach not only validates the file size and type but also integrates seamlessly with Magento’s front-end validation mechanisms.

References: Magento’s documentation on UI components highlights how to enforce file type and size restrictions through XML configurations within , making it the standard and most efficient solution for this task.

Alternatives and Limitations:

Option A: Adding validation within the controller (UploadPdf) can provide additional server-side validation, but this does not prevent the user from selecting invalid files in the first place. Server-side validation alone lacks the user experience enhancement provided by client-side feedback.

Option B: Configuring a virtual type in di.xml for validation (e.g., setting allowedExtensions and maxFileSize within a custom uploader model) is effective for backend processing but is not as straightforward for direct form validation within the admin UI. It complicates the implementation by requiring custom backend logic where native XML validation can suffice.

Option C provides a straightforward, maintainable, and user-friendly way to implement file validation directly in the form configuration. It reduces the need for custom controller or model logic and leverages Magento’s built-in form handling capabilities.

The CLI command that the developer would use to update the admin url is magento-cloud variable:set ADMIN_URL. This command sets an environment variable called ADMIN_URL with a custom value for the admin url on a specific environment. Environment variables are configuration settings that affect the behavior of the Adobe Commerce Cloud application and services. By setting an environment variable for ADMIN_URL, the developer can change the default admin url to a unique url for every branch/environment of their Adobe Commerce Cloud project. Verified References: [Magento 2.4 DevDocs]