Actions
Patch #39699
closedMore flexible CustomField usage for relations
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
The change in #38772 prevents usage, if a class is a subclass of CustomField, e.g UserCustomField. No filter group name is used, because of this change. "Translation missing: de.field_cf_19" is used instead of the name of the custom field.
This patch solve this problem.
def <=>(field)
- return nil unless field.is_a?(CustomField)
+ return nil unless field.is_a?(self.class)
position <=> field.position
end
Files
Updated by Alexander Meindl almost 1 year ago
The patch does not work, sorry. I suppose I have to search for the real solution for that.
This issue can be closed, I can create a new issue, if I've more information.
Actions