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

    the Context concept looks very promising. For example I am thinking of the following structure for a 3 domain Modx site:

    A "Shared" context which contains all web pages and will be used by all three domains.
    A "DomainA", "DomainB" and "DomainC" context which specific content for the these domains

    The "Shared" context would be more or less only a repository for shared pages which I then can plug into any of the other contexts by using references or links.

    Compared to 3 different modx installations I would have the benefit of:

    - Most of the common code, plugins and snippets can be shared and has to be maintained only once
    - A considerable amount of web pages which are identical can be shared and have to be maintained only once
    - The Modx core code is shared and needs only updated and maintained once

    Is this approach feasible and in line with the intended use of these contexts?

    Also, is it correctly understood that Context settings override System settings?

    Regards

    Henrik
      • 22303 MODX Staff
      • 10,725 Posts
      Quote from: hwmaier at Feb 13, 2009, 07:20 PM

      - Most of the common code, plugins and snippets can be shared and has to be maintained only once
      - A considerable amount of web pages which are identical can be shared and have to be maintained only once
      - The Modx core code is shared and needs only updated and maintained once

      Is this approach feasible and in line with the intended use of these contexts?

      Also, is it correctly understood that Context settings override System settings?
      It looks like you’ve got the concept down already, and yes, that is absolutely feasible, and context settings do override system settings (and user settings override context settings).