Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

[peteconway]

Good news..

[frankbicknell]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

Good news indeed.

[mikeallenbrown]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

Did you have to go to each UX and uncheck the detailed JS reporting or was it already unchecked?? ...I'm considering trying the prerelease because these popups are driving people crazy.

[mikeallenbrown]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

I continue to get pop-up errors ...

Ashampoo_Snap_Friday, August 18, 2017_12h36m21s_001_.png

That's a screenshot from the console. You can see right there that Alpha has an alert in the handler they coded in.

Sending in a bug report soon.

[iRadiate]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

I'm still getting annoying popups like this

Error.jpg

I can't track this down even though I have turned off the detailed JS reporting (which seems to be enabled in all my components by default).
If you submit a bugrep, perhaps you could mention that the "detail JS reporting" in NOT turned off by default for UX components?

[mikeallenbrown]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

Stephen, if you haven't already recalculate controls at the component level. The bulk recalculating of controls doesn't recalculate things the same as doing it at the component level (confirmed by Jerry at Alpha). Bulk recalculating doesn't recalculate the prerendered portion of the UX.

As for the popups I found the source of the problem (for me anyways...): I utilize the destroyChildComponent method in my app and when I comment it out all of my JS woes go away. Something in Alpha was referencing the previous component but since it was destroyed that code bombed.

[iRadiate]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

Yes thanks Mike, I already have recalculated controls at the UX level. It didn't help in my case.

Jerry mentioned to me that closing a tab does not destroy the grid object, it just hides it. He had me put a try/catch around a problematic js code piece which worked for that case.
I'm not using the destroyChildComponent method, at least I don't remember using it but I'll take a look at it anyways.

[peteconway]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

Hmm.. i'll just keep my fingers crossed I keep on the lucky of all this... for now.

[iRadiate]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

Man, this has got to be one of the most frustrating updates in recent memory!!!

I now have one component giving me this js error:

js Error.jpg

Looking in Firebug, I get this:

Firebug 1.jpg Firebug 2.jpg

I have turned off the "Capture detailed Javascript error information" property in both the parent and child components but that didn't help.

Any ideas anyone? I am starting to get really pissed with the amount of time wasted on this

[peteconway]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

I can't help on that issue - I have some serious pain going on now as well, it is a wonder how that Official Release could still be in play.

[[email protected]]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

I`m facing the same problem about this annoying alerts. Did not get this kind of errors until I started to use the releases (official and also pre released) after the release of Alphaanywhere version 4.4.4 build 4346_4889.
So I refer this things to Alpha and Selwyn replied me as below

"The error shown in the image below looks like an old bug that was fixed some time ago.
There was a bug in the product for a short time that occurred when a radio button or checkbox control had some Javascript defined for the onChange event.

if you edit and resave the javascript for the onChange event that should fix the problem.

if that does not fix the problem, try deleting the radio button or checkbox control and then adding it back in.

if that still does not fix the problem, then please send a test case."

I do as what he ask me to do.I recreate a new control but I still cant get pass the alert (especially with the alert that have something said about the onchange event). It still there. I already send a test case to him and now I`m waiting for them to response.I though I`m the only one facing this alert. I guess I`m not alone.Hope they can fix this thing soon

jserror.PNG

[peteconway]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

Lets know how you go. You can rest assured its not you. That said, the features in the release (and speed) are really something else, very powerful, so once we get past this should be all good.

[iRadiate]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

I think I finally have all these javascript errors squashed in my application.

The last "document.getElementById() is null" error turned out to be some code in my client-side afterValidate event:

document.getElementById('TBI_LOA_FORM_85855PPMG.V.R1.BUTTON_SUBMIT').disabled=false;
document.getElementById('TBI_LOA_FORM_85855PPMG.V.R1.BUTTON_RESET').disabled=false;

As soon as I commented it out, the errors went away. Many thanks to Jerry at Alpha for the help tracking these down!

[Davidk]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

I've been following this thread from the start and I keep thinking the same thing. It's not Alpha causing Javascript errors. Alpha is tightening up it's code... and adding the ability to show errors... but ultimately what you're seeing are your own errors. They may not have been displayed in an alert before... but they were there. Very few people in this forum check their browser's console for errors... but that's where you'll see them. Some will be benign, some will stop app execution... but they'll all be in the console.

Now they're more in your face... and they should be. There's no reason why these user created errors should exist in your application... you can fix them. So many times I run into errors in other's code that have been there for some time... and ignored... "we'll get to it later" thinking. But if you check your code as you progress through your app, and fix the errors, then threads like this won't seem so mis-leading.

[iRadiate]

Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

David,

You are absolutely correct in your thinking.

According to Alpha, prior to build 4346-4889, many errors in user code were just written to the browser console log, which is normally only seen when using developer tools.
Starting in that build, there was code added to show an alertbox() with the errors. Later builds added a more verbose message in the alertbox, but then the developer was given the option to turn off the verbose message. However, that did not turn off the first alertbox().

Alpha is examining the code and will probably turn off the basic alert. However, that means that many user errors will again go unnoticed unless they show some unexpected behavior.

The fact is that some of us had been running along blissfully unaware of any javascript errors in the background for years. So the optics of all these errors suddenly popping up windows following an update immediately makes you think the errors were due to the update itself.

But yes, essentially these are real errors that exist in our applications, and Alpha is making them visible for us now.