[#19870] - [4.0] Namespace content site route helper
- Fixed in Code Base
- 14 Jun 2019
- Medium
- Build: 4.0-dev
- # 19870
- Diff
- Digital-Peak:j4/ns/content/route
- Success Hound No violations found. Woof! Details
- Success continuous-integration/appveyor/pr AppVeyor build succeeded Details
- Success continuous-integration/drone/pr Build is passing Details
User tests: Successful: Unsuccessful:
Summary of Changes
Namespace content site route helper.
Testing Instructions
Open an article on the front.
Expected result
Article is displayed.
Actual result
Article is displayed.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_categories com_content Front End com_contact com_search Libraries Modules Plugins |
| Labels |
Added:
?
|
||
I was also thinking about the container. Problem is that mostly legacy code is using it where boot is not called before.
Conflicts fixed
| Labels |
Removed:
J4 Issue
|
||
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-06-14 19:35:05 |
| Closed_By | ⇒ | wilsonge |
Thanks!
I still feel that this is wrong because 3PD extensions have no way of adding entries into the extensions mapper file. This file should be something that we use to allow other extensions to function who extended non-namespaced classes. But as you say it gets the namespacing done for now and can be improved in the future.
Can you create an issue with your comments so it doesn't get forgotten
Done
Conflicts. But I want to sit on this one for a bit. I really really don't like mapping this class globally. But I need to have a think about what a better solution actually looks like - presumably something in the extensions container? :/