Dear Andrea

If you are using the Occurrence List for a CMS User report you will encounter problems as this report does not contain a field with spatial information. Consider creating your own version of the report which contains the sample.geom field as demonstrated by the Map Occurences for Survey report.

See documentation on the Report Map form and the Report File Format

In addition to this, however, the error you report sounds like one I recall from a long time ago. Are using version 0.7.1 ?

Jim Bacon.

I've checked: we are currently using version 0.7.1 !!!

John, I supposed that your suggestion will not work until we upgrade the version, is it true?

I only hope to avoid data losses in the process of upgrading!

Many thanks,

Andrea

Dear Jim and John,
I put some lines below written by the technicians that will help me in upgrading to the version 0.8.1:

-----------------------------------------------------------------------------------------------------------
Starting from a 0.7.1 in production, we just dowloaded release 0.8.1 into a temporary folder through a svn call. As far as the initial 0.7.1 is involved, only the following 2 files
./application/helpers/spatial_ref.php
./application/config/email.php

were modified after the initial installation.

Can we transform the 0.8.1 distro into the production one, by simply copying all files from the temporary folder and copying back the 2 listed and modified files above ?
Are any other actions against the postgres database or the config files needed ?
-----------------------------------------------------------------------------------------------------

Thank you for your help,

Andrea

Thank you very much, Jim. We followed your instructions, but there's something wrong.
As I did last time, I paste below the message of the person who is working on the server:

After I downloaded and installed release 0.8.1, I needed to

    mk /tmp/images
    transfer all files from the old /upload directory to the new one

in order to correct trivial errors.

Nevertheless when navigating to our warehouse page I expected to find something allowing the upgrade database mechanism, but I only found an error message saying "Unable to Complete Request - You can go to the home page or try again".The same thing happens when I try subpages such as index.php/home/upgrade

Any ideas ?

Our site is temporarily out of order, since we are waiting for an answer to my last message in this post. Anyone could be so kind to give us a suggestion on this topic?

Many thanks!

Andrea

Hi all.

We tried to merge our distro with 0.8.1, always obtaining problems. I'd
like to ask for your competent opinion, examining every single step of
ours; surely we made mistakes.

I'd have a question about the svn command.

What is the exact command we have to execute in order to download release
0.8.1 ?

At first we tried *svn checkout
http://indicia.googlecode.com/svn/core/trunk/ indicia-read-only* , yet such
command downloaded the last unstable release, maybe the 0.8.2, something
more than the desired and stable 0.8.1, with no chance to go backward to
0.8.1 .

Then we tried *svn checkout
http://indicia.googlecode.com/svn/core/ … a-branches
* . We do not know svn well, so our aim is to consider the subdirectory
0.8.1 inside the tree of files and directories and to copy it into the
production subtree.

The execution of the latter svn invocation ended with some warnings.
Is the mechanism above correct in order to get 0.8.1 release or do better
and correct ways exist ? What is the meaning of the following errors that
happened at the end of the svn command ?
*
svn: warning: Error handling externals definition for
'indicia-branches/version 0.8.0/modules/phpUnit':
svn: warning: OPTIONS of '
http://source.kohanaframework.org/svn/phpunit/trunk': 200 OK (
http://source.kohanaframework.org)
svn: warning: Error handling externals definition for
'indicia-branches/version 0.6.2/modules/phpUnit':
svn: warning: OPTIONS of '
http://source.kohanaframework.org/svn/phpunit/trunk': 200 OK (
http://source.kohanaframework.org)
svn: warning: Error handling externals definition for
'indicia-branches/version 0.8.1/modules/phpUnit':
svn: warning: OPTIONS of '
http://source.kohanaframework.org/svn/phpunit/trunk': 200 OK (
http://source.kohanaframework.org)
Checked out revision 4717.

Hi all,
just to let you know that the upgrade went well. Thank you Jim your kind
and useful answers.

Yes, there are some warning errors after the lauch of the svn command, but I
thin the actual diffference was due to a different command used to copy the
new distro onto the old one.

Practically, I hope I will be useful for all future Linux users, the cp -a
<new distro directory>/* <old distro directory> was the real solution for
the problem, while a double tar (--create at first and --extract later)
provoked errors.

Best Regards

Dear Jim,
we have been successful with the upgrade, but apparently we are still far from the solution of the original question:
following John's instructions, a "map explorer" choice should appear under the following menu:
Select Form Category: Reporting
Select Form: Map Explorer
Unfortunately, the menu does not show this choice, being the same shown with the previous version of Indicia.

Any suggestion?

Andrea

Some (not very encouraging) updates:
- we performed the upgrading;
- the system created a copy of users in the warehouse dbase, but only for a couple of users recently registered through the internet site;
- the number of users in the warehouse [lookuplist/people] is significantly smaller (about half) in comparison of that of the internet site [in Drupal: user management/users/list];
- after login, the data visualisable are those recorded by another user;
- in practice, the number ID of the warehouse is associated to a different user in comparison to that associated to the same number by the CMS;
- if a new user register himself, the system does associate to him the data already present in the dbase, previously recorded by a different user.

This "disallineation" caused, as you can imagine, heavy problems and we have to decide how to go ahead. Upgrading to 0.8.1 has to be done, but we are wondering if this (and expecially the easy login feature installation) had to be done in a system with an empty dbase!

I beg you pardon for a not-specific language, but I hope you understood our problem.
As usual, any hel is wellcome!

Andrea