Listings use the base permitted manager to select their content (https://github.com/praekelt/jmbo-foundry/blob/master/foundry/models.py#L256). So if a subclass of ModelBase uses a custom permitted manager, listings will ignore this and use the base manager. This feature changes it so that it uses the leaf class' manager if the base manager has been overridden. There might be an altogether different solution to the problem. This is just a first try.
Listings use the base permitted manager to select their content (https://github.com/praekelt/jmbo-foundry/blob/master/foundry/models.py#L256). So if a subclass of ModelBase uses a custom permitted manager, listings will ignore this and use the base manager. This feature changes it so that it uses the leaf class' manager if the base manager has been overridden. There might be an altogether different solution to the problem. This is just a first try.