Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter thecrazy1

    (@thecrazy1)

    Thank you so much for this solution and the outstanding support! It’s impressive how adaptable and proactive your team is.

    I’ll go ahead and add the constants to my wp-config.php now, so everything is ready for the next update. This will make it so much simpler to maintain compatibility with my site’s setup without having to hardcode adjustments after every update.

    Your team has been fantastic, and this experience really highlights how customer-focused Matomo’s support is. Thanks again for the quick turnaround and thoughtful resolution!

    Thread Starter thecrazy1

    (@thecrazy1)

    @dizzyatinnocraft

    Thank you for the continued support.

    I’ve discovered that DB_COLLATE is actually set to an empty value in my wp-config.php. I hadn’t realized this until now, and it seems to be the reason Matomo defaults to utf8mb4_general_ci for the archive tables.

    I’m concerned about explicitly setting DB_COLLATE as serialized data on the site might break. From reviewing the code in Matomo’s Installer.php, it looks like leaving DB_COLLATE empty causes $collation to default to utf8mb4_general_ci, which may be contributing to this issue.

    Would you recommend any way to handle this without a global DB_COLLATE change? Any additional insights would be greatly appreciated.

    Thank you again for helping me through this!

    Thread Starter thecrazy1

    (@thecrazy1)

    @dizzyatinnocraft

    I did replaced the Installer.php with the version from the link you shared. After doing that, I applied the charset/collation settings as per my WordPress configuration as shown below, which has restored functionality without further issues.

    $charset = $wpdb->charset ? $wpdb->charset : 'latin1';
    $collation = $wpdb->collate ? $wpdb->collate : 'latin1_swedish_ci';

    Could you suggest a way to retain these settings through plugin updates, or do I need to redo this method after every update?

    Thanks again for your support on this!

    Thread Starter thecrazy1

    (@thecrazy1)

    Hello @dizzyatinnocraft,

    Thank you for the guidance and for sharing the updated Installer.php file. I reviewed and implemented the suggested changes to specify the charset and collation within the file. Specifically, I modified the code to use latin1 as the charset and latin1_swedish_ci as the collation, ensuring compatibility with my WordPress setup.

    These adjustments have successfully resolved the issue, and the archiving process is now functioning as expected. I appreciate the detailed support and the troubleshooting steps you provided to work through the configuration.

    Thanks once again for your patience and assistance!

    Thread Starter thecrazy1

    (@thecrazy1)

    @dizzyatinnocraft I’m using the latest version. Is there an option within Matomo’s configuration to override the charset and collation specifically for its archive tables, perhaps something in config.ini.php?

    Thread Starter thecrazy1

    (@thecrazy1)

    Thank you for your response.

    Yes, in wp-config.php, I have set the following due to compatibility needs with my WordPress theme and plugins, which depend on latin1 for serialized data compatibility:

    define('DB_CHARSET', 'latin1');
    define('DB_COLLATE', 'latin1_swedish_ci');

    The issue I’m encountering is that Matomo’s archive tables seem to require utf8mb4 collation. When the WordPress configuration specifies latin1, I get the following error on Matomo’s monthly archive cron jobs:

    WP DB Error: [1253] COLLATION 'utf8mb4_general_ci' is not valid for CHARACTER SET 'latin1'
    SQL: CREATE TABLE wp_matomo_archive_numeric_2024_11 ( … ) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=utf8mb4_general_ci

    Since my WordPress setup must remain in latin1 to preserve serialized data, is there an option to configure Matomo to use utf8mb4 independently of the WordPress DB_CHARSET setting? This would allow me to avoid potential conflicts without altering the database settings for the entire WordPress installation.

    Alternatively, if there are any recommended workarounds to maintain Matomo’s functionality under the current latin1 setting, I’d appreciate any guidance you can offer.

    Thank you again for your assistance.

    Thread Starter thecrazy1

    (@thecrazy1)

    Yeah but i don’t want my competition to see what plugins i’m using ?? [Facebook for WooCommerce] Product Set not Saving WC Product Category – Pastebin.com

    Thread Starter thecrazy1

    (@thecrazy1)

    for privacy reason, is there anyway i could send my system report privately?

    https://snipboard.io/pIlCf0.jpg

    https://snipboard.io/j7J6qk.jpg

    when i try to add a wc category to any of my product sets, after i click submit, the

    WC Product Categories box just goes blank again, it doesn’t save.

    there are is no log being logged by facebook plugin when i try to do this. Yes i’ve followed the procedure in the documentation. am i not just supposed to add one of my categories in the box, hit submit, and it should save? in this screenshot, https://snipboard.io/WYA2fK.jpg, once i click submit, it will go blank.

    • This reply was modified 1 year, 8 months ago by thecrazy1.
Viewing 8 replies - 1 through 8 (of 8 total)