is that right? If I go to a library in the designer, i can see upload.aspx there. Can't create a new one (and i guess that is because there is really only one per site, or collection?). Anyway, I can open upload.aspx in advanced and put some script under PlaceHolderMain, but unlike any other page/form,etc I have worked with, this one won't respond to anything. alert('hi'); will not worK?

2 Answers
2

You shouldn't manipulate (OOTB) Upload.aspx since it is not recommended!

You best chance is to use Custom Action with Location="ScriptLink". It loads the JavaScript on all the site pages and even the dialogs. You can have a custom actions in a feature (Site Collection/Web). See this example

To be a little more verbose for Falak, editing files in the hive breaks your warranty. It is possible to make your own virtual layouts folder to do branding for these files, but it heavily impacts maintainability. Falaks answer stands. (You can also change the master page for the upload.aspx by creating your own layouts folder... still not recommended)
–
Hugh WoodDec 4 '12 at 15:12

I see. thanks for the info. If i could simply figure out how to pass the ID from dialog init to the edit form to save variables...i wouldn't have this problem. lol...thanks guys.
–
JustinDec 4 '12 at 15:28

Justin,
There are tricks that you can implement to still manupulate the upload page client-side without changing the form. I have done this through the use of an iframe.
From the host page (example: All Items.aspx) you would load the upload.aspx page into an iframe and once loaded, you can manipulate it from the host page because it is being served from the same domain. With the help of some UX/UI concepts (ie: overlays, animated 'busy' icons) the user will never nitice they actually in a different page.