See only Adsense placeholder for all enabled nodes
Thomasr976 - January 12, 2009 - 04:40
| Project: | Adsense Injector |
| Version: | 5.x-2.7 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | hswong3i |
| Status: | closed |
Description
I recently updated to version 5.x-2.7 and am running Drupal 5.14. Just noticed low adsense stats and realized that the ads were not showing up in any nodes. However this is what has shown up in their place: adsense:250x250:0123456789]
I rechecked Adsense and Adsense Injector settings and all seem fine. Can you assist in trouble shooting this. Thanks.

#1
This is what source is showing:
[adsense:250x250:0123456789]
perhaps this is a clue as to what is wrong
#2
I don't think this is related to the Adsense module as all of my other adsense ads are fully visible. Only the inline ads don't show and all I see is a placeholder
#3
Anyone?
#4
I've never seen this happen, and it's never been reported before.
I'll try to investigate soon.
If no one else can suggest a solution soon, I'd advise that you revert to a prior version since this is impacting your revenue.
#5
Thanks. I appreciate it. I was going to revert back to a previous version, but I'll wait til I hear from you.
It's probably something simple, but for the life of me i can't figure it out. I also checked the input format and I have the Google adsense checkbox enabled and no other code is being stripped.
If you want to see the actual pages go to my site.
#6
Hi,
I went back to version 5.x.2.6 and all works fine. There must me some kind of a bug. Perhaps the 5.x.2.7 version requires the Adsense 5.x-3.0-beta2 version. Please let me know if there is a solution. I really hate to use mods that are not current.
Thanks in advance.
Tom
#7
2 Qs:
For my case with latest adsense.module beta version, I need to update my official Google Adsense account detail and reconfigure adsense.module in order to get everything function.
[adsense:250x250:0123456789]? Because the 0123456789 is just a dummy placeholder and you will need to replace as your own value. Please refer to adsense.module help message for more inforamtion.#8
Exactly the same is happening to me. I'm thinking of switching back to previous version, which worked perfectly, until then, I've had to disable injection :-(
#9
Thanks for the tip, hswong3i, it seems that new version (either of adsense.module or adsense_injector.module) use a placeholder for (I guess) the google adsense client number. However, I've entered my own value, both with and without pub- , and It doesn't seem to work either. The rest of the ads, i.e. the not injected ones work OK.
#10
@fuldespanto: Sorry that still not correct. That's not the client number but the slot number. Here are the adsense.module help message:
Regards,
Edison Wong
#11
hswong3i
Many thanks for getting back to us. I think my Adsense Module was configured correctly. Now that I have gone back to version 5.x.-2.6 all works well.
#12
I should RTFM more often. Now I have done it i find that even though I've put the correct values it doesn't work either. Switched back to 2.6 and it works again. Anyway, I was happy with that version.
Thanks a lot Edison
#13
I double check my Drupal 5.x testbed and all are function correctly. Some screenshots here about my site setup:
Hope this can help you all figure out the problem :D
#14
Thanks for sharing this. I'll take a look.
#15
Now that I have taken a look at your images I realize what is going on. You are using the recommended version of the Adsense Injector Module for drupal 5, but you are not using the recommended Adsense module 5.x-2.1. Instead you're using the 5.x-3.0-beta2 version. This specific version requires a Managed Ads module.
It seems to me that if we use the recommended Adsense injector module, it should work as a matter of policy with the recommended version of the Adsense Module. We should not have to use a beta version. Could you and the other Adsense Injector module maintainers seriously consider looking into getting it to work that way? thanks for considering this.
#16
From a technical point of view, what adsense_injector.module does are:
adsense_injector.module have no duty about the syntax used for adsense.module placeholder. So, please use the corresponding placeholder syntax and all should be function correctly.
P.S. Even though I am now using adsense.modules beta2, all are function correctly. Moreover, the requirement from Google Adsense already changed, which only supported by latest adsense.module beta version. IMHO, I would suggest a upgrade of your Drupal module :D
#17
hswong3i,
I see your point and will upgrade my Adsense module to the beta version as you suggest. I think that the documentation on the Adsense Injection Module page should reflect the above to avoid problems. Thanks for the assistance.
Tom
#18
yup i got the same problem...
Adsense module 5.x-2.1
Adsense Injector: 5.x-2.7
But after i'm change the setting:
The new setting [adsense:250x250:0123456789]
back to old setting ... [adsense:336x280:4:4] adsense display back to normall...
wrote something about this on http://nossdutytask.com/drupal_config/adsense_injector_no_google_adsense...
but still on the front page ... the page show twice.... i thint the new module still have bug....
http://nossdutytask.com/
#19
As far as I know, Adsense Injector defers all processing of tags to the adsense module. Adsense injector hands your template strings (the ones you use in the adsense_injector settings) over to the adsense module for processing. Adsense injector does absolutely nothing with your configured [adsense:x:y:zzz] tags.
If you see malformed output, it's probably due to malformed tags (which seems to be the case), malformed adsense_injector templates, or some other module interfering with normal operation.
So, I ask you to disable all non-core modules (including CCK if it is enabled) except adsense and adsense_injector, and see if your observed issues remain.
What version(s) of adsense module support this new tag syntax? ([adsense:250x250:0123456789]) Does anyone know when this feature was introduced?
Would you mind attaching a text file with copy of the offending adsense_injector templates (the node and list injection templates), so I can verify that I'm testing using the same patterns?
Thanks.
#20
Hi,
The [adsense:250x250:0123456789] tag syntax was introduced right at the beginning of the 5.x-3.x (and 6.x-1.x) development, as a much cleaner syntax for the new code (for backwards compatibility there's an equivalent [adsense:250x250:::0123456789] syntax, but please don't use it).
The old syntax tag [adsense:336x280:4:4] still works, but (of course) you must enable adsense module's old code sub-module, as you're not providing any slot ID. Basically, when you provide a slot ID, Google's new code is used, and when you don't then the old code is used. Since support for old and new code is in different sub-modules in the adsense package, you must have the appropriate ones enabled.
Anyway, the adsense module's recommended version is now version 5.x-3.0, so just upgrade to it and activate all sub-modules (except click tracking and revenue sharing, if you don't use them). The ones marked (old) will support your existing setup, and the new ones provide you with the new 'official' code from Google, so you can keep them all enabled while you migrate to Google's new code.
Assuming that hswong3i is keeping both the 5.x-2.7 and 6.x-2.7 versions in sync, and since there were few changes between 6.x-1.0beta3 and 6.x-1.0, I would think that the latest versions are fully compatible with each other (on the adsense side, the 5.x-3.0 and 6.x-1.0 are in sync).
João Ventura
#21
@jcnventura: Yes, both adsense_injector 5.x-2.7 and 6.x-2.7 versions are in sync. They should fully compatible with latest adsense.module with new [adsense:250x250:0123456789] tag syntax.
As you mentioned, user should enable legacy adsense tag syntax support if they do need it:
As I have using latest adsense.module with adsense_injector.module for more than 3 months without any error, this issue now marked as fixed. Please kindly reopen this issue if problem still happened.
#22
Automatically closed -- issue fixed for 2 weeks with no activity.
#23
Hi,
I have a small Q,
If I use revenue shearing,
who's "slot" is it, the users or mine?
can I consider other ways of doing this? I am really confuse on how to treat the revenue sharing.
any help would be most appropriated.
Avi