I just upgraded from Pathologic 1.x to 2.x, and I've noticed that wherever I link to files in my local Drupal instance's /sites/defaut/files directory, the paths are being modified invalidly to point at sites/default/files/sites/default/files/(File).

Specifically, I have a file located at:
http:// localhost/company_name/test/sites/default/files/logos/image.jpg

which is now filtered to:
http:// localhost/company_name/test/sites/default/files/sites/default/files/logos/image.jpg

I'm using the following base paths:

  • http:// localhost/company_name/test/
  • /company_name/test/

Has anyone else experienced similar issues after upgrading?

Comments

ioanmar’s picture

Yes, I'm experiencing the same exact issue.

sense-design’s picture

Same issue here

sense-design’s picture

Priority: Normal » Critical

Pushing this critical because all my images are not visible any more

dwalker51’s picture

I also have this problem....

stevep’s picture

same issue, could not find work around.

Reverted to 1.4, site again fully functional.

ioanmar’s picture

I had to deactivate Pathologic for Full HTML, which was the most common format I used for blocks containing images. I had to rewrite the broken paths, as I was mainly using Pathologic to avoid broken images from local to online server transitions.

Any suggestions from the maintainers of this super popular module?

Garrett Albright’s picture

Arg. Thanks for the notifications, all. Guess I should have had one more beta before making a full 2.0 release.

I'll take a look at this and try to get a fix out before the end of the weekend. Sorry for the trouble… big fail on my part.

Garrett Albright’s picture

Status: Active » Closed (fixed)

Okay, the fix to #1672430: File paths prepended with ?q= when clean URLs are disabled was what was causing the problems here. Oddly, my automated tests didn't catch it - they were passing regardless. I've backed out the fix and made another release, since it was clearly causing more problems than it was solving, but that means that that other issue is still in need of a smarter fix - and some smarter tests.

At any rate, please nab the latest release and give it a try. I again apologize for the flub.