[Resolved] Mageplaza_Core has been already defined

Question

[Resolved] Mageplaza_Core has been already defined

imsamthomas opened this issue 8 years ago · 45 comments

imsamthomas commented 8 years ago

Few customers reported to us the following issue:

Issue

Module 'Mageplaza_Core' from app/code/Mageplaza/Core has been already defined in vendor/mageplaza/core-m2.

Explain

There are 2 different ways to install Mageplaza extensions:

Copy and paste: download from our store https://www.mageplaza.com
Composer command

Because you installed Mageplaza Extensions via composer and now install by copying a package from our store.
In this case, it conflicts Core module. Now we are going to resolve this issue in 3 simple steps:

Solution

Step 1: You should DELETE Core module from

app/code/Mageplaza/Core
vendor/mageplaza/core-m2 (if any)

Run the following command:

composer remove mageplaza/core-m2
rm -rf app/code/Mageplaza/Core
rm -rf vendor/mageplaza/core-m2
composer dump-autoload

Step 2: Now install Mageplaza_Core again run upgrade command line to resolve the issue.

composer require mageplaza/module-core
php bin/magento setup:upgrade

Step 3: Check result

Check the result, if there is still an issue, feel free to leave a comment here or contact us

Answer 1 · 2017-05-06T14:34:32.000Z

I get
Autoload error: Module 'Mageplaza_Core' from '/vendor/mageplaza/module-core' has been already defined in '/vendor/mageplaza/core-m2'

by deleting 'vendor/mageplaza/module-core' doesn't work though...the upgrade command doesn't even run.

Answer 2 · 2017-06-07T08:46:14.000Z

Same result as nsid32: nothing works and upgrade not working neither

Answer 3 · 2017-06-07T08:51:36.000Z

Hi @alejandromartincruz ,

You should follow the solution mentioned above:

Solution

See #3 (comment)

Answer 4 · 2017-06-07T08:55:10.000Z

I deleted app/code/Mageplaza/Core and when I type the command php bin/magento setup:upgrade
Then I got the error:
Autoload error: Module 'Mageplaza_Core' from '/var/www/html/magento2/vendor/mageplaza/module-core' has been already defined in '/var/www/html/magento2/vendor/mageplaza/core-m2'.ubuntu@ip-175-33-22-175:/var/www/html/magento2$

Answer 5 · 2017-06-07T08:56:21.000Z

You should delete both folders:

app/code/Mageplaza/Core
vendor/mageplaza/core-m2

Keep folder vendor/mageplaza/module-core

Answer 6 · 2017-06-07T09:01:49.000Z

Ok, so I delete vendor/mageplaza/core-m2

and then:

ubuntu@ip-175-33-22-175:/var/www/html/magento2$ php bin/magento setup:upgrade
Autoload error: Module 'Mageplaza_Core' from '/var/www/html/magento2/vendor/mageplaza/module-core' has been already defined in '/var/www/html/magento2/vendor/mageplaza/core-m2'.ubuntu@ip-175-33-22-175:/var/www/html/magento2$ php bin/magento setup:upgrade
PHP Warning:  require(/var/www/html/magento2/vendor/composer/../mageplaza/core-m2/registration.php): failed to open stream: No such file or directory in /var/www/html/magento2/vendor/composer/autoload_real.php on line 71
PHP Fatal error:  require(): Failed opening required '/var/www/html/magento2/vendor/composer/../mageplaza/core-m2/registration.php' (include_path='/var/www/html/magento2/vendor/phpunit/php-file-iterator:/var/www/html/magento2/vendor/phpunit/phpunit:/var/www/html/magento2/vendor/symfony/yaml:/var/www/html/magento2/vendor/magento/zendframework1/library:.:/usr/share/php') in /var/www/html/magento2/vendor/composer/autoload_real.php on line 71

vendor/mageplaza/module-core folder it's still in its place

Edit: finally it worked, but first I had to remove the line of the las module I added to composer.json

Answer 7 · 2017-07-18T12:28:07.000Z

Delete vendor/mageplaza/core-m2.
run command composer dump-autoload
run command php bin/magento setup:upgrade

Answer 8 · 2017-07-24T16:53:20.000Z

if you're using any mageplaza language packs core-m2 might be required... so that makes these two modules conflict 😠

Answer 9 · 2017-07-24T16:53:38.000Z

why are there two versions of the core module floating around?

Answer 10 · 2017-08-08T01:13:25.000Z

what's the permanent solution here? Everytime I do a new composer require core-m2 gets back in the mix

Answer 11 · 2017-08-08T01:44:34.000Z

@blizam

To Resolve `core-m2`

See #3 (comment)

Answer 12 · 2017-08-15T20:57:53.000Z

@eddyonboard

this is the real correct answer. Many thanks for sharing!

Answer 13 · 2017-09-09T16:01:51.000Z

Is there a final solution?

For the moment every time I do some setup:static-content:deploy or setup:upgrade I get the following message:

Autoload error: Module 'Mageplaza_Core' from '/mage2/vendor/mageplaza/core-m2' has been already defined in '/mage2/vendor/mageplaza/module-core'.

The only way to get around it is like @eddyonboard described, installing the new module-core is ending up in the same problem because this installs core-m2 version 1.3.1

Answer 14 · 2017-09-10T05:48:25.000Z

It's a combination of @eddyonboard and @imsamthomas posts I as it's resolved for me currently.

Delete vendor/mageplaza/core-m2
composer remove mageplaza/core-m2
composer dump-autoload
composer require mageplaza/module-core
php bin/magento setup:upgrade

Answer 15 · 2017-09-10T10:16:18.000Z

@blizam I can confirm your answer is perfectly valid 👍

Answer 16 · 2017-09-10T11:37:01.000Z

However I can not confirm. Every time I run composer and a dependency check is made, it will reinstall mageplaza/core-m2
So I searched trough all mageplaza extensions (all installed by composer!) and found out that the norwegian language pack requires mageplaza/core-m2 in its composer.json which is the reason why core-m2 is installed again and again no matter what I do.

So my solution was to run:

composer remove mageplaza/magento-2-norwegian-language-pack
composer clear-cache
composer remove mageplaza/core-m2
composer dump-autoload
php bin/magento setup:upgrade

I also created a pull request to correct the composer.json

Answer 17 · 2017-09-11T00:06:40.000Z

Thanks @blizam @alen12345 @plastikschnitzer
I have updated the solution on top of this topic: #3 (comment)

Answer 18 · 2017-10-13T08:13:13.000Z

Information for anyone using theme Porto.

If you use Porto theme you will get Mageplaza_Core has been already defined error.

app/code/Mageplaza/Core
app/code/Mageplaza/LayeredNavigation

are included in the Porto installation.
I did not use the layered navigation so I followed #3 (comment)

I did these steps.

rm -rf app/code/Mageplaza/Core
php bin/magento setup:upgrade

I dont know if it's ok to leave the app/code/Mageplaza/LayeredNavigation but it's disabled so it should not be any problem.

Answer 19 · 2017-10-13T08:15:43.000Z

@inelukipg It's all right, as long as you disable it (via module:disable), it won't run in any case.

Answer 20 · 2017-10-13T08:21:51.000Z

@gixid192 Ok! Do you know why there is different core modules from Mageplaza with different names?
module-core, Core, core-m2?

Answer 21 · 2017-10-13T16:15:20.000Z

@inelukipg Sorry if that made you confused.

As our business grows, we changed the name time to time. The reason is Magento offers 2 different ways of installing extensions so some installed by Composer, others prefer copy/paste method.
We are trying to fix this issue by instructing users to install core-module by composer, as you can see from our user guide here: https://www.mageplaza.com/install-magento-2-extension/

Answer 22 · 2017-10-16T07:39:30.000Z

@gixid192 Ok, but vendor/mageplaza/module-core is the latest version?
I mean if I decide to buy another extension from Mageplaza and install via composer it will work with that core module?

Answer 23 · 2017-10-16T08:16:04.000Z

@inelukipg oh yes, that's the latest name if you are using Composer.
You can just follow our user guide (the link I gave above), everything will be all right.

Answer 24 · 2017-10-27T08:40:05.000Z

follow @inelukipg's answer #3 (comment) if have yourstore theme and try to install a lang package

Answer 25 · 2017-11-15T23:28:11.000Z

I can't not remove your core plugin I'm getting this error and Mageplaza_Affiliate is disabled as well as Mageplaza_Core. after doing this I also tried to remove the extention by doing composer remove mageplaza/module-core and I'm getting this error now

PHP Fatal error: Class 'Mageplaza\Core\Helper\AbstractData' not found in /chroot/home/newcloud/cloudvdesign.com/html/app/code/Mageplaza/Affiliate/Helper/Data.php on line 20

Fatal error: Class 'Mageplaza\Core\Helper\AbstractData' not found in /chroot/home/newcloud/cloudvdesign.com/html/app/code/Mageplaza/Affiliate/Helper/Data.php on line 20

We want to remove this plugin completely because it simply doesnt work

Answer 26 · 2017-11-16T01:53:22.000Z

Your store cannot run without Mageplaza_Core module.

You removed the old Core module, then you should install the new one via composer:

Step 2 : Now run upgrade command line to resolve the issue.

composer require mageplaza/module-core
php bin/magento setup:upgrade

Answer 27 · 2017-12-19T09:41:16.000Z

@imsamthomas your solution on top works well for one time, but you need to update the Norwegian language pack to avoid the problems, every composer command re installs core-m2.

Please merge the pull request asap - mageplaza/magento-2-norwegian-nynorsk-language-pack#3

Answer 28 · 2017-12-28T13:52:07.000Z

@dinkeronline thanks for notifying us here.
We have pulled the pacakge.

Answer 29 · 2018-02-09T09:34:51.000Z

@imsamthomas Can you help me for install sociallogin_v2.4.0.1_ce_mageplaza extension in magento 2 store.in sociallogin_v2.4.0.1_ce_mageplaza extension ZIP file i have 2 folder -app, lib.i have read your all reply for install this extension(sociallogin_v2.4.0.1_ce_mageplaza).but i need help
Can you tell me Step by step process for install this extension.

and Mageplaza_Core module i have zip file.when i have extract this file i have found
Block, Controller, etc, Helper, i18n, Model, Observer, view folder. how to install this module. i mean here is not app folder etc.

Answer 30 · 2018-02-16T21:30:11.000Z

just follow this

Delete the following files, folders::
app/code/Mageplaza/EXTENSION_NAME

Run the following command line::
php bin/magento setup:upgrade

Answer 31 · 2018-05-09T10:27:55.000Z

solution indicated by @imsamthomas worked. Thx!
Does this means that magento comes already with that module preinstalled? cuz I did not uploaded any module directly, but only through composer..

Answer 32 · 2018-08-06T14:13:09.000Z

thanks @inelukipg, it works.

Answer 33 · 2018-11-10T01:32:21.000Z

im getting
Module 'Mageplaza_Core' from '/app/code/Mageplaza/Core' has been already defined in '/vendor/mageplaza/module-core'.

not core_m2

Answer 34 · 2018-11-10T07:03:33.000Z

@thrmda The core_m2 is the old name, you can follow the insturction by replacing it with the new name module-core

Answer 35 · 2019-02-16T09:48:33.000Z

install midnight-commander[dot]org and delete
#mc
/var/www/html/magento/app/code/Mageplaza/Corefoder via 'F8' keys just all

Answer 36 · 2019-05-03T14:58:40.000Z

It worked for me .. thanks buddy

Answer 37 · 2019-05-08T05:21:11.000Z

Solution worked for me and saved my butt. Thank you so much!!

Answer 38 · 2020-06-07T22:32:49.000Z

When I implement this resolution (using porto) I get a lot of errors when running: php bin/magento setup:static-content:deploy -f

For this reason, I have had to make sure to not use any other mageplaza extensions, unfortunately :( It was tested on 2.3.3. We are on 2.3.5-p1 now and I will test one more time, but I expect the result to be the same.

Edit: I have tried on 2.3.5-p1 and it is now working properly.

Answer 39 · 2020-08-12T10:58:44.000Z

Thank you for the solution provided by @imsamthomas it worked perfectly, im using magento CE 2.3.5-p1 with Porto theme, production site. You saved my day!

Answer 40 · 2020-08-26T15:08:41.000Z

I got an error that Class Mageplaza\CustomerApproval\Console\Command\Approve\Interceptor does not exist. Please specify the solution

Answer 41 · 2020-09-04T15:31:46.000Z

If using Porto & Mageplaza Search module, try this:

composer remove mageplaza/core-m2
rm -rf app/code/Mageplaza/Core
rm -rf vendor/mageplaza/core-m2
rm -rf app/code/Mageplaza/Search
composer dump-autoload

composer require mageplaza/module-core
php bin/magento setup:upgrade

Answer 42 · 2020-09-04T16:38:17.000Z

For Mageplaza it is mandatory to have the Mageplaza_Core module.
After that, all errors will be resolved.

Thanks

Answer 43 · 2020-09-04T19:57:02.000Z

For Mageplaza it is mandatory to have the Mageplaza_Core module.
After that, all errors will be resolved.

Thanks

I had it, but in spite of having the Mageplaza_Core module, errors can still occur, because of various reasons such as using theme such as Porto where the Mageplaza_Search module comes bundled etc.

Answer 44 · 2020-11-24T01:22:11.000Z

im in magento 2.4. your module supports only magento 2.3.x ????
please help me. Thank you

Answer 45 · 2022-09-08T13:39:01.000Z

Hi, I followed the instructions above and everything worked till the sudo php bin/magento setup:upgrade, I get one last line that says "Invalid entity_type specified: themelayout_maincontent " should I be concerned. Thank you in advance.

Issue

Explain

Solution

Solution

To Resolve core-m2

To Resolve `core-m2`