Gibbs Consulting

This is probably a v2 compatibility issue - one of the known challenges is that v2 Dash essentially stops additional arguments being passed to callbacks.

@lBulgur how are you running your app?

It is quite possible that there is a cache miss causing the arguments to not be found - this could be happening when running in a debug environment as the...

@kotnikd3 one approach might be to use state within the application. In other words, instead of setting the initial arguments in the template call, create an instance of the [DashApp](https://django-plotly-dash.readthedocs.io/en/latest/models_and_state.html#the-dashapp-model)...

The [outline](https://django-plotly-dash.readthedocs.io/en/latest/demo_notes.html#session-state-example-walkthrough) in the documentation walks through how demo eight works; the 'dash' part of the code can be found [here](https://github.com/GibbsConsulting/django-plotly-dash/blob/master/demo/demo/bootstrap_app.py). Feedback on what would help fill in the gaps...

That is strange. A couple of questions about your configuration: - are other static files being served correctly? - what values do you have for `STATIC_URL` `STATIC_ROOT` and `STATICFILES_DIRS` in...

@alexwolf22 can you put the image in the same directory as the app code, or a subdirectory - assets is the conventional name for dash apps. Then run collectstatic and...

@alexwolf22 if you want to share assets, then the best thing to do is to handle them using Django's static file technology. You do need to ensure it is set...

@jchang10 this does sound a bit unexpected. Were you running in a multi-threaded or multi-process server? It is possible that there is a race condition when multiple callbacks are invoked...

The GET parameters are available to whatever view is rendering the template containing the `plotly_direct` or similar tag. You'll need to pass the necessary parameters to the dash app as...