The wonderful Drupal AsSense module received a great new update tonight. Ironically one of the notes I made on the plane was to look into whether a universal patch for hiding the currently selected AdSense ID from the user profile made sense. It probably wouldn't have made much sense. Instead I came home to find out that the AdSense module now has a great API and modules can do all sorts of things. In addition there are a plethora of options for integrating with UserPoints, setting ID's by content type or taxonomy terms. All and all an outstanding piece of work.
According to the post the download will be here. Upgrading is pretty straight forward. Remove your old AsSense module and install the new one. A visit to the admin/build/modules page will reveal that you need to enable one of the two included modules, either basic or revenue-sharing.
I've been working recently on a presentation about open source software. This great upgrade will be included as a prime example of where open source and the community behind projects like Drupal make software better than many a closed-source shop.
Comments
Great point. In case you're here because you're missing the code it *might* be possible to check the profile_values table and finding the value. That will get harry quickly unless you've got just a few codes. Along those lines it is best to upgrade and make sure it works before you remove the field from the user profile. Although in a simple configuration the profile field is unneeded you can edit the user to get the code until you delete the field.
I just upgraded adsense on a client site only to discover it loses your code. Luckily he had an ad that was just pasted in and I was able to pull the code out from that so I didn't have to try and get a hold of him. So make sure you have a copy of the code before you update. :)
Michelle
In my case I didn't delete anything. It's a single admin site with just one adsense code, no revenue sharing. All I did was upgrade the module and it blew up. I didn't delete any fields. I expected the code to still be there after the upgrade. Usually module upgrades don't delete settings and there wasn't anything in the release notes about it.
Michelle
Post new comment