ralpharama

I think I can answer this myself in case anyone else has the same issue: we use a separate domain just for network admin, and this domain isn’t proxied through cloudflare, only the main multisite websites are, so of course Defender when we’re editing settings on that network domain can’t see the Cloudflare headers – because they aren’t there…

• This reply was modified 1 month ago by ralpharama. Reason: resolved

Thanks for the reply but in the end we wrote an in-house solution for this as we couldn’t wait any longer. Best of luck in the future with this though.

• This reply was modified 1 year, 6 months ago by ralpharama.

I can’t find any activity anywhere about a GA4 version, so we’re sadly looking for something else. Anyone found anything as a replacement that hooks into GA4?

Hi there, as the cut-off for UA is looming, is there any news on the GA4 version?

Thanks!

Thanks Cristian, I look forward to trying the new version when it is ready. If you need any testers, do let me know.

I’ve changed Do not display search archives in search engine results (noindex) in Titles & Metas to checked and it now shows:

<meta name="robots" content="follow, noindex">

Which is better! So this isn’t a hidden/default feature?

So I’m not sure what I can provide to help replicate this except for paste the two definitions. I can confirm that for me, removing the meta_box_cb results in the duplicates appearing. Adding it back in makes it work properly. It’s odd as the DOM of the edit page in both scenarios is identical, so I suspect you are right – something else is listening to the save maybe and causing issues. Here’s the definition of both. I tried removing one by the way and it happens with just one box enabled, so I’m not sure having multiple is the issue.

  /* Article Type */
  $labels = array(
    'name'              => _x( 'Article Type', 'taxonomy general name', 'sage' ),
    'singular_name'     => _x( 'Article Type', 'taxonomy singular name', 'sage' ),
    'search_items'      => __( 'Search Article Types', 'sage' ),
    'all_items'         => __( 'All Article Types', 'sage' ),
    'parent_item'       => __( 'Parent Article Type', 'sage' ),
    'parent_item_colon' => __( 'Parent Article Type:', 'sage' ),
    'edit_item'         => __( 'Edit Article Type', 'sage' ),
    'update_item'       => __( 'Update Article Type', 'sage' ),
    'add_new_item'      => __( 'Add New Article Type', 'sage' ),
    'new_item_name'     => __( 'New Article Type Name', 'sage' ),
    'menu_name'         => __( 'Article Types', 'sage' ),
  );

  $args = array(
    'hierarchical'      => false,
    'labels'            => $labels,
    'public'            => true,
    'show_admin_column' => true,
    'meta_box_cb'       => 'post_categories_meta_box',
    'rewrite'           => array( 'slug' => __( 'article-type', 'sage' ) ),
  );

  register_taxonomy( 'article_type', array( 'post' ), $args );

  /* Access Type */
  $labels = array(
    'name'              => _x( 'Access Type', 'taxonomy general name', 'sage' ),
    'singular_name'     => _x( 'Access Type', 'taxonomy singular name', 'sage' ),
    'search_items'      => __( 'Search Access Types', 'sage' ),
    'all_items'         => __( 'All Access Types', 'sage' ),
    'parent_item'       => __( 'Parent Access Type', 'sage' ),
    'parent_item_colon' => __( 'Parent Access Type:', 'sage' ),
    'edit_item'         => __( 'Edit Access Type', 'sage' ),
    'update_item'       => __( 'Update Access Type', 'sage' ),
    'add_new_item'      => __( 'Add New Access Type', 'sage' ),
    'new_item_name'     => __( 'New Access Type Name', 'sage' ),
    'menu_name'         => __( 'Access Types', 'sage' ),
  );

  $args = array(
    'hierarchical'       => false,
    'labels'             => $labels,
    'public'             => true,
    'publicly_queryable' => false,
    'show_ui'            => true,
    'show_admin_column'  => true,
    'meta_box_cb'        => 'post_categories_meta_box',
    'rewrite'            => array( 'slug' => __( 'access-type', 'sage' ) ),
  );

  register_taxonomy( 'access_type', array( 'post', 'page' ), $args );

If you’d like anything else do let me know! Or if you have any idea how I could find the hidden listener/function maybe?

Thanks!

• This reply was modified 2 years ago by ralpharama.

Thanks for the reply. Curiously this was fixed by adding in this line to the definition of the taxonomy:

'meta_box_cb'       => 'post_categories_meta_box',

With this present the duplication doesn’t occur, without it the radio buttons still appear but the duplicates come back on any post update!

I posted this on StackExchange where I mostly talked to myself but it has more details!

https://wordpress.stackexchange.com/questions/414317/taxonomy-entries-are-spawning-copies-of-existing-entries-with-the-new-title-as-t

• This reply was modified 2 years ago by ralpharama.

Looks great, thanks @presslabs, I’ll let you know if I encounter any problems. Thanks again for taking the time to look at and fix the problem.
Ralph

Thanks @presslabs!

I suppose not calling the disconnect & forget here! ??

            if (401 == $e->getCode()) {
                $this->serviceDisconnect(true);
            }

I wonder if you could keep a count of 401s, and if there’s say three then do the disconnect & forget otherwise assume it’s a glitch, ignore it, and just try again on the next scheduled time?

This makes a lot of sense as to why this is so weirdly sporadic! Nice work finding the problem, I hope there is a solution ??

Thanks for the reply and sorry for the delay in getting back to you. This is still getting wiped.

When I first connect it I see the client_id and client_secret properly stored in [toplytics_private_auth_config] in wp_options.
[toplytics_auth_code] has a value in it
[toplytics_profile_data] is correct
[toplytics_auth_config] is empty
[toplytics_google_token] has a value in it

Does this sound correct?

Sorry for delay in this reply, I got this working. Not sure why it wasn’t, I just moved its position in the template. I think it’s to do with the odd way this WP project is configured. All good now, thanks for taking the time to investigate.