SQL error when accessing preferred individual (#1)

[torefahlstrom]

Created a tree and inserted records from a .ged-file. After that, added and updated records manually. At some point in time, i tried to access the preferred individual (me, record nr 1) and got the following error:
#0 /app/Statement.php:82 PDOException("SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ''223')' at line 1")
#1 /app/Individual.php:64 execute()
#2 /app/Family.php:45 load()
#3 /app/GedcomRecord.php:205 __construct()
#4 /app/Fact.php:97 getInstance()
#5 /app/Controller/GedcomRecordController.php:48 getTarget()
#6 /app/Controller/IndividualController.php:61 __construct()
#7 /individual.php:31 __construct()

I am running webtrees 1.7.1. and php 5.5.x. I have been using older versions of webtrees (1.6.2) without seeing this type of error before.

[fisharebest]

This particular function is new for 1.7

It loads all members of a family in one SQL query to improve performance.

The query is very simple, and I cannot see any obvious errors.

Can you add some debug to see what is happening.

app/Individual.php, line ~58:

        if (count($args) > 1) {
            $rows = Database::prepare(

Change to

        if (count($args) > 1) {
            var_dump($sql, $args);
            $rows = Database::prepare(

You should now see debug info on the individual page.

[ghost]

That var_dump gives me:

string(12) ",:x1,:x2,:x3" 
array(4) { 
   ["tree_id"]=> int(1) 
   ["x1"]=> string(2) "16" 
   ["x2"]=> string(1) "3" 
   ["x3"]=> string(1) "4" 
}

[fisharebest]

Can you add one more line of debug

        var_dump($xrefs);
        foreach (array_unique($xrefs) as $n => $xref) {

[ghost]

That gives:

array(4) {
   [0]=> string(1) "1" 
   [1]=> string(2) "16"
   [2]=> string(1) "3" 
   [3]=> string(1) "4" 
}

[fisharebest]

Thanks. I see the problem now..

[torefahlstrom]

Unfortunately i was on a trip and was not able to help. However, i can confirm that the fix resolved the issue that i had.