I've found you can load a community entry into the community edit form, in the same way you can load a user entry into the user edit form. But you can't load a comm entry into a user edit form or a user entry into a comm edit form, because the forms are different and presumably the query that loads the entry gets a malformed response from the slightly different permissions that operate in communities unless the right form is used.
I'm not sure I'd even call the ability to do this a bug, given that you can't save or view anything you shouldn't, it's really just forcing a form to show content you can view anyway using a slightly different template.
The thing that sounds like a bug is whatever it is that is redirecting people to the forms in such a way that they see the wrong content and think they have the ability to edit other people's journals, because that's clearly causing panic.
I am wondering if this problem is actually linked to having a broken lj-login install on the browser - I think that may also be linked to the problems where LJ keeps logging people out? Just a theory but I tried to replicate this problem and was unable to do so.
It would certainly be a polite and commercially astute move if LJ could offer lj-login assistance in getting their plugin working asap, particularly if the broken plugin is causing people to think there are other problems.
Sorry, I don't have a dw so this will be screened. I assume someone will be able to unscreen it if it seems helpful.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2011-10-30 09:05 pm (UTC)I'm not sure I'd even call the ability to do this a bug, given that you can't save or view anything you shouldn't, it's really just forcing a form to show content you can view anyway using a slightly different template.
The thing that sounds like a bug is whatever it is that is redirecting people to the forms in such a way that they see the wrong content and think they have the ability to edit other people's journals, because that's clearly causing panic.
I am wondering if this problem is actually linked to having a broken lj-login install on the browser - I think that may also be linked to the problems where LJ keeps logging people out? Just a theory but I tried to replicate this problem and was unable to do so.
It would certainly be a polite and commercially astute move if LJ could offer lj-login assistance in getting their plugin working asap, particularly if the broken plugin is causing people to think there are other problems.
Sorry, I don't have a dw so this will be screened. I assume someone will be able to unscreen it if it seems helpful.