I've create a Content Type vocabulary with terms like Static, Book, Book Page, Blog, etc. My goals were:
to create several department front pages (my other vocabulary is Department) that each list everything except blogs
to provides department-specific links to a particular content type, like all books in department XYZ
Now, the first goal was easy; I just told Drupal not to make the Department vocabulary available to blogs. But the I had to create the Content Type vocabulary to meet the second goal.
I've read through many of the forum messages, but I'd like someone to clarify what is going on with permissions in the next major release after 4.3.x.
Will I be able to specify that a role or user X has read or read-write permission on a particular node?
Will taxonomy permissions be there? For example, if you have a Department vocabulary, creating a node under Sales would require different permissions than creating a node under Development.
Will rights and roles be grantable? For example, members with the Administrator role could grant the right "administer node" to other members, but regular members could not. Like in Oracle.
Will the first user stop being so special, and we get a real Administrator role?
Is this already in CVS, and how stable is the CVS version?
I'm ready to use Drupal as a lightweight CMS, but the 4.3.x permission system really doesn't promote collaboration very well. I'd like to collaborate on static pages and book pages, but only the book pages have an "edit node" (and everyone can edit that node, too).
Also, I'm using webserver_auth.module to integrate with Active Directory (using LDAP authentication support in Apache). Works very well. Can I somehow use Active Directory groups to give access? For example, assign a role to a group that came from Apache authentication?
I've been using Drupal since 4.1.0 with PostgreSQL. While this version works flawlessly, we're having trouble upgrading from 4.1.0 to first 4.2.0 and now 4.3.x.
When I first tried upgrading to 4.2.0, I ran the update script, and IIRC, I got no errors. The main page would return
[html][body][/body][/html], though. I thought it was our custom theme, and despite trying to do changes to see if it liked it more, it wouldn't help.
How can I prevent Drupal from hijacking my subdirectories and without compromising security?
I have existing content in a typical website directory structure and would still like to be able to access it AND drupal simultaneously.
How can I put a section on the front page without it being a 'post', where it can be commented on, shows a timestamp etc? Maybe I have a product that I would like to talk about on the front page without it being a post, story or any content from the DB, just some static HTML and images etc...
I was interested in creating a fine-grained access control to my drupal site. Out of the box, Drupal users can either have permission to access or not to access content.
What I'd like to do is more selectively allow permission to access content by type. For example, I would like only logged in members to be able to access some static pages and Forums while non-authenticated users should be able to view other content.
Is there a way to do this without modifying drupal code? Has anyone implemented such a concept on their site?