MasterPress

Menu

Reply To: All Post Type Field Sets show when using default WP template (i.e. page.php)

Author Replies
handbuiltDave # Posted on January 21, 2015 at 9:26 am

Quick update:

Looks like the DB is storing the correct info for the field set.
Here’s a dump of the ‘visibility’ JSON array from …mp_field_sets:

json:{“sites”:”*”,”templates”:”site_home.php”,”post_types”:”page”}

In other words, this field set is visible to all sites, only for pages assigned with the ‘site_home.php’ theme template (which is what we want), and for posts which are designated as ‘pages’ (again, this is perfect).
Problem is – MasterPress doesn’t honour these visibility settings.

Would you agree that this sounds like a PHP error when the field set is rendered?
I assume there is an ‘if’ statement which checks the visibility of the field set against the current page settings before it renders the field set in the admin area of WP?

Traversal, I presume you will already know this info but thought it may helpful with debugging.

Latest From the Blog

MasterPress 1.3.6 is now available

Masterpress 1.3.6 is a compatibility release. It resolves an edge case with shared fieldsets not working for MySQL 8 when the fieldset is limited to more than 1 post type or taxonomy or excluding any post types or taxonomies.

Plugin Requirements

MasterPress requires a minimum of WordPress version 4.9, MySQL 5.6, and PHP version 5.6.20.

We also recommend that PHP is configured to use a memory limit of 64MB per request (128MB may be required for sites with higher complexity).

This plug-in is not compatible with the WordPress.com hosted service.

Three AM