• Oct. 7, 2017, 12:25 a.m.

    Misago 0.12 has been released!

    This release focuses mostly on quality of life improvements for board administrators and moderators. Most important changes delivered by this release is changed implementation of loading permission providers, which hopefully will resolve the issue of Misago crashing during ACL serialization, the bug that pops up from random admins from time to time. In addition to that, some API endpoints that previously lacked such sanitization, now check if data sent to them is of expected structure, and return error 400 accordingly if this isn't the case. Previously those views would throw an error instead.

    Additionally, Misago no longer counts events produced by moderation actions to check deciding if thread shoulde be automatically subscribed to on reply. Previously performing moderation action on thread that resulted in creation of event before replying to thread meant that Misago wouldn't automatically subscribe it, against user's preferences.

    Updating instructions

    To update Misago from 0.11 to 0.12 use PIP to uninstall old Misago and install new one:

    pip uninstall misago
    pip install misago

    Then run migrate and collectstatic to make sure you database and static files are up to date too:

    python manage.py migrate
    python manage.py collectstatic

    New features


    Theme changes


    Bugs fixed

    • 893 - Tightened the input validation in various API endpoints, which would previously crash if they received incorrectly structured data.
    • 911 - Events from moderation actions are no longer accounted for when making decision if to subscribe thread on reply.
    • 920 - Fixed typo in threadslist/base.html template causing Misago to never display root-specific "forum is empty" message when no visible threads exist.

    Implementation and API changes

    • 907 - Removed excessive user.lock() calls from codebase. Moved location of thread's read transaction to the utility function.
    • 921 - Replaced lazy ACL provides initialization occurring on first request with eager one that occurs after application models have been initialized. This should hopefully resolve the issue that some people have experienced, where sometimes ACL providers were initialized twice, likely by race condition, causing hard to debug crashes on their sites.

    Documentation changes


    Localization changes

    • 913 - Some translation messages were moved around or removed as part of #893.
  • bookmark

    Thread has been pinned globally.

  • Members 11 posts
    Oct. 14, 2017, 6:32 a.m.

    Excellent forum system. Can it be suite for production or it's only for testing?

  • Oct. 14, 2017, 5:54 p.m.

    Misago is peramanent beta project. It will contain errors, mistakes and gotchas, and updating from version to version may be annoying as featureset changes.

    But if one accepts that, he or she is free to use Misago. In fact, I've removed the message telling people to don't use Misago in production from our readme when 0.6 has been released. :]

  • Members 11 posts
    Oct. 14, 2017, 5:59 p.m.

    Even released projects contain errors, mistakes and gotchas, so I'll try in production. It looks more stable, than others.

  • Members 19 posts
    Oct. 19, 2017, 7:53 a.m.

    I use it in production since 3 months and no major problems until then.

  • Members 11 posts
    Oct. 19, 2017, 7:59 a.m.

    Thanks for reply. Yes, it's stable enough for production, as I can see.

  • Oct. 19, 2017, 8:06 a.m.

    Automatic tests suite is great thing to have - makes sure that Misago's behavior for tested scenarios remains constant between changes in codebase. After that I'll be taking time off from work so I could rewrite frontend for Bootstrap 4 and React 16, hopefully also increasing tests coverage for our frontend. :]

  • panorama_fish_eye

    Thread has been unpinned.