hhanna

Well, I have gone down the demo route already.

The problem blindly selecting options and investigating what happens means I can miss a whole lot. If I know what an option is supposed to do, I can then test to ensure it behaves as expected. If I don’t know the criteria to test against, it becomes less testing and more a process of discovery.

For example: On a demo site, I activated the “archive” setting. Then, when I visited the blog (still logged in as super admin), I saw a fully functioning blog. I didn’t know I had to log-off to see a difference. Hence, not testing and more a process of discovery.

You (wptesting) gave me a criterion to test. You told me an archived the site is no longer visible to non-super admins. I tested to ensure that was accurate (and it was).

Thanks for the suggestion.
Does anyone know if documentation exists for these options?

Ah yes… I see that now.

Have I explained the difference between “archive” and “deactivate” correctly? (See below)

Archive: Only network/super admins can archive a blog. It is essentially a way to suspend a blog. All data remains intact and the blog can be unarchived. Upon navigating to the blog, users will encounter a message “This site has been archived or suspended.”

Deactivate: Only network/super admins can deactivate a blog. This is a means to take down a blog. All data remains intact and the blog can be re-activated. Upon navigating to the blog, users will encounter a message “This user has elected to delete their account and the content is no longer available.” (Is the message accurate? When a blog admin chooses Tools > Delete Site, does it just deactivate the account or does it actually destroy the blog? Judging from the wordpress message above, I’d assume a blog admin’s “delete site” request would just deactivate the blog, not destroy it.)

Can anyone add to this or do a better job explaining the differences? Did I miss anything?

Correction, that last line of code is meant to read:
update_option('widget_classroll', $classroll_options);