Code: Getting rid of the duplicate submenu with add_menu_page and add_submenu_page

So  I ran across an issue today when creating a custom admin menu and submenu items. I wanted to have a submenu item in the menu that linked to the main admin menu page, but did not have the same anchor as the parent. I kept running into this:   You can see that, since I’m currently… Continue reading Code: Getting rid of the duplicate submenu with add_menu_page and add_submenu_page

No matter what else you may pay for when you hire a developer, you will always be paying for these two things:

1) Their time. Every developer I know is busy, including myself. That means, in order for something to be good enough for them to stop whatever else it is that they are working on, you need to be willing to make it worth their time. This may be that the project is particularly interesting to them or it may be monetarily. Either way, you will be bidding on their time against any number of other projects that are already attracting their attention.

2) Experience. By hiring a developer, you are making a leap of faith that they know what they are doing. Generally speaking, experience coincides with cost — you won’t find many (if any) experienced developers working for cheap. The market tends to work these things out naturally — an inexperienced developer, overpricing their work, will end up breaking something or getting in over his/her head and will end up getting negative feedback of one form or another and lose clients.

The more you are willing to value these two things in a potential developer, the better the developer you’ll end up with. Anyone can write code, but not everyone comes with the experience and expertise to write good code. If you are  unwilling to apply value to your potential developer’s time and experience, you are unlikely to end up with a very good developer.

Use Bootswatch themes with Museum Core to “skin” your site

I did a writeup on Museum Themes on how to use Bootstrap 3 themes with Museum Core (which this site uses) to get new “skins” for the Core theme. Note: I wouldn’t have even thought of this if it wasn’t for Shawn Wildermuth‘s Bootstrap 3 course on Pluralsight. If you want to check it out, I still have some trial codes to give away over here.

Use Bootswatch themes with Museum Core to “skin” your site – Museum Themes

New Pluralsight Course: User Roles & Capabilities in WordPress

I’ll tell you a secret: up until a few months ago, user roles and permissions in WordPress were a vast, unexplored land of confusing terms (capabilities and — gasp — meta capabilities) and complex relationships. I didn’t know much, but I did know that if you were playing with new user roles or capabilities and messed up… Continue reading New Pluralsight Course: User Roles & Capabilities in WordPress

Theme update and a mad dash to fix broken stuff

So Museum Core was pushed live to the WordPress.org repo today. Of course I immediately switched my blog from the Twenty Fourteen theme I was testing to Core because, you know, it’s my freaking theme. And immediately I ran into some issues. If you are using Core and experience any of these, here are the fixes.… Continue reading Theme update and a mad dash to fix broken stuff

Nginx config with WordPress multisite on DreamHost

Probably I should post this on the DreamHost wiki BUT I wanted to throw this out that I figured out a solution to an issue I was having on WordPress multisite since migrating to nginx… The problem The issue is that, while permalinks were working as expected, images were all broken, particularly when you were on… Continue reading Nginx config with WordPress multisite on DreamHost