Ads EZ Plugin for Google AdSense

Description

Sunset Edition
This update of the plugin is the last publicly released version. We do not expect to make any serious changes or add new features to it from now on.

We may not always be able to provide prompt support for this plugin on the WordPress.org forums. If you would like to have professional support or extra/custom features, consider buying the Ultra version

Ads EZ Plugin for Google AdSense provides a streamlined interface to deploy Google ads on your blog. You can customize the colors, sizes and placement of the ad blocks and activate them right from the plugin interface.The admin interface uses a highly functional and modern interface based on the twitter bootstrap framework with generous, context-sensitive help on every single option.

Live Demo

Google AdSense admin interface is feature-rich, user-friendly and functional. Please visit this fully operational live demo site to see what it can do for you.

Ads EZ Plugin for Google AdSense is a specialized version of Google AdSense Ultra, which lets you manage in basic, standard and expert modes, all in a beautifully designed modern interface.

Features

  • Rich display and alignment options.
  • Control over the positioning and display of ad blocks in each post or page.
  • Customized Google interface with color pickers.
  • Widgets for your sidebar.
  • Beautifully designed, fully responsive, intuitive interface.
  • Inline editing and instant saving of your options with AJAX (no more form submit/refresh etc.)
  • An interface tour to familiarize yourself with the plugin features and layout.
  • Popover help for every option in the plugin.
  • Ability to spawn the plugin interface as a separate tab/window independent of the WordPress admin interface.
  • Robust codebase and option/object models.

Pro Version

Ads EZ Plugin for Google AdSense is the freely distributed version of a premium plugin. The Ultra version gives you even more features.

  • Safe Content filter: To ensure that your Google AdSense ads show only on those pages that seem to comply with Google AdSense policies, which can be important since some comments may render your pages inconsistent with those policies.
  • IP filter: Ability to 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.
  • Compatibility mode: To solve the issue of the ad insertion messing up your page appearances when using some themes.
  • Category/Post Control: Ability to suppress ads on specific categories, posts and pages.
  • Shortcode Support: Show the ads only on the pages or posts you want, and exactly where you want them.
  • Mobile Support: Ability to show different sets of ads on mobile devices, or to suppress ads.
  • Excerpts: Ability to show a configurable number of ads on Excerpts (which make up the home page in some themes).
  • Option Sets: Multiple option sets can be defined and easily switched between.
  • Suspend Ads: Ability to temporarily suppress ad serving.
  • Admin Interface Themes: Multiple color schemes for the admin interface.
  • Ad Serving Statistics: Keep an eye on your ad serving statistics to make sure that Google is not shortchanging you. (Optional paid module)
  • Basic/Expert Modes: You can choose to operate it in basic or expert modes in addition to the standard mode.

The Ultra version costs $9.45 and can be purchased online with instant download link.

Screenshots

  • Ads EZ Plugin for Google AdSense "Overview" tab.
  • How to set the options for Ads EZ Plugin for Google AdSense.
  • Advanced configuration of the plugin.
  • Options to support safety, compatibility, mobile devices and category/post control.

FAQ

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](http://support.thulasidas.com/ “Contact Manoj”) 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.

Reviews

This guy is seriously confused, Dashboard like a xmas tree.

reg1970

What is up with this guy. He has got so many plugins aiming to do the same thing on the adsense repository under different brand names. i paid for a pro version and then found there was an upgrade and was required to buy the upgrade just after i bought the pro version. no thanks.

1. so many different plugins by same author
2. his DASHBOARD LIKE A CHRISTMAS TREE - it lights up, so confusing. its a f**cken mess!

Works fine

malzminor

Had a small issue with my theme and the plug in when I first installed. Contacted the developer and he quickly took care of it. Good variety of functions and easy to use.

Read all 13 reviews

Changelog

  • V4.10: Compatibility with WP4.6. Many accumulated fixes and changes. Releasing the sunset version. [Oct 12, 2016]
  • V4.00: Compatibility with WP4.5. [Apr 12, 2016]
  • V3.98: Improvements in the Google Translator interface. Compatibility with multisite installaton of subdomain type. [Feb 28, 2016]
  • V3.97: Minor interface and documentation changes. [Feb 25, 2016]
  • V3.95: Work-around for servers that refuse to save ad code because of the script tag. [Feb 18, 2016]
  • V3.94: Restricting Google Translate not to translate user-editable strings. Optimizing screenshots. [Feb 7, 2016]
  • V3.94: Ensuring widget titles can be suppressed in Easy AdSense. [Jan 27, 2016]
  • V3.93: Adding diagnostic information on the update page. [Jan 20, 2016]
  • V3.92: Changes to make the plugin compatible with multisite installations. [Jan 14, 2016]
  • V3.91: Adding a dev-friendly include to introduce local settings, if any. [Dec 30, 2015]
  • V3.90: Compatibility with WordPress 4.4. [Dec 5, 2015]
  • V3.82: Making the admin menu dynamic (optionally) in standalone mode. Improving DB layer error handling. [Nov 29, 2015]
  • V3.81: Warning about PHP V5.4 requirement on the admin page. [Nov 8, 2015]
  • V3.80: Admin pages in your language using Google translation. [Oct 22, 2015]
  • V3.73: Renaming the Mobile_Detect class for compatibility. [Oct 14, 2015]
  • V3.72: Improving the speed of admin page loading. [Sep 30, 2015]
  • V3.71: Killing the option to allow update checks. [Sep 26, 2015]
  • V3.70: Changes to make the plugin work on nginx and Microsoft servers. [Sep 20, 2015]
  • V3.64: Ensuring usability on touch-screen devices. [Sep 17, 2015]
  • V3.63: Reinstating the option to force the admin page loading, moving to a less colorful default theme. [Sep 14, 2015]
  • V3.62: Minor refactoring changes. [Sep 12, 2015]
  • V3.61: Adding the missing EzPlugin.php.[Sep 9, 2015]
  • V3.60: Removing WP core file loading. [Sep 4, 2015]
  • V3.52: Fixing a minor error in text-wrapping around the bottom ad. [Aug 20, 2015]
  • V3.51: Ensuring plugin admin files can be loaded in an iFrame. [Aug 19, 2015]
  • V3.50: Compatibility with WordPress 4.3. [Aug 10, 2015]
  • V3.42: Fixing the “Database Replace/Insert Error” that affected some servers. [Aug 8, 2015]
  • V3.41: Fixing a bug in mobile detection. [Aug 1, 2015]
  • V3.40: The plugin now remembers the last used tab. SQL schema change for better compatibility. Fixing a bug that may have caused the plugin not to display ads on some pages/posts. New option to control mid-text ad position in pro version. [Jul 30, 2015]
  • V3.35: Minor improvements in setup, plugin active status check and AJAX functions. [Jul 26, 2015]
  • V3.34: Minor changes in links. [Jun 25, 2015]
  • V3.33: Documentation changes only. [Jun 18, 2015]
  • V3.32: Admin page improvements. [May 22, 2015]
  • V3.31: Admin page compatibility checks and improvements. [May 12, 2015]
  • V3.30: Compatibility with WordPress 4.2. [April 25, 2015]
  • V3.23: Preparing the codebase for the release of AJAX AdSense. [April 17, 2015]
  • V3.22: Improvements in the admin dashboard. [April 14, 2015]
  • V3.21: Improvements in the admin dashboard. [April 14, 2015]
  • V3.20: Launching a demo site. [April 11, 2015]
  • V3.19: More changes in the compatibility check. [April 7, 2015]
  • V3.18: Fixing a style that may have caused the admin page not to appear on some blogs. [April 4, 2014]
  • V3.17: More compatibility checks. [April 2, 2015]
  • V3.16: Minor fixes. [Mar 27, 2015]
  • V3.15: Fixing a bug that prevented custom fields from working properly. [Mar 26, 2015]
  • V3.14: Minor bug fix on ad suppression while not in loop. [Mar 25, 2015]
  • V3.13: Adding error handling for updates. [Mar 24, 2015]
  • V3.12: Serious bug fix related to multiple passes of the content filter. Introducing a verbosity option. [Mar 22, 2015]
  • V3.11: Minor bug fixes, and adding diagnostic comments. [Mar 21, 2015]
  • V3.10: This twitter-bootstrap version of the plugin is now feature-complete. [Mar 19, 2015]
  • V3.09: Adding information about how to revert to the non-AJAX version of the plugin. [Mar 16, 2015]
  • V3.08: Documentation and usability enhancements. [Mar 13, 2015]
  • V3.07: Documentation and usability enhancements. [Mar 11, 2015]
  • V3.06: More changes for compatibility with PHP5.30. [Mar 11, 2015]
  • V3.04: Improvements in the login check functions. Various accumulated fixes. [Mar 9, 2015]
  • V3.03: Killing anonymous functions for compatibility with PHP versions older than 5.3. [Mar 8, 2015]
  • V3.02: Changes to the activation validation checks. [Mar 7, 2015]
  • V3.01: Modifications to the update module. Minor code clean up. [Mar 5, 2015]
  • V3.00: Complete rewrite of the plugin with a lot more features. Admin page based on the twitter bootstrap framework. [Mar 3, 2015]
  • V2.50: Compatibility with WP4.1. [Jan 8, 2015]
  • V2.40: Renaming the plugin as requested by Google. [Nov 30, 2014]
  • V2.30: Automatic options migration upon plugin activation. [Sep 26, 2014]
  • V2.22: Minor change to the admin interface. [Sep 9, 2011]
  • V2.21: Compatibility with WP4.0. [Sep 8, 2014]
  • V2.20: Compatibility with WP4.0. [Sep 7, 2014]
  • V2.12: Updating translations, minor bug fixes. [Jul 17, 2014]
  • V2.11: Minor bug fix. [May 8, 2014]
  • V2.10: Internationalization and compatibility with WP3.9. [May 7, 2014]
  • V2.00: Major changes to the design — adding a translation interface, getting ready to change options handling. [Mar 22, 2014]
  • V1.81: Adding options to suppress ads on sticky front page or search pages. [Jan 5, 2013]
  • V1.80: Compatibility checks for WordPress V3.8. Bug fixes in options migration. [Dec 18, 2013]
  • V1.70: Compatibility checks for WordPress V3.7. [Nov 11, 2013]
  • V1.60: Compatibility with WP3.6. [Aug 10, 2013]
  • V1.50: Adding an admin page translator. [May 22, 2013]
  • V1.46: Bug fixes (Fatal error: Call-time pass-by-reference has been removed). [Jan 24, 2013]
  • V1.45: Bug fix. [Dec 22, 2012]
  • V1.44: Enforcing the Google policy on the number of ads, and making the pub-id entry flexible. [Nov 4, 2012]
  • V1.43: Minor changes to validate the readme.txt. [Oct 21, 2012]
  • V1.42: Minor changes to validate the readme.txt. [Oct 21, 2012]
  • V1.41: Initial public release of the lite version. [Oct 21, 2012]
  • V1.40: Admin interface modifications. [Sep 30, 2012]
  • V1.31: Taking care of some debug notices from WordPress debug mode. [Aug 28, 2012]
  • V1.30: Initial public listing at WordPress.org. [July 18, 2012]
  • V1.20: Bug fixes, coding improvements. [Sep 9, 2011]
  • V1.00: Initial release. [Nov 15, 2010]

Contributors & Developers

This is open source software. The following people have contributed to this plugin.

Contributors

Browse the code