Hello,

I am part of a small team building a drupal website for our college. One of our members installed the rules module on our site. We are running drupal 7.7 and when the rules module was installed it removed the ability for ANY node to be viewed by any user who was not an admin even though all the permissions have been set properly. The site displays an access denied error to all the nodes except admins regardless of permissions now.

We tried uninstalling the module using the drupal interface but no luck as we still get access denied on every node. In addition to this problem we cannot uninstall the rules module from the server it self without crashing the entire site with a fatal error in the bootlog. Therefore we are really at a lost as to what to do.

Any help would be much appreciated be my team. Weeks of work and research went into our site and this rules module seems to have really mess things up

CommentFileSizeAuthor
rulescrash2.jpg271.28 KBwferrell343
rulescrash.jpg214.49 KBwferrell343

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Component: Rules Core » Rules Engine
Category: bug » support
rawrzors’s picture

rawrzors commented

Have you tried to remove the rules entries from the table in phpMyAdmin?

invisibleink’s picture

invisibleink commented

Normally modules will still appear on the modules page after uninstalling, unless you remove the module files from the server. I would try removing Rules, updating core, then reinstalling Rules. Also, making frequent backups with backup_migrate can shorten recovery time from code conflicts.
I have seen similar problems with Rules, and found that using the most recent release reduces this type of frustration.

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
commented
Priority: Critical » Normal
Status: Active » Fixed

as rules doesn't appear enabled it should not cause the errors you are experiencing.

in order to make sure, you can remove the rules modules folder as well.

Status: Fixed » Closed (fixed)

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