Since I "updated" to v416, previously selected "Never Show Again" items are showing again. I reselected them as "Never Show Again", but they still show on subsequent scans. geez :?


Same deal with RegSupreme Pro v.416.

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

Nope;

1. The "Never Show Again" works in jv16PT v.413, and RegSupremePro v.414 and doesn't stop working until I "update" to the v.416.


2. I don't know what you'd consider "very large" but my SuperRegIgnoreList.dat is 5k and contains 44 entries, and the exact same file worked just fine before "updating".


3. The entries I want ignored are in the SuperRegIgnoreList.dat, it's just that the RegCleaners aren't ignoring them.


The Never Show Again worked just fine until it was "fixed". Maybe it should be unfixed.

JRd1st wrote
Nope;

1. The "Never Show Again" works in jv16PT v.413, and RegSupremePro v.414 and doesn't stop working until I "update" to the v.416.

tullik wrote
The "fix" probably causes what you reported.

Yep!

JRd1st wrote
2. I don't know what you'd consider "very large" but my SuperRegIgnoreList.dat is 5k and contains 44 entries, …

piaqt wrote
… So why does regcleaner take over an hour to run in agressive mode? I'm using v. 1.7.0.413.

piaqt wrote
I cleared my superignore.dat file. (was 477kb)

Guess what? Regcleaner took only 105 seconds in aggressive mode! …

I think piaqt's qualified as "very large." Mine is 0 B unless I'm testing. I prefer the Ignore words tab since a simple string can cause scores of lines not to show.

JRd1st wrote
… and the exact same file worked just fine before "updating".


3. The entries I want ignored are in the SuperRegIgnoreList.dat, it's just that the RegCleaners aren't ignoring them.

Unfortunately, the bugs caused the feature not to work correctly -- also, see the added note in my prior post.

JRd1st wrote
The Never Show Again worked just fine until it was "fixed". Maybe it should be unfixed.

tullik wrote
The "fix" probably causes what you reported.

Yes … it should be either unfixed or corrected …

13 days later

These issue should now be fixed, thank you for reporting. The fixed version will be released within two weeks.

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.