Support more core content entities [#2457455]

Comment #1

Sam152 CreditAttribution: Sam152 commented 23 March 2015 at 00:25

Title:

Support more core entities

» Support more core content entities

Log in or register to post comments

Comment #2

dman CreditAttribution: dman at Sparks Interactive commented 11 August 2016 at 10:05

+1, this should probably be able to manage the label of any entity.

We started doing some site build, leveraging title module (initially so that we can place an image and the date above the title on full-node view)
When extending the theme, I was hoping to make an additional view mode for taxonomy terms (to show the tag and its associated logo, which would then be shown as a rendered_entity on the pages)

Unfortunately. title support was not there to let me place a terms title into a terms view mode, where I was expecting to see it.
Investigating the code shows that conceptually, the D8 code is in place and expected to be able to do it for any entity, but it seems the UI is not there yet? I could not choose to "Display Configurable Title" for a vocab (presumably we expect to see it on /admin/structure/taxonomy/manage/*.

I have since moved on to using Display Suite to better expose additional entity fields - we need to use it to take better control of several other aspects of the render anyway - so I have an alternative for now.

Log in or register to post comments

Comment #3

Sam152 CreditAttribution: Sam152 commented 12 August 2016 at 01:07

I agree that supporting just nodes sucks. Based on what I now know with the work done on other contrib modules, I think it would be fairly straightforward to extend the settings to make this configurable on any bundle. The problem comes up in the theme layer. The entity API doesn't assume any kind of standard way of rendering the original entity label in the template. You'll see that there was a tonne of undoing and redoing to be able to hide the node title on command. Throw the new title block in the mix for the full pages, and you have an all out unmaintainable mess on your hands.

This module is potentially completely superseded by modules like display suite and panels, hence the lack of general interest. I also think that the implementation is potentially flawed. Instead of trying to make the existing label base fields display configurable and dealing with all the headaches that come along with that, a new branch could simple expose an extra field?

Assuming it would be worth it at all, I'd probably look at this avenue if I saw this as a valuable D8 project.

Log in or register to post comments

Comment #4

dman CreditAttribution: dman at Sparks Interactive commented 12 August 2016 at 05:19

Yeah. I'm putting my weight behind DisplaySuite - to the point where I'd probably remove this one from our ingredients as it's duplicate functionality once that is happening.
(Although I do realise that the original purpose of title.module was more about translations first, and rendering second)

Log in or register to post comments

Comment #5

Sam152 CreditAttribution: Sam152 commented 12 August 2016 at 06:11

Yep. Having used plain old "manage display" for a long time in D7, this seemed to be a nice feature to have if you were to take the same approach in D8, but I pretty much agree this is defunct now.