Jeff Daigle

Done, thanks!

Yes, they all have the post_type set to shop_order and I didn’t see anything out of the ordinary in the post meta either. I could send you the database rows for an affected order if you want to take a look?

I’m seeing the same thing. Installing the jQuery Migrate Helper plugin is the only thing that fixes it. Here’s the error that jQuery Migrate Helper shows on the New Export page—it does look like a bug in WP All Export:

jQuery Migrate Helper — Warnings encountered

This page generated the following warnings:
https://revolvethegame.com/wp-content/plugins/wp-all-export-pro/static/js/jquery/jquery.tipsy.js: jQuery.fn.live() is deprecated
https://revolvethegame.com/wp-content/plugins/wp-all-export-pro/static/js/jquery/jquery.tipsy.js: jQuery.fn.live() is deprecated
Please make sure you are using the latest version of all of your plugins, and your theme. If you are, you may want to ask the developers of the code mentioned in the warnings for an update.

I just came across this thread while Googling how TF to move blocks in WP 5.5. I agree that this on the surface seems like a highly irresponsible change especially in light of the fact that I didn’t see any onboarding messages giving me hints regarding how to use the updated interface. I can’t understand how this made it past any type of usability testing.

Thanks, I would like to continue to pursue this, how should I contact you with login info for the site?

It’s happening on /wp-admin/admin.php?page=wc-settings&tab=cc_woo&section. I enter data for all the fields, then click “Save changes”. This takes me to the “Import Existing Customers” tab. Regardless of whether I choose Yes or No I never get taken to Constant Contact and when I go back to the “Store Information” tab the Phone Number field is empty, but all the others show the info I entered previously.

I’m using Safari 12.1.2 without any content blockers.

@yehuda, I tried making the change to the file as you instructed but got this PHP error message when trying to send an email with the modified plugin activated:

Recoverable fatal error: Object of class SendGrid\Mail\Cc could not be converted to string in /home/tempsixe/public_html/wp-content/plugins/post-smtp/Postman/Postman-Mail/sendgrid/vendor/sendgrid/sendgrid/lib/mail/EmailAddress.php on line 77

So I tried changing the modification to use single quotes instead of double quotes, but all that did was result in a new error being logged:

{$emailAddress} must be valid and of type string.

The email being sent was a WooCommerce order notification, to my own email address jeff [at] dbdc [dot] us.

With nothing except this in the transcript:

https://api.sendgrid.com:443

@yehudah, your website doesn’t seem to be working properly, getting a lot of broken images and the support link on https://postmansmtp.com/contact/ (https://postmansmtp.com/forums/forum/extended-support/) returns a Page Not Found. Reverting to 1.9.8 has stopped the errors for now.

I started getting this error with 2.0.1 as well. It’s preventing delivery of WooCommerce transactional emails to customers and administrators, too.

@stephjacq thanks—for someone used to the old UI this wasn’t immediately obvious.

Could this behavior be controlled via a user-visible setting? I have clients who need to issue partial refunds frequently (i.e. 50% the cost of a line item) and it appears that this is not possible as of 3.6.

I found this thread through a Google search and just wanted to report that in my case, using the plain old “File” field type works. The “Advanced File Uploader” field did not, in fact, upload any files.

Thanks, I’ll send an email out.

Regarding the form I looked at the error console and a couple of javascript files that looked to be related to the form weren’t loading due to 403 errors. Hope that helps!

• This reply was modified 6 years, 6 months ago by Jeff Daigle. Reason: miss-typed "form" as "for"

That’s actually a Storefront theme setting, with a filter to change the text:

https://docs.woocommerce.com/document/change-the-primary-navigation-button-text/

Checked back with the client and found that they are still on PHP 5.4(!). Will update and try again.