WP Hide Dashboard http://wphidedash.org Now you see it / Now you don't Sun, 18 May 2014 16:10:26 +0000 en-US hourly 1 http://wordpress.org/?v=4.1 WP Hide Dashboard 2.2 http://wphidedash.org/2012/12/wp-hide-dashboard-22/ http://wphidedash.org/2012/12/wp-hide-dashboard-22/#comments Thu, 06 Dec 2012 21:30:56 +0000 http://wphidedash.org/?p=289 With the release of WordPress 3.5 right around the corner, version 2.2 of WP Hide Dashboard is now available for download from the wordpress.org Extend section. Those of you who have the plugin installed should see an upgrade notice show up in your WordPress dashboard.

Continue reading ]]>
With the release of WordPress 3.5 right around the corner, version 2.2 of WP Hide Dashboard is now available for download from the wordpress.org Extend section. Those of you who have the plugin installed should see an upgrade notice show up in your WordPress dashboard.

The new version of the plugin has some significant changes to it:

  • Support for WordPress version 3.3 and earlier removed.
  • Reworked code to remove fatal error issue, ensure compatibility with WordPress 3.4 and 3.5.
  • Reworked how Multisite user scenarios (assigned to no blogs/1 blog/2+ blogs) are handled.

Version 2.2 now requires a minimum of WordPress 3.4 for it to work.

A critical issue was brought to my attention a few days ago regarding version 2.1 causing a fatal error with WordPress 3.5. I have reworked the code in version 2.2 to take care of that issue, and included support for WordPress 3.4 so that you can upgrade now and not lose functionality.

If you are running version 2.1 of the plugin, you must upgrade to version 2.2 before you upgrade your WordPress install to version 3.5, once it is released, in order to avoid the fatal error issue.

There have been significant changes made to the admin bar (now called the toolbar) since the last plugin release. The code has been rewritten to incorporate those changes, and some extra goodies added, such as removal of the WordPress logo menu, and better handling of different user scenarios in Multisite.

Comments/questions/support requests should be posted on the Version 2.2 page. Please make sure you read the Support page before posting so that you provide me with the information I need to help you.


Copyright © 2015 WP Hide Dashboard - All Rights Reserved.
This feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is guilty of copyright infringement. Please send an email to legal@kimparsell.com with the link of the offending website so I can take appropriate action. Thank you.


]]>
http://wphidedash.org/2012/12/wp-hide-dashboard-22/feed/ 0
Best Practice For Adding Custom Functions http://wphidedash.org/2011/04/best-practice-for-adding-custom-functions/ http://wphidedash.org/2011/04/best-practice-for-adding-custom-functions/#comments Sat, 02 Apr 2011 18:10:40 +0000 http://kpdesign.net/wphidedash/?p=262 "Where should I put custom functions...in my theme or in a plugin?"

That's a good question. I've seen lots of WordPress tutorials, and even the WordPress Codex, recommend adding custom functions to your theme's functions.php file.

While that method does work, it can also cause problems when you change your theme to something else. The new theme won't have that code in its functions.php file, and your custom functionality will just...you guessed it...stop functioning.

Continue reading ]]>
"Where should I put custom functions...in my theme or in a plugin?"

That's a good question. I've seen lots of WordPress tutorials, and even the WordPress Codex, recommend adding custom functions to your theme's functions.php file.

While that method does work, it can also cause problems when you change your theme to something else. The new theme won't have that code in its functions.php file, and your custom functionality will just...you guessed it...stop functioning.

In early February 2011, Justin Tadlock wrote an awesome tutorial about a great alternative to using the functions.php file - Creating a custom functions plugin for end users.

Go read it, then come back here and I'll walk you through adding the first custom code snippet to your shiny new custom functions plugin.

Step 1: Create your custom plugin

I've created a blank plugin file along the same lines as the sample plugin in Justin's tutorial. Copy the following into a blank text file and save it as my-custom-functions.php:

<?php
/*
Plugin Name: My Custom Functions
Plugin URI: Your site URL here
Description: A simple plugin that contains all the awesome little functions that I use to make my site work <strong>my way.</strong>
Author: Your name here
Author URI: Your site URL here
Version: 0.1
*/
 
/* Disallow direct access to the plugin file */
 
if (basename($_SERVER['PHP_SELF']) == basename (__FILE__)) {
	die('Sorry, but you cannot access this page directly.');
}
 
/** START ADDING CODE BELOW THIS LINE **/
 
/** STOP ADDING CODE NOW**/
 
/* That's all folks! */
 
?>

Make sure to change the sample text for the plugin URI, author name and author URI so that it reflects your information.

Step 2: Let's add code!

For the example, I'll add code to only show the admin bar when in the WordPress admin area. Hat tip goes to one of my commenters, Clay Campbell, for the idea.

Add the following directly after the /** START ADDING CODE... **/ line:

/* URL: http://wphidedash.org/2011/04/best-practice-for-adding-custom-functions/
    Set the admin bar so it only shows in the admin area, not the public-facing site.
    This overrides the admin bar settings on the profile page for all users. */
 
function my_custom_admin_bar_setting() {
	if (is_admin())
		return TRUE;
	else
		return FALSE;
}
 
add_filter ('show_admin_bar', 'my_custom_admin_bar_setting');

This function will override any admin bar settings that you or other users make on your profiles. It works in both WordPress single user and WordPress Multisite (activated on one site, network-activated, or installed in the mu-plugins folder to run network-wide).

When adding custom functions that you've found on the web, you might include the URL where you found the code in the opening comment, along with a short description of what it does, so you don't have to do the "needle/haystack" search if the code doesn't work right.

Step 3: Upload/activate your custom functions plugin

Justin's tutorial suggests using either the /wp-content/plugins/ folder or the /wp-content/mu-plugins/ folder to house your shiny new custom plugin.

If you aren't familiar with the mu-plugins folder, I suggest reading both the explanation Justin has in his tutorial (see Option #1), and the awesome explanation from Andrea Rennick of WordPress Must-Use Tutorials - What is the mu-plugins folder? - before choosing this option. A word of caution - any plugin placed there runs automatically (no activation required), and, for plugins downloaded from wordpress.org, there are no update notifications if a new version of that plugin is released. If you aren't comfortable with that, then you can place it in the regular plugins folder (Option #2), and activate it like any other plugin.

Wrapping things up

And there you have it - a great way to house all of your custom functions AND ensure that they'll keep on working, no matter how many times you upgrade or switch your theme.

Who said best practices have to be hard?


Copyright © 2015 WP Hide Dashboard - All Rights Reserved.
This feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is guilty of copyright infringement. Please send an email to legal@kimparsell.com with the link of the offending website so I can take appropriate action. Thank you.


]]>
http://wphidedash.org/2011/04/best-practice-for-adding-custom-functions/feed/ 0
WP Hide Dashboard 2.1 http://wphidedash.org/2011/02/wp-hide-dashboard-21/ http://wphidedash.org/2011/02/wp-hide-dashboard-21/#comments Wed, 23 Feb 2011 15:11:03 +0000 http://wp-church.com/wphd/?p=227 With the announcement of the release of WordPress 3.1, version 2.1 of WP Hide Dashboard is now available for download from the wordpress.org Extend section. Those of you who have the plugin installed should see an upgrade notice show up in your WordPress dashboard.

Continue reading ]]>
With the announcement of the release of WordPress 3.1 a short while ago, version 2.1 of WP Hide Dashboard is now available for download from the wordpress.org Extend section. Those of you who have the plugin installed should see an upgrade notice show up in your WordPress dashboard.

The new version of the plugin has some significant changes to it:

  • Support for WordPress version 2.9 and 3.0 removed.
  • Support for roles other than Subscriber removed.
  • Reworked code for removing Personal Options section on Profile page.
  • Added support for removing Dashboard links in new admin bar.
  • Added support for WordPress Multisite (mu-plugins and network-activation capable).

In order to continue to keep the code "lean and mean" and take advantage of the new functions available in WordPress 3.1, I have removed support for WordPress versions 2.9 and 3.0. Version 2.1 now requires a minimum of WordPress 3.1 for it to work.

I also removed code to remove menu items for roles other than Subscriber. While I appreciate that some users need this type of functionality for other roles, most don't require it, so I don't want to bloat the plugin with unnecessary code for the majority of users.

One issue that seemed to come up often with version 2.0 was the code that removed the Personal Options section on the Profile page. Whether it was a conflict with other plugins or the fact that the additional javascript file wasn't uploaded to the server, it caused concern for too many users. I have reworked that code so that it is all inside the main plugin file now.

However, the issue that caused a conflict with other plugins still remains. In order to hide the profile page until the javascript is able to hide the Personal Options section, I have to use #your-profile { display: none; }. Other plugins use the same code, and the resulting combination is that the Profile page won't display at all. I have submitted a Trac ticket, requesting that a class (personal-options) be assigned to the h3 and table that are in that section so it can be hidden with just CSS; however, it won't be considered for inclusion until WordPress 3.2.

WordPress 3.1 Admin BarA new feature in WordPress 3.1 is the admin bar. If you've had a blog on wordpress.com, then you know what the admin bar is. The screenshot to the right shows you what a subscriber will see if the admin bar is enabled in WordPress (single mode). The same links show up in WordPress Multisite plus a My Sites menu (see screenshots). I've added code to hide the Dashboard link and only show the Edit My Profile link if the user is on the public-facing site, as well as reworking the My Sites menu in Multisite to only show links to the public-facing sites a user is assigned to.

Last, but not least, I've added support for WordPress Multisite to the plugin. It now works installed in the /wp-content/plugins/ folder and network-activated or just activated on one site in the network, as well as working when installed in the /wp-content/mu-plugins/ folder.

All that translates to lots of goodies in this version. Comments/questions/support requests should be posted on the Version 2.1 page.

I'd like to give a big shout-out to my friend Ipstenu for beta-testing the plugin for me while I was developing this version. Thanks so much for all your help!

Now, go upgrade WordPress to 3.1, then upgrade WP Hide Dashboard to 2.1, and enjoy!


Copyright © 2015 WP Hide Dashboard - All Rights Reserved.
This feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is guilty of copyright infringement. Please send an email to legal@kimparsell.com with the link of the offending website so I can take appropriate action. Thank you.


]]>
http://wphidedash.org/2011/02/wp-hide-dashboard-21/feed/ 0
What WP Hide Dashboard Version Are You Using? http://wphidedash.org/2011/02/what-wphd-version-are-you-using/ http://wphidedash.org/2011/02/what-wphd-version-are-you-using/#comments Tue, 22 Feb 2011 15:00:00 +0000 http://kpdesign.net/wphidedash/?p=256 WP Hide Dashboard Active Versions a/o 2-20-2011I was checking out the wordpress.org download stats for WP Hide Dashboard, in particular the active version stats graph.

As of 20 February 2011, 57.5% of the active plugin installs are running the latest version (2.0). That leaves 42.5% of the active plugin installs running older versions of the plugin (1.3, 1.4, and 1.5).

While I've noticed a steady increase in the percentage of active plugin installs running version 2.0 in the past few weeks, the number of installs running older versions causes me a bit of concern.

Continue reading ]]>
WP Hide Dashboard Active Versions a/o 2-20-2011I was checking out the wordpress.org download stats for WP Hide Dashboard, in particular the active version stats graph.

As of 20 February 2011, 57.5% of the active plugin installs are running the latest version (2.0). That leaves 42.5% of the active plugin installs running older versions of the plugin (1.3, 1.4, and 1.5).

While I've noticed a steady increase in the percentage of active plugin installs running version 2.0 in the past few weeks, the number of installs running older versions causes me a bit of concern.

For those of you that are running the latest version - bravo! It means you are actively keeping both your WordPress install and your plugins updated.

But, those of you that are running an older version of the plugin - why? I can think of a few possible reasons:

  1. I'm running an older version of WordPress and I'm afraid my site will break if I upgrade the plugin or WordPress.
  2. It's just a simple plugin - there's really no reason to upgrade it, is there?
  3. I've customized the plugin and I don't want to lose my changes.

If you fall into group #1, I strongly encourage you to upgrade BOTH WordPress and the plugin. Running older versions of WordPress and plugins opens up your site to security weaknesses and the possibility of being hacked.

Group #2 - it may be a simple plugin, but yes, you do need to upgrade it. New versions are released to correct errors, add features, and take advantage of new WordPress goodies. Go ahead and press the upgrade link - I promise, it won't bite.

Now for group #3. I know that many of you have customized your version of WP Hide Dashboard so that it applies to other roles beside Subscriber, and to remove links that some plugins have added to the admin menu. It's humming right along, doing what you want it to. You're afraid of losing your changes. However, you're also missing out on changes to the plugin made to take advantage of new WordPress functionality, and new plugin features that have been added in recent versions.

So...which group do you fall into and why?


Copyright © 2015 WP Hide Dashboard - All Rights Reserved.
This feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is guilty of copyright infringement. Please send an email to legal@kimparsell.com with the link of the offending website so I can take appropriate action. Thank you.


]]>
http://wphidedash.org/2011/02/what-wphd-version-are-you-using/feed/ 0
30,000 and Counting http://wphidedash.org/2010/12/30000-and-counting/ http://wphidedash.org/2010/12/30000-and-counting/#comments Fri, 17 Dec 2010 23:43:54 +0000 http://wp-church.com/wphd/?p=225 Another milestone was reached today - 30,000 downloads. It was 6 months ago that the plugin hit 20,000 downloads. Stats from wordpress.org look pretty awesome!

Continue reading ]]>
Another milestone was reached today - 30,000 downloads. It was just 6 months ago that the plugin hit 20,000 downloads. Stats from wordpress.org look pretty awesome!

Download Stats From wordpress.org 12-17-2010

Thank you to everyone who has downloaded and installed the plugin, blogged about it, linked to it, and supported it.


Copyright © 2015 WP Hide Dashboard - All Rights Reserved.
This feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is guilty of copyright infringement. Please send an email to legal@kimparsell.com with the link of the offending website so I can take appropriate action. Thank you.


]]>
http://wphidedash.org/2010/12/30000-and-counting/feed/ 0
WordPress 3.0 and WP Hide Dashboard 2.0 http://wphidedash.org/2010/06/wordpress-30-and-wp-hide-dashboard-20/ http://wphidedash.org/2010/06/wordpress-30-and-wp-hide-dashboard-20/#comments Thu, 17 Jun 2010 23:27:29 +0000 http://kpdesign.dev/?p=105 WP Hide Dashboard 20K DownloadsThis is an awesome week for WordPress and the WP Hide Dashboard plugin.

First, the WP Hide Dashboard plugin hit the 20,000 download mark on the morning of June 16th, just 8 months after hitting the 10,000 download mark last October. I am still truly amazed at the support this simple little plugin has received since it was released in October 2008. Lots of new features have been added since then, and there's more goodness in the latest version, 2.0, which was released just a short while ago.

Continue reading ]]>
WP Hide Dashboard 20K DownloadsThis is an awesome week for WordPress and the WP Hide Dashboard plugin.

First, the WP Hide Dashboard plugin hit the 20,000 download mark on the morning of June 16th, just 8 months after hitting the 10,000 download mark last October. I am still truly amazed at the support this simple little plugin has received since it was released in October 2008. Lots of new features have been added since then, and there's more goodness in the latest version, 2.0, which was released just a short while ago.

Second, the release day of the much-anticipated WordPress 3.0 is finally here! This version is the culmination of 6 months of heads-down development, testing, bug whacking, more testing, two betas and 3 release candidates. There were 218 people who made contributions to the 3.0 release cycle, along with the countless testers reporting issues on the wp-testers mailing list and Trac. Check out the video below for a tour of all the cool new features. As Matt Mullenweg said, it truly does take a "village" to build something this awesome!

With the announcement of the release of WordPress 3.0, version 2.0 of WP Hide Dashboard is now available for download from the wordpress.org Extend section. Those of you who have the plugin installed should see an upgrade notice show up in your WordPress dashboard.

The new version of the plugin has some significant changes to it. Enough has changed to warrant this being considered a major release; hence the jump from 1.5 to 2.0 in the version number.

In order to keep the code "lean and mean", I have removed support for WordPress versions 2.5 - 2.8. Version 2.0 now requires a minimum of WordPress 2.9 for it to work. I have done this to encourage people to upgrade their WordPress installs.

Far too many people are running older versions of WordPress and other plugins, as they are afraid to upgrade, and they end up getting hacked. As a plugin author, I don't want to contribute to the problem; hence the change to pull backward compatibility for older WordPress versions from the plugin.

I have also updated the menu removal code to be compatible with WordPress 3.0 in single user mode. I have not done any testing of the plugin with WordPress 3.0 in multisite mode, but plan to do that in the next several weeks. I'll keep you posted on what I find out.

Last, but not least, there is a new feature in version 2.0: the removal of the entire Personal Options section from the Profile page for Subscribers along with the Dashboard link, etc. Major thanks go to Matthew Pollotta of Large Interactive for allowing me to incorporate the functionality from his Hide Personal Options plugin into WP Hide Dashboard. More features FTW!

I've updated the post for the WP Hide Dashboard plugin with the latest information, so check out the changelog for more details. If you have any issues with the new version, please post them there.

Now, go upgrade your WordPress installs and enjoy all of the 3.0 awesomeness!


Copyright © 2015 WP Hide Dashboard - All Rights Reserved.
This feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is guilty of copyright infringement. Please send an email to legal@kimparsell.com with the link of the offending website so I can take appropriate action. Thank you.


]]>
http://wphidedash.org/2010/06/wordpress-30-and-wp-hide-dashboard-20/feed/ 0
WP Hide Dashboard: One Year In http://wphidedash.org/2009/10/wp-hide-dashboard-one-year-in/ http://wphidedash.org/2009/10/wp-hide-dashboard-one-year-in/#comments Tue, 20 Oct 2009 10:00:50 +0000 http://kpdesign.dev/?p=85 Today marks the one year anniversary since I released the first version of the WP Hide Dashboard plugin.

WP Hide Dashboard Extend

The plugin started out as a hack to fill a need that I had on a website that I was developing. I tried the version that Thomas Schneider had released as an add-on to his Role Manager plugin, but it required that Role Manager be installed for it to work. This was the only functionality that I needed, so I set out to make it work on its own.

Continue reading ]]>
Today marks the one year anniversary since I released the first version of the WP Hide Dashboard plugin.

WP Hide Dashboard Extend

The plugin started out as a hack to fill a need that I had on a website that I was developing. I tried the version that Thomas Schneider had released as an add-on to his Role Manager plugin, but it required that Role Manager be installed for it to work. This was the only functionality that I needed, so I set out to make it work on its own.

At the time I only planned to use it on my websites, but during the research that I had done for the fix, I found so many people who were needing the same thing and didn't want to bloat their WordPress install with an unneeded plugin just to obtain this functionality. That convinced me that I should release it publicly.

So I went to the wordpress.org Extend section on 10/18/2008, and applied for an account to set up the plugin on their repository. On 10/19/2008 my request was approved, and on 10/20/2008 WP Hide Dashboard was born.

WP Hide Dashboard Trac, Version 1.0

Now, one year later, the plugin has been through four revisions since the initial release to add functionality and ensure that it continued to work with the latest version of WordPress. I have helped people rework the plugin to extend the functionality beyond the Subscribers role, including hiding other menu items for both WordPress core and other plugins. There have been some situations where I was unable to find a resolution for a user's issue, but the majority of issues have been resolved successfully.

Downloads for the plugin are currently at almost 10,800, and still climbing. The average number of daily downloads is around 30, with obvious spikes whenever a new version has been released. The image below shows the download stats from wordpress.org as of the time of this post:

WP Hide Dashboard Download Stats

To be honest, I never expected the plugin to have the response that it has. I knew that it was needed by some people, but to have almost 11,000 downloads in a year's time is awesome.

I plan to continue developing the plugin, and have already done preliminary testing on the nightly builds of WordPress 2.9 - so far, so good. I'll also be testing against the WordPress 2.9 Beta and RC versions when they are released, and will update the plugin if needed.

If you've used the plugin, like it, and would like to help me celebrate, head on over to the WP Hide Dashboard plugin page on wordpress.org and rate the plugin (there's only been 14 people give it a rating in all of those downloads).

Thank you to everyone who has downloaded and installed the plugin, blogged about it, linked to it, and supported it. You rock!


Copyright © 2015 WP Hide Dashboard - All Rights Reserved.
This feed is for personal non-commercial use only. If you are not reading this material in your news aggregator, the site you are looking at is guilty of copyright infringement. Please send an email to legal@kimparsell.com with the link of the offending website so I can take appropriate action. Thank you.


]]>
http://wphidedash.org/2009/10/wp-hide-dashboard-one-year-in/feed/ 1