problem with DNNTree on 4.0.3 - ClientAPI Component [Lead: Jon Henning]

Forum DotNetNuke® Pro... ClientAPI Compo... problem with DNNTree on 4.0.3

5/16/2006 11:41 AM

	Eric Scott
9 posts
www.promediagroup.com

problem with DNNTree on 4.0.3

Modified By Eric Scott on 5/16/2006 1:43:06 PM)

I am using xhtmlConformance = transitional.
I found the post regarding the client id and changing : to $. I have done this and now I am getting a different error. I have changed xhtmlConformance back to legacy and the error persists.

With FireFox 1.5, I get the following:

Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIDOMParser.parseFromString]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: http://localhost/js/dnn.xml.js :: anonymous :: line 63" data: no]

With Internet Explorer 6, it blows up on line 517 of dnn.controls.dnntree.js:
for (var i=0; i<oNode.childNodeCount(); i++) with oNode being null.

I can trace this back to generateTreeHTML which does not set this.rootNode to a value because this.DOM.childNodesCount = 0

Any Ideas?

I forgot to mention, this is occurring within the default FileManager.

Thanks,
Eric

5/16/2006 3:11 PM

	Eric Scott
9 posts
www.promediagroup.com

Re: problem with DNNTree on 4.0.3

I tracked this down a little bit farther. The error occurs when I change the default COLUMN_DELIMITER from Chr(17) to something else. Using Chr(17) causes the page to fail xhtml validation. Using other characters causes the previously posted error to occur.

I have gotten around this by changing the ClientAPICaps.config file as follows:
    <functionality nm="SingleCharDelimiters" desc="Supports single character delimiters (i.e. Char(18))">
        <supports>
        </supports>
        <excludes>
            <browser nm="*" />
        </excludes>
    </functionality>

That seems to take care of this issue. Any caveats to using this approach?

Thanks,
Eric

5/17/2006 7:51 AM

	Jon Henning
1622 posts
www.codeendeavors.com

Re: problem with DNNTree on 4.0.3

I am interested to see where you found the info that states that using something like Chr(17) causes xhtml validation to fail. I am not disagreeing, only requesting more info. Ideally we could use a single "safe" character to perform our delimiting of strings. Making the change as you have done will increase the size of each roundtrip, for I am relying on multiple character delimiters when this is set.

5/17/2006 8:21 AM

	Eric Scott
9 posts
www.promediagroup.com

Re: problem with DNNTree on 4.0.3

The error message is outlined at:
http://validator.w3.org/docs/errors.html

It is "410: reference to non-SGML character". The page is using UTF-8 encoding.

Perhaps selecting a different encoding type would eliminate the validation error?

For reference, the site I am working on is posted at: http://motorsports.promediagroup.com. It is currently set to use the 3 character delimiter. I don't have anything that is publicly viewable that uses Chr(17) which will trigger the validation error. If you think it would be helpful, let me know and I'll try to post something.

Thanks,
Eric

5/17/2006 1:34 PM

	Eric Scott
9 posts
www.promediagroup.com

Re: problem with DNNTree on 4.0.3

I put a simple test page up that writes Chr(17) to the body of a page. The url is:
http://www.promediagroup.com/test2.asp

The encoding was not set correctly on the other site I posted. On the test page, I changed the encoding to iso-8859-1 and verified that this is what the validator was using.

I tried to validate the page using two validators and both failed on Chr(17).
http://www.htmlhelp.com/tools/validator/
http://validator.w3.org/

Thanks,
Eric

Page 1 of 2

Forum

DotNetNuke® Pro...

ClientAPI Compo...

problem with DNNTree on 4.0.3