Issue in MasterPress 1.1.8

This topic is: not resolved

Tagged: 

Viewing 2 posts - 1 through 2 (of 2 total)
Author Posts
November 8, 2019 at 10:41 am #3989
TUC
Post count: 7

Hey,

Seems like the compatibility for MySQL 8 you’ve added breaks custom field types on MariaDB servers.

It looks like you’re using two different methods to determine MySQL version within your plugin.

mpv_settings.php

<?php printf( __( "MySQL Version: %s", MASTERPRESS_DOMAIN), $wpdb->db_version() ) ?>

mpm.php

$version = $wpdb->get_var('SELECT VERSION();');

if ( version_compare( $version , '8.0.0', '<' ) ) {

The issue we see is that they both return different versions when you’re running MariaDB (which our shared hosting uses).
Method 1:

5.5.5

Method 2:

10.3.18-MariaDB-cll-lve

Because of this, the if statement returns as if we’re greater than version 8, which breaks all of the associated custom fields with any post in the system.

November 12, 2019 at 12:00 pm #3997
Simon [MasterPress Sales]
Post count: 2

Hey TUC, thanks for alerting us to this.
We have just released 1.1.9 which addresses this issue:
https://www.masterpressplugin.com/2019/11/masterpress-1-1-9-now-available

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

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