By David Montoya on Tuesday, 07 July 2015
Posted in General
Replies 5
Likes 0
Views 486
Votes 0
What are your thoughts on using this method to override component core with edits?

https://docs.joomla.org/How_to_override_the_component_mvc_from_the_Joomla!_core

I've been trying to find a way of playing around with the source code while not breaking functionality, and I'm a big fan of template overrides so updates still work.

I've also been looking at NoNumber's ReReplacer combined with his Sourcerer plugin, but that would still constitute some kind of core edit that could be overridden and makes an additional dependency.

Especially after seeing some posts regarding loss of customizations due to an upgrade (and potentially without backups), I think core overrides would be highly beneficial. I just need to learn the best way to go about it. What do you think?
Hello David,

This would work but I think it doesn't really make sense to override it since most of the time, every version some edits would be done on the core structures. Eventually, you end up having to update these mvc files on every release
·
Tuesday, 07 July 2015 15:51
·
0 Likes
·
0 Votes
·
0 Comments
·
While true, wouldn't this help preserve custom code to be salvaged later? One component comes to mind, ARK Editor, that requires a core edit for its custom templates. It gets overridden on every update. While I can argue that's bad coding, overrides would be a good end-user solution. :P
·
Wednesday, 08 July 2015 01:22
·
0 Likes
·
0 Votes
·
0 Comments
·
Yeah, but eventually it would defeat the purpose altogether I would rather have the codes added into the core and then use a source control system to monitor these changes
·
Wednesday, 08 July 2015 01:24
·
0 Likes
·
0 Votes
·
0 Comments
·
Source control system? Tell me more.
·
Wednesday, 08 July 2015 02:22
·
0 Likes
·
0 Votes
·
0 Comments
·
·
Wednesday, 08 July 2015 03:09
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post