diff options
Diffstat (limited to 'docs/_build/html/_sources')
| -rw-r--r-- | docs/_build/html/_sources/administration.txt | 104 | ||||
| -rw-r--r-- | docs/_build/html/_sources/configuration.txt | 4 | ||||
| -rw-r--r-- | docs/_build/html/_sources/customisation.txt | 4 | ||||
| -rw-r--r-- | docs/_build/html/_sources/import_export.txt | 72 | ||||
| -rw-r--r-- | docs/_build/html/_sources/install.txt | 77 | ||||
| -rw-r--r-- | docs/_build/html/_sources/upgrade.txt | 18 |
6 files changed, 149 insertions, 130 deletions
diff --git a/docs/_build/html/_sources/administration.txt b/docs/_build/html/_sources/administration.txt index fa95012..92b6442 100644 --- a/docs/_build/html/_sources/administration.txt +++ b/docs/_build/html/_sources/administration.txt @@ -10,7 +10,7 @@ Administration :Copyright: CC-BY 3.0 This document presents the administration of Chimère. -It has has been updated for version 2.0.0. +It has been updated for version 2.0.0. Administration pages presentation @@ -34,18 +34,18 @@ Main page Once authentified you'll have access to the main admin page. -This looks like this: +It looks like this: .. image:: _static/chimere_admin_01.png #. links to this **Documentation**, to the **Change password** form and to - **Log out** -#. a list of recent actions made with this account + **Log out**, +#. the list of recent actions made with this account, #. an application title, most of your action will be in the **Chimere** - application -#. an item inside the application. From these page you can **Add** a new item or - consult/**Change** items. The **Add** link lead to the new `Item form`_. The - **Change** link lead to the `Item list`_. The `Item list`_ is also available + application, +#. an item inside the application. From these pages you can **Add** a new item or + consult/**Change** items. The **Add** link leads to the new `Item form`_. The + **Change** link leads to the `Item list`_. The `Item list`_ is also available by clicking on the item label. @@ -55,16 +55,16 @@ Item list .. image:: _static/chimere_admin_02.png #. path in the admin site. This is a convenient shortcut to come back to the - main page. -#. link to create a new item from the item list -#. search items by word (not available for all type of items) -#. this filter box permit to filter current entries with some criteria (not - available for all type of items) -#. the header of the table is cliquable. Click on an header sort the items by + main page, +#. link to create a new item from the item list, +#. search items by words (not available for all item types), +#. this filter box permits to filter current entries with some criteria (not + available for all type of items), +#. the header of the table is clickable. Clicking on an header sorts the items by this header (ascending or descending). Multiple header sort is possible (the - number on the right of the header explain the order of sorting). + number on the right of the header explains the sorting order), #. each item can be checked (for applying an action) or selected (by clicking on - the first column) to see the detail and possibly edit, delete it. + the first column) to see the detail and edit or delete it. Item form ********* @@ -72,13 +72,13 @@ Item form .. image:: _static/chimere_admin_03.png #. fields for the selected item (or blank if it is a new item) are displayed in - this form. A few of the fields concerning an item are read-only and a few of - them are hidden. Mandatory fields have their label in bold. Changes on theses - fields are only effective once the form is submitted. -#. for some items there are associated sub-items. Theses associated items can be + this form. A few fields are read-only and another few are hidden. Mandatory + fields have their label in bold. Changes on these fields are only effective + once the form is submitted. +#. for some items there are associated sub-items. These associated items can be modified in this form. If there are many sub-items associated for the current item, they can be ordered by drag and drop. -#. the form has to be validated by one of theses actions buttons. They are +#. the form has to be validated by one of these action buttons. They are self-explanatory. Status @@ -87,7 +87,7 @@ Status *Status* is a property attached to each geographic item in Chimère. To administrate efficiently Chimère you need to understand the mean of each status. -- **Submited**: Status of a new item freshly proposed by an end user. This item +- **Submitted**: Status of a new item freshly proposed by an end user. This item is not visible on the map. - **Available**: Status of an item visible on the map. - **Disabled**: Status of a discarded item. @@ -102,14 +102,14 @@ Managing news A news system is available. All you have to to do is to click on the **Add** button near News. -For each news you have to provided a name and a content. The content can contain +For each news you have to provide a name and a content. The content can contain HTML tags. The availability is set with a checkbox. Creating categories/subcategories --------------------------------- -Before adding categories you have to set some icons. Theses icons appears on the +Before adding categories you have to set some icons. These icons appear on the map and in the categories' box on the main map. Be careful to resize correctly your icons. Indeed the icon will be presented at their real size on the map. @@ -122,17 +122,17 @@ it?) Fields of subcategories are: an associated category, a name, an icon, an order, a color and an element type. -Theses fields are mainly quite self- explanatory. +These fields are mainly quite self- explanatory. The color is used to draw routes (if this subcategory contains routes). If it a basic color it can be set with the English name (for instance: *red*, *blue*, *yellow* or *purple*) otherwise you can put the HTML RVB code (for instance *#9227c9*). -The element type is the type of element the subcategory can contain: POI, route +The element type is the type of element that the subcategory can contain: POI, route or both. .. _geographic-items-management: -Edition/moderation of items +Editing or moderating items --------------------------- The moderation step is quite simple. It works the same with POIs and routes. @@ -142,35 +142,40 @@ list. A search field is available to search by name but the more interesting is to filter POIs (or route) by state and by subcategory. -There is a some actions available in the action list. +There are some actions available in the action list: -- **Delete** to delete selected items. A confirmation step is displayed. -- **Validate** to set the status *Available* to selected items. -- **Disable** to set teh status *Disabled* to selected items. This is useful to - keep items you don't want to be exposed on the map. -- **Managed modified items** to manage the amendment made by end users on the - main site cf. to :ref:`managing-modified`. Modified item has to be treated - one by one. -- **Export to...** to export selected item to the selected format. +- **Delete**: to delete selected items. A confirmation step is displayed, +- **Validate**: to set the status *Available* to selected items, +- **Disable**: to set the status *Disabled* to selected items. This is useful to + keep items you don't want to be exposed on the map, +- **Managed modified items**: to manage the amendment made by end users on the + main site (cf. :ref:`managing-modified`). Modified item has to be treated + one by one, +- **Export to...**: to export selected item to the selected format. -To modify an item, classically you have to click on his name. +To modify an item, classically you have to click on its name. Then you access to a form to freely modify the item. -In this form there is all data available to the end user form plus some extra + +.. image:: _static/chimere_admin_modify_item.png + +In this form there are all data available to the end user form plus some extra fields. + - The *Import fields* only make sense with data imported from an external -source or for data to be exported to OSM cf. to the :ref:`import section -<importing>` of this documentation. -- *Associated items fields* are read only fields that list items associated to -the current one (reference item of an amendment, associated file of a route). + source or for data to be exported to OSM (cf. the :ref:`import section + <importing>` of this documentation), +- *Associated items fields* are read-only fields that list items associated to + the current one (for example the reference item of an amendment or an associated + file of a route). Associated multimedia items are at the bottom of the form. You can freely add, change items and change their order with drag and drop. Don't forget to validate your change with one of the **Save** buttons at the -bottom of the form (it is easily forgot when you change multimedia items). +bottom of the form (it is easily forgotten when you change multimedia items). -If an item is not relevant the **Delete** button permit to remove it. +If an item is not relevant the **Delete** button enables to remove it. .. _managing-modified: @@ -183,9 +188,9 @@ to the reference item modified. .. Note:: If you are logged as an administrator and make changes on the map with the - end user form there will be directly validated. + end user form they will be directly validated. -A special form has been developed to facilitate the processing of theses +A special form has been developed to facilitate the processing of these modified items. You can access to this special form with the action *Managed modified items*. @@ -194,10 +199,11 @@ You can access to this special form with the action *Managed modified items*. This form is a table with three columns. -#. The first column display the information for the reference item. -#. The second column display the information proposed by the submitter. +#. The first column displays the information for the reference item, +#. The second column displays the information proposed by the submitter, #. The third column is a list of checkboxes. For each row checked, after the validation, the value of the modified item will replace the value of the reference item. -To reject all modification validate the form with no checkbox checked. +.. Note:: + To reject all modification validate the form with no checkbox checked. diff --git a/docs/_build/html/_sources/configuration.txt b/docs/_build/html/_sources/configuration.txt index 39acdfd..c0cef30 100644 --- a/docs/_build/html/_sources/configuration.txt +++ b/docs/_build/html/_sources/configuration.txt @@ -80,8 +80,8 @@ An *Area* is the base of your map. It defines: *Areas* are customizable directly on the web administration interface in *Chimere > Areas*. -As there is little chance that the default area is appropriate for you, you'll -have to set at least one default area. +As there is little chance that the default area should be appropriated for you, +you'll have to set at least one default area. Adding many area can be a mean to show your map in different flavors. diff --git a/docs/_build/html/_sources/customisation.txt b/docs/_build/html/_sources/customisation.txt index e6615db..665e2f8 100644 --- a/docs/_build/html/_sources/customisation.txt +++ b/docs/_build/html/_sources/customisation.txt @@ -8,7 +8,7 @@ Customisation :date: 2012-11-28 :Copyright: CC-BY 3.0 -This document presents the installation of Chimère. +This document presents the customisation of Chimère. It has been updated for version 2.0.0. @@ -17,7 +17,7 @@ It has been updated for version 2.0.0. Managing layers --------------- -There is some different layers available by default in Chimère (OSM Mapnik, OSM +There are some different layers available by default in Chimère (OSM Mapnik, OSM Mapquest, OSM Transport map, OSM Cyclemap). You can add some extra layer using the web administration pages of Chimère. The new layer is defined with the appropriate `Openlayers <http://openlayers.org/>`_ JS code. This JS code must diff --git a/docs/_build/html/_sources/import_export.txt b/docs/_build/html/_sources/import_export.txt index e8d283b..eb581ce 100644 --- a/docs/_build/html/_sources/import_export.txt +++ b/docs/_build/html/_sources/import_export.txt @@ -16,16 +16,19 @@ It has been updated for version 2.0.0. Importing --------- -In Chimère the import mechanism is based on **Import object**. Theses objects +In Chimère the import mechanism is based on **Import object**. These objects are stored in database to keep trace of imports and to facilitate the re-importation from the same source. In fact if possible the update of data from -a same type of source is managed. The ability to do such updates depends on the -existence of a unique id for each object on your source. +a same type of source is managed. + +.. Note:: + The ability to do such updates depends on the existence of a unique id + for each object on your source. To add an **Import object** you need to go to *Chimere > Imports* then **Add**. After that you'll have to select your source type and then the form depends on -the type of source. +this source type. Common fields ************* @@ -35,7 +38,7 @@ Common fields associated category will be use. - **SRID**: Chimère will try to identify automatically the correct projection from the given source. But sometimes the information is not present or cannot - be guessed (for instance a Shapefile that uses non standard proj file). In + be guessed (for instance a shapefile that uses non standard proj file). In this case Chimère will use WGS84 by default (the classic latitude/longitude) but it is not always correct. If you experience problems with items localisation you should put here the SRID associated to the projection of @@ -60,7 +63,7 @@ KML import file. You'll have to fill one of the two fields. - **Filter**: if you want to import only a specific *Folder* of your KML file put his name on this field. -- **Zipped file**: if your source is a KMLZ file (a zipped KML) check this case. +- **Zipped file**: if your source is a KMLZ file (a zipped KML), check this case. Shapefile import **************** @@ -68,9 +71,9 @@ Shapefile import .. image:: _static/chimere_admin_import_shapefile.png -- **Web address/source file (mandatory)**: your KML could be distant or a local - file. You'll have to fill one of the two fields. -- **Zipped file**: only zipped shapefile are accepted this checkbox have to be +- **Web address/source file (mandatory)**: your shapefile could be distant or a + local file. You'll have to fill one of the two fields. +- **Zipped file**: only zipped shapefiles are accepted so this checkbox has to be checked. GeoRSS import @@ -85,12 +88,17 @@ Simple GeoRSS and W3C GeoRSS are managed. CSV import ********** -As the format of the CSV file managed by Chimère could vary depending on the -property you have add on your Chimère instance we recommend you to first do -an export of some items in CSV with Chimère. The CSV format of the exported -file will meet Chimère requirements. By the way because of the geometry of -the item this format is not very convenient to add new content but could -be handy to update informations. +The format of the CSV file (number and order of columns) managed by Chimère +varies depending on the properties you have added on your Chimère instance. +So we recommend you to first do an export of some items in CSV with Chimère. +The CSV format of the exported file will meet Chimère requirements. + +By the way because of the geometry of the item this format is not very +convenient to add new content but could be handy to update informations. + +.. Warning:: + If you mean to update existing data by this import, do *not* modify the + geometry column. .. image:: _static/chimere_admin_import_CSV.png @@ -104,11 +112,11 @@ OpenStreetMap import .. image:: _static/chimere_admin_import_OSM.png -To import from OSM Chimère uses the XAPI API of OSM. +To import from OSM Chimère use the XAPI API of OSM. - **Web address (mandatory)**: XAPI url used to import data. This field should be filled with a default address. By default the MapQuest server is used as it - seems to be the more robust. If you experience problems with OSM import check + seems to be the more robust. If you experience problems with OSM import, check the availability of the XAPI server used and eventually change it. - **Filter area (mandatory)**: draw the bounding box you want to use for your OSM import. @@ -123,18 +131,18 @@ To import from OSM Chimère uses the XAPI API of OSM. Importing ********* -Once your new import item created. Select it in the import object list, select -the **Import** action and validated. +Once your new import item created, select it in the import object list, choose +the **Import** action and validate. -The import should be processing normally. If not an explicit error message -should be print in the state column of your import. +The import should be processing normally. If not, an explicit error message +should be printed in the state column of your import. Managing imported data ********************** All new imported items have the state **Imported**. To make them available on -the map you'll have to validate them. If you don't want an item to be visible on -the map instead of delete them it is recommended to set them to the state +the map you'll have to validate them. If you don't want some items to be visible on +the map, instead of deleting them it is recommended to set them to the state **Disabled**. .. Warning:: @@ -148,7 +156,7 @@ Export to CSV/KML/Shapefile *************************** Directly from the :ref:`geographic items list <geographic-items-management>` you -can export to the choose format. All you have to do is to select the desired +can export to the chosen format. All you have to do is to select the desired items, choose the appropriate action in the action list and validate. Export to OSM @@ -156,19 +164,19 @@ Export to OSM .. Warning:: If you are not sure of what you are doing with OSM export: don't do it! It is - really important to not mess with others data. + really important to not mess with others' data. .. Note:: Only export of OSM nodes are managed. OSM export is not that easily managed. First (if not yet done) you'll have to -define an import (:ref:`see above <osm-import>` for details). This will permit +define an import (:ref:`see above <osm-import>` for details). This will enable to determine: - the area concerned by your export. - the key/value tag to append to your new/updated items. - the subcategories concerned by your export. If you think that some items in - theses subcategories should not be in OSM database (because there are not + these subcategories should not be in OSM database (because there are not relevant or because of license issues) beforehand mark them as **Not for OSM** in the *import fields* of the :ref:`geographic items forms <geographic-items-management>`. @@ -176,23 +184,23 @@ to determine: The OSM export in Chimère is designed to be the more preservative possible in regards to OSM database. That's why before any export an import is done. If -the new import has updated data theses new data will overload data in your +the new import has updated data, these new data will overload data in your Chimère (if you don't want that: don't do export). All pending imported items should have been treated before doing an export. To launch an export select the appropriate Import object in the imports list. Then select the **Export to OSM** action and validate. Then you'll be asked for your OSM username and password and the API you want to -use. If you use regularly Chimère to do export it is recommended to create an +use. If you regularly use Chimère to do export, it is recommended to create an OSM specific account for that. The test API is available to make export test. If you want to use the test API you'll have to create a specific account on the test platform. .. Warning:: - The data on the test platform are not synced with the main platform you are - not going to have the same data that you got with XAPI. + The data on the test platform are not synced with the main platform. You won't + have the same data than the ones you got with XAPI. -Once all this field filled you can (finally!) launch the export. +Once all this field filled, you can (finally!) launch the export. When exporting tags are automatically added/updated: diff --git a/docs/_build/html/_sources/install.txt b/docs/_build/html/_sources/install.txt index f05e5f0..248ece9 100644 --- a/docs/_build/html/_sources/install.txt +++ b/docs/_build/html/_sources/install.txt @@ -78,7 +78,7 @@ Database configuration ********************** Now that postgres and postgis are installed, you need to create a new user for -chimere:: +Chimère:: su postgres createuser --echo --adduser --createdb --encrypted --pwprompt chimere-user @@ -92,8 +92,8 @@ the paths accordingly to your needs):: psql -d chimere -f /usr/share/postgresql/$PG_VERSION/contrib/postgis-1.5/postgis.sql psql -d chimere -f /usr/share/postgresql/$PG_VERSION/contrib/postgis-1.5/spatial_ref_sys.sql -Install the sources -******************* +Installing the sources +********************** Choose a path to install your Chimère:: @@ -105,8 +105,7 @@ From an archive The last "stable" version is available in this `directory <http://www.peacefrogs.net/download/chimere/>`_. Take care of getting the last version in the desired X.Y branch (for instance -the last version for the 1.0 branch is version 1.0.2. -Extract it to the desired destination path:: +the last version for the 1.0 branch is version 1.0.2).:: wget http://www.peacefrogs.net/download/chimere -q -O -| html2text (...) @@ -127,7 +126,7 @@ readable directory:: From the git repository +++++++++++++++++++++++ -Another solution is to get the last git version:: +Another solution is to get it from the git repository:: cd $INSTALL_PATH git clone git://www.peacefrogs.net/git/chimere @@ -136,26 +135,26 @@ Another solution is to get the last git version:: git checkout v2.0 # checkout the desired version -Create a custom project template -******************************** +Creating a custom project template +********************************** -There a default project is provided (example_project). Copy and modify it (or -get another project based on Chimere):: +There, a default project is provided (*example_project*). Copy and modify +it (or get another project based on Chimère):: cd $INSTALL_PATH/chimere cp -ra example_project mychimere_project Your project name is used for the name of the Python package of your template. As a Python package it should follow the rule of Python variable name: -it must be at least one letter and can have a string of numbers, letters and -underscores ("_") to any length. Don't begin the name by "_" because it has -special significance in Python. +it must contain at least one letter and can have a string of numbers, letters and +underscores ("_") to any length. Don't use accentuated letters. Don't begin the +name by "_" because it has special significance in Python. -In your chimere application directory create local_settings.py to fit to your +In your Chimère application directory create *local_settings.py* to fit to your configuration. -A base template is provided (local_settings.py.example) and short descriptions of -the more relevant fields are given below (at least check them). Most of these -settings are initialized in settings.py. :: +A base template is provided (*local_settings.py.example*) and short descriptions +of the more relevant fields are given below (at least check them). Most of +these settings are initialized in *settings.py*. :: cd $INSTALL_PATH/chimere/mychimere_project cp local_settings.py.sample local_settings.py @@ -167,18 +166,20 @@ settings are initialized in settings.py. :: * PROJECT_NAME: name of the project * SECRET_KEY: a secret key for a particular Django installation. This is used to provide cryptographic signing, and should be set to a unique, - unpredictable value. Change it! + unpredictable value. **Change it!** * ROOT_URLCONF: url configuration for your project something like: 'mychimere_project.urls' * EMAIL_HOST: smtp of an email server to send emails * TINYMCE_URL: url to tinymce path (default is appropriate for a Debian - installation with tinymce activated) - * JQUERY_JS_URLS: list of Jquery and Jquery-ui urls (default is appropriate - for a Debian installation with Jquery and Jquery-ui activated) - * JQUERY_CSS_URLS: list of Jquery and Jquery-ui urls (default is appropriate - for a Debian installation with Jquery and Jquery-ui activated) + installation with tinymce package installed) + * JQUERY_JS_URLS: list of jquery and jquery-ui javascript urls (default is + appropriate for a Debian installation with libjs-jquery libjs-jquery-ui + packages installed) + * JQUERY_CSS_URLS: list of jquery and jquery-ui CSS urls (default is + appropriate for a Debian installation with libjs-jquery libjs-jquery-ui + packages installed) * GPSBABEL: path to gpsbabel (default is appropriate for a Debian - installation with gpsbabel installed) + installation with gpsbabel package installed) * TIME_ZONE: local time zone for this installation * LANGUAGE_CODE: language code for this installation @@ -203,9 +204,9 @@ Regroup static files in one path:: Compiling languages ******************* -If your language is available in the locale directory of chimere, you will just -need to get it compiled. This can be done with (here, **fr** stands for french. -Replace it with the appropriate language code):: +If your language is available in the directory *chimere/locale/*, you will just +need to get it compiled. This can be done with the following command (here, +**fr** stands for French, replace it with the appropriate language code):: cd $INSTALL_PATH/chimere/chimere/ django-admin compilemessages @@ -227,14 +228,14 @@ would have if the language file was already available. Database initialisation *********************** -Create the appropriate tables (still being in chimère application directory):: +Create the appropriate tables (still being in your Chimère project directory):: cd $INSTALL_PATH/chimere/mychimere_project ./manage.py syncdb You will be prompted for the creation of an administrator account -(administration can be found at: http://where_is_chimere/admin). Then you have -to create tables managed with south:: +(administration can be found at: http://where_is_chimere/admin/). Then you have +to create tables managed with Django-South:: ./manage.py migrate @@ -251,23 +252,25 @@ Webserver configuration Apache configuration with mod_wsgi ++++++++++++++++++++++++++++++++++ -Install mod_wsgi for apache:: +Install *mod_wsgi* for Apache:: apt-get install libapache2-mod-wsgi -TODO: adapt apache-wsgi.conf - Create and edit a configuration for Chimère:: - cp $INSTALL_PATH/chimere/apache/django.wsgi $INSTALL_PATH/chimere/apache/mydjango.wsgi + cp $INSTALL_PATH/chimere/apache/django.wsgi \ + $INSTALL_PATH/chimere/apache/mydjango.wsgi vim $INSTALL_PATH/chimere/apache/mydjango.wsgi - cp $INSTALL_PATH/chimere/apache/apache-wsgi.conf /etc/apache2/sites-available/chimere + cp $INSTALL_PATH/chimere/apache/apache-wsgi.conf \ + /etc/apache2/sites-available/chimere vim /etc/apache2/sites-available/chimere # create log dir mkdir /var/log/apache2/chimere/ + chown www-data /var/log/apache2/chimere/ -Adapt the files *mydjango.wsgi* (with the correct sys path) and Apache *chimere*. +Adapt the files *mydjango.wsgi* (with the correct sys path and the correct +module) and Apache *chimere* (with the correct servername and correct paths). To activate the website, reload apache:: @@ -276,7 +279,7 @@ To activate the website, reload apache:: If you encounter problem with the upload of files with Unicode chars in their names, activate the appropriate locale in Apache. On a Debian server with UTF-8 -as default encoding in the file */etc/apache2/envvars*, uncomment the following +as default encoding, in the file */etc/apache2/envvars* uncomment the following line:: . /etc/default/locale diff --git a/docs/_build/html/_sources/upgrade.txt b/docs/_build/html/_sources/upgrade.txt index d7c7233..796ed98 100644 --- a/docs/_build/html/_sources/upgrade.txt +++ b/docs/_build/html/_sources/upgrade.txt @@ -8,6 +8,8 @@ Upgrade :date: 2012-10-08 :Copyright: CC-BY 3.0 +This document presents the upgrade of Chimère. +It has been updated for version 2.0.0. Before any upgrade backup the database and all your installation files (specially if you have made changes to them). @@ -25,8 +27,8 @@ If you are considering to contribute on Chimère get the Git master. The instruction are given for Debian Squeeze and Debian Wheezy. -Get new version of dependencies -------------------------------- +Getting new versions of dependencies +------------------------------------ Version 1.1 -> 1.2 ****************** @@ -62,8 +64,8 @@ If you are planing to do major import consider the install of `Celery apt-get install python-django-celery python-kombu -Get the new sources -------------------- +Getting the new sources +----------------------- First of all we have to get the new version of the source code. For this upgrade process, we are getting the source code from the Git @@ -102,7 +104,7 @@ From a previous Git installation From a previous tarball installation ************************************ -Remove first your old installation and get the Git version. +First remove your old installation and get the Git version. .. code-block:: bash @@ -217,7 +219,7 @@ Version 1.1 -> 1.2 ****************** Migration scripts test your installation before making changes so you probably -won't have any lost but by precaution before running theses scripts don't forget +won't have any lost but by precaution before running these scripts don't forget to backup your database. You can also make a copy of your current database into a new database and make the new installation to this new database. @@ -288,8 +290,8 @@ Version 1.2 -> 2.0 -> master cd $CHIMERE_PATH/chimere django-admin compilemessages -Force the upgrade of visitor's web browser cache ------------------------------------------------- +Forcing the upgrade of visitor's web browser cache +-------------------------------------------------- If major changes in the javascript has be done between version, many of your users could experience problems. There are many tricks to force the refresh |