#4916 (BadRequest in cms1)
by Luc Saffre · in Developers · assigned to Luc Saffre
Summary
When opening the detail view of the index page, it says django.core.exceptions.BadRequest: Request on slave table pages.PagesByParent has no master instance
Children
Comments
- 3 years, 7 months ago by Luc Saffre about #4916 (BadRequest in cms1) : The problem occurs also under ExtJS.
- 3 years, 7 months ago by Luc Saffre about #4916 (BadRequest in cms1) : Sharif fixed this by having the client specify mt and mk when asking for delayed values.
- 3 years, 7 months ago by Luc Saffre about #4916 (BadRequest in cms1) : @8lurry i need your help... Please ping me when you are available for a jitsi session.
- 3 years, 7 months ago by Luc Saffre about #4916 (BadRequest in cms1) : DelayedValue view instantiates the action request without specifying a master_instance. It seems that this was never a problem because somehow Lino then determines the master instance before actually executing the datatabse query. So I now moved the BadRequest complain from BaseRequest.__init__() to...
- 3 years, 7 months ago by Luc Saffre about #4916 (BadRequest in cms1) : Created new Ticket #4916 (BadRequest in cms1).