We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32070
    • 87 Posts
    I've got a site with multiple contexts. Users of the non-web context have no issues. Everything functions normally.

    For my admin users and other users that are assigned ONLY to the main web context, there are a few strange things happening.

    1) The username is not displayed in the top right of the manager interface. This hasn't necessarily been a big deal - just different. I did notice, that if I took a web-context only user and moved them to a group with manager access for a different context (i.e. moved them from the web group to another group), the were able to see their username up there.

    2) I THINK whatever is happening is somehow preventing my web-only users from accessing the resource browser to add photos/files via TinyMCE... interestinging I CAN see everything from the files tab - I keep getting an access denied message and have tried every conceivable thing to reconcile this (e.g. changing server permissions, changing modx permissions, reinstalling modx, etc). All of my non-web-context users, again, are just fine and can add user the resource browser without issue. I have other MODX installs running on the same server, again with multiple contexts, that aren't experiencing this issue.

    I'm absolutely stuck and really need to be able to get my site admins this access. ANY thoughts on where to check would be welcome at this point!

    Thanks!

    Setup:
    PHP 5.4.20 on Apache 2.2.x
    MODX 2.2.10
    MySQL 5.5.17

    Articles 1.7.3
    Breadcrumbs 1.1.0
    Formit 2.2.0
    getResources 1.6.0
    phpThumbOf 1.4.0
    SimpleSearch 1.6.1
    TinyMce 4.3.3

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

      Des
      webandflowdesign.com
      • 18373 ☆ A M B ☆
      • 3,141 Posts
      That definitely sounds like an ACL problem. When you assign permissions to a specific user group, that means that other user groups no longer have access to that permission, unless they also have it assigned to their group. It sounds like your non-web user groups have access to something that your web user group does not. I'm not sure what permission that would be, but putting them side-by-side might reveal the culprit.
        Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

        Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
        • 32070
        • 87 Posts
        I thought that too - but the group that's having the issue is the main site administrator group - they're all super users and should have every conceivable permission - even if I make them sudo users they can't access the resources browser and their username doesn't show in the nav bar.

        All of my lower level groups are functioning fine.

        I will definitely parse through them again though - just to be sure smiley
          Des
          webandflowdesign.com
          • 32070
          • 87 Posts
          UPDATE: So, I've determined that my administrative users don't have a session context for the mgr context....

          And I have no idea how to grant them that... I assumed because they're logged into the mgr and "mostly" everything works, that they DO in fact have a session context....

          But I can't seem to convince MODX that they have a session context smiley

          UPDATE X2: It looks like when I log in as a user in the admin group the context that gets reported is "web" - for all of my other users, it gets reported as the 'mgr' context.

          I feel close - somehow I have to make modx believe that I'm actually in the 'mgr' context.... this seems like it will clear up a lot of my issues.





          [ed. note: webandflow last edited this post 12 years, 10 months ago.]
            Des
            webandflowdesign.com
          • discuss.answer
            • 32070
            • 87 Posts
            And, as it turns out....

            A poorly written plugin (by yours truly) was to blame that was forcing MODX to load the web context for my admin users even when it should have been the mgr context....

            MODX 42 - ME 0 smiley

              Des
              webandflowdesign.com