Greg Sullivan

@alexterrenas No problem! If you’re able to post more about your situation in the Github issue, that might help isolate what’s causing the problem for us. (That said, my hope is that they’ll also fall back to the current user’s ID if the ID isn’t set by an argument.)

It sounds like you were facing a similar issue to one I encountered on a client site:

https://github.com/ultimatemember/ultimatemember/issues/568

However, I was having the same issue in 2.0.46. Can you confirm that’s the version you rolled back to? At the time of your post, 2.0.46 was the most recent version.

Be careful about rolling back, as the changes were in response to this:

https://blog.sucuri.net/2019/05/multiple-vulnerabilities-in-the-wordpress-ultimate-member-plugin.html

Awesome, thanks very much!

Great, much appreciated!

We’ve made this change in production, and WP to Buffer is now working on cron job imports from WP All Import.

(For clarity: It’s not just that the logs are empty; WP to Buffer isn’t triggered at all, so nothing is sent to the Buffer API.)