10
10
* on the store settings page.
11
11
*
12
12
* @method \Magento\Config\Block\System\Config\Form getForm()
13
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
13
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
14
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
15
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
16
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
17
+ * issues that will be addressed in future releases.
14
18
* @api
15
19
*/
16
20
class DisableOutput extends \Magento \Config \Block \System \Config \Form \Fieldset
17
21
{
18
22
/**
19
23
* @var \Magento\Framework\DataObject
20
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
24
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
25
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
26
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
27
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
28
+ * issues that will be addressed in future releases.
21
29
*/
22
30
protected $ _dummyElement ;
23
31
24
32
/**
25
33
* @var \Magento\Config\Block\System\Config\Form\Field
26
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
34
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
35
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
36
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
37
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
38
+ * issues that will be addressed in future releases.
27
39
*/
28
40
protected $ _fieldRenderer ;
29
41
30
42
/**
31
43
* @var array
32
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
44
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
45
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
46
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
47
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
48
+ * issues that will be addressed in future releases.
33
49
*/
34
50
protected $ _values ;
35
51
36
52
/**
37
53
* @var \Magento\Framework\Module\ModuleListInterface
38
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
54
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
55
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
56
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
57
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
58
+ * issues that will be addressed in future releases.
39
59
*/
40
60
protected $ _moduleList ;
41
61
@@ -59,7 +79,11 @@ public function __construct(
59
79
60
80
/**
61
81
* {@inheritdoc}
62
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
82
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
83
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
84
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
85
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
86
+ * issues that will be addressed in future releases.
63
87
*/
64
88
public function render (\Magento \Framework \Data \Form \Element \AbstractElement $ element )
65
89
{
@@ -88,7 +112,11 @@ public function render(\Magento\Framework\Data\Form\Element\AbstractElement $ele
88
112
}
89
113
90
114
/**
91
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
115
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
116
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
117
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
118
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
119
+ * issues that will be addressed in future releases.
92
120
* @return \Magento\Framework\DataObject
93
121
*/
94
122
protected function _getDummyElement ()
@@ -100,7 +128,11 @@ protected function _getDummyElement()
100
128
}
101
129
102
130
/**
103
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
131
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
132
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
133
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
134
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
135
+ * issues that will be addressed in future releases.
104
136
* @return \Magento\Config\Block\System\Config\Form\Field
105
137
*/
106
138
protected function _getFieldRenderer ()
@@ -114,7 +146,11 @@ protected function _getFieldRenderer()
114
146
}
115
147
116
148
/**
117
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
149
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
150
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
151
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
152
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
153
+ * issues that will be addressed in future releases.
118
154
* @return array
119
155
*/
120
156
protected function _getValues ()
@@ -131,7 +167,11 @@ protected function _getValues()
131
167
/**
132
168
* @param \Magento\Framework\Data\Form\Element\Fieldset $fieldset
133
169
* @param string $moduleName
134
- * @deprecated 100.2.0 Magento does not support custom disabling/enabling module output since 2.2.0 version
170
+ * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
171
+ * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
172
+ * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
173
+ * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
174
+ * issues that will be addressed in future releases.
135
175
* @return mixed
136
176
*/
137
177
protected function _getFieldHtml ($ fieldset , $ moduleName )
0 commit comments