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
After alot of trials, i have done the obvious and translated the whole block for different languages with each property condition as follows: ->propertyCondition('langcode', 'en...
How to get the current page language?
Thanks so much! It's working now: I was able to transfer the docroot files to the containing directory without the need for a second database or any manual configuration export/import/sync...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.
Ah, I see. Sorry, I hadn't clicked the link and assumed it was the instructions for upgrading from Drupal 7. If you are simply copying a site from one location on a server to another, the...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.