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/18/2006 9:47 AM
 

Thanks for taking the time to post your findings.  It appears that I will need to do one of two things.

1) Find a different "safe" character to use that will allow validation

2) Come up with a more complicated means of providing delimiter functionality

Unfortunately, I don't have a lot of time to investigate this matter at the moment.  I have a few theories on how I can accomplish 2, but would prefer to get option 1 working if at all possible.  If you could do some trial and error here and report back your findings it would be greatly appreciated.


 
New Post
5/18/2006 10:33 AM
 
Jon,
I appreciate you taking the time to look into this.

I'm not sure when I will get back to this since the workaround of using 3 character delimiters is acceptable for my current situation.  I expect option 1 is possible with the right "safe" character.  I tried ~ and | without success.  After I get a couple of projects out the door, I will revisit this and post whatever I find.

Thanks,
Eric
 
New Post
11/29/2008 2:32 PM
 

i'm still getting this error in the filemanager using dnn4.9.  has this been looked at yet?


 
New Post
6/2/2009 1:22 PM
 

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://domain.com/js/dnn.xml.js :: anonymous :: line 63"  data: no]

CurlyFro wrote i'm still getting this error in the filemanager using dnn4.9.  has this been looked at yet?

I am still getting this error on 4.9.4 in the File Manager as well. However, I found that if I remove the jQuery 1.3 javascript include from my skin it works fine. Only problem is my skin needs jQuery to function properly.

Any helpful work arounds?

 
New Post
6/29/2009 8:31 PM
 

CurlyFro wrote

i'm still getting this error in the filemanager using dnn4.9.  has this been looked at yet?

I'm right there with you, Though, i didn't have this problem just a few weeks ago!  I think that it's an odd odd situation... haven't seen it before in some pretty extensive DNN moves and upgrades.

the problem:
browsing to the Host or Admin File Manager (in DNN 4.9), expanding the Portal Root folder will not work! the icon keeps "spinning" and at the bottom of the browser it will alert a javascript error regarding the child nodes. it spins for ever and no sub folders can be displayed!

the details:
- if you create a new folder, it will display that new folder for the split second after it's created. any refresh action on the page and it will not be able to be displayed again.
- it seemed that a broken </form  (note no end tag?) would appear at the bottom of the page and at the bottom of some of the other admin related dnn pages
- in SAFARI (PC) it will still work properly!!?  in Safari you can click to expand the tree just fine. However IE 7, 8, FFox, Chrome all have the problem of not being able to expand the tree, giving a javascript error.
- this dnn instance was a move from one old server to a new one... the old server works fine and has zero errors with the file manager for all browsers(!?). once moved over to the new server, the error appeared. there were no changes to the site skin or anything else. So early on i looked to the host to correct the issue, suggesting possibly folder permission issues, etc, but they've had little luck, and all other features of DNN related to IIS permissions are funcitoning properly including being able to create new folders and images, etc from within the File Manager.

So is this an IIS setting or version issue? or is that related somehow, or is it a coincidence?

I've got an otherwise perfectly running site not able to use the File Manager...

 

 
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