Advanced HTML Editor 3 Support Product Page
Solved
Parent Paths & Permissions
Reported 24 Mar 2011 04:46:01
1
has this problem
24 Mar 2011 04:46:01 Peter Wiseman posted:
I just updated a CMS page from HTML Editor 2 to HTML Editor 3.Couple of things:
1) Why does the extension contain files which use ../../../ and require parent paths be allowed on a server? It's 2011 and none of the ISPs I use will allow parent paths. I've discovered that if I move the PureUpload files into 'ScriptLibrary/dmxeditor/dialog' folder after deleting the offending parent paths script in upload.asp it works, but why, why, why do I have to spend time frigging around like this???
2) The site I updated was working fine using HTML Editor 2 and PureUpload. I could upload images without a problem. Nothing has changed on the site or the server except the HTML Editor upgrade, but the page will no longer upload images. I get the following error message:
"Upload Error
This folder is not authorised for upload!
Please make sure it has write permissions and the authorisation file is in it."
Other CMS pages in the site still work with HTML Editor 2, the folder has write permissions, but what is "the authorisation file"?
Promoted Solutions
Replied 30 Mar 2011 11:03:11
Hello Peter,
Parent paths are required. And as of the latest versions of IIS the parent paths are not a security issue. That is fixed in the IIS itself.
"Upload Error
This folder is not authorised for upload!
Please make sure it has write permissions and the authorisation file is in it."
The way to set up a folder for upload requires a sertain file to be presented in that folder. When you see it you will recognize it. Upload it and you'll be fine.
Regards,
Parent paths are required. And as of the latest versions of IIS the parent paths are not a security issue. That is fixed in the IIS itself.
"Upload Error
This folder is not authorised for upload!
Please make sure it has write permissions and the authorisation file is in it."
The way to set up a folder for upload requires a sertain file to be presented in that folder. When you see it you will recognize it. Upload it and you'll be fine.
Regards,
Replies
Replied 30 Mar 2011 06:35:01
30 Mar 2011 06:35:01 Peter Wiseman replied:
104 views, but no reply.
Gotta do better than this guys!
Gotta do better than this guys!
Replied 30 Mar 2011 11:03:11
30 Mar 2011 11:03:11 Miroslav Zografski replied:
Hello Peter,
Parent paths are required. And as of the latest versions of IIS the parent paths are not a security issue. That is fixed in the IIS itself.
"Upload Error
This folder is not authorised for upload!
Please make sure it has write permissions and the authorisation file is in it."
The way to set up a folder for upload requires a sertain file to be presented in that folder. When you see it you will recognize it. Upload it and you'll be fine.
Regards,
Parent paths are required. And as of the latest versions of IIS the parent paths are not a security issue. That is fixed in the IIS itself.
"Upload Error
This folder is not authorised for upload!
Please make sure it has write permissions and the authorisation file is in it."
The way to set up a folder for upload requires a sertain file to be presented in that folder. When you see it you will recognize it. Upload it and you'll be fine.
Regards,