- Issue created by @thomas.wardin
- πΊπΈUnited States owenbush Denver, CO
Thanks for raising this issue, I am not familiar with ECA and how it works, is there any way you could explain what exactly is happening? Are there any available event instance tokens? Usually tokens are contextual to the underlying entity, so are you trying to access event instance tokens from the registrant entity?
From what you've said, maybe it would be easier rather than using the url to get at the event instance, if you have something like [registrant:eventinstance:blah] as a way of accessing those tokens?
- π©πͺGermany thomas.wardin
I have to admit that I did not dig deep enough in the tree as shown by token browser. What I missed was this already existing token:
[registrant:url:args:value:#] with # being the position in the arguments array. - Status changed to Closed: works as designed
over 1 year ago 4:57am 16 May 2023 - Status changed to Needs work
over 1 year ago 11:57am 19 May 2023 - π©πͺGermany thomas.wardin
From the ECA team, I learned that the help text displayed there is originating from this module. The help text for [registrant:url:args] currently suggests [registrant:url:args:#] which obviously should be changed to [registrant:url:args:value:#] with # being the position in the arguments array.
- @owenbush opened merge request.
- Status changed to Needs review
over 1 year ago 11:44pm 25 May 2023 - πΊπΈUnited States owenbush Denver, CO
I've opened a merge request which adds the ability to access tokens from the eventseries and eventinstance associated to a registrant
For example:
[registrant:eventinstance:date]
and
[registrant:eventseries:title]
Let me know if this works for your needs.
- First commit to issue fork.
- Status changed to Fixed
over 1 year ago 11:30am 16 June 2023 Automatically closed - issue fixed for 2 weeks with no activity.