Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIproblem with DNNTree on 4.0.3problem with DNNTree on 4.0.3
Previous
 
Next
New Post
5/16/2006 1:41 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



 
New Post
5/16/2006 5:11 PM
 
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
 
New Post
5/17/2006 9:51 AM
 
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.

 
New Post
5/17/2006 10:21 AM
 
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
 
New Post
5/17/2006 3:34 PM
 
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
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIproblem with DNNTree on 4.0.3problem with DNNTree on 4.0.3


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out