Hello,
Apologies for the delay.
1. To be clear, do internal transfers work only for users who were created by an admin, but not for users who signed up to your site on their own?
2. Also, have you checked the user capabilities?
Please let me know. Thank you.
with regards
Hi.
Internal transactions only work when performed by the administrator. If the internal transactions are made by any other user, they do not work (before they worked). The user capabilities are fine. I also get this message “The wp_cron tasks have not run in the past 4 hours.You must either enable auto-triggering or trigger cron manually via curl / system-cron.”
Thanks!
Thanks for the clarification.
If you get a message saying that the cron job has not run, then that is the problem.
Before, the plugin would consider that the cron jobs have run, if they had started. Now, they are considered to have run if they have finished. This means that probably the process crashes mid-way for some reason.
A couple of things you could check:
1. Run the cron job manually by clicking on the link provided in the admin screen. Do you get { result: "success" }? Do the transactions get processed then?
2. To diagnose if the jobs indeed crash mid-way, you could enable “Verbose log output” in the cron job settings. Then, the log output in wp-content/debug.log will show if execution is running out of memory, or after which task it fails. If you like, post here or email me the log output and I can look at it.
Hi. I get {result: “success”} but internal transactions are not completed. I have activated “Verbose log output” in the cron job settings but I can not find the file “wp-content / debug.log”.
I have seen this message in the registry of my server:
Sorry, this is the debug.log
[ log removed ]
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
@mc_deimon Posting log data here doesn’t work. Please use a service like https://pastebin.com/ instead and share the link to that paste.
After investigating, it turns out this issue caused internal transactions to not fail when there is not enough available balance. Instead, they remained in pending state. This bug was introduced in 4.0.0. I have provided a fix for this issue in version 4.0.5.
with regards
