Admin pages are often used for plugin or theme settings, and sometimes for user guide. However, there are situations you want to add a hidden admin page that only shows under a specific condition, and won’t show in the admin menu. Pages such as WordPress welcome page, credit page for new versions are examples. These page are displayed only once when users update their WordPress websites and they contain only information about the new versions. Plugin authors might want to add similar pages that shows a quick start guide for users when they first install their plugins. And this tutorial will show you how to do that.
A while back I got an email from Jackie and I just had to share it with you.
I hear stories like this a lot from WordPress developers trying desperately to building custom meta boxes and custom fields in WordPress. But this one really hit home because you can feel the pain:
WordPress is the easiest way to create a website or blog. Migrating your site from one web host to another? Not so much.
An adequate migration will ensure that your website faces zero downtime. All links must remain working correctly on completion of migration procedure. No data must be lost. Automating WordPress migration is the best way to make sure that your site will be up and running quickly.
Custom fields is a way for WordPress to store arbitrary extra data for content (posts and custom post types), such as author name, published date for a book. To make custom fields flexible and compatible with different kinds of data, WordPress designs the meta tables (post meta, term meta, user meta and comment meta) in the form of key value. According to that, each custom field is stored as one row in the database. This approach allows developers store unlimited data regardless its structure. But, the downside is the rapid bloat of the database. Because the number of custom fields is usually very large. This article will present solutions to optimize the storage of custom field in the database to help boost your website’s performance.
In the State of the Word 2016, Matt Mullenweg said that one of three main focuses of WordPress in the next year will be the editor, which will be block-based and unify widgets, interface for shortcodes. The result is the new the Gutenberg editor, which was first introduced to the public at WordCamp Europe 2017. However, it raises many concerns with the existing meta box API. In this post, we’ll take a deep look at those problems and the future of the Meta Box plugin (and similar plugins/frameworks).
Today, a lot of developers use custom fields to store data for their custom post types. Plugins for custom fields such as Meta Box provide an easy way to create them with tons of options. Developers don’t need to handle the UI, outputting and saving data. But are custom fields always good? Do we misuse them?
We’re happy to announce the release of Meta Box 4.12 today. This is a minor update with a big improvement for the meta storage and some interesting features. If you’re using old version of Meta Box, please update now.
A few days ago, we launched a new design for metabox.io and introducing a Lifetime Bundle. The great thing about lifetime bundle is you buy once and have all extensions forever, including the updates and support. But you already bought a Core Bundle or Developer Bundle? Never mind, the upgrade is available for all users of Core Bundle and Developer Bundle. And you have to pay just the difference in value.
During the last 2 weeks, we’ve been working on the redesign for Meta Box. This is the 2nd theme for Meta Box. The previous one was made in 2014 which is a little out-dated.