Author |
|
silentpond Newbie
Joined: 16 March 2013
Online Status: Offline Posts: 36
|
Posted: 15 April 2013 at 11:38pm | IP Logged
|
|
|
AfterLogic WebMail Lite PHP version works fine but most often it displays the error "Error while parsing XML. Error code 1." at the top of the page during session log out.
The snapshot of the error is as following:
What is causing this error and how to resolve it?
Thanks in advance.
|
Back to Top |
|
|
Igor AfterLogic Support
Joined: 24 June 2008 Location: United States
Online Status: Offline Posts: 6104
|
Posted: 15 April 2013 at 11:41pm | IP Logged
|
|
|
Some PHP error probably breaks the XML output. You can activate browser console (for example, F12 in Google Chrome, or use Firebug extension of Mozilla Firefox) and see what's the error thrown there. You can also check web server log of course, assuming you have access to it.
--
Regards,
Igor, AfterLogic Support
|
Back to Top |
|
|
silentpond Newbie
Joined: 16 March 2013
Online Status: Offline Posts: 36
|
Posted: 16 April 2013 at 12:07am | IP Logged
|
|
|
Does the debug mode log help figure out the problem as the error appears for very short time and also not in every session log out?
Regards,
|
Back to Top |
|
|
Igor AfterLogic Support
Joined: 24 June 2008 Location: United States
Online Status: Offline Posts: 6104
|
Posted: 16 April 2013 at 12:09am | IP Logged
|
|
|
Debug log of WebMail itself won't probably help if PHP error is thrown, as in that case application will be aborted.
--
Regards,
Igor, AfterLogic Support
|
Back to Top |
|
|
silentpond Newbie
Joined: 16 March 2013
Online Status: Offline Posts: 36
|
Posted: 16 April 2013 at 12:30am | IP Logged
|
|
|
I shall check the error in browser console and keep inform you the update.
Thanks,
|
Back to Top |
|
|
silentpond Newbie
Joined: 16 March 2013
Online Status: Offline Posts: 36
|
Posted: 18 July 2013 at 2:06pm | IP Logged
|
|
|
In google JavaScript console I trace an error, example of which is as following:
Resource interpreted as Image but transferred with MIME type text/css: "www.site.com/webmail/skins/AfterLogic/styles.css". webmail.php:174
Line no. 174 of webmail.php has the following code:
function GetWidth() {
var w = 1024;
if (document.documentElement && document.documentElement.clientWidth) {
w = document.documentElement.clientWidth;
}
Is this conflict generation XML error code 1? How to resolve it?
Regards,
|
Back to Top |
|
|
Igor AfterLogic Support
Joined: 24 June 2008 Location: United States
Online Status: Offline Posts: 6104
|
Posted: 19 July 2013 at 12:14am | IP Logged
|
|
|
I don't think it's related. Anyway, that doesn't look like current version of the product. It's strongly recommended to switch to version 7 available here.
--
Regards,
Igor, AfterLogic Support
|
Back to Top |
|
|
silentpond Newbie
Joined: 16 March 2013
Online Status: Offline Posts: 36
|
Posted: 19 July 2013 at 10:38am | IP Logged
|
|
|
Thanks for your suggestion but I hope that you shall assist me to resolve the problem of this version. I shall try to figure out the problem more definitely.
Regards,
|
Back to Top |
|
|
silentpond Newbie
Joined: 16 March 2013
Online Status: Offline Posts: 36
|
Posted: 28 July 2013 at 1:42pm | IP Logged
|
|
|
I was able to trace the error more definitely.
I was noticed the the following error in error console while the webpage was displaying the subject mentioned error.
[02:25:08.188> unclosed token @ http://www.webmail.site.com/processing.php:106
<?xml version="1.0" encoding="utf-8"?><webmail><error><![CDATA[Token invalid>>></error></webmail>
What is causing this error and what corrective measure can eliminate it?
Regards,
|
Back to Top |
|
|
Igor AfterLogic Support
Joined: 24 June 2008 Location: United States
Online Status: Offline Posts: 6104
|
Posted: 29 July 2013 at 12:54am | IP Logged
|
|
|
The only suggestion we have at the moment is to disable token-based CSRF protection, that's done by adding the following item to array defined in data/settings/config.php file:
Code:
'labs.webmail.csrftoken-protection' => false, |
|
|
--
Regards,
Igor, AfterLogic Support
|
Back to Top |
|
|
silentpond Newbie
Joined: 16 March 2013
Online Status: Offline Posts: 36
|
Posted: 29 July 2013 at 8:15am | IP Logged
|
|
|
I've disabled the token-based CSRF protection by adding the code 'labs.webmail.csrftoken-protection' => false, to data/settings/config.php but the subject mentioned error is still there.
After placing the code the latest error I observe in error console is
[01:01:59.894> unclosed CDATA section @ http://www.webmail.site.com/processing.php:492
<?xml version="1.0" encoding="utf-8"?><webmail><error><![CDATA[Token invalid>>></error></webmail>
is there something missing there?
Regards,
|
Back to Top |
|
|
Igor AfterLogic Support
Joined: 24 June 2008 Location: United States
Online Status: Offline Posts: 6104
|
Posted: 30 July 2013 at 12:11am | IP Logged
|
|
|
We've never encountered such issues, there's probably some configuration problem on PHP or webserver level, checking the logs of those might be helpful.
--
Regards,
Igor, AfterLogic Support
|
Back to Top |
|
|
silentpond Newbie
Joined: 16 March 2013
Online Status: Offline Posts: 36
|
Posted: 30 July 2013 at 8:46am | IP Logged
|
|
|
What could be the misconfiguration of possible PHP run time directives that may cause such problem?
Can you give me a hint?
Regards,
|
Back to Top |
|
|
Igor AfterLogic Support
Joined: 24 June 2008 Location: United States
Online Status: Offline Posts: 6104
|
Posted: 30 July 2013 at 10:32pm | IP Logged
|
|
|
All we can definitely tell that it doesn't sound like something caused by the product. If your web environment uses some additional protection layers, those might cause issues. One of the examples is mod_security extension of Apache which blocks potentially harmful requests (and false positives could happen there of course).
--
Regards,
Igor, AfterLogic Support
|
Back to Top |
|
|
silentpond Newbie
Joined: 16 March 2013
Online Status: Offline Posts: 36
|
Posted: 31 July 2013 at 7:46am | IP Logged
|
|
|
I shall check apache configuration.
Regards,
|
Back to Top |
|
|