Timeline for Cannot upload to a permissions-enabled document library even with RunWithElevatedPrivileges
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 13, 2011 at 21:32 | history | edited | sumitkm | CC BY-SA 3.0 |
Corrected suggestion made in original answer and provided additional references.
|
| May 13, 2011 at 20:43 | comment | added | Grace Note♦ | Hm... I'll try that instead, and treat that as your answer. Though, if it turns out to solve the problem, you'll need to revise your answer to reflect the contents of your comment here. ♪ | |
| May 13, 2011 at 20:30 | comment | added | sumitkm | Apologies are in order. I got that completely on it's head. You are doing it right from the 'RunWithElevatedPrivileges' point to view. How about doing site.AllowUnsafeUpdates = true and then opening the web? One good reference link (that brought be back on track) blog.bugrapostaci.com/2010/04/28/… | |
| May 13, 2011 at 18:58 | comment | added | Grace Note♦ |
I'd like to see those references, because my recollection is that SPContext is guaranteed to be the current user, while generating a new SPSite inside of RunWithElevatedPrivileges is supposed to be created under the admin privileges, not the current user (if created outside of RunWithElevatedPrivileges, it would indeed use the current user). I'll give it a shot, though. Next time we run into the situation, I'll see if it works better.
|
|
| May 13, 2011 at 18:21 | history | answered | sumitkm | CC BY-SA 3.0 |