Fix for 'ManyToOneRel' object has no attribute 'verbose_name' on Document/Images Usage page #11808
+9
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Users cannot view the usage details of documents or images (where they’re being used) used at least once in any multiple Parentalkey levels models from the Wagtail admin site. This seems to be a problem in referencing the
verbose_name
of the correct child field due to the nested structure of multi-level ManyToOneRel fields.More information including steps to reproduce the issue on a fresh Wagtail project can be found on #11482.
This fix should also fix an initial issue where the first field level's
verbose_name
is excluded from the returned string.For example, for a field reference of ResourceItem → Document within a ResourceGroup object:
Current result: Document
This fix's result: Resource item → Document