TYPO3 Core

Sorry Benni,

meanwhile I switched to a TypoScript-Only solution in LUX to get linkhandler to work. Also "Local History" in PhpStorm is empty for the file.
With this issue I opened a second one with #99886 - maybe that helps you (even if the issue is a bit different).

Alex

Update I think it was exactly like Torben shows it in his blogpost like:

config {
    recordLinks {
        registration {
            typolink {
                parameter = 1
                userFunc = DERHANSEN\SfEventMgt\UserFunc\TypoLink->createEventLink
                userFunc {
                    eventUid = TEXT
                    eventUid.data = field:event
                    registrationUid = TEXT
                    registrationUid.data = field:uid
                }
            }
        }
    }
}

Hi,
we are experiencing the same issue for a project we are upgrading from a working LTS 11 version to 12.

It seems that the userfunc return value is not used in any way for the typolink generation.
We did double check and can confirm that our userfunc is returning a full (and valid) a-tag.
(We even tried with only returning an opening a-tag as suggested by some source)
If we comment out our userFunc line in our TS, a link is generated to the parameter pid given in our typoscript.

Therefore we assume userFunc is not working with typolink in v12.

Are there any news on this issue? Or can you at least confirm, it is an open issue?

Thank you!
Ulrike

Hey Ulrike,

does your userFunc return a string or a LinkResult object?

Hey Benni,

currently we are returning a string but if it is required we can switch to a LinkResult object.

Hi,

any news or hints regarding this userFunc issue?

Thank you!
Ulrike

cosmoblonde GmbH wrote in #note-7:

Hi,

any news or hints regarding this userFunc issue?

Thank you!
Ulrike

Hey Ulrike,

yes. feel free to ping me (e.g. on slack https://typo3.org/community/meet/chat-slack) so we can exchange the code, if that's ok.

Hey Benni,

thanks for your offer to directly communicate - I appreciate it!

In the meantime I have already found a solution for my specific problem by using the following typoscript structure:

Working TypoScript structure:

     customLinkType {
           typolink {

                # Detail page
                parameter.cObject = USER
                parameter.cObject {
                    userFunc = Myvendor\MyExtension\UserFunc\MyClass->buildLink
                    item.data = field:uid
                    # PID used if no detail page can be found
                    fallback = 13
                }
                additionalParams.data = field:uid
                additionalParams.wrap = &tx_myextension_dummy[controller]=MyController&tx_myextension_dummy[action]=show&tx_myextension_dummy[item]=|

            }
            forceLink = 1
        }

In that working example the userFunc is "only" returning the required PID of the target page, which - for my use case - is a good and clean solution.

Nevertheless, in the non-working version we tried to generate the complete link via a userFunc, which worked until TYPO3 v11 but with version 12 the returned link is never passed on and no links appear in the frontend.

Failing TypoScript structure:

     customLinkType {
           typolink {
                # parameter only set as dummy
                parameter = 1

                # additionalParams are available to the userFunc, so are used to pass the current field:uid to that function
                additionalParams.data = field:uid
                additionalParams.wrap = &UID=|&

                userFunc = Myvendor\MyExtension\UserFunc\MyClass->buildLink
            }
            forceLink = 1
        }

So for my example the new solution is preferable but it would be good for other use cases to be able to generate complete anchor links via a userFunc.

Thank you!