Abhishek Reddy — Sun, 19 Nov 2006 01:08:25 +0000

To avoid namespace clashes, prefix your global variables with an uncommon string. You might rename your [incode]$sql[/incode] to [incode]$triexa_sql[/incode], for example. [incode]$sql1[/incode] isn't meaningful and might cause problems later.

To ensure variables are in the global namespace, refer to them by [incode]$GLOBALS['var'][/incode], even when assigning. If you still can't see the variable from elsewhere, it's possible you're looking for it before it has been created. Check the order of execution, you might be able to fix it by promoting a call to require or something.

Triexa.com — Sat, 18 Nov 2006 22:39:35 +0000

DDoSAttack;210714 wrote: For the $sql problem I would just use something different like $sql1 or something. It is easier to alter your code then it is to alter their code.

If it is not in $GLOBALS then it is not in the scope. Is your variable that you are trying to find inside of a function or a class?

Nope - its just in an init.php page called from header.

Works for my entire site, but not when it is called from within the header.php template in wordpress. My best guess is that it is wrapped in a function/class/something, but surely there is some way to "get around" this?

DDoSAttack — Sat, 18 Nov 2006 20:49:38 +0000

For the $sql problem I would just use something different like $sql1 or something. It is easier to alter your code then it is to alter their code.

If it is not in $GLOBALS then it is not in the scope. Is your variable that you are trying to find inside of a function or a class?