If the user in question is going to be editing pages, then he needs to be a logged-in Manager user anyway. Logged-in Manager users can see unpublished pages (unless you’ve created a role without that permission and assigned your editor users to that role). That’s why you leave these manager-only viewable pages unpublished. Manager users can see them; web users whether logged in or not cannot, even if they put the URL directly in their browser address bar. Unless you’ve disabled it, logged-in Manager users get the QuickManager menu bar.
QuickManager is a plugin. Go to Elements -> Manage Elements, and the Plugins tab. Click on QuickManager, and go to its Configuration tab. Scroll down and you’ll find a field for adding the URLs and titles for custom buttons in the QM menu bar.
'Tutorial','link','[~45~]','',''
there are five parts to it; the button title, the type (in this case it’s a link), URL of the page to link to (use MODx tags here for internal links), templates this applies to (irrelevant) and roles this applies to (irrelevant, unless you want to limit it to certain roles). You can have as many custom links as you want; separate them with || characters. Of course, too many of them might break the nice-looking layout of the QM menu bar, so it’s best to use custom buttons with some thought.
You can use QM to create a front-end management portal by creating an unpublished resource with buttons for various front-end functions, then create a custom button in QM to that page. Then set your manager users’ login home ID to that same page, and they never even have to see the Manager itself. If you’re going to be doing a lot of this kind of thing, learning all about QM is well worth your time. You can find documentation for it in the assets/plugins/qm/readme.html file.
☆ A M B ☆
☆ A M B ☆
