Page break error display :The "logo" entity type does not exist

Yes, there is an issue with this because the entity type that is being used for this file is logowhich does not exist hence the error.

In the core/modules/navigation/src/Form/SettingsForm.phpthe code to add/delete records uses the "logo" as the entity name
$this->fileUsage->add($new_logo_managed, 'navigation', 'logo', 1);
$this->fileUsage->delete($previous_logo_managed, 'navigation', 'logo', 1);

The file usage is a view that requires it to be an entity type /admin/structure/views/view/files/edit/page_2 which is throwing an error.

Now I am not sure whether this is a bug in the Navigation module or core itself that allows an entity name in File usage that does not even exist.

I wanted to update regarding the issue we discussed. I pulled the latest code from the 11.x branch, and I was unable to reproduce the issue locally. This behavior was consistent with the problem we encountered previously, so it seems to be resolved with the recent changes.

For reference, I’ve attached recording that demonstrate the current state of the application.

Please let me know if you need any further information or if there’s anything else I should look into.

I have taken the latest pull , however still replicable this issue, attaching the screenshots.

I tried to upload the navigation custom logo image
Then click on file menu on the left sidebar this page open, you 'll redirect to this page: admin/content/files
Click on the Usage link for this file , page break with above mentioned error.

Tried to debug while calling file usage API(), correct entity type missing that causing error, working on it.

Tried to address issue & added test coverage with minimal changes in relevant existing test.

Please review, moving NR.

I have closed this issue as I was unable to reproduce it with the latest pull from the 11.x branch. It appears that the issue has been resolved with recent fixes.

If anyone encounters a similar issue in the future, please feel free to open a new issue.

Thank you!

have reviewed patch. yes oversight in original name spacing for file usage.

will also probably need an update hook to check if any update any existing entries to be updated to 'file' (as $new_logo_managed->getEntityTypeId() will equal 'file').

Thanks for reviewing it, looking into it.

Tried to address the feedback. Please review, moving NR.

Good catch!

The file usage logic should be gone as part of 📌 Store the file path instead of ID for the navigation logo Needs work , so I would prefer to focus on addressing that issue that indirectly would solve this one.

@plopesc should this continue? Or closed and credit moved over?

Let’s close this as a duplicate of 📌 Store the file path instead of ID for the navigation logo Needs work , and continue efforts there, and also remember to transfer credits. I'll make a note of those who contributed here on the other issue.