Error when no user with ID #1 is in the database

[evertalbers]

Trying to solve another issue (which I don't exactly remember but might have been caused by persistent cookies in my browser actually) I deleted all users and then started fresh, using bin/console bolt:add-user. The new users had ID's starting from 5 or so.

After this, when trying to get a page listing in the Bolt Backend, this error was shown (below). The error was solved by going into the database and setting the ID of one user to 1 (I picked the user with a DEVELOPER role, not sure if that made any difference).

[eduardomart]

I believe it's the same issue that I reported a while back: #2827

[abdellahrk]

@bobdenotter can I look into this? I made some comments on #2827.

[evertalbers]

FYI I found out later that the issue is about Bolt having records with not-existing user ID's in general, not per se #1. Just in case you didn't already know this.

[abdellahrk]

FYI I found out later that the issue is about Bolt having records with not-existing user ID's in general, not per se #1. Just in case you didn't already know this.

can you emphasize on this? @evertalbers

[bobdenotter]

Hmm, I think we shouldn't try to ensure id 1 is present, but look at it from the other direction: Why does it break if this user isn't present? And, would it be possible to handle it more gracefully. Say, if we have a location where the backend just assumes something exists, perhaps we can make it so that we use an {% if %} of some sorts to handle it gracefully.