Bug #105946
openDont store missing-icon markup in icon LocalStorage
0%
Description
When using a icon-identifier, that has not been registered yet (this happens quiet often in development), typo3 will render the missing icon svg. So far so good. But typo3 will also persist the missing-icon markup in the LocalStorage. So you won't be able to fix the issue unless you clear your local storage. If you don't know this it is really confusing because it might work when deployed (other LocalStorage) or when simply changing the icon identifier.
This is really annoying. I suggest using the correct HTTP response code (404) if a icon can not be loaded and avoid using additional caching logic.
Updated by Ulrich Koch 20 days ago
· Edited
Philipp Wrann wrote:
When using a icon-identifier, that has not been registered yet (this happens quiet often in development), typo3 will render the missing icon svg. So far so good. But typo3 will also persist the missing-icon markup in the LocalStorage. So you won't be able to fix the issue unless you clear your local storage. If you don't know this it is really confusing because it might work when deployed (other LocalStorage) or when simply changing the icon identifier.
This is really annoying. I suggest using the correct HTTP response code (404) if a icon can not be loaded and avoid using additional caching logic.
I can confirm this for TYPO3 v13.4.4 in the area of the New content element wizard. I have no idea how much time I spent on this.
Even if you replace an existing icon, you will not see the new icon in the New content element wizard without deleting the local storage - in contrast to the display of the icon on the content element and in the dropdown of the CType itself, where it works as before.
Updated by Garvin Hicking 19 days ago
- Has duplicate Bug #105994: Strange behaviour of icon use in custom content elements added