Comment 5 for bug 786904

> the UserPrivledgeException should be thrown inside the ModelWrapper (if it
> silently fails then it should be added to checking in ModelWrapper)

Yes, that is absolutely what *should* happen, but it isn't going to happen any time soon. I spent a couple of hours and made a complete analysis over on the other bug. See the last part of the discussion -- the checkPermissions functions have very weird overlapping functionality and I would prefer it be elsewhere but we can't fix it now.

So for now, we are going to keep those checkPermissions functions checking and throwing exceptions. We just need to get the logic right.

I have done what I suggested, and it worked -- I am now getting a PRIVATE view where previously I was getting a PUBLIC. But it is *still* failing silently to actually write to the datastore, no doubt due to yet another bug. I'm on it.