Feeling Lucky
No Code Attached Yet
[#35770] - [3.x] Upgrade override information
- Closed
- 1 Feb 2022
- Medium
- Build: 4.0-dev
- # 35770
Upgrading a site today to j4 and everything went perfectly - woohoo
The one bit I struggled with was the site template - no surprise there EXCEPT the site template actually worked perfectly it was the overrides of core modules and components where it fell down. Something I had completely forgotten I had created.
Perhaps other people will have the same problem and we can save some time for them. Either by checking if there are any in the upgrade check and informing you OR something that @laoneo did with dpcalendar and renamed the html override folder so that the files were still present but not loaded.
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
brianteeman
- comment
- 7 Oct 2021
using the override manager would be the perfect solution. even a very simple article override from j3 will break a site in j4
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-02-01 23:02:24 |
| Closed_By | ⇒ | brianteeman |
Hmm I'm not sure whether renaming the html folder is a wise choice for the core as we even decided to intentionally break sites and not disable for example critical extensions on upgrade.
What kind of information do you have in mind about the pre Upgrade checker?
I have not checked the details of the new Override manager but couldn't that be triggered somehow to show a message within J4? Maybe something like "we found overrides that have not been checked yet for J4 compatibility"? Given that this is the place starting from 4.0 for overrides anyway right?