7 | | As I recollect, the_widget(), when it was introduced, was designed in such a way that it wouldn't cause a fatal error when a call is left lying around in a theme or in php content while the plugin that introduced the widget is disabled. The widget factory, in contrast, should only ever get called when a theme or plugin introduces a new widget. |
| 7 | As I recollect, the_widget(), when it was introduced, was designed in such a way that it wouldn't cause a fatal error when a call is left lying around in a theme or in php content while the plugin that introduced the widget is disabled -- which is an end-user error, rather than a developer error. The widget factory, in contrast, should only ever get called when a theme or plugin introduces a new widget. |