It is said that Drupal photo management module needs more time to be perfected. Many users think that there is some important functionality that needs to be patched. They said that it has no manual sort, which means that there is a need to use numeric title and sort by title. There is no mass upload, and mass edit and it is difficult to implement gallery hierarchies. Almost everyone seems to view Drupal as having some weak spot in photo management.
May it be image module, Img Assist, IMCE or CCK + Views + Imagefield + Imagecache, all of them have certainly good features but there is nothing that handles everything perfectly in one shot.
What does the future hold?
There is some good news though. Some users like the direction in which Drupal is headed with CCK and Views. It has the functionality of creating custom content types with custom fields. There is even a tutorial available for setting up a gallery utilizing Views. It also has the added benefit of using the Taxonomy module to categorize the images into libraries.
What Dupra is basically doing is building a good strategy out of the different function pieces that already exists. For example, it uses Taxonomy, which is good in categorizing images, then Views which is good in customizing lists, tables and pages and Imagecache for automatically creating different sizes and versions of the thumbnails.
The future holds so many possibilities for the improvement of Drupal photo management module. Many users think that it is heading in the right direction.
Drupal Settings is defined as a global storage of JavaScript settings that may be needed on the client side. A user needs some modules for his pages to function properly.
There are several guidance and tips provided online on how to have two sites and only one installation of Drupal. The step-by-step instructions assume that the reader has a prior knowledge of Drupal and is using Drupal 4.6.x. The reader must also have two shared sites wherein the primary site is already configured. He must also have a second domain that is directed to his Drupal home directory.
How is this done?
The step-by-step instruction focuses on the settings.php setup. There are several steps to do to set this up in terms of location, creation and editing. Four parts of the Drupal Settings has to be edited which are database name, database prefix array, base url, and the variable overrides.
First, the user needs to create his Drupal site directory for the secondary site. He has to go to the sites directory in Drupal. If the user has not changed the name of the default directory, then he must change that directory to become the domain name of his primary site. After that, he can create the secondary directory.
Second, he can upload the Drupal settings to the secondary site, which can be copied from the primary site, or it can be the default he got with Drupal.
Third, he can set-up the database name and the database prefix array, and the base URL.
Lastly, the user can setup the primary variable overrides. These variables will provide a unique theme to the site, which is the basic requirement to make the same sites look much different.
