Oh man, just when I was getting comfortable under this rock. In SmartEdit mode, if you reference a CSS or JS page instance of a content class, when generating that page instance in SmartEdit mode (later found out that even in page preview), page builder looks for <HEAD> and try to inject stuff <HEAD> code. When <HEAD> is not found, an entire block of <HTML><HEAD></HEAD><BODY></BODY></HTML> is inserted, hence breaking any CSS or JS format.
Having &script=1 is supposed to tell page builder that leave the page linked by anc_ or list alone, but then &script=1 stopped working... Current best practices: 1. Manage the CSS as inline css (via <style><%con_css%></style> during non publishing mode, and use <link> during publishing mode. JS file as static files in File Folder in the project, referenced via media placeholder. 2. Manage and reference CSS and JS seperately on the file system and publish seperately (not from CMS) Will probably make a blog post about this. 75% of the project upgrade issues ended on support desk is either concerning CSS not working or preexecution breaking. -Jian On Wednesday, April 3, 2013 12:00:19 PM UTC-4, Wolfgang Roiter wrote: > > Sorry, I was not aware that script=1 stopped working somewhere in between. > In the past we've been including static css/js files due to the > performance impact that you've mentioned, so I stopped using the script > parameter anyway. > > But if I remember correctly, in some cases you had to include the > parameter anyway to get JS stuff working, no matter if you're including > js-files with placeholders or with external URLs (...but I cannot tell with > certainty). > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
