Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
Is there a way to have the user tick an 'appropriate usage' before they get access to a particular category of content on the site? I have some material that should be public but the user needs to understand how it is to be used.
Thanks
I'm running Drupal 5 RC1 with CCK 5.x-1.0-beta on OS X Server 10.4.8 (PHP 5.1.4, MySQL 5.0.25-standard, and Apache 1.3.33) and CCK nodes types are not working. Everything else works fine so far with Drupal 5 RC1, but when I create a new CCK node from a CCK content type I defined, the page returns PHP warnings and doesn't display any data from that CCK node. For example, I created a CCK content type that has 5 fields, for each field I get the following error when trying to view that node in Drupal:
I have found "Random Image Block From One or More Galleries Using Views (http://drupal.org/node/82617)" extremely useful on how to display several random images.
This has worked successfully in displaying images on the sidebar but what I'm hoping to do is display 4 random images in a square in the centre of the screen.
I am redesigning my school's website and I'm looking to use Drupal. I will admit, I'm new to this CMS as well as to the navigation system that Drupal empowers. Here's the story:
1. I need to seperate the website into 6 main sites: one for each of the schools in our school district.
2. Within each school I need to have menus and submenus.
3. So I have 6 menus and 6 sites and I need to pair them up so that the menu only appears on the pages that it coinsides with. I also need to have links to the 6 different schools at the top of the page.
I suppose it's a sign of progress that I've made it this far without giving up. :) I'm starting to get the hang of Drupal themes, and I'm starting to get familiar with the Drupal modules and standard maintenance...
... but there's one prominent part of Drupal I don't like at all -- that's the navigation block. It takes up too much space on a sidebar, and there are too many sublinks for it to flow properly across the header.
Only user/1 is able to set the permissions. When logged in as another user the permissions boxes show up when creating content, but any choices of view/edit are not entered into the node_access table upon submit.