Support

Account

Register Login

Forum Replies Created

  • So, with everything said above, I assume I’m all good moving forward, ain’t I?
    I updated “acf_version” option to “5.5.1”, basically telling ACF not to try copying termmeta from wp_options to ‘native’ WP termmeta table since I don’t have any in wp_options.
    Or will ACF 5.5.x still attempt to store any new termmeta I’ll add via ACF into both wp_options and ‘native’ tables?

  • Ok, so you said ACF is looking for things like "{$taxonomy_slug}_{$term_id}_%" in wp_options.
    Doesn’t it have to ‘know’ all existing $taxonomy_slug and $term_id values before being able to look for them in options table?

    If that’s the case – I imagine it’ll try to pull all existing taxonomy slugs and term IDs from the DB first, and that’s the point when it’ll probably choke with my 300k+ items before even being able to do anything else.

    Makes sense?

  • The thing is that I haven’t even started to use ACF for termmeta or for anything else. The very first thing it gave me was DB update message, thus all the fuss here 🙂
    My existing terms don’t have ACF fields, I also checked the whole wp_options table and there isn’t a single sign of termmeta added by ACF 5.4.

  • John, all that makes sense, except one ‘but’ – I don’t have any term meta in wp_options. All my existing termmeta is in it’s ‘native’ table because Pods implemented termmeta support long before ACF.
    And yes, in case anyone wants to ask, ACF does see termmeta created by Pods and vise versa 🙂

    That’s why I mentioned that I believe there’s actually nothing to update in my case. But I’ll play with that action to see if it produces anything.

    Thanks a bunch for your help!

  • There’s no way to disable ACF bundled with Intense, looks like it’s a ‘hard’ dependency.
    Still, even when I disabled Intense (and thus its bundled ACF) – the database update never completed, meaning, it kept asking for update again and again. There was no way for the bundled ACF to load before the stand alone one because I even tried moving the Intense dir out of plugins and this didn’t change anything.

    From the looks of it, the DB update process tried to query all existing taxonomies and terms, and considering the fact that I have 300k+ of those – it simply failed at some point.
    Generally speaking, there was nothing to update, I used Intense to add a single shortcode somewhere in the theme and I highly doubt this shortcode (masonry, https://intenseplugin.com/shortcodes/masonry-shortcode/) actually utilizes the bundled ACF in any way.

    I’ll review your DB update process when I have some spare time, but my wild guess is that if ACF notices a sign of a previous version (e.g. in wp_options) – it’ll attempt to update the DB and it’ll start from querying all available taxonomies and terms. I realize my case is rare, not many of us here keep 300k taxonomy terms, lol.

    However, I did contact Intense guys, they also said this looks weird, partially, because they believe Intense does detect the stand alone ACF and doesn’t load the bundled one if it’s not needed.

    Ok, we’ll see where all this takes us 🙂

  • Thanks a bunch, this makes perfect sense.

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