Pure ASP Upload 3 Support Product Page


PAU 3 causes Dreamweaver Javascript error when executing onload in PureUpload_beforeSave.htm

Reported 13 Sep 2012 22:40:36
have this problem
13 Sep 2012 22:40:36 Steve Skinner posted:
I've had this problem on two clean (new installs) of Dreamweaver on my desktop and my laptop. Both machines are running Windows 7 64-bit and Dreamweaver ver. 12 (CS6).

Many extensions were installed prior to installing the PAU 3 extension (almost all are DMXzone extensions), but immediately after installing PAU 3, when I try to create a new file by right-clicking, I get the error popup in Dreamweaver.

"While executing onLoad in PureUpload_beforeSave.htm, a JavaScript error occurred."

I have tested this thoroughly and it is 100% repeatable. It happens only when you right-click in the files view in Dreamweaver to create a new file. If you use CTRL-N or click File, and then New in the top menu the error does not occur.

I have been through a couple of clean restarts with Dreamweaver and installing all the new extensions again and without fail, PAU 3 is the only one that will cause this problem.

Granted, there is a way around it but I've spent a lot of money on all your extensions I've purchased. It'd be great if this error could be resolved with an extension update.


Replied 14 Sep 2012 06:42:41
14 Sep 2012 06:42:41 Vulcho Vulev replied:
Hello Steve.

We are going to check this issue.

Regards: Vulcho.
Replied 14 Sep 2012 16:40:40
14 Sep 2012 16:40:40 Steve Skinner replied:
Thanks. Let me know what you find.
Replied 13 Mar 2013 05:55:57
13 Mar 2013 05:55:57 Steve Skinner replied:
Still waiting to hear on this. I have a fresh install of Windows 8 Pro. Installed all extensions I use with no problem until I installed Pure ASP Upload 3.

Once I did that, I get this same problem when right clicking on a folder to create a new file.

"While executing onLoad in PureUpload_beforeSave.htm, a JavaScript error occurred."

So, now you have three unique installs, spanning Windows 7 and Windows 8 where this problem has been repeated 100% of the time. I hope you are still "going to check the issue" that you mentioned 5 months ago....

Just to be clear, I installed all of my extensions in batches, deleting the wincache file after every batch just to make sure there wouldn't be any problems relating to that file. I even deleted the whole configuration folder (which was just created same day when I installed DW CS6) when I first encountered the problem again and then tried DW again without Pure ASP Upload 3. Same results. I get no javascript bugs in DW when PAU3 isn't installed. My test conditions were about as clean as you can get.
Replied 16 Feb 2014 20:05:15
16 Feb 2014 20:05:15 Mr. em replied:
no answer yet?
Replied 16 Feb 2014 20:44:58
16 Feb 2014 20:44:58 Steve Skinner replied:
I know... I have been asking for a solution for this for years. When they feel like providing support, they're excellent, but for whatever reason they have refused to dig into this one. A few different people have posted about this other than me, but aside from "acknowledging the problem" nothing has ever been done.
Replied 17 Feb 2014 10:05:31
17 Feb 2014 10:05:31 Teodor Kuduschiev replied:

This will be improved in the next Pure ASP Upload/ Pure PHP Upload updates.
Replied 17 Feb 2014 13:37:35
17 Feb 2014 13:37:35 Steve Skinner replied:
That's great news!
Replied 17 Feb 2014 14:09:43
17 Feb 2014 14:09:43 Rusty Back replied:
When can we expect the next Pure ASP Upload/Pure PHP Upload updates?
Replied 25 Feb 2014 22:48:25
25 Feb 2014 22:48:25 Christine T replied:
I am having this issue as well.
Replied 26 Feb 2014 09:17:20
26 Feb 2014 09:17:20 Teodor Kuduschiev replied:
Hello Christine,

This will be improved in the next Pure ASP Upload/ Pure PHP Upload updates.

Rusty, unfortunately i do not have an exact update date yet.
Replied 26 Feb 2014 17:51:45
26 Feb 2014 17:51:45 Christine T replied:
Okay, thanks. Somehow, even after that error, the extension is working fine and hasn't thrown it again.
Replied 26 Mar 2014 16:21:12
26 Mar 2014 16:21:12 Teodor Kuduschiev replied:
The issue is fixed in the latest version of the extension. Please update.
Replied 26 Mar 2014 16:35:30
26 Mar 2014 16:35:30 Steve Skinner replied:
Hallelujah! This issue is been lingering for years. I'm so glad to know it's solved. Updating right now...
Replied 26 Mar 2014 17:03:19
26 Mar 2014 17:03:19 Christine T replied:
Thank you! Do we need to rebuild or reapply the extension to our existing pages?
Replied 26 Mar 2014 17:17:14
26 Mar 2014 17:17:14 Teodor Kuduschiev replied:
No, this is not required.

Reply to this topic