rhisflow

ok thank you!

Will you be letting me know here in this thread once the devs have solved the issue?

Thank you!

Best,
Flo

Hi,

ok I’ve gone ahead and done some extensive testing.

First of all, I created a clone of the website.

Then I cleared the website cache and disabled the caching plugin.

That didn’t help.

Then I went to the extreme and disabled each and every plugin (except AIOWPS obviously).

I can now confidently say that the issue is definitely a problem of your plugin.

It is obviously not caused by a plugin or theme conflict (since I’ve used a standard WP theme), as we can both conclude from my tests.

Do you think you will be able to fix this soon?

Thank you!

UPDATE:

I initially said that it was at least working in Chrome.
This is no longer true, for neither website (probably after completely clearing chrome’s cache).
This leaves us with the plugin functionality not working at all anymore, on no browser.

Best,
Flo

• This reply was modified 4 years, 7 months ago by rhisflow.

Hi!

Thank you for your reply.

Yes, I have the caching plugin Breeze.

Are you saying that having a caching on the website or server level will cause this feature to not work?

That would be strange since pretty much every site has at least one form of caching.

However, I’ve also tried clearing the page and server-level cache, but that doesn’t help.

Thank you for your support!

Hi Jeff,

wow, thank you so much for your fast and very helpful answers!

1) Ok got it, I’ll just hit that “Reset Bad Bot Log” once in a while as you suggested to make sure no reassigned legit IP addresses get blocked.

2) Ok got it. I noticed that 7G also blockes “amazonaws” Remote host – I was a bit surprised as I wasn’t aware that Amazon’s servers are a problem?
Also, will that interfere when I have Amazon native ads on my site?

3) That’s great advice and it may even speed up the sites when disabling rate limiting. So in other words: would you say that with 7G (and maybe even black hole for bots) in place, that there isn’t really a need for rate-limiting protection anymore, anyway?

Thanks so much!

Best wishes,
Flo

Hi Sybre,

thanks for your quick answer ?? !

I’ve read both sources you pointed me to, and 2 questions came up:

1) Reading the first source (google webmaster guide), I couldn’t actually see that having all languages in one sitemap “isn’t according to spec” as you said.

In fact, I feel like Google specifically say it’s ok to do so.

I have taken a screenshot of one of Google’s slides in that video on that side:

https://we.tl/t-GNQIWbDo5A

That’s where they clearly say it’s fine. In any case, they never mention anything about it being against specs.

The only explanation I can come up with for why you guys don’t do it like this is because it involves specifying all alternate hreflang tags in that one sitemap as well.

Since that’s more complicated, I understand why you choose not to do this.

But in my book, that’s a very different reason than saying that doing so would be against specs :).

2) In the second source you linked to (the SEO Framework documentation), I’ve found the localized sitemaps, thank you!

However, reading the entire doc, 2 questions came up:

a) Do you think it’d be wise to submit a sitemap index that includes all sitemap versions?

b) Regarding Polylang, you say:

Polylang works differently from WPML, since it augments (annihilates) the WordPress installation URL’s integrity, among changing the WordPress Query based on cookies–affecting your site’s performance by roughly 20%.

My question is: If I disable the “Detect browser language” setting, is this issue and all negative consequences resolved?

Because I’m not quite sure if by “augments (annihilates) the WordPress installation URL’s integrity” what you mean is that it works with cookies, or if there’s something else which is not caused by those cookies and therefore remains unresolved after disabling them.

Thank you so much!

Best,
Flo

Hi Calin,

ok I’ve talked extensively to my hosting provider and completely deleted the plugin folder, then reinstalled it.
Even uploading it directly to the directory.

The issue that the drop down functionality doesn’t work was still there.

I have reinstalled the old version 3.1.7, which is working like a charm.

So I can confirm that the issue is definitely caused by a change you guys made when updating the plugin.

Any chance you can get this fixed?

Maybe in the next update?

I’m happy to stay on the old version but it’d be nice if at some point I could update as well without breaking the drowndown functionality.

Thanks so much!
Best,
Flow

Hi Calin,

thanks so much for this, I’ve just sent you an email.

Best,
Flow

Hi Calin,

just wanted to follow up if you’ve had a chance to read my previous message?

Thanks so much!

Best,
Flow

Hi Calin,

sure, I can send you a link! Would you mind giving me an e-mail address or something (so that I don’t have to share the URL publicly here?)

Thanks so much!
Best,
Flow

Hi Calin,

thank you for the super fast reaction, that’s impressive ?? !

However, this issue is still unresolved, even though I just installed the update and cleared the cache.

Thank you!
Best,
Flow

Thanks for your advice.

That’s actually what I did right away, after first having tried disabling only WF.

I’m using twenty seventeen anyway.

Here’s what I did specifically:

– Enter troubleshooting mode (with the Health Check & Troubleshooting plugin)
– Enabling only the Insert Headers & Footers plugin
– Hitting “Save” within IHF plugin (without making any changes)

Turns out, even with only that single Plugin and a standard theme running, the “page not found” issue still persists.

I was thinking this is because WF is so deeply integrated, with some “deny all” lines in the .htaccess and so on, that it is still caused by it.

But I’d rather not completely uninstall it since I appreciate what it does.

So that’s really odd I think, that there’s obviously no other plugin or theme causing the issue (as a result of that troubleshooting mode test).

At the same time, the IHF plugin itself cannot be the issue either, since it’s working fine on my other website (as I originally explained).

Thanks for your help!

Even disabling the WF plugin doesn’t resolve it.

Thanks,
Florian

Hi Gerroald,

thanks for your reply and sorry for not mentioning that earlier.
I did of course try that, even disabling the Firewall completely.
To no avail.

Thanks!
Florian

Hi,

I’ve scanned the remote storage (google drive) as well and noticed the same “issue”.
Now I’m seeing all the backups, even those from other sites.
How can I go back to only seeing the relevant backups for this particular site?

It only gives the option of restoring or deleting the other backups, both of which I don’t want to do.

P.S.: out of curiosity: what would happen if I actually clicked on “restore” for one of those backups that I’m seeing but which actually belongs to a completely different site?
Would I overwrite my site with the contents of that other site?
Or is there some sort of fail-safe mechanism in place, where updraftplus warns me that this backup belongs to a different site?

Thank you!

Hi @magicfilou

I actually steered clear of this bestazon plugin, due to the serious doubts about the ongoing support you, I and probably many others have.
Like you rightly pointed out, the facts speak a very clear language…

Instead, I was looking at this plugin: https://de.www.ads-software.com/plugins/amazon-link/
This seems like a very solid solution and is definitely actively supported.
I can confirm this because I actually opened several support threads and the developer Paul was super helpful and nice.

Check it out, I think it’s a actually a much better option.