Simeon

I’ve marked it resolved with this reply. However, there seems to be a problem in that Woocommerce Core, even when kept up to date, isn’t updating this template in its native folder wp-content/plugins/woocommerce/templates/auth. If it had the job of grabbing the most recent version would have been much simpler.

Found the up to date version of this file by downloading the entire core plugin, it was in that package.

OK thanks, I just did post these two requests as different feature requests over at your link. I’ll grab the mu-plugin here shortly as well… would be nice if you can integrate that into the main Burst-Statistics plugin in time.

I love what you’re doing with Burst… in one of the Complianz email newsletters I saw you asking for suggestions for Burst.

1. Options to let us more specifically define what constitutes a ‘bounce’ for our site. I’m sure you’re aware of the various possibilities, let us choose different setups based on them.

2. A way of anonymously tracking user hits on specific pages from specific referrers, and an ability to drill down regarding the behaviour of those visitors after they landed on the page. This would give us the ability to better dial-in ad campaigns we may run on specific platforms (ie Facebook, Twitter) but without violating privacy laws and rules.

In other words, if we are running an ad campaign on FB and are driving traffic to a specific landing page with some hoped for results, knowing the percentage of those visitors who landed on that landing page and who followed through with our CTA would be very helpful and would not require them giving up any personal information. The session cookie with the ID required to track where they go on the site can be expired shortly after they leave the site and the ID would be anonymized as well so it cannot be used to identify anyone in particular or track them beyond our own website.

I just discovered this stylesheet only shows up in the source code when I’m logged in as an admin, so it’s probably just being used for fonts in the backend display of the Sitekit admin interface and does not affect normal site visitors.

This issue is therefore resolved.

Can the premium version display sub-categories even if there are no posts, just sub-categories?

If yes, can the number of levels of sub-categories be controlled… i.e. restrict display to just the first level of sub-categories?

Yep, that did it Bethany, no more console error… THANKS! Indeed we had no use for tag manager at this time, I just wanted the analytics.

No, there is no tags in that container because we are not using them. We simply used Google Site Kit to get the Google Analytics setup because all the old methods are now defunct. They hoist this tag stuff on you as a result. If I have to add a tag I’ll try to sort out what that might be and add one and see if that clears the error, which is more important to use than the goofy tags.

Hi,

That is not the case I’m sorry to say and I was able to easily verify the site ownership using another method, I just thought I’d try the Tag Manager route to see if it also bonked due to this problem, and it apparently did

The cited problem with the google tag being in the wrong location on that verification attempt is due to what the Google Site Kit plugin did when it was installed and configured, and is not related to the plugin not being configured properly.

See the screenshot at the link below… it clearly shows that all sections of Google Site Kit are configured and connected with green checks and thus should be working properly, but they’re not and that is why I opened this thread.

https://www.dropbox.com/s/i8felups0ogt3z1/21_05-04_Goggl-Site-Kit-All-Green.png?dl=0

I also just experienced this error which is related to the Google Tag Manager when attempting to verify ownership of the site via Google Tag Manager… says the tag is in the wrong place, but it was installed by Google Site Kit?

https://www.dropbox.com/s/9q81sn0l77tx8hz/21_05-04_Google-Webmaster-Central-Tag-Manager-Site-Ownership-Verify-Failure.png?dl=0

Thanks for the private space to share the Site Health info, I have just done so.

The host is Siteground. We currently do not have CDN active. No plugin type firewalls or WAF. Siteground does have some firewall/filtering protection as described here…

https://www.siteground.co.uk/kb/does_siteground_offer_any_protection_from_my_site_getting_dd/

Given the fact that just trying to reach the https://www.googletagmanager.com/gtm.js?id=GTM-N4NMDP8 URL in the browser as a standalone generates a 404 may indicate it’s not a firewall issue though. Seems it might be on the Google Tag Manager side for some reason?

Yes, was away for a bit, sorry for the delay in responding and thanks a bunch for the prompt responses and help!

You asked for Site Health to be shared privately here… I don’t see any specific options for that, is this forum private by default?

Regards the Container ID in Google Tag Manager, you can see that it indeed exists in this screenshot…

https://www.dropbox.com/s/mswopiy6ay3rr4t/21_05-04_Google-Tag-Manager-Container-ID.png?dl=0

UPDATE: I found the fix for this columns issue too. I just needed to add a width:100% css snippet for my default Gutenberg columns block class (.wp-block-columns). Thanks for a great plugin!

I did some testing and discovered that using two or more columns layouts in Gutenberg editor causes this issue. It goes away when just using the single column paragraph blocks.

Any chance that it could be made to accommodate two column layouts?

It works very nicely though now with just single column.

Just have free version installed right now. Need to see if it’s compatible before buying your premium version. I have a 3 page test post. All I’m getting by using the <!–nextpage–> code is:

? 1st page = Next
? 2nd page = Prev Next
? 3rd page = Prev

These links appear on the bottom left, but I have both “Both” selected in “Slider Navigation Position” setting. I also have “Both” selected for “Slider Count (e.g. “2 of 4″) Position,” but these numbers are not being displayed any place on the page.

Does it require the premium version to get those options working? If so, they aren’t marked as such in the settings.

If these options are supposed to be available in the free version, do you have any suggestions why they aren’t working?