In the past if you used a variable in mivascript and did not scope it, empresa would first look for the global with that name, then continue through database scope and finally local scope. Scoping is good thing as the engine does not have to go through a heirarchy to find the variable. Occasionally, I miss that scope. Everything works fine on the server my test store is on when the scope is omitted. However, I just came across a case which behaved differently. The variable without the scope came up blank even though their was a global version of that variable.
Is it a bug in the empresa version that allow the non-scoped variable or is it a bug in the empresa that failed to go through the heirarchy?
Is it a bug in the empresa version that allow the non-scoped variable or is it a bug in the empresa that failed to go through the heirarchy?
Comment