[development] How do you fix this, in theme.inc or the module?
Carl Mc Dade
carl_mcdade at yahoo.com
Mon Feb 19 17:34:41 UTC 2007
Did I miss something or is my writing? In the first line of my post I explain that I am updating a module to 5.1. So my post definately belongs here. I am not looking for support but clarity on an issue that was posted. Since that issue came up under my "development" of a 5.1 module.
I am at a total loss as to if the other items you posted about have anything to do with the problem I was having. But if you think it is helping someone I guess it makes sense.
I am pretty much aware of the techniques for debugging. But that was not the question. What I wanted to know was if this issue was resolved by 1) a patch to the core 2) unresolved 3) could be avoided by adjustments in my module code.
In this case it was the modules code. I think a better reply would have been "can you post your code" since I forgot to do so.
But it is done and fixed now so I am on to the next row of code.
Boris Mann <boris at bryght.com> wrote: On 2/19/07, Carl Mc Dade wrote:
> I am working on a module update and there is a problem with theme.inc
> throwing an error on lines 552+
> There are lots of threads and issues about this but none of them are
> What exactly is causing this and what is needed to correct the module so
> that it works with D5.1? Is it in fact something in the modules or is it
> something in the core that needs to be accomodated?
> PHP 5.2 mysql5 Apache 2 windows2000
OK....so, this is pretty much a support question, not a development
question. The proper way to follow up would be in the issue thread.
Only by me actually clicking through and reading the whole thread did
I find what it is about.
A better title would have been
"Spam module causes fatal error in theme.inc"
In fact, that's a great title for an issue tracker item for the spam module.
* it's an issue with the spam module and need to be fixed there
* post an issue in the spam module issue tracker
* this is essentially a support question, and should be directed to
the support mailing list (who will tell you to contact the spam
If it's your own module, then use standard debugging techniques to
figure out where your code is causing a problem.
For a gut check on whether something belongs on dev. vs. support -- if
you are including your system stats and/or asking "how do I fix
this?"....it's likely support.
San Francisco 415-367-3595
Carl Mc Dade
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development