Hi Chanaka, could you have a look at this? To reproduce in current master, click on a table name in the navi panel, then click on the SQL menu tab in the main panel:
Call to undefined function backquote() in libraries/Util.class.php on line 3400
Hi,
On Tue, Oct 2, 2012 at 3:28 PM, Marc Delisle marc@infomarc.info wrote:
Hi Chanaka, could you have a look at this? To reproduce in current master, click on a table name in the navi panel, then click on the SQL menu tab in the main panel:
Call to undefined function backquote() in libraries/Util.class.php on line 3400
Sure, I'll check that.
Regards !
Hi Marc,
could you have a look at this? To reproduce in current master, click on
a table name in the navi panel, then click on the SQL menu tab in the main panel:
Call to undefined function backquote() in libraries/Util.class.php on line 3400
I couldn't reproduce the error. How ever I went through the code. Definitely there is a possibility to raise an error at that code line.
There are two different types of $escape variable all over the php files in application. Since function type variable has only used inside Util.class.php file, replacing $escape($parama) with self::$escape($param) should fix the error.(there are two places to replace and I couldn't verify since I cannot reproduce the error). Can you verify the steps to reproduce are correct ?
Le 2012-10-02 21:51, Chanaka Dharmarathna a écrit :
Hi Marc,
could you have a look at this? To reproduce in current master, click on
a table name in the navi panel, then click on the SQL menu tab in the main panel:
Call to undefined function backquote() in libraries/Util.class.php on line 3400
I couldn't reproduce the error. How ever I went through the code. Definitely there is a possibility to raise an error at that code line.
There are two different types of $escape variable all over the php files in application. Since function type variable has only used inside Util.class.php file, replacing $escape($parama) with self::$escape($param) should fix the error.(there are two places to replace and I couldn't verify since I cannot reproduce the error). Can you verify the steps to reproduce are correct ?
Yes, the steps are correct; I am running PHP 5.3.15.
Fix confirmed and pushed, thanks.
-
Chanaka Dharmarathna -
Marc Delisle