delsey

Same problem fatal error in the back end editing a Woo Product (that uses Posts2posts) – fixed it locally by changing the sprintf specifier. An official plug in update would be appreciated – thx.

I have the same problem – the audience tab is missing. I noticed this is marked as resolved, but not sure what the fix was?

Thanks for the speedy response – works like a charm. I will make a donation to one of your recommended causes (your do not donate page is heartwarming)!

Thanks for the response. I am just looking at this again with the latest version of everything, but the same issues as detailed above still exist.

For layouts we use either VC or just the native editor (for simple blog posts etc)

For us to move off VC, Guttenburg would have to automatically migrate all of my VC pages into Guttenburg – with no styling or CSS issues and working across all devices sizes. I know that we have tweaked layout and CSS specific to VC, so its hard to imagine this happening!

Then someone from www.ads-software.com would come and re-train our employees for us. Or you would compensate us for the time we need to spend learning not just a new editor, but a whole new UI experience.

And all plugins, metaboxes etc would be fully tested and working.

“When you first loaded it, seems you wanted some form of guide or more visual guidance. Is that right? What would have helped you there?” No – I just want it to work with my existing site without me having to do a bunch of work! Basically whilst I am not against change, our organization does not want or need a new WordPress editing/UI experince (self serving maybe, but also true!)

” Overtime WooCommerce will become more and more merged into Gutenberg as far as experience goes.’

Thank makes me even more afraid, as it could remove the option for me to just disable Guttenberg and run our business. In the processes of re-testing Guttenberg I upgraded to the latest version of Woo and I can already see a couple of issues just related to the Woo upgrade. I am sure I can fix them, but the amount of regression testing required once 5.0 hits just to keep my site the way it is could be huge.

As I said we are a use technology to support our business, but technology is not our business. I simply have no business case to justify going through the pain of this kind of change, and I fear at some point this change will make WordPress/Woocommerce unusable for our company.

I have the same problem – dropbox pro 2.13.2.21 just installed on a new site.

Success: you have authenticated your Dropbox account (though part of the returned information was not as expected – your mileage may vary.)
Dropbox error: Error in call to API function “users/get_current_account”: Must provide HTTP header “Authorization” or URL parameter “authorization”. (400)

and if I try to de-authenticate:
Dropbox/Curl error: Error in call to API function “auth/token/revoke”: Must provide HTTP header “Authorization” or URL parameter “authorization”. (Dropbox_BadRequestException) (line: 216, file: /home/saltspri/domains/tctcpreprod.saltspringonlineservices.com/public_html/wp-content/plugins/updraftplus/includes/Dropbox2/OAuth/Consumer/Curl.php)

scratch my previous comment – that DOESN’t work!

You need to change the plugging settings to autosort OFF. Because the default sort in Woo will sort by menu_order, the plugin will still pick that up and re-sort. Works for me – both the custom sorting by product category and the built in sorts selected on the page work. Yay!

I just had this problem. In your blog general settings make sure that WordPress Address and Site address are of the form:

https://mywebserver/mysite/wordpress

NOT

https://localhost/mysite/wordpress

localhost will be resolved to the LOCAL machine which will only work on the machine running the webserver.

I just had this problem. In your blog general settings make sure that WordPress Address and Site address are of the form:

https://mywebserver/mysite/wordpress

NOT

https://localhost/mysite/wordpress

localhost will be resolved to the LOCAL machine which will only work on the machine running the webserver.