For years now, using the backend "template/create overrides" process has worked the way it was intended to: to prevent the overwriting of modified files during updates. This has worked for years.

The expected result of creating an override is to duplicate the "default" view of a module or component in a place (HTML folder) so that it can then be modified and used form that location. The duplicate looks exactly like the original when you start. That's the pont.

Anywhere you go that discusses Joomla and overrides will reference this process. "template/create overrides" is built around that process.

I work with Joomla every day. I have for about 15 years or more. I'm not an expert and I don't know everything, but I can say for sure I don't believe Joomla, or website development using it should be any more difficult or compllicated than it absolutely has to be.

When you diverge from the established functionality (that clearly is intentional because it's included in Joomla 4) to do your own thing, such as breaking this built in functionality (no, you didn't break it: you just rendered it useless - same thing), you effectively cut off a key functionality by moving it somewhere else that someone who didn't know, would have great difficulty finding or being aware of and then having the skills necessary to move the files manually. I have them, but I'll guarantee a lot of people don't, and many that do may not be comfortable doing it.

This does not serve anyone. It adds a level of complexity that is truly unnecessary. The argument: https://www.joomshaper.com/documentation/helix-framework/helix-ultimate-2/template-views-override "3. Now you can edit & customize default.php file without fear that the next update will overwrite your changes." describes the existing functionality. It's added nothing but complexity and made it harder.

So, now that I have no choice in this process, I've created an override of the basic login module on the backend like always. I navigate to the folder the file is created in "html/mod_login/default.php"

and rather than getting the actual default.php for the module, I get: "require HelixUltimate\Framework\Platform\HTMLOverride::loadTemplate();" and nothing else.

Now, because I know you guys have hijacked the entire override process, I will manually go out to the actual module folder "modules/mod_login/tmpl" and manually copy the files to create the override - except now I put those files in "overrides/mod_login", not "html/mod_login".

Either way doesn't work. If I move the files to "html/mod_login" or "overrides/mod_login" I do NOT get the duplicate layout of the module I should get.

This "overrides" folder is a terrible idea. First, it duplicates an existing and established process built into the core and replaces it with a more complicated and infinitely less user friendly process that clearly doesn't work as it's supposed to.

Add to that the potential for conflict with other compoinents and/or modules.

This doesn't work. At all. When I create an override, I should get a duplicate of the layout being overridden. Period. Nothing more. No more adjustments. That is the way it's designed.

THAT'S NOT WHAT HAPPENS.

The idea that you have now created a much more complex system that is going to require more time to make work the way it should out of the box is the single biggest reason I have taken the time to write this. ![]https://upload.picpaste.me/images/2021/09/27/overrides-issue.jpg