Over the past week I’ve been working with Rami Yushuvaev on a cool utility plugin that helps you stay on top of your site’s security by letting you know about old core files that may exist in your installation’s file-system. Not only that old core files are deprecated, but they can potentially expose your site to risks.
It’s time to make sure you’re protected!View & Download on WordPress.org Review on WPBeginner
By default, WordPress 3.5 doesn’t specify the file size on the individual attachment’s editing screen. Today I’m sharing with you a tiny snippet that will add exactly that — so now on you’ll be able to know what’s the size of the file you’re looking at.
You should add this snippet to your functionality plugin. But yes, it will also work if you place it in your
functions.php file within the active theme.
I’ve been working lately with my buddies at illuminea on setting up the WordCamp Jerusalem 2013 site and the payment form. Can’t be more excited! I’m really looking forward to this event, and I’m also pretty impatience to meet some WordPress folks in this WordCamp.
Are you planning to attend WordCamp Jerusalem 2013? Let me know in the comments!
Today I’ve been to SMX Israel with my colleagues from Illuminea. It was pretty cool. Have seen many people getting excited about SEO and online marketing — they almost convinced me to switch my career. Almost.
In his post on Make WordPress Core, core lead developer Andrew Nacin states that the release of WordPress 3.3 will be postponed to Monday, December 10, 2012 @ 11 a.m. EST. There are some open bugs and things that were yet to get fixed that hold the core team back from releasing it sooner.
Waiting for that moment.
I have stumbled upon a great presentation by Erick Hitter from Automattic regarding the Roles and Capabilities API in WordPress. The presentation focuses on the
map_meta_cap filter, explaining why and when meta capabilities are useful, and what differs it from the regular (primitive) capabilities. I had great time watching this presentation and so I hope will you. This presentation is from WordCamp Toronto 2012.
Great news my fellas! The recent Jetpack update brings in a great feature that many developers have waited for. From now on you can use the WordPress.com REST API on your self-hosted site. This means that if you have an app running off WordPress, you can offer REST API support by simply installing Jetpack. You can also build sophisticated apps that rely on the REST API, so you can
It’s also worth mentioning that self-hosted sites had XML-RPC API support for a while now, and is pretty useful by its own. That said, the WordPress.com API is far more robust and well-documented.
Ever wondered how to block access to your WordPress site for logged-out visitors? In my case, I needed to create a P2 installation that will be visible only to the site’s registered users. What’s going on here is pretty straight forward. First we check if the user is logged in using
is_logged_in(). Then, if the user isn’t logged in, we call
auth_redirect(), which is a core function that handles the redirect to the login page.
Seems like I could have worked fine by calling
auth_redirect() alone, since this is what it says in core:
Checks if a user is logged in, if not redirects them to the login page
… But, when I tried to do that, I got an infinite redirection loop. Not really what I expected. So if any of you know a better way to do it, please share in the comments!