Marius L. J.

Hiya!

The themes you use as an example here have empty style.css files, as they are Block Themes, which make use of WordPress’ Site Editor instead. This means they make use of a concept called “Global Styles” allowing the theme to put all its styles into code in a theme.json file instead, which again allows the users to make any style changes from the admin interface instead.

You can learn more about this, and how to use it, at https://learn.www.ads-software.com/lesson-plan/how-to-style-your-site-with-global-styles/

It looks like you may have hit the trifecta of a plugin incompatibility, and an incomplete update ??

I would continue with James’ recommendation for manually updating WordPress’ files then, sorry about the inconvenience there!

You will need to check your server error logs to find the actual message here, but most likely a plugin or your theme is not compatible with the new WordPress release for some reason.

If you are unable to find your way to such a log file, you may need to follow the “Deactivating all plugins” step from the troubleshooting guide.

It looks like you either have an incomplete update, or have plugins that would normally combine CSS and JS files which was not quite ready for the update.

I would suggest attempting a manual update first, to do so download a fresh copy of the latest.zip file for this release (top right on this page) to your computer, and use that to copy up. You may need to delete the wp-admin and wp-includes folders on your server (NOTE: do not delete the?wp-content?directory or your?wp-config.php?file)?Read the?Manual Update directions first.

Hiya! It’s definitely something we can replicate, although not directly intentional, there’s a good reason why it does happen.

So to capture jQuery deprecation/fatal errors, a global error handler is added by this plugin. A side effect of this is that any code that does not it self implement error handling will be caught by the same check, and thus be suppressed).

That said, it may be worthwhile looking into surfacing any errors that are not covered by the jQuery checks (if anyone would like to help with that, the code is available at https://github.com/WordPress/jquery-migrate-helper)

Hiya @sp17mf,

Looking at your file, it would appear your site may have been compromised.

Don’t worry though, this can happen, we recommend reading over https://www.ads-software.com/documentation/article/faq-my-site-was-hacked/ and following it’s suggestions, likely your host can help with restoring a backup of your site from before any bad code was added to it.

Hiya,

I’m not able to reproduce this issue on a fresh WordPress 6.2.2 installation, have you attempted the normal troubleshooting steps of disabling all plugins and then seeing if the problem goes away?

Hiya @nspeakingarch,

This is the support forum for the open source WordPress software, and we do not sell anything here.

It looks like your host is bluehost, so you should reach out to their support over at https://www.bluehost.com/contact to resolve this ??

Hiya,

I can ease your mind here, as reinstalling will only replace WordPress’ core files, and will never touch your content or uploaded media.

Hiya!

WordPress’ automated updates for security updates (the third digit in the version number) is generally enabled by default, there’s no user interface for this built into WordPress itself.

You can either control how updates are handled using a plugin, through the setting file (wp-config.php), and in some cases your hosting provider may have setting for this in their control panel.

To change this via the config file, you can follow the documentation at https://www.ads-software.com/documentation/article/configuring-automatic-background-updates/ (make sure to search in the file first to see if theyve been set up already, as setting up the same value twice will cause an error on your site until you remove the duplicate ?? )

As some of you may have noted, WordPress 6.2.2 was just release, which provides additional hardening to the original security issue, and changes up the logic to allow for shortcodes within site editor templates again.

The security and editor teams have been working asynchronously through the week since 6.2.1 was released to find a good solution here that would restore the previous shortcode functionality, without re-introducing any the security concern that prompted the initial removal, which is what allowed for such a quick solution to be found.

This isn’t the first time WordPress has had a rapid followup release, they’re not common, but it all depends on the underlying issue, and how it may impact users.

Hiya,

It’s not impossible to think that you may be experiencing synchronization issues if your host has files replicated between servers (for example), because if the file is deleted, it is not possible for the plugin to execute that code (since it wouldn’t be there to be read and ran).

As for the disabled plugins affecting anyone, this may be another plugin, or your theme, doing something strange to the plugin loading, force-loading an entry (which unfortunately overwrites what the list of active plugins should be). We’ve not seen a lot of those cases after version 0.9, but there may be scenarios we’ve not accounted for, so I encourage you to open a support thread to look into what plugins or themes you have running and maybe we can find a fix for that together.

test reply to “open”?

Hiya, I’m Marius, one of the moderators with www.ads-software.com

Firstly, there’s nothing wrong with reviewing the experience with a plugins paid solution, as the plugin upsells their services via the free plugin and the listing here on www.ads-software.com, this makes the entire flow, free to paid, one unified experience that can be reviewed.

That said, the tone you’ve adopted in your last reply, @cosmindan22, is rather hostile, and not very helpful at all. I do ask that you keep in mind that we’re all trying our best to help each other here, and that good intent should always be presumed.

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

Hiya @nurk,

It looks like you may have an incomplete update on your hands, as some new files introduced in WordPress 6.2 are not available.

The quickest way to resolve this is to perform a Manual Update (if possible), don’t worry though, this will only replace WordPress files, your media and content should still be fine.

Or, if you are with a managed host, let them know that the update failed, and that it needs to be performed anew ??