Hi Dieter
Can I check - do you have the "Easy login" feature enabled?
Regards
John

So what are the other options to try? To summarize: I added in the warehouse the CMS user id block to the survey. I'm logged in on Drupal 7 with the user created with Easy Login feature. I created a record/sighting. The add picture button does not work for the record. It doesn't open the explorer screen (as I noticed before in my other topic)!  Then I check in the warehouse if the record was created. Then I created the 'My records' page, and then it does't give me an output... I can take printscreens if nescessary.

Hi Fiona,

It's not related since I use chrome and the map does show, but just no output. I will take some screenshots to make my case clear.

Dieter

Hi Dieter

I know very little about the My Records page and obviously nothing about your warehouse configuration.
However, if you have copied over settings such as the following, which vary from one warehouse to another, they could very easily cause you problems.

@taxon_list_id=15
@indexedLocationTypeIds=[15,1370]
@otherLocationTypeIds=[2412,2188]

Jim Bacon.

Hi Dieter,

I tried removing these too and I still get records showing. Have you changed the Form Structure in other ways?

Are there any errors in the warehouse log?
If you set the debug level to 4 in the warehouse config files it will log the queries being executed when you visit the My Records page.
Sometimes when you look at the query that is actually running the problem becomes obvious.

Jim Bacon.

I find it helpful when trying to understand a problem like this to copy and paste the query in to the SQL editor of pgAdmin and systematically delete 'wheres' and 'joins' to find out which part of the query is filtering out results.

Jim Bacon.

Hi

If your installation is like mine, in pgAdmin, when you expand the list of schemas there will be one called indicia and, if you expand its list of tables there will be one called cache_occurrences.

If you can see that then you know that the table does exist. Almost certainly the problem is the search path that postgres is using to locate the table.

If you execute the sql command

show search_path

and the indicia schema is not in the list then you need to add it.
You can add it on a per session basis by executing

set search_path = indicia, public;

or you can make that the default by setting it in the postgresql.conf file.

You can always qualify table names with their schema name if you prefer but that soon gets tiresome.

Jim Bacon.

Hi

Great. Now what you can do is run the query again and again, each time with a different bit of the WHERE deleted. Something is filtering out your record and you'll be able to say which part it is.

E.g if you remove the line

AND o.created_by_id=3

and suddenly your record is returned by the query then that tells you that the record was created by a different user from the one requesting the report which would explain why it is not showing up.

Jim Bacon.

Note, it might be a JOIN causing the problem as well, e.g if there were no records in the map_squares table.