Search the Community
Showing results for tags 'scripts'.
Hi all, Not sure if this has been asked already but... Recently came across an agency with a build script for PW! I was amazed and also bemused, as alot of the script was used to create the right fields and templates in the DB from other local copies, and they'd done this by separating out tens of JSON files with individual field / template export data and sticking it back together on deploy creating new id's adhocly. (a far as i could see as id's were ommited) Anyway, in my experience I've always felt that export profile and profile installing has worked well for buiding for live as you
If i have a template that requires scripts added in head and at the end of body. Do you have any idea how to handle this whith $config->scripts. Another point is how to handle if its necessary to add not just files but small scripts that need to be added at the head or bottom.(like google analytics). Is there something like : $config->scripts-bottom $config->scripts-direct Maybe there is a way to make such an array, besides from silmply creating the var.
Hi I try to build a simple basic responsive layout / profile with pocket grid... So it would be great to set additional values as variables. IE conditional comments could be build by a module to generate the needed code. I would use $config->styles and $config->scripts to build a filenameArray with needed css and js files. But how could a add additional values like media attribute or IE condition? Any idea to keep it simple? Last site media query styles were hard coded at page template file (a templateFile template ) before output $config->styles ... Maybe the media queries
My site has several pages that require access to one-off scripts the rest of the site doesn't use. To keep pages loading as fast as possible we don't load these scripts on every page. Instead, we typically include them on a per-page basis in an extra block loaded after the footer html. When I first started trying to port to PW I added textarea fields for "extra_head" and "extra_footer" into my primary template, and I hoped I could include these script loading directives in the "extra_footer" block and be off to the races. In fact, this would have worked beautifully if I had hard-coded paths