Re: settings.DEFAULT_CONTENT_TYPE incompatibility with admin

2017-02-12 Thread Adam Johnson
> > Would Django hard code "text/html" as the default? Yes, that's exactly what would happen. Thanks for the bump up, finally added a ticket: https://code.djangoproject.com/ticket/27829 On 12 February 2017 at 07:28, Brian May wrote: > On Friday, 13 January

Re: settings.DEFAULT_CONTENT_TYPE incompatibility with admin

2017-02-12 Thread Brian May
On Friday, 13 January 2017 19:22:13 UTC+11, Aymeric Augustin wrote: > > I agree that this setting has become less useful now that > has won. > > It made more sense when it wasn’t clear whether XHTML1.1 would take over > HTML4. > > I’d be interested to hear about use cases, if someone still uses

Re: settings.DEFAULT_CONTENT_TYPE incompatibility with admin

2017-01-13 Thread Aymeric Augustin
Hello, I agree that this setting has become less useful now that has won. It made more sense when it wasn’t clear whether XHTML1.1 would take over HTML4. I’d be interested to hear about use cases, if someone still uses it and reads this. -- Aymeric. > On 13 Jan 2017, at 04:10, charettes

Re: settings.DEFAULT_CONTENT_TYPE incompatibility with admin

2017-01-12 Thread charettes
+1 Le jeudi 12 janvier 2017 08:11:09 UTC-5, Florian Apolloner a écrit : > > > > On Thursday, January 12, 2017 at 11:56:49 AM UTC+1, Marc Tamlyn wrote: >> >> DEFAULT_CONTENT_TYPE does sound like a setting which shouldn't exist. >> > > +1 > -- You received this message because you are subscribed

Re: settings.DEFAULT_CONTENT_TYPE incompatibility with admin

2017-01-12 Thread Florian Apolloner
On Thursday, January 12, 2017 at 11:56:49 AM UTC+1, Marc Tamlyn wrote: > > DEFAULT_CONTENT_TYPE does sound like a setting which shouldn't exist. > +1 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To

Re: settings.DEFAULT_CONTENT_TYPE incompatibility with admin

2017-01-12 Thread Marc Tamlyn
DEFAULT_CONTENT_TYPE does sound like a setting which shouldn't exist. On 12 January 2017 at 10:53, Adam Johnson wrote: > Having reviewed the ticket a bit and thought about it, I've had two > thoughts: > >1. The current patch doesn't fix existing custom views > >

Re: settings.DEFAULT_CONTENT_TYPE incompatibility with admin

2017-01-12 Thread Adam Johnson
Having reviewed the ticket a bit and thought about it, I've had two thoughts: 1. The current patch doesn't fix existing custom views which the docs explain how to use, and I've seen used quite often.

settings.DEFAULT_CONTENT_TYPE incompatibility with admin

2017-01-10 Thread Tim Graham
According to ticket #23908 [0], By using the setting: DEFAULT_CONTENT_TYPE = "application/xhtml+xml" The admin site no longer renders correctly. Do you think we should try to fix this by having all the admin responses specify content_type="text/html"? That requires a lot of changes [1] --