Plugin Directory

Ads EZ Plugin for Google AdSense

Ads EZ Plugin for Google AdSense inserts Google ads on your blog, with customization using color pickers, widget support and robust placement options.

How can I control the appearance of the ad blocks using CSS?

All <div>s that Ads EZ Plugin for Google AdSense creates have the class attribute adsense. Furthermore, they have class attributes like adsense-top, adsense-bottom etc., You can set the style for these classes in your theme style.css to control their appearance.

Can I control how the ad blocks are formatted in each page?

Yes! In Ads EZ Plugin for Google AdSense, you have more options [through custom fields] to control ad blocks in individual posts/pages. Add custom fields with keys like adsense-top, adsense-middle, adsense-bottom and with values like left, right, center or no to have control how the ad blocks show up in each post or page. The value "no" suppresses all the ad blocks in the post or page for that provider.

How do I use shortcodes?

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:

  • Do auto placements if shortcode is missing
  • Do not place any ads if shortcode is missing
  • Always ignore shortcodes and do only auto placement
  • Do not place any ads in posts/pages

The last option effectively disables the plugin for the body of posts and pages, leaving the widgets unaffected.

I don't understand the Pro features. Porn and site block - can't you set those during Asdense ad setup?

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.)

How do I report a bug or ask a question?

Please report any problems, and share your thoughts and comments at the plugin forum at WordPress Or contact me.

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.

Can I go back to the previous version of the plugin? I don't like the modern bootstrap/AJAX interface.

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.

Why do I get error message saying something about direct access to plugin files?

This plugin admin interface is designed with a loosely coupled architecture, which means it interacts with the WordPress core only for certain essential services (login check, plugin activation status, database access etc). Loosely coupled systems tend to be more robust and flexible than tightly integrated ones because they make fewer assumptions about each other. My plugin admin pages are fairly independent, and do not pollute the global scope or leak the style directives or JavaScript functions. In order to achieve this, they are loaded in iFrames within the WordPress admin interface.

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 wp-content or 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.

Is the direct access to plugin files a security hole?

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: 3.2 or higher
Compatible up to: 4.3.1
Last Updated: 2015-9-29
Active Installs: 2,000+


3.4 out of 5 stars


1 of 1 support threads in the last two months have been resolved.

Got something to say? Need help?


Not enough data

0 people say it works.
0 people say it's broken.