Actions
Bug #7669
closedtab, field, and plugin class endpoints applying limits to names
Description
When calling the tabclass, fieldclass, or pluginclass endpoints the &tab, &field, and &plugin values are being cut short. This isn't necessary. If the tab/field/plugin doesn't exist it won't do anything. Limiting the length breaks the possibility of pseudo tabs, fields, and plugins from functioning with endpoints. For example fields inside of a fieldgroup will not work because their fieldname is longer than normally allowed storable and this is because it's 2 field names concatted together. Removing the length limit at the endpoint usage resolves this with no harm done.
Updated by krileon over 5 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Fixed in MR !1486
Actions