ACL to replace backend

[gliderguld]

Does more than history command the frontend/site - backend/admin separation? Before ACLs were introduced it was a fine substitut, but is it really needed now?

I'm asking out of curiosity, but also becauce I think I se a lot of redundant code or workaround hereof in theese two applications.

Yours,
/Poul

[ranwilli]

As we're expressing only opinion, I would say you're correct, it isn't strictly necessary, but it is extraordinarily convenient for developers, and I don't see a shred of "work-around" in well-crafted extensions.

Redundancy, perhaps... of little consequence in my opinion.

[rcarey]

To some extent I agree with your perception. But pragmatically, I think we need the separation. While the ACL alleviates the need to separate the front from back, it does so only if the ACL is set up correctly. Too many site developers (and especially single-site owners) don't fully understand the ACL, so the separation protects a good many sites.

[gliderguld]

Thanks for the replies.

If a default ACL-setup can't replace frontend/backend, it isn't designed as well as I thought.

I am considering making all of my extension in one of the environments, but am facing challenges:
* Menu-items are linked to views/xxx/tmpl/yyy.xml, which can be frontend only.
* Management of categories is backend only.
I am affraid there are more like theese. But maybe I missed something - I'm still learning?