"summary" token for text+summary field is empty when using anything other than the core "body" field

I suspect this is a bug in the token system, which Metatag doesn't actually get involved in.

That said, lets put together a test for your scenario and see what happens.

I have had a similar bug, but it was on [node:summary]. For some reason, if I put a white space after the token, the tag works. You can try this as a workaround.

I'm sorry you're having this problem. I haven't been able to look into this problem yet as I was moving last month.

We need tests for a few different scenarios:

• Standard node summary works when the node's body field has summary text.
• Standard node summary works when the node's body field does not have summary text.
• Custom node longtext+summary works using a field token when the field has summary text.
• Custom node longtext+summary works using a field token when the field does not have summary text.

There is a separate issue for truncating meta tags to a specific length: #2309017: Automatically trim meta tag lengths (D7)

There's nothing on that issue for D8, but once it's included in D7 (probably 7.x-1.23) we'll look to porting it to D8.

Not yet.

This is a known issue in the Token system, sorry. See #1671420: If no body field, [node:summary] [node:body] etc tokens are not replaced for a discussion on the problem.

Do you have the Entity Token module installed, or just the basic Token module?

Ultimately the problem with token values not giving the correct value is not Metatag's fault, which is why I closed the issue in the first place.

Lets go back to writing some tests.

Out of interest, do you have HTML at the beginning of the summary?

Thanks for all the screenshots, that helps.

Just to mention it, "needs work" is for where there's a patch that needs further work, it isn't just a way of saying "this needs to be worked on"; "active" is the correct status to use until we have a patch to look at.

So I installed core 8.4 with Metatag, added a new long text field to the default Article content type and used the token browser to see what tokens were available for the content type:

I also noticed that the summary field is not editable, so I edited an issue for that: #2906282: No summary option showing for "Text area with a summary" widget

Just out of interest, have you checked to see the field via the Devel module to see if the summary contains anything? I wonder if that's why the summary field isn't outputting anything, that it doesn't have any text?

Clarifying the title - it seems to be a general problem with the text+summary field.

I thought I'd posted an updated comment. Sorry.

Yes, there are some core issues related to this and the core maintainers are looking to delete the field type entirely: #1378350: Clean up the "Long text and summary" field

I do want to write tests, though, just to confirm the functionality.

The problem isn't the text fields themselves, it's the "summary" token.

As a work-around you might try filing something into the "summary" portion of those text fields.

I really think the problem is in core, but it could be worked around in the contrib module.

[node:summary] is also not replaced (on my site, at least) where field_data_body is set in the content type to permit unlimited values rather than a single value.

This is D7, so I fear it may be difficult to get attention of core devs, or at any rate core committers, for it.

Just noticed this. Appears to still be an issue.

There is an available patch for the token module.

#2924873: Summary token not fully handled in fields

The patch here:
#2924873-11: Summary token not fully handled in fields

Is working well for us.

It's being held up on a "Needs tests" tag.