Fixes issues with metabox icons being displayed incorrectly under WordPress 4.4+. Specifically, the “edit field set” arrows were always being displayed when they shouldn’t have been, and custom field set icons were not being displayed.

1.1.4.b1

9th February 2016

CHANGES

Fixes issues with metabox icons being displayed incorrectly under WordPress 4.4+. Specifically, the “edit field set” arrows were always being displayed when they shouldn’t have been, and custom field set icons were not being displayed.

1.1.3

8th December 2015

CHANGES:

Fixes an issue with an oversized index on the mp_templates table when installing into sites running WordPress 4.2.

Fixes an issue where icons wouldn’t render in the title area of edit screens on WordPress 4.3+.

Fixes display issues in metaboxes when running in WordPress 4.4+

Fixes a mixed protocol error the video field type when embedding in an HTTPS site.

The Map field type now adds a marker in the center as the location changes, to better indicate where the final selected location is.

1.1.3.b1

25th June 2015

WHAT’S NEW:

Fixes an issue with an oversized index on the mp_templates table when installing into sites running WordPress 4.2.

1.1.2

28th May 2015

What’s New

Video Field Type: The video field type now uses v3 of the YouTube API to restore broken functionality (the V2 API has recently been switched off).

1.1.1

22nd April 2015

Changes

IMPORTANT FIX: Added auto-correction of data associated with split taxonomy terms in WordPress 4.2. This detection will amend both custom field data (metadata) for any affected terms, but will also amend custom field data for any other objects which use a “related term” field to point to these affected terms.

Added Tools tab the Masterplan main menu section to allow later migration of split term data in the scenario where MasterPress was not updated to version 1.1.1 before a term had been split under WordPress 4.2.

Icon fonts are now extensively used to render icons throughout the MasterPress admin UI.

Field Type icons have been completely replaced by a new custom-designed icon set which blends in well with the vector icons throughout WordPress.

Added links to the breadcrumb area of “edit” screens to be able to quickly view parent objects highlighted in their respective lists. For example, clicking on the name of the post type in the “Post Type:” will return you to the list of post types with that post type highlighted.

Toned down some of the glossier UI elements to match the flatter UI style of WordPress.

Simplified the action buttons in all listing screens, by removing “Edit” and “Manage Field Sets” buttons. “Edit” is available by clicking almost anywhere within the row, “Manage Field Sets” is available by clicking the Field Sets column (where appropriate).

1.0.3

15th April 2014

New

Dashboard

Restored post type and taxonomy icons to the title area for post / term editing and post / term listing screens.

Added support for the new version 4 of TinyMCE included with WordPress 3.9.

API

Added WordPress filters to manipulate the available options for checkbox and radio list field types (filter documentation coming soon).

Fixes

Dashboard

Fixed an issue where field and field set settings would not be stored for Page templates stored in a sub-folder of the theme folder.

Fixed numerous warnings related to PHP strict standards which would appear when debugging was switched on under more recent versions of PHP. (5.4+).

Fixed incorrect Masterplan and Site Content icons for high resolution (2x) devices.

Fixed an issue where numeric titles for posts would cause related post fields to show the ID of the post rather than the post title.

Fixed an issue where custom fields would not be saved when adding a taxonomy term via the terms listing screen.

Removed unnecessary date.js integration which could cause infinite JavaScript recursion issues for other plugins using date.js.

Remaining character count now works correctly for multi-line text field type.

Fixed various PHP warnings related to undefined variables.

API

Fixed numerous issues with listing posts attached to a WOOF_User object and retrieving incoming posts for a user.

Fixed WOOF_File enclosure method to output correct enclosure tags.

1.0.3.b1

25th March 2014

What’s New

Dashboard

Significant user interface fixes and visual enhancements to make MasterPress look a lot better when used with WordPress 3.8.

Restored post type and taxonomy icons to the title area for post / term editing and post / term listing screens.

API

Added WordPress filters to manipulate the available options for checkbox and radio list field types (filter documentation coming soon).

Fixes

Dashboard

Fixed an issue where field and field set settings would not be stored for Page templates stored in a sub-folder of the theme folder.

Fixed numerous warnings related to PHP strict standards, which would appear when debugging was switched on under more recent versions of PHP. (5.4+).

Fixed incorrect Masterplan and Site Content icons for high resolution (2x) devices.

Fixed an issue where numeric titles for postd woul cause related post fields to show the ID of the post rather than the post title.

Fixed an issue where custom fields would not be saved when adding a taxonomy term via the terms listing screen.

Removed unnecessary date.js integration, which could cause infinite JavaScript recursion issues for other plugins using date.js.

API

Fixed numerous issues with listing posts attached to a WOOF_User object, and retrieving incoming posts for a user.

1.0.2

3rd March 2014

What’s New

Dashboard:

User interface has been updated to support the new Dashboard UI in WordPress 3.8

Added latest version of mediaelement.js. MasterPress will now also make use of the bundled version where available (WP 3.6+)

Moved to version 3 of CodeMirror.js for HTML source editor and Code Editor field type.

Migrated to new version of select2, and made the MasterPress-specific additons to select2 a separate script enqueue. This allows the standard select2 plugin (and styling) to be used by themes without including MasterPress-specific additions and style changes.

Fixes

Dashboard:

Fixed issue with empty availability panel when not using MASTERPRESS_MULTISITE_SHARING flag.

1.0.2.b3

3rd November 2013

What’s New

Cleaned up built-in scripts, styles, and script / style registration significantly, in an effort to allow future versions of third party libraries to be integrated more easily.

Fixes

Front-end

Fixed an issue where drag and drop to the media library would not work correctly when a MasterPress image field was present in the same post.

Developer

Fixed many issues when using the API to create and update posts, terms, and field values when programatically switching between sites in a multisite environment.

Removed a lot of built-in results caching in the API, which could cause consistency problems when updating data and trying to re-fetch. Decided it’s also best to not have this level of caching, as there are better ways to do this, such as the object cache facilities in WordPress.

Fixed issues with meta data being incorrectly saved when using API update methods while in a post save hook.

MEOW_Field::set_value now allows a MEOW_Field to be passed as an argument, which allows more expressive ways to set values based on the value of another field.

1.0.2.b2

4th October 2013

FIXES

User roles are now correctly created when importing a Masterplan containing them, as reported here

1.0.2.b1

2nd October 2013

WHAT’S NEW

MasterPress now correctly supports the latest versions of the MP6 plugin.

Added new methods to the Map Field Type Class (MPFT_Map) to allow an alternative style of embedding via JavaScript, rather than an iframe

FIXES

Added latest version of MediaElement JavaScript library.

MasterPress now falls back to bundles WordPress version of MediaElement when available.

1.0.1

23rd August 2013

What’s New

Dashboard:

Added a Google Maps Field Type.

Added preliminary support for the MP6 plugin, which is likely to represent the new admin interface in a future WP version

Further refinements to Google Maps Field Type.

MasterPress now stores its files in wp-content/uploads/mp, rather than wp-content/mp. This change brings more consistency to the way files are stored in multisite installations, and also makes plugin activation a much simpler process when the uploads directory is already setup correctly. All new installs will use this directory, but existing installs can continue to use the previous setup.

MasterPress now supports the new locations for files in a multi-site environment, as of WordPress 3.5, while also supporting the previous blogs.dir setup

The image field type can now work with images that have external URLs – that is, images not stored in the local WordPress environment. This is enabled by adding the configuration line define(“MASTERPRESS_RESOLVE_EXTERNAL_URLS”, true) in wp-config. Note that external images will be pulled down and cached on an as-needed basis. Pulling images down is required to be able to generate thumbnails from them for display in both the admin and front-end.

API:

The WOOF and MEOW APIs now use PHP 5 autoloading of classes, so that classes are now only loaded on an as-needed basis. This reduces the memory footprint of the plugin quite significantly for admin and front-end requests that don’t use these APIs.

Added auto-links to MasterPress documentation pages when using “debug” methods.

Added WOOF_Collection::intersect method for computing the intersection between two collections.

Made default param for WOOF_Collection::flatten the id of the object.

Added WOOF_Post::clear_terms method, to remove all terms for all or a specific taxonomy.

WOOF_Post::terms can now be called without a taxonomy, to fetch terms for all taxonomies.

Allowed WOOF_Post::remove_term to operate without needing to specify the taxonomy

WOOF_PostType::in_a method now allows more flexibility when dealing with terms which are WOOF_Term objects (and so have a taxonomy built-in), and added “relation” argument to all related methods.

WOOF::posts now uses WP_Query to fire off a query, and meta properties are now available in the collection to retrieve found_posts, post_count, and max_num_pages (accessed as simple properties).

WOOF now uses different directories underneath “wp-content/uploads”, to better support UI-less installation and use (which will be useful when the API is released separately in the future)

The WOOF API is now a git sub-module, and can be used separately to MasterPress.

Added GPL Licence file to WOOF.

MasterPress now includes a read-only (GET) JSON REST API, allowing you to serve up JSON listings of your posts to integrate with web and mobile applications. This is currently controlled by a series of WordPress filters. More documentation will be added to describe this soon…

Fixes

Dashboard:

Fixed a fatal error on activation for certain PHP setups.

Fixes a problem with capabilities for custom field sets, for user roles without the “manage_options” capability.

Fixed the “public” flag for post types, which is now true by default, and further refined by the more granular settings.

Critical fix to a func_get_args() call which was preventing the field editing interface from being rendered in certain PHP versions.

Posts and Terms are now ordered correctly underneath their parents in Related Post and Related Term fields (previously these was being sorted directly and ignoring the hierarchy making them difficult to work with)

API:

Added itemscope, itemtype, and itemprop to the list of acceptable attributes for HTML5 in WOOF_HTML generation methods. These attributes are an essential part of the schema.org syntax.

Critical fix for MEOW_FieldSetCollection::update method, which was encoding collection data incorrectly under certain circumstances, preventing some field data from being saved properly when using this method. (Note, this method is not used when saving info for custom fields when editing posts, terms, users in the dashboard, so saving via the UI was not affected).

1.0.1.b8

14th August 2013

FIXES

1.0.1.b7

11th August 2013

What’s New

Auto-caching of external files and images is now opt-in only, by defining the config variable MASTERPRESS_RESOLVE_EXTERNAL_URLS. The auto-cache behaviour, while useful at times, can cause issues with infinite 404s if a URL points to an image/file on the same server but the file does not exist. (see bugfix below). Therefore, this should not be default behaviour.

Fixes

Fixed nasty problem with auto-loading external images, where a URL pointing to an image on the same WP install that does not exist could cause an infinite httpd loop of 404s. Auto-caching will only occur now if the URL is external to the site, and also only if the config variable mentioned above is defined.

1.0.1.b6

7th August 2013

One more beta release before the final 1.0.1…

WHAT’S NEW

The image field type will now work with images that have external URLs – that is, images not stored in the local WordPress environment. This works seamlessly, nothing that external images will be pulled down and cached on an as-needed basis. Pulling images down is required to be able to generate thumbnails from them for display in both the admin and front-end.

FIXES

Fixed fatal error when programmaticaly creating posts based on a custom post type.

Fixed further issues with manage posts column display when displaying custom post types not created with MasterPress.

Fixed major problem causing image and file uploads to record an incorrect URL when running MasterPress on a Windows server.

Removed blockUI plugin which is now unnecessary and was causing issues in WordPress 3.6.

Fixed issue with List Box ordering not being retained on save.

Fixed a few issues with thumbnail display for the image field type on retina displays.

1.0.1.b5

17th June 2013

What’s New:

Migration of content directories in 1.0.1 will no longer be specifically required. All new installs will use the new directory, but existing installs will work fine.

Updated the “Update” and “Save” buttons to a new style closer to the current version of WordPress

Fixed Taxonomy warning in the edit taxonomy field set screen when WP_DEBUG was activated.

1.0.1.b4

1st June 2013

WHAT’S NEW

The Add New Term form now also displays custom MasterPress fields (in a fairly limited amount of screen real estate).

FIXED

Fixed a major issue where MasterPress was incorrectly trying to handle plugin api filters not intended for it. This caused delays in some plugin screens and loss of functionality in others.

Fixed issue with blank field values for the image field type.

Reduced the volume of inline stylesheet rules for custom icons.

Fixed an issue where columns created by other themes and plugins were showing PHP warnings.

1.0.1.b3

30th May 2013

WHAT’S NEW

MasterPress now stores its files in wp-content/uploads/mp, rather than wp-content/mp. This change brings more consistency to the way files are stored in multisite installations, and also makes plugin activation a much simpler process when the uploads directory is already setup correctly.

MasterPress now supports the new locations for files in a multi-site environment, as of WordPress 3.5, while also supporting the previous blogs.dir setup

The WOOF API is now a git sub-module, and can be used separately to MasterPress.

Added GPL Licence file to WOOF.

WOOF now uses different directories underneath “wp-content/uploads”, to better support UI-less installation and use.

Fixes:

UI:

Critical fix to a func_get_args() call which was preventing the field editing interface from being rendered in certain PHP versions.

Posts and Terms are now ordered correctly underneath their parents in Related Post and Related Term fields (previously these was being sorted directly and ignoring the hierarchy making them difficult to work with)

API:

Added itemscope, itemtype, and itemprop to the list of acceptable attributes for HTML5 in WOOF_HTML generation methods. These attributes are an essential part of the schema.org syntax.

Critical fix for MEOW_FieldSetCollection::update method, which was encoding collection data incorrectly under certain circumstances, preventing some field data from being saved properly when using this method. (Note, this method is separate from the updater for custom fields when editing posts, terms, users).

1.0.1.b1

17th March 2013

What’s New

Added a Google Maps Field Type.

MasterPress now includes a read-only (GET) JSON REST API, allowing you to serve up JSON listings of your posts to integrate with web and mobile applications. This is currently controlled by a series of WordPress filters – more documentation coming soon…

The WOOF and MEOW APIs now use PHP 5 autoloading of classes, so that classes are now only loaded on an as-needed basis. This reduces the memory footprint of the plugin quite significantly for admin and front-end requests that don’t use these APIs.

Fixes

Fixed a fatal activation error for certain PHP setups.

Fixes a problem with capabilities for custom field sets, for user roles without the “manage_options” capability.

Fixed the “public” flag for post types, which is now true by default, and further refined by the more granular settings.

Fixed undefined $wf variable in WOOF::post_types

1.0

28th January 2013

This is the first public release of MasterPress, the premium content management plugin for WordPress.

Latest From the Blog

MasterPress 1.1.4 is now available. This release contains an important compatibility fix for WordPress 4.5 to allow correct detection of the taxonomy term editing screen. Without this fix, any custom fields you have attached to custom taxonomies will not be shown at all in the editing form. Note also that MasterPress will still detect the edit screen correctly in…