Small Tweeks in Oro-Commerce

Hello Oro Team,

I have the following 3-4 small items I would like to tweak:

1. I am using Oro-Commerce with Demo-data to readjust it to my specification. Everything is adjustable however, in the products drop down menu the “Sale” node & an associated picture under it is not being removed. I don’t have the sale as a node in my web-catalog yet it’s showing. Can you help me get rid of it?

2. On the Contact us form, or registration form or billing address, certain important field like Name, Phone, etc I want to make mandatory”*” rather than the current non-mandatory classification of these items on the forms – how can I achieve this.

3. There are quite a few product filtering options shown on the product/subcategory page – is there a way for me to remove certain filters (e.g, contains certain text filter etc.)?
or place them in the right sidebar rather than on top of the page to have better-looking pages? -please let me know both the scenarios.

4. I am using AWS – and I want to set up email such that I have multiple Emails for the website sperate sections (e.g contactus@website.com, Sales@website.com, info@website.com etc, noreply@website.com(default used for sending system generated emails)) how can I have this in different sections of the website. Is one email work email from AWS enough to cater to meet my requirements?

Appreciate your help.

Topic

[MichaelKeymaster]

Hello snb-me,

1. The layout of the menu drop-downs can be overrided in your custom theme by setting “use_for” and “not_use_for” options in the layout – https://github.com/oroinc/orocommerce/blob/3.1.4/src/Oro/Bundle/WebCatalogBundle/Resources/views/layouts/blank/page/main_menu.yml#L17-L36, or by customizing the menu templates in your theme – https://github.com/oroinc/orocommerce/blob/3.1.4/src/Oro/Bundle/WebCatalogBundle/Resources/views/layouts/blank/page/main_menu.html.twig#L71-L101

2. It depends on what fields, but generally for any form modifications you would need to create a form extension (https://symfony.com/doc/3.4/form/create_form_type_extension.html), and possibly add additional validation constraints in validation.yml to the corresponding entities.

3. The out-of-the-box filter form types, their matching JS widgets and templates are listed in https://github.com/oroinc/platform/blob/master/src/Oro/Bundle/FilterBundle/Resources/doc/reference/filter_form_types.md , https://github.com/oroinc/platform/blob/master/src/Oro/Bundle/FilterBundle/Resources/doc/reference/javascript_widgets.md and https://github.com/oroinc/platform/blob/3.1.4/src/Oro/Bundle/FilterBundle/Resources/views/layouts/blank/config/requirejs.yml .

Some examples of the filter widgets (you can see how they extend some existing filter and add their own functionality):
– (simple) https://github.com/oroinc/orocommerce/blob/3.1.4/src/Oro/Bundle/CatalogBundle/Resources/public/js/filter/subcategory-filter.js
– (more complex) https://github.com/oroinc/orocommerce/blob/3.1.4/src/Oro/Bundle/PricingBundle/Resources/public/js/filter/product-price-filter.js

Moving filters to a sidebar is also achievable via customizing the storefront theme.

4. I’m not sure what AWS functionality you are referring to.

[Author]

Replies