Marius L. J.

Hiya,

Does this error also happen if you disable all plugins or use one of the default themes?

It may be that something is interacting directly with this code, and not using WordPress’ HTTP API, so that’s a good place to start testing. If the problem is not there when disabling plugins, enabling them one at a time until it happens to identify where the problem comes from would be the next step.

Hiya,

That is indeed an odd scenario, have you checked that there are no plugin or theme conflicts causing JavaScript errors on your site?

https://www.ads-software.com/support/topic/read-this-first-wordpress-master-list/#post-14157464 should help to narrow this down, and the step on troubleshooting with your browser would help you identify any JavaScript errors that could be shared to help identify what is causing this for you.

Hiya,

As this has likely been indexed by search engines already, I would recommend removing the image at the source (on the snipboard pasting service used), the owner of the image should be able to do so ??

Hiya @neverdowork, I’m Marius, one of the moderators here on www.ads-software.com.

Just wanted to let you know that I’ve redacted the user credentials in your post, as per our guidelines we don’t allow the sharing of login details (this is for your safety, and others).

Now, it has been quite a while since you posted them, and they are guaranteed to have been picked up by search engines and such by now, I would strongly recommend you change them as soon as possible, and check your logs for any unknown traffic, as nefarious users may have the details (I don’t say this to scare you, but rather to inform that this is the case ?? ).

If you should have any further questions about the www.ads-software.com support guidelines, you can find the moderation team on the Making WordPress Slack (https://make.www.ads-software.com/chat) in the #forums room.

Hiya,

Thanks for the report, I see this has previously been addressed a few times. Since this isn’t a new regression in WordPress 6.2, would you mind either commenting on the previous ticket at https://core.trac.www.ads-software.com/ticket/44911, or creating a new one with the details you’ve collected so far about the issue?

Since it’s not tied specifically to a beta release of WordPress, I’m going to mark this support topic as resolved from that point of view.

You can follow the work on improving compatibility and resolving deprecation notices such as this one in the tickets listed under https://core.trac.www.ads-software.com/query?status=!closed&keywords=~php81

As there are overarching tickets to address this issue, I’m going to mark this support topic as resolved, as future discussions should ideally happen in a ticket ??

As this is just an experimental feature of the plugin, I’ve marked the thread here in the support forums as “resolved” fro ma 6.2-beta perspective ??

It sounds like you’ve got a plugin that isn’t playing nice with the latest planned release for WordPress, since 6.2 is not yet available, they may be working on compatibility, but you may also wish to reach out to them in their own support forums over at https://www.ads-software.com/support/plugin/ultimate-member/

Since this appears to be a plugin issue, I’m going to mark it as resolved from a beta-testing point of view, but feel free to let us know if you encounter other issues ??

A new topic was created at https://www.ads-software.com/support/topic/problem-while-creating-variations/ for this issue.

Hiya,

That is indeed a bit misleading, and a ticket has been created to improve the wording here to avoid any future confusion for others.

I’ve removed the two links in the original topic that led to this decision to erase your account. Although we don’t generally do that, this is more of a goodwill-exception due to the confusion incurred by the back and forth between forum systems and data erasure procedure instructions.

Hiya,

Thanks for bringing this to our attention, the link has been updated to reflect the new URL for the Site Health overview, and should be fixed with the next plugin release.

Hiya,

This is indeed an odd one, but I suspect one, or more, plugins are modifying the site URL, and when they’re no longer active, this causes the original URL to be used, which leads to a redirect loop. This is just a guess though, but If possible, try disabling only one plugin at a time, instead of enabling one at a time (you can do this by selecting all plugins in the Plugin screen, and in the bulk action dropdown choosing “Troubleshoot the selected plugins”).

Hiya,

Lots to unpack here ?? The new recommendations are part of WordPress core, and not the Health Check plugin, but that’s OK, we’ll field feedback as well.

There’s no plans on making checks optional, it is already a recommendation, and not a critical issue. There are many plugins that will let you manipulate which checks your site will perform though ??

Although it’s true that in most cases you won’t see a huge change on smaller sites, there is definitely a performance gain to most users, and also the added benefit of needing less resources in general when sending page responses to users. The recommendation only pops up if certain thresholds are hit as well, which are there to not give the recommendation unless there is a perceived possibility for improvements to both your administrative experience, but also to your site visitors.

Do note that although your host might have support for these cache solutions, you may need a plugin to manage the cache connections if your host does not automatically include this for their users.

• This reply was modified 2 years ago by Marius L. J.. Reason: Fixed incorrect styling that got included

Hiya,

That does sound not so ideal, have you checked if any other plugins, or your theme, may be interfering here? I did test this on a fresh install of WordPress 6.1, and the navigation items are there as expected.

What you may be able to do is visit the Plugins list, and if you hover over the plugin, a “Troubleshoot” link should appear allowing you to enable troubleshooting just for the Health Check plugin, much like what would happen if you started off in the Troubleshoot page.

Hiya Michael,

One of the side-effects of enabling troubleshooting, is that it will also do everything in its power to disable all kinds of caching (both full-page ones via the no-cache headers, and object caches that may save some processing in both the back- and front-end).

Since the problem goes away when running troubleshooting mode, even with all plugins enabled, I would start by checking if you have an object cache running on your site, and if you do, see if you can flush it somehow (usually you’ll have a companion plugin that will help with this). If that fixes it, reaching out to the plugin authors and letting them know that their plugin isn’t working when an object cache is enabled, it may just be a logical error in their code ??