Why do new versions of pages require approval?

Permalink January 19, 2010 at 7:41 PM

I edited several pages on a client's site (still in development) yet didn't notice until much later that the changes weren't visible when logged out of the site - the older version was still the publicly viewable version.

After searching the forums I determined this was because the page edits required "approval" before being seen by the public. It's true, the bold approved version was in some cases many revisions behind the most recent.

This behavior seems odd - I seem to remember that in the past, all my edits would take effect automatically. Is this a new "feature" added to 5.3.3.1, or a bug, or am I wrong and it has always worked that way?

I would like to set it up so that new edits by admins are automatically published for everyone without requiring the extra step of approval. I see the benefit of having old versions of pages saved in case something goes wrong, but being forced to click several extra buttons just to confirm the publishing of a page edit is a hassle for my client. How can I make this happen, or fix the problem if it is indeed a bug?

Thanks-

ScottC replied on Jan 19, 2010 at 10:58 pm Permalink Reply

depends i guess, but i think that you have permissions set up as advanced so you need to explicitly set up this stuff. In simple permissions mode if you can edit a page generally you can add a page below it etc since you are either the super user or the administrator.

you might want to go to the sitemap as superuser, click the homepage, and set permission there so administrators can edit. I haven't looked at this stuff in a while since I wrote up the permissions layer on top of the blog app, but generally this stuff just works unless you've done something to mess w/ it.