Now! Plugin for AdSense gets you started with Google AdSense. No mess, no fuss. Simplest Google AdSense plugin.
Now! Plugin for AdSense draws a red box on your blog posts to show where the ads would be shown if you entered the ad code on its admin page. (These boxes are shown only if you are logged in as admin.) This is meant to serve as a reminder for you to go to the admin page and enter the ad code. If you would like to suppress them, check the option "Suppress Placement Boxes" in the Pro section. The right thing to do, however, would be to enter your ad codes in the text boxes for each ad slot, or suppress the ad slot in the Ad Alignment panel.
Now! Plugin for AdSense is the freely distributed version of a premium plugin. The Pro version gives you more benefits -- lets you activate a filter to ensure that your ads show only on those pages that seem to comply with Google AdSense policies. It also lets you specify a list of computers where your ads will not be shown, in order to prevent accidental clicks on your own ads -- one of the main reasons AdSense bans you. These features will minimize your chance of getting banned. It also has full support of mobile devices, and supports per category and per post ad suppression. The Pro version costs $6.95.
What you have in AdSense is an ability to block ads from certain sites. For instance, if you don't like ads from my site "thulasidas.com", you can block them. What the pro version gives you is the ability to block ads to certain clients. That is, if you don't want visitors from certain IP addresses see your ads (because they may click on too many of them, getting your AdSense account banned, for instance), you can with my plugin.
Porn block also is similar -- Google lets you choose non-porn ads (I think). What my plugin does is to look at the content of your page, and block ads if it looks like a porn page. (This can happen if a spammer posts a porn kind of comment on your blog, which again may get your AdSense account banned.)
This plugin uses a paid support model in order to manage the support load. Each support ticket will be charged at $0.95 for the Lite version (and for the Pro version after a short free support period). The support ticket is valid for 72 hours, and further follow-up questions will call for a new support ticket.
<div>s that Now! Plugin for AdSense creates have the class attribute
adsense. Furthermore, they have attributes like
adsense-leadout depending on the type. You can set the style for these classes in your theme
style.css to control their appearance.
The other plugin I have published, Easy AdSense, does everything that Now! Plugin for AdSense does and more. But in doing so, Easy AdSense has become an All-in-One AdSense plugin, and not "Easy" any more. I wanted to go back to the basics and provide a simple plugin to get our fellow bloggers started on AdSense.
If you think Now! Plugin for AdSense is too lean and mean for your taste, try my full-fledged, feature-rich plugin Easy AdSense. I plan to keep Now! Plugin for AdSense simple.
Note that you have to generate your adsense code from Google, and paste the entire code in the text box, replacing the existing text. Changing the publisher id alone is not good enough.
If you just created the new Google AdSense code, it may not be active yet. Google takes about ten minutes or so before serving ads. Please try again later.
Yes! Now, in V1.1+, you have more options (using Custom Fields) to control adsense blocks in individual posts/pages. Add custom fields with keys like
adsense-search and with values like
no to have control how the Google adsense blocks show up in each post or page. A Custom Field
adsense with value
no suppresses all AdSense ad blocks in the post or page.
In the Pro version of this plugin, you can control the ad placements using the shortcode
[adsense] in your blog posts and pages. If you would like to place your ads using shortcodes, please enable it on the Pro page.
By default, only those ads specified by the shortcode will be displayed (when shortcodes are enabled). You can specify how the plugin handles shortcode priority using a drop-down menu. You have these choices:
The last option effectively disables the plugin for the body of posts and pages.
If you have a question or comment about the Pro version, please do not use the forum hosted at WordPress.org, but contact the plugin author using our support portal.
You can download the previous version and install it. First deactivate and delete the latest version of the plugin, and then follow the Uploading method under the Installation section of this document. The new version uses an completely different options model, and your old options are left intact in your database, so that you can go back anytime.
Your web server needs direct access to the plugin files to load anything in an iFrame. Some aggressive security settings block this kind of access, usually through an
.htaccess file in your
plugins folders, which is why this plugin gives a corresponding error message if it detects inability to access the files (checked through a
file_get_contents call on a plugin file URL). But some systems implement further blocks specifically on
file_get_contents or on iFrames with specific styles (using
mod_securty rules, for instance), which is why the plugin provides a means to override this auto-detection and force the admin page.
Note that it is only your own webserver that needs direct access to the PHP files. The reason for preventing such access is that a hacker might be able to upload a malicious PHP (or other executable script) to your web host, which your webserver will run if asked to. Such a concern is valid only on systems where you explicitly permit unchecked file uploads. For instance, if anyone can upload any file to your media folder, and your media folder is not protected against direct access and script execution, you have given the potential hacker an attack vector. This plugin has no upload facility, so allowing your webserver to serve the plugin admin files in an iFrame is completely safe, in my judgement.
Requires: 2.5 or higher
Compatible up to: 4.3.1
Last Updated: 3 weeks ago
Active Installs: 5,000+
2 of 2 support threads in the last two months have been resolved.
Got something to say? Need help?