Blogapi will not function without blog.module
| Project: | Drupal |
| Version: | 5.7 |
| Component: | blogapi.module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
I've been working on building a Drupal 5.6 site that does not make use of blog.module. I enabled blogapi.module and set one of my CCK content types to be publishable, but no matter what I did, I kept getting the same error in any of several desktop blogging applications, You either tried to edit somebody else's blog or you don't have permission to edit your own blog.
That error is from the following code in blogapi.module, lines 512 - 519:
if ($user->uid) {
if (user_access('edit own blog', $user)) {
return $user;
}
else {
return t("You either tried to edit somebody else's blog or you don't have permission to edit your own blog.");
}
}The 'edit own blog' permission, is from blog.module, so without blog.module enabled, only uid 1 will ever be able to post content via blogapi, regardless of the settings in admin/settings/blogapi .
It looks like this has been fixed in the HEAD version of 6, so what's the proper approach to this for 5? Should we:
- Make blogapi.module require blog.module,
- Backport the fix from Drupal 6, or
- Instead check to see if the user in question can edit the content type they're attempting to post
Please let me know, and I'd be willing to try my hand at a patch - I just want to know what path is the right one to take on this.
#1
A quick status change, because I know what's wrong, but would like guidance on the right way to go about fixing this issue.
#2
Hello Steven,
I back ported the changes from Drupal 6.2. I had the same issue with the Drupal 5.7 blogapi.module. I wanted to use Ecto or MarsEdit with my blog and did not need the blog.module installed since I am using a custom content type for blog entries. I have attached a patch for Drupal 5.7 blogapi.module below. It would be great if this could be committed to Drupal 5 core.
Thanks!
Mark
#3
Committed to 5.x.
#4
Automatically closed -- issue fixed for two weeks with no activity.