Post installation

I've been having duplicate entry errors related to my category_hierarchy module.

And so I went into phpmyadmin and saw this error in red in the category_hierarchy database: Primary and Index keys should not both be set for a column 'cid'

So, I made a backup and deleted the 'nid' which was causing the problem- the error message went away.
Since then, I've been fooling around with it, and aside from all the normal category bugs and goofiness, everything seems to be working- error free so far.

How do you manually configure Drupal's SQL settings?

I had a working instalation of Drupal for about a year, but then I upgraded to 4.7, decided I didn't like it, tried to revert, one thing led to another and I ended up with no drupal and a backup copy of my SQL database. It was a stupid accident that I would not enjoy explaining, and am not sure how it happened, anyway.

I've been playing around with drupal for a little while and well I've deleted a bunch of test nodes, but for some reason the archive module still thinks they exist, so it makes various dates a link and when you click on them it gives a 'no posts found' message.

Is there anyway to stop this.

I'm trying to prevent my "right" region blocks from showing up on civicrm pages. I tried configuring the blocks in question to show up on all pages except civicrm/*

But that doesn't work. Any suggestions?

Thanks,

Sean

Greetings,
Though I have seen this discussed I have not been able to find a good answer. I am looking to password protect a group of nodes- I want visitors to my site to be able to see a page and its subpages if they know a password but I dont want them to have to create an account.

For example if users choose the 'Faculty Development' section or any of its subpages they are prompted for a password that, when entered, would give them access to all of the pages in that section for the duration of their visit.

I am using Pacs ;-) to let specific user-roles' view and edit permissions in specific parts of a Book.

E.g. the the php-crew maintains the php sections and the js-crew maintains the js-sections - and everybody may view their sections.

My problem is that as the php-crew may view the js-sections, they can also add child pages there ...

How do I keep them from adding pages in other folks' sections (just to reduce confusion)?

Gorm