Anh author of one of the most popular metabox plugins weighed in on what he thinks is the future of MetaBoxes with all new Gutenberg!
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). What is Gutenberg?
Gutenberg is a new editor developed with the aim to improve the user experience in creating and writing content. It has been developed since early this year and first introduced to the public at the Q&A session at the WordCamp Europe 2017.
At the moment, Gutenberg is being actively developed. You can download it from WordPress.org repo and test how it works. But it’s not recommended to use on the production sites.
The development team expects to create a revolution in creating content by minimizing the editor UI and making predefined content blocks. Gutenberg might replace the current TinyMCE editor and/or widgets, shortcodes interface. It aims to make
Custom Fields is powerful and probably one of the most used features of WP. Anh has written this amazing guide and shares his thoughts on various ways to use custom fields.
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. Common problems with WordPress database structure for custom fields
There are some disadvantages of using the WordPress default database structure for meta tables as follows:
Unclear, fragmentary data model
Because stored as a key value, the data of the same post is not stored in the same row in the database. The lines are not consecutive and unordered. Therefore the data is discrete and does not represent the data model of the post. See the picture
My favorite plugin to build custom Metaboxes in @WordPress has announced support for #Gutenberg before #WordPress 5.0 It's huge. 300,000+ active sites. Props to @rilwis He's good people — part of the WP Community and a fellow #OpenSource dev.
2017 was a great year for Meta Box. The number of users, the number of extensions and even the revenue have increased significantly. Let’s take a look at what Meta Box has achieved and what’s the plan for 2018. 2017 in Review
18 releases, from 4.10 to 4.13.0, including 4 minor releases. The number of releases is more than 2016.
300,000 active installs. Compared to the 2016’s 200,000 active installs, Meta Box grew 100,000 active installs per year (Meta Box had 100,000 active installs in 2015). The growth rate was 50%, not bad.
5 extensions. There are 2 free extensions and 3 paid extensions. Premium extensions like MB Custom Table and MB Frontend Submission provide a complete solution for managing data and creating frontend forms for users. We are proud to be the only company that offers these integrated solutions for custom post types and custom fields in WordPress.
New tools for users
Meta Box AIO: a single plugin with all premium features. Available in developer bundle and lifetime bundle.
Lifetime Bundle: customers only need to buy one time and have update and support forever.
Online Generator: users can create meta boxes and custom fields through