How do you fix this, in theme.inc or the module?
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 conclusive. http://drupal.org/node/111517 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 TIA Carl Mc Dade ____________________________ Web Developer --------------------------------- Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get things done faster.
On 2/19/07, Carl Mc Dade <carl_mcdade@yahoo.com> 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 conclusive.
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. Short answer: * 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 maintainers) 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. Thanks, -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com
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@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 conclusive.
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. Short answer: * 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 maintainers) 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. Thanks, -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com Carl Mc Dade ____________________________ Web Developer --------------------------------- TV dinner still cooling? Check out "Tonight's Picks" on Yahoo! TV.
Unless I'm confused about this, the support mailing list is for discussion pertaining to developing *with* Drupal (what you are doing with your module), while the development mailing list is for discussion pertaining to the development of Drupal itself (ie. core). So with that in mind, while you are developing a 5.1 module, it is a type of development for which questions are better suited in support. William On 2/19/07, Carl Mc Dade <carl_mcdade@yahoo.com> wrote:
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.
If this is true then someone should speak up and I will switch mailinglists immediately. But if not then I do not want to further complicate things by taking a posting the same type of questions again to the wrong mailing list. So what is the rule? Where do questions about contrib module development go? William Smith <william.darren@gmail.com> wrote: Unless I'm confused about this, the support mailing list is for discussion pertaining to developing *with* Drupal (what you are doing with your module), while the development mailing list is for discussion pertaining to the development of Drupal itself (ie. core). So with that in mind, while you are developing a 5.1 module, it is a type of development for which questions are better suited in support. William On 2/19/07, Carl Mc Dade <carl_mcdade@yahoo.com> wrote: 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. Carl Mc Dade ____________________________ Web Developer --------------------------------- Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains.
On 2/19/07, Carl Mc Dade <carl_mcdade@yahoo.com> wrote:
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.
The issue linked indicated that it was in the spam module -- I tried to help you by spending my time reading it and reposting that information.
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.
No. Posting your code here is not appropriate -- this list is not for debugging your code. -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com
Sounds like questions of this the type I need answered should be restricted to the online forum. Is this true? If so I will get out of your hair and continue my endeavours there. Boris Mann <boris@bryght.com> wrote: On 2/19/07, Carl Mc Dade wrote:
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.
The issue linked indicated that it was in the spam module -- I tried to help you by spending my time reading it and reposting that information.
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.
No. Posting your code here is not appropriate -- this list is not for debugging your code. -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com Carl Mc Dade ____________________________ Web Developer --------------------------------- Don't pick lemons. See all the new 2007 cars at Yahoo! Autos.
On 2/19/07, Carl Mc Dade <carl_mcdade@yahoo.com> wrote:
Sounds like questions of this the type I need answered should be restricted to the online forum. Is this true? If so I will get out of your hair and continue my endeavours there.
On 2/19/07, Carl Mc Dade <carl_mcdade@yahoo.com> wrote:
If this is true then someone should speak up and I will switch mailinglists immediately. But if not then I do not want to further complicate things by taking a posting the same type of questions again to the wrong mailing list.
So what is the rule? Where do questions about contrib module development go?
We use this list to coordinate the core development of Drupal as well as issues which affect the future direction as a whole. Quick questions like "X doesn't work, how do I fix?" are not appreciated (and maybe better for support or #drupal). You are welcome to email the list with suggestions on approaches, etc. -- BUT -- do your homework first, explain what you've tried, etc. -- i.e. we strive for high signal to noise. Thanks, -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com
Nevermind, Seems like I fell in for a namespace conflict with the new links syntax. Carl Mc Dade <carl_mcdade@yahoo.com> 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 conclusive. http://drupal.org/node/111517 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 TIA Carl Mc Dade ____________________________ Web Developer --------------------------------- Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get things done faster. Carl Mc Dade ____________________________ Web Developer --------------------------------- Never Miss an Email Stay connected with Yahoo! Mail on your mobile. Get started!
participants (3)
-
Boris Mann -
Carl Mc Dade -
William Smith