Can someone confirm this error:

1) Install an enable the Module Disable Message
2) Within the Disable Message Module Settings, just enable filtering (no other settings) or leave default settings (if filtering is already enabled)
3) (Clear or rebuild cache/s and) logout
4) Try to login with false password or similar, then, no message, f.e. "Unrecognized username or password. Forgot your password?" is shown

Seems to me, that after enable filtering such important system-warnings are per default filtered as it not should be (here all login/account-form-related system warnings)?

If so, the module isn't usable (especially for more comlpex sites, f.e. if you have to told your customer what exactly is wrong with his input).

Page and user level filtering options are no option, if you have a sidewide warning, you must filter.

Is this fixable?

Comments

Rainer F. Gottlieb created an issue. See original summary.

v.belous’s picture

I have the same problem...

v.belous’s picture

Assigned: Unassigned » v.belous
v.belous’s picture

Status: Active » Needs review
StatusFileSize
new0 bytes

This bug related with checking users permission in disable_messages.module line 124
In this line exists checking on the user permissions to view the messages of the type "error" or these permissions were planned to be configured in the module itself

v.belous’s picture

StatusFileSize
new1.55 KB
rainer f. gottlieb’s picture

I installed the patch and it works now as aspected for the case I described initially, means, the Warning "Unrecognized username or password. Forgot your password?" is shown know. Thank You verry much v.belous for this patch.

nkoporec’s picture

Assigned: v.belous » Unassigned
Status: Needs review » Reviewed & tested by the community

Tested the patch and it fixes this issue.Great work!
Marking as RTBC.

milos.kroulik’s picture

Works fine for me.

  • zyxware committed 2b024d0 on 8.x-1.x authored by v.belous
    Issue #2934067 by v.belous: No more form-warning-messages at all, after...
zyxware’s picture

Status: Reviewed & tested by the community » Fixed

Applied the patch.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.