Marius L. J.

We’ve approved the pending WP Engine accounts at this time, but we obviously can’t publicly disclose why they were kept in limbo.

We strongly recommend checking in with your mail provider why their mail services may (or have been) blocked recently, to ensure you are able to reach out in the future if similar incidents should occur.

It does indeed sound like your company email server is being flagged, I’ll escalate it and see if we can find out the reason, as I’m not seeing an immediate cause for it (it may have been a temporary fluke that has since been resolved, as I unfortunate did not have a chance to follow up with you yesterday).

Hi there,

I’m going to presume you are encountering issues sending emails, and not that you are receiving an automated rejection response from the email mentioned?

If that is the case, please check your outbound spamfilters first of all, as we rely on reliable email transactions to verify who individuals are (if we can’t email back and forth, then we don’t know who you are after all).

If it’s an outbound spamfilter, we would love to hear more about it of course, you may also reach out on Slack if there is information in the filter that can not be posted publicly.

Hiya,

Just chiming in to let y’all know that it’s known that the new CSS selectors (which, as you’ve discovered, are intentionally meant to be quite weak, to make them easier to customize), may have unexpected consequences in some scenarios.

You can read more about the change at https://make.www.ads-software.com/core/2024/06/21/wordpress-6-6-css-specificity/, and the discussion about the fix for this can also be followed at https://core.trac.www.ads-software.com/ticket/61660

This is partially expected behavior, as WordPress 6.4 changes how templates outside the post content are loaded.

While the fact that it returns true when you call the function again is a bit unexpected, but a plugin would also not call have_posts() multiple times in a row like that, so for now this seems like an unhandled edge case.

A developers note is being published to ensure this change is communicated, once it has been published, I’ll make sure to add a link to it here as well, and if there’s any unexpected interactions that users encounter due ot this change, we would love to hear about them as well.

I will correct my self, as WordPress does not add both of these attributes any more (and has not since version 5.6), but the Gutenberg plugin may still be doing so it seems.

There aare many examples of plugins or code to filter the attributes though, and if one does not work in your specific example, I would urge you to try one of the other solutions available. One such example is https://github.com/WordPress/gutenberg/issues/26914, linked to from the topic above.

Hiya @vvt10551

Just letting you know, I archived your last reply, there is an apparent language barrier here, and your words were not well chosen, but we also all make mistakes so I’ve cleared that one up for you ??

As to your issue at hand, the noreferrer and noopener attributes automatically added to links are there to tell browsers to remove tracking information when you click links, they do not have any relation to a links ability to be opened in a new tab or window.
In fact, you can choose this when adding a link in WordPress as well (when adding a link, under the “Advanced” dropdown there is an option to open links in a new window).

If you wish to remove this feature from your WordPress installation, you will need to use a plugin, or some custom code. There are many examples of how to do this online, but a reference from the www.ads-software.com forums can be seen at https://www.ads-software.com/support/topic/how-to-stop-gutenberg-from-adding-rel-noreferrer-to-new-links/ for example.

The error message indicated that a function that comes bundled with WordPress was missing, and being familiar with the tests WordPress performs, this is not the kind of file that would be missed during testing.

Are any of you using any security plugins or plugins that change the wp-admin directory in any way?

Hiya,

Most likely, there is one or more files in your wp-content/mu-plugins directory that are added by your previous host, that you would want to remove.

If I was a betting man, I would also suspect that you have some caching files (so called drop-ins) directly under your wp-content directory as well that you may wish to remove, as well as some configuration options in the wp-config.php file that are host specific.

What all of these are, is hard for me to say, as I do not use Bluehost for my own hosting, so I don’t know which features they have or offer at this time.

No worries about the terminology, it’s one of the hardest parts of tech on the internet these days (and we all know things under different terms) ??

So yes, it sounds like you have an incomplete upgrade on your hands then, are you able to attempt the manual copying of files as outlined in the article above? (some hosting providers are also able to help with this if you are stuck, although I can’t guarantee that this is the case)

As this has been ongoing for some time for you, I would suggest you follow the troubleshooting steps of disabling plugins, and switching to a default theme, as it sounds like you may be experiencing a conflict with one of those.

To do so, you can follow the steps outlined at https://www.ads-software.com/documentation/article/faq-troubleshooting/ (I would advise against using the alternatives to manipulate your database directly if you can, and instead stick to modifying the folder names, as then you will not have to re-enable all plugins again afterwards)

Hiya,

This is an expected page to be redirected to (to ensure that any DB changes have been ran as they should, if there are any), and is a part of the post-upgrade flow with every release.

That you are seeing a 404 error for this file though, would normally indicate that you have an incomplete update on your hands. You mentioned that you’ve attempted a manual update, and that the error remains though, would you mind sharing how you did the manual update; for example, was it following the steps from https://www.ads-software.com/documentation/article/updating-wordpress/#manual-update, or some hosting-specific instructions (and if it were hosting-specific, would you be able to attempt the instructions from the official documentation)?

Hiya,

It looks like you’ve got an incomplete update on your hands, where some files have not been added to your site, and some files have not been properly added to your site.

Would you mind attempting to do a manual update (you can find the instructions for doing so at https://www.ads-software.com/documentation/article/updating-wordpress/#manual-update), as I believe that will resolve this error for you ??

It looks like there is either some styling, or JavaScript code misbehaving in your scenario.

I noticed you were not using a default theme, and that the current theme adds some notices to various admin interfaces. Would you be able to test using one of WordPress’ own themes to rule out if this is a conflict with the theme you are using?