? ? Pending

User tests: Successful: Unsuccessful:

avatar roland-d
roland-d
18 May 2019

Summary of Changes

This removes the outdated and obsolete trigger. The correct trigger happens the line above.

Testing Instructions

  1. Go to Systems
  2. Go to Plugins
  3. Open plugin Action Log - Joomla
  4. Click on Save
  5. Notice you get the following error:

image

6. Apply the patch 7. Reload the page 8. Click on `Save` 9. Plugin is now saved

Expected result

Plugin is saved

Actual result

Class 'JEventDispatcher' not found error

Documentation Changes Required

None

avatar roland-d roland-d - open - 18 May 2019
avatar roland-d roland-d - change - 18 May 2019
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 18 May 2019
Category Libraries
avatar richard67
richard67 - comment - 18 May 2019

I have tested this item successfully on f2d08b1

Note: The testing instructions only tell 1 example when that error happens. It happens also with other actions like e.g. enable/disable plugin with button in list view. This PR fixes all of them.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24941.

avatar richard67 richard67 - test_item - 18 May 2019 - Tested successfully
avatar richard67
richard67 - comment - 18 May 2019

@roland-d I think @alikon is right: Instead of removing lines 1323 and 1324, you should replace those 2 lines by the one line
Factory::getApplication()->triggerEvent('onAfterCheckin', array($this->_tbl));
like he suggests.

avatar richard67
richard67 - comment - 18 May 2019

I have not tested this item.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24941.

avatar richard67 richard67 - test_item - 18 May 2019 - Not tested
avatar roland-d roland-d - change - 18 May 2019
Labels Added: ?
avatar roland-d
roland-d - comment - 18 May 2019

@alikon There is definitely a confusion with 2 triggers with basically the same name. What is the difference between them? One is J4 and the other is for J3?

@richard67 I have added the trigger as suggested

avatar richard67
richard67 - comment - 18 May 2019

Would be confusing me if the was no confusion in J4 ;-) (joke)

avatar richard67
richard67 - comment - 18 May 2019

I have tested this item successfully on 485f985

Note: The testing instructions only tell 1 example when that error happens. It happens also with other actions like e.g. enable/disable any plugin with the button in the plugins list view. This PR fixes all of them.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24941.

avatar richard67 richard67 - test_item - 18 May 2019 - Tested successfully
avatar alikon
alikon - comment - 18 May 2019
avatar alikon
alikon - comment - 18 May 2019

I have tested this item successfully on 485f985


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24941.

avatar alikon alikon - test_item - 18 May 2019 - Tested successfully
avatar alikon alikon - change - 18 May 2019
Status Pending Ready to Commit
avatar alikon
alikon - comment - 18 May 2019

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24941.

avatar infograf768 infograf768 - change - 19 May 2019
Labels Added: ?
avatar infograf768
infograf768 - comment - 19 May 2019

FYI, there are other places where the error happens: for example when playing with custom admin menus. PR also solves issue there.

avatar infograf768 infograf768 - change - 19 May 2019
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2019-05-19 06:30:03
Closed_By infograf768
avatar infograf768 infograf768 - close - 19 May 2019
avatar infograf768 infograf768 - merge - 19 May 2019
avatar infograf768
infograf768 - comment - 19 May 2019

Thanks.

avatar roland-d
roland-d - comment - 19 May 2019

Thank you

Add a Comment

Login with GitHub to post a comment