We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

CSS in 2nd Context.

    • 39498
    • 169 Posts
    spica8 Reply #1, 13 years, 6 months ago
    I do have a second context. With ContextRouter as Gateway. My Resource CSS file gets delivered as text/html instead of text/css after repeated reloads. Cleard cache and reload delivers text/css, reload again text/html. Same file in the first context does well. I have no idea…
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      sottwell Reply #2, 13 years, 6 months ago
      Contexts seem to have problems dealing with sharing of resources.

      Do your two contexts have context setting for base_url?

      What would happen if you have a duplicate .css resource in the second context?
        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
        • 39498
        • 169 Posts
        spica8 Reply #3, 13 years, 6 months ago
        it is a unique ressource of the context. I just pushed the ressource to the first context for testing, but it lives in the second.
          • 39498
          • 169 Posts
          spica8 Reply #4, 13 years, 6 months ago 
          <b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /www/htdocs/core/model/modx/modresponse.class.php:189) in <b>/www/htdocs/core/cache/includes/elements/modplugin/1.include.cache.php</b> on line <b>106</b><br />

          When loading the css ressoure first time with cache cleared this warning is in the log.
            • 39498
            • 169 Posts
            spica8 Reply #5, 13 years, 6 months ago
            this is realy weired. I now realized, that css ressources of all contexts are affected for anonymous users. The default context only was behaving "normal" when logged in as admin. So it should be a rights management issue, played a bit with the settings but can not make any improovement.

            This is the default setting. Is it as it should be?
            web
(anonymous)	
9999	
Load Only
              • 28042 ☆ A M B ☆
              • 24,524 Posts
              sottwell Reply #6, 13 years, 6 months ago
              Try Load, List, View.
                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
                • 39498
                • 169 Posts
                spica8 Reply #7, 13 years, 6 months ago
                did try already, no effect
                  • 39498
                  • 169 Posts
                  spica8 Reply #8, 13 years, 6 months ago
                  same with context
                    • 39498
                    • 169 Posts
                    spica8 Reply #9, 13 years, 6 months ago 
                    [2013-04-02 16:54:31] (ERROR @ /index.php) [OnWebPageComplete]<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /www/htdocs/core/model/modx/modresponse.class.php:189) in <b>/www/htdocs/core/cache/includes/elements/modplugin/1.include.cache.php</b> on line <b>106</b><br />


                    Missed first line before. What could cause this header error?
                      • 39498
                      • 169 Posts
                      spica8 Reply #10, 13 years, 6 months ago
                      ok, found reason. plugin xFPC. if deaktivated behaviour is normal. will put a thread in plugins.