Hey! Nice extension @askvortsov. Thanks for that. I noticed that when we are using the newer FontAewsome version, the circle icon isn't renderized, causing this problem:
categories

Can you add an option in config to allow us to edit the class of the icon or update the extension?

19 days later

after flarum update, it seems to be broken - any news here?

    m4v3rick I'll take a look next week to see if I can replicate the problem. At the moment I am using the extension under version 1.6 of Flarum and everything is working properly.

    5 days later

    Feels like it's probably a custom styling issue of some sort

      @m4v3rick I just upgraded my forum to version 1.7.2 and it still works without any problem.

      Take a look at the browser console for any errors to see what's going on, but I think the same as askvortsov and it's probably a CSS tweak.

      m4v3rick I have the same problem on 1.7.2 (was also an issue on 1.7.0).
      I have disabled custom styles and all extensions besides Tags and Categories and the issue persists.

      There are no errors in console.

        sorry for the late reply - since 1.7.2 icons are not loaded anymore. Console message: [Intervention]Images loaded lazily and replaced with placeholders. Load events are deferred.

        image

        Tell me, how do you make child categories? I don't understand

        6 days later

        askvortsov I have made a fresh install using my current database with only Tags and Categories enabled and it still happens. It does indeed not happen on a fresh database though.

          22 days later

          Noticing with a new install and dark theme enabled, child tags/sub-categories have visible icons on hover but not by default.

          Anything I can edit css-wise to make the default background color different? I appreciate any direction.

          Never mind. Figured it out.

          14 days later

          askvortsov I disabled everything except Tags and Categories, removed all the custom stuff and CSS, ensured that I cleared the cache after every change, cleared the vendor folder and re-downloaded it all via composer, manually removed all the files in the public/assets directory and cleared everything in the storage directory, tried every setting categories exposes and played with the element inspector in the hopes that I would find the evil CSS property. Next step in debugging would be to use the fresh database again and slowly migrate everything, but I was too lazy for that. Thus it remains a mystery to me!