Posted by dorien on May 12, 2008 at 10:03am
Jump to:
| Project: | Content Injector (formerly AdSense Injector) |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I have a few conten types without body. So the adsense won't display...
Comments
#1
In /admin/settings/adsense_injector at the Node body ad insertion option set "Minimum node body word count:" to be 0 and you're all set.
Cheerio.
#2
Sorry, that is assuming that you have a Body field" in the content type that you are talking about. Otherwise your post is likely a double of this one where there is some interesting discussion: "A. injector don't show ads if CCK without body field is used" http://drupal.org/node/151604
#3
Moving to 6.x dev, since 5.x is no longer supported.
This is a feature request, since the module is known not to work without a node body.
#4
+1 as instructed
#5
@Stomper:
Thanks for the +1 vote.
@All:
If anyone is interested, I've added a poll to my project homepage. What SINGLE new Adsense Injector feature is most important? Feel free to visit and register your opinion...
#6
+1
#7
I've tried pasting in the PHP AdSense code from the Adsense module into the tpl.php of the content types I want the ads to show in, it still does not work. The content types do not have a body field, only custom CCK fields.
#8
Is it possible that there is a conflict between the core Adsense module and Adsense Injector? If I go with the inserted PHP code as suggested by Adsense core, does that mean I still need Adsense Injector enabled too?
#9
+1
#10
+1
#11
+1
#12
+1
#13
+1 for biblio fields
#14
offcourse +1
#15
+1, greetings, Martijn
#16
+1 : created an online drupal account for that purpose as it's such an issue . . .
#17
Well, seems to be the most popular feature request. Before I try to tackle this, we should work up some kind of mini-spec.
I think at a minimum, the module should allow admins to specify the CCK field name to be used instead of the standard node body.
Is it truly necessary to allow specifying this on a per content type basis, or can it be global? It's starting to look like it would be useful (though complicated) to be able to specify everything per content type:
But this would become pretty unwieldy in the admin settings interface, so that's going to be a pretty big change.