Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter kkspn

    (@kkspn)

    Your plugin creates wp_cf7gs_feeds with:

    created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
    updated_at DATETIME DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

    Our server runs MariaDB 5.5.68.

    On this version, the CREATE TABLE fails with:

    Invalid default value for 'created_at'

    As a result, wp_cf7gs_feeds is never created, while wp_cf7gs_settings is created successfully because its datetime columns use DEFAULT NULL.

    This leaves the database schema incomplete and prevents Manual Google Sheets Configuration from being saved.

    Please confirm the minimum supported MariaDB/MySQL version for v5.2.4, and consider either:

    declaring MariaDB 5.5 unsupported, or
    making the table schema backward-compatible.

    —-
    Given the age of MariaDB 5.5.68 and the compatibility issues we have now confirmed, we also recognize that our current database version is far too outdated. We therefore intend to ask our hosting provider to consider upgrading the database server to a more recent supported version.

    Thread Starter kkspn

    (@kkspn)

    After updating to v5.2.4, the pagination AJAX nonce issue is resolved and the updateSlider() JavaScript error is also gone.

    However, Manual Google Sheets Configuration is still not retained after saving.

    We inspected the actual Contact Form 7 save POST.

    The request completes normally with HTTP 302 and contains all four correct values:

    cf7-gs[sheet-name] = 00_ContactFormAutoExport
    cf7-gs[sheet-id] = 16CVs6Xy7iB2DlEMVcYKhJLZ7082-1gDTcK-jfv8s8_8
    cf7-gs[sheet-tab-name] = LC_CF
    cf7-gs[tab-id] = 2109694184

    Therefore, the browser-side save process is now working and the values reach WordPress.

    However, after the redirect and page reload, all four fields are empty again.

    We also noticed that the same POST contains another feed-specific set of fields under cf7-gs79[...], whose sheet-related values are empty.

    Could you please check whether the v5.2.4 save handler has a conflict between the legacy cf7-gs[...] values and the feed-specific cf7-gs79[...] values, particularly for forms migrated from versions prior to the custom database-table migration introduced in v5.1.7?

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