Solution

This is the path I have to the file:
/sites/all/modules/adsense/managed/adsense_managed.admin.inc
For both dev and stable.

at am.org error but not am.com
mod_fcgid: stderr: PHP Fatal error: Call to undefined function adsense_managed_help_text() in /home/aspiremortgage.org/public_html/sites/all/modules/adsense/managed/adsense_managed.admin.inc on line 29
Which is this line
'#value' => adsense_managed_help_text(),
I get this error when I click on /admin/settings/adsense/managed (I get a blank screen also)

I'll use these two sites to debug with; but have the stable version; I can install the dev on one; but this will give you a chance to see why one has errors and one doesn't; both do not display ad.

Where do you call the javascript at?

I did download and test archives and deleted FTP folders and reuploaded them. No help.

I did a little poking around your sites and found this:
http://baheyeldin.com/drupal/drupal-module-google-adsense.html
Found the symptom
Submitted by Anonymous (not verified) on Wed, 2007/04/18 - 11:42.
Using Firefox's Firebug, I can see that the JavaScript to inject (pull) the ads from Google and place them in the box is missing. Hope this helps.

It seems this is a very old problem; I started playing with settings and I got it to work on one site so far; it seems like it has something that isn't being set; you should do a fresh install and run a debugger on it; step each line of code; look for things not getting set correctly; this is a bug; its gong to be hard to find without a line by line debug.

If it was only me I'd say ok; but you have numerous others with the same problem; and it seams you give them them this same speech; which means you never get this problem and can not duplicate it.

As I have stated; after bouncing around it finally started to work; don't know why; my best guess is that somewhere in the code it finally set something that was needed and has worked fine ever since.

I wasn't my ads; they have ran for over a year; its not GA I have a module I wrote for Joomla that works fine all the time.

I repeated this for 4 installs on 4 different sites; I'm sure I put in the right numbers since I didn't change them again and eventually it did start working; after a few hours. Saying it works fine for the other 4999 users is fine; I agree; you can now add me to that total for an even 5,000; but not until you admit that the install has an issue sometimes; maybe rare, but it happened to me and others like me; so its a problem; duplicating it will be hard; firebug isn't the tool to use; you need to first duplicate the issue on a machine; then use a real PHP source code debugger to step thru each line of code and find out what's going on; I have a feeling that you'll find it if you just step thru each line once and pay attention to what's going on, I didn't look at the code, so I don't have any idea; if it continues to be a problem for me, I'll break out my Nusphere's PHP Ed and figure it out and let you know, I'll try to make time to do this, it would be worth it to me, (after I figure out an issue that may stop me from using Drupal for my project, in which case I'll have to start looking for another CMS); otherwise this will continue to be an issue for some installs at least; that is all I'm saying at this point.

You can tell people if the ad doesn't show up right away to give it time; maybe a few hours; this is acceptable for me, it worked eventually; I don't know; is this normal?

At this point I'd say this is a very minor problem / bug, and may not be worth debugging; once it started working it never stopped again.

I can duplicate this on my machine; every install does it. I'm running CentOS 5.3 x64 using install script from Virtual Min.

Great module and thanks

These may not be related to my problem but they do need to be resolved.

$Id: adsense_click.logs.inc,v 1.1.4.2 2008/12/19 01:32:37 jcnventura Exp $
line 55 $path is not defined

// $Id: adsense.module,v 1.68.2.14 2009/01/23 00:28:33 jcnventura Exp $
line 201 $major, $minor is not defined

I understand about not having a debugger to run it line by line; right now I have the same issue in Fedora 10; I can't get the debugger to work in Eclipse; I can jump back to windows where my debugger is working; I just hate windows is all; but I did find that if I set the Enable test mode that sometimes it will start working; not always; but I do always eventually get it to work, so its not that big of deal.

Once I get my debugger working I'll step thru it and find out why this is happening and let you know.

I didn't know if the errors I reported had anything to do with it; or if they are errors; some programmers like to not define variables and then check to see if they have been set with isset; I think this is a bad idea; if it looks like a bug it might turn into one; set the variable with null or false then check to see if its still null or false is a better way to do it, the correct way in fact. I would look at these two lines and see if fixing them solves the problem; I think its worth looking at, otherwise I wouldn't bother you with it. Its clear that something isn't being set correctly; once it is then it works fine; I verified this on another server.

Thanks

@jflesher: I haven't had time to check the adsense_click warning, but the other one is strange: the $major and $minor variables there are parsed from Drupal's version string. In every version I have tested up to now, these have never been undefined.. The question is: what version of Drupal are you running?

One thing about PHP; it has a lot of features like basic; for example sscanf(VERSION, "%d.%d", $major, $minor); it will create the variables if they do not exist; or fill them if they do.

$major, $minor do not exist prior to this command running; therefore they are undefined; after running they are defined

if you define them prior to this; like so:

$major=0;
$minor=0;
sscanf(VERSION, "%d.%d", $major, $minor);

You will not get this warning when running test against the code. This is a best practice; even though the examples of its use do not show this

Either way is still correct in PHP and was not causing any problems.
But by defining them first you do not get a warning and I would say its more correct.

I should have looked at the code before posting this; sorry; lazy on my part; but if you define them the warnings will not show up and look cleaner and more professional.

This module is working great once the settings take; thanks for your hard work.

Just to clarify for NancyDru about settings:

Make sure you enter the ID here admin/settings/adsense/publisher in the format pub-9999999999999
Check enable test mode under advanced here admin/settings/adsense

In the block to display the ad here admin/build/block/configure/adsense_managed/0 (0 may differ for you) but make sure the ad slot ID is in the format 0123456789
Make sure you pick the correct ad format for this slot

You should be able to see the block and compare the code in it with the code Google Adsense gave you at their site.
Google will give you the code to cut and paste it; if you are still having problems; paste that code and the code at your site that shows up in the block here and we can help you a little more.