Category: magento 2.x

Adobe Commerce Technical Project Manager is managing / controlling the technical aspects of projects related to the implementation, customization, and maintenance of Adobe Commerce (formerly Magento) e-commerce platforms. Here are some key responsibilities and tasks you might have in this role:

Step-1:: Project Planning – Collaborate with stakeholders to define project objectives, scope, and requirements. Develop project plans, timelines, and resource allocation strategies.

Step-2:: Technical Expertise – Possess in-depth knowledge of Adobe Commerce and its technical components. Understand the platform’s architecture, customization options, integration capabilities, and extension development.

Step-3:: Team Management – Lead a team of developers, designers, and other technical professionals. Assign tasks, provide guidance, and ensure efficient collaboration to meet project goals.

Step-4:: Requirement Analysis – Work closely with clients or business stakeholders to understand their e-commerce requirements. Translate business needs into technical specifications and ensure alignment with Adobe Commerce capabilities.

Step-5:: Solution Design: Collaborate with architects and developers to design technical solutions that meet the project requirements. Identify and evaluate potential risks and propose mitigation strategies.

Step-6:: Project Execution: Monitor project progress, track milestones, and ensure adherence to timelines and budgets. Coordinate with cross-functional teams to resolve issues and ensure successful project delivery.

Step-7:: Quality Assurance: Define and implement quality assurance processes to ensure the stability, performance, and security of Adobe Commerce implementations. Conduct testing, bug tracking, and issue resolution activities.

Step-8:: Stakeholder Communication: Maintain regular communication with project stakeholders, providing updates on project status, risks, and dependencies. Address any concerns or queries and ensure effective stakeholder engagement.

Step-9:: Documentation and Reporting: Create and maintain project documentation, including technical specifications, project plans, and progress reports. Prepare and present project status reports to stakeholders and management.

Step-10:: Continuous Improvement: Stay updated with the latest trends, best practices, and updates related to Adobe Commerce and e-commerce in general. Identify opportunities for process improvements and contribute to the enhancement of project management methodologies.

Once Installed Magento 2.x & try to open frontend & backend & getting below error

Exception #0 (Magento\Framework\Exception\ValidatorException): Invalid template file: 'D:/xampp/htdocs/mage244/vendor/magento/module-backend/view/adminhtml/templates/page/js/require_js.phtml' in module: 'Magento_Backend' block's name: 'require.js'

Solution:: Follow below steps

Step [1] – Open file Validator.php below path

Magento2.x_base-path\vendor\magento\framework\View\Element\Template\File

Step [2] – Go To Function — protected function isPathInDirectories($path, $directories) & replace with below code

protected function isPathInDirectories($path, $directories) {

	$realPath = str_replace('\\', '/', $this->fileDriver->getRealPath($path));

	if (!is_array($directories)) 

	{ $directories = (array)$directories; } 

	foreach ($directories as $directory) { 

	if (0 === strpos($realPath, $directory)) 

	{ return true; } 

	} return false; 

	}

Step [3] – Finally Save File & run below command & issue will resolved

php bin/magento setup:upgrade && php bin/magento setup:static-content:deploy -f && php bin/magento indexer:reindex && php bin/magento cache:flush

In PatchApplier.php line 170: Unable to apply data patch MagentoThemeSetupPatchDataRegisterThemes for module Magento_Theme. Original exception message: Wrong file In Gd2.php line 64:

Magento 2.x / Adobe Commerce 2.x “Regenerate Url rewrites” extension add a CLI feature which allow to regenerate a Url rewrites of products/categories in all stores or specific store.

Need to use below magento2-regenerate_url_rewrites extension

https://github.com/olegkoval/magento2-regenerate_url_rewrites extension

Installation By Composer (“Regenerate Url rewrites” extension)

composer require olegkoval/magento2-regenerate-url-rewrites

How To Enable Extension

enable extension (use Magento 2 command line interface as below):

php bin/magento module:enable OlegKoval_RegenerateUrlRewrites

To make sure that the enabled module is properly registered, run ‘setup:upgrade’:

php bin/magento setup:upgrade

[if needed] re-compile code and re-deploy static view files:

php bin/magento setup:di:compile $> php bin/magento setup:static-content:deploy

HOW TO USE “Regenerate Url rewrites” extension:

Step[1] – To regenerate Url Rewrites of all products in all stores (only products) set entity type to “product”: >

php bin/magento ok:urlrewrites:regenerate --entity-type=product

because product entity type is default – you can skip it:

php bin/magento ok:urlrewrites:regenerate

Step[2] – To regenerate Url Rewrites in the specific store view (e.g.: store view id is “2”) use option –store-id:

php bin/magento ok:urlrewrites:regenerate --store-id=2

Step[3] – To regenerate Url Rewrites of some specific product then use option product-id (e.g.: product ID is “122”):

php bin/magento ok:urlrewrites:regenerate --entity-type=product --product-id=122

or

php bin/magento ok:urlrewrites:regenerate --product-id=122

Step[4] – To regenerate Url Rewrites of specific products range then use option products-range (Example regenerate for all products with ID between “101” and “152”):

php bin/magento ok:urlrewrites:regenerate --entity-type=product --products-range=101-152

• if in the range you have a gap of ID’s (in range 101-152 products with ID’s 110, 124, 150 not exists) – do not worry, script handle this.

or

php bin/magento ok:urlrewrites:regenerate –products-range=101-152

Step[5] – To save a current Url Rewrites (you want to get a new URL rewites and save current) use option –save-old-urls:

php bin/magento ok:urlrewrites:regenerate --save-old-urls

Step[6] – To prevent regeneration of “url_key” values (use current “url_key” values) use option –no-regen-url-key:

php bin/magento ok:urlrewrites:regenerate --no-regen-url-key

if you do not want to run a full reindex at the end of Url Rewrites generation then use option –no-reindex:

php bin/magento ok:urlrewrites:regenerate --no-reindex

if you do not want to run cache:clean at the end of Url Rewrites generation then use option –no-cache-clean:

php bin/magento ok:urlrewrites:regenerate --no-cache-clean

if you do not want to run cache:flush at the end of Url Rewrites generation then use option –no-cache-flush:

php bin/magento ok:urlrewrites:regenerate --no-cache-flush

if you do not want to display a progress progress bar in the console then use option –no-progress:

php bin/magento ok:urlrewrites:regenerate --no-progress

Regenerate url rewrites of category

Step [1] – To regenerate Url Rewrites of all categories in all stores set entity type to “category”:

php bin/magento ok:urlrewrites:regenerate –entity-type=category

Step [2] – To regenerate Url Rewrites of some specific category then use option category-id (e.g.: category ID is “15”):

php bin/magento ok:urlrewrites:regenerate –entity-type=category –category-id=15

Step [3] – To regenerate Url Rewrites of specific categories range then use option categories-range (e.g.: regenerate for all categories with ID between “4” and “12”):

php bin/magento ok:urlrewrites:regenerate --entity-type=category --categories-range=4-12

if in the range you have a gap of ID’s (in range 4-12 category with ID “6” not exists) – do not worry, script handle this.

If you use options –category-id or –categories-range then you can skip option –entity-type=category – extension will understand that you want to use a category entity.

There are following 6 type Magento 2.x / Adobe Commerce 2.x Offline payment methods6 Type Magento 2.x / Adobe Commerce 2.x Offline payment methods

1. Zero Subtotal Checkout
2. Cash On Delivery Payment
3. Bank Transfer Payment
4. Check / Money Order
5. Purchase Order
6. Payment on Account B2B for Adobe Commerce (Available with B2B for Adobe Commerce)

1). Zero Subtotal Checkout:: Once Order Total is Zero ( 0 ), Payment Methods (Zero Subtotal Checkout ) is applied automatically in Magento 2.x / Adobe Commerce

How To enable Zero Subtotal Checkout Payment:: Follow below Admin steps

[a] – Go to Stores > Settings > Configuration.

[b] – In the left panel, expand Sales and choose Payment Methods.

[c] – Under Other Payment Methods, expand the Zero Subtotal Checkout Payment section & select Yes option from Enabled Select Option

2). Cash On Delivery Payment:: Shipping Person (Delivery Person) receives payment from the customer at the time of delivery

How To enable Cash On Delivery Payment:: Follow below Admin steps

[a] – Go to Stores > Settings > Configuration.

[b] – In the left panel, expand Sales and choose Payment Methods.

[c] – Under Other Payment Methods, expand the Cash On Delivery Payment section & select Yes option from Enabled Select Option

3). Bank Transfer Payment:: It is allowed to accept payment that is transferred from a customer bank account and deposited into your merchant bank account.

How To enable Bank Transfer Payment:: Follow below Admin steps

[a] – Go to Stores > Settings > Configuration.

[b] – In the left panel, expand Sales and choose Payment Methods.

[c] – Under Other Payment Methods, expand the Bank Transfer Payment section & select Yes option from Enabled Select Option

4). Check / Money Order Payment:: It is allowed to accept payment that is transferred from a customer bank account and deposited into your merchant bank account.

How To enable Check / Money Order Payment:: Follow below Admin steps

[a] – Go to Stores > Settings > Configuration.

[b] – In the left panel, expand Sales and choose Payment Methods.

[c] – Under Other Payment Methods, expand the Check / Money Order Payment section & select Yes option from Enabled Select Option

5). Purchase Order Payment:: The purchase order is authorized, verified & issued in advance by the company that is making the purchase. Is is specially made for Commercial Customers to pay for authorized purchases by referencing the PO number, that is issued by the company in advance

How To enable Purchase Order Payment:: Follow below Admin steps

[a] – Go to Stores > Settings > Configuration.

[b] – In the left panel, expand Sales and choose Payment Methods.

[c] – Under Other Payment Methods, expand the Purchase Order Payment section & select Yes option from Enabled Select Option

6). Payment on Account B2B for Adobe Commerce (Available with B2B for Adobe Commerce)::

Payment on Account is not supported for orders with multiple shipping addresses

How To enable Payment on Account:: Follow below Admin steps

[a] – Go to Stores > Settings > Configuration.

[b] – In the left panel, expand Sales and choose Payment Methods.

[c] – Under Other Payment Methods, expand the Purchase Order Payment section & select Yes option from Enabled Select Option

The following below steps follow to configure Tax Settings in Magento 2.x or Adobe Commerce

Step [1] – Go To Stores > Settings > Configuration

Step [2] – left panel, Click on Sales > Tax

Step [3] – Expand Left Panel Tax Classes.

Step [4] – Select Tax Class for all below Tax Classes

Select Tax Class for Shipping:: either None or Taxable Goods, by default None selected

Select Tax Class for Gift Options:: either None or Taxable Goods, by default None selected

Select Default Tax Class for Product:: either None or Taxable Goods:: by default Taxable Goods selected

Select Default Tax Class for Customer:: By default Retail Customer selected

Step [5] – Finally click on Save Button.

What is Cross Border Trade:: It is also call Cross-Border Price Consistency, when other merchants who want to maintain consistent prices for customers whose tax rates are different from the predefined store tax rate.

How To Enable Cross-Border Price Consistency:: Follow below steps::

Step [1] – Go to Stores > Settings > Configuration

Step [2] – In the left panel, expand Sales and choose Tax.

Step [3] – Expand  the Right Panel Calculation Settings section.

Step [4] – Set Catalog Prices to Including Tax.

Step [5] – To enable cross-border price consistency, set Enable Cross Border Trade to Yes.

Step [6] – Finally click on Save Button & Cross Border Trade has been enabled.

HIPAA (Health Insurance Portability and Accountability Act of 1996) is U.S. legislation created to improve healthcare standards.

HIPAA offers data privacy and security protections for protecting medical services based Data , following below services provides

• To improve efficiency in the healthcare industry
• To improve the portability of health insurance
• To protect the privacy of patients and health plan members
• To ensure health information is kept secure and patients are notified of breaches of their health data.

No, Magento 2.x / Adobe Commerce do not support HIPAA-Compliance based services

There are following below Adobe Products support HIPAA-Compliance Based Services include:

1. Adobe Experience Manager (AEM) Managed Services
2. Adobe Experience Manager (AEM) as a Cloud Service
3. Adobe Customer Journey Analytics (CJA)
4. Adobe Journey Optimizer (AJO)
5. Adobe Real-Time Customer Data Platform (RTCDP) B2P (Consumer Audiences) Prime and Ultimate Editions
6. Adobe Real-Time Customer Data Platform (RTCDP) B2C Prime and Ultimate Editions
7. Adobe Acrobat Sign Solutions for enterprise and business
8. Adobe Connect Managed Services
9. Marketo Engage
10. Workfront