We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 24865
    • 289 Posts
    Okay, excuse the long topic title, but it's the best way to describe this.

    I've got a couple of context (seriously, more than 15) for one site (different departments). The problem is as follows:

    When I search in the Resource Search field for "Resource 1" located in a context which is not visible inside the Resource Tree itself, I can still find it. Searching via the Search page however, I can't. So it seems to me that somewhere along the way rights get lost or my Access Policies got messed up badly.

    This also goes for searching via TinyMCE, which I fixed by checking context access from the SESSION of the current user. Naturally, this is a hot-fix and I don't like touching other people's code, let alone changing MODX core code.

    So, am I misinterpreting Access Policies or is this a real bug.
    To add to this, when I remove Load Only rights for the specific context in which I find it, I can still find it in the Resource Tree but editing is disabled (Rights error). This is not the case when Load Only on the context is in place - I can still edit that resource.
      @MarkGHErnst

      Developer at Adwise Internetmarketing, the Netherlands.