Joe Westcott

Got it, thank you, Adam.

I’ll mark this as resolved because based on your reply, it seems that we’ve hit the limits of what this plugin can do at this time, and our only feasible options at this time are to either:

1. Stop checking for broken links on certain domains like Zendesk.com and other domains that use Cloudflare DDoS protection.

2. Or find a new way to check for broken links without this plugin.

As you mentioned, Cloudflare has an API in place, so the only feasible way to run broken link checks that are allowed through Cloudflare’s DDoS protection is to somehow use their API, either through a plugin that we write ourselves or a similar method, using API authorization that we set up ourselves.

Which would basically mean that we’d have to write our own plugin or our own service to handle broken link checks.

Oh well. We’ll consider the two options listed above.

Thanks for your reply and your help, Adam.

Hi folks, FYI, you’ll now find two feature requests on Github, to address issues with the “full height alignment” option:

1. Customize “full height alignment” functionalityhttps://github.com/WordPress/gutenberg/issues/32899
2. Request for theme support option to enable and disable “full height alignment”

Thank you for your time and your suggestions!

Joe

• This reply was modified 3 years, 9 months ago by Joe Westcott. Reason: The issue was resolved previously but I saved my message without resolving this issue moments ago, due to the lack of a "preview" option in this forum. I wanted to check whether my reply looked as I thought it should. Now that I'm fairly sure that my message appears as expected, I'm marking the issue resolved

Thank you, folks. Your replies here are so helpful!

My workaround at the moment is to tell people not to use the feature, ha. And in some cases, we manual it adds class to items in order to apply CSS with the desired affect.

We can’t feasibly override it with !important — good thinking, though — because we only want to override cases where this option is used, and we don’t want to force a height for cover blocks where the height is either the default or set elsewhere. It might be worth noting, for anyone new who finds this support issue, that the “full height alignment” option only applies styling inline, rather than applying a CSS class that in turn can be targeted and overridden.

The cover block allows us to set a minimum height in pixels, but that doesn’t enable people to set the height to the available viewport height, and this setting is not responsive at all.

Thanks again for your help so far, and for checking the core code to see what the options were, if any.

I’ll place a feature request. Thank you for your advice!

I’ll keep this issue open until I place that feature request, so that I can link to it as part of the documentation for this issue.

Hey @paaljoachim , thank you for the suggestion.

This question is a how-to question, so I’m not sure that the options at that link would be a good fit, e.g. “bug report” and “feature request”. But please let me know if you’d recommend a particular option at the link that you shared.

https://www.ads-software.com/support/topic/customize-or-disable-the-full-height-alignment-option-in-gutenberg/#new-topic-0

I already placed a General help request, at the link above. There, a moderator named @t-p directed me to place this technical help request, suggesting that “the plugin’s developers and support community can help you with this.”

I’m hoping that someone familiar with the code can reveal whether there’s a built-in way to customize or disable the functionality of the “full height alignment” option that’s now in Gutenberg.

Thank you, @t-p. I’ve reposted as you suggested, here:

https://www.ads-software.com/support/topic/customize-or-disable-the-full-height-alignment-option-in-gutenberg-2/#new-topic-0

Thanks very much, Jeff. It won’t be feasible for me to disable page caching outside of the ?blackhole URLs, but I really appreciate the clarity that you provided, and your help.

FWIW, in case anybody searches and finds this support thread, I was trying to set up the plug-in on Pantheon hosting.

Again, thank you, Jeff.

Hi Jeff, thanks for your reply. I tried the “check if the plugin is working” steps and I saw the Blackhole URL, but when I visit the URL, I fail to see an error, and nothing appears in the Blackhole log.

A few questions to help troubleshoot:

1. Should the blackhole URL (parameter value) change with every visit, if things are working correctly?
2. Do the new robots.txt entries do anything other than warn good bots away, or do they serve some other sort of function? E.g. during testing, is it necessary to have robots.txt set up properly? Asking because we have a slightly weird test setup, which makes it a little difficult to troubleshoot this.
3. When you wrote “it looks like you have some other sort of caching that is interfering”, were you referring to anything specific from the headers that I shared? The response headers seem to show that we’re successfully bypassing the cache, but if you’re expecting something different or you require certain headers in order for Blackhole for Bad Bots to work, please let me know.
4. Does this plugin need anything else excluded from the page cache, apart from visits to ?blackhole URLs?

Thank you,
Joe

I love the ‘Tada!’ that you added, @danielbachhuber . Cheers!

Hi Adam, I saw your message last month, but I forgot to mark this as resolved.

Thank you for your help!

Thank you, Kasia. How were you able to test this?

I’m being dense, and not able to think of a way to test a change to the exclusion list other than simply waiting for a day or so, or else completely re-doing the check of every link on the site, maybe?

Thank you, Renee. I had to repurpose the test site for something else after a couple of weeks due to a project deadline. Thank you for checking on the issue, and for following up.

Thank you for confirming that the double analytics.js script is a known bug when following the instructions to implement Google Analytics and Google Optimize as Google Tag Manager tags. I confirmed that if I disable Optimize completely, then the second analytics.js script goes away.

And thank you again for confirming that the “non-standard implementation” warning message is a known false positive bug in the Tag Assistant browser extension for Chrome.

Thanks for all your help, and have a good one!

https://www.dropbox.com/s/jhwjodzecvdjh0r/google-site-kit-gtm-preview-multiple-installations-detected-google-tag-manager.png?dl=0

If it helps, when I enter Debug / Preview Mode in Tag Manager, then Tag Assistant states that there are multiple instances of GTM on the page. This only happens when in debug / preview mode. Please see attached screenshot of the problem.

Presumably, Site Kit is doing this — adding multiple GTM instances to the page — because this is a stock install of WordPress with no custom code and no plugins apart from Site Kit.

FYI, from 2020/10/22 – 10/27, there was a message in Optimize that there were problems with GTM debug mode. But that message is now gone, so I’m assuming that we can trust this info from debug / preview mode.

At the moment, I am _not_ running an Optimize experiment. I’m simply adding Optimize via a GTM tag, and GTM is configured through Site Kit.

(edit: clarification and typo fix)

• This reply was modified 4 years, 4 months ago by Joe Westcott.

Thank you, Renee! I posted to Tag Manager Help almost a week ago and there’s been no reply, so it’s great that you see the problem as well, and that it’s not just me.

Here’s the question that I posted to Tag Manager Help:
https://support.google.com/tagmanager/thread/78426577?hl=en

Hi Renee! Thank you for taking my support request.

You won’t see analytics.js twice in the source code because GTM is pushing GA to the site, which basically happens after the source code loads.

However, if you open your browser developer tools and inspect the DOM, you should see the double analytics.js script in the <head> at that point.

If it helps, here are screenshots that show parts of the problem.

DOM inspector with two analytics.js scripts: https://www.dropbox.com/s/cy1myt2lolybgil/google-test-site-ga-js-appears-2x-with-head.png?dl=0
GTM GA tag settings: https://www.dropbox.com/s/j1bk5dke85rvjfu/gtm-ga-tag-google-test-site.png?dl=0
GTM Optimize tag settings: https://www.dropbox.com/s/ushwwdso4mgzdfw/gtm-optimize-tag-google-test-site.png?dl=0