[The latest version of the readme.txt file is always available under here]
BASIC INFORMATION
AgriDrupal demo package 7.x.7.9
Disclaimer.
Please be reminded that what we call "AgriDrupal demo package" is not a tool that we officially distribute or maintain: it is only a demo Drupal setup packaged with the features that we find useful for agricultural information management.
The versions available for download come with no guarantee, are not maintained and are to be considered test versions for circulation in the AgriDrupal community and for testign and adoption only by users who know Drupal and can use and customize AgriDrupal with no assistance.
THIS PACKAGE WILL BE SOON AVAILABLE AS A DRUPAL DISTRIBUTION PROFILE.
NB: This version is "FEATURES-ENABLED", which means that any improvements we will add to the AgriDrupal tool will be released as "Features" so that they can be integrated in any Drupal installation by just downloading the corresponding "Feature" (click here to read more about features:http://drupal.org/project/features) and installing it in your (Agri)Drupal: no need anymore to re-install the whole AgriDrupal package.
Contact: agridrupal@gmail.com
More information here:
http://aims.fao.org/community/oekcs-community/forums/agridrupal-tool-customization-roadmap,
here:
http://aims.fao.org/community/group/agridrupal
and here:
http://www.agridrupal.org
And on Drupal: www.drupal.org
SYSTEM REQUIREMENTS:
(Read the Drupal documentation on requirements: this version of AgriDrupal is built on Drupal version 7.14.)
-------------------
1) Machine and OS:
- Minimum 2GB of RAM
- OS: UNIX/Linux, OS X, or Windows. Best option: Linux.
-------------------
2) Web server:
Apache 2.x. Tested on Apache 2.0.
Settings:
- Apache 'mod_rewrite' extension enabled:
in httpd.conf: uncomment:
LoadModule rewrite_module modules/mod_rewrite.so
- AllowOverride: not None - for the (virtual) directory where the app is installed
- PHP version: 5.2.6 or later (tested on 5.2.9, but Drupal 7 is compatible also with PHP 5.3)
- Read/write permissions on httpd.conf and php.ini file
PHP settings:
- Preferably installed as an Apache module
- MySql extension, XML extension
- SOAP extansion (./configure --with-soap) (--enable-soap); or in php.ini: uncomment:
extension=php_soap.dll
- register_globals: off
- error_reporting: E_ALL & ~E_NOTICE
- safe_mode: off
- session.cache_limiter: nocache
- max_execution_time: 90
- memory_limit: 127MB
Also the LAMPP environment Xampp can be used:
AgriDrupal has been tested with Xampp version 1.6.8
Xampp for Linux 1.6.8a:
http://sourceforge.net/projects/xampp/files/XAMPP%20Linux/1.6.8a/xampp-linux-1.6.8a.tar.gz/download
-------------------
3) Database
MySql 5.0 or later (tested with 5.0)
Settings:
- Necessary permissions: SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES
- InnoDB tables, UTF-8 encoding
- max_allowed_packet: at least 16M
QUICK INSTALLATION INSTRUCTIONS
This folder contains: {xxx indicates the version, e.g. 078 for version 0.7.8)
- a .zip file called agridrupalxxx, which is the root folder of the Drupal website (for installation on a web server, see below)
- an .sql file with the database dump (for installation on a web server, see below)
- an AgriDrupal-training PDF file for basic guidance
INSTALLATION ON A WEB SERVER
1) Unzip the agridrupalxxx.zip file to your web server (e.g. Apache) docs root and import the .sql into a newly created Mysql database (important: you have to create the database beforehand and then import the .sql file into it).
2) Edit the settings.php file under agridrupalxxx/sites/default and modify the database connection string using your Mysql server abd database configuration:
The variable identifying your database connection is $db_url.
3) Open the config.php file
under:
/sites/all/modules/fckeditor/fckeditor/editor/filemanager/connectors/php
Look for the following 2 lines:
// Path to user files relative to the document root.
$Config['UserFilesPath'] = '/agridrupalxxx/sites/default/files/';
and make sure that the path is actually relative to the documents root.
If you keep the original agridrupalxxx folder name this path should be correct.
4) Open the settings.php file under /sites/default and look for the following lines:
$base_url = "xxx";
change it to the base url of your website (examples: http://www.example.org or http://www.example.org/drupal)
$cookie_domain = 'xxx';
change the value to the IP or domain name of your server: e.g.
$cookie_domain = 'example.com';
(if run locally, localhost should work)
Without doing this, image uploads in the rich editor may not work.
5) Ensure that the following folders have 777 access permissions:
/sites/deafult/files (and contained files)
/sites/deafult/files/tmp
/sites/deafult/files/ctools
/sites/deafult/files/parser_common_syndication_cache
6) If using version 078 or later and if your relative path is not /agridrupalxxx/ (where xxx corresponds to the version you're using),
once logged in go to Admin > Site configuration > Performance, click on the "Boost htaccess rules generation" tab,
tick the two checkboxes and click on Save configuration.
7) Once the website is set up and working, these accounts can be used;
Administrator role:
(the administrator account on this installation is not public)
Editor role:
editor
editor-agridrupal
Basic registered user:
user
agridrupal-user
8) Important:
After installing AgriDrupal on your server, remember to immediately edit the administrator account (login as administrator, go to My account and change the contact email and the password), to edit the website email address (at Administer --> Site configuration --> Site information) and to edit the contact form email (at Administer --> Site building --> Contact form)
Also check that the OAI-PMH configuration is correct and adjust it to your needs: [website-root]/admin/settings/oai2forcck.
IMPORTANT NOTES ON DEPENDENCIES, PATCHES AND HARD-CODED PATHS
1) The conditional_field module is patched in order to allow to use a Content Taxonomy Field to be used as a controlling field.
If you upgrade to a later version or upload the original version, you have to patch it again as indicated here:http://aims.fao.org/community/agridrupal/forums/patch-use-taxonomy-field-conditional-field
2) Before adding new terms to the "document type" taxonomy it is necessary to check the requirements (e.g. mandatory fields and conditional fields) for this document type and adjust the content type accordingly (document type is a controlling field for many conditional fields). Above all, if resources that have been classified under a certain document type have to be classified under the new document type, it is essential to make sure that the two document types have the same requirements (e.g. mandatory fields and conditional fields), otherwise it may be impossible to edit resources that are moved to the new document type.
In general, unless you know how to adjust the content type requirements and its “conditional fields”, it is advisable not to add new terms to the document type taxonomy and not to change the “document type” field of resources.
3) After transferring the website from one server/domain to another:
- Check that the multigroup module (sub-module of CCK) is correctly copied under CCK
- Check the absolute path for the Agrovoc popup selectTerms.php in the help text of the "Agrovoc keywords" field in the resource/document content type.
4) If you adopt a new theme, beside reactivating all modules under the new theme, remember to copy the views-views-xml-style-raw.tpl.php file that is under the agricms theme into the new theme folder.
