Magento 2.4.2: The following modules are outdated: Perfectmakeupmirrors_PmmHead schema: current version - none, required version - 0.0.1

Magento 2.4.2: The following modules are outdated: Perfectmakeupmirrors_PmmHead schema: current version - none, required version - 0.0.1

October 11, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento 2.4.2: The following modules are outdated: Perfectmakeupmirrors_PmmHead schema: current version - none, required version - 0.0.1

Solving Outdated Module Errors in Magento 2.x

When working with custom modules in Magento 2.x, it’s not uncommon to encounter outdated module errors after making changes or running upgrade commands. This issue occurs when the schema version of your module doesn’t match the required version set by Magento.

Understanding Outdated Module Errors

An outdated module error typically appears as follows:

The following modules are outdated:
Perfectmakeupmirrors_PmmHead schema: current version - none, required version - 0.0.1
Perfectmakeupmirrors_PmmHead data: current version - none, required version - 0.0.1

Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory.

This message indicates that the setup_version field in your module’s schema.xml file is either missing or set incorrectly.

Identifying the Issue with Your Custom Module

In your case, you’ve created a custom module to add a metatag to the head of a category page. The error suggests there might be an issue with how the setup script has been defined in your module’s registration.php file or with the version number specified in the setup_version field.

Let me take a closer look at this issue:

// Perfectmakeupmirrors_PmmHead/registration.php

\Magento\Framework\Component\ComponentRegistrar::register(
    \Magento\Framework\Component\ComponentRegistrar::MODULE,
    'Perfectmakeupmirrors_PmmHead',
    __DIR__
);

Ensure that the setup_version field is correctly set in your module’s schema.xml file:

<setup_schema version="0.0.1">
  <table name="catalog_category_entity_metatag" new_define="true">
    <column name="meta_title" type="varchar(256)" nullable="false"/>
    <constraint xsi:type="foreignKey" referenceTable="catalog_category_entity" referentialColumn="entity_id" table="catalog_category_entity_metatag" column="entity_id"/>
  </table>
</setup_schema>

If the schema file isn’t present or doesn’t contain a valid setup_version attribute, you’ll encounter this error.

Correcting the Outdated Module Version

To resolve this issue, follow these steps:

  1. Open your custom module’s registration.php and ensure it is properly registered.
  2. Check if the schema.xml file exists in the root directory of your module. If not, create one with a valid setup schema version number (e.g., 0.0.1).
  3. If the setup_version attribute is present but set to an incorrect value, update it to match the current version of your module.
  4. Run the following commands in the Magento root directory:
bin/magento setup:upgrade
bin/magento cache:flush
bin/magento indexer:reindex

The setup:upgrade command will apply any pending schema changes, including those for your custom module.

Best Practices for Custom Module Development

To avoid outdated module errors in the future:

  1. Always define a valid setup version number in your schema.xml file when creating new tables or modifying existing ones.
  2. Ensure that the version numbers across the various module files (e.g., registration.php and schema.xml) are consistent.
  3. Test your custom modules thoroughly, including running the upgrade command multiple times to validate their compatibility with the Magento core.

Conclusion

Outdated module errors in Magento 2.x can be frustrating but are usually caused by inconsistencies between the defined setup version and the actual version of your custom module. By ensuring that your schema files contain valid setup_version attributes and running the appropriate upgrade commands, you can easily resolve these issues.

Remember to always define a consistent version number across all relevant module files and thoroughly test your custom modules before deployment.

For more information on Magento 2.x development best practices, feel free to explore our Magento Development Guide at Laravel Company.

Magento 2 Catalog Database Extensions

Our network