Changes between Initial Version and Version 1 of Ticket #34939


Ignore:
Timestamp:
Nov 2, 2023, 1:26:07 AM (13 months ago)
Author:
davidtoulmin
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #34939 – Description

    initial v1  
    5353The <p> element only shows up if I manually stop `manage.py runserver` and restart it. Then the changes are reflected on all forms using that widget, but if I make another change to the widget template the change isn't reflected again until another refresh.
    5454
    55 I have replicated this across multiple widgets (including non EmailInput based widgets), widget templates, forms, form fields. I've replicated this across multiple colleagues' computers (both of my linux machines, and my colleagues' Mac machines). And I seem to have narrowed it down to a change between 4.0.10 and 4.1.0. In 4.0.10 (and all other 4.0 versions I've tested) a change to a widget template is instantly reflected in the page on page refresh (as I would expect). For version >=4.1.0 (including the current 4.2.7), this strange behaviour where template changes aren't reflected on page reload occurs, with the only change being updating the version of Django. I've read through the release notes for 4.1 and the only thing that seems like it might be relevant is the "cached template loader" as I don't have `OPTIONS['loaders']` set, but I don't see why that would only be caching templates in this one very specific circumstance, and why that would be affecting a `manage.py runserver` local environment.
     55I have replicated this across multiple widgets (including non EmailInput based widgets), widget templates, forms, form fields. I've replicated this across multiple colleagues' computers (both of my linux machines, and my colleagues' Mac machines). And I seem to have narrowed it down to a change between 4.0.10 and 4.1.0. In 4.0.10 (and all other 4.0 versions I've tested) a change to a widget template is instantly reflected in the browser upon page refresh (as I would expect). For version >=4.1.0 (including the current 4.2.7), this strange behaviour where template changes aren't reflected on page reload occurs, with the only change being updating the version of Django.
     56
     57I've read through the release notes for 4.1 and the only thing that seems like it might be relevant is the "cached template loader" as I don't have `OPTIONS['loaders']` set, but I don't see why that would only be caching templates in this one very specific circumstance, and why that would be affecting a `manage.py runserver` local environment.
    5658
    5759Any help would be much appreciated. Let me know if I can provide any further information.
Back to Top