If, much like myself, you've recently activated the blog.module along with the blogapi.module, you've probably run into a problem as you navigate to the blog page of a user.
You've navigated to a page you know should exist.
Gah! I didn't ask for this. "Page Not Found". What the Frak!
Odds are you have not completed the activation process. Should you come across any of the following issues, here are a few tips on what you might do to resolve them.
List of Issues
- Page not Found
- Access Denied
Issue 1: Page not Found
The odds are on this issue, you've just not activated the blog and blogapi modules. It is quite important both modules be checked if you wish to have the User profile show the blogs available to a user.
Also, recommended is to check that the Access Controls (Permissions) are set correctly on all User Roles. The process does not end here though, as you will notice on the next issue.
Issue 2: Access Denied
This error can drop-kick even the most hardened of expert Drupalites.
The oft forgotten settings page. If you've gone ahead, felt smug about your Drupal Administrative skills, told your newest Drupal convert how easy it is to do things and had the audacity to prove to them the awesome power of a framework like Drupal, it may come as a surprise and an embarrassment, when you attempt to view the blog page [http://my.site/blog/2] and that dreaded of errors pops up: "Access Denied"!
How absolutely annoying, right? Fret not, as you can see, the graphic above shows a set of checkboxes that will make you feel like a Drupal God once again.
All you have to do now is check mark those content types you wish to have set as Blogs and away you go.
You'll note from this set of options, you really do not need to user the blog.module to allow a user access to a Drupal Blogosphere. In fact, you could choose to omit the blog.module entirely from you site. Opting instead to use one of the pre-made content types, or if you have the CCK module active, create your own blog content type and use that one. Either way, selecting one from the list of in the Blog API's Settings page will relieve you of that undue "Access Denied" frustration.
Click "Submit" and away you go. No more error. No more pain.