🇵🇱Poland @blazey

Added the method body.

blazey → created an issue.

Great! Thanks for confirming.

The error should be fixed in 1.0.3.

Thanks for the reports folks. Which version of Drupal core are you on?

Hi Folks!

I've added a few changes to the MR regarding the access checks. It might be ok to use ->accessCheck() in places where we show transactions in the UI, e.g. in the list builders. However, we can't rely on the currently logged in user having access to the transactions in places which are critical for the functionality of the module and there we should explicitly disable access checking with ->accessCheck(FALSE).

Transactions can be created in cron or via a drush command and in these scenarios there is no current_user, i.e. they run as anonymous. The anonymous user doesn't need to (and really shouldn't) have access to see the transactions, so the calls to critical methods like getLastExecutedTransaction can return wrong values.

blazey → made their first commit to this issue’s fork.

Hi Folks,

Thanks for your contributions, that's awesome to see the module going forward!

Unfortunately, I don't have time to maintain the module anymore. @Eli-T would you like to push it forward? I've added you as the maintainer.