after moving to new hoster: No new post/site/media critical error. Editing works

Post and site are showing an “critical error message ….”.

If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

Meanwhile, try:
– manually resetting your plugins?(no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.
– If that does not resolve the issue, access your server 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), navigate to /wp-content/themes/ and rename the directory of your currently active theme. Hopefully, this will force the default theme to activate and rule out a theme-specific issue (theme functions can interfere like plugins).

• This reply was modified 1 month ago by t-p.

Hi, thx for reply.

I don′t think it is there related, as I tried 2 different ones, which I installed, but never used. No difference.

This is the log: I edited the config file with

define(‘WP_DEBUG’, false);

define( ‘WP_DEBUG_LOG’, false); which is supposed to be correct, according to an 1+1 article. Though this edit already created several issues on the the dashboard site. I dont know if this is to be expected.

[24-Oct-2024 16:58:02 UTC] PHP Fatal error: Uncaught Error: Attempt to assign property “post_content” on null in /homepages/6/d1017xxxxxx/htdocs/wp-admin/includes/post.php:808
Stack trace: 0 /homepages/6/d1017xxxxxx/htdocs/wp-admin/includes/dashboard.php(556): get_default_post_to_edit() 1 /homepages/6/d1017xxxxxx/htdocs/wp-admin/includes/template.php(1456): wp_dashboard_quick_press() 2 /homepages/6/d1017xxxxxx/htdocs/wp-admin/includes/dashboard.php(274): do_meta_boxes() 3 /homepages/6/d1017xxxxx/htdocs/wp-admin/index.php(204): wp_dashboard() 4 {main}

thrown in /homepages/6/d1017xxxxx/htdocs/wp-admin/includes/post.php on line 808

The lines above seem to the relevant ones, all others are max warnings. I am by no means an expert in php though ??

This is the entry in my sql db from the above try to create a post:

022024-10-24 18:57:190000-00-00 00:00:00 Automatisch gespeicherter Entwurf auto-draft open open 2024-10-24 18:57:190000-00-00 00:00:0000 post

= auto saved post

ID=0

author 2, which is correct

• This reply was modified 1 month ago by derjackistweg.

Hi @derjackistweg

I suggest trying to replicate the same on a local website, based on old reports such as here and here the issue is usually due to duplicated entry IDs or corrupted table structure.

So you can check if the Autoincrement is set + the structure matches the https://codex.www.ads-software.com/Database_Description#Table:_wp_posts

Best Regards
Patrick Freitas

Hi Patrick,

I get the point and looked into it, as far as I am able to.

Though my issue is not “just” new posts but basically everything that writes into my SQL (afaik). I cannot also:
new post/site/category but also cannot edit my theme. I can upload a media file and it will be stored but: I cannot see/edit ANY FILE that is newly uploaded. I also cannot ad a new admin/user: It seems to work at first but the new user is not active or can be edited with a picture, name and so on.

I am assuming anything with the import of my sql is not correct:

To connect to my old SQL I needed to open it in notepad and edit the old name of the sql to the new name given by my hoster 1+1. I am not sure that this is the correct way to do it.

I tried to replicate the installation in a VM with XAMP. But I cannot upload the existing SQL with an error “maybe too big” or similar. The SQL is just 80MB, should be no issue.
The SQL import to 1+1 (my live system) creates an error with a plugin the needs a “super user”. That plugin is not used anymore, it counts visits.

At this stage I can do a lot of things, as my website is “static” now. Like new installation and so on. Main concern is: I must not loose a roughly 240 articles and some thousand photos inside of that.

When I upload a file I cannot see in media storage later:

no date, no “uploaded from”, no preview.

Hi @derjackistweg

exported my Sql and imported it to IONOS

During the import was there any error?

If you still have access to the old hosting database can you compare both databases directly in phpmyadmin do they use MyISAM or InnoDB? If, for example on old hosting it was InnoDB and on new hosting this is MyISAM, you will need to convert those.

What about a plugin conflict? Did you try already to disable all plugins and create a new post/page or add a new image?

Kind Regards,
Kris

Hi Kris,

as said in the beginning, of course I tried disabling all plugins. And of course I do not have any more access to One.com.
I downloaded the SQL once and 2 week later again on a different machine. Both DB reproduce the same error.

I did have one error uploading regarding an plug which requires super user to, it counts clicks. pretty irrelevant plug in. But even after import, deactivating/deleeting THAT plugin and reimport, no change.

The DB itself is working, so I do not see why I should have an error notice when uploading. But WP has not rights to write into that DB, but reading access.

Anyway:
I do not want to waste days learning DB and trying to manage to find an error and than trying to fix it.

I did a workaround – so this thread will be again a useless one because it mot lead into a solution.

My workaround is a 1 years old updarft backup including GB, which does not hold a roughly 30 articles. So I installed the corrupt DB, exported all articles. Installed the old backup and after that imported the articles separately.

This also works with all the above plug-ins. So there is no plug-in error.

At least if we all learn ONE THING: DO NEVER EVER DO A CONTRACT WITH ONE.COM!