The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
A proposal for a tool to debug pluggins
Hi Folks,
I have found it a real pain to debug pluggins. I use a debugger (PHP ED, which I highly recommend!) which allows me to step through the code with breakpoints, tooltip variable evaluation, and lots of great things! Programming without is like flying blind. Which is what it feels like when I'm working with Pluggin code since its eval'ed and can't be stepped through. What I'd like to see (but don't want to write at the moment because I'm not fully up to speed in PHP yet) is a pluggin to the pluggin system that when a switch is set ('debugpluggin') writes the pluggin code to a file and then calls the file . It would then send a false back to the hook call to defeat the eval call. I imagine the same file name could be re-used each time. They guy/gal who develops this handy tool would be a hero in my book and many other VB developers out there! Thanks for your consideration! Barry |
#2
|
|||
|
|||
Hi Barry,
This is working for me on our test server. I (temporarily) insert my plugin code inline into the vB code. That way it runs inline through the debugger and can be trapped and stepped as much as I want. Usually I comment out the hook call completely for this, but imagine that it would do just as we to make sure that your plugin just isn't installed or is disabled so that you don't have another copy of it firing in the hook eval. Hope this is helpful. Regards, -- Mike |
#3
|
||||
|
||||
Quote:
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|