We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 31255
    • 118 Posts
    User got this error window when open resource in manager:
    Code: 200 OK
    {"success":false,"message":"K\u00e4ytt\u00f6 estetty!","total":0,"data":[],"object":[]}

    (K\u00e4ytt\u00f6 estetty! is "Permission denied" in finnish lang manager)

    I have tried several solutions around forums but none of them work now.

    I`m raised my hands to find what permission caused this.

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

      Tassu, webmaster of Valokammi
      • 3749
      • 24,544 Posts
      First, be sure to flush both permissions and sessions after making any changes.

      As a quick test, make the user a sudo user. If the problem persists, it's not a MODX permission problem and could be mod_security. If that fixes the problem, take away the sudo status and flush everything.

      Look at all the permissions in both the user group's Context and Resource Group Access (if any) Policies. Look especially for the key words: load, list, view, edit, save, and update.

      If that fails, check the checkbox for all the permissions on the user group's Context and Resource Group Access (if any) Policies. Then take them away, a few at a time, flushing and testing as you go until you find the critical permission.
        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 31255
        • 118 Posts
        Yes, these problems can be tricy to solve. Especially when they come from bushes. I did it with hard way, starting with full administrator access policy grid.

        I attached policy template which worked for my purposses without error (I never found what exactly causes error) and are relatively safe user to use.

        NOTE: Template contains user management and other policies that you may not need. Use your own risk this template and check it carefully. But no 200 ok errors.
          Tassu, webmaster of Valokammi
        • discuss.answer
          • 36816
          • 109 Posts
          Quote from: valokammi at Jan 05, 2017, 01:42 PM
          I`m raised my hands to find what permission caused this.

          I just came across this on a new 2.5.4 site using a policy that had worked fine up to and including 2.5.2, so something changed in 2.5.3 or 2.5.4.

          Specifically, granting the permission view_template made the error go away.

          In case it helps someone investigate similar problems, the way I zeroed-in on this was the following.:

          1. Open browser developer toolbar (Chrome in my case)
          2. Go to the Network tab therein
          3. Take the action in MODX that triggers the error
          4. Within the developer toolbar Network window, click on each URL, then select the Response sub-tab of that URL
          5. Do so for each URL accessed, looking for the error you saw in the popup in the response. That URL is the likely culprit
          6. In the Headers sub-tab for that URL, look for the action field within the Form Data section. This should give a clue as to what access was failing. In this case, the action field was, element/template/getList leading me to try out permissions for templates
          [ed. note: clareoconsulting last edited this post 7 years, 3 months ago.]
            • 43864
            • 151 Posts
            • Hi Folks, this appears to be a byproduct of changes to permissions in 2.5.4, the user would never have been able to see the templates but now, it's displaying the error that they do not have permission to see them. See: https://github.com/modxcms/revolution/issues/13243


                Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. BlogTwitterLinkedInGitHub
              • I am not suggesting this is the right outcome. The field should probably just be not rendered or disabled for the user who doesn't have permissions since my understanding is view_templates is related to seeing/accessing in the Elements tree. I could be wrong.
                  Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. BlogTwitterLinkedInGitHub
                  • 3749
                  • 24,544 Posts
                  @clareoconsulting: Nice bug hunting. smiley

                  Do you mind if I do a blog post on it?
                    Did I help you? Buy me a beer
                    Get my Book: MODX:The Official Guide
                    MODX info for everyone: http://bobsguides.com/modx.html
                    My MODX Extras
                    Bob's Guides is now hosted at A2 MODX Hosting
                    • 36816
                    • 109 Posts
                    @BobRay, no objections whatsoever.
                      • 3749
                      • 24,544 Posts
                      Thanks. smiley
                        Did I help you? Buy me a beer
                        Get my Book: MODX:The Official Guide
                        MODX info for everyone: http://bobsguides.com/modx.html
                        My MODX Extras
                        Bob's Guides is now hosted at A2 MODX Hosting