Is this module ready for use, yet? It's hard to tell with dev versions but I didn't see any warnings not to use it. This is what I got when I tried to install it:
# 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 '; /*!40100 DEFAULT CHARACTER SET UTF8 */' at line 8 query: CREATE TABLE content_field_privacy ( `uid` int(10) NOT NULL, `field_name` varchar(32) collate latin1_general_ci NOT NULL, `type_name` varchar(32) collate latin1_general_ci NOT NULL, `permission` char(1) collate latin1_general_ci NOT NULL, UNIQUE KEY `uid_2` (`uid`, `field_name`, `type_name`), KEY `uid` (`uid`, `type_name`) ); /*!40100 DEFAULT CHARACTER SET UTF8 */ in //includes/database.mysql.inc on line 172.
# warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /v/sites/all/modules/cck_field_privacy/cck_field_privacy.module on line 110.
I hope it's an easy fix... This module is just what I'm looking for to use with advprofile.
Thanks,
Michelle
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | cck_field_privacy.install.patch | 1.42 KB | obsidiandesign |
Comments
Comment #1
obsidiandesign commentedError confirmed; there's actually two different errors at play here:
1) The SQL syntax for creation of the table is wrong.
2) The variables storing the content types & CCK field preferences are not stored in the DB upon install, generating the 'array_key_exists()' error.
Comment #2
ms2011 commentedPatch looks great; RTBC.
Care to commit, Bryan? :)
Comment #3
michelleThanks, guys. I'll give this module another try soon as it gets committed. :)
Michelle
Comment #4
obsidiandesign commentedPatch committed.
Comment #5
djorn commentedJust confirming the patch worked for me as well (downloaded the module before the reroll).
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.