OK, I see that you get the errormessage from ther contemplate module, it, most liekly, has no knowledge of the drupalicioussummarise function (it is out of scope). The solution I'd go for is to create a module that contains drupalicioussummarise. Creating a module is quite simple, but I don't know if you've ever tried that and/or is proficient in PHP.
I see, makes sense actually :) I haven't tried creating my own module yet but I guess this would be a good chance. However, it sounds a bit frightening to create an entire module just for this single function? Even though it must be the best way of doing it.
Adding the function quick and dirty to the content template module must be a way as well, think I'm gonna try that first?
(you could try to keep it in template.php and "see what happens", but really theres no excuse for not embedding this function in a module, there's nor much to developing a module - the most confusing should be the manifest files where you have to adhere to a nameing convention, you could call it danskdynamit.module and in this module you'd just collect useful functions like this drupalicious_summarise). At Drupal Camp 2008 "Miki" did a pretty good introduction to modules, you can find it here: http://mikkel.hoegh.org/blog/2008/drupalcamp-2008-slides-and-code
Nice that you get answers on drupal.org, that is of course the correct place to ask questions, long live the community <3. Views is powerful, but it's terrible when you want to do "advanced" things, what you're trying to do would be really simple to do with regular SQL. I believe that Views 2 (for Drupal 6) shows the actual SQL it generates, that might be helpful in determining what's wrong with the query.
6 comments so far
OK, I see that you get the errormessage from ther contemplate module, it, most liekly, has no knowledge of the drupalicioussummarise function (it is out of scope). The solution I'd go for is to create a module that contains drupalicioussummarise. Creating a module is quite simple, but I don't know if you've ever tried that and/or is proficient in PHP.
10 months ago by kimbach
I see, makes sense actually :) I haven't tried creating my own module yet but I guess this would be a good chance. However, it sounds a bit frightening to create an entire module just for this single function? Even though it must be the best way of doing it.
Adding the function quick and dirty to the content template module must be a way as well, think I'm gonna try that first?
10 months ago by lyf
You can do that, even though it's a hack, but remember to remove the function from template.php
10 months ago by kimbach
(you could try to keep it in template.php and "see what happens", but really theres no excuse for not embedding this function in a module, there's nor much to developing a module - the most confusing should be the manifest files where you have to adhere to a nameing convention, you could call it danskdynamit.module and in this module you'd just collect useful functions like this drupalicious_summarise). At Drupal Camp 2008 "Miki" did a pretty good introduction to modules, you can find it here: http://mikkel.hoegh.org/blog/2008/drupalcamp-2008-slides-and-code
10 months ago by kimbach
Aha, that solved the problem without, well, problems. Thank you so much! For the link as well.
Now that we're at it, should you have the time, could you (or anyone else for that matter) please take a look at the following problem?
#comment-1221100" target="_new">http://drupal.org/node/343783#comment-1221100
10 months ago by lyf
Nice that you get answers on drupal.org, that is of course the correct place to ask questions, long live the community <3. Views is powerful, but it's terrible when you want to do "advanced" things, what you're trying to do would be really simple to do with regular SQL. I believe that Views 2 (for Drupal 6) shows the actual SQL it generates, that might be helpful in determining what's wrong with the query.
10 months ago by kimbach