GaryT

I can have a look and see if I can at least reproduce. I did get a leaflet based 'version'/option sort-of working, if that would be of interest. It would be hopefully relatively easy (assuming I can remember what I did) to hack it into your system - less so to do a "proper" version that works out of the box. There's issues with bits of google maps specific code in odd places (presumably the refactoring that Tomasz referred to), and potentially a legal/moral issue of having 'googlemaps' hardcoded...

I can have a look and see if I can at least reproduce. I did get a leaflet based 'version'/option sort-of working, if that would be of interest. It would be hopefully relatively easy (assuming I can remember what I did) to hack it into your system - less so to do a "proper" version that works out of the box. There's issues with bits of google maps specific code in odd places (presumably the refactoring that Tomasz referred to), and potentially a legal/moral issue of having 'googlemaps' hardcoded...

Sorry. Yes it is fixed. I thought I had edited my comment after posting it. I'm happy to close this one if you are.

Well I'm listening, and impressed. Whereas I've never been a professional programmer. But I learnt Pascal at school using marksense cards, and went out specially to buy a B5 pencil that would make a readable mark with just one stroke. And I used to run a machine at work that ran on a PDP-8 that had an intermittent core memory fault. That meant that I had to reload the papertape bootstrap routine on the front panel toggle switches fairly regularly. I used to know those 20-odd codes off by heart: 6014,6011,7375......

I just noticed a couple of minor comment typos in class_reportbase.php: 254 /aproxiamte/approximate/ 256 /Stationary/Stationery/ 708 /alignement/alignment/ 715 /carachter/character/ Would it be easier if I learnt to generate a patch file? In terms of the PDOException, I did a bit of googling on the error, and it seems it may be postgresql specific. e.g. https://github.com/querydsl/querydsl/issues/2443 - they just suggest "it can be resolved by adding the order by expression to the select clause"....

I'm still getting the PDOException If it helps, I think the offending query is: SELECT DISTINCT 'INDI' AS type, i_id AS xref, i_file AS ged_id, i_gedcom AS gedrec, i_isdead, i_sex FROM pgv_individuals JOIN pgv_dates AS filter1 ON (filter1.d_file=i_file AND filter1.d_gid=i_id) JOIN pgv_dates AS filter2 ON (filter2.d_file=i_file AND filter2.d_gid=i_id) WHERE i_file=1 AND filter1.d_fact='CHAN' AND filter1.d_julianday2<=2459595 AND filter2.d_fact='CHAN' AND filter2.d_julianday1>=2459565 ORDER BY fil...

I'm still getting the PDOException If it helps, I think the query is: SELECT DISTINCT 'INDI' AS type, i_id AS xref, i_file AS ged_id, i_gedcom AS gedrec, i_isdead, i_sex FROM pgv_individuals JOIN pgv_dates AS filter1 ON (filter1.d_file=i_file AND filter1.d_gid=i_id) JOIN pgv_dates AS filter2 ON (filter2.d_file=i_file AND filter2.d_gid=i_id) WHERE i_file=1 AND filter1.d_fact='CHAN' AND filter1.d_julianday2<=2459595 AND filter2.d_fact='CHAN' AND filter2.d_julianday1>=2459565 ORDER BY filter1.d_jul...

Parse error: syntax error, unexpected variable "$ascii_langs", expecting "," or ";" in V:\phpGedView\includes\classes\class_reportbase.php on line 45 Looks like a missing semicolon on the line above. I added one, and that fixed the error.