Closed (fixed)
Project:
Pathologic
Version:
6.x-1.1-beta13
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Dec 2008 at 10:21 UTC
Updated:
27 Aug 2009 at 17:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
webel commentedAmendment:
href="project/thing" > href="/drupal/project/thing#"
BTW I tested switching Pathologic input filter on and off and isolated other input filters, too.
Comment #2
jjalocha commentedI tested this with Firefox 3.0 and Opera 9.27, and it doesn't jump to the bottom of the page, here. So it's probably a browser specific behaviour.
But I still agree, it looks weird, and I would be glad if we could get rid of this unnecessary element.
Comment #3
Garrett Albright commentedI'll try to look into this on the weekend (and I really mean it this time… maybe).
Comment #4
Garrett Albright commentedOkay, I got a chance to look at this tonight. And yeah, it's broken.
Le sigh… It seems like every time I think I've got this right, it turns out I've just broken something else and not noticed it yet. And truth be told, I don't really use this module much myself, so I'm rarely the first one to notice it.
webel and jjalocha, could you try replacing pathologic.module with the attached file and letting me know if it fixes things? (You'll have to edit your nodes and/or dump your cache before Drupal will re-run input filters on your content again.)
Comment #5
webel commentedHi,
The patch doesn't seem to work at all.
I downloaded and installed the pathalogic.module.
Afterwards EVERY page opened as a single line of text:
project/drancing/software
(which is just one alias I am using, Drancing is one of my R&D projects).
The page source showed no HTML, just that line of text, and always the same.
I tried a diff of the old .module and the patch .module, however could not see why.
I replaced the patch with the original and it worked again (but of course still with the # problem).
FYI am using Firefox 3.05 and Safari 3.1.2 on Mac OS X 10.5.4.
Comment #6
jjalocha commentedExactly the same problem here. Wherever try to navigate, I only get a text-page with one pathname '../top-one', 'top-one' being my main page.
The leading '../' is probably related to multi language setup here. I am using language prefixes for all languages.
Comment #7
Garrett Albright commentedArgh, I'm so dumb. I forgot to delete a testing line. Please try deleting line 164, which looks like:
and try again.
Comment #8
jjalocha commentedThanks, that fixes it! I tested it in a multilanguage set-up, with the following pages:
* top-page (default prefix empty)
* top-page/sub-page
* en/top-page (default prefix en)
* en/top-page/sub-page
As expected, it doesn't work correctly with translated pages:
* de/top-page
* de/top-page/sub-page
But it doesn't break anything. It just directs all links to the default language, which is the same behavior we had before applying the patch.
Thank you, Garrett, for the help!
Jerzy
Comment #9
webel commentedYes, that seems to have fixed it, one less worry, thanks for your prompt attention, Webel
Comment #10
Garrett Albright commented