Restrict specific folders from public download (via .htaccess)

See the official online handbook for more information about securing private files. The information about private files starts at the "Managing file locations and access" header.

If you set "public" as the download method, you can still protect some of your folders by settings in your .htaccess file, if you have mod_rewrite enabled.

For instance, if your files live in sites/default/files, and you want to protect everything in sites/default/files/protected_download_dir, then you can add the following line to your central .htaccess file:

RewriteRule ^sites\/default\/files\/(protected_download_dir\/.*)$ index.php?q=system/files/$1 [L,QSA]

The files in this folder (or, all files that match the regular expression) will not be served directly by apache, but by a full drupal request using the file_download() callback. The routing for system/files is defined in system_menu().

It is recommended to force the browser to download the file instead of displaying the file. If you for instance offer a protected .jpg for download, the browser will try to open it in the browser which will result in a 404 (which means access denied in this case).

Additional fields (CCK)

If you wish to have additional fields displayed in your ads (e.g. Price, Colour, Size, etc.) then you should install/use the CCK (Content Construction Kit) module.

This module allows you at add fields to your Classified Ad content type and change the order of the fields and display format.

Classified Ads 6.3 only

Adding CCK will also enable you to adjust the placement of the Ad expiration gadget on the node editing form and the node view, and to customize the display of Ad lists built by the module.

emulate the apache directory behavior, redirect example.com/folder to example.com/folder/

This module allows Drupal to replicate the apache behaviour regarding directories, namely that when a request for http://example.com/folder is received it's redirected with a 301 to http://example.com/folder/ (with a trailing slash).

Troubleshoot installation problems

Links to some of the more common installation issues are listed below. More troubleshooting information is available at the Troubleshooting FAQ.

Fatal error: Allowed memory size of n bytes exhausted

The error "Allowed memory size exhausted" indicates that Drupal needs more memory than has been allocated under current settings. This error can be resolved by adding an extra line to Drupal's configuration files.

Failed to connect to your MySQL database server

The installation script cannot connect to the database. Check if the username, password and hostname that you provided are correct.

Cannot create directories 'files' or 'private'

The installation script needs permissions to create these directories inside the sites/default folder.

Cannot write to configuration files settings.php

The installation script needs permissions to write to the configuration files settings.php.

Blank page (White Screen of Death)

Occasionally the page is completely blank (No content. No errors.) This is what is sometimes referred to as the "White Screen of Death". There are several reasons why this might occur.

Calendar Module How To

Here's a tutorial video with a detailed look at the Calendar module and how it interacts with the Date module, Views and CCK. Covers some of the differences between date field types and highlights the changes you need to make to feel comfortable using Calendar.

Drupal tutorial video about using the Calendar module. Running time is about 22 minutes.

Gigya (7.x-4.x) - Configuration & Customization

Settings

The module can be configured from the Configuration>>Web services>>Gigya settings menu.

Pages

Subscribe with RSS Subscribe to RSS - Site administrators