Ticket #1301 (closed defect: fixed)
[PATCH] Improved reloading mechanism in TurboKid
|Reported by:||chrisz||Owned by:||faide|
The reloading mechanism in TurboKid? did not work properly when you have two templates that are dependent on the same base template. When you update the bas template and load the first template, the template and its base template is reloaded. But when you load the second template, it is not reloaded though its base templated has changed. This leads to an incompatibility of the template and its base template, resulting in the notorious "Initialize / NoneType? not callable bug".
The attached patch improves the reload logic. We do not store the mtime for the template files, but the maximum of the mtime of the template and all its base templates. If a base template has been touched, the template will also be reloaded.
- Owner set to jorge.vargas
- Component changed from unassigned to Kid
- Owner changed from jorge.vargas to faide
- Status changed from new to assigned