Thanks for the suggestion! I understand that sc_select_where(add) can dynamically insert the WHERE condition at runtime. I’ll try this workaround to bypass Scriptcase’s issue with global variable prompts not appearing after the first run.
Still, this shouldn’t be necessary — global variable handling worked fine before the update. But I’ll test it and get back with results.
"Still, this shouldn’t be necessary " . you are right but i think the major goal is to have the application run fine. Also you could try to place in scripipinit something like: [glob_var]=[glob_var];
Sometimes you work around the problem. [glob_var]=[glob_var] is sometimes a solution. Sometimes globals get lost in situations where you need a blank to fix the issue. I have a similar issue open for quite some time where a global in an application link is passed, but not picked up by the linked application. Looks pretty similar to this problem. But if you use a blank, you will notice that the variable is sent.
The update version 9.12.007 (15) came out, where it says that there is an arrangement of global variables, I updated but I still have the same problem. The same error.
the same problem i have too , and i already write a ticket
Hello SC colleagues, has anyone been able to correct the problem with global variables? Two updates have been released and the problem has not been resolved.
I’m having serious SC globals issues as well.
Just installed version 9.12.009 hoping to fix them, but nada.
SC Team: What’s up with this issue? It’s been a long time, and I see nothing has been resolved.
not 100% sure yet, but i just disabled the notification module in the responsive menu app and it seems that session vars in all other apps are stable now.
it seems rather odd.
maybe any change\regeneration of the menu app would have had the same result.
i have no time to do any more test now; since the notification module was on but not actually used, I’ll leave it off for now.
Hi everyone,
In the latest versions, as well as the one released today (9.12.010), we have released fixes related to global variables.
Please update your environments if you are not yet on the latest version.
If the problem persists, contact the tool’s support via chat or ticket so that the team can investigate further what may be happening, as these are very isolated cases.
Best regards!
Dear all, if anyone who updated to the latest version, 9.12.010, commented, did the problem get resolved? I’m on a hosting account, and it’s harder to do so. I had to downgrade to version 9.12.004. It didn’t work at all, and the main problem was the variables that stopped passing data, displaying a false connection error. Please comment. Regards.
If anyone is in the same situation as i was, i.e. responsive menu with notification module, testing if just disabling the notification module fix the issue (see my previous post) should be less risky than upgrading SC.
Since I disabled the notification module I have no var issues.
Has anyone updated to version 9.12.010 and tested whether the problem with global variables that were giving a false connection error or general problems was actually solved?
Dear Scriptcase Support,
I don’t think it is normal — or even remotely acceptable — that for three months now I haven’t been able to work properly with Scriptcase, despite having paid for a full lifetime license.
Ever since version 12.0.004, when everything was working well, you released an update that completely broke global variable handling. And since then, I have been constantly told that “it will be fixed” or “we are working on it,” but the truth is: nothing has changed.
You’ve already released six updates since I reported this issue, and yet this critical bug is still not fixed.
This is beyond frustrating. I kindly but firmly ask you to treat this message with the utmost seriousness and make this issue a top priority.
I know it’s easy for you — you’re there, and I’m here, just another user. But please understand that I also have responsibilities and clients waiting, and I am completely stuck because of this bug. I don’t even know what to tell my clients anymore.
Once again, I urge you: stop everything else and fix this problem.
Frankly, I don’t understand how this product is even still being sold with such critical bugs unresolved.
You’ve seen it yourself. You’ve tested it. You know it doesn’t work.
So let’s find a solution. Please, I’m asking insistently — solve this issue.
Sincerely,
I also have problems with variables - I doubt they will listen to you - recomandarea mea ar fi sa incepi (treptat) sa treci la laravel - eu deja ma gandesc destul de serios la asta.
Is this solved with the newest release ?
Best regards
Uwe
Hi everyone,
We have released a fix in version 9.12.013 that was released last Monday that is related to this issue with global variables.
Please check if the problem still persists so that we can be aware of it.
Best regards!
There now seems to be a new issue I noticed this week. Im using a button to update a global variable within a grid application and using that to essentially update the SQL for that grid, however when I refresh/reload the application (after the global variable was updated) the grid reloads but still uses the old value of the global in the SQL.