Fixing false positives (UI indicates results found when there are none)

[ianray42]

First and foremost -- love the app, use it a TON in filling requests.

Some of the things I search for are pretty obscure, so I am used to getting 0 results, even with my fairly large net of selected filters. Sometimes, I get that coveted green box and get excited, only to find out it was simply a parsing error.

~ SO ~

I started to investigate some of the errors and believe I have fixed them, so I thought it would be good to start a thread where we share the small userfixes we've discovered, potentially to be included in future releases while saving the glorious devs some time. :)

I'll start:

• Knaben Database (as of v17.6 of IMDb_Scout_Mod.user.js)

  • IMDb-Scout-Mod/IMDb_Scout_Mod.user.js

    Line 1458 in 762b59f

    'matchRegex': />Total hits : 0</},

  • IMDb-Scout-Mod/IMDb_Scout_Mod.user.js

    Line 1462 in 762b59f

    'matchRegex': />Total hits : 0</,

  • 'matchRegex': />Total hits : 0</}, --> 'matchRegex': />Total hits: 0</}, (removal of space before colon)

[Purfview]

Sites constantly change their code, so, various discrepancies arise in time.

About saving time: just do PR [Pull request] with fixes per site.

[Purfview]

To do PR is simple: Press on the script > Press Edit.
That will create a fork for you automatically, and after your edits GitHub should ask if you want to do PR, then it should be obvious what to press next.

[ianray42]

Okay, no worries -- I will just do that.