Hi

I found hundreds and hundreds errors in my watchdog (evey day) after I enabled this module.
It is the same error but for each contenttype.
please note that I have set enabled only one contentype - 'uprofile' for work with cck field privacy, rest of them are unchecked on (admin/content/cck_field_privacy). Currently I have set cck field privacy permissions only for admin but errors are with userid of various authenticated users.

I did site update, clear cache, but nothing helps.
this is one of examples of watchdog errors:

Table 'somvprahe_sk_1.cckfp' doesn't exist query: SELECT field_name, permission FROM cckfp WHERE uid = 3229 AND type_name = 'blog' ORDER BY field_name DESC in /home/users/somvprahe.sk/web/www/sites/all/modules/cck_field_privacy/cck_field_privacy.module on line 110.

thanks
Igorik
http://www.somvprahe.sk

Comments

igorik’s picture

igorik commented
Status: Active » Fixed

Hi
I found that cckfp table wasn't created. (don't know why, I migrate from drupal 5 2 weeks ago)
However, I uninstall module, install again and the table is created and errors are gone.
Bye

obsidiandesign’s picture

obsidiandesign commented
Assigned: Unassigned » obsidiandesign
Status: Fixed » Active

I'm actually going to re-open this as a task for myself, since there should not be tons of watchdog output simply because something's up with the module - I'd like it to be more graceful (a status message, for example) instead.

obsidiandesign’s picture

obsidiandesign commented
Title: hudreds errors in watchdog after enabling this module » Unnecessary Watchdog output created if CCK Field Privacy table doesn't exist

Re-titling to be more specific about what the issue is for.

obsidiandesign’s picture

obsidiandesign commented
Status: Active » Fixed

Corrected in next development snapshot. Module disables itself if the table is moved/deleted/renamed in some way and the site admin accesses the admin page (or any other place that triggers hook_requirements()).

Bryan O'Shea
Obsidian Design

Status: Fixed » Closed (fixed)

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