Support forums - Seems that the TempDirectory property is not working correctly anymore

Support forums » Products » Ajax Uploader » Re: Seems that the TempDirectory property is not working correctly anymore

Seems that the TempDirectory property is not working correctly anymore

Last post 03-25-2009, 2:05 AM by el.c.. 5 replies.


	Sort Posts: Previous Next

03-24-2009, 1:11 PM 50225

el.c.
Joined on 03-03-2009
Posts 16

Seems that the TempDirectory property is not working correctly anymore

Reply Quote

It seems that the TempDirectory property is not working correctly anymore with the latest release (03/17). (eveything was okay with the previous version)

On the dev server, Persisted files are now stored on C:\Documents and Settings\ServerName\ASPNET.ServerName\Local Settings\Temp\AjaxUploaderTemp , no matter of the TempDirectory value.

Of course that fails on the prod. server, as the AjaxUploader tries to write the persisted files on c:\windows\temp\AjaxUploaderTemp

Error Message: Unable to find the uploaded file in directory: c:\Windows\TEMP\AjaxUploaderTemp

PS: what is quite strange: error does not happen everytime but the persisted are NEVER saved in the TempDirectory folder! (I had the error with almost all browsers (IE, Firefox, Chrome))

Any clue??

Thanks in advance

03-24-2009, 1:23 PM 50228 in reply to 50225

Adam
Joined on 09-23-2003
Aurora, ON
Posts 18,678

Re: Seems that the TempDirectory property is not working correctly anymore

Reply Quote

Please set AutoUseSystemTempFolder property to false then try again.

asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx

03-24-2009, 2:09 PM 50231 in reply to 50228

el.c.
Joined on 03-03-2009
Posts 16

Re: Seems that the TempDirectory property is not working correctly anymore

Reply Quote

Thanks for this prompt reply.

Persisted files are still saved in systemTempFolder (the TempDirectory property is not recognized??)

but the error message is now more logical:

Unable to find the uploaded file in directory: TempDirectory value

public pageclass() {
this.Init += new EventHandler(this.CPage_Init);

}

protected void CPage_Init(object sender, EventArgs e) {
   tDocUpload.AutoUseSystemTempFolder = false;
   tDocUpload.TempDirectory = CfgVar.DOC_STORAGE_TEMPDIR;
} 

Any idea?

03-24-2009, 3:13 PM 50235 in reply to 50231

Adam
Joined on 09-23-2003
Aurora, ON
Posts 18,678

Re: Seems that the TempDirectory property is not working correctly anymore

Reply Quote

I made a test using the following code and it works fine.

<script runat="server">
protected override void OnInit(EventArgs e)
{
base.OnInit(e);
PersistedFile1.FileChanged += new PersistedFileEventHandler(PersistedFile_FileUploaded);
}
void PersistedFile_FileUploaded(object sender, PersistedFileEventArgs args)
{
InsertMsg("File is changed! " + args.FileName + ", " + args.FileSize + " bytes.");
//Copys the uploaded file to a new location.
args.CopyTo("c:\\temp\\" + args.FileName);
//Opens the uploaded file's data stream.
//System.IO.Stream data = args.OpenStream();
}
</script>
<CuteWebUI:UploadPersistedFile AutoUseSystemTempFolder="false" runat="server" ID="PersistedFile1" InsertText="Upload File">
<VALIDATEOPTION MaxSizeKB="10240" />
</CuteWebUI:UploadPersistedFile>

Please try it and if you still have problems download the control again.

Keep me posted

03-24-2009, 10:26 PM 50245 in reply to 50231

cutechat
Joined on 07-22-2004
Posts 2,332

Re: Seems that the TempDirectory property is not working correctly anymore

Reply Quote

Hi,

That's a bug. We have fixed it today.

Please download it and test again.

Regards,
Terry

03-25-2009, 2:05 AM 50252 in reply to 50245

el.c.
Joined on 03-03-2009
Posts 16

Re: Seems that the TempDirectory property is not working correctly anymore

Reply Quote

Thanks. This release fixed it.

Would be so cool if the new releases do not break what was correctly working with the previous one - It looks like I really have to make a FULL check before upgrading...