[code][elema@localhost ~]$ df -h
File system Dim. Usati Disp. Uso% Montato su
/dev/sda1 12G 4,0G 7,3G 36% /
/dev/sda6 902G 10G 892G 2% /home
/dev/sr1 13M 13M 0 100% /media/Alice MOBILE
[/code]
This piece of code broke geshifilter parsing, but bbcode module parse this text correctly just after geshifilter.
I think that the problem is located here: "[code][elema@localhost ~]"
Any hints ?
Thanks a lot and thank you so much for this great module.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | 1010216-square-bracket-confusion-03.patch | 2.24 KB | soxofaan |
| #9 | 1010216-square-bracket-confusion-02.patch | 1.3 KB | soxofaan |
| #6 | Screen shot 2011-01-08 at 11.42.24.png | 82.61 KB | soxofaan |
Comments
Comment #1
paolomainardi commentedI made another test:
< code >[elema@localhost ~]$ df -h
File system Dim. Usati Disp. Uso% Montato su
/dev/sda1 12G 4,0G 7,3G 36% /
/dev/sda6 902G 10G 892G 2% /home
/dev/sr1 13M 13M 0 100% /media/Alice MOBILE
< /code >
The same text but with standard tag < code > works like a charm (i've just put spaces in order to not be parsed by editor)
Comment #2
soxofaan commentedcan you give more info on the input format: which other filters are active and in which order?
Comment #3
paolomainardi commentedDear soxofaan,
Of course:
HTML Filter
Quote
GeSHi filter
BB Code
Smileys filter
URL Filter
HTML Corrector
All activated and in this order.
Comment #4
soxofaan commentedThanks,
does it work when you disable other filters like "Quote", "BBCode" and/or "Smiley filter"?
Comment #5
paolomainardi commentedDear soxofan,
Sadly not, it is not parsed anyway, but only using "bbcode" like tagging.
Comment #6
soxofaan commentedHi,
I just tried it and there is indeed a problem with
[code][elema@localhost ~].An easy workaround for the moment is to put a new line between
[code]and[elem....see screen shot in attachment
Comment #7
paolomainardi commentedYes, I'm just fixing putting a space between the 2 square brackets.
Thanks a lot for the info.
Comment #8
paolomainardi commentedDear soxofaan,
Do you have some news about this bug ? I didn't have much time to trying to fix the problem.
If you don't have time i'll try to make a patch within this days.
Thanks a lot for your precious work.
Comment #9
soxofaan commentedHi,
I started working on it, but only got time to write a test for it
see attachment
Comment #10
paolomainardi commentedThat's wonderful.
Please tell me if you need support, in the meanwhile i'll try to code a patch.
Comment #11
soxofaan commentedHi Paolo,
I hope you didn't burn a lot of effort on the patch already, because I guess the regular expressions involved here are not easy on the eyes :)
Anyway, I picked up my work in #9 a bit an I think a small tweak to a regular expression should do the trick.
See attachment.
Comment #12
paolomainardi commentedWonderful, it works like a charm.
Thanks a lot for the patch :)
Comment #13
soxofaan commentedcommitted for 6.x-1.x: http://drupal.org/cvs?commit=493796
to be ported to 7.x-1.x
Comment #14
soxofaan commented7.x-1.x too
http://drupal.org/cvs?commit=493800
Comment #16
yukare commentedI have this same issue on drupal 8, now this is the only failing test. Is possible to work arround it by using language, eg [code language="ini"], but since it works on drupal 6 and 7, must be something missing in upgrade.
Comment #17
yukare commentedComment #18
yukare commentedIt is working and the test pass, just forgot to close this.