We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 5452
    • 41 Posts
    I can’t access the pages that are restricted to the document group. I thought logged in as default admin that I would be able to access ANY document group???

    Please help.

    All the best,
    ~Slim~
      • 7231
      • 4,205 Posts
      You can access any document via the manager, but you need to login as webuser to view private pages. Role 1 can view all private manager documents.
        [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

        Something is happening here, but you don't know what it is.
        Do you, Mr. Jones? - [bob dylan]
        • 5452
        • 41 Posts
        For some reason it’s not working. I have the quickEdit box open on the pages... so I am obviously logged in Role 1. But when I try to access a page in my browser that is assigned to a webuser group (specifically one I want members only to view), I keep getting sent to the index page.

        I have WebLoginPE form on some of the pages, but there isn’t enough clear docs on how to use the WebLogin or WebLoginPE, imo.

        Still need help.

        All the best,
        ~Slim~
          • 4310
          • 2,310 Posts
          Only Manager Users can edit via logging into the Manager.
          Only the allowed web user/web group can view the page from the front end.
          Manager Users & Web Users are two completely separate beasts.
          It’s a quirk/feature of MODx, changing for 0.9.7 I think.
            • 5452
            • 41 Posts
            How do I login as a web user via the regular browser? I have tried and tried and tried. I have WebLoginPE username, password, and login button on one page...

            But, once I login, nothing happens. I am still at the same page, and the username and password textbox and the login button still appera.

            There isn’t enough info on the WebLoginPE, and WebLogin snippets, as there is for other snippets.

            ~Slim~
              • 28042 ☆ A M B ☆
              • 24,524 Posts
              Do you have the WebLoginPE snippet called cached, [[...]], or uncached [!...!] ?

              All interactive snippets must be called uncached (if the document itself is cached). If you think about it, it is logical. A cached document caches everything, including snippet output. The next request it doesn’t do anything but serve the cached document output. So when the user clicks "submit", he’s requesting the same document only with POST data included in the request. But when the whole document is cached, the snippet doesn’t run, so nothing is using the POST data. It’s like the phone rings and the answering machine picks up because nobody’s home. You can yell "help" all you want, the answering machine can’t help you and there’s nobody there to do anything. But if you have the snippet uncached, MODx will run the snippet, and it will pick up on the POST data and produce the appropriate output which gets plugged into the otherwise cached document.
                Studying MODX in the desert - http://sottwell.com
                Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                Join the Slack Community - http://modx.org
                • 7231
                • 4,205 Posts
                You will need to create a web user account to log into the private web section, the manager account will not work. In MODx 096x the web and manager users are 100% independent. There is a snippet named web2manager that will add an option to create a mirrored web account for an existing manager account.
                  [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

                  Something is happening here, but you don't know what it is.
                  Do you, Mr. Jones? - [bob dylan]