<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 17:25:45 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Stefan Koopmanschap's Blog: Removing stylesheets in symfony 1]]></title>
      <guid>http://www.phpdeveloper.org/news/16256</guid>
      <link>http://www.phpdeveloper.org/news/16256</link>
      <description><![CDATA[<p>
<i>Stefan Koopmanschap</i> has a quick post to his blog with a handy, not immediately obvious tip for the <a href="http://symfony-project.com">Symfony</a> users out there - how to <a href="http://www.leftontheweb.com/message/Removing_stylesheets_in_symfony_1">remove site-wide stylesheets</a> in a Symfony application so it's not loaded automatically.
</p>
<blockquote>
Today I encountered a situation I've not encountered before: I have a project-wide stylesheet that should be used for everything, except one specific module that has different (brandable) stylesheets. I created a view.yml for this module with a different stylesheet, but of course the configuration files are merged so it doesn't actually overwrite the main stylesheet file. And this wasn't really what I needed here.
</blockquote>
<p>
His technique involves a change to the main view.yml configuration file with a special syntax to remove the CSS file with a negation. A snippet is included to illustrate. You can find out more about view configuration in <a href="http://www.symfony-project.org/book/1_0/07-Inside-the-View-Layer#chapter_07_view_configuration">this chapter</a> of the "Definitive Guide to Symfony".
</p>]]></description>
      <pubDate>Wed, 27 Apr 2011 08:58:49 -0500</pubDate>
    </item>
  </channel>
</rss>
