You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be my lack of understanding of the Django settings system, but in my settings.py I set the FORCE_SCRIPT_NAME variable to 'X" so my application is located under http://servername/X/ and not http://servername/, without adding 'X' every time in urls.py.
The problem I found that 'X' is not included in the url path of the ajax message sent from the JS side and so obviously it can not be interpreted on the server.
I think the solution could be something like modifying dajaxice.core.js as follows;
It may be my lack of understanding of the Django settings system, but in my settings.py I set the FORCE_SCRIPT_NAME variable to 'X" so my application is located under http://servername/X/ and not http://servername/, without adding 'X' every time in urls.py.
The problem I found that 'X' is not included in the url path of the ajax message sent from the JS side and so obviously it can not be interpreted on the server.
I think the solution could be something like modifying dajaxice.core.js as follows;
Where
settings_value
is a template tag defined as follows:This worked for me, but I am not sure if this is the correct approach, since I am a bit lost in the many configuration options of Django.
The text was updated successfully, but these errors were encountered: