I'm trying to create a module for my Magento 2 installation because I need to change some behaviours. I followed this guide to build a module which basically (at the moment) just wants to override a method for GroupManagement class in Customer Model. The matter is that when I run the setup:upgrade command everything seems to be ok, but then every request to the site gets an exception. I looked into logs and found that my class is not found (there is a ReflectionException "class does not exist"). What it seems to me is that something is missing telling the autoloader to load my module's namespace. Should I manually update some autoloader.php file? I don't think that's intended as a solution, but what am I missing?
2 Answers
From your comments I gather your module is being developed under app/code and you are not following psr-0 conventions for your classes (code is under a custom src folder inside of your module). This is fine, but still, since composer is not aware of modules installed under app/code, it won't know about your psr-4 definitions.
As a workaround for that, you could enter your psr-4 classpaths in the project composer.json (the one which is found in the project root), and then run composer dump-autoload to regenerate the vendor/autoload.php and all its related files. Even if it is not the cleanest solution, it would still work in your case.
But very important to note: your should never manually edit the autoloader files, since they are re-generated every time you install a new module via composer for example. Also, you probably don't want to put your vendor folder under version control, your edits would be lost then.
-
Sorry for seeing your answer just now. Anyway I had tried without
srcfolder too, and classes were not found as I wrote in my comment on Apr 27 at 16.49 CET. Maybe I'm wrong, but what I see is that Magento can automatically detect classes that are directly placed underapp/code, and not underapp/code/<vendor>/<module>. So I didn't find a solution other than editing the projectcomposer.jsonand regenerate autoload files. Thanks for your help, anyway! Commented May 5, 2016 at 6:03 -
I do have a composer.json in my module root, in which I define an additional PSR-4 namespace, but it does not get picked up on regenrating the autoload classes. Thus: my classes that obey the Magento 2 structure are found, but an additional library (code commoon to a number of extensions for different webshops) that comes with it, is not found. Commented May 11, 2016 at 16:01
-
Maybe enter a new question, and post your code. I can try to help you... From a comment it's hard to understand what's happening.– fmrngCommented May 11, 2016 at 22:08
There can be multiple reasons but below could be among them...
1. Check the name space of your classes..
2. give the permission of your Magento directory according to the official document.
magento official document for permission set
3. And obviously all the classes should start with uppercase with same file name.
4. Classes should not contain UNDERSCORE(_).
Hope this will help, please let me know if issue still persist...
answered Apr 25, 2016 at 13:03
-
Thanks for answering, but all the points you stated seem to be ok. I guess the matter is I need something to put my module's namespace in autoload. How can I get it? Commented Apr 25, 2016 at 15:19
-
you don't need to put anything in autoloader.php, We are not suppose to make any changes there. May be I can help you better if I can see your codes along with directory path.. Commented Apr 26, 2016 at 10:09
-
Please take a look at my comment above (6th comment to the question), thanks! Commented Apr 27, 2016 at 14:26
-
Thanks @mohammad-mujassam.
Classes should not contain UNDERSCORE(_)helped me Commented Aug 3, 2017 at 7:14
developermode? Also, have you tried to delete everything undervar/generation?app/code, there is usually no need to edit the autoloader (for sure you shouldn't do it manually), as long as you follow class path conventions, e.g.app/code/[Company]/[Module]/YourClass.phpfor class\[Company]\[Module]\YourClass.