I know this has been logged a number of times but from reading the other issues apparently it has been fixed in the September 2012 release. Unfortunately this still seems to be an issue in the June 2013 release as it will simply not work!
To test:
* I have created a simple page with only the AjaxFileUpload control
* I call my page with a query string (i.e. Upload.aspx?Id=9)
* I use the AjaxFileUpload to upload a file
* In the code behind, in UploadComplete, I try to get the Id value from the querystring (this is used to make changes to my database), however, the value isn't available.
I am loathed to do some of the fixes mentioned by amending the js myself and compiling my own dll as it'll get overwritten if I download the next version of the toolkit.
One of the workarounds mentioned is to use a session variable. This just seems ridiculous. If a user opens two tabs containing the site the session variable will be the same across both tabs. This could (and probably will) cause issues when I'm allowing users to upload files.
As this has apparently been fixed in the past could the fix please be applied again?
Comments: I too have this problem and I have seen the very odd suggestion to use a session variable. This is an abuse of the concept of a session. I can understand that the upload request does not follow the standard page lifecycle (hence no controls are posted back) but I do need a way to know the context that I am uploading a file in. In my case I am uploading a file against a shipment. The shipment carries an id in the database. I need a way to determine that ID from within the OnUploadComplete callback. Any suggestions would be much appreciated.
To test:
* I have created a simple page with only the AjaxFileUpload control
* I call my page with a query string (i.e. Upload.aspx?Id=9)
* I use the AjaxFileUpload to upload a file
* In the code behind, in UploadComplete, I try to get the Id value from the querystring (this is used to make changes to my database), however, the value isn't available.
I am loathed to do some of the fixes mentioned by amending the js myself and compiling my own dll as it'll get overwritten if I download the next version of the toolkit.
One of the workarounds mentioned is to use a session variable. This just seems ridiculous. If a user opens two tabs containing the site the session variable will be the same across both tabs. This could (and probably will) cause issues when I'm allowing users to upload files.
As this has apparently been fixed in the past could the fix please be applied again?
Comments: I too have this problem and I have seen the very odd suggestion to use a session variable. This is an abuse of the concept of a session. I can understand that the upload request does not follow the standard page lifecycle (hence no controls are posted back) but I do need a way to know the context that I am uploading a file in. In my case I am uploading a file against a shipment. The shipment carries an id in the database. I need a way to determine that ID from within the OnUploadComplete callback. Any suggestions would be much appreciated.