Flarum + Django (flarum-ext-django)

WaldemarHamm

I updated the original post with a ToDo-List for convenience reasons.

Franz

I would have just resorted to an iframe, but apparently you want to avoid that ?

So, yes, you'd have to recreate the HTML skeleton that Flarum needs, and include the proper JS files - but that's really not too much work, even in Python.

As for authentication, I'd probably replicate the parsing logic in Flarum - you'd need to replace Flarum's authentication middlewares with your own...

WaldemarHamm

Franz Sounds like I'd need to fork Flarum and just make a Django-Package out of it and then render it on my own. Any objections to that?
This way I could skip the Django-package/Flarum-extension necessity. But then again I don't know how I could assure up-to-date Flarum code without manually updating it.

I'll ponder about this some more and try to follow your suggestion rendering Flarum through Django first.

Franz

WaldemarHamm No fork is needed, I'd say. You'll need

your Flarum extensions for proper authentication with Django's auth system, and
a Django package that renders the basic HTML that Flarum needs (wrapped with your site's HTML) and includes the JavaScript.

WaldemarHamm

Franz The second point (btw. how do you make bulleted lists? The markup guide said something about beginning each line with - but doesn't work for me ^⁾ means I need to copy or link the Flarum HTML template and also copy (or better link) the Flarum javascript and include it within the Django HTML template, correct?

WaldemarHamm

Franz luceos First step to success:
I managed to set up an Ubuntu server that successfully serves a django app via postgres on domain.tld and Flarum via mysql on forum.domain.tld via nginx.

I will look at how everything looks and works now.

Man had I a lot of stuff to work out getting there...

WaldemarHamm

Franz So I'm looking at the flarum files right now. The three important viewing files should be index.php, admin.php (and maybe api.php).
But all they seem to do is require some other file that itself requires a bunch of stuff. Sadly I'm not experienced enough with PHP and apps in general with such a deep structure.

Could you point me to the location of the relevant HTML skeletons and tell me the JS files I'd need to link? That would help me a lot ?.

WaldemarHamm

Well the js and css stuff seems to be in the folder /assets alright. (Tell me if there's more ?.) Looking for the HTML skeleton now.

EDIT: Could it be that there's no real HTML skeleton per se, but that it is really created fully dynamically?

EDIT2: I guess that it's all about the IDs in the HTML and the JS playing with it. I'll try to dig in some more but would appreciate any help.

EDIT3: Yeah, I found the views folder in /vendor/flarum/core. So the HTML skeletons are PHP files. Looking at the forum.blade.php there are three tags that seem PHP-related. One is for the forum URL, the other for the title. And the last one is for the content.
Franz Now two questions remain:
1. How would I go about asking the API for the forum URL and title, so I could include that in my Django template.
2. How can I replace the {!! $content !!} part? Is this PHP or JS?

Sadly flarum.org/docs/templates is not yet implemented/available.

WaldemarHamm

By the way: If anyone had problems up till now setting up Flarum with nginx on Ubuntu 15.10 server within a local VM guest, you can ask me up.

luceos

WaldemarHamm 1. How would I go about asking the API for the forum URL and title, so I could include that in my Django template.
2. How can I replace the {!! $content !!} part? Is this PHP or JS?

Create a simple api client (for instance php has Guzzle) that can do REST calls. You should be able to work with that, I created a simple API wrapper in PHP here.
This is actually a template engine called Blade, which is part of Laravel, see its blade documentation. The template engine is very much like raw PHP, in this example $content is simply a PHP variable injected into the view by a controller. The {!! tags around it tell the Blade parser that it should not escape the contents/variable value inside it.

WaldemarHamm

luceos

From what Franz mentioned I understood that there are already API-calls in place. Is that not the case for the forum title and url?
I see. Django also has template tags that look somewhat like this. I already looked it up but I am not sure what the {{!! content !!} part means to the whole template yet. Right now I'm about to include the JS to the template without the {!! content !!} and see what happens.

luceos

WaldemarHamm

Api endpoints (an API server) exists and the js in the html call them. You asked specifically how to get the forum title and url from the API. You'd need to call the API in that case.
Let us know what happens ?

WaldemarHamm

luceos So I could use URL/api.php for this, right? Could you give me an example URL I could call for the forum title or url? ?

WaldemarHamm

WOOHOO it works!
I just messed up putting the script part at the very end of the HTML template, the app-composer div was still under it.

Now I need to fix an issue where access to the fonts is not allowed due to anti CSRF stuff and I think the part with the babelhelper is generated dynamically.

luceos The part that starts this way:

babelHelpers._extends

and then has this very long JSON. This is dynamically generated, right? How can I substitute this correctly in my template?

WaldemarHamm

forum-acaa4b60.js:1368 Uncaught Error: Please ensure the DOM element exists before rendering a template into it.

What the glob... off to debugging this now.

luceos

WaldemarHamm access to fonts can be fixed with CORS, you can handle that with .htaccess or some other method based on your webserver.

Going to bed, have to get back to you about those other issues, or maybe Franz beats me to that.

WaldemarHamm

luceos Thank you a lot! Have a good night ?.

Yeah I can't click on the discussion itself as well: No 'Access-Control-Allow-Origin' header is present on the requested resource.

WaldemarHamm

Well, even though I added

add_header Access-Control-Allow-Origin "*";

to both server configs in nginx, only the issue with the fonts on the homepage disappeared. When I click on the test discussion I created I get another error:

XMLHttpRequest cannot load http://forum.django.local/api/discussions/1?page%5Bnear%5D=0. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://django.local' is therefore not allowed access. The response had HTTP status code 500.

So I need to fix the CORS-stuff as well as work with the link. I can't have the discussions link to domain.tld/somethingelse/somethingevendifferent or else Djangos URL-conf stuff will kick in after a reload and block it.

WaldemarHamm

Ok, so from what I understand this error means that I can't retrieve the API value because there is no Access-Control-Allow-Origin header in the requested resource at all.

scratches his head

« Previous Page Next Page »