We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 14877
    • 110 Posts
    Revo 2.3.2.

    On my test site, I'm working on the beginning of a large port of some genealogy software to MODX. I've been working at trying to get the security set-up. I've previously not had any problems with handling such things as "Members Only" areas and a complete "Private" site; however, I now need to be able to apply security policies to data in custom tables as well as to "normal" MODX objects.

    I've been attempting to set up User Groups, Resource Groups, Access Policies (based on my own policy template starting with a copied policy template and adding custom permissions) and ACLs.

    I thought I was getting it straight, when...

    I went to login as user "Susan" and my website reports I'm logged in as "jrg" — and seems to act that way.

    Both user ids were working fine at one stage and I've never had:
    Logged in as: [[+modx.user.username]]

    mis-report.

    I thought perhaps I'd failed to clear something, so I went through the following sequence a couple of time:

    Testing the site is being done using the Chrome browser; MODX manager stuff is being done using the Firefox browser.

    1) (manager) Flush Permissions
    2) (manager) Clear Cache
    3) (manager) Logout All Users
    4) (front-end) Clear cache (includes clearing cookies)

    Additionally, I also quit both browsers. After trying that, I also rebooted my computer (it runs Linux Mint).

    The problem persists: Login as "Susan" (my wife's name smiley ) and appear to be logged in as "jrg" (my initials). Those are currently the only two defined users.

    It's bizarre! Any trouble-shooting suggestions would be appreciated.

    This question has been answered by jrg. See the first response.

      __________________
      JRG
      • 42046
      • 436 Posts
      Have you tried calling it uncached? Clearing the cache within the manager doesn't clear all cached items, just resources.

      [[!+modx.user.username]]
      • discuss.answer
        • 14877
        • 110 Posts
        Quote from: absent42 at Nov 11, 2014, 02:58 PM
        Have you tried calling it uncached? Clearing the cache within the manager doesn't clear all cached items, just resources.

        [[!+modx.user.username]]
        Well, that isn't (shouldn't) be the problem as it's a placeholder that is supposed to be set by the login process.

        However, you did get me thinking… That bit of code is embedded in a chunk referenced in templates and that chunk reference was being cached! Going back up the chain and changing the chunk reference to uncached solved the problem.

        Thank you for the clue.
          __________________
          JRG