Magento Marketplace User Guide

Technical Review

The first part of technical review is an automated process that scans your code to verify that it is free of errors and malware, and that the code was not plagiarized from another Magento extension. When the automated technical review is complete, a link to the results appears in the profile of the extension, theme, or package that was submitted for review.

  • Submit to Technical Review. The process begins when you upload an extension, theme, or shared package to Magento Marketplace.

    Code is scanned. As soon the uploaded is received, it goes into the queue to be scanned. When complete, a link to the results of the scan appears in the profile.

    Submission status updated. The Marketplace administrator reviews the submission, and updates the status according to the results of the review.

    Ready for Marketing Review. If an extension or theme passes Technical Review, the status changes to “Ready for Marketing Review.” You receive email notification that the product has passed Technical Review, and you can begin to work on the profile in preparation for Marketing Review.

    Ready for Use. If a shared package passes Technical Review, the status changes to “Ready for Use.” You receive email notification that your shared package is approved, and it becomes immediately available to be included with other extensions that you submit.

    Requires Developer Action. If a submission is rejected during Technical Review, the status changes to “Requires Developer Action,” and email notification is sent of the change. The notification includes a list of each issue that was identified during the review process. An explanation of each issue is also included in the Technical Report. A link to the report can be found on the Developer Portal under the extension.

    If your submission requires developer action, you are welcome to correct the problem, and resubmit the extension. For a description of each issue that requires developer action, see Code Quality Issues and Solutions.


Technical Report
  • 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, contact the Magento Marketplace team.

    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.

    Malware

    Issue:

    Malware was detected in extension.

    Solution:

    The Marketplace team will provide you with a list of the files where malware was identified. Remove each instance of malware in the extension code. Then, upload a new package and resubmit the extension.

    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.

    Extension Key

    Issue:

    (Magento Connect Only) The extension key must have the exact same name that was used during the packaging process.

    Solution:

    Extension names are case sensitive, and can include any combination of letters (a-z or A-Z), numbers (0-9), and the underscore character. Other characters are not allowed.

    The name of the package cannot be changed to match the extension key. The name that was used during the packaging process is stored in the package.

    The extension name cannot be changed after the extension profile is saved. If the key does not match the package name, you must create a new extension profile.

    An extension key is required for all "paid" extensions. The key is required if you later choose to make the extension available for free.

    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.

    Duplicate Functionality

    Issue:

    This extension duplicates functionality that is already available on Marketplace.

    Solution:

    Because the selection of extensions on Marketplace is continually changing, check back often so you can keep pace with the changes. Although there might not be a place for your extension at this time, an opening might become available in the future.

    We value you as a developer and member of the Magento community, and look forward to the time when you become a seller on Magento Marketplace. We are happy to provide feedback, and you are welcome to contact us to discuss potential projects, or ideas before you begin work or submit an extension to Magento Marketplace.