Callback problem

[Steve Workings]

Using 4119_4825

Something I've not seen before, can't resolve.

I have a largish UX, been building it up for a couple weeks. It has a lot of callbacks that work just fine. But suddenly I can't add the simplest of callbacks.

Putting a button on with this javascript:

{dialog.object}.ajaxCallback('', '', 'TestThis', '');

Here's the Xbasic function in the UX:

function TestThis as c (e as p)
    TestThis = "alert('confirmed');"
end function

And the response I get is unusual: I get a javascript alert-type popup that says

Function: 'TestThis' was not recognized.

It's kinda odd to see this javascript error message -- usually if a function doesn't exist or is misspelled, I don't recall getting a javascript message like this.

I've tried adding buttons in other places to test this - same result. I've tried the same function with a different name to no avail.

Chrome developer tools / Network tracing shows the callback being made with a status code of "200 OK".

Server logs show nothing at all.

I can repeat this on three different servers, with and without going through the load balancer.

And I've used the "recalculate all controls" feature.

Still, after several hours, no fix.

Any thoughts?

[GGandhi]

Re: Callback problem

may be it does not like Test..whatever. would try with confirmThis as the function name.

edit:
i tested different versions in different workspaces TestThis seems to work. but of course this will not help since I am on version 11.

[Steve Workings]

Re: Callback problem

I've tried several names in case that made a difference. I never has. The real function name I started with when I discovered the problem is "Confirm_Message_Read". It's pretty clear from the variants I've tried (plus the fact I've never run into something like this) that I'm not using any "reserved" function name.

[Davidk]

Re: Callback problem

It may be that something client-side is failing during render and the callback function isn't getting set. Anything in the browser console? Errors? This is most likely unrelated to the actual callback method and function.

[Steve Workings]

Re: Callback problem

i agree - something is "in the way" as the callback is simple, and another dozen of them work just fine in the UX. But no errors in the browser console. I may have to start tearing pieces out until this works to identify the problem.

[peteconway]

Re: Callback problem

I'start with a copy of the UX, then, delete the callback and anything to do with it and pre-render turn it off if turned on, save the UX, see what happens if still an issue. Then remove the last List component, if one exists, save the UX and see if it works. - I've had some success with this - don't know why but it worked in many cases, if it works paste the list from the original UX back in. Good luck.

[Steve Workings]

Re: Callback problem

24 hours later, still no joy. I actually have 2 callback problems, so focusing on just one:

This is an update of a UX - a lot of revisions, etc for a new version. So I have one callback being made, that is insisting on running Xbasic code that no longer exists. The callback occurs, but is still calling Xbasic that I've removed from the Xbasic function.

So I've made a copy of the UX - working with that. I've removed *all* Xbasic function code, saved, published, put it back, saved, published, and still the callback insists on running the "old" function code with Xbasic lines that no longer exist.

This particular function is called "SetArea".

So, I built a new function "SetArea_v2", copied the Xbasic into it, and changed the reference in the javascript callback. When I do that I'm back to the javascript-type alert message that says "Function SetArea_v2 was not recognized."

I'd upload/share this UX but it's extensive, reliant on a lot of support leading up to it, etc. Anything I supply wouldn't be very representative of what I'm doing at that point.

[CharlesParker]

Re: Callback problem

Sounds like your running a cached component in some way. I would not recommend making a "copy" but rather create a new UX and copy the controls over without the xbasic or the button calling it - upload and run it to make sure your good then add in the offending controls. How is the UX called in the first place? Is there a chance it's calling anything from local storage?

[CharlesParker]

Re: Callback problem

Also, I tend to agree with David K when he said: "This is most likely unrelated to the actual callback method and function."

I have had issues with javascript leaving off a ; or putting end function in twice in a server side X basic event that caused goofy errors.
Which is why I am saying create a NEW UX and copy in the controls till it fails...

[Steve Workings]

Re: Callback problem

OK, so I created a new UX, copied and re-created everything to it, same problems.

I didn't do this a few steps at a time - as I noted there are a lot of dependencies. I may have to take yet another day and go more slowly and in smaller pieces to see if I can find the culprit(s). Shouldn't have to do this of course....