Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Thanks for this module.
I get this error when i enable Theme developer with Bootstrap theme (v. 7.x-3.1):
Fatal error: Unsupported operand types in sites\all\themes\bootstrap\templates\system\html.vars.php on line 44.
From the comment of the maintainer of Bootstrap:
It sounds like some other module is screwing with these arrays and perhaps flattening them (into strings).
in Fatal error: Unsupported operand types.
i assume that this belongs to the Theme developer issue queue as a feature request for compatibility with this theme.
Comment | File | Size | Author |
---|---|---|---|
#9 | M9X9NKVX@K$$1)M`BE$)YQ7.png | 4.53 KB | kk3829099 |
Comments
Comment #2
EmanueleQuinto CreditAttribution: EmanueleQuinto commentedThe issue is very serious indeed. I was able to get rid of all the bootstrap errors adding lot of
isset
here and there but the final result is a blank page with "Skip to main content".As the issue disappear once you disable
devel_themer
I have the feeling that boostrap developers didn't use the module during the development cycle and given that the last update to 3.1 was quite impressive it could be tricky to find an easy solution. Too bad.Comment #3
vdewit80 CreditAttribution: vdewit80 as a volunteer commentedCan you share your solution?
Comment #4
cabita CreditAttribution: cabita commentedThe solution #2 was useful for me. Thanks.
Comment #5
markhalliwellNo, I do not use this module to "develop" Bootstrap. I haven't used it since D6 and I stopped using it because it was never really that stable or predictable. I use my IDE (PHPStorm) and Xdebug and manually step through the theme hook invocations as they're being called.
I get that some may find this module useful. However, and IMO, I find it's really nothing more than a mere hack to expose things that:
a) should already be well documented (e.g. the theme system itself, not necessarily the Bootstrap base theme) and
b) can be done is in various other ways that are more suitable than this "solution"
Regardless, I do wish to make it quite clear that I do not, nor will I ever, actively support this module since their are better and more stable ways to "debug" a theme.
---
That all being said, it sounds to me like the problem (with this module) has something to do with it not initiating a theme properly or, at the very least, including all the files provided with a theme hook to properly preprocess it (e.g. iterating over and including each
$hook['includes']
file which the Bootstrap base theme takes advantage of).Comment #6
dzy CreditAttribution: dzy commentedis there simple solution for display theme hook and tpl file?
i really need this to learn drupal theme development.
i had issue about alter html output for specify field in specify form ( bootstrap) inline, i want unwrapper all unnecessary div and keep html output same as bootstrap structure. that means radio type field's input element should inside label markup.
Comment #7
kenorb CreditAttribution: kenorb commentedThe same here when using with Bootstrap.
Comment #8
kenorb CreditAttribution: kenorb commentedBacktrace (copy and unwrap it for a better view):
Comment #9
kk3829099 CreditAttribution: kk3829099 commentedI have the same issue and no solution
Comment #10
ipwa CreditAttribution: ipwa commentedJust add this to your settings.php
$conf['theme_debug'] = TRUE;
Comment #11
bmango CreditAttribution: bmango commentedI tried the solution in #10 but it didn't work for me.
Comment #12
bmango CreditAttribution: bmango commentedMy bad, I misunderstood the comment in #10. Setting
$conf['theme_debug'] = TRUE;
provides an alternative way to see theme information through the source code, it doesn't fix this issue.Thanks to ipwa for the tip!
Comment #13
Martyshake CreditAttribution: Martyshake commentedI have the same issue and can't access the interface. I am new to programming. Can you tell me step by step what I can do to restore the interface?
I deleted Theme Developer manually from the modules using file manager, but it did not help to restore the access. I suppose I can delete everything and reinstall Drupal (I haven't made much progress and won't lose much), but as a learning experience, can you tell me what should be done to fix it?
Comment #15
paean99 CreditAttribution: paean99 commentededit: undoing revision https://www.drupal.org/node/2613218/revisions/view/9449137/9449157 because summary of this issue was accidentally deleted.
Comment #16
longtom CreditAttribution: longtom as a volunteer commentedI just got this error, also. It happened because I upgraded the theme from Bootstrap 7.x-3.0 to Bootstrap 7.x-3.5, although I did not get the error for weeks until I enable the devel_themer module on dev.
While I understand the justifications for this error, I might respectfully suggest that the final solution that this module and this theme can not play well together is not a great solution for Drupal as a whole.
When the average Drupal user upgrades the theme, and gets a blank screen, they are probably not going to know what to do (turn on PHP errors, search the issue queues down to the Bootstrap theme and the devel themer module, drush disable theme developer, use other debugging tools, and then find that the theme developer will not support the module, which is an often recommended module for investigating an already complex theme layer).
Again, I understand the justification, but the message to the end user is
'Your production Drupal installation may stop working after an update for reasons that are not clear to the average user. Use at your own risk.'
Comment #17
youssef.aazri CreditAttribution: youssef.aazri commentedI've the same error, i get rid of it by disabeling devel_themer module.
Comment #18
sillo CreditAttribution: sillo as a volunteer commentedUhm. Is that a solution? Just asking.. Because disabling the module that causing the error doesnt seem to be a solution.