Reviewed & tested by the community
Project:
Akismet
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
13 Oct 2015 at 13:16 UTC
Updated:
15 Jun 2020 at 17:10 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
drummAttached is a patch to fix this.
Comment #4
drumm#2254871: Default action behaviors in getAccessMask() could be the root cause here.
Comment #5
drumm#2254871: Default action behaviors in getAccessMask() is definitely the root cause.
Comment #6
drummI realized this is only updating the
{node}.statuscolumn, but not the{node_revision}.statuscolumn.node_load()gets the object's status from{node_revision}.status, so the nodes were unpublished in listings, but not unpublished on the individual node pages. We didn't notice this until now because we usually delete the nodes shortly after.Comment #7
drummThe attached patch uses the action API's
'behavior' => array('changes_property')to do the node save when the action is done.Comment #8
drummComment #13
drummI confirmed this works using /admin/content's core bulk operation, and double checked the Views Bulk Operations UI works as well.
This updates the test to do the node save, as actions-calling code is expected to do.
Comment #14
drummComment #15
drummComment #16
b_manUpdating this patch for Akismet.
Comment #17
drummComment #18
b_manBacked this patch out as it seem to break functionality on d.o.
Comment #19
drummYes, seems this is no longer needed.
Comment #20
drummTurns out we do need this #3069572: "Report node to Akismet as spam and unpublish" does not unpublish
Comment #21
drummComment #22
drummFresh port of #13 to the new project.
Comment #23
gisleJust unpublished a spam node using the "Report node to Akismet as spam and unpublish" menu item. It did unpublish the node with no extra step required.
Comment #24
avpaderno