Labels |
Added:
?
|
Patch tester is easy to put a message in. And I honestly put it there not because the code is broken now, but because since it is a moving target still, there's no guarantee it won't be broken.
Putting those messages in core would add a lot of maintenance overhead. Any known issues should easily be found with either GitHub's or our own issue tracker's search/filters.
@franz-wohlkoenig I think that's better.
It is easy to put whatever notifications we want into core, but that doesn't mean it's appropriate. And to be honest it is not appropriate to ever check into the code a warning mechanism that essentially says "this section is a work in progress, see X issue for more details".
The new media manager has not yet been merged, so I'm not going to bother styling something that'll be replaced.
This can be closed.
I'm going to leave this open. But don't expect much progress, there's no need to do this for now whilst @laoneo 's team is working on the revamped media manager. If it looks like that won't make it for J4 for whatever reason it's not a huge amount of work to go back style that
Category | ⇒ | com_media Layout |
Title |
|
@wilsonge shouldn't this be closed cause of https://developer.joomla.org/roadmap.html?
Status | New | ⇒ | Discussion |
No. Legitimate issues should not be closed just because something is a known work in progress or planned to be replaced. Because if the plan to replace it doesn't get followed up on for whatever reason, then this has to be acted upon. It's a low priority issue, but one nonetheless.
@franz-wohlkoenig - The new Media Manager is now gradually being merged into J4, so this can be closed
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-10-03 13:02:32 |
Closed_By | ⇒ | brianteeman |
Closed as requested
known Issue #14039