Get a WSOD due to:
PHP Fatal error: Call to undefined function dsm() in modules\views\includes\cache.inc on line 123
This function is called from the following files/line #
[C:\WWWRoot\drupal\sites\all\modules\views\includes\cache.inc]
Line 56 : dsm('Views data build time: ' . (microtime() - $start) * 1000 . ' ms');
Line 83 : dsm('Views plugins build time: ' . (microtime() - $start) * 1000 . ' ms');
Line 123 : dsm('..');
[C:\WWWRoot\drupal\sites\all\modules\views\includes\handlers.inc]
Line 60 : dsm("missing join: $table $primary_table");
[C:\WWWRoot\drupal\sites\all\modules\views\includes\view.inc]
Line 185 : dsm("Init_style: $this->style_plugin");
[C:\WWWRoot\drupal\sites\all\modules\views\views.module]
Line 294 : dsm("Missing handler: $table $field $key");
each of these lines needs to be preceded by:
if (module_exists('devel'))
Note that in includes/cache.inc lines 56 and 83 do have this.
Comments
Comment #1
catchhttp://drupal.org/node/95897
;)
Comment #2
kwikone commented1) YES
2) YES (many years development experience)
3) Comfortable enough that if I report a bug I also do what I can to provide a fix (with what limited time I have available to me - since I do have to concentrate on my money making activities first), such as above, or, with a patch file.
Comment #3
merlinofchaos commentedinstall devel.module -- dsm() outputs debugging information.
(That makes me worry a bit about item (1) above)
Comment #4
dman commented<mock class="Nelson">
hahhah!
</mock>
A drupal developer should really recognise dsm() and probably already have the devel.module available.
Nice try tho ;-)
(I saw that dire warning posted, and wondered if things were really that dangerous with the code. Obviously so.)
Comment #5
kwikone commentedmerlin...
and others...
Yes, I recognized dsm as being from the devel mod.
I was testing as a 'normal' (devel turned OFF). And, in my opinion, marking an issue as won't fix when the problem (IF NOT FIXED) means that this particular development branch is a dead issue since if the problem is not resolved then no 'normal' people will be able to get it working (or devel needs to be a module requirement)
Comment #6
merlinofchaos commentedYea, dman, they are. There's no UI to speak of (there's a tiny little bit now but not enough to do anything) and I'm not being particularly careful about my checkins; I'm actually checking in, at this point, more as a form of backup, so that I don't lose my work should something untoward happen.
So I'm not being careful at all about my dsm() calls, and I don't want to have to be. I put that warning up to keep people who don't know what they're doing from trying to install it; apparently the update status module was telling people to use it but all it can do, right now, is make life very bad for you if you're not installing it to help with development. At this time having devel.module installed is a requirement, and I'm not excited about having to spell that out.
I'm not sure why kwikone is harping on this issue, but it's really irritating me that my time is being wasted on this.
Yes, there are raw dsm() in the code. Deal with it. This is development code. I'm working on it. It doesn't work yet. That's the current state of affairs. If you're going to report issues, please, for the love of whatever deity you give two shits about, please please please make them for actual problems, and not stupid stuff like this.
If this kind of thing keeps up, I will just wipe HEAD on d.o and put this stuff into a private CVS somewhere instead. That's not an optimal solution for me; that creates yet more work and reduces visibility but I don't have a lot of patience for this stuff.
I am not wasting more time on this issue. This is won't fix. Change it and I'll just delete the issue. I'm not kidding.
Comment #7
kwikone commentedI hope that you get some relaxation as you seem to be uptight :-). At the least you could have marked as POSTPONED. In that way any others who happen to see it would know for certain one issue which could cause them problems (dire warning aside :-) ) and that it would eventually be resolved. Marking it as won't fix means just that - the issue will always remain.