ethan700
Forum Replies Created
-
I turned the total cache plugin off before starting to test. It is still off. It did not fix the issue.
I have setInterval at 1250 now and it does seem to be working. However, it makes the fields load in slower, so I’m not sure it’s the best solution. I’m still waiting to see if people report issues with the fields, or if this is a definite fix.
2000 seems to make the fields load in too slow on fast internet. Trying 1000 now.
I am trying the setInterval to 2000 again in the javascript. I will keep testing this and see if I stop getting reports that the fields are unclickable.
By the way, I am the one that found and did troubleshooting with the “stuck on hold” issue that got incorporated into the latest update. I can work with you to troubleshoot and fix this issue as well.
Forum: Themes and Templates
In reply to: [Storefront] Revert to previous versionThanks for the quick response James.
Forum: Themes and Templates
In reply to: [Storefront] Removal of logo option?Thanks for the quick response James.
Forum: Plugins
In reply to: [WooCommerce] Orders stuck on holdIt worked! Thank you!
Forum: Plugins
In reply to: [WooCommerce] Orders stuck on holdWhich file and line number?
Forum: Plugins
In reply to: [WooCommerce] Orders stuck on holdHey that’s great – but any chance you can help me with a line of code to make the submitted_for_settlement status go to processing until then?
Forum: Plugins
In reply to: [WooCommerce] Orders stuck on holdI’m not sure what the exact status is, it might need to be: submitted_for_settlement
Forum: Plugins
In reply to: [WooCommerce] Orders stuck on holdAkeda, I just spoke to Braintree again. They said it’s possible that some credit card banks go straight to “settling” but that others will go to “submitted for settlement.” They also said that my account was operating normally and that there were no holds on it.
Can you send me the correct code and file/line location to change the code to have this line:
if ( 'settling' === $result->transaction->status ) {
change to either ‘settling’ OR ‘submitted for settlement’ ?
I would recommend that be a permanent update to the code for the next plugin update.
Forum: Plugins
In reply to: [WooCommerce] Orders stuck on holdAkeda, then it looks like my problem is that Braintree is taking hours to get to the “settled” state instead of instantly like you have.
In my logs, I see the first two lines you’re showing, but not the last two.
I did try purchases with all plugins off with no change.
When I call Braintree support, they say it’s “normal” for transactions to take hours to be settled, but you obviously don’t have that issue.
What can I do?
Forum: Plugins
In reply to: [WooCommerce] Orders stuck on holdI’ve been on the phone with Braintree support a few times. They said that once it is “submitted for settlement” the payment is guaranteed and the order should update to “processing.” It is also normal for it to remain in the “submitted for settlement” state for up to 24 hours. Obviously, waiting that long for a status change on Braintree’s end is not ideal, so it seems like the code should be:
if ( 'submitted for settlement' === $result->transaction->status ) {
Forum: Plugins
In reply to: [WooCommerce] Orders stuck on holdYes, in Braintree, the status goes to “submitted for settlement.” After a number of hours, it changes to “settling” and then to “settled.” During each of these, the WooComm order status never updates.
Forum: Plugins
In reply to: [WooCommerce] Orders stuck on holdI re-saved. I also unchecked “Capture charge immediately” and saved. Then checked it again and saved. Charges are being captured immediately, but the order status is not updating properly.
Screenshot: https://www.thedaddynamic.com/wp-content/uploads/2016/05/braintree.png