Iacopo Spalletti
Iacopo Spalletti
The raw query approach taken in `alphabet()` function drops all the filters in the passed queryset. Why was it necessary to have raw queries for newer Django version?
This allows editing an application hooked to a page behind the curtains, otherwise editor can't interact with application data unless page is published. @digi604 any comment on this?
When using unique together on translated fields, error message is duplicated, apparently because both form (https://github.com/django-parler/django-parler/blob/master/parler/forms.py#L169) and model (https://github.com/django-parler/django-parler/blob/master/parler/models.py#L654) run the same `translation.validate_unique()` check This might also be a flaw...
It would be great to have a way an easy way to define file types other than Image; this way it could be possible to associate different file icons according...
To make filer consistent with django CMS it should be ported to treebeard to avoid duplicating dependencies when used with django CMS A 3.0 compatility branch should be maintained
Refactor project settings to allow easier overriding in tests and improve documentability Use the same approach as https://github.com/nephila/djangocms-blog/pull/623/files#diff-386361aab5a80162bffb1c2710b7d9b4
Add schema.org by adding a separate set of data to handle it As the schema.org standard keeps adding more type and properties, trying to map them would be pretty pointless:...
`meta.html` is quite burdensome to support, as any change to will require people who extended it to adapt. We will likely need a more robust solution that will allow people...
We have all the machinery we need for a better schema.org support, and to allow generating metadata in **json+ld** format We should definitely make easier and more straightforward to output...