D6
Ministry Intranet Style Site Security
I'm working on a D6 site that could be considered an Intranet style site for members of our ministry. It is accessible from anywhere on the Internet, but should have very little content available without logging in.
How do I best lock down the site so that people have to log in before getting information without showing an "Access Denied" page at the first page where they log in? I envision a future where blogs with some public facing content could occur so I don't want to lock out that option in solving this problem.
D4 - Deep Drupal Development, Dude | Agent16
Agent16 has an immediate opening for a freelance Drupal developer. This is a full-time, on-site, freelance/contract position near Union Square in New York City. Reports directly to the CTO.
Are performance optimisations still going into D6?
I'm assuming it's too late, but if not here's an easy performance win for D6:
<
blockquote>The type column of the {system} table is currently a varchar(255) field. Yet in 99% of all Drupal installations it stores either the text 'module' or the text 'theme' and nothing else. This is already a strong case for making it an int column and defining constants for module and theme. Then, on every page, there is this query:
SELECT filename FROM system WHERE name = 'user' AND type = 'module';
Improved CCK for D6
KarenS who just organized a Drupal User Group, in Central IL, gave a presentation to it's founding members explaining a much improved CCK for the D6 release. CDMUG took notes and posted them to share with the Drupal community - check out our milestone 100th node post. ;-)





