Remember to back up your database first!
Also, you might consider working with a development/test setup and then deploying tyhe last stable version from there to production site in future.
Victor Kane http://awebfactory.com.ar
On Mon, Dec 1, 2008 at 1:00 PM, Daniel Carrera daniel.carrera@zmsl.com wrote:
Hi Victor,
Thanks, I'll definitely try that. I'll wait until after business hours, just in case something goes wrong. In any case, what you describe ("regular, normal, fresh Drupal install") sounds like exactly what I want.
Thanks. I'll write back in a couple of hours and report on whether these ideas worked or not.
Cheers, Daniel.
Victor Kane wrote:
Here is a silver bullet for this problem (backup your database first).
Assuming you want to return to a state in which no access modules are at work, in which everything is like a regular, normal, fresh Drupal install, you:
- Delete all rows from the node_access table.
- Perform this command:
db_query("INSERT INTO {node_access} VALUES (0, 0, 'all', 1, 0, 0)");
That should leave your table looking like this:
nid gid realm grant_view grant_update grant_delete 0 0 all 1 0 0
Then things should be right as rain.
Victor Kane http://awebfactory.com.ar
On Mon, Dec 1, 2008 at 12:34 PM, Daniel Carrera daniel.carrera@zmsl.com wrote:
Ok, I'll do that in 2 hours. Right now a customer is demo-ing the website to his boss and the last thing I want is to break something mid-way through the demo (I gave the customer admin rights just for today so he could do the demo).
Daniel.
William Smith wrote:
Clearing the cache is worth a shot, and yes it is safe to delete everything from the cache* tables
On Mon, Dec 1, 2008 at 9:15 AM, Daniel Carrera <daniel.carrera@zmsl.com mailto:daniel.carrera@zmsl.com> wrote:
Hmm... it doesn't seem to help. Maybe I have the wrong permissions set in the access control page (admin/user/access) but I don't think I do. Under "node module" I have the "access content" permission set for anonymous users. That's all I need, right? All the other permissions in this section are "administer" this, "create" that, and "edit" the other. Is there some other permission I should check? Is it possible that the Drupal cache is acting up? I see five cache* tables in the database (cache, cache_filter, cache_menu, cache_page, cache_views). Is it safe to delete everything from these tables? Might that help? Daniel. Bill Fitzgerald wrote: > Try rebuilding your permissions table at admin/content/node-settings > > Daniel Carrera wrote: >> Shit. It's worse than I thought. It looks like only users that have a >> role with the "administer nodes" permission can view these pages. In >> other words, only site administrators can view these pages. This is >> horrible. >> >> Help! :( >> >> Daniel Carrera wrote: >> >>> Hello, >>> >>> I was using the "taxonomy access" module but I decided that it doesn't >>> do what I want, so got rid of it. That is to say, I didn't delete the >>> categories, but I set them to not be used for "Pages". >>> >>> Here is my problem: Some pages are now inaccessible to anonymous users. >>> When you go to the page you get an access denied error. I'm getting >>> stressed about this because my users are mad and they want to show their >>> pages to other people. >>> >>> I have gone to the regular permissions page (admin/user/access) and >>> under "node module" the permission "access content" is activated for >>> anonymous users. >>> >>> I don't know what to do and I was hoping someone here had an idea. I'm >>> using Drupal 5 btw. >>> >>> I would welcome any help. >>> >>> Daniel. >>> >> > > -- [ Drupal support list | http://lists.drupal.org/ ]-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]