Timeline for Magento2 - setup:di:compile
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2020 at 14:22 | comment | added | Black | I often added plugins and I never had to run setup:di:compile after it. It worked without (developer mode) | |
| May 31, 2020 at 6:25 | comment | added | Duke | @PrincePatel Please can you answer this question magento.stackexchange.com/questions/279795/… | |
| S Jun 28, 2019 at 3:58 | history | suggested | Ricardo Martins | CC BY-SA 4.0 |
folder update for newer versions of magento
|
| Jun 28, 2019 at 1:34 | review | Suggested edits | |||
| S Jun 28, 2019 at 3:58 | |||||
| Jan 16, 2019 at 4:57 | history | edited | Prince Patel | CC BY-SA 4.0 |
added 1 character in body
|
| Aug 9, 2017 at 16:00 | history | edited | Prince Patel | CC BY-SA 3.0 |
added 110 characters in body
|
| Jul 19, 2017 at 8:32 | comment | added | Prince Patel | This can happen if your sub-class added new dependencies after the existing optional dependencies of the parent class. You can fix this by moving any new required parameter up above the optional ones. | |
| Jul 19, 2017 at 7:56 | comment | added | Raul Sanchez | Thanks! So, it is totally optional... Just one point, so it is more clear to me. In our case, setup:di: compile does not throw any error, command ends ok. It is when browsing the site, after command has finished, when Fatal Error is fired, in product view pages... so I don't really understand why not compiled code works nice but when compiling then Fatal Error happens | |
| Jul 18, 2017 at 17:17 | history | answered | Prince Patel | CC BY-SA 3.0 |