As there is still no port of this module to Backdrop, I found the following article about using Rules Components instead very helpful:
https://drupal.stackexchange.com/questions/245049/whats-the-alternative-...
I can confirm that the patch is working.
On the other hand, I can also recommend to install
Ultimate Cron →
module, which provides an easy UI to schedule each module's cron run differently, e.g. linkchecker only once or several times in the night. No patch needed in that scenario.
Thanks for your feedback. The Backdrop port is available here: https://github.com/backdrop-contrib/filehash
(Note: not sure about that issue fork, I only wanted to post this comment)
Hello,
I'm also interested in this and I'm thinking about doing it. Did you already try to do the port?
Although this is old, I also needed this feature. As I still have a site on D7 (to be ported to Backdrop), I did a patch for this feature.
It adds a checkbox "Sync on click instead of hover" under Cross-highlighting field set in Views Display Format Settings.
The click event has much better usability than hover in case of a lot of markers/records.
I also added a smoother scrolling for the synced content.
If anyone is interested in this feature, I would appreciate any feedback.
The patch in #7 works well and solves the problem for me.
Sorry for forgetting to provide the patch file and for not noticing this for a long while...eventually, the patch is attached here.
This issue is still in the current dev version from 4 Feb 2021. Only the notice message is slightly different (line 441 instead of 431):
Notice: Trying to access array offset on value of type bool in calendar_plugin_row->render() (line 441 of /home/icpdrobs/danubis-icpdr-org/sites/all/modules/contrib/calendar/includes/calendar_plugin_row.inc).
So, the current code still accesses $items[$delta] which is false because the previous call to field_get_items did not get a result. This happens (at least in my case) when there are multiple date fields used in the contextual filter of the View, i.e. a calendar with more than one node type where the names of the date fields are different.
I used the fix in #5 and it gets away with the notice message and the View display works fine (at least in my case).
Just had the same issue when upgrading to PHP 8.1 and the patch solved the issue. Thanks!
Just migrated from PHP 7 to 8.1 and encountered the same warnings.
The patch in #3 applied well and resolved the warnings. Seems all works fine.
Thanks you very much!
Sorry to post in a closed issue. But I had the same issue and solved it, so I just want to share this with anybody who still would need it.
The error occurred in my setup when using also the Media Bulk Upload module → . I see that in that module entity_save is called three times, so I assume this is causing the multiple calls of hook_node_insert. Bulk Media Upload is unmaintained and I did not see how to fix the issue there.
But I saw two issues in the hook_node_insert implementation of this module:
- It accepts a node ID instead of a node object as parameter and then adds the auth key to the non-existing node object. I did not check if it is ever called with a nid instead of a node, but it is easy to fix that by loading the node in such case.
- It says to generate the key only if not set, but then inserts it also when it was already set. This creates the PDOException when the hook is called twice, so I think also the db_insert statement should be conditional.
Attached is a patch which addresses both issues and fixed the issue for me.
I encountered the same bug and fixed it. Please check out the patch.
Also just tried #231 on Drupal 7.38 and it solves a bug with dissappering rows I had with a View using a not required relationship. Hope this goes into core asap.