Plugin: Network Plugin Overview

I wrote this little plugin for WordPress Networks allowing super admins to easily see which plugins are being used on which sites in a wordpress network.

Download

> ยป WordPress.org Plugins: Network Plugin Overview

Description

Quickly view all your plugins and see which sites are using them, which are network-wide, and which plugins are not active on any sites at all.

Installation

1. Upload the /network-plugin-overview/ folder into the /wp-content/plugins/ directory, or add via the “Add New” option in /wp-admin/plugins

  1. Activate the plugin through the ‘Plugins’ menu in WordPress
  2. Navigate to “Plugin Overview” page in the admin sidebar

Frequently Asked Questions

Why would I need this?

> I personally needed it to delete dated/forgotten plugins that posed a security risk by keeping around. Having a large number of different sites in a network, it’s sometimes hard to determine which plugins are being used where. This plugin clearly highlights which plugins are not being used at all….if you are not using a specific plugin, delete it from the system.

Can I use it on a single installation instead of a network?

> No, just go to “Plugins” in the admin.

Screenshot

Wordpress Network Plugin Overview

Changelog

Version 1.0

> Nov 25, 2012

Public Launch

Suggestions / Notes

Please post any comments or questions below.

WordPress Simple Cronjobs

WordPress makes it super simple to run cronjobs.. To add one, just place the following code in your functions.php file and change the function/action prefix’s to your relevant plugin name/functions.

A little break down for those unfamiliar: the first action runs myplugin_schedule_cron() on each load. If your cronjob (myplugin_cronjob) is not registered, it’s scheduled into WordPress’s cron and becomes a hook. Once it’s registered/schedualed with WordPress, the second action myplugin_cronjob is usable and runs your cronjob function (myplugin_cron_function).

If you want your cronjob to occur less frequent than ‘daily’, you need to add a additional timespan. Since what I’m writting this for has dynamic timespans, I’ve added several intervals for weekly, monthly, quaterly, biyearly, and yearly cronjobs:

If you’re uncertain if your cron function is working and want to test it, you can uncomment the third action and refresh the page (to run what WordPress cronjob will run on it’s intervals). If you’re uncertain if your cronjob is actually scheduled you can install Cron View, a plugin that displays the available schedules and the scheduled tasks.

Get Embed from Youtube or Vimeo URL

Here’s a function I’ve used on quite a few times. If you have the URL of a Youtube video, from a Custom Meta Field, or a field in a Custom Settings Page or custom meta box, you can run that user-supplied URL through this function and get the source code for an embedded video:field

I’ve also done this for Vimeo videos, below is from a project I worked on using Vimeo’s API, untested but it should work:

If your user supplied URL could be either of the two, strpos() or another find function could detect which and use either of the above.

How To Make A Responsive Site

Every since the tablet boom in the last two or so years, responsive design is the only way to make sites.

As an owner of a tablet and heavy web user, it makes a world of difference on my impression of a site (and thus a company/organization) when you visit a site that’s responsive. It’s butt hurt going to (a) a full size site where you have to awkwardly zoom-in, wait for 9000 things to load, and awkwardly scroll down in a straight line with the article. Worse than loading an unresponsive full size site on a tablet is a site detecting the large iPad to be a “mobile” device, thus redirecting you to a plain-text-2005-mobile site with images no bigger than your pinky finger nail, and no visual interest at all, and no care into textography for large-mobile devices.

Responsive design is easy, and for reference here’s the framework for detecting the screen size:

I found using CSS was enough, but sometimes loading bigger images and extra things is a pain, so you can use some basic Javascript to detect the size and change things up.

To make sure the viewport is the width of the device, HTML meta tag is used:

On a foot note, to further enhance the responsive experience, optimizing the site for the visitors screen-size, I use tools like LazyLoad to ensure the site loads speedy on slower 3/4G connections, Swipey for scrolling horizontal images, and Off-canvas-navigation easy app-like navigation.