page is showing
error in Edge console, but google chrome does not have this error, the page has the ajax refresh to refresh a message listing.
Edge:
Chrome
By the way, the error only happens if the console is open.
There is no actual problem happening on the page, it's just a minor annoyance that the Edge console tries to interpret the ajax communications as a xml document while it is not.
Regards,João Rosado
Hello Leo,
Is this a mobile application built with OutSystems 10?
Cheers,Rodrigo
Rodrigo Coutinho wrote:
it is a web application with outsystems 10.
Hi Leo,
I managed to replicate this. I'll forward it to the R&D team to get it fixed.
Thanks for reporting!R
This error also appears to happen whenever an ajax refresh is executed in a web app.
Hi Rodrigo Coutinho,
I'm having this error in the version 9.1.301.4. The R&D team fixed this issue just for version 10?
Thanks,
LT
Luís Teixeira wrote:
I'm still getting it in version 10 so nope they haven't fixed it for 9 or 10.
Hi.
There are any update about this error?
We are having the same problem on Java stack with version 10.0.408.2.
There are any quick fix for this?
Kind Regards,
Diogo Miguel
Hi Diogo,
The team has been notified about the error, and it's on our backlog to be fixed. But this problem has no impact on customers using your application.
As João mentioned, this error only occurs when you have the Edge console window open. It is a problem of the console trying to interpret our AJAX communications, so you shouldn't need to worry about it.
Cheers,R
Hi, I am having the same error "XML5632: Only one root element is allowed." with IE 11. The problem is that I am not able to trigger with notify server action from javascript with message using input control. It didn't work even though I didn't open console (F12). After removing xml tag "<strong></strong>" in the notify message, I am able to trigger notify message to server action. I don't know what the root cause is but it works for me as workaround. I just wanna share that for those who encounter the same issue. Cheers.
Hello Everyone..
The reason for this error is, Your page size(generated html) is crossing the limit of the configured http post size in your configuration(standalone-outsystems.conf). To avoid this type of errors try to remove the huge resources(huge xml,images(binary data) from entities in your preparation) from the preparation.
Thanks
Ramakrushna Rao Seera
We are having the same issue. Using OS10 with IE11
Ajax submit is working fine, but submit is giving "Only one root element is allowed." on the same page.
Hi Saugat,
Like I said above, it's not an issue. The message open appears because you open the browser console and it tries to parse requests that it shouldn't.
The application is not affected.
Regards,
João Rosado
Hello Joao,
We have just deployed our app on production. It was earlier on prod but this time we have changed its backend theme with the base theme.Now this app is working great in chrome.But on IE we are not at all able to load the app and its giving this error XML5632: Only one root element is allowed on console.We are getting this error on firefox too, but the application is still loading and working.Can you please suggest what should we do to fix it.
Thanks,Anagha
Hi Joao,
Is there any update regarding this error XML5632: Only one root element is allowed.
im using OS V11 with IE latest version.. the errror only come out when i used datepicker.
IE console error
Datepicker:
Jomari
Jomari Reyes wrote:
Hi Jomari,
I am having this exact problem. Do you already have a fix for this problem?
Thanks!
Hi Jorgen,
There is no update nor a fix for this problem. OutSystems has confirmed this error only occurs when you have the console open (I do wonder how they checked that though). The issue that you are having lies more likely in the fact that you use IE11 instead of a mordern HTML5 browser.
Can you tell us what framework you are using? SilkUI or OutSystemsUI? and what type of application are you creating? A Web Traditional or a Reactive/Mobile one?
Greetings,
Vincent
Hi Vincent,
Its a traditional web app with OutSystemsUI. I was hoping to fix the datetime picker when i resolved the issue shown in the console.
i find it interesting that when i open IE i dont encounter the datetime issue and when the reporter (my colleague) of this issue opens the same screen in IE (Same version number and update version) he still encounters the datetime picker issue.
Jørgen