3.3: final preparation and performance

And now the snippets and testing pages should (mostly be removed). Please give pixelhick.com another whirl to make sure I didn’t miss anything. QE is dues a minor update, but I’ll get a testing build out as soon as possible.

The "Add a Blog Entry" link (item 5 in the Mini-Blog HOWTO) is a bit problematic. If I click on the link, not being logged in as the correct web user, I get shipped off to the Login page, which says something about needing to be logged in to comment.

That message in the login page could be confusing, since they are expecting to see references to creating blog entries, not commenting. At first I thought the link was pointing to the wrong page!

It looks to me, redundant as it may seem, that the not-logged-in reaction to the Add a Blog Entry page needs to be a different Login page. It shouldn’t offer a registration feature, for one thing.

I see what you mean. Problematic indeed from a usabilitty standpoint.

I’ve created such a page; it won’t show in the menu (document id 37). I’m not sure how to make it the not-logged-in error page for the Add a Blog Entry page, though.

I don’t think you can ... you get one page globally for this purpose. Maybe the not logged in page should in fact go to a different unallowed page from the global login link. I think it should and will make this change. Good catch and thank you Susan!

Or, maybe that item shouldn’t even be a link at all under these circumstances. Normally, there wouldn’t be a link visible unless the user is properly logged in.

I tend to agree, but if we got it absolutely right the first time, there’d be no reason for additional releases!

Lemme make a few revisions incorporating your new login page and let’s see if it makes more sense.

Even if it does go to a different page, that won’t help in the install default page, since the user won’t have a proper login to login with! Unless we supply a default blog user login? Kind of like the default manager login?

I think the instructions cover it. If not, the revised unauthorized page do a better job of getting the point across. Good enough, I think, anyway. Pefect, no, but better than a lot!

Forgot to mention:

We need to turn on Access Permissions by default so that webuser accounts can be properly created to access blogs!

Good point. I think there’s multiple config flags that can be set differently for common usage... let’s list them here.