lost app when upgrade 2.0

[LALMEJA9]

Lost one app when upgrade 2.0, no errors there,
linja hangup when try open that app, I try with backup but not work.


no report on the debug file.

what can i do.

is not the first time that happens, I think that you should improve your report errors and avoid these problems.

[barrymavin]

We read your ticket already so why are you cross posting in the forums?

The zip file you provided attached to your ticket does not have any data so we are unable to look into the problem.

There have been no reports of any issues running v1 Apps with v2.

Also, it is better to provide a .lpk file (Lianja Package) rather than a zip file and include your data attached to your ticket so we can look into it.

Also... Did you have any custom command line switches on the desktop shortcut prior to the upgrade?

Please provide all this information on your ticket and we will investigate.

[barrymavin]

That App has a page with id "Catalogo_de_Almacenes" containing spanish characters.



That is the "id" NOT the "caption".

In the app directory look for the file with a .lianja extension then search for that name and remove the accented character (it is in two places) then your app will work.

You cannot use accented characters for the id or any of the UI elements.

I have changed our code to take care of this hanging situation which was caused by an internal XML parsing error.

[LALMEJA9]

and remove the accents in the cataprod.lianja but still not working, I now understand that they should not be, but should not be hung lianja and does not send any error message. I send the file again to make me check it for.

This problem was first put on the forum but did not allow me to upload the file size, send a ticket. Although I think that these problems help all programmers.

please no more scolding

[barrymavin]

As you mention in your ticket, you have --utf8 on the app builder command line switch but that particular app had been saved with a codepage locale set.

It is much better to use Unicode UTF8 as this works better in web and mobile apps too.

You cannot use accented characters in page, section or formitems id. They can be used in captions and other attributes.