Closed (fixed)
Project:
Feeds
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Sep 2019 at 07:14 UTC
Updated:
27 Oct 2019 at 18:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
spadxiii commentedComment #3
megachriz@SpadXIII
What kind of issues are caused when using the base ID instead of actual ID?
This sounds like this needs an update function, as it would affect existing configurations. Existing feed type configurations would need to be updated to use the new action ID.
Comment #4
megachrizIt seems like the test failed because of a testbot issue, not because there's something wrong with the patch.
Comment #5
spadxiii commentedThe base id and actual id are different:'entity:unpublish_action' vs 'entity:unpublish_action:node'
By using the base id, there are errors thrown because it can't find the plugin with that id.
And yes, it would need an upgrade for existing feeds (no idea if or how they would work though.. because of the errors)
Comment #6
megachrizHas perhaps someting changed in Drupal Core in this regard? I'm using the feature to unpublish content when the source no longer provides it, but for me the action is called 'node_unpublish_action'. That's also what the test
\Drupal\Tests\feeds\Functional::UpdateNonExistentTestuses.Comment #7
megachrizClosed #3080143: Drupal\Component\Plugin\Exception\PluginNotFoundException: The "entity:unpublish_action" plugin does not exist as a duplicate.
Perhaps we do not need an update function as the current one isn't working anyway. I was confused that I had been using the unpublish action with success, but that probably is because I use the older unpublish action called 'node_unpublish_action'.
Comment #8
spadxiii commentedThat action still works, but is deprecated. So if there should be an upgrade, it should upgrade that to the new method. This might be out of scope for this issue though, because there are several other deprecations to be fixed as well.
ps. I didn't find that closed issue, otherwise I would've added a patch there. :)
Comment #9
megachriz@SpadXIII
That other issue is newer (created yesterday) ;)
Comment #10
megachrizLet's see what happens if we update the tests to use the recommended node unpublish action.
Comment #12
megachrizCool, tests are passing with the updated action ID. Committed #10.