wyrfel

<p>LogStore can be used to log (important) data from within your plugin.<br />
It provides a simple interface to log entries and a friendly administration interface for viewing and managing the log entries.</p>
<p>While LogStore can be used to log debug output or system events, it’s main intention is to log more extensive data, such as:</p>
<ul>
<li>system emails sent your users</li>
<li>data received from remote API calls</li>
</ul>
<h3>Usage</h3>
<p>To use LogStore in your plugin, add the following line to your plugin’s ‘plugins_loaded’ callback function:</p>
<pre><code>if (class_exists('LogStore')) $this->log = new LogStore('slug', __('Title'));
</code></pre>
<ul>
<li>The ‘slug’ should be a unique identifier for your logger.</li>
<li>The ‘Title’ will be the title used in menu entries, options and page titles.</li>
</ul>
<p>Once that’s done you can then start logging your data from anywhere within your plugin by using the following:</p>
<pre><code>if (!empty($this->log)) $this->log->log(__('My log message'), $my_log_data, 'status', 'tag');
</code></pre>
<ul>
<li>‘My log message.’ is any arbitrary message to describe your log entry.</li>
<li>$my_log_data is the extended data you want to log. This can be either an array or string.</li>
<li>‘status’ is one of ‘none’, ‘ok’, ‘warn’, ‘critical’ or ‘fatal’.</li>
<li>‘tag’ can be any kind of singular tag to  further classification to your log entries.add</li>
</ul>
<p>If you use LogStore in your plugin, you should check for it’s presence in</p>
<ul>
<li>your ‘plugins_loaded’ callback</li>
<li>your plugin activation callback</li>
</ul>
<p>You should either make LogStore use optional or notify the user that they need to install LogStore for your plugin to work properly.</p>
<h3>Plugin Hooks</h3>
<p>In the following hooks, <code>*myname*</code> stands for the name with which you instanciated the LogStore class.</p>
<h4>Action Hooks</h4>
<ul>
<li><code>logstore_init-*myname*</code> – runs during the execution of WP’s <code>init</code> action hook, passes a single boolean parameter indicating if logging is active or inactive for this logger</li>
</ul>
<h4>Filter Hooks</h4>
<ul>
<li><code>logstore_new_entry-*myname*</code> – runs during the creation of a new entry, passes a single array containing all values for that entry (‘time’, ‘message’, ‘data’, ‘status’ and ‘tag’)</li>
<li><code>logstore_entry-*myname*</code> – runs before displaying an entry on screen, passes a single array containting all values for the entry (‘time’, ‘message’, ‘data’, ‘status’ and ‘tag’)</li>
<li><code>logstore_format_entry_data-*myname*</code> – runs before displaying the formatted data on screen, passes the formatted data as string</li>
</ul>
<h3>Further Notes</h3>
<p>Please note that the ‘bulk actions’ in the log viewer are currently not<br />
working.</p>


LogStore

LogStore is a 'meta' plugin that allows other plugins to log data easily.

reviewmylife

<p>Ad Logger from <a href="http://www.advancedhtml.co.uk/" title="advancedhtml" rel="nofollow ugc">advancedhtml</a> logs data about iframe clicks – it can log clicks from Google AdSense, Amazon Affiliates, Facebook Likes, Twitter Tweet button, and Google’s +1 button. It does this without modifying your ad code – it uses other accessible events to estimate when the ad has been clicked. This method is about 80% accurate.</p>
<p>It logs the page, IP, browser, referrer, and dimensions of the clicked iframe to your MySQL database. You can then get reports showing which pages generated the most clicks, where clicking visitors came from, and who is clicking your ads the most. The data and reports are loaded using AJAX so you can browse the data without refreshing the UI.</p>
<h4>Logs clicks without modifying the iframe</h4>
<p>No modifications are made to your adverts/iframes which should (hopefully) enable you to use Ad Logger without breaking any TOS from your ad provider.</p>
<h4>AJAX table reports</h4>
<p>You can view the raw log information in a table, and also view summary reports showing which pages were most clicked, which IPs did the most clicking, what types of ads were most clicked and more.</p>
<p>You can also filter the results. e.g. you can click on the arrow next to an IP address and you’ll see all the clicks that came from that IP address.</p>
<h4>Block AdSense ads if too many clicks appear – basic click bombing protection</h4>
<p>If you insert your AdSense ads using Ad Injection 1.2.0.4+ you can configure Ad Logger to block these ads if too many clicks come from the same person within a set time frame.</p>
<p>This feature uses JavaScript and cookies, so it won’t function if these are turned off, of if your website readers turn their cookies off.</p>
<h4>Dynamically remove ads – basic click bombing protection</h4>
<p>Ad Logger can dynamically hide a named div after the click count is reached (i.e. the ads would dissapear from the current page without the page having to be re-loaded). These divs will stay hidden on subsequent page loads for the click detection expiry time.</p>
<h3>Troubleshooting</h3>
<h4>Reporting bugs</h4>
<p>If you do get any errors please use the ‘Report a bug or give feedback’ link on the plugin to send me the error details. If things go so badly wrong that you can’t even get to the settings page please send me an email via <a href="http://www.reviewmylife.co.uk/contact-us/" title="contact form" rel="nofollow ugc">this contact form</a>.</p>


Ad Logger

Ad Logger from [advancedhtml](http://www.advancedhtml.co.uk/ "advancedhtml") logs data about iframe clicks - it can log clicks from Google A …

LogStore vs Ad Logger