- Issue created by @matthieuscarset
- Status changed to Needs review
9 months ago 2:51pm 24 March 2024 - π¨π¦Canada mandclu
I'm a little confused, because this issue is against Smart Date 3.6 (which is no longer supported) but the MR seems to target 4.1, but without many recent commits.
I'm curious, could the change proposed here be a potential fix for π Updating to Token 1.13 breaks smart_date range tokens Needs review ?
- Status changed to RTBC
9 months ago 8:57pm 24 March 2024 - π§πͺBelgium dieterholvoet Brussels
I encountered the same issue with a token in the format
[node:field_event_dates:0:value-format:date_only]
. This fixes the problem. I'm using Smart Date 4.1.0-rc4. - π¨πSwitzerland berdir Switzerland
Sorry about breaking this, the token.module changed seemed like the only feasible long-term fix for those weird bugs that were reported there, and opens up the ability to move those token implementations into the respective core/contrib modules eventually.
Have you tried to implement an alter hook instead, which would allow you to alter the existing tokens instead of relying on hook order execution?
- π¨πSwitzerland berdir Switzerland
Ah, it's the tokens hook, not token_info. Not sure if a token alter then is feasible or not.
- πΊπΈUnited States dalemoore
I was banging my head against the wall trying to figure out why these weren't working on a new site I'm working on, having the same issue I was having last year in No other token format available or accepted besides the default one π No other token format available or accepted besides the default one Fixed , this fixes it for me for now. Trying to use the tokens in the URL for the same as before.
-
mandclu β
committed 090c725d on 4.1.x authored by
matthieuscarset β
Issue #3433267 by matthieuscarset: Smart date value custom format tokens...
-
mandclu β
committed 090c725d on 4.1.x authored by
matthieuscarset β
- Status changed to Fixed
8 months ago 11:09am 20 April 2024 - π¨π¦Canada mandclu
Merged in. Thanks for finding this solution @matthieuscarset!
Automatically closed - issue fixed for 2 weeks with no activity.