In the version of BigTree that we're currently using (v4.2.24), there are NO warnings when doing things like:

1. Publishing a page that has pending changes.
2. Archiving a page.
3. Deleting a page.

We've experienced instances where all three of these have been problematic.

Early on, someone (who was used to the icons used in our previous CMS) clicked the wrong things and managed to archive and then delete an entire section of our website. Luckily, we were able to restore it from backup and there were relatively few changes that had been made elsewhere on the site (so not much else got "lost" when we restored from backup).

Today, we had someone edit and publish a page without realizing that the page already had been edited and not published by someone else. So, placeholder text and images and whatnot that were in there as part of that ongoing page-editing process showed up on the public site.

It stands to reason that there should be some sort of warning at least to help reduce the chances of any of these things happening:

1. "Warning. You are about to publish this page that already has pending changes. Are you sure you want to do that?"
2. "Warning. You are about to archive this page (and any subpages of this page). Are you sure you want to do that?"
3. "Warning. You are about to delete this page (and any subpages of this page). Are you sure you want to do that?"

(That sort of thing...I'm not a wordsmith or anything, so the exact wording wouldn't need to be this, of course)

#1 could go even further and provide a way to see what the pending changes are (see my other Feature Request post, made a few minutes ago), but at least providing some sort of "are you sure you want to do that?" warning might make users thing twice before proceeding.

It's entirely possible that some/all of this functionality is in place in a newer version of BigTree than what we're currently running...and that's fine, as we plan to upgrade our BigTree version sooner rather than later.

Anyway, just a thought that I figured I'd share.

Doug Thompson
Manager of Web and Electronic Communications
Ohio Wesleyan University

Currently, it's very much an "all or nothing" situation in regards to us granting access to the calendar/events module and to the news module. Since we're such a large organization and have users scattered around all over the place, we basically have to give the "keys to the kingdom" to users that we want to have edit/publish access to those modules. They either have access or they do not...there's nothing in between.

If there were a way to assign specific categories within those modules to users, I would think that would be ideal.

That way, for instance, you could have a user that is only responsible for (and only has access to) a specific category of calendar event, or a user that can only see/edit three news categories instead of all 50+...things like that.

We're only at BigTree v4.2.24, so I have no idea if that sort of thing has already been addressed in one of the many minor versions of BigTree that have come out since, but if it hasn't, maybe that would be something useful to do in BigTree 5?

Doug Thompson
Manager of Web and Electronic Communications
Ohio Wesleyan University