Home

Welcome to the gsoc18_override_management wiki!

Project goal

This project adds the feature to Joomla which check for upgrades, if the template file is changed where an override exists, it notifies the user that one of core file of his template overrides is changed with the update, to avoid security issues or functionality issue and he can adjust his override before anyone can notice.

Reference: https://summerofcode.withgoogle.com/

Documentation: https://docs.joomla.org/J4.x:Improved_Override_Management

Reviewed Project Timeline

Phase 1

27 April - 14 May

Community Bonding Period

• Getting familiar with Joomla MVC, Plugins, extensions.
• Studying core API and external API.
• Discussing the architecture of project with mentors.

Phase 2

14 May - 3 June

• Discussing a mechanism to find correct core files which were updated in Joomla! update where override exists.
• Implementing the decided mechanism.

Phase 3

4 June - 24 June

• Discussing diff-view to implement with template component.
• Short report about the decided mechanism.
• Implementing the decided mechanism.

Phase 4

25 June - 15 July

• Discussing notification to inform the user and informations should to be displayed in notification.
• Overview which contains list of override files which was updated in Joomla update. And some more functionality.
• Short report about the decided mechanism.
• Implementing the decided mechanism.
• Implementation and testing.

Phase 5

16 July - 29 July

• Writing tests and documentation for all new features.
• Improving and finalizing the documentation.
• Fix bugs and other issues.
• Creating video documentation for a tutorial example to use this feature.
• Implementation, testing and complete product with documentation.

Phase 6

30 July - 5 Aug

• Final Wrap-up
• Final week, submitting final work.
• Final Submit