When the Recurring Events module was initially created there was no support for bundle base field tokens, but now with the patch on #3047568: Consistent tokens support across all entities and fields these hardcoded tokens may not be needed anymore, as the core tokens are more flexible and versatile than the hardcoded options.
Remove all hardcoded tokens if/when #3047568: Consistent tokens support across all entities and fields lands.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 3172265-5-recurring_events-remove_custom_tokens.patch | 4.16 KB | megakeegman |
| #2 | recurring_events-remove_custom_tokens-3172265-2.patch | 3.69 KB | owenbush |
Comments
Comment #2
owenbush commentedApply the patch is the related issue, and then apply this patch.
Comment #3
pfrenssenPostponed until #3047568: Consistent tokens support across all entities and fields is in.
Comment #4
megakeegman commentedI realize that this is postponed, but for documentation sake, it is noteworthy that patch #2 no longer applies.
Comment #5
megakeegman commentedHere is a new patch that applies to 2.0.x
The tokens available by 3047568 offer more flexibility than the ones provided by this module. I used both of these patches so that I could leverage the date formatter on Drupal tokens. Before trying this patch, I tried to apply a date format to a token for a pathauto pattern and received a validation error about an invalid token, and that is why I am here now.