[#6562] - Fix plugins trigger using cli scripts
- Closed
- 25 Jun 2016
- Medium
- Build: staging
- # 6562
- Diff
- fastslack:plugin-trigger
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
User tests: Successful: Unsuccessful:
If we try to trigger authentication plugins we receive the error.
Application Instantiation Error
The exactly issue is into 'cookies' plugin, enabled by default:
https://github.com/joomla/joomla-cms/blob/staging/plugins/authentication/cookie/cookie.php#L27
The example of the plugin trigger:
https://github.com/fastslack/matware-libraries/blob/master/api/application/web.php#L218
joomla-cms-bot
- | Labels |
Added:
?
|
||
zero-24
- | Category | ⇒ | CLI |
@fastslack I am closing this as there seems to be an existing way of dealing with this issue. I have done the same as Paladin by stuffing the cli into the application. If this is not the case feel free to re-open this if you want to work further on it. Thank you.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6562.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-06-25 10:56:03 |
| Closed_By | ⇒ | roland-d |
FWIW assigning your CLI application to JFactory::$application is indeed the correct behavior. During the web application bootup, this is automatically done because the calls to JFactory::getApplication() can resolve the web applications without issue but because there is no service location or standardized structure for CLI applications that method can't be made smart enough to account for basically any application class not named JApplication<$name>.
Maybe related with #6553