Deleted user, now page has errors.

This is line 419 of ft.file.php:

$file_info['id_path'] = array('/'.$file_info['file_id'], array('path_variable' => TRUE));

This is line 529 of boot.common.php:

header("Status: {$code} {$text}", TRUE);

I (not logged-in) am not seeing any errors.

I see that these errors are not public facing, which is good.

Here are there errors displayed:

Notice Undefined index: file_id ee/EllisLab/Addons/file/ft.file.php, line 419 show details

Severity: E_NOTICE

Warning Cannot modify header information - headers already sent by (output started at ee/legacy/core/Exceptions.php:115) ee/EllisLab/ExpressionEngine/Boot/boot.common.php, line 529 show details

Severity: E_WARNING

The Notice on is on there 6 times. If anyone can help, I’d appreciate it. Thanks!

It shows up on any page that has entries.

An employee left our organization and as a security precaution, I removed their account and had their posts assigned to the person who is taking their place. After doing this, this page: http://www.hillikerymca.org/employment is now full of errors. I had EE3.4 at the time. I decided to see if updating to 3.4.3 would magically fix it (wishful thinking, I know) but it did not. Can anyone help me understand what is happening here and how to fix it?

Do you have a backup of the database?

No backup from before deleting the member.

Start by looking at the database and make sure that the entries that were reassigned have the new author and that the old author is no longer in the members table.

After you get this sorted out I’d recommend getting a backup procedure in place and develop and test locally. Can’t tell you how many times that’s saved my bacon.

Its been a while (this site and its error was sort of low priority).

I looked around in the database but couldn’t identify where the authors are listed for the channel entries. When I look at all of the entries in ExpressionEngine, there is an author listed for each one, so I assume there are no empty fields in the table. Where would I look specifically to double check?

Could this error be related to any thing else?

I have resolved this issue, although I can’t pinpoint what exactly caused it…but I noticed the pages these errors occurred on were pages that were pulling entries. I started to close entries one at a time and began to notice certain entries were responsible for the errors. I would remove certain ones and instances of the error would go away. I created new entries based on the old ones and then deleted the old ones and this seems to have resolved the issue.