joelharkes

<p>A new plugin where people can schedule in hours into a timetable.<br />
easily when they are registered or with recaptchawhen they are not.</p>
<p>This plugin is heavenly reliant on you using a theme which uses bootstrap ass layout base.</p>
<p>This is the long description.  No limit, and you can use Markdown (as well as in the following sections).</p>
<p>For backwards compatibility, if this section is missing, the full length of the short description will be used, and<br />
Markdown parsed.</p>
<p>A few notes about the sections above:</p>
<h3>Configuration</h3>
<ol>
<li>Go to this menu and add the reCaptcha keys in the settings.</li>
<li>Add the calendars you want.</li>
<li>Add the post, added by this plugin, in your menu so people can go to this page.</li>
</ol>
<h3>1.3.0</h3>
<ul>
<li>Added option to only let logged in users book hours</li>
<li>Shows popup now notifying settings are saved (admin)</li>
<li>Fixed some texts to also be Dutch</li>
<li>Show more user friendly dates in popup</li>
<li>Logged in users can now overwrite there username and email in booked hour</li>
</ul>
<h3>1.2.8</h3>
<ul>
<li>Added setting for visibility calendar select box</li>
</ul>
<h3>1.2.7</h3>
<ul>
<li>Added plugin css setting</li>
</ul>
<h4>1.2.6</h4>
<ul>
<li>Update stable version</li>
</ul>
<h4>1.2.5</h4>
<ul>
<li>Fix Calendar name was not showing on page load.</li>
</ul>
<h4>1.2.4</h4>
<ul>
<li>Fix readme. Update stable version to this corresponding plugin version.</li>
</ul>
<h4>1.2.3</h4>
<ul>
<li>Add localisation for dates (moment.js is used for dates)</li>
</ul>
<h4>1.2.2</h4>
<ul>
<li>Add localisation support. (Dutch added, english default)</li>
</ul>
<h4>1.2.1</h4>
<ul>
<li>Hotfix for include file warning</li>
</ul>
<h4>1.2</h4>
<ul>
<li>Set to active version</li>
</ul>
<h4>0.1</h4>
<ul>
<li>Initial check-in of the plugin to wordpress</li>
</ul>


Jih Schedular

A schedule in your wordpress website where (unregistered) people can sign up for an hour.

Arno Welzel

K. Tough

<p>The Timed Content plugin allows users to specify that a portion of a Page or Post should appear/be visible or disappear/be invisible based on given time characteristics. You can also make portions of a Post or Page be visible at certain dates and times; you can even set up a schedule!</p>
<p>The plugin adds the following:</p>
<ul>
<li>A “client-side” shortcode that allows the marking of content to appear or disappear after a given time interval; a “fade” effect is included.  This functionality is intended to be used for special effects only, as content marked in this manner is still visible in the HTML source and, therefore, not a secure method of hiding content.</li>
<li>Two “server-side” shortcodes that allow the marking of content to be visible only during specified date/time intervals.  This functionality <strong>can</strong> be used as a secure method of hiding content, because the marked content will be included in the Page/Post <strong>only</strong> when viewed in the specified date/time intervals.</li>
</ul>
<p>A TinyMCE dialog is included to help users build the shortcodes. See the Screenshots tab for more info.</p>
<h3>Examples</h3>
<pre><code>[timed-content-client show="1:00"]Show me after one minute.  Since we don't want a fade-in, we can leave it out of the "show" attribute completely.[/timed-content-client]

[timed-content-client show="1:00:1000"]Show me after one minute with a 1000 millisecond (1 second) fade-in.[/timed-content-client]

[timed-content-client hide="1:00:1000"]Hide me after one minute with a 1000 millisecond (1 second) fade-out.[/timed-content-client]

[timed-content-client show="1:00:500" hide="5:00:2000"]Show me after one minute with a 500 millisecond (a half-second) fade-in, then hide me after five minutes with a 2000 millisecond (2 seconds) fade-out.[/timed-content-client]

[timed-content-server show="2013-09-13 20:30:00 -0600"]Show me starting at 8:30 PM Central Standard Time on September 13th, 2013. I will not be displayed before then.[/timed-content-server]

[timed-content-server hide="2013-09-13 20:30:00 America/Chicago"]Hide me starting at 8:30 PM Central Daylight Time (i.e., the same timezone as Chicago) on September 13th, 2013.  I will not be displayed after then[/timed-content-server]

[timed-content-server show="2013-09-13 20:30:00 -0600" hide="2013-09-13 21:30:00 -0600"]Show me starting at 8:30 PM Central Standard Time on September 13th, 2013, then hide me an hour later. I will not be displayed before or after then.[/timed-content-server]

[timed-content-rule id="164"]Display me based on the settings for the Timed Content Rule whoseID is 164.[/timed-content-rule]<h3>Usage</h3>
</code></pre>
<p>NOTE: All shortcodes can be built using the TinyMCE dialog.  When in doubt, use the dialog to create correctly formed shortcodes.</p>
<p><strong>The timed-content-client shortcode</strong></p>
<pre><code>[timed-content-client show="mm:ss:fff" hide="mm:ss:fff"]Example Text[/timed-content-client]
</code></pre>
<ul>
<li><code>show</code> – Specifies the time interval after loading the web page when the marked content should be displayed. The attribute consists of three parts,<br />
separated by colons: <code>mm</code> – minutes, <code>ss</code> – seconds, and <code>fff</code> – if greater than <code>0</code>, a fade-in effect lasting <code>fff</code> milliseconds is applied.</li>
<li><code>hide</code> – Specifies the time interval after loading the web page when the marked content should be hidden. The attribute consists of three parts,<br />
separated by colons: <code>mm</code> – minutes, <code>ss</code> – seconds, and <code>fff</code> – if greater than <code>0</code>, a fade-out effect lasting <code>fff</code> milliseconds is applied.</li>
</ul>
<p>Both attributes are optional, but at least one attribute must be included. Leading zeros (0) are optional. The shortcode’s behaviour depends on which attributes are used:</p>
<ul>
<li><code>show</code> only – Marked content is initially not visible, then appears <code>mm</code> minutes and <code>ss</code> seconds after loading with a <code>fff</code> millisecond fade-in.</li>
<li><code>hide</code> only – Marked content is initially visible, then disappears <code>mm</code> minutes and <code>ss</code> seconds after loading with a <code>fff</code> millisecond fade-out.</li>
<li><code>show</code> and <code>hide</code> – Marked content is initially not visible, then appears according to the values set in <code>show</code>, then disappears according to the values set in <code>hide</code>.</li>
</ul>
<p>Your users must have JavaScript enabled for this shortcode to work.</p>
<p><strong>The timed-content-server shortcode</strong></p>
<pre><code>[timed-content-server show="datetime" hide="datetime" debug="true|false|when_hidden"]Example Text[/timed-content-server]
</code></pre>
<ul>
<li><code>show</code> – Specifies the date/time when the marked content should start being included on the web page.</li>
<li><code>hide</code> – Specifies the date/time after which the marked content should stop being included on the web page.</li>
<li><code>debug</code> – If <code>true</code>, adds some debugging statements to the web page as HTML comments. If <code>when_hidden</code>, the debugging statements are added only when the content is hidden. Defaults to <code>false</code>.</li>
</ul>
<p>The date and time are expected to be yyyy-mm-dd HH:MM (similar to ISO 8601), for example <code>2019-04-07 15:30</code> for April 7, 2019, 15:30. For backward compatiblity old “human readable” date formats should also work, but these should not be used any longer!</p>
<p>In addition you can provide a timezone in the date/time parameter either as name or as offset like <code>2019-04-07 15:30 America/Chicago</code> or <code>2019-04-07 15:30 +0200</code>. If you do not provide a timezone, the WordPress timezone setting will be used as default.</p>
<p>Both <code>show</code> and <code>hide</code> attributes are optional, but at least one attribute must be included. The shortcode’s behaviour depends on which attributes are used:</p>
<ul>
<li><code>show</code> only – Marked content is outputted only after the date/time set here.</li>
<li><code>hide</code> only – Marked content is outputted only before the date/time set here.</li>
<li><code>show</code> and <code>hide</code> – Marked content is outputted only during the time period defined by the <code>show</code> and <code>hide</code> attributes.</li>
</ul>
<p><strong>The timed-content-rule shortcode</strong></p>
<pre><code>[timed-content-rule id="{rule_id}|{rule_name}"]Example Text[/timed-content-rule]
</code></pre>
<p>You can find the correct shortcode from the Timed Content Rules overview page, or use the TinyMCE dialog.</p>
<p><strong>Testing server side rules</strong></p>
<p>For testing the behaviour of server side rules at specific times, you may use the GET parameter <code>tctest</code> in an URL, followed by date and time in the format <code>YYYY-MM-DD+hh:mm:ss</code>. This works only you are logged in with a user which has the right to edit the displayed page or post. For example: <code>http://mysite.example?tctest=2018-02-10+19:16:00</code> will show the content as if it was February 10, 2018 at 19:16.</p>
<h3>Developer Documentation</h3>
<p><strong>Action hooks</strong></p>
<pre><code>add_action( "timed_content_server_show", "{function_name}", {priority_level}, 4 );
</code></pre>
<p>Fired when the <code>[timed-content-server]</code> shortcode is encountered <em>AND</em> the content is to be displayed based on the shortcode’s show/hide attributes.  Functions using this hook should accept the following arguments in order:</p>
<ul>
<li><code>$post_id</code> – the ID of the currently displayed Post/Page</li>
<li><code>$show</code> – the value of the <code>show</code> attribute. If not set, defaults to “1970-Jan-01 00:00:00 +000”</li>
<li><code>$hide</code> – the value of the <code>hide</code> attribute. If not set, defaults to “2038-Jan-19 03:14:07 +000”</li>
<li>
<p><code>$content</code> – The content enclosed by the shortcode</p>
<p>add_action( “timed_content_server_hide”, “{function_name}”, {priority_level}, 4 );</p>
</li>
</ul>
<p>Fired when the <code>[timed-content-server]</code> shortcode is encountered <em>AND</em> the content is to be hidden based on the shortcode’s show/hide attributes.  Functions using this hook should accept the following arguments in order:</p>
<ul>
<li><code>$post_id</code> – the ID of the currently displayed Post/Page</li>
<li><code>$show</code> – the value of the <code>show</code> attribute. If not set, defaults to “1970-Jan-01 00:00:00 +000”</li>
<li><code>$hide</code> – the value of the <code>hide</code> attribute. If not set, defaults to “2038-Jan-19 03:14:07 +000”</li>
<li>
<p><code>$content</code> – The content enclosed by the shortcode</p>
<p>add_action( “timed_content_rule_show”, “{function_name}”, {priority_level}, 3 );</p>
</li>
</ul>
<p>Fired when the <code>[timed-content-rule]</code> shortcode is encountered <em>AND</em> the content is to be displayed based on the Timed Content Rule’s properties.  Functions using this hook should accept the following arguments in order:</p>
<ul>
<li><code>$post_id</code> – the ID of the currently displayed Post/Page</li>
<li><code>$rule_id</code> – the ID of the Timed Content Rule being called. Use <code>get_post_meta( $rule_id )</code> to get the Rule’s properties.</li>
<li>
<p><code>$content</code> – The content enclosed by the shortcode</p>
<p>add_action( “timed_content_rule_hide”, “{function_name}”, {priority_level}, 3 );</p>
</li>
</ul>
<p>Fired when the <code>[timed-content-rule]</code> shortcode is encountered <em>AND</em> the content is to be hidden based on the Timed Content Rule’s properties.  Functions using this hook should accept the following arguments in order:</p>
<ul>
<li><code>$post_id</code> – the ID of the currently displayed Post/Page</li>
<li><code>$rule_id</code> – the ID of the Timed Content Rule being called. Use <code>get_post_meta( $rule_id )</code> to get the Rule’s properties.</li>
<li><code>$content</code> – The content enclosed by the shortcode</li>
</ul>
<p><strong>Filter hooks</strong></p>
<pre><code>timed_content_filter
</code></pre>
<p>Filter for any content enclosed by a Timed Content shortcode.  Implements the same filters as <code>the_content</code>:</p>
<ul>
<li><code>wptexturize</code></li>
<li><code>convert_smilies</code></li>
<li><code>convert_chars</code></li>
<li><code>wpautop</code></li>
<li><code>prepend_attachment</code></li>
<li>
<p><code>do_shortcode</code></p>
<p>timed_content_filter_override</p>
</li>
</ul>
<p>Replaces the <code>timed_content_filter</code> with another pre-existing filter to use for any content enclosed by a Timed Content shortcode.  Any function hooked into this filter must return the name of a filter (as a string).</p>


Timed Content

This code is an integral part of one of my websites, and simplified the way I had to structure the information.
Instead of a shortcode-based solution with many subpages, this plugin does all that already.
It has a neat debugging function, which I used just once to see how the logic was reasoning.
Very well done! The people of Gjesdal thank you ;)

Brilliant.

A realy nice job..!
Congratulation for this work.

A realy nice job

Plugin to show or hide portions of a Page or Post based on specific date/time characteristics.

Jih Schedular vs Timed Content