• March 24, 2017, 1:39 p.m.

    Just so I can customize it with my own logo, favicon and such.

    Love the system, btw. :)

  • Project Lead March 24, 2017, 4:10 p.m.

    Hey there Sanjaya!

    Assuming that you've setup Misago with misago-start.py testforum, you'll get this directory structure:

      + avatar_store
      + media
      + testforum
        * __init__.py
        * settings.py
        * urls.py
        * wsgi.py
      + static
      + theme
        * static
        * templates
      + cron.txt
      + manage.py

    Misago uses special scripts called "finders" for templates and assets. Default setup makes those finders search for assets in your "theme" directory and only then fallback to Misago's default.

    So assuming you have custom favicon.ico, you may replace default one with it by adding it to your theme/static/, like theme/static/favicon.ico, and then running python manage.py collectstatic when deploying your site.

    You may use this approach for other icons as well (Misago comes with plenty of apple-specific icons), or by overriding default templates with custom html.

  • March 24, 2017, 5:10 p.m.

    This brings up another question, how would one edit the colors to the site? For example: Green instead of the default white

  • Project Lead March 24, 2017, 5:13 p.m.

    You'll need to either add custom CSS file and override misago/base.html template to include it, or grab default less files and modify them to suit your needs. Either approach is good, but forking less files will allow you for easier customisation due to bootstrap's style variables.

    ...on sidenote, it may be good idea for Misago to come with separate template for head.html section for board admins to customize on their own.

  • March 24, 2017, 5:22 p.m.

    Indeed, it would be also cool if you could directly edit the colors of the site via the admin panel. This would help a lot of people since they wont have to go fishing for files. :)

  • Project Lead March 25, 2017, 1:26 a.m.
  • arrow_forward

    Thread has been moved from Questions, Problems and Issues.

  • March 26, 2017, 10:03 p.m.

    So, ive create a custom favicon.ico and placed it via theme/static/favicon.ico and invoked the command python manage.py collectstatic . When I then deploy my site, it still shows up with the default one. Ive been trying this for an hour with no success.

    Going to /static/favicon.ico shows the favicon image, btw.

  • Project Lead March 26, 2017, 10:40 p.m.

    Looks like browser cache to me.

  • March 26, 2017, 10:41 p.m.

    How does one fix that?

  • Project Lead March 26, 2017, 10:49 p.m.

    I dunno. If you are sure that favicon shown under the /static/favicon.ico shows correct (new) image, I would look up on google possible approaches to forcing favicon's refresh in browser. Speaking from experience, browsers update favicons once in a while, but I've never pinpointed triggers for such updates.

  • March 26, 2017, 10:50 p.m.

    I deleted all of the default/favicon images from the folder and still it shows up. Im not sure where else that image could be from.

  • Project Lead March 26, 2017, 10:51 p.m.

    Like I've said, from browser cache most likely.

  • March 27, 2017, 12:44 a.m.

    So, really nothing I can do? insert sad emoji here lel

  • Project Lead March 27, 2017, 8:50 a.m.

    There's two things to consider actually:

    Firstly change your static files storage to one that fingerprints assets. This is approach I'm using on this forum, because I deploy changes to frontend frequently, and this assures that users will not browse with outdated assets.

    Second one is see if favicon you are testing is actually right icon for your device/browser. Like other things, favicons got annoyingly complicated over last years. Just consider Misago's html for icon:

    <link rel="apple-touch-icon" href="/static/apple-touch-icon.82ce80504b45.png">
    <link rel="apple-touch-icon" sizes="57x57" href="/static/apple-touch-icon-57.d4828c32a03b.png">
    <link rel="apple-touch-icon" sizes="72x72" href="/static/apple-touch-icon-72.5a5be5451c80.png">
    <link rel="apple-touch-icon" sizes="76x76" href="/static/apple-touch-icon-76.9ab7eeab9916.png">
    <link rel="apple-touch-icon" sizes="80x80" href="/static/apple-touch-icon-80.a64487d138d9.png">
    <link rel="apple-touch-icon" sizes="114x114" href="/static/apple-touch-icon-114.a29d0645024f.png">
    <link rel="apple-touch-icon" sizes="120x120" href="/static/apple-touch-icon-120.82ce80504b45.png">
    <link rel="apple-touch-icon" sizes="144x144" href="/static/apple-touch-icon-144.ad7d88d010d2.png">
    <link rel="apple-touch-icon" sizes="152x152" href="/static/apple-touch-icon-152.575c69f28f51.png">
    <link rel="apple-touch-icon" sizes="167x167" href="/static/apple-touch-icon-167.a8bb70902968.png">
    <link rel="apple-touch-icon" sizes="180x180" href="/static/apple-touch-icon-180.5c839d86d081.png">
    <link rel="shortcut icon" href="/static/favicon.0b87dfbd7c18.ico">
    <link rel="icon" sizes="16x16 32x32" href="/static/favicon.0b87dfbd7c18.ico">

    There's 12 icons involved. But wait, that favicon.ico? Its actually three icons packed in one file.

    And here's chrome guys explaining how favicons are treated differently than other assets because they are actually tied to bookmarks and browsing history, not assets cache.