Not sure how to concisely describe the problem in title, feel free to correct it with better wording. But here is the problem I encountered on a fresh 6.0-beta2 install:

1. admin(uid=1) creates a new active user 'dami'. No new roles are created, and dami is in authenticated user role by default.
2. admin grants 'create/edit/edit own/delete/delete own page' permissions to authenticated user role. Note auth users do not have 'administer nodes' permission.
3. When dami tries to create new page node, following error pops up and the node is not properly created/saved:

user warning: Field 'log' doesn't have a default value query: INSERT INTO node_revisions (nid, vid, uid, title, body, teaser, timestamp, format) VALUES (3, 0, 3, 'asfsa', 'fdsadfsafd', 'fdsadfsafd', 1195160552, 1)

The error disappears if use has 'administer nodes' permission. I think I have seen similar errors in 5.x, and it has something to with revision log is set/empty or not. But can't remember what was it.

Comments

keith.smith’s picture

keith.smith commented
Version: 6.0-beta2 » 6.x-dev
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

@ dami: I just followed the steps you outlined above on a fresh checkout of Drupal 6, and did not encounter the problem you describe.

Specifically:

  • I created a new instance of Drupal 6 (HEAD),
  • As the administrative user gave, create/edit/edit own/delete/delete pages permissions to the authenticated users role,
  • created a new user,
  • logged in as that user,
  • successfully created, viewed, edited a page.

Perhaps this problem has been addressed since the Beta2 of 6 was released. Can you try this again on a copy of 6.x-dev from http://drupal.org/node/97368 and see if you still have the same problem (if so, please report back here) or if the problem has been addressed (if so, please set this issue to 'fixed').

Thanks!

dami’s picture

dami commented

keith, thanks for your quick reply. I grabbed the latest nightly build from the link you gave, but the problem still exists. Maybe it has something with my server setup? I was testing it on localhost with: mysql 5.0.45 and php 5.2.4

Ok, after a bit more testing, I think it's related to mysql strict mode. The error is gone after turning off strict mode by:

set @@global.sql_mode='';

Not sure it still qualifies as a bug or not.
BTW: Can anyone test it with pgsql to confirm it's not a problem there?

keith.smith’s picture

keith.smith commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

I believe this to actually be a duplicate of http://drupal.org/node/188462 and am marking as such. Please reopen this issue if I am mistaken.