my head is spinning from all the patches, i tested on 5.5 and get database errors

Comments

vm’s picture

it would help to know verbatim what those errors were.

It would also help to know what "patches" you are talking about ? or did you mean modules ?

darumaki’s picture

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'update tinyint(3) unsigned NOT NULL default '0', delete tinyint(3) unsig' at line 5 query: CREATE TABLE simple_access_node ( nid int(10) unsigned NOT NULL default '0', gid int(10) unsigned NOT NULL default '0', view tinyint(3) unsigned NOT NULL default '0', update tinyint(3) unsigned NOT NULL default '0', delete tinyint(3) unsigned NOT NULL default '0', PRIMARY KEY (nid) ) TYPE=MyISAM /*!40100 DEFAULT CHARACTER SET utf8 */; in 


user warning: Table 'drupal.simple_access_node' doesn't exist query: SELECT na.gid, na.view, na.update, na.delete FROM simple_access_node na WHERE na.nid

just to name a few

vm’s picture

It would also help to know what "patches" you are talking about ? or did you mean modules ?

darumaki’s picture

it was the mod but i gave up on it already,

vm’s picture

Status: Active » Closed (fixed)
oboingo’s picture

Status: Closed (fixed) » Active

You attempt to create the simple_access_node table in simple_access.install. You have columns like "update", "delete."

These are reserved words in MySQL, and no wonder during installation of the module the table creation fails. Please fix as this module might otherwise be useful.

gordon’s picture

Status: Active » Fixed
suzzer’s picture

Can someone confirm this module actually works on 5.5? I can create an access group, and set it on some content. But it doesn't seem to actually restrict anything. Anonymous users and everyone else can still see the content.

suzzer’s picture

Status: Fixed » Active
gordon’s picture

Status: Active » Fixed

Yes I test and do all development on 5.5

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.