Description
Hitting Preview 10 times on a default installation triggers the edit surge protection (10, 120). In my opinion this is a mistake, although not a severe one, it surprised people, if they try out e.g. some layout problem with previewing.
Steps to reproduce
See above.
Example
Details
MoinMoin Version |
1.5.4 |
OS and Version |
linux |
Python Version |
|
Server Setup |
|
Server Details |
|
Language you are using the wiki in (set in the browser/UserPreferences) |
|
Workaround
One could change the 'edit' surge, but I believe it´s useful, if someone really hits 'edit' so often.
Until there is a real fix (making preview not count as edit), I relaxed the default limits for edit a bit. Will be in 1.6.2.
Discussion
I got similar complaints from a user who edited a lot of pages rather fast (as he copied the same macro into all of them). As a result I did increase all the surge settings by a factor 10. What I'm missing is a "big switch" to turn off the whole surge protection, as it is not really needed in a "friendly" intranet situation (no bots, no spiders, no spammers, just docile users who should know what they do ) -- RobertSeeger 2006-08-15 16:41:46
The big switch will be in next release, by just setting surge_action_limits = None.
It seems that I missed the decisive point when discribing the bug: "edit" protection is usefull, but "preview" protection is nonsense. The problem is that previewing triggers edit. -- TobiasPolzin 2006-08-21 10:37:20
Well, this is no bug. It just behaves as configuration tells. We could raise the default limit for edit, but then spammers (doing lots of edits in little time) wouldn't get locked out. Of course spam protection keeps them out if the pattern is already known, but not if it is not known... -- ThomasWaldmann
Moin should differentiate between preview and actual editing. -- AlexanderSchremmer 2006-08-21 10:52:19
Totally agree with AlexanderSchremmer - and that's the bug IMHO. -- Soeren Staun
Plan
- Priority:
- Assigned to:
- Status: