chaplina

Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Forum: Plugins
    In reply to: [MailPoet - Newsletters, Email Marketing, and Automation] enforce ssl for database user breaks MailPoet
    Thread Starter chaplina

    (@chaplina)

    4 years, 4 months ago

    Thanks for the information.

    We can live with MailPoet not using SSL for the database connection (although that may change if our security audit makes certain recommendations).

    Modifying that file is not onerous but we’d have to check it after every plugin upgrade.

    It looks like the only lines needed would be:

    PDO::MYSQL_ATTR_SSL_CA => ‘/etc/pki/tls/cert.pem’,
    PDO::MYSQL_ATTR_SSL_VERIFY_SERVER_CERT => false

    I’ve added them in our test site, configured the mysql user to require ssl and mailpoet no longer reports any errors.

    Thanks to all who provided assistance and happy new year!

    Forum: Plugins
    In reply to: [MailPoet - Newsletters, Email Marketing, and Automation] enforce ssl for database user breaks MailPoet
    Thread Starter chaplina

    (@chaplina)

    4 years, 5 months ago

    The error displayed in the site using MailPoet is the “Unable to connect to the database…” message.

    Since MailPoet does not use the wpdb API to connect to the database, it will need to somehow recognize the SSL config associated with the database connection for WordPress.

    The line in our wp-config.php that enforces SSL is:

    define(‘MYSQL_CLIENT_FLAGS’,MYSQLI_CLIENT_SSL|MYSQLI_CLIENT_SSL_DONT_VERIFY_SERVER_CERT);

    Forum: Plugins
    In reply to: [MailPoet - Newsletters, Email Marketing, and Automation] enforce ssl for database user breaks MailPoet
    Thread Starter chaplina

    (@chaplina)

    4 years, 5 months ago

    MailPoet is unable to connect to the MySQL database when require ssl is configured for the user.

    Forum: Plugins
    In reply to: [Classic Editor] Multisite request
    chaplina

    (@chaplina)

    7 years, 5 months ago

    Tested and works. We’ll need to collaborate with the Divi folks.

    This is the PHP error generated if Classic Editor plugin is network activated with the Block editor as the default:

    FastCGI sent in stderr: “PHP message: PHP Notice: edit_form_advanced is deprecated since version 5.0.0! Use block_editor_meta_box_hidden_fields instead. This action is still supported in the classic editor, but is deprecated in the block editor.

    Forum: Plugins
    In reply to: [Classic Editor] Multisite request
    chaplina

    (@chaplina)

    7 years, 5 months ago

    First, much appreciation from me to the author for developing this plugin. WP should have at the very least included this as an option with the caveats that classic would get limited support (no new features) and would be “dropped” by v6.

    This plugin seems to break Divi (editing with Classic OK…editing with Block blank page with PHP error in logs). The ability to activate on a per-site basis would be splendid as our Divi sites will likely not care about the editor.

    diff below for changing default…apparently this can also be done via a filter but I’m not a WP expert so (FAQ hint :))

    --- classic-editor.php	2018-12-13 14:06:48.580319361 -0500
+++ classic-editor.php.ANDY	2018-12-13 11:07:21.582468527 -0500
@@ -188,7 +188,7 @@
 
 		if ( is_array( $settings ) ) {
 			return array(
-				'editor' => ( isset( $settings['editor'] ) && $settings['editor'] === 'block' ) ? 'block' : 'classic',
+				'editor' => ( isset( $settings['editor'] ) && $settings['editor'] === 'classic' ) ? 'classic' : 'block',
 				'allow-users' => ! empty( $settings['allow-users'] ),
 				'hide-settings-ui' => true,
 			);
@@ -200,7 +200,7 @@
 
 		if ( is_multisite() ) {
 			$defaults = array(
-				'editor' => 'classic',
+				'editor' => 'block',
 				'allow-users' => false,
 			);
    Forum: Plugins
    In reply to: [Classic Editor] Multisite request
    chaplina

    (@chaplina)

    7 years, 5 months ago

    I have to agree with the OP. There needs to be an option in the multi-site network settings to be able to set the default for all sites to either classic or block. It would then be up to the site admin to change as needed.

    Most of our sites would need to be touched after deploying this plugin to make the default block. In our test multi-site instance I have deployed this plugin after modifying the code, to the best of my ability, to set the default to block. We are currently testing to determine if the change is working.

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)