I found two bugs regarding the use of the SassFilter in the AsseticBundle on Windows.
=== 1. The filterLoad() method in SassFilter class the array_map function to execute the escapeshellarg function on all the elements of the $options array. The first option contains the path the the sass executable. proc_open on windows will not execute the command if it's escaped. "C:/ruby192/bin/sass" "--option1" "--option2" ....' [Broken] C:/ruby192/bin/sass "--option1" "--option2" ....' [Works] Without the escaping the sass command it worked, haven't digged in it further, but maybe on windows systems the sass command could be prepended with call (unquoted): call "C:/ruby192/bin/sass" "--option1" "--option2" .... === 2. In SassFilter the $cacheLocation attribute is initialized to sys_get_temp_dir(); On windows this points to 'C:\DOCUME~1\[Username] \LOCALS~1\Temp\'. Sass complains that it cannot find the cache directory and fails. This is because of the trailing slash. If this is trimmed of, it works. The following code fixes this problem, but is not very neat. $options[] = trim($this->cacheLocation, '\\'); ==== I'm working on Windows XP SP3. Keep up the good work! Looking forward to the first release of Symfony, IMHO the best PHP webapplication framework known to mankind. Cheers, Arjen -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
