Scott Reilly

<p>Easily keep track of the last time you interacted with your contacts.</p>
<p><strong>NOTE: This plugin is currently considered experimental. The implementation and/or interface may change, and features may be added or removed. Attempts will be made to ensure data viability through subsequent releases but is not guaranteed. Not recommended for use on a live production site.</strong></p>
<p>This plugin allows for contacts and contact groups to be imported from Google Contacts (and in future releases, other contact services) into a WordPress installation. The contacts can then be managed to keep track of the details about your interactions with each contact. You can record:</p>
<ul>
<li>Date you contacted the person</li>
<li>The method used to contact the person (email, IM, phone, in person)</li>
<li>A brief note about the interaction (optional)</li>
</ul>
<p>Links: <a href="http://coffee2code.com/wp-plugins/last-contacted/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/extend/plugins/last-contacted/" rel="ugc">Plugin Directory Page</a> | <a href="http://coffee2code.com" rel="nofollow ugc">Author Homepage</a></p>
<h3>Credits</h3>
<p>Thanks to (PC.DE)[http://pc.de/icons/] for the Berlin icons used by the plugin.</p>
<p>Thanks to <a href="http://p.yusukekamiyamane.com/" rel="nofollow ugc">Yusuke Kamiyamane</a>, by way of <a href="http://randyjensenonline.com/thoughts/wordpress-custom-post-type-fugue-icons/" rel="nofollow ugc">Randy Jensen</a>, for the Fugue icons used in the menus.</p>
<h3>TODO</h3>
<h4>BUGS/MINOR</h4>
<ul>
<li>Properly report failed OAuth authentication</li>
<li>Extract import stuff from LastContacted and put into dedicated class</li>
<li>Remove non-sprited versions of sprited icons</li>
<li>Dashboard widget: reinstate hide contact button for dashboard</li>
</ul>
<h4>ENHANCEMENTS</h4>
<ul>
<li>Prefix all CSS classes with “lc_”</li>
<li>Summarize stats for each import (when manually performed) (i.e. X groups added/removed, X contacts added/removed)?</li>
<li>Expose date for when group/contact first got imported?</li>
<li>Expose name of contact source for each contact?</li>
<li>Require registration of contact services (rather than having Google Contacts assumed)</li>
<li>Use wp_remote_<a href="" rel="nofollow ugc">get|post</a> methods to contact Google</li>
<li>Display time since rather than date of last contact? (“5 days ago” vs “2011-11-01”)</li>
<li>Pseudo-cron (or at least expire) knowledge about contacts not having Gravatar</li>
</ul>
<h4>FEATURES</h4>
<ul>
<li>Allow access to contact history beyond most recent (popup? embedded listing that needs to be expanded?)</li>
<li>Show multiple email addresses for contact if there are more than one?</li>
<li>Support multiple contact sources</li>
<li>Recognize a contact from across multiple contact sources
<ul>
<li>Handle name collisions (may be same or different person)</li>
<li>Handle same contact with different name under each source (perhaps via manual merge capability)</li>
</ul>
</li>
<li>Sparklines for frequency of contacting per contact</li>
<li>Support multiple users : either each user manages their own contacts (walled gardens) or one user is designated the master and all users share in contacting that person’s contacts (community garden) (i.e. so it can be a team tool)</li>
<li>Support addition (and removal) of contact methods</li>
</ul>


Last Contacted

Easily keep track of the last time you interacted with your contacts.

<p>Though it is typically an individually configurable aspect of WordPress, there are times when forcing a single admin color scheme upon all users of a site can be warranted, such as to:</p>
<ul>
<li>Provide a unique backend color scheme for multiple sites used by the same set of users to reinforce the difference between the sites.</li>
<li>Clearly denote backend differences between a production and staging/test instance of a site. Especially given that in this situation with the same plugins active and often the same data present, it can be easy to get mixed up about what site you’re actually on.</li>
<li>Force a site brand-appropriate color scheme.</li>
<li>Crush the expression of individuality under your iron fist.</li>
</ul>
<p>Additionally, the plugin removes the “Admin Color Scheme” profile setting from users who don’t have the capability to set the admin color scheme globally since being able to set its value gives them the false impression that it may actually apply.</p>
<p>Links: <a href="https://coffee2code.com/wp-plugins/force-admin-color-scheme/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/force-admin-color-scheme/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/force-admin-color-scheme/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a></p>
<h3>Hooks</h3>
<p>The plugin is further customizable via one filter. Typically, code making use of filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain).</p>
<p><strong>c2c_force_admin_color_scheme (filter)</strong></p>
<p>The ‘c2c_force_admin_color_scheme’ filter allows you to set or override the forced admin color scheme. Use of the constant (“) takes priority over the filtered value, but the filtered value takes priority over the value set via the admin.</p>
<p>Arguments:</p>
<ul>
<li>$color (string): The name of the admin color scheme. If an empty string is returned, then the plugin will behave as if no forced admin color scheme has been defined.</li>
</ul>
<p>Example:</p>
<pre><code>/**
 * Sets a forced admin color scheme based on user. Admins get one color scheme, whereas everyone else gets another.
 *
 * @param string $color The current forced admin color scheme. Empty string indicates no forced admin color scheme.
 * @return string
 */
function my_c2c_force_admin_color_scheme( $color ) {
    return current_user_can( 'manage_options' ) ? 'sunrise' : 'coffee';
}
add_filter( 'c2c_force_admin_color_scheme', 'my_c2c_force_admin_color_scheme' );
</code></pre>


Force Admin Color Scheme

Force a single admin color scheme for all users of the site.

Last Contacted vs Force Admin Color Scheme