Hi Alan

Rather than look too deeply in to this, my recommendation is that you first upgrade your warehouse by downloading the code from branch 0.8.2 of the repository.

Development is galloping away ahead of the release cycle. Instant Indicia 0.8.2 came out recently to allow new features to be used but they may be dependent on changes to the warehouse since 0.8.1 was released.

Jim Bacon

Mmm - just overwrote my warehouse installation with 0.8.2 from repository. I don't see the notification or the button to upgrade the database.

Spot-on Jim. I corrected the version number and the upgrade prompt and button appeared.

However, the upgrade failed:

Ah, thanks Jim.  I've been meaning to ask about cache_builder.

So:

I moved 201301101936_cache_taxon_searchterms_taxon_list_index.sql as you suggested and ran upgrade again and all went fine.

I then enabled cache_builder in config.php and ran the upgrade again. Also fine. (I noted in pgAdminIII that the cache tables were built).

Then reading in the documentation that I needed to run scheduled_tasks to populate the cache tables, I did so. Most of the table updates proceeded OK, but there was one error:

Cheers

Alan

Hi Jim

Thanks very much for that. No need to apologise for inconvenience - it's  all a learning experience.

Cheers

Alan

That is good, but all a preamble to addressing the original problem. How now?

Jim Bacon.

Right then, back to the begining. But we are now in the happy position that I should be able to replicate your problems as we are now running similar systems.

First of all, the missing form, reports_for_prebuilt_forms/dynamic_sample_occurrence_samples. This hasn't been removed but is absent from your system as it and the the Sample With Occurrence form were part of the development trunk and would have come together in a 0.9.0 release. This thing called Instant Indicia 0.8.2 might also be called a beta release of 0.9.0. Perhaps I better copy that report in to the 0.8.2 branch of the warehouse so that  there is compatibility between these two things labelled 0.8.2.

You did download this report but say there is an SQL error in it. I would hazard a guess that this relates to identifying the user for whom the report should list records as this is the only complicated bit of the thing. If there is no helpful error message I would be setting the warehouse log level to debug and looking to see what query is being attempted and what parameters it has been supplied with.

With regard to the edit link not working, this is a consequence of a bug introduced in r5205 and fixed a couple of days later in r5234. If you patch data_entry_helper.php you will make some headway although I am seeing another problem on my test system.

Jim Bacon

Hi Alan

The SQL error is a bit further down in the  ( > 0 AND s.created_by_id = ) filter. This is caused by a bug that is already fixed in the trunk.

To patch your copy of client_helpers/prebuilt_forms/dynamic_sample_occurrence.php (probably in sites/all/libraries/iform) locate the function getSampleListGrid and, around line 1296, change

if (isset($iUserId)) $filter = array (

to

if ($iUserId !== false) $filter = array (

I think that should do the trick although I confess to answering your question by inspection without actually trying it.

Also, I hope you understood from my last email that you need to modify your data_entry_helper.php by copying the changes made in r5234 which is done most easily by looking at the diff. You need to ammend your code with the green higlighted changes in the right hand listing in the region of line 4000.

Jim Bacon.

Hi Alan

Just a quick thought. You probably have the client helpers installed in two places, one copy with your warehouse and one copy with your Instant Indicia. You are making the changes in the Instant Indicia copy aren't you? And also, in Drupal, the client_helpers could be in sites/all/modules/iform or sites/all/libraries/iform. Can you just check they only exist in the one place.

I was just going to paste what your patched getSampleListGrid function should look like and spotted another bug, also already fixed in the trunk. So what I am going to do is paste in the relevant bit of code from the trunk.

    // Get the CMS User ID attribute so we can filter the grid to this user
    foreach($attributes as $attrId => $attr) {
      if (strcasecmp($attr['caption'],'CMS User ID')==0) {
        $filter = array (
          'survey_id' => $args['survey_id'],
          'userID_attr_id' => $attr['attributeId'],
          'userID' => $user->uid,
          'iUserID' => 0);
        break;
      }
    }
    // Alternatively get the Indicia User ID and use that instead
    if (function_exists('hostsite_get_user_field')) {
      $iUserId = hostsite_get_user_field('indicia_user_id');
      if (isset($iUserId) && $iUserId!=false) $filter = array (
          'survey_id'=>$args['survey_id'],
          'userID_attr_id' => 0,
          'userID' => 0,
          'iUserID' => $iUserId);
    }

I hope it is clear to you the lines that need replacing with the above.

What this code is doing is finding the parameters to pass to the report. The first half gets the parameters that are relevant if you identify the recorder by saving their CMS User ID as a sample attribute, the second half is the alternative if you are using the EasyLogin module (which I assume you have not enabled).

Jim Bacon.

Ah! We seem to be OK. I've just tried logging out and then back in again and now the grid display appears. Even better - clicking on the Edit links does now take me to the previously entered record.

Phew!

Thanks very much once again Jim.

Alan

Hi Alan

Do your edit links point to the same form that you have used for the original data entry?

That is the way I have always used it so that it loads with the entered data, both sample and occurrences. It won't create new occurrences unless I add them in the form.

Adding an edit link from the "record details" page should not be hard - just needs a little PHP to concatenate the url of your data entry form with a query string that contains the occurrence_id which can be got from $_GET["occurrence_id"]. Just a question of whether you where to put that bit of code.

The programmers way would be to create a new prebuilt form that subclasses the one you currently use. A less daunting approach might be to enable the PHP input filter in Drupal and put the code in the "Page Introductory Text".

Jim.

Hi Alan

Are you using the "sample with occurrences form"?
What did you select as the method for entering species, single occurrence or multiple occurrences using a checklist?

Jim.