Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Not sure if this has been fixed, but in the 6.x-1.8 version I was having issues with the span tag breaking my apachesolr links.
Attached is a patch to fix.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | Screenshot of Development Block | 2.98 KB | mattez |
| devel_themer_nl2br.patch | 470 bytes | jason ruyle |
Comments
Comment #1
jason ruyle commentedmeant to have it be 18 not 8
Comment #2
Kai commentedThis patch doesn't work :)
warning: Wrong parameter count for nl2br() in .../sites/all/modules/devel/devel_themer.module on line 507.
devel_theme_call_marker function has to return an array with to fields: Line 235 list($prefix, $suffix) = devel_theme_call_marker
nl2br() doesn't return an array and just let this term be true: if ($start_return != $start_prefix ...
Comment #3
moshe weitzman commentedComment #4
effulgentsia commentedYeah, the use of spans does cause a bunch of problems, and fixing it isn't a small task. There's an issue for it: #425716: Use comments instead of spans to markup theme calls, which will hopefully see some energy put into it.
In the meantime, people get around it by having "Theme developer" disabled most of the time, and only enabling it when needing to do something specific: there's a handy "Disable/Enable Theme developer" link in the "Development" block provided by the devel module to do just that.
Comment #5
mattez commentedI have got last dev version of devel & devel_themer and there is no "Disable/Enable Theme developer" link in Development" block! WTF? :>
Comment #6
mattez commented+ screenshot [logged as user uid 1 with permissions]
Comment #7
alanburke commentedThis appears to be a side issue of spinning off devel_themer into its own module.