|
|
Rank: Member
Groups: Member
Joined: 5/12/2009
Posts: 20
|
The well known callbackPanel error occurs on my website too. I spent already hours in your forum but did not get the right hint. Now I am in Kongo Kinshasa where band with is low and there is no opportunity to continue searchin' the forum.
Here is what I have:
- I have only one callbackpanel on my site
- I have no server side redirect
- even if the callback's execute routine is empty, this error occurs
- if I remove the triggers the error disappears (which is clear)
- the error occurs only in IE but not in Firefox !!!
Due to the low bandwiths here I have no oppotunity to prepare a test project - sorry. But the problem seems to be difficult to trace ...
Thank you for any help,
Ralph
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi, The error is almost always caused by code errors related to dynamic loading. Please see this post for details: http://www.essentialobjects.com/Forum/Default.aspx?g=posts&t=1056You usually only notice the issue on IE because IE is able to show you the stack trace, where FireFox can not. It does not mean the error does not occur on FireFox. If the problem continues, we do need a test project/page from you. If you send the full project, you can omit EO.Web.dll and that should reduce the file size to only a few KBs. If you have a single file that can reproduce the problem, you can just post it directly in the forum. Thanks!
|
|
Rank: Member
Groups: Member
Joined: 5/12/2009
Posts: 20
|
Thank you so far,
Unfortunately the whole page is complex. I placed the callbackPanel inside a formview inside a contentPlaceHolder working with a master page. The page works with a Postgres database. But I will try to break it down!
Ralph
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi, We have looked into the test code you sent to us. It is an encoding issue caused by the following line in your web.config:
Code: HTML/ASPX
<globalization fileEncoding="iso-8859-1" requestEncoding="iso-8859-15"
responseEncoding="iso-8859-15" culture="fr-FR" uiCulture="fr-FR"/>
Change it to utf-8 should resolve the issue for you. Generally you should always stick with utf-8 whenever you use AJAX (no matter which AJAX solution). A few core client side JavaScript components that almost every AJAX solution relies on can only handle utf-8 well. So very often you would run into mysterious problems once you change the encoding to something else. The same problem can cause multiple very different errors. The other very common error caused by the same problem is "invalid viewstate" error. Thanks!
|
|
Rank: Member
Groups: Member
Joined: 5/12/2009
Posts: 20
|
I am - again - impressed by the efficiency and the answering time of the EO support. I sent two test projects and I got two good solutions:
1. I should stick to utf8 encoding if I want to use Ajax. As I have to develop applications for francophone countries I worked with another encoding (web.config) which caused the problem
2. I had nested forms in my app: The master page contains a form tag and my page itself too - which is not allowed. A problem which became visible only after introducing the callback component.
Now everything seems to work fine - Thanks again!
Greetings from Kinshasa
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Thanks for the update. Glad to hear that everything is working for you!
|
|