I have created a design asset. Under that I have created a CSS file asset called modern.css ie. New Child >> Design >> CSS File and made this live and granted public permissions. I have uploaded a css parse file
Then in the design parse file I have added the following in the HTML head area
However, instead of the folloing being output:
@import url("http:///blah..../modern.css");
it is just blank????? nothing is output.
I have read the Chapter 9 Linked CSS part of the latest designs document. All my other design areas are being output.
For the Linked CSS design area to work, you need to create a customisation for that design first. From there, you customise the Linked CSS design area - it should appear under the Customised header of the design areas list.
Click on the ID of the design area ("modern" in your case), and there should be the ability to select the CSS asset to link to.
The diagram on the bottom of page 80 of the Design Guide shows the kind of setup that you should be aiming for.
[quote]For the Linked CSS design area to work, you need to create a customisation for that design first. From there, you customise the Linked CSS design area - it should appear under the Customised header of the design areas list.
Click on the ID of the design area (“modern” in your case), and there should be the ability to select the CSS asset to link to.
The diagram on the bottom of page 80 of the Design Guide shows the kind of setup that you should be aiming for.
Ok so I have created a CSS File under my design asset and then created a customisation to my design asset and then linked the css file asset from the details screen of the design customization but the parse file is still not outputting the stylesheet reference.
I also gave everything in the design public permissions and all of it is live.
[quote]So, what now??
[right][post=“10352”]<{POST_SNAPBACK}>[/post][/right][/quote]
Do your pages use the customisation as the design, rather than the design itself? For the customisation to take effect, you need to apply it where you had the design applied before (the site, I’m assuming).
[quote]Do your pages use the customisation as the design, rather than the design itself? For the customisation to take effect, you need to apply it where you had the design applied before (the site, I’m assuming).
[right][post=“10353”]<{POST_SNAPBACK}>[/post][/right][/quote]
Hi Luke,
My pages are set to use the design itself not/not the customization. The customization is linked via the settings page to the linked_css file modern.css which is a child of the design and referenced in the design parse file as detailed in the above post.
[quote]You need to apply the Customisation to your pages.
[right][post=“10356”]<{POST_SNAPBACK}>[/post][/right][/quote]
Thanks Avi,
Actually I tried this before but it made no difference. I applied it in Settings as an Overide in conjunction with the parent design as well as replacing the parent design altogether with the customization but it didn’t make any difference.
It needs to replace the Design as the System Frontend Design. Only then will Matrix actually print all the customisations while its displaying the page.
[quote]It needs to replace the Design as the System Frontend Design. Only then will Matrix actually print all the customisations while its displaying the page.
[right][post=“10358”]<{POST_SNAPBACK}>[/post][/right][/quote]
Sorry Avi,
It makes no difference. I already applied it as the system frontend design for the page in question privacy.html but it still doesn’t print out. All of the other design area stuff does though eg. meta-data, page title, body copy etc.
I had to go to the details screen of the customised design, then in the Design Area section click on the hyperlinked design area linked_css which opens another screen and from here there was another text box to link to the css file itself.
Thanks for everyone's help. I think I will write this up as a dedicated step by step in our Wiki.
So I have to manually wrap the style tags around it as follows in the parse file:
Obviously, this renders the media value attribute redundant for the import type css as opposed to the link type. The interface states this but the manual will need updating at some stage.