susheelhbti

<p><strong>Server Scout</strong> is a tool for server administrators who manage multiple WordPress sites on the same server. Instead of logging into each site one by one, Scout gives you a single dashboard where you can see every WordPress installation on the server and quickly access them.</p>
<h4>What it does</h4>
<ul>
<li>Recursively scans a directory of your choice (e.g. <code>/var/www</code>) for all WordPress installations.</li>
<li>Stores the results in a dedicated database table so the dashboard loads instantly without re-scanning.</li>
<li>Refreshes the stored results automatically in the background (WP-Cron), every 30 minutes by default.</li>
<li>Displays each site’s name, URL, WordPress version, and database prefix.</li>
<li>Lists all administrator users for each site (username + email).</li>
<li>Generates a secure, one-time, 5-minute login link so you can jump straight into any site’s admin area without needing the password.</li>
</ul>
<h4>Who is it for?</h4>
<ul>
<li><strong>VPS / dedicated server owners</strong> managing multiple client or personal WordPress sites.</li>
<li><strong>Developers</strong> running several local or staging environments on one machine.</li>
<li><strong>Agencies</strong> with a fleet of sites on a single server.</li>
</ul>
<h4>How scanning & caching works</h4>
<ol>
<li>The first time you open the dashboard, click <strong>Scan Server</strong>.</li>
<li>Results are written to a <code>{prefix}servsc_sites</code> table — one row per installation.</li>
<li>Every later visit renders straight from that table (no filesystem walk).</li>
<li>A background WP-Cron task re-scans the same root on a schedule so the data stays fresh.</li>
<li>Use <strong>Rescan Now</strong> any time to force an immediate refresh.</li>
</ol>
<h4>How login links work</h4>
<ol>
<li>Click <strong>Generate Login Link</strong> next to any admin user.</li>
<li>A cryptographically signed, one-time token is stored in that site’s database (valid for 5 minutes).</li>
<li>The generated link goes through WordPress’s standard <code>admin-ajax.php</code> endpoint — not a direct PHP file — and includes a nonce for request verification.</li>
<li>Opening the link logs you directly into that site’s admin dashboard.</li>
<li>The token is deleted immediately on first use — it cannot be used twice.</li>
</ol>
<h4>Security</h4>
<ul>
<li>Requires the <code>manage_options</code> capability (Administrator) to use the plugin.</li>
<li>All form submissions are protected with WordPress nonces.</li>
<li>Login links use <code>wp_ajax_nopriv_</code> (WordPress AJAX), include a nonce, and go through <code>admin-ajax.php</code>.</li>
<li>Tokens are HMAC-signed with a per-token secret — cannot be forged.</li>
<li>Scan paths are validated with <code>realpath()</code> before use.</li>
<li>All database queries use prepared statements.</li>
<li>The standard <code>wp_login</code> action is fired on login so security plugins (login limiters, audit logs) are notified.</li>
</ul>
<p><strong>Important:</strong> This plugin is intended for server administrators only. Do not install it on shared hosting environments where you do not control all sites on the server.</p>


Server Scout

Helps server administrators discover and manage all WordPress installations on the same server from a single dashboard.

Scott Reilly

<p>This plugin adds a dynamic, functional clock to the admin bar (at top of all admin pages) to show the server time for the blog. The clock automatically updates as time passes, as you would expect of a digital clock.</p>
<p>This plugin also supports a static mode which puts a timestamp string at the top of all admin pages instead of the dynamic clock. This static admin time widget can be clicked to update the time in-place (without a page reload) to show the new current server time.</p>
<p>Also provided is a “Blog Time” widget providing the same functionality as the admin widget, but for your sidebars. You may also utilize the plugin’s functionality directly within a theme template via use of the template tag <code>c2c_blog_time()</code>.</p>
<p>NOTE: For the front-end widget, if the “Use dynamic clock?” configuration option is unchecked, this plugin generates a timestamp and NOT a clock. The time being displayed is the time of the page load, or if clicked, the time when the widget last retrieved the time. It won’t actively increment time on the display. By default the widget displays a dynamic clock that does increment time.</p>
<p>This is most useful to see the server/blog time to judge when a time sensitive post, comment, or action would be dated by the blog (i.e. such as monitoring for when to close comments on a contest post, or just accounting for the server being hosted in a different timezone). Or, when used statically as a timestamp and not a clock, it can indicate/preserve when the page was loaded.</p>
<p>Thanks to <a href="https://momentjs.com/" rel="nofollow ugc">Moment.js</a> for the JavaScript date handling library.</p>
<p>Links: <a href="https://coffee2code.com/wp-plugins/blog-time/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/blog-time/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/blog-time/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a></p>
<h3>Template Tags</h3>
<p>The plugin provides one template tag for use in your theme templates, functions.php, or plugins.</p>
<h4>Functions</h4>
<ul>
<li><code><?php function c2c_blog_time( $time_format = '', $echo = true ) ?></code><br />
Returns and/or displays the formatted time for the site.</li>
</ul>
<h4>Arguments</h4>
<ul>
<li>
<p><code>$time_format</code> (string)<br />
Optional. PHP-style time format string. See https://www.php.net/manual/en/datetime.format.php for more info. Default is ” (which, unless otherwise modified, uses the default time forat: ‘g:i A’).</p>
</li>
<li>
<p><code>$echo</code> (bool)<br />
Optional. Echo the template info? Default is true.</p>
</li>
</ul>
<h4>Examples</h4>
<ul>
<li>
<p><code><?php // Output the site's current time.<br />
c2c_blog_time();<br />
?></code></p>
</li>
<li>
<p><code><?php // Retrieve the value for use in code, so don't display/echo it.<br />
$site_date = c2c_blog_time( 'M d, Y', false );<br />
?></code></p>
</li>
</ul>
<h3>Hooks</h3>
<p>The plugin exposes four filters for hooking. Code using these filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain). Less ideally, you could put them in your active theme’s functions.php file.</p>
<p><strong>c2c_blog_time (filter)</strong></p>
<p>The <code>'c2c_blog_time'</code> hook allows you to use an alternative approach to safely invoke <code>c2c_blog_time()</code> in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site.</p>
<p>Arguments:</p>
<ul>
<li>same as for <code>c2c_blog_time()</code></li>
</ul>
<p>Example:</p>
<p>Instead of:</p>
<pre><code><?php c2c_blog_time(); ?>
</code></pre>
<p>Do:</p>
<pre><code><?php echo apply_filters( 'c2c_blog_time', '' ); ?>
</code></pre>
<p><strong>c2c_blog_time_format (filter)</strong></p>
<p>The <code>'c2c_blog_time_format'</code> hook allows you to customize the default format for the blog time. By default this is ‘g:i A’ (though this may be different if modified by localization).</p>
<p>Arguments:</p>
<ul>
<li>$format (string): The default format for the blog time.</li>
</ul>
<p>Example:</p>
<pre><code>/**
 * Change the default blog time string
 *
 * @param string $format The default time format.
 * @return string
 */
function change_blog_time_format( $format ) {
    return 'b, g:i A';
}
add_filter( 'c2c_blog_time_format', 'change_blog_time_format' );
</code></pre>
<p><strong>c2c_blog_time_toolbar_widget_for_user (filter)</strong></p>
<p>The <code>c2c_blog_time_toolbar_widget_for_user</code> hook allows you to control if the admin toolbar clock widget should be shown, on a per-user basis. By default the admin toolbar clock is shown to everyone who can see the admin toolbar.</p>
<p>Arguments:</p>
<ul>
<li>$shown (boolean): Whether the admin toolbar clock widget should be shown. Default of true.</li>
</ul>
<p>Example:</p>
<pre><code>/**
 * Only show the admin toolbar clock for the 'boss' user.
 *
 * @param $show bool Status of whether the admin toolbar clock should be shown.
 * @return bool
 */
function restrict_blog_time_widget_appearance( $show ) {
    return 'boss' === get_current_user()->user_login;
}
add_filter( 'c2c_blog_time_toolbar_widget_for_user', 'restrict_blog_time_widget_appearance' );
</code></pre>
<p><strong>c2c_blog_time_active_clock (filter)</strong></p>
<p>The <code>'c2c_blog_time_active_clock'</code> hook returns the boolean value indicating if the Javascript-powered dynamic clock introduced in v2.0 should be enabled or if instead the v1.x era behavior of a static timestamp that can be clicked to update the timestamp via AJAX should be enabled. By default the dynamic clock is enabled.</p>
<p>Arguments:</p>
<ul>
<li>$allow (boolean): Boolean indicating if the admin widget should be a dynamic clock. Default is true.</li>
</ul>
<p>Example:</p>
<pre><code>// Disable the dynamic clock and use the static timestamp (whcih can be clicked to update the time via AJAX) instead.
add_filter( 'c2c_blog_time_active_clock', '__return_false' );
</code></pre>


Blog Time

Display the time according to your blog via an admin toolbar widget, a sidebar widget, and/or a template tag.

Server Scout vs Blog Time