In #4908 @philsward suggested that there was a need to implement the same feature to include taxonomy terms:
Taxonomies are used for a lot more than tagging content; for example they can be used as select lists. This means that currently, any taxonomies that you don't want to be indexed, have to be added as a disallow to the robots file. ... The architect could opt to remove the path field so there is no "public" alias.
In #100 we introduced a "Hide path display" checkbox in the "Display settings" tab when configuring a content type:
The Drupal version of the contrib module that offers this functionality already supports more entities:
Supported entities
This project includes sub modules that are responsible to add this behavior to different entities. The currently supported entities are:
- Nodes
- Taxonomy terms
- Users
- Files
- Field collection
- Profile 2
- Bean
You'll only need to enable the modules that you wish to add the functionality for. More entities are likely to be supported in the future. If you have a suggestion, submit a feature request using the issue queue.
I think that we should extend this feature in core to support more entities, at least taxonomy terms.
Recent comments
We can no longer add contrib projects in the Tugboat sandboxes that we use for core PR's? Can this be fixed or is there a reason for this? We can add contrib projects to demo...
Apr 25th Weekly Meetings
The Mail System and MimeMail modules are now installed. I'll let you know if they solve the problem. Edit: Using Mail System with MimeMail I was able to send plain text emails. There is...
HTML Email treated as plain text
If you haven't already I recommend installing Mail System and MimeMail. The latter will help format emails as HTML and first helps with configuring which module will handle the formatting...
HTML Email treated as plain text