Node privacy by role: node view and edit permissions

The node privacy by role module allows users, when creating or editing a post, to select which roles of users on a site will have view, edit, or delete permissions for the node. Community leaders frequently want to give permissions to roles to create and manage content for a site. The ability to publish information, that would traditionally be hoarded, allows communities to educate each other while still preserving the value of knowledge.

Archive: view content by date

NOTE: This module has been removed from core as of 5.0

The archive page allows content to be viewed by selecting the day. It also provides a monthly calendar view that users can use to navigate through content.

Working with the Help system

The Help module supports Drupal's help system. It displays context-sensitive help, as well as the core Help pages provided in the administrative section.


Core Help landing page


Contextual help in Drupal 7

The main reference Help pages can be accessed by navigating to Administer > Help in the Toolbar in Drupal 7, or by going to the URL http://www.example.com/admin/help in any version. In Drupal 7 you can also access the help pages via any of the "Get help" links on the Module administration page (Administer > Modules or http://example.com/admin/modules).


How to access Help in Drupal 7

The help text provided via the Help module (via help hooks in each individual module) displays a brief explanation of various settings, uses, and configuration options, to help guide administrators and users. Administrators cannot alter the help system's text, as it is built into each module's code.

Enabling user pictures (avatars)

User pictures (or avatars) or pictures are part of the user.module, not the profile module.

Share tables across instances (not recommended)

You can share tables between Drupal installations by setting table prefixes ($db_prefix) on only some tables but not others. One interesting application for this is to share the taxonomy tables (vocabularies, term_data). Another interesting use is to share users across Drupal installations. To share tables in Drupal, sites must be shared in the same database .

Warnings!

This procedure could result in unexpected results, depending on which tables you choose to share, including broken version updates and/or security holes.

Upgrades to the next version of Drupal are not supported! Be sure you have read EVERYTHING on this page, most especially the issues surrounding a major Drupal upgrade, before considering using shared tables!.

Configure error reporting

Where Drupal, PHP and SQL errors are logged. On a production server it is recommended that errors are only written to the error log. On a test server it can be helpful to write logs to the screen. By default, errors are displayed to the screen. You should change this to 'Write errors only to log' only for your production site.

You can tell Drupal to automatically discard error log entries older than the age you specify. This requires a crontab (example.com/cron.php) to be set up. See step 6 of the install.txt for example of setup.

Pages

Subscribe with RSS Subscribe to RSS - Drupal 4.7.x