diff --git a/libraries/src/Application/EventAware.php b/libraries/src/Application/EventAware.php index 76ca8c95ae1b5..62016788be90c 100644 --- a/libraries/src/Application/EventAware.php +++ b/libraries/src/Application/EventAware.php @@ -72,7 +72,7 @@ public function registerEvent($event, callable $handler) * * This is a legacy method, implementing old-style (Joomla! 3.x) plugin calls. It's best to go directly through the * Dispatcher and handle the returned EventInterface object instead of going through this method. This method is - * deprecated and will be removed in Joomla! 5.x. + * deprecated and will be removed in Joomla! 7.0. * * This method will only return the 'result' argument of the event * diff --git a/libraries/src/Application/EventAwareInterface.php b/libraries/src/Application/EventAwareInterface.php index c5ae193027629..962a997315056 100644 --- a/libraries/src/Application/EventAwareInterface.php +++ b/libraries/src/Application/EventAwareInterface.php @@ -42,7 +42,7 @@ public function getDispatcher(); * * This is a legacy method, implementing old-style (Joomla! 3.x) plugin calls. It's best to go directly through the * Dispatcher and handle the returned EventInterface object instead of going through this method. This method is - * deprecated and will be removed in Joomla! 5.x. + * deprecated and will be removed in Joomla! 7.0. * * This method will only return the 'result' argument of the event * diff --git a/libraries/src/Plugin/CMSPlugin.php b/libraries/src/Plugin/CMSPlugin.php index 2668f1b82176b..d134dd886f0d7 100644 --- a/libraries/src/Plugin/CMSPlugin.php +++ b/libraries/src/Plugin/CMSPlugin.php @@ -95,7 +95,7 @@ abstract class CMSPlugin implements DispatcherAwareInterface, PluginInterface, L * Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While * this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are * advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole - * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners, + * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners, * removing support for legacy Listeners. * * @var boolean @@ -403,7 +403,7 @@ function (AbstractEvent $event) use ($methodName) { /** * Registers a proper event listener, i.e. a method which accepts an AbstractEvent as its sole argument. This is the - * preferred way to implement plugins in Joomla! 4.x and will be the only possible method with Joomla! 5.x onwards. + * preferred way to implement plugins in Joomla! 4.x and will be the only possible method with Joomla! 7.0 onwards. * * @param string $methodName The method name to register * diff --git a/plugins/multifactorauth/email/src/Extension/Email.php b/plugins/multifactorauth/email/src/Extension/Email.php index 049b3b30f1978..4b76126c941b9 100644 --- a/plugins/multifactorauth/email/src/Extension/Email.php +++ b/plugins/multifactorauth/email/src/Extension/Email.php @@ -71,7 +71,7 @@ class Email extends CMSPlugin implements SubscriberInterface * Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While * this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are * advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole - * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners, + * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners, * removing support for legacy Listeners. * * @var boolean diff --git a/plugins/multifactorauth/fixed/src/Extension/Fixed.php b/plugins/multifactorauth/fixed/src/Extension/Fixed.php index c7d0796dec6f1..1d43c452f097e 100644 --- a/plugins/multifactorauth/fixed/src/Extension/Fixed.php +++ b/plugins/multifactorauth/fixed/src/Extension/Fixed.php @@ -63,7 +63,7 @@ class Fixed extends CMSPlugin implements SubscriberInterface * Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While * this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are * advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole - * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners, + * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners, * removing support for legacy Listeners. * * @var boolean diff --git a/plugins/multifactorauth/totp/src/Extension/Totp.php b/plugins/multifactorauth/totp/src/Extension/Totp.php index 7d010b127075a..578eb08d9eae8 100644 --- a/plugins/multifactorauth/totp/src/Extension/Totp.php +++ b/plugins/multifactorauth/totp/src/Extension/Totp.php @@ -62,7 +62,7 @@ class Totp extends CMSPlugin implements SubscriberInterface * Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While * this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are * advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole - * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners, + * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners, * removing support for legacy Listeners. * * @var boolean diff --git a/plugins/multifactorauth/yubikey/src/Extension/Yubikey.php b/plugins/multifactorauth/yubikey/src/Extension/Yubikey.php index 5fa32e1635c9d..79e964423f2a2 100644 --- a/plugins/multifactorauth/yubikey/src/Extension/Yubikey.php +++ b/plugins/multifactorauth/yubikey/src/Extension/Yubikey.php @@ -61,7 +61,7 @@ class Yubikey extends CMSPlugin implements SubscriberInterface * Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While * this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are * advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole - * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners, + * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners, * removing support for legacy Listeners. * * @var boolean diff --git a/plugins/system/webauthn/src/Extension/Webauthn.php b/plugins/system/webauthn/src/Extension/Webauthn.php index a50b950cb84f9..6360145bc5ee0 100644 --- a/plugins/system/webauthn/src/Extension/Webauthn.php +++ b/plugins/system/webauthn/src/Extension/Webauthn.php @@ -69,7 +69,7 @@ final class Webauthn extends CMSPlugin implements SubscriberInterface * Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While * this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are * advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole - * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners, + * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners, * removing support for legacy Listeners. * * @var boolean