elaraweb

Hi, upon further testing, it’s ACFE Pro related, not the free version (the custom date field is fine in the free version, tested on a blank WP install). I rolled back to 0.9.0.8 Pro and face the same issue.

Apologies, I know this is for support for the free version, I just didn’t notice what plugin I was using (I run free on some websites, and pro on those that need it).

I’ll close this topic and submit a ticket.

Thanks

Hi, yes, latest version of WP, ACF Pro and ACF Extended. I’ll run some further tests, but from what I have found initially as soon as ACFE is disabled, the custom date inputs show. Will report back. Thanks

Fixed with:

<?php

// For the main <title> tag
add_filter('pre_get_document_title', 'custom_course_cat_main_title', 999);
function custom_course_cat_main_title($title) {
    if (is_tax('course_category')) {
        $term = get_queried_object();
        $custom_title = get_term_meta($term->term_id, '_seopress_titles_title', true);
        return !empty($custom_title) ? $custom_title : $title;
    }
    return $title;
}

// For the SEOPress meta/OG/Twitter titles
add_filter('seopress_titles_title', 'custom_course_cat_seo_title');
function custom_course_cat_seo_title($title) {
    if (is_tax('course_category')) {
        $term = get_queried_object();
        $custom_title = get_term_meta($term->term_id, '_seopress_titles_title', true);
        return !empty($custom_title) ? $custom_title : $title;
    }
    return $title;
}
?>

The issue is listed here too, lots of people are impacted: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2463.

@hans410947 yes, it’s a Stripe issue, see https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2463.

Hmm, I tried with WP SMTP, same issue occurs. Set to send via Brevo / Sendinblue, same issue occurs.

If I clone the website to staging, the issue is fixed, weird.

Dosn’t look to be Fluent SMTP specfic.

This is all via the same browser / device. Fine for me, log in to another admin account, doesnt save. Odd!

Re-entering the same auth key over at ShipStation fixed the issue for us (still running v4.4.0). Have held off updating to 4.4.1 for now

Morning Carol, thanks for the quick response.

The issue only started happening last week, and in terms of updates, the only thing we’ve updated recently is the latest version of Woo (8.6.0 to 8.7.0).

We aren’t running any caching on the website.

I’ve checked Woo -> Settings -> Shipping but there isn’t anything related to ShipStation? Under Woo -> Settings -> Integrations -> Shipstation, everything looks to be correct.

• Yesterdays ShipStation log

Thank you

Any update?

This happens multiple times per year and causes no end of issues. I’ve purposely turned off auto-updates for every website we manage, but missed one, and you guessed it, a critical error.

Hi, sorry for the slow reply.

Shortcodes are embedded like this example:

[asp_product id="7532"]

Products are / were created via Stripe Payments -> Add New Product.

Thanks

• This reply was modified 9 months ago by elaraweb.

Any update on this, please?

No caching plugin active or server-level caching. W3 Total Cache was installed previously, but I have flushed the cache and had the plugin disabled for the last three or four weeks now.

Hi, here’s the log (I replaced user email addresses with [email protected]).