1.5 - Submitting form (edit_interface.php) results in page loading error about webtrees HOT 8 CLOSED

edit_interface.php is used for many different types of editing. It appears to work OK on the demo site - http://dev.webtrees.net/demo-stable/

Unless I can see the problem, it is difficult to make suggestions.

from webtrees.

Do you still see this problem?

If yes - which form?

from webtrees.

In WT_Filter::_inputArray the PHP 5.3 shorthand form of the ternary operator ?: is used.

return $tmp[$variable] ?: array();

Although my QNAP NAS is running PHP 5.3.26, it seems to fail to resolve the expression. I dont know why. Inside my Development-VM I run PHP 5.3.8 without throwing any errors. If I replace it with the default syntax, in my eyes also much more easier to read.

return isset($tmp[$variable]) ? $tmp[$variable] : array();

The error went away.

WT_Filter seems to be the only place where the shorthand form of the operator is used (My search founds 6 matches). Maybe those affected lines could be replaced with the normal syntax?

from webtrees.

I don't think the "?:" is the problem (and you don't supply the actual PHP error message).

More likely, $tmp[$variable] is not set (failed validation??), and you are seeing an error for this.

Perhaps $default needs to be array() rather than null ?

from webtrees.

There is actual no PHP error message as the server connection gets lost. Problem still exists after changing $default to an array(). $tmp[$varialbe] is also set. Only changing to the long hand version of the ternary operator resolves the problem.

from webtrees.

Can you create a test for this in isolation? e.g.

<?php echo 1 ?: 2;

from webtrees.

After loading the testpage for the first time the result 1 is displayed. After reloading the page for several times, that the error occurs from time to time (3 success, 1 error and so on).

Seems to be a bug in QNAP php version. But there is currently no way to upgrade to a newer version without compiling it by myself.

from webtrees.

I have finally gained access to a QNAP to investigate this problem...

It appears to be a bug in the eAccelerator module. Disabling this module fixes the problem.

from webtrees.