We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 27210
    • 158 Posts
    MODx 2.2.0

    In my css I duplicated several ids and styles that differentiate product years.
    The -2012 strings work fine, but the -2013 strings aren't seen.

    Examples:
    productlistingbox-even-2012 (works)
    productlistingbox-even-2013 (not seen)

    css_play_row-2012 (works)
    css_plan_row-2013 (not seen)

    etc.

    When I view the page with Firebug, NONE of the new -2013 ids / styles are seen.

    What I have tried.
    - verified the css
    - Cleared browser cache.
    - Cleared MODx cache.
    - Tried IE and Firefox.
    - Checked spelling.
    - looked at code until i am bleary eyed.
    - Searched here and the bug database.

    This is driving me crazy - I feel pretty dumb...

    Any suggestions would be appreciated.
    Thank you very much! [ed. note: signcarver last edited this post 13 years, 8 months ago.]
      • 27210
      • 158 Posts
      I know what the problem is but i don't know how to fix it!

      The css file is correct in the Manager BUT when i open a file using the css in Firebug i still have a copy of my old CSS file

      Any ideas?
        • 27210
        • 158 Posts
        OK here's the problem. When i update the css file, the updated file never gets read in. So the fix below worked until i change the darn thing again. Please help.

        Fixed it but don't know why - i renamed the css from mainstyle.css to mainstyle-2013 and linked the new mainstyle-2013.css. Maybe there's a cache somewhere that wasn't cleared??? I even deleted the folders / files under core/cache.
        [ed. note: signcarver last edited this post 13 years, 8 months ago.]
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          It's a web server configuration issue, with the browser itself having a smaller part to play. The server should be configured to send some request types, such as text/css, with no-cache headers. If it isn't configured properly, then most browsers will cache everything they aren't specifically told not to cache. http://www.mnot.net/cache_docs/
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 27210
            • 158 Posts
            Quote from: sottwell at Feb 10, 2013, 12:01 AM
            It's a web server configuration issue, with the browser itself having a smaller part to play. The server should be configured to send some request types, such as text/css, with no-cache headers. If it isn't configured properly, then most browsers will cache everything they aren't specifically told not to cache. http://www.mnot.net/cache_docs/

            Thank you so much sottwell - That did it! - i found that GoDaddy has, under Domain > Tools > Web Accelerator a Developer mode that turns off caching for 24 hours. I also read the link you posted, all totally new to me. I learn something every day in this business.

            Thanks you!!!