The following modules are outdated

[nomuprive]

Hi. Keep getting the error below in Magento exception error log

The following modules are outdated: Goomento_Core schema: current version - none, required version - 1.0.1 Goomento_Core data: current version - none, required version - 1.0.1 Goomento_PageBuilder schema: current version - none, required version - 0.1.6 Goomento_PageBuilder data: current version - none, required version - 0.1.6 at /home/.../public_html/vendor/magento/framework/Module/Plugin/DbStatusValidator.php:66)"} []

[haihv433]

Hi @williambize Thanks for letting us know the issue

Here is a checklist you can do to resolve this quickly

• Update the Goomento - Page Builder to the newest via Composer
• You can modify the table setup_module, find the records that stored the version of the current module by running this command SELECT * FROMsetup_moduleWHEREmoduleLIKE '%Goomento%' Then delete these all, running the upgrade command once again.

If the issue persists, please help us to provide some information,

• Which version of Magento that you install it
• Which version of Goomento - Page Builder did you get (the version on the composer.json - for packaging)

Thanks

[nomuprive]

Hello @haihv433 Thanks for the support.

I used the command lines below to install your Module, so I think it should download the latest version...

composer require goomento/module-page-builder

I also ran the command below...

php bin/magento module:enable Goomento_PageBuilder php bin/magento setup:upgrade php bin/magento setup:static-content:deploy

Do I have to add the version before Composer will know which one is the latest? It seems like Composer is not able to recognize the version of the Module at all...

Thanks

[haihv433]

Hi @williambize You don't need to specify the version in the command line

can you run this command to get the current Magento version then paste it back here?

php bin/magento --version

[nomuprive]

My version of Magento is 2.4

[haihv433]

Hi @williambize

I tried to replicate the issue on the M2.4.x instance but seems everything is okay, We will consider checking more,

For now, we suggest you

1. Run this command to update Goomento - The Magento Page Builder

composer update goomento/module-page-builder if you are using the old version

For checking the module version, please run

composer show goomento/module-page-builder

The newest version is 0.2.2 (at the time we posted this comment)

2. Manual change of the table setup_module

References: https://github.com/Smile-SA/elasticsuite/issues/740#issuecomment-567594467 https://magento.stackexchange.com/questions/301595/i-got-this-issue-the-following-modules-are-outdated Thanks

[nomuprive]

Hi. Check the screenshot below. I'm not sure why Composer is not recognizing the versions of your module... It seems Composer is actually trying to remove the Module...

When I run

composer update goomento/module-page-builder

It gives me: https://prnt.sc/wQBHSJbnuj9U

And when I run

composer show goomento/module-page-builder

It gives me this error: https://prnt.sc/m4X9hXvpZ8ba

Also, while Magento system is showing Composer could not find the module, error log is still showing that the required version is 1.0.1

Please check error below...

[2022-04-19 06:54:26] main.CRITICAL: Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory. The following modules are outdated: Goomento_Core schema: current version - none, required version - 1.0.1 Goomento_Core data: current version - none, required version - 1.0.1 {"report_id":"cf8028617858b998238f4ad01322b1ac1df7946fdaad658d5349c0b9c9c34422","exception":"[object] (Magento\\Framework\\Exception\\LocalizedException(code: 0): Please upgrade your database: Run \"bin/magento setup:upgrade\" from the Magento root directory.

[haihv433]

This is wired, Did you also add this module in app/code/Goomento Can you run composer search goomento/module-page-builder then show what you see on the console Btw, you can connect directly with me for faster checking Skype: live:huynhvanhaipro

[haihv433]

I closed this issue, since there is no activity so far