Magento Marketplace User Guide

Code Validation

During technical review, all submissions are checked to ensure that the code meets Magento standards.

  • Type

    Severity

    Description

    Error

    10

    A critical error with severity level 10 prevents an extension from passing technical review.

    Warning

    8

    A severity level 8 warning does not prevent an extension from passing technical review. Developers are encouraged to resolve any issues that trigger a level 8 warning.

    Warning

    6

    A severity level 6 warning does not prevent an extension from passing technical review. Developers are encouraged to resolve any issues that trigger a level 6 warning.

  • Code Quality Issues and Solutions

    Field

    Description

    Copy Paste Detector (CPD)

    Issue:

    The Copy Paste Detector indicates that the extension contains duplicate code from Magento native products or from other extensions.

    Solution:

    The Marketplace team will provide a list of places in your extension code that were identified as duplicate.

    If the extension is found to duplicate Magento code, review the list, and remove each instance of duplicate code. Then, upload a new package and resubmit the extension.

    Any extension that is found to duplicate code from another extension will be rejected. To prove that you own the code in question, see Magento Marketplace Support.

    Sniffs

    Issue:

    The extension contains code elements that are not allowed to be used in Marketplace extensions. See the Technical Report for a list of elements in your code that are not allowed.

    Solution:

    To duplicate the tests locally, use the MEQP CodeSniffer tool. Remove all disallowed code elements. Then, upload a new package and resubmit the extension. To learn more, see: Magento Extension Quality Program Coding Standard.

    Inconsistency

    Issue:

    The extension conflicts with other extensions.

    Solution:

    The Marketplace team will provide you with a list of the identified conflicts. Correct the code that is causing the conflict. Then, upload a new package and resubmit the extension.

    M1 Package Missing

    Issue:

    The package file was not submitted, or is missing from the Magento repository. It's possible that the package file wasn't included correctly during the migration.

    Solution:

    Upload a new package, and resubmit the extension.

    Hidden Files in Archive

    Issue:

    Hidden files were detected in the archive. It is possible that configuration files from the development environment were included in the distribution package. Such hidden files can cause configuration problems for the end user.

    Solution:

    Remove the hidden files. Then, upload a new package, and resubmit the extension.