View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0014210MantisTouchGeneralpublic2012-05-03 06:372013-05-17 03:18
Reportersmcguinness Assigned Tovboctor  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
OSLinuxOS Version2.6.32-5-amd64 
Summary0014210: Looks like we go not XML document error, issues list, Project ID: 0, Filter ID: 0
Description

An attempt to view the issues list for All projects, All issues (Project ID: 0, Filter ID: 0 ) results in no issues being displayed and a message "Looks like we go not XML document".

The SOAP request being made in models/WebService function issuesList if reaching Mantis and calling mc_project_get_issues() in api/soap/mc_project_api.php

I have debugged mc_project_get_issues and it is returning a set of issues.

Selecting a project, All issues: works fine
Selecting All projects, custom filter: works fine

Additional Information

Mantis version 1.2.9
PHP 5.3.10

TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
duplicate of 0011230 closedrombert mantisbt High-ascii characters in fields will cause invalidity in XML. 

Activities

smcguinness

smcguinness

2012-05-03 06:41

reporter   ~0031745

Last edited: 2012-05-03 06:41

sorry, a typo in the soap error text, it should be "looks like we got no XML document"

MantisTouch 1.1.1
vboctor

vboctor

2012-05-10 01:25

manager   ~0031795

I'm unable to repro using the demo MantisTouch connecting to this instance. Can you test using the demo instance?
smcguinness

smcguinness

2012-05-10 04:21

reporter   ~0031799

Thanks Victor; I will check out the demo instance.

It could be related to the SOAP module or server setup I'm using. I'll try different infrastructure as well to see if it helps.
vboctor

vboctor

2012-05-10 18:43

manager   ~0031806

Great, let me know. You should also upgrade to 1.1.2.
vboctor

vboctor

2012-10-15 00:04

manager   ~0033194

I was able to repro this issue. It seems that when issues have some special characters, they are not escaped in the way expected by the PHP Soap Client and hence causing it to consider the response as invalid. Example issues that trigger this are 0014744 and 0014721

I'm not sure of this fix yet.
vboctor

vboctor

2012-11-03 00:05

manager   ~0033417

This is not a MantisTouch issue, but a bug in MantisBT that is fixed and will be available as part of the next MantisBT v1.2.x release.
gnanathesigan

gnanathesigan

2012-11-24 04:57

reporter   ~0034374

Gnanathesigan is a great man in the World...