Blocky! is a revolutionary new way to manage your content and add additional sections to your page content with no theme editing required!
Author: | Cameron Jones (profile at wordpress.org) |
WordPress version required: | 4.2 |
WordPress version tested: | 4.3.3 |
Plugin version: | 1.2.8 |
Added to WordPress repository: | 08-08-2015 |
Last updated: | 10-09-2015
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
Rating, %: | 100 |
Rated by: | 1 |
Plugin URI: | http://cameronjones.x10.mx/projects/blocky |
Total downloads: | 3 659 |
Active installs: | 40+ |
Click to start download
|
Screenshots
The admin interface
Blocky! settings page
Blocky! in action
FAQ
Why can’t I use the plain text editor or media uploader?
Unfortunately the way the WYSIWYG editor is activated for new sections it doesn’t support the plain text editor or media uploader for new sections. However if you save your post any content sections that had been created will include both the media uploader and plain text editor.
Why don’t you just use a widget?
I have found that users find it easier if all the content for a page or post is confined to the editor for that page or post, not split across multiple pages.
Why aren’t my Blocky! content sections saved in the revisions?
Blocky! content sections are saved as post meta, which is different to post content. Only the title and content are saved in revisions. This is something I will look to explore in future versions.
Can I get an unfiltered version of my post content?
Yes. Blocky! adds a filter to the the_content()
function, but you can use echo get_the_content();
in your template to return your post content unfiltered. Blocky! also includes a get_additional_content()
function, which returns the additional content sections as an array, so you can use your additional content sections in more advanced uses such as in a sidebar, with nested tags, use the class input as a data-attribute or to add additional filters to your additional content.
I’m getting `stripos` and `preg_match_all` errors
If you’re using Jetpack’s Embed Shortcodes module and Blocky 1.2.1 or below you will get these errors when saving a post. Please update to at least 1.2.2.
ChangeLog
1.2.8
- Changes sanitization to only be dependent on posts instead of the post type
1.2.7
- Fixes data not being saved
1.2.6
- Fixes another undefined index bug
1.2.5
- Setting priority so additional content is grouped with the main post content
1.2.4
- Fixes
undefined index
bug
1.2.3
- Direct link to setting page from plugins page
- Setting Blocky! to be active on posts and pages by default when first installing
- Text fixes
- Additional conflict fixes
- Sanitizing class as well as content
1.2.2
- Fixing conflict with Jetpack’s Shortcode Embeds module
1.2.0
- Changed settings page heading tag to come into line with WP 4.3 standards
- Updated to support translations
1.1.3
- Added filter to include Blocky! section content in Yoast SEO’s Page Analysis
1.1.2
- Fixing
invalid argument for foreach
bug that would appear on seemingly random excerpts
1.1.1
- Applied
do_shortcode
filter to Blocky!’s content filter.
1.1.0
- Added
get_additional_content()
function to allow for more advanced uses of Blocky!
- Small readme fixes
1.0.2
- Fixing bug that would return errors if there were no content sections and
WP_DEBUG
is turned on.
1.0.1
- Fixing bug where meta box wouldn’t close in certain situations
1.0