[Solved] Force Reason in Last edited

[Stratis]

No it is not. Even if it is, i have Exempt Usergroups to none. That means what ever situation it must not save edited post with less than 10 characters as i have in settings. For now i use the previous xml you send and its ok.

Thank you

[MarkFL]

Originally Posted by Stratis

No it is not. Even if it is, i have Exempt Usergroups to none. That means what ever situation it must not save edited post with less than 10 characters as i have in settings. For now i use the previous xml you send and its ok.

Thank you

Even if you have "Exempt Usergroups" set to "None," if your usergroup permissions are such that "Show edited by note on edited messages?" is set to "No" in the "General Permissions" section of the Usergroup Manager," you will always be exempt. Otherwise you will be subject to the requirements of this product.

To me, it simply makes no sense to require a user to give a reason when their permissions allow them what we call at MHB, the "Ninja edit." We allow global mods/admins the ability to edit posts without showing the post was edited (we primarily use this on the important posts of each other, such as announcements/tutorials to correct spelling/grammar errors), and if we were to require an edit reason, this would take away this ability (if "Exempt Usergroups "was set to "None").

I feel the usergroup permissions should supercede the actions of this product...however, I will add a setting in this product that will give you a choice about whether the usergroup permissions take precedence or not.

[Stratis]

Sorry for not understanding well all you wrote above(my english problem)
but whatever when users put reason even if it is less than 10 character, post can be saved. Is this right? Option in modification "Minimum Characters" does not take effect in all situation we have in vbsettings?

Any way don't bother for anything else, i will find the way as it is.

Thank you Mark

[MarkFL]

Everything works exactly as it should in Firefox...however Chrome fails to execute the mouse events properly (known but as of yet unaddressed bugs), and I simply don't have any more time at the moment to squander on browser failure workarounds.

[Stratis]

Yes, yes its not a big deal.

[MarkFL]

Since Chrome is broken with respect to the needed mouse events, the best workaround here is to simply disable the quick edit if Chrome is being used, which I have done in this latest update.

[MarkFL]

I devised a workaround to overcome Chrome's shortcomings, and published the product here:

Require Edit Reason