Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion libraries/src/Application/EventAware.php
Original file line number Diff line number Diff line change
Expand Up @@ -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
*
Expand Down
2 changes: 1 addition & 1 deletion libraries/src/Application/EventAwareInterface.php
Original file line number Diff line number Diff line change
Expand Up @@ -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
*
Expand Down
4 changes: 2 additions & 2 deletions libraries/src/Plugin/CMSPlugin.php
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
*
Expand Down
2 changes: 1 addition & 1 deletion plugins/multifactorauth/email/src/Extension/Email.php
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion plugins/multifactorauth/fixed/src/Extension/Fixed.php
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion plugins/multifactorauth/totp/src/Extension/Totp.php
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion plugins/multifactorauth/yubikey/src/Extension/Yubikey.php
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion plugins/system/webauthn/src/Extension/Webauthn.php
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down