• March 16, 2014, 11:19 a.m.

    Yep, all those things will land in 0.6 release which is big cleanup of existing codebase.

    When's 0.6 going to happen? Not sooner than Django 1.7. 0.6 will change a lot about models so I would like to have one annoying update (data & south deprecation) instead of two.

  • Members 2 posts
    March 17, 2014, 11:03 p.m.

    Since the topic was already discussed about integrating misago into an existing Django site/application. What about the reverse part. Will misago play nice with other django applications? Can other applications be easily added, and inherit from misago user/permission model?

  • March 17, 2014, 11:18 p.m.

    If you want to use Misago as framework to build whole site around, you'll be able to. In fact this is second usecase I'm focusing on (first being stand alone solution).

    However there will be one gotcha. Misago has its own admin panel implementation and until dedicated apps start to show up, you'll have to enable Django's admin under other url's path to manage those extra apps you'll be installing.

    User model will be implementing Django's PermissionMixin which means it will support Misago's Roles/Permissions implementation as well as standard Django Groups/Permissions for you to use in your sites.

  • Members 11 posts
    Sept. 27, 2014, 10:19 a.m.

    Hi,
    I was looking for a Django app forum and found Misago to be exactly what I was looking for.
    Unfortunately it seems that it won't work as a standard Django app.
    Given that you are currently redesigning it in the reverse way (able to integrate other Django apps), can you describe what will be the remaining problems after 0.6 to use it as a Django app ?

    Thanks,

  • Sept. 27, 2014, 4:53 p.m.

    If your project is already in production, making your user model inherit from misago.users.models.User will be only challenge I can think of.

  • Members 11 posts
    Sept. 27, 2014, 5:23 p.m.

    That would be really great.
    But have you changed your mind ?
    You have written in another thread (Update on 0.6):

  • Sept. 27, 2014, 6:17 p.m.

    Propably my opinion is evolving as more features are done for 0.6 release.

    But hey! While 0.6's is still incomplete, features that have impact on problem at hand are already there, so why not spend few hours seeying what issues are there with getting Misago 0.6 to work with your project?

  • Members 11 posts
    Sept. 27, 2014, 6:26 p.m.

    Will do !
    I was just making sure that your vision was also including Misago as a standard Django app.
    It would have made no sense to try to include Misago and provide all kind of pull requests and bug reports if you don't intend to have Misago going in that direction.

    But now that you told me that your opinion on the subject has evolved, I will give a try and keep you updated.

    Thanks,

  • Members 9 posts
    April 9, 2015, 12:04 a.m.

    bummer, it's in Django 1.8 now :D

  • April 9, 2015, 12:21 a.m.

    It is is, but most of templating action happens in Ember's HTMLbars anyway.

    And there's no telling how complete Jinja2 support is. From what I see all you can do is render templates via them, but there's no word on makemessages support in Jinja or interop, so primary reason for drop still stands IMHO.

    edit: I've checked it and it turns out that in terms of Jinja2 support, Django 1.8 does less than other compat apps like Coffin, that gave you support for i18n, makemessages, as well as attempted to support Django's filters and tags in Jinja, so its no-go.