Tim Dueck

Hey @adeelkhan for me the issue was like you predicted that I didn’t have my code optimized or organized properly. Once I went through and fixed all my code or reorganized it so that it would fire correctly if minified/grouped then it worked well.

Thank you!

@enomoto-celtislab Ok that makes sense, thank you for the in-depth explanation and bearing with me. Once again, love this plugin! Thank you for taking the time to help me.

Have a great day!

@capuderg So I wanted to say thank you for your help, before when you mentioned to put the code above the /*Happy blogging */ line, I had made this change but upon upload the file failed and I didn’t catch this. I have now put it in the correct place with the constant and password and it is working correctly. Thank you for the taking the time to assist me! I greatly appreciate it!

So the URL filter is doing the exact opposite of what I need when I use the URL filter it allows the plugins to run on the taxonomy pages. I am wanting to disable certain plugins on these pages since they load way more than is necessary.

Also like I mentioned your plugin is working correctly how I want, I am able to set up your plugin nicely on my taxonomy pages. However, as soon as a question mark indicating a query string is added to the end of the URL your plugin no longer works as it’s supposed to.

example.com/store – This works how it should, all bloat from extra plugins is disabled

example.com/store?123 – Your plugin does not run, meaning that all this extra bloat from certain plugins is enabled on these pages.

Another plugin that his a similar feature is the redirection plugin, here it explains how this feature works under the Query Parameters heading.
https://redirection.me/support/matching-a-url/

Let me know if that makes sense?

It is a custom post type taxonomy page. So if I set the url filter to store will it allow your plugin to run on that page? The problem is that currently I am disabling plugins to be only on specific pages, but on these taxonomies it ignores your plugin and doesn’t listen to the page rules that I’ve set.

@capuderg Ok I did move up the code but the issue is still occurring, any chance it’s because my cron isn’t run through WordPress? And it is triggered by my server? I ask because I noticed that there is a cron job that is supposed to run every minute and my server cron runs every 15 minutes.

@capuderg Hey, I did have constants enabled because I thought I need to set that as true for the password. I have now disabled the constants line but left the password and my test email still went through. I’ll see if the issue keeps popping up.

Ya, I’m having the issue where this message pops up on every page, however when I click test email it always goes through.

EMAIL DELIVERY ERROR: the plugin WP Mail SMTP v2.1.1 logged this error during the last time it tried to send an email:

Mailer: Other SMTP
SMTP Error: Could not authenticate.
Please review your WP Mail SMTP settings in plugin admin area. Consider running an email test after fixing it.

Ok, thank you!

I just wanted to let you that I don’t believe it’s an issue directly with Yoast, I think I’m just receiving lots of bot traffic to URLs that don’t exist any more every hour and it’s causing my server to lag.

@pcosta88

1. Yes I am on latest release

2. Yes I am using 5.4.1

3. All my plugins are updated

4. I’m running on a Cloudways Digital Ocean server with 4gb ram, 2 core processor, 4tb bandwidth.

I should note, like I mentioned I’m not totally convinced this is an issue with Yoast, I’m wondering if my site is doing some kind of work in the background every hour and Yoast just happens to be running at that time which flags yoast as the issue but there might be something else occurring.

@maybellyne Yes it is still receiving a spike every hour even after the indexation.

@marcanor Hey, It says “Great, your site has been optimized!”

Not sure what else I could look at. My only thought is that if I’m getting lot’s of 404 hits then the plugin keeps checking those pages whether they should be indexed or not?

It is, however I don’t know if it’s necessarily an issue with Yoast. I’m trying to figure that part out.

@whereskarlo It is fixed for me, I realized some of my kid was created incorrectly. Try using the default TwentyTwenty theme and see if it breaks. Mine worked perfectly so I realized I had to fix my theme then. It was mostly rearranging the order of css files so that they worked properly.