[#16358] - [4.0] Migrating com_config to legacy MVC and namespaces
- Fixed in Code Base
- 31 May 2017
- Medium
- Build: 4.0-dev
- # 16358
- Diff
- yvesh:dev4
User tests: Successful: Unsuccessful:
This PR is migrating com_config to the namespaced legacy (not any more) MVC.
It's not doing a clean up on the code itself or code style etc (Which should be done independently!)
Summary of Changes
Migration to legacy MVC.
Testing Instructions
Check that com_config is still working in all places and with extensions. Also in the frontend, where it takes care on module and template editing.
Documentation Changes Required
Maybe
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_config |
That might be a good thing
Not my summer of code project. That never went beyond a Pull Request updating a lot of this stuff. This was the year before me.
| Labels |
Added:
?
|
||
We need to think about if we want to migrate the existing menu items over. It's a dodgy precedent to set. But potentially doable.
We want to search for index.php?option=com_config&view=config&controller=config.display.config
or
index.php?option=com_config&view=templates&controller=config.display.templates
and replace them with the new links (and this is always the non-sef path too as it's the menus table so should be ok)
| Category | Administration com_config | ⇒ | SQL Administration com_admin Postgresql com_config |
@joomdonation I think this is ok as a first pass - it definitely needs some further work - but this is 'good enough' as it is
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-05-31 17:18:38 |
| Closed_By | ⇒ | wilsonge |
and in one pr george summer of code is deleted :)