[6.0] Event Deprecation code comments (#47337)

brianteeman · web-flow · commit a547e10a5c2b · 2026-03-09T18:52:11.000Z
* [6.0] Event Deprecation code comments
* 7.0
diff --git 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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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

Original file line number	Diff line number	Diff line change
`@@ -72,7 +72,7 @@ public function registerEvent($event, callable $handler)`
`72`	`72`	`*`
`73`	`73`	`* This is a legacy method, implementing old-style (Joomla! 3.x) plugin calls. It's best to go directly through the`
`74`	`74`	`* Dispatcher and handle the returned EventInterface object instead of going through this method. This method is`
`75`		`- * deprecated and will be removed in Joomla! 5.x.`
	`75`	`+ * deprecated and will be removed in Joomla! 7.0.`
`76`	`76`	`*`
`77`	`77`	`* This method will only return the 'result' argument of the event`
`78`	`78`	`*`
Original file line number	Diff line number	Diff line change
`@@ -42,7 +42,7 @@ public function getDispatcher();`
`42`	`42`	`*`
`43`	`43`	`* This is a legacy method, implementing old-style (Joomla! 3.x) plugin calls. It's best to go directly through the`
`44`	`44`	`* Dispatcher and handle the returned EventInterface object instead of going through this method. This method is`
`45`		`- * deprecated and will be removed in Joomla! 5.x.`
	`45`	`+ * deprecated and will be removed in Joomla! 7.0.`
`46`	`46`	`*`
`47`	`47`	`* This method will only return the 'result' argument of the event`
`48`	`48`	`*`
Original file line number	Diff line number	Diff line change
`@@ -95,7 +95,7 @@ abstract class CMSPlugin implements DispatcherAwareInterface, PluginInterface, L`
`95`	`95`	`* Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While`
`96`	`96`	`* this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are`
`97`	`97`	`* advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole`
`98`		`- * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners,`
	`98`	`+ * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners,`
`99`	`99`	`* removing support for legacy Listeners.`
`100`	`100`	`*`
`101`	`101`	`* @var boolean`
`@@ -403,7 +403,7 @@ function (AbstractEvent $event) use ($methodName) {`
`403`	`403`
`404`	`404`	`/**`
`405`	`405`	`* Registers a proper event listener, i.e. a method which accepts an AbstractEvent as its sole argument. This is the`
`406`		`- * preferred way to implement plugins in Joomla! 4.x and will be the only possible method with Joomla! 5.x onwards.`
	`406`	`+ * preferred way to implement plugins in Joomla! 4.x and will be the only possible method with Joomla! 7.0 onwards.`
`407`	`407`	`*`
`408`	`408`	`* @param string $methodName The method name to register`
`409`	`409`	`*`
Original file line number	Diff line number	Diff line change
`@@ -71,7 +71,7 @@ class Email extends CMSPlugin implements SubscriberInterface`
`71`	`71`	`* Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While`
`72`	`72`	`* this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are`
`73`	`73`	`* advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole`
`74`		`- * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners,`
	`74`	`+ * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners,`
`75`	`75`	`* removing support for legacy Listeners.`
`76`	`76`	`*`
`77`	`77`	`* @var boolean`
Original file line number	Diff line number	Diff line change
`@@ -63,7 +63,7 @@ class Fixed extends CMSPlugin implements SubscriberInterface`
`63`	`63`	`* Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While`
`64`	`64`	`* this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are`
`65`	`65`	`* advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole`
`66`		`- * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners,`
	`66`	`+ * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners,`
`67`	`67`	`* removing support for legacy Listeners.`
`68`	`68`	`*`
`69`	`69`	`* @var boolean`
Original file line number	Diff line number	Diff line change
`@@ -62,7 +62,7 @@ class Totp extends CMSPlugin implements SubscriberInterface`
`62`	`62`	`* Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While`
`63`	`63`	`* this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are`
`64`	`64`	`* advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole`
`65`		`- * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners,`
	`65`	`+ * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners,`
`66`	`66`	`* removing support for legacy Listeners.`
`67`	`67`	`*`
`68`	`68`	`* @var boolean`
Original file line number	Diff line number	Diff line change
`@@ -61,7 +61,7 @@ class Yubikey extends CMSPlugin implements SubscriberInterface`
`61`	`61`	`* Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While`
`62`	`62`	`* this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are`
`63`	`63`	`* advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole`
`64`		`- * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners,`
	`64`	`+ * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners,`
`65`	`65`	`* removing support for legacy Listeners.`
`66`	`66`	`*`
`67`	`67`	`* @var boolean`
Original file line number	Diff line number	Diff line change
`@@ -69,7 +69,7 @@ final class Webauthn extends CMSPlugin implements SubscriberInterface`
`69`	`69`	`* Should I try to detect and register legacy event listeners, i.e. methods which accept unwrapped arguments? While`
`70`	`70`	`* this maintains a great degree of backwards compatibility to Joomla! 3.x-style plugins it is much slower. You are`
`71`	`71`	`* advised to implement your plugins using proper Listeners, methods accepting an AbstractEvent as their sole`
`72`		`- * parameter, for best performance. Also bear in mind that Joomla! 5.x onwards will only allow proper listeners,`
	`72`	`+ * parameter, for best performance. Also bear in mind that Joomla! 7.0 onwards will only allow proper listeners,`
`73`	`73`	`* removing support for legacy Listeners.`
`74`	`74`	`*`
`75`	`75`	`* @var boolean`