-
Notifications
You must be signed in to change notification settings - Fork 2
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
No icon in frontend #42
Comments
Hey,
Is the whole
As soon as you have the value (EXT: fontawesome/...svg) in the frontend you should use the |
Try to add the debug statement into the Layout of your fluid_styled_content element. Maybe you are trying to access the data from a partial: Fluid styled content does not always pass all variables with |
The whole data array is empty in the partial Header.html - and in the Layout Default.html the <f:debug>{data.tx_bwicons_icon}</f:debug> returns the right value. |
You have to check the whole template inclusion path: The entry point is your Templates/Header.html, Templates/Textmedia.html,... All of these use the Layouts/Default.html Layout. This layout file renders the Partials/Header/All.html partial with
You could override this file and add |
So very NICE - I have learned something today - this works and now I just have to puzzle with the f:uri.image or what img src to retrieve the {icon} - HAPPY NEWYEAR and thanks for your great help :-) |
My setup is typo3 11.5.33 with php 8.2.13 and bw_icons 2.1.7
In typo3 backend everything is fine - I can choose the icons for ex a header element - but when I use <f:image src="{data.tx_bwicons_icon}" /> in my fluid template for ex. header.html nothing shows up in frontend. When I debug: <f:debug>{data}</f:debug> there is nothing in {data} even if the header element has a icon in the backend and also in the tt_content database there is a field called tx_bwicons_icon and for the element there is a value: EXT:fontawesome/Resources/Public/Images/Icons/Fontawesome/algolia.svg
How can I get the icon to show up in the frontend?
The text was updated successfully, but these errors were encountered: