Old menu looked like:

With this PR they look like:

I much prefer that we don't continue with hard coding the admin menu and
finally have a real admin menu manager that is configurable

That would be better. J3.6 itself or leave it for 3.7!

Too late for 3.6 please see #5492

Wow! That's my Sunday treat ? I'll surely read all that tomorrow and make up my mind around.

Well, in that case we may consider this small change for now. Right?

I have tested this item ✅ successfully on a2bfff3

I've tested this .
It works Successfully...
All link works Perfectly same as it works before Patched.

While revoking Permission on 'com_joomlaupdate', 'com_postinstall' and 'com_installer' it hidden for the respective User.

This PR has received new commits.

CC: @zafarnayab

Can we remove label "Language Change" as this no longer requires one!

Removed as requested (note it is still too late for 3.6)

Well, if protocols says I must obey.

May I ask under which specific reason this is late, coz IMO, this is just a reorganisation of existing menu items only. No additions, no removal of anything at all and no b/c break, no new feature. Just visual change.

I assumed the language freeze was the issue, hence I modified. I must be missing something, please enlighten me.

About the backend menu manager (i had a look at #5492), it sounds great to me and that I'd gladly work on if suggested/assigned to. And that I think is too late for now and should be considered only for J3.7.

re #5492 I really want to see that happen so any help i can give you I will

re this PR my understanding that as we are in beta stage then we are
"feature complete" see
https://developer.joomla.org/news/586-joomla-development-strategy.html

Maybe @wilsonge can expand on that

On 19 June 2016 at 11:39, Izhar Aazmi notifications@github.com wrote:

Well, if protocols says I must obey.

May I ask under which specific reason this is late, coz IMO, this is just
a reorganisation of existing menu items only. No additions, no removal
of anything at all and no b/c break, no new feature. Just visual change.

I assumed the language freeze was the issue, hence I modified. I must me
missing something, please enlighten me.

About the backend menu manager (i had a look at #5492
#5492), it sounds great to
me and that I'd gladly work if suggested/assigned to. And that I think is
too late for now and should be considered only for J3.7.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#10657 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABPH8U0mxwppI0y72Zxi_HSchvwxVomJks5qNRxvgaJpZM4IpGX7
.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

IMO, this is not even a feature, however if you think so.
This could be really helpful to people messing with the new Joomla update method vs extension installer.

For #5492. I'll soon get into a strategy as well as some programming based on the discussion there plus my understanding. I'll get back to you as and when needed.

I have tested this item ? unsuccessfully on 1b0008c

Firefox. Staging staging 2016-06-16.
Applied patch. Clicked on Manage. Clicked on System. First level closes. Second level remains open.

This PR has received new commits.

CC: @bertmert, @zafarnayab

I have tested this item ? unsuccessfully on 967145d

Problems with mobile menu.

Resize window or use mobile device to see mobile menu.

Tip Extensions. That's OK because you have the sidebar menu in next view.

Tip System. That's not OK because this is a "dead end street".

@bertmert This PR does not add anything different that is not already in
the cms.
Does it work as expected before this patch? Waiting for your images and
description.

Thanks.

See edits above.

I have tested this item ? unsuccessfully on 967145d

I confirm the findings of @bertmert

I have tested this item ✅ successfully on 967145d

I have tested this item ✅ successfully on 967145d

Tested using joomla staging branch

Made some changes against reported issue in test failures above. Please test again.

What about the hathor template? It doesnt always have to be identical but if you are moving a menu item from components to extensions in Isis then the same should be done in hathor

Ok. I'll do it in couple of hours.

@brianteeman While implementing this in hathor override, I notice the following differences in hathor vs isis. Which looks like due to out of sync changes (like I did an hour ago).

Should I update those too?
Doing so will make the override unnecessary (identical to default) so is it okay to rather remove the override?

@brianteeman I am now up and regular working for the backend menu manager as discussed earlier and I'm already half way through. I'd submit the code here as soon as I am ready with a working prototype/alpha. I am not sure if we'd make it to 3.7 but I really wish we do.

I'd need some help and guidelines. If you can spare some time please be in touch.

For now I want your ideas for menutypes (actually menu item types). For front-end they are loaded from component views and metadata xml etc. What should be the best way for backend?

Can we also have some testers for this PR, until we are ready with that better solution.

For this PR I would really try to hold off on it and see if we can get the
real one done ;) Even if it is not ready for 3.7 I dont really think we
should be changing things twice

For the real PR - great stuff - maybe if you create a github repo for it we
can discuss it there

On 18 October 2016 at 15:50, Izhar Aazmi notifications@github.com wrote:

Can we also have some testers for this PR, until we are ready with that
better solution.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#10657 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8dtdaBLK_wjYEGpxlD3SkFBZOTWOks5q1NyfgaJpZM4IpGX7
.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
https://brian.teeman.net/ http://brian.teeman.net/

Thanks @brianteeman for such quick response. You can see ongoing work here izharaazmi#1

May I ask for this now please! :)

@izharaazmi you mean for tests?

Yes

A bit too late imho for 3.7.0. Has to be considered for 3.7.1 or 3.8

I have tested this item ✅ successfully on 740cfec

I have tested this item ✅ successfully on 740cfec

RTC

This is a big change in the UI and should not be just set to RTC based on two tests that it works

My first thought here is let's do this in 4.0 and leave potentially major workflow related changes alone in 3.x in favor of stability at this point (and moving menu items is a major workflow change).

I agree

Agreed this should be moved to V4. Users won't be pleased with this change in 3.x since it's quite a workflow change.

But I think it's a great idea.

Moved to 4.0 milestone for reasons stated above.

please reassign Milestone 4.0, thanks.

please reassign Milestone 4.0, thanks.

@izharaazmi can you please resolve conflicting Files?

I would wait for the results of the UX team research into the menus

Are we ready to move on this?

Well the template team still havent completed the menu and have arbitrarily reassigned the menus etc so I guess not

Now we have the configurable admin menu and a different structure in J4 I'm going to close this for now (it totally conflicts anyhow with the xml structure for admin menus - so it would need to be completely redone to test anyhow). We can create a new version if people still feel this is a good idea later on.