Archive

Archive for January, 2012

Howto redefine the hostname on Debian/Ubuntu

January 24, 2012 2 comments

Just a small procedure as a self-reminder (I seem to have to use it just seldom enough to forget it each time – thanks Marvil):

  • define the new hostname on the 127.0.0.1 localhost line (after localhost) in /etc/hosts
  • set the new name in /etc/hostname
  • issue a “hostname -F /etc/hostname
  • done
Categories: English, Techie Tags:

Drupal 7 problem: Content edit tab doesn’t appear for user editor

January 11, 2012 1 comment

In Drupal 7, there is a *very tricky* problem you might fall upon at some point. We did and because it’s not *really* a Drupal bug (although it could be considered as a usability bug), it’s worth writing down.

The problem is simple: one admin (Joe) and two editors (Sam and Max) edit a website. They all create their own content of the type “artist”.

They all have permissions to “Create artist”, “Edit own artist”, “Edit all artist” and “Delete artist”.

Also, the “artist” content type has a text body which can use the “Pure text” format, the “Filtered HTML” format and the “Full HTML”. However (and this is part of the problem), editors can only use “Pure text” or “Filtered HTML” (through the WYSIWYG module)

  • Sam (editor) can create an artist and edit it
  • Max (editor) can create an artist and edit it
  • Joe (admin) can create an artist and edit it
  • Sam can edit the artist that Max has created
  • Max can edit the artist that Sam has created
  • Joe can edit the artist that Sam or Max have created but…
  • Sam and Max cannot edit the artist that Joe created. That is, they can see the content, but for some obscure reason, the edit tabs do not appear!
  • “WHY OH WHY???” …I hear you say. The answer required (the first time) a little bit of investigation

The answer is in the WYSIWYG module’s configuration. Because Joe (admin) created his artist using Full HTML (because HE CAN but also because that’s the default for the admin role), and because the editors CANNOT use the Full HTML style. When this happens, Drupal detects it and automatically prevents the edition of the content by the editor users…

The fixes are easy:

  • update the editor role to give him Full HTML permissions
  • update the content (as admin) to use Filtered HTML
  • update your node_revisions table to change the edit type to another number

 

%d bloggers like this: