Since October, after formatting bullet points in the ShopBuilder, you receive an ordered, numbered list (<ol>) instead of an unordered list (<ul>). This behaviour is intentional and is due to a change in the underlying component.Cause of the behaviourThe behaviour is due to a change in the underlying component, the Quill Editor v2, which the ShopBuilder uses. Unfortunately, in this new version, bullet points (<ul>, unordered lists) are no longer supported, only numbered lists (<ol>, ordered lists). A direct change to this behaviour is not possible.Alternative for creating unordered listsIf you want to create an unordered list with bullet points, you can use the ShopBuilder's Code Widget and manually insert the HTML code for an unordered list.Example of an unordered list in the Code Widget:HTML <ul> <li>First item</li> <li>Second item</li> <li>Third item</li> </ul>

To ensure your customised favicon is displayed permanently and correctly in all future build and linking processes, you must integrate it via the designated assistant.Step-by-step guideCheck file for internal format: Make sure the favicon has a genuine .ico file structure and is not merely a renamed PNG file. If necessary, convert the file beforehand using a conversion tool.Upload file into the system: Upload the converted favicon.Run the assistant:Navigate in your system to the assistant for your webshop (plentyShop LTS).Select the newly uploaded .ico file in the icon configuration step.Complete the assistant fully.Remove manual LTS lines (if present): Remove manual favicon links from the normal plugin configuration. The values from the assistant are automatically reflected correctly.Why setting up via the assistant is importantWhen saving in the assistant, the image is loaded directly from the CDN, checked for its valid mime-type and stored in the root directory. If the icon is only specified manually in the plugin configuration,...

After updating the favicon, it may happen that the browser continues to show the old icon or the default Plenty logo. This is usually due to the specific caching mechanisms of favicons and browsers.Technical causesBrowser cache: Favicons are stored by browsers extremely aggressively and sometimes for up to 14 days in the local storage of the device. A normal page visit therefore often does not reload the icon from the webspace.Invalid file format when uploading: If an image file (e.g. PNG) is merely manually renamed to .ico, it retains its internal PNG signature. The configuration assistant recognises this mime type as invalid, aborts the upload to the server, and falls back to the default logo.Steps to resolveConvert the favicon correctly: Use an online conversion tool (such as convertico.com) to save the image in a genuine .ico format. Simply renaming the file extension is not sufficient.Re-upload and assign: Upload the converted file again to the file manager and select it in the assistant.Clear the local browser cache:Perform a...