Users unable to edit their own blog posts

By jasko on 7 Jan 2005 at 21:04 UTC

Aren't users supposed to be able to edit their own posts? A problem was brought to my attention on my relatively young Drupal 4.5.0 site. Since I always log in as admin, I always get the "edit" link when looking at nodes. But regular users don't. I have the "edit own blog" permission set for authenticated users, but it doesn't seem to work.

I logged in as a regular authenticated user, and created a blog post. Then I tried to edit it, and the link was there! I edited it successfully and deleted it. Then I went to my blog (the blog I have as as a user, rather than as "admin") and tried to edit another entry - no link! I even tried going to the /node/nodenumber/edit URL, and got an Access Denied screen.

What's up? I can understand disallowing editing of forum posts (it wouldn't be fair for me to change my words after you wrote about them) because that's built for conversation. But blogs are built for expression, and users should own them.

Thanks in advance.

Comments

Seriously?

jasko commented 11 January 2005 at 23:16

Is there really nobody with a clue for me here? I have compared the records of editable and non-editable blog nodes in the database and found no striking differences.

Have I really stumped all of Drupal.org or did posting this on a Friday afternoon just doom it to obscurity?

jasko
admin of
http://fortprogress.org

You do not have your user permissions set correctly.

grohk commented 12 January 2005 at 00:03

Goto:

administer >> users >> configure >> permissions

The blog module has one permission associated with it -- edit own blog -- Set this permission for all user roles that you wish to have the this ability.

Search is your friend. I searched for the words "edit own blog" and found that all of this information is readily availible in the Drupal Handbook under Administrator's guide » Drupal modules and features: A blog for every Drupal user.

http://drupal.org/node/280

---
Code Orange: Drink Your Juice

I wish it were that simple

jasko commented 19 January 2005 at 13:22

Actually, my permissions are set exactly like that, and have been since I enabled the blog module. I have created a screenshot showing the problem- the logged in user (my non-admin account) is browsing his / my own blog post and unable to edit it - there is no link. Going directly to the editing URL produces an "access denied" error.

But the post the screenshot is in wasn't perfect the first time and I was able to edit it normally. And as admin, I can edit everything.

Thanks, Code Orange - I appreciate your response.

Jasko
admin of
http://fortprogress.org

Can it be this simple?

gonzocoder commented 23 January 2005 at 14:54

Hi Jasko,

Log in as the person who posted the blog entry, click on the title of the entry (in your case "Phew!") and you'll see the edit tab.

Barry

Regrettably not

jasko commented 24 January 2005 at 14:06

I'm posting this here to make sure if we get a resolution the trail is available to the Drupal community at large.

Current blog posts can be edited - that is, I could click on the post that Barry responded to and have an edit link. But an earlier post in the same blog, same user, logged in (same session, even) cannot be edited.

Barry is helping - others welcome to chime in. I think we're past the "you're not using it correctly" stage though - which is quite welcome. I would have been happier if it had been a simple user headspace error, too.

admin of
http://fortprogress.org

A hint for you

RoxanneJ commented 26 January 2005 at 13:16

I'm using the bluemarine theme, so this suggestion may not apply if you are using something else (switch to bluemarine for a minute?) but you can edit/delete posts using that them under administration>content>blogs>edit/delete.

Of course, this limits editing capability to the Administrator, but it's a way in for urgent changes.

You can also switch to chameleon for full capability for editing.

Same problem different install

RoxanneJ commented 25 January 2005 at 18:14

Using the themes/bluemarine means there is no Edit menu on any content. In fact, any theme BUT themes/chameleon creates many problems with disappearing content.

This is because no them but chameleon invokes the .theme file and makes using other themes useless.

Even the LOGO doesn't appear unless you aren't using chameleon.

This is very frustrating because these problems have been reported and no action taken on them.

Since my hosting company did a system wide installation at my request, a "hack" isn't possible without effecting the default themes. I really don't think his other users want MY logo on their implementation of Drupal.

Same problem

jsimonis commented 20 September 2005 at 04:05

I've run into a similar problem.

People with the permission to be able to edit pages cannot edit those pages.

Using the privacy by role, I've set it so that the role can edit each of the content types. I've checked, and within each actual posting, that role is selected for editing.

I've even made sure that "admin" have all permissions regarding editing content. Still, the edit tab doesn't show up and if you go to it manually, it gives you the page stating you don't have permission.

I've tried changing themes, but that doesn't change anything.

Items I've posted today have the "edit" tab, but not older ones.

--
Jenni S.

Solved...

jsimonis commented 20 September 2005 at 04:11

I just figured out the problem on mine.

I'd turned off the ability for people to post in "Full html." That option used to be on for others, but not now. I expanded filtered html's tags and they can use that or plain text.

However, some pages were still in full html. As such, those without the ability to post in full html could not edit those pages.

It didn't even occur to me that the input filters could be causing the problem.

--
Jenni S.