Same form two different versions of foxincloud, different result

This with 2.31.beta4

This with 2.31.beta6

No button in grid column and when i clicked on the column where there was the button a new form is opened like i do with the button. the new form depends for the value in the column3 but with version 2.31.beta6 always the same form is opened. In 2.31.beta4 i can open different forms one for HD one for PM one for GE

Hi Michel

You should come back to version 2.31 in beta 5, beta 6 seems to have some problems!

Regards

Gilles

Ciao Michele,

To analyze and fix the issue, we need to compare the HTML and JScode generated in both versions.

On the FoxInCloud Live Tutorial, the command button is generated OK in a grid column:

Can you share the HTML and JS generated from your form in beta.4 and beta.6? Or even better compare these 2 couples of files using WinMerge and share the differences?

Thanks in advance

Hello Gilles,

Do you also have a generation issue with V2.31.0-beta.6?
If yes, do you have the same symptom as Michele?

Anyone else?

Also, have you checked the developer console for possible JavaScript errors?

I haven't had time to test yet

Here are the files... I tested with beta5 and i have no problems... In the same form i have another problem. In this form i have a pageframe and in each page i have a button to return to main page. This button doesn't work.

Click here

This button doesn't work

JavaScript Error?

Thanks,

The slight differences between these files don't explain the issue…

Do you have the problem in dev. or prod.?

If in prod. only, make sure to update awScript/*.* on your production server…
Using xxxProd.Update.prgis the simplest and safest way.

No errors in js... Problem still in dev mode on my server

I confirm.

Many problems with input and label. Details to come ...

I need more details to understand… please share more debugging info. and/or a test URL, with a complete explanation how to reach the test case and reproduce the issue.

I don't know which details..... i have a version where a page works and a version where the same code used before doesn't work... If someone want to see directly the problem i can show it.... if someone want to access to my dev machine to verify it, no problem, but i can't make every time the debug for others... I continue to use beta4... In beta6 it is a fact that something doesn't work correctly

OK then we need to switch to private support. I'll PM you for an appointment.

thanks to our private session, V 2.31.0-beta.7 released today should fix the issue… do you confirm?

I can confirm that with last beta7 the problem has been fixed

Thanks

Thanks for the feedback!