Bug DBSEO Stop Words Not Working Properly

[neounix]

OBTW... since your last fixes on our site.. stop words are not working now.

I checked the settings and stop words are turned on; but they are not working at all.

For example:

http://our.site.com/shell-programming-and-scripting/237627-get-status-of-dd-running-in-background-job-post302866869.html#post302866869

containe the stopwords:

and
of
in

These stop words are all in our stop word list:

a
an
and
are
as
at
be
by
for
from
in
is
it
of
on
or
that
the
this
to
was
which
with

Also. see attached:

 

[bzcomputers]

This may have been an issue slightly before his last fix on your site. Because I'm also not seeing stop words being filtered anywhere on my site either. My last Beta8 download from here was almost 3 hours ago - so it had to occur in a change prior to that.

 

[neounix]

Thanks for confirming.

We checked and we are not seeing any stop words filtered at all on any of our URLs.

 

[bzcomputers]

It doesn't appear they are being filtered hear on DBTech either and I'm almost positive they were filtering at least some before. I'm sure he'll get on it as soon as he sees these posts.

He may have crashed for a few hours I know he's been at it quite awhile today.

 

[neounix]

Confirmed. Stop words still not being filtered on our site.

 

[neounix]

I just double checked are settings, and the stop word are being filtered OK on every setting except 0 (zero).

If we set "Maximum URL Keywords" to 5 or 7, it works as it should; but if we set it to 0, they do not get filters as they should. It was working before because we set them to zero.

You can use this setting to control the maximum number of keywords that will be used when generating your URLs.

Recommended value is either 0 (default) or a value between 5 and 7.

 

[Fillip H.]

EDIT: Nevermind.


PS: Nothing much is going to change between 3AM and 9AM...

 

[Fillip H.]

Upon further revision it does appear as if the previous change was indeed the fix after all.

 

[neounix]

Thanks! I see the "zero" setting is working as it should (again!)...

Thank you for fixing it and for the excellent follow-on and continuing support.