You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is possible already, that's why I open it as feature-request here (at least it seems not documented): It would be really great if there is a way to link local/extension script-files in TypoScript inject() object. For example, not all script are always remote on servers at Google, Facebook, etc... Or even if they are, sometimes it is useful to create a wrapper around such tracking-scripts e.g. to mock function calls to fbc().
So if these scripts are stored in a local extension, how can we link them to be loaded dynamically? Hardcoding the following path might work until v11, but I think starting from v12 where the assets directory are generated dynamically by hash-folder names, this will not work anymore. If possible the common TYPO3 approach like EXT:my_ext/Resources/Public/Js/custom.js would be better to create an absolute URL:
Feature Request
Not sure if this is possible already, that's why I open it as feature-request here (at least it seems not documented): It would be really great if there is a way to link local/extension script-files in TypoScript
inject()
object. For example, not all script are always remote on servers at Google, Facebook, etc... Or even if they are, sometimes it is useful to create a wrapper around such tracking-scripts e.g. to mock function calls tofbc()
.So if these scripts are stored in a local extension, how can we link them to be loaded dynamically? Hardcoding the following path might work until v11, but I think starting from v12 where the assets directory are generated dynamically by hash-folder names, this will not work anymore. If possible the common TYPO3 approach like
EXT:my_ext/Resources/Public/Js/custom.js
would be better to create an absolute URL:Any ideas on that matter? Appreciate your feedback 🙂
The text was updated successfully, but these errors were encountered: