Why is the filter added with -50 and not +50? I understand +50 as the last... Is the documentation wrong? I'm not sure why it should be bad to run it first... So html corrector can followup...

Comments

Garrett Albright’s picture

Garrett Albright commented

-50? +50? Huh?

It should be okay to run HTML corrector after Pathologic, but rather than try to make some sort of whitelist of filters that are okay to run after Pathologic, I think it's just easier to tell people that it should always be the last one, since that's going to be correct 99% of the time. For example, if a site is using an input filter to transform BBCode or Markup or the like into HTML, Pathologic needs to run after that filter, or else it's not going to be able to find URLs in the input.

hass’s picture

hass commented

-50? +50? are the filter order weights... You may not see them with JS enabled :-)

Ok, bbcode example is good... Can you add the filter with weight +50 so it becomes the last by default? Today it defaults to the first in filter order...

Garrett Albright’s picture

Garrett Albright commented

Derp. Now I get you. Actually, in the code, I have the weight set to 65535, but I guess Drupal is trying to set 65535 as the default option in the menu, but can't since that option doesn't exist, so the first option gets selected instead. Okay, I should be able to get that in in the next update.

hass’s picture

hass commented

Sorry for confusing intro. :-)

hass’s picture

hass commented
Title: In most cases, Pathologic should be the last filter in the “Filter processing order” list. » Default “Filter processing order” to +50
hass’s picture

hass commented
Title: Default “Filter processing order” to +50 » Default “Filter processing order” to weight +50
Lloyd’s picture

Lloyd commented

This is still happening. There's no way to move the Pathologic filter to the bottom of the list per the instructions. The weight of the filter is +50 when it should be -50. And it seems like there's no way of manually updating that value.

hass’s picture

hass commented
Version: 7.x-1.4 » 7.x-1.x-dev
Component: Documentation » Code
Category: support » bug

You can drag and drop it. Changing status to bug.

Garrett Albright’s picture

Garrett Albright commented

I haven't created a new release with the bug fix yet. I've been stupid busy and neglecting my contrib projects… sorry. I'll try to get a new one out soon.

Garrett Albright’s picture

Garrett Albright commented
Version: 7.x-1.x-dev » 7.x-2.x-dev
Status: Active » Fixed

Fixed soon in the next 2.x beta.

Garrett Albright’s picture

Garrett Albright commented

Fixed soon in the next 2.x beta.

Status: Fixed » Closed (fixed)

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