-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEATURE: Add additionalParams to ConvertUrisImplementation #3486
FEATURE: Add additionalParams to ConvertUrisImplementation #3486
Conversation
We mix that in other parts already, but additionalParams != query arguments.
I also wonder if those arguments are always to be appended to node and asset links. |
Something new about this PR? It seems like an ongoing discussion :) |
Can we find a solution here? As we have feature freeze tomorrow ;) |
I still stand to my suggested solution (extend To work around the limitation (i.e. to achieve what @jonnitto described in the original PR message) I would suggest to add a separate processor that just appends query parameters to already converted URLs:
|
I think, it won't make it into 7.3 anyway, but I will look to bring it into Neos 8 with the extended |
Are you able to work on that for 8.3? |
This might be related to neos/flow-development-collection#2744 |
..and maybe #3914 |
Not sure about this, i would rather use a custom processor for that rather than extend convertUris.
Could be distributed as package for reusability so imho there is no need to support this directly from the core. Just seen that Bastian already suggested a custom processor for that. So i second that |
@jonnitto you want to take another try at this or should we close it? |
If you create newsletter with Neos, it is crucial to have some additional parameters like
utm_source
,utm_medium
andutm_campaign
to every link. This change enables theConvertUrisImplementation
to haveadditionalParams
.