I'd like to invoke a specified feed importer after a node of a particular content type is deleted (this is all within the same site).
I started with Rules and found that the so called 'after' events don't actually occur after the operation has been written to database. Discussing in this issue in the rules issue queue the idea was floated of using hook_post_action.
I did have a look but couldn't work out how to integrate this to rules. I looked for examples but didn't find anything comparable that I could use as a template.
I actually found an acceptable and reliable workaround to doing this for creation and updating. However, I haven't found a workaround for invoking the feed importer after a node has been deleted.
hook_post_action has hooks so you can write your own functions that invoke the functions in that module. So, in theory I should be able to do something like:
function mymodule_node_postdelete($node) { feeds_import('myfeedimporter',0); }
However, I'm not sure what command to use to invoke the feed. I've hunted through the feeds module and it looks like feeds_action_import_feed
may be the function that is invoked by Rules, but I'm not sure that it works or that I've specified it properly:
$params_array = array( "importer" => "myfeedimporter", "feed_nid" => "0" ); feeds_action_import_feed('myfeedimporter',0, $params_array);
While I think, if it works, a simple invocation of the feed importer would suffice for my needs, there would be much greater value to the wider Backdrop community if we could use these post action hooks as events in Rules (I note the D8/9 module 'Business Rules' has an issue for adding this in).
I would appreciate some pointers as to how I can invoke the feeds importer, either in my custom implementation of hook_node_postdelete, or in Rules.
Recent comments
Thanks! The site was on PHP 7.0. With assistance from my hosting provider, I updated to PHP 7.4 and now I have access to the site again. No database re-import required.
Locked out of site after updating modules
Thank you very much. I will follow your advice.
Locked out of site after updating modules
The best you can do is test and report. If you find a contrib that doesn't work in php 8.3, create an issue in its queue so it gets fixed. In my experience, I've found that 7.4 is safest...
Locked out of site after updating modules
Hi argiepiano, Some contrib will not work in php 7.2 or lower, and some will not on PHP 8.1 or higher. Is there a way to find out which is the optimal PHP version for a...
Locked out of site after updating modules
This sounds like a combination of a buggy module and the "wrong" version of PHP. The fact that you are being redirected to the maintenance page may be an indication that your site was put on...
Locked out of site after updating modules