shaunbowen

@shameem can you please clarify how to tell if we need this setting enabled?

I have the checkbox for ‘Enable the legacy REST API’ ticked on my site, but there are no webhooks or API keys in any section.

Can a plugin use the Legacy Rest API without it showing in Woocommerce Settings?

It is totally unclear whether we are actually using this functionality, or if it has been left checked from the default install.

Hi there, sorry for the delay.

I tried adding that to my theme’s functions.php file, but unfortunately it didn’t work.

I have successfully changed the excerpt length and ‘read more’ text with these codes further up in my functions.php file:

  // Add Read More to Excerpts
function new_excerpt_more( $more ) {
    return ' <a class="read-more" href="'. get_permalink( get_the_ID() ) . '">' . __('Read More...', 'your-text-domain') . '</a>';
}
add_filter( 'excerpt_more', 'new_excerpt_more' );

//Filter the except length to 80 characters.
function mytheme_custom_excerpt_length( $length ) {
    return 15;
}
add_filter( 'excerpt_length', 'mytheme_custom_excerpt_length', 999 );

@adamdunnage I have just tried resetting Site Kit and performing all the connections again. Still only 50 properties showing.

I won’t delete my cache as I have lots of tabs and logins in progress at the moment, so instead I performed the process on my mobile. Still 50 properties only.

Hi @adamdunnage I tried doing this from a different Chrome profile and in an incognito window, but I can still only see 50 properties.

My version of Site Kit did automatically update to the official 1.111.0 version so I had to re-download the development version and install that again before trying the above.

For now I will see if I can delete some old Analytics properties from that account, as some are no longer in use and that might get the total under 50.

But the issue still remains unfortunately.

@adamdunnage I downloaded and installed the development version, but this seemed to be the same version number of 1.110.0 that I already had installed. I continued with the install regardless.

Even after this, I still cannot see the new property I need in the drop down list. Nothing appears to have changed.

Do I need to clear some sort of cache for Site Kit? If so, how do I do this?

@tnolte I agree – if you are having the exact same issue then surely this is the right place to comment!

it also reinforces that this is not due to my browser or particular website, but likely a bug with the Site Kit plugin.

@adamdunnage I tried connecting analytics on that temporary site, and it still doesn’t show the property that I am looking for in the list.

@adamdunnage I only placed that code after I couldn’t get Site Kit to connect. The existence of that manual code makes no difference to the issue, as I have tested with and without it there.

Hi Adam,

I have submitted the Site Health information as requested.

Using an incognito browser window did not work wither.

Yes there are other users with access to this GA4 property, however the property was setup with the account I have used to connect Site Kit.

Hi Alex, many thanks I have found a temporary fix for now by adding a line to my custom CSS, which will be easier to implement until the official update is released.

I have actually managed to figure it out based on some deep Google searching! The syntax should actually be:

cat=-9,-179,-180,-181,-182,-183,-184

I will mark this as resolved.

I have actually managed to figure it out based on some deep Google searching! The syntax should actually be:

cat=-9,-179,-180,-181,-182,-183,-184

I will mark this as resolved and then perhaps it could be added in the plugin widget, under the relevant box (to help future users).

As a side note, the query does not exclude the categories from showing in the filter section (if used). To get around this, I used this in my CSS:

a[data-value=".term-9"],
a[data-value=".term-179"],
a[data-value=".term-180"],
a[data-value=".term-181"],
a[data-value=".term-182"],
a[data-value=".term-183"],
a[data-value=".term-184"] {
	display: none !important;
}

• This reply was modified 1 year, 7 months ago by shaunbowen.

My apologies, after some investigation and testing I have narrowed down the issue to another plugin conflicting at the same time. I will mark as resolved.

Looks like Fancybox 3 is not GPL, which is why not everyone is using it yet. The Easy Fancybox developer still hopes to implement it in future, but until then I will need to find a different lightbox plugin for my regular (non-property) images.

Thanks for the response – I will see if the Property Hive developers can incorporate some extra options for their fancybox integration.