#5739 (Oops, get_atomizer(...) returned None)
by Luc Saffre · in Developers · assigned to Luc Saffre
Résumé
Concepts sous-jacents
Commentaires
- 1 année, 5 mois ago by Luc Saffre about #5739 (Oops, get_atomizer(...) returned None) : Uff, I found the explanation and fixed it. It was because the html boxes created by LightWeightContainer for rendering a slave table as delayed value were created lazily after site startup. Now Kernel.kernel_startup() triggers their creation.
- 2 ans, 1 mois ago by Luc Saffre about #5739 (Oops, get_atomizer(...) returned None) : It has to do with the fact that the data element representing a slave panel in a detail layout is the actor class and not (as for "normal" fields) an instance of a Django field. And because atomizers are created lazily and stored in _lino_atomizer, and because a slave panel creates a return_type_for...
- 2 ans, 1 mois ago by Luc Saffre about #5739 (Oops, get_atomizer(...) returned None) : An old issue that doesn't disturb very much, but now I got a reproducible case of it while trying to reproduce #5715.
- 2 ans, 1 mois ago by Luc Saffre about #5739 (Oops, get_atomizer(...) returned None) : Created new Ticket #5739 (Oops, get_atomizer(tickets.AllTickets, comments.CommentsByRFC, comments.CommentsByRFC) returned None).