We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 26903
    • 1,336 Posts
    When a package is installed that has context dependent content such as resources say what as a packager are you supposed to do here if anything to take this into account?

    This has just been raised on the Frontpage support thread in that a user has Frontpage working in the web context only, which it assumes, but not the other contexts, which it doesn’t hence it doesn’t work in them.

    You could write a resolver here to duplicate the resources across all contexts but it may be better if the installer did this, either way you still have the prob of which ones to pick, the user may only want the resources in some contexts and not others. Then of course there is the backend, some packages(gallery and I think visioncart IIRC) have backend connectors/processors that are split into mgr and web context handling, OK, you can assume mgr, but not web, and what about any others?

    Perhaps there’s some docs I’ve not seen yet on this topic, docs/tuts for Revo seem to be hitting the streets at a fair pace lately.
      Use MODx, or the cat gets it!