0

I am new to magento development, made a custom module Vendor: Scandiweb Module: Scandiweb_Test The naming convention is not correct so I decided to delete it, I can't run module:uninstall because its not installed from composer, I deleted the directory and the occurance in app/etc/config also checked db setup_modules, the module name is not present.

Now whatever I do I am getting this error: How do I solve this?

PHP Warning: require_once(/app/code/Scandiweb/Scandiweb_Test/registration.php): Failed to open stream: No such file or directory in /app/etc/NonComposerComponentRegistration.php on line 29
Improve this question
1
  • After deleting the folder. Did you ran setup upgrade command?
    – Vishwajeet Kumbhakar
    Aug 21, 2022 at 17:49

2 Answers 2

Reset to default
0

Go to your config.php file in the following path

app/etc/config.php

Find your module name there. If it is present then change the value from "1" to "0" and run the following command,

bin/magento setup:upgrade

If it is not present then run the above upgrade command and check if the error is still there.

Improve this answer
6
  • Already tried this before, still getting same error
    – Saad Amir
    Aug 22, 2022 at 7:00
  • Try making the module with the name provided in your error and make a registration.php file for it. Then run the upgrade command. This might fix your issue!
    – Muhammad Muiz Ather
    Aug 22, 2022 at 7:01
  • I know it will fix the error but I wish to delete the module :)
    – Saad Amir
    Aug 22, 2022 at 7:02
  • Run these commands. This will delete any previous files and make new ones. bin/magento setup:upgrade bin/magento setup:di:compile rm -rf var/di/* var/generation/* var/cache/* var/log/* var/page_cache/* var/session/* var/view_preprocessed/* pub/static/* bin/magento setup:static-content:deploy -f bin/magento c:f bin/magento indexer:reindex bin/magento c:f
    – Muhammad Muiz Ather
    Aug 22, 2022 at 7:03
  • It got solved for now, I shared in an answer, But I'll try your shared commands if I face this again. Thanks
    – Saad Amir
    Aug 22, 2022 at 7:03
0

I cleared the cache from docker terminal and run setup:upgrade, and it worked after that.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.