I think you can do that in J3.7 beta3 and later.
Take a look at #11166

Thanks for the link.

I do not understand why tags would not default to /tags/alias even without a menu.

This needs to be simple and not complicated for non-developers.

The default core routing without any menu items defaults to /component/<component_name>/<view_name>

It's not just tags doing that. Problem is routing is massively tricky and doesn't support configurable URI schemes without the menu system basically. It gets even trickier if you're trying to consistently generate routes to the same content across components.

So there's still a lot of room for improvement in general. But the long and short of it is you really need menus to get things "just right" for now.

Could the component automatically create a menu item when a user creates their first tag (if a tag menu is not already present)?

You get into a lot of arbitrary behaviors then. Do you create a new single tag item for each tag? Where in the tree do you put it? Not an easy workflow to start mapping out. It's probably a good UX win to come up with something, but considering how much configuration has to go into defining the workflows it might be better off as a plugin versus a default core behavior in com_tags.

And which menu would you put it in? And what happens when you delete the
tag?

On 27 March 2017 at 18:38, Michael Babker notifications@github.com wrote:

You get into a lot of arbitrary behaviors then. Do you create a new single
tag item for each tag? Where in the tree do you put it? Not an easy
workflow to start mapping out. It's probably a good UX win to come up with
something, but considering how much configuration has to go into defining
the workflows it might be better off as a plugin versus a default core
behavior in com_tags.

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

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

Offer the ability to remove menu/category levels for alias only URLs
domain.com/my-alias

That would require that an alias has to be unique site-wide (instead of category wide like today) and you would need a way to look them all up to determine which component it comes from. For that, you would have to completely rewrite the way routing and components work. You would need an "alias" table with at least an "alias", "component", "view" and "item_id" field. It would take away a lot of the flexibility we have today.

Thanks for the feedback/insight @mbabker @Bakual

So basically, the current tag system is robust but not simple to use (create tag/select > output clean/non-CMS specific URL)

My goal is to help make Joomla! more content-centric and user-friendly.

The issues you're expressing have nothing to do with tags specifically. The same issues can manifest regardless of component and workflow, just few components have a "horizontal" interaction with other components like tags do (a lot of these issues highlight themselves the most when you're doing something that involves cross-component handling). You're digging deep into a box regarding the routing system, the menu system, and a general user workflow of creating items with the desired URI structure.

So ya, it's a lot to think about and take in, but it's not isolated to a single use case. You just happened to highlight the one that makes this conversation easiest to have.

Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/14915

Closed as there is no Content.

Set to "open" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/14915

Haven't seen Content in opened Comment.

By continuing to rely on the Joomla menu system we will always fall back on the same problem of multiplying elements to link the same content. These problems will always manifest themselves as external components to Joomla ?, I think it is still crazy that we have to create 1000 elements of tags and then create 1000 times in a menu for everything to work correctly, this will occur in all components External to Joomla ?.

What @heyjoecampbell comments on creating a menu item would be a way to save work by creating elements within the site.

Regarding the questions of Mr. @brianteeman ,

And which menu would you put it in?

If this could be achieved it would be fantastic to do so in a menu called invisible, from which all tags created from the tags component could be hung.

And what happens when you delete the tag?

To get that removing the tag from the tags component or from the invisible menu to remove the label from both sites would be fantastic.

I know that everything may sound like utopia, but they would have to raise this issue more either for the label component in question or for other components in the future of Joomla.

As long as we continue to depend on the "All-Powerful Menu" we will have to repeat thousands of actions to reach the same destination. :(

I know it's not exactly the same issue but I'm going to close this issue in favour of #13598 and use that to discuss tags routing more generally