WordCamp Moscow 2016

I’m Konstantin Kovshenin, a WordPress core contributor, ex-Automattician, public speaker and consultant, enjoying life in the rainy UK. I blog about tech, WordPress and DevOps.

I do code review, training and consulting on WordPress performance, scaling and security. Schedule a call if you’re interested.

Subscribe to my newsletter and follow me on Twitter.

Recent Blog Posts

Meet the Brand New CodePoet!

Meet the brand new Code Poet, which is now a resource for making (and breaking) things with WordPress. Congrats to Pete, Pick, Evan, Rebecca, Krista, and Dave on the launch and hope to see more great content on the site very soon. Oh, and can you make it into the 780-800 club in the Quiz?

The Third WordPress Meetup in Moscow

The Moscow WordPress Meetup Group is growing and we recently held our third meetup, which was quite a success! We had a total of 12 attendees (including a 5 year old kid) and 4 presentations, around 30 minutes each: What’s new in WordPress 3.4 Building a Wiki with WordPress The GNU GPL Explained An Into to HyperDB We met on a Saturday morning and the weather was perfect, everybody seemed to...

Quick tip: Hide the Home Item on Your Front Page in WordPress

The title says it all — this one-liner CSS will hide the home item from your navigation menu, when you’re on the home page: body.home .current-menu-item { display: none; } If you’re not yet using wp_nav_menu to build your navigation menus, then, uhm, wake up! Also, the snippet relies on the body_class usage in your theme, and if your theme doesn’t use one, uhm, wake up! :)...

Rewrite Rules Inspector

Clients often ask for fuzzy, non-standard, maybe weird and not always logical permalink structure for their sites. If you’re now working with such a client, consider yourself lucky, because the brand new Rewrite Rules Inspector plugin is here! Props to the WordPress.com VIP team :)

Never Set Defaults in the Database

Speaking of defaults, NEVER SET DEFAULTS IN THE DATABASE. Not ever. The theme options you store in the DB should always, always, *always* be something the user has selected. If the user selects the default, then that’s fine to set in the DB. but you don’t set it in the DB just because it’s not set at all. get_theme_mod has a second option for the default value. So does get_option for that matter...