We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 11149
    • 17 Posts
    Hello,

    I'm trying to set up a Session-less Contexts as suggested by Jason Coward.

    Problem:
    Whenever I try to access a recourse in the newly created context I get a "404 HTTP error message".
    When I move the same recourse in the standard "web" context it works again.

    I created a new context and added the suggested Context Setting:
    Key = session_enabled
    Name = session_enabled
    Field Type = yes/no
    Namespace = core
    Area Lexicon Entry = session
    value = 0
    with following Access Permission:
    User Group = (anonymous)
    Authority = 9999
    Access Policy = Load only

    Possibly important System Settings:
    Use Friendly URLs = 1
    Allow Forwarding Across Contexts = 1

    Could it be a Access Permission issue or something else I overlooked?
    I'm running a MODX version 2.2.6 advanced installation.

    Any help would be much appreciated.

    This question has been answered by multiple community members. See the first response.

    • discuss.answer
      • 22303 MODX Staff
      • 10,725 Posts
      How are you routing requests to this new Context you setup?
        • 11149
        • 17 Posts
        Quote from: opengeek at Dec 13, 2012, 01:07 PM
        How are you routing requests to this new Context you setup?
        Thanks, your question pointed me in the right direction to look for.

        I wanted the resources of the new context on the same domain as my standard domain for the "web" context. The Package ContextRouter does that.

        What would be the settings, if I'd had done it manually without the ContextRouter plug-in?
        • discuss.answer
          • 22303 MODX Staff
          • 10,725 Posts
          Setting up Contexts requires choosing a method of routing, whether that be with a plugin that handles the switching based on information from the client request, or via virtual host configurations for different domains/sub-domains in your web server. There are no "Settings" on their own which will enable routing to custom Contexts.
            • 11149
            • 17 Posts
            Quote from: opengeek at Dec 13, 2012, 01:55 PM
            Setting up Contexts requires choosing a method of routing, whether that be with a plugin that handles the switching based on information from the client request, or via virtual host configurations for different domains/sub-domains in your web server. There are no "Settings" on their own which will enable routing to custom Contexts.

            Thanks for the clarification!
            I checked the source of the ContextRouter plug-in. Now I understand it better.