Ben Lobaugh (blobaugh)

freshmuse

<p>Adds the ability to duplicate an event created by Modern Tribe’s The Event Calendar plugin. This plugin utilizes the TEC functions to ensure that the new event gets passed through all proper filters</p>
<p>Want to get involved? For this project on Github https://github.com/FreshMuseDesign/duplicate-tec-event</p>
<h3>1.5.2</h3>
<ul>
<li>Updated compatibility with WordPress 4.8</li>
</ul>
<h3>1.5.1</h3>
<ul>
<li>Verified working with WP 4.4.1</li>
</ul>
<h3>1.5</h3>
<ul>
<li>Updated to ensure functionality with 3.7</li>
</ul>
<h3>1.4</h3>
<ul>
<li>Fixed bug causing duplicated recurring events to also alter the original recurring events on edit ( thanks Steve! )</li>
</ul>
<h3>1.3</h3>
<ul>
<li>Added a nonce for security</li>
<li>Performed updated requested by Modern Tribe</li>
</ul>
<h3>1.0</h3>
<ul>
<li>First release</li>
</ul>


Duplicate TEC Event

Adds the ability to duplicate an event created by Modern Tribe's The Event Calendar plugin.

Modern Tribe, Inc.

Jonathan Brinley

Peter Chester

<p>You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls, and server IPs.</p>
<p>This is designed to either be managed using wp-config.php and logging OR using the admin and debugbar plugin ( https://wordpress.org/extend/plugins/debug-bar/ ). Most of the following documentation applies equally to the settings panel or the wp-config.php vars.  Either one works fine. The only exception is the DEBUG_LOG configuration which is only supported as a wp-config var.</p>
<p>Firstly, you can manually log things using the following function:</p>
<pre><code>do_action( 'log', $message, $group, $data );
</code></pre>
<p>The $group allows you to selectively output logging based on groups of log messages. The $message is the string you want to see in the log. $data is an optional parameter for the data that you want to display in the log (objects, arrays, or any other sort of data really).</p>
<p>To render messages to the log, you must configure wp-config.php as follows:</p>
<p>Run debug on only these groups. Use ‘ALL’ to debug everything. The group ‘ACTIONS’ is reserved for WordPress actions.</p>
<pre><code>define( 'DEBUG_GROUPS', 'ACTIONS,default,myspecialgroup' );
</code></pre>
<p>Display these outputs in the log for each log message.</p>
<pre><code>define( 'DEBUG_PARAMS', 'time,timedelta,memory,memorydelta,data,backtrace,url,server' );
</code></pre>
<p>WordPress actions that you wish to log.</p>
<pre><code>define( 'DEBUG_ACTIONS', 'wp_head,switch_theme,wp_footer' );
</code></pre>
<p>Optional restriction by URL (useful on MU installs).</p>
<pre><code>define( 'DEBUG_URLS', 'myurl.com' );
</code></pre>
<p>Minimum time in milliseconds required to register a log entry as being slow. Default 0 for no minumum.</p>
<pre><code>define( 'DEBUG_MIN_TIME', 500 );
</code></pre>
<p>Minimum memory in killobytes required to register a log entry as being heavy. Default 0 for no minumum.</p>
<pre><code>define( 'DEBUG_MIN_MEM', 1024 );
</code></pre>
<p>Path to log file or set to TRUE to use php error log. Default FALSE for no logging.</p>
<pre><code>define( 'DEBUG_LOG', '/path/to/writable/log/file' );
</code></pre>
<p>or</p>
<pre><code>define( 'DEBUG_LOG', TRUE );
</code></pre>
<h4>Todo</h4>
<ul>
<li>Add variable for sample rate so that this could run randomly on production installs</li>
<li>Admin panel per site</li>
<li>Admin panel globally</li>
<li>WordPress error logging</li>
<li>Mysql query logging</li>
<li>WP_Error integration</li>
<li>Alerts ex: if this takes more than this much memory then log it…</li>
</ul>


Debugger

You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls …

Duplicate TEC Event vs Debugger