Paul

I have dug a little deeper.I am getting a warning in 2.1 ...

D:\Users\mike\envs\xxct3\lib\site-packages\django\forms\widgets.py:126: 
MediaOrderConflictWarning: Detected duplicate Media files in an opposite 
order:
admin/js/vendor/jquery/jquery.min.js
/tinymce/filebrowser/
  MediaOrderConflictWarning,

... which doesn't prevent collapsible elements collapsing. 

Django 2.2 forms.widgets.merge is merging multiple lists instead of just 
two lists in Django 2.1 so it is possible that the innocuous warning from 
2.1 becomes an unintended elimination of the particular bit of js which 
collapses those elements when javascript files are in the wrong sequence.

I'm guessing the actual problem in 2.2 is likely from collectstatic 
skipping files which already exist. Try deleting all your static files and 
run collectstatic again.

Mike

On Sunday, July 14, 2019 at 10:53:14 AM UTC+10, Mike Dewhirst wrote:
>
> Are you using TinyMCE, filebrowser and Grappelli? 
>
> I had a similar problem as you describe and resorted to 
> django-tinymce4-lite and django-filebrowser-no-grappelli which fixed it 
> for me. 
>
> I haven't done any deep digging so I can't be certain why mine started 
> behaving properly. 
>
> Mike 
>
> On 13/07/2019 3:11 am, Paul Michalski wrote: 
> > 
> > I just upgraded from Django 2.1.3 to 2.2.3, at which point collapsible 
> > elements in the admin interface stopped working. I’m using IE11, and 
> > in the console I see the error “object doesn't support property or 
> > method 'matches'”, with a reference to line 35 of collapse.js in the 
> > admin package. I did some research and I found that IE11 doesn’t 
> > support the “matches” function, so I just modified the admin base 
> > template with a polyfill to get things working on my machine. But the 
> > collapsible elements were working fine with my old version of Django 
> > on IE11, so it looks like a polyfill (or something) was removed in the 
> > most recent Django version. Does anyone know what might have changed? 
> > If something was changed, I think this is a bug – we shouldn’t have to 
> > modify the templates in the admin package to use IE11. 
> > 
> > This is my first post. Thanks for any comments or suggestions. 
> > 
> > 
> > Paul 
> > 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8d34bf59-bcab-4540-a1bd-74794e3a1f71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to