| User | Post |
|
8:37 pm March 1, 2009
| joejanish
Member
| | | |
|
| posts 11 |
|
|
This may seem like a dumb question but … when is it a good idea to click the "Flush Cache" button in the options?
I have about 45 people set up as contributors and every once in a while something weird happens with the permissions. For example I have one user who, if I set up as an "editor" for a category, can no longer edit anything — not even his own posts – but when I remove him from the category, he can do what he did before. In other words, Role Scoper permissions are working in reverse, and only for this one user.
Could it be something with the cache? Many thanks.
|
|
|
2:44 pm March 2, 2009
| Kevin
Admin
| | | |
|
| posts 2503 |
|
|
In theory, you should never need to manually flush the cache. In practice, it has been useful under various configurations in the past where Role Scoper failed to auto-flush the cache appropriately. In theory, those bugs are all fixed now.
As always, the manual "flush cache" is useful in answering your final question - "Could it be something with the cache?" If and when you discover that it is, I will be disappointed but glad for the feedback.
Regarding the user who can edit unless you assign him the editor role for a category, my first thought is that he can already edit it due to some other role assignment, and that something about the category role assignment is triggering a db/php error. Yes, in theory it could be related to a corrupted cache, but I don't have any specific experience or suspicions regarding this issue.
This in the rare class of bugs that (for the sake of sanity and morale) I probably can't/won't pursue until I can log into as the symptomatic user and generate some diagnostic output. E-mail me through the contact form if you'd like to go that route.
Dare I ask what the other weird examples are? Oh, and what RS version are you running?
|
|
|
3:58 pm March 2, 2009
| joejanish
Member
| | | |
|
| posts 11 |
|
|
Thanks for the explanation.
Turned out that somehow, one of the user's posts wound up in the "Restricted" list — it wasn't assigned as such. As long as that one post was "Restricted", the user couldn't edit any of his other articles.
The solution was to make that one post unrestricted, and then it was deleted, and then everything went back to normal.
There were a few other random issues that may or may not have been due to user error, still trying to determine.
FYI I've disabled caching after reading through other people's posts in this forum, as we have more than 40 people contributing to our site and the consensus seems to be that having many writers can cause issues with the cache feature …. is that a correct assumption on my part?
Thanks again, this is an incredible plugin!
|
|
|
11:10 pm March 2, 2009
| Kevin
Admin
| | | |
|
| posts 2503 |
|
|
joejanish said:
FYI I've disabled caching after reading through other people's posts in this forum, as we have more than 40 people contributing to our site and the consensus seems to be that having many writers can cause issues with the cache feature …. is that a correct assumption on my part?
Actually, you're in a better position to answer that since my testing setup is not adept at simulating multiple concurrent users. I have added a significant bit of precautionary code since the last (and only) WSOD report that stemmed from a cache corruption. At least one other site with dozens of authors was running with the cache, last I knew (Daisy - can you confirm and/or offer any reports on recent results?).
I did correct one cache storage bug as recently as rc9.9227, but I'm not aware of any other issues, nor have heard any suspicious reports.
|
|
|
11:12 pm March 2, 2009
| Kevin
Admin
| | | |
|
| posts 2503 |
|
|
joejanish said:
As long as that one post was "Restricted", the user couldn't edit any of his other articles.
Hmm, that's a new one; I'll definitely look into that tomorrow.
|
|
|
10:27 am March 5, 2009
| Kevin
Admin
| | | |
|
| posts 2503 |
|
|
joejanish said:
Turned out that somehow, one of the user's posts wound up in the "Restricted" list — it wasn't assigned as such. As long as that one post was "Restricted", the user couldn't edit any of his other articles.
Can you reproduce that by temporarily restricting the one post again? I haven't been able to.
|
|
|
10:30 am March 5, 2009
| Kevin
Admin
| | | |
|
| posts 2503 |
|
|
joejanish said:
one of the user's posts wound up in the "Restricted" list — it wasn't assigned as such.
That might have been caused by a bug which was fixed in rc9.9227:
- BugFix : In Post/Page Edit Form, Restriction checkboxes showed wrong settings following a Bulk Restrictions edit, if cache enabled. Invalid settings were stored on Post/Page save if any other role settings were manually altered (since rc9).
|
|
|
11:10 am March 5, 2009
| joejanish
Member
| | | |
|
| posts 11 |
|
|
Issue hasn't occurred since, and it does seem possible that the issue occured after I did a bulk restrictions edit.
where is rc9.9227 ? is it available for download yet?
|
|
|
3:33 pm March 5, 2009
| Kevin
Admin
| | | |
|
| posts 2503 |
|
|
I've promoted rc9.9305 as the current stable release.
|
|
|
3:52 pm March 5, 2009
| joejanish
Member
| | | |
|
| posts 11 |
|
|
Thanks Kevin!
FYI I'm running RoleScoper on a production site with about 45 contributors who are writing daily, and often concurrently - BaseballDigest.com. Other than the few minor issues I've encountered, it seems to be doing what it's supposed to do. Not sure how many other sites using RS have that many contributors — I saw at least one with contributors in the hundreds — but if there's anything I can do to help in the way of testing, feedback, etc., let me know.(And yes a donation is on the way.)
Thanks again.
|
|