changing the default template

Hi!

Ok, thank you. I did new "not-found" page (resource #123) in web-context and configure the system settings to use that new error_page.

When I write www.sitename.com/whatever/ it shows that "page not found", but when I write www.sitename.com/archives/ it's still shows the default page template for that resource.

The only thing why I need that "archives" context to run is to give rights for only one user to fill that page in manager.

Tom

Wait a minute... you are using a context just to control what a user can edit? Well, you can do it that way, but it'll give you more trouble than it's worth.

http://bobsguides.com/controlling-access-to-resources-in-the-manager.html

Thanks again!

Is it also possible to give rights just certain people who can see this resource (archives) on front-end? I remember to read it somewhere that's not possible, but maybe I'm wrong. At least the resource (archives) need some kind of login system.

I really have Bob's book MODX: The Official Guide, but unfortunately it's not on my hands right now, that's why I try to remember how to handle different contexts.

Tom

You might want to take a look at http://bobsguides.com/blog.html/2013/05/22/protecting-pages-the-easy-way/

There's also the PageLocker extra, which might be more what you are looking for. http://modx.com/extras/package/pagelocker

That's why I have BobRay's site bookmarked in my browsers, as well as the main MODX documentation page.

BobRay has now released his book in e-book format so it's on my pad and my phone.

To refresh your memory, here's what it says in the book:

Do You Need Another Context?

Contexts complicate the administration of the web site, so before implementing them, you should be sure that there’s no way to achieve what you want without them. To hide subsets of resources from certain users, for example, it’s generally better to use resource groups and ACL entries rather than contexts.

I'm using contexts for my mashup of RO.IDEs and cssSweet, but the resources in the "stylesheet" context are never accessed directly, they're just concatenated into one uglified .css file using a getResources snippet (well, I use pdoTools and pdoResources) and cssSweet. In such a case, an ACL for the "stylesheet" context could be used to only allow designer users to access the CSS resources.