James Huff

Whatever that is, it’s not from WordPress, and definitely not the same as WordPress’s login, which looks like this: https://wordpress.org/documentation/article/first-steps-with-wordpress-block-editor/#log-in

There is probably an index.html or home.html file in the same directory as the WordPress index.php file. Remove the index.html or home.html file, either via SFTP or FTP or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), and all should be fine.

If that doesn’t work, try editing your .htaccess file with with a plain text editor and add this to the top:

DirectoryIndex index.php index.html index.htm

Good news! This is definitely a Safari bug: https://wordpress.org/support/topic/safari-18-0-breaking-classic-editor/page/2/#post-18027846

The Safari developers are working on it at https://bugs.webkit.org/show_bug.cgi?id=280063

I guess my challenge would be to them that, based on your description, 1 of 3 things happened:

1. You, or someone with your password, logged in to your site and deleted content and reverted edits to a very specific time period. You would indeed need a logging plugin already installed to have known that. That sounds unlikely, it’s a lot of work for destruction when just deleting everything is easier.
2. You, or someone with your password, logged in to your site and restored a backup of your site to a very specific time period. You would indeed need a logging plugin already installed to have known that, and you would have needed a backup plugin to have backups in the first place. If malicious, it also sounds unlikely, it’s a lot of work for destruction when just deleting everything is easier. But also, it is an easy mistake to make if you’re already using a backup plugin.
3. The hosting provider restored a backup of the server or your account to a very specific time period without telling you. WordPress wouldn’t log any of that, but your hosting provider would have, unless either they’re trying to hide it or they don’t keep logs (which is very bad). Either way, in my experience, this does happen from time to time, hosting providers can make mistakes.

This is a public support forum, and you’re welcome to link to this if you want to keep discussing with them, so they can see our replies.

Otherwise, it sounds like you’re going to have to re-build what you lost. You might also want to consider moving https://developer.wordpress.org/advanced-administration/upgrade/migrating/#moving-to-a-new-server to a new hosting provider: https://wordpress.org/hosting/

We have some general recommendations at https://developer.wordpress.org/advanced-administration/performance/optimization/

For specific recommendations, try a tool like https://gtmetrix.com or https://tools.pingdom.com

Assuming those are inside a Columns Block, add a Spacer Block: https://wordpress.org/documentation/article/spacer-block/

Please note too that we can provide support in your native language at https://nl.wordpress.org/support/forums/

I recommend getting in touch with WooCommerce’s support about this via https://woocommerce.com/my-account/contact-support/ if you have any of their paid WooCommerce products or https://wordpress.org/support/plugin/woocommerce/ if you do not.

I’m not sure, I’m not one of the developers so haven’t been able to keep track.

Taking a look now, it seems to be fixed in the Gutenberg plugin, and slated for merge with WordPress 6.7.

So, if you want the fix now, install and activate: https://wordpress.org/plugins/gutenberg/ (and, ignore the reviews/rating, most of them are just “I hate the block editor”)

• This reply was modified 8 hours, 46 minutes ago by James Huff. Reason: fixed typo