Actions
Feature proposal #5711
closedDeprecate restricting fields from plugin tabs
Feature proposal #5711:
Deprecate restricting fields from plugin tabs
Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
12 January 2016
Due date:
% Done:
100%
Estimated time:
Description
Currently many plugin tabs do not allow fields. However, it probably doesn't make much sense to restrict this anymore and just always allow fields to be placed on plugin tabs. The question is where (above or below plugin content).
Updated by beat over 10 years ago
- Target version changed from CB 2.0.13 to CB 2.0.14
Updated by beat over 10 years ago
- Target version changed from CB 2.0.14 to CB 2.0.15
Updated by beat about 10 years ago
- Target version changed from CB 2.0.15 to CB 2.1
Updated by krileon almost 10 years ago
- Target version changed from CB 2.1 to CB 2.2
Updated by krileon over 8 years ago
- Target version changed from CB 2.2 to CB 2.8
Updated by beat over 3 years ago
- Target version changed from CB 2.8 to CB 2.8.1
Updated by beat about 3 years ago
- Target version changed from CB 2.8.1 to CB 2.8.2
Updated by beat almost 3 years ago
- Target version changed from CB 2.8.2 to CB 2.9.0
Updated by beat almost 3 years ago
- Target version changed from CB 2.9.0 to CB 2.9.2
Updated by beat over 2 years ago
- Target version changed from CB 2.9.2 to CB 2.9.3
Updated by beat about 2 years ago
- Target version changed from CB 2.9.3 to CB 2.10.0
Updated by beat over 1 year ago
- Target version changed from CB 2.10.0 to CB 2.11.0
Updated by krileon 3 months ago
- Status changed from Feedback to Rejected
- Target version deleted (
CB 2.12.0) - % Done changed from 0 to 100
Instead of having plugin tabs to begin with replace them entirely with fieldtypes instead. Tabs will also just be field groups in CB 3.0 and be containers for fields and nothing more.
Actions