Enable use in Django 3.0 and later

Django 3.0 has been released, and contains some changes that are not yet compatible with django-plotly-dash.

For starters, X-FRAME-OPTIONS now prevents the serving of content into iframes by default. This is probably the cause of #214

[pallavg]

Hi - Just some feedback. I am using Django 3.0.2 and Plotly/Dash/Boostrap4. I am able to get django-plotly-dash working for a sample dashboard with the following:

1. In settings.py, set X_FRAME_OPTIONS = ‘SAMEORIGIN’

2. In my html file, I had to use the plotly_app_bootrstrap tag for the app to render correctly.

{% extends "base.html" %}

{% load static %}

{% block page_content %}

{% load plotly_dash %}
<div class="{% plotly_class name='ProjectDashBoard' %} card">
{% plotly_app_bootstrap name='ProjectDashBoard' %}
</div>

{% endblock %}

If I use plotly_app, it shows it up inside a very small iframe. If I use plotly_direct, I just get a ‘Loading…’ output. I think this probably incorrect usage on my since I am using dash_boostrap_components + bootstrap4 css so plotly_app_bootstrap seems to be the way to go.

Beyond that, I didn’t encounter any other major issues with using this nice library on Django 3.0.2.

It would be good if the X_FRAME_OPTIONS issue could be resolved in the near future.

[robd003]

Hey guys, can we still support Django 2.2 since it’s an LTS release?