Two feature suggestions (Node specific injection settings; Fine grained teaser control)
| Project: | Adsense Injector |
| Version: | 6.x-2.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Your module, along with the AdSense module, have really made my life easier! I have two suggestions for future consideration:
1. Node Specific Insertion Points. It would be nice for each content type (blog, page, story) to have their own injection option. e.g. On pages I may want an advert inserted at the top and bottom, but on blog pages I only may want them on the bottom.
2. More control over placement in teasers. For example on the homepage I would really like to have an advert right after the first teaser ONLY. The AdSense tips and suggestions do give some examples of why this is helpful for blogs and forums. Being able to insert adverts after the first and fourth teaser (or whatever fits your site) would add a lot of flexibility.
#2 would be especially relevant because Google limits you to 3 adverts per page.
Thanks for the great module!
#1
Thanks for the kind words and suggestions (yes, I like the module too, and it has so many interesting capabilities even in its current crude form.)
Per-content-type configurations: I've shied away from any per-content-type or per-taxonomy-term behaviors mainly because configuration becomes a bit of a nightmare - just the user interface for configuring all the content types tends to be a bit of a hassle. I've not yet come up with an easy-to-use configuration method. I suppose I can inject configuration form elements into the content-type configuration pages.. I don't really like that since you have to meander all over creation to see the configuration. I'm still thinking about the problem.
Regarding #2, and the 3 adsense ads per page limit, the adsense module enforces per-page limits, doesn't it? I've never seen more than three ads on a page of teasers using adsense injector on any of my sites. Can you confirm that you *ever* see more than three adsense ads on a page in teaser mode? If you do, then I think it's an issue with the adsense module - adsense injector relies heavily on that module and I don't want to re-implement any of the features of the adsense module in adsense injector.
#2
#3
Thanks for the reply inactivist!
Now that you lay it out, yes, the complexity of per-node administration could confuse and stump a lot of users (I say this looking in the mirror!). The AdSense module tags do relieve a bit of this, so in reality it is only a minor issue and probably best left ignored as manual tags and blocks (and theming) can resolve these issues with less complexity.
As for the 3 AdSense advert limit per page... good point! I do think it does limit the number of adverts, so that probably isn't a problem. If you have a block or two of AdSense and then only 1 or 2 node teasers should be injected.
Now to test this and to see what gets preference: Node Teasers or Blocks! :)
Thanks for the time and comments :)
#4
Having said all that, I have been considering adding the ability to control AI behavior (visibility and insertion) using admin-defined php snippet or snippets - that would allow total flexibility, but of course, would also raise the possibility of bringing down the entire site...
Still thinking about it....
#5
Subscribing.
I think templates according to taxonomy, or nodetype are very interesting.
I want ie. "articles" to show adsense blocks at the end of the node, and befores comments, and I want simple "pages" to show adsense down there AND at the top of the page...
This would really improve this already excellent module.
Rosamunda
#6
I think per node type setting is very interesting. Maybe we can have some trade-off, e.g. a global default setup in admin/settings/adsense_injector, where also allow to have per node type override setting from admin/content/node-type/xxx. This may generate some additional complexity for end user, but we may assist them with documentation :D
IMHO, we can even eliminate the global default setup but coming with per node type setup only. Just disable display for all node type by default, and request user to activate support for each type manually. As they usually need to configure once and forever, this may be somehow acceptable, too. For sure, documentation is a must :S
#7