359 reputation
316
bio website
location 6
age
visits member for 4 years, 3 months
seen Mar 31 at 19:34

"Being an Alice in the world of computing can be a very problematic position."

I'm a Community Manager for the Stack Exchange Network. I look forward to working with you on improving this community. ♪

On the offside: programmer/designer with a Computer Science degree and an electronic media degree. Enjoys gaming and does designwork as a hobby. Formerly employed as a full-time SharePoint developer in a WSS 3.0 environment.


May
9
comment Cannot upload to a permissions-enabled document library even with RunWithElevatedPrivileges
@Dave That sounds kinda like an answer, if you knew what I could do to avoid that.
May
9
comment Cannot upload to a permissions-enabled document library even with RunWithElevatedPrivileges
@Dave Mostly out of not remembering whether I have to call web.Update() after changing the value of web.AllowUnsafeUpdates (which is set to true before the upload, then set back to false). I figured that it'd be safer to call the updates than to assume that changing the boolean alone was enough.
May
9
comment Cannot upload to a permissions-enabled document library even with RunWithElevatedPrivileges
I will try this variant out. Next time we run into the situation, we'll see if it works out.
May
9
comment Cannot upload to a permissions-enabled document library even with RunWithElevatedPrivileges
For the curious, GetSPUser just extracts the SPUser from an SPUserValue that has a user, while NonfiringUpdate is just a System.Update(false) inside of the DisableEventFiring of an event receiver template. Everything else is just normal functions and ideally intuitive variable names.
May
9
asked Cannot upload to a permissions-enabled document library even with RunWithElevatedPrivileges
May
6
awarded  Citizen Patrol
May
6
comment Origin of different styles of ID numbers for recurring Calendar events
Ooh, I see. So, basically, until it gets modified, it'll be the timestamp of the recurrence, but once it gets modified, it then gets treated as its own ID (32, in this case), and it consequently uses a notice of the root (3) instead of the timestamp. This is enlightening. Makes it a pain to try and figure how best to avoid links breaking, but definitely a step forward. Thank you much!
May
6
accepted Origin of different styles of ID numbers for recurring Calendar events
May
4
asked Origin of different styles of ID numbers for recurring Calendar events
Apr
15
comment Cannot send emails through SMTP using a Timer Job?
Wasn't directly the cause of my specific issue, but farm account permissions were indeed at the root of it. The login should've been fine, but my development server wasn't allowed to properly access the mail server like the production server does. Something in the services for workflows gets around this issue, but the Timer service did not get affected. Once we incorporated proper access for the dev server, it worked! Thank you much.
Apr
15
accepted Cannot send emails through SMTP using a Timer Job?
Apr
15
awarded  Commentator
Apr
15
comment Cannot send emails through SMTP using a Timer Job?
The value for "Log On As" for the "Windows SharePoint Services Timer" service, which I assume will be my WSS 3.0 equivalent of your SP 2010 Timer, is the System Account. So it should have permissions on the mail server on the same bound that it does for the Workflows.
Apr
15
comment Cannot send emails through SMTP using a Timer Job?
Where would I go about confirming the farm account's identity (I'm in charge of object model work, not so much the farm topology)? I'm under the impression that the Farm Account is the same as the System Account under which Workflows are run under, as well as SPSecurity.RunWithElevatedPrivileges, but if this is what is probably tripping me up, I should investigate.
Apr
15
revised Cannot send emails through SMTP using a Timer Job?
I apparently have a strong tendency to fall asleep halfway through a sentence. This is twice...
Apr
15
asked Cannot send emails through SMTP using a Timer Job?
Apr
14
comment Develop a timer job that operates only on selected site collections
This worked like a charm. I'm able to activate and deactivate the feature on different site collections, and the timer job flawlessly adapts to it. Thank you much! ♪
Apr
14
accepted Develop a timer job that operates only on selected site collections
Apr
14
asked Develop a timer job that operates only on selected site collections
Apr
13
comment Multiple workflows across a list versus one workflow iterating the list
This is how the one-on-all workflow would function, yes.