Git Product home page Git Product logo

magento-configuration-powered-css's People

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

magento-configuration-powered-css's Issues

Ability to create multiple stylesheets

Ideally, we should be able to specify which page handles to apply configuration generated css applies to, and the ability to implement multiple stylesheets.

For example, if generated CSS is to be used on the catalog_product_view handle, then that should be the only place that CSS is loaded.

I'd propose changing Meanbee_ConfigPoweredCss_Block_Css to inherit from Mage_Core_Block_Text_List and for child blocks to be implemented based on xml configuration where you can also specify what handles should be applied. i.e.

<config>
....
<default>
    <meanbee_configurationpoweredcss>
        <css_blocks>
            <default_css>
                <block_type>namespace_module/config_css_default</block_type>
                <handles>default</handles>
            </default_css>
            <products_css>
                <block_type>namespace_module/config_css_products</block_type>
                <handles>catalog_product_list,catalog_product_view</handles>
            </products_css>
        </css_blocks>
    </meanbee_configurationpoweredcss>
</default>
</config>

Thoughts?

Supporting topologies with multiple web servers

I'm running into a problem in a topology with one admin server and two front end servers. With the extension, in its current form, I run into a problem trying to get the published file pushed out to the front end servers. The publish button exists and is executed on the admin server causing the file to be generated on the admin server, in the skin/ directory. The skin directory isn't something that has generated content and so is typically committed to the repository or, at the very least, isn't shared across multiple servers. Directories that are typically shared are media/ and var/.

I propose the following solutions:

  • Generate the CSS file when requested (if the code notices that the file isn't there, then generate it) and keep the file in the skin directory. This means the file would be generated three times in the example, once on every server.
  • Move the generated files to the media/ directory so that they can be shared across all of the machines. The file would only be written once.

Thoughts?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.