The alias placeholder text Auto-generate from title is now misleading.

@Quy I don't remember which text was there before this function was removed.
But as far as I can remember, placeholder was same.

This change was intentional why are you reverting it

@brianteeman
The reason is simple. Convenience. In my projects, I very often use system menu items. And it is not uncommon that their alias coincides with existing or created ones, so as to avoid problems they have to write each time with their hands. And a similar problem arises not only for me. And after each update, you have to re-write the hack.
The larger the project the more there are system menu items. And alias these points are not needed.

In addition, I missed the discussion on the topic of deleting this function, well, or just do not remember, but I clearly remember my inconvenience caused by this cancellation.

I do not insist on accepting this PR, but in my opinion and the opinion of my friends, this function is very useful. I can show a screenshot of the site where about 20 menus and about 500 menu items, many of which are system menu items, but I think you'll roar to me on the floor.

The reason for the change was so that users who have real menus as sub menus of system menus have real data in the menu path and not dates eg

Example.com/system/sports/article.html
Instead of
Example.com/2018-01-17/sports/article.html

@brianteeman In such cases, you can fill in the alias field, this is much more logical than when you need to fill out the ailas field for the menu item delimiter. Which in action performs the function of a visual separator. Or for an external link.

I think so there is a page in the url that the visitor should have the opportunity to go to it. And where will I go if I go to this url Example.com/2018-01-17 ?
I'm not an SEO specialist, but it's not true to mine.

Now I know reason =)

I have tested this item ✅ successfully on 37cae77

No, this is very bad.

Users not knowing how the menu structures work end up killing their SEO.

A better solution would be to test the Alias on pre-save then add a unique 5digit number if one already exists.

For reference #10756

The problem occurs when you create a component menu item . Every time one has to remember whether there is a heading item with such alias or not. . And then every time you look for him. then change alias. then again change alias, then again and again, And in a few days the story repeats itself

System menu items should not be present at all in the site structure. They are more of a decorative nature, or refer to third-party resources. But somehow everyone forgot about this.

Sorry but I completely disagree with your view on the system menu alias

No that's completely wrong @Septdir the site structure is completely defined of the menu item and how it should be done. Even more so now you can create content form the menu item level.

From an SEO Perspective you need to be having unique aliases which following the correct pattern. If you are having multiples of the same name at the same level there something if very wrong with your build in my opinion. I can't see at what point you would need this? Maybe at the level of a footer or hidden mobile menu, but again when you build that you know you are using system aliases you can can type in menuname-alias1 for instance sake.

@dgt41 what are your thoughts on writing a neat little ajax validator pre-save for the menu item alias validation?

@brianteeman I understand your position, you brought good arguments. At me the vidin have at you the. You look from the point of view of the beginner to use, I also look from the point of view of administering sites where hundreds of menu items, more than half of which system menu items in particular "Menu Item Alias" and "alias from title" give me discomfort.

@tonypartridge menuname-alias1 for 20-30 menu items. Are you seriously?

what are your thoughts on writing a neat little ajax validator pre-save for the menu item alias validation?

This is a great idea, but does not solve this "problem".

If PR does not accept I will write a system or content plugin without any problems.

If you have a site with hundreds of menu items then you are really doing it wrong

sorry for that - its not my right to tell you if you are doing something right or wrong but joomla always has to consider the needs of the many more than the needs of the few

If you have a site with hundreds of menu items then you are really doing it wrong

Simply sites are large =) and there are a lot of different sub menus.

sorry for that - its not my right to tell you if you are doing something right or wrong but joomla always has to consider the needs of the many more than the needs of the few

That's all right.
It's just that almost all my friends complain about this, so I decided to try PR.

If the issue is exhausted PR can be closed.

I do not regret having tried it. I did this PR very quickly.
Now I can safely create a plugin. I think it's even better. Maybe I will not even use the current date for alias and I'll think up something more interesting.

PS I really liked the idea with ajax checking alias. It would save a lot of time.

I think your reasoning is right to a point i.e. we validate the data before submitting the form. Then you know you need to change it, its just how we go about doing that as a core solution.

On 5 Dec 2017, 21:52 +0000, Igor Berdichevskiy notifications@github.com, wrote:

If you have a site with hundreds of menu items then you are really doing it wrong
Simply sites are large =) and there are a lot of different under the menu. Though in what you are right to do such sites on joomla not the best invention.
sorry for that - its not my right to tell you if you are doing something right or wrong but joomla always has to consider the needs of the many more than the needs of the few
Nothing wrong.
It's just that almost all my friends complain about this, so I decided to try PR.
If the issue is exhausted PR can be closed.
I do not regret having tried it. I did this PR very quickly.
Now I can safely create a plugin, knowing that I tried. I think it's even better.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@tonypartridge

we validate the data before submitting the form.

It's really much more convenient than checking the data after sending.
There is one shortcoming. And what if two administrators at the same time will check the same alias. For example
One checks alias main-menu-seperator-1 and the second administrator checksmain-menu-seperator-1. After the error, both change the number by 2.
The situation is of course absurd, but possible

It is, but we then have the serverside validation we currently have which it would spit an error should it fail.

Yes you are right.

@Septdir
If you are satisfied with the replies, please close PR.

Thank you for your answers, the question is settled.