Josh

Any chance you could point me in the right direction for enabling this for the block-based checkout? I’m a developer myself but I’m having trouble finding documentation for this particular question.

Thanks. I’m gonna give that a try this morning.

It’s being created by the host’s staging functionality. But I checked with their helpdesk first and they could not identify the issue.

You’re just giving me a canned response. The reason for the 500 error is that none of the Woo tables were created. That’s the problem I need to resolve: the creation of Woo’s tables in the database. Pretty certain the settings pages will work after that.

Actually, all the Woo admin pages return 500 (Internal Server Error)

I can’t access those menus because none of the Woo tables were created, and those menu pages return 501s (if I remember correctly).

Maybe I misunderstood what was happening with that image. I thought the plugin was using the “thumbnail” image size for those headers. But are you using a full-size image and then just adjusting via CSS?

Same problem.

Thanks. I guess I’ll mark the thread as resolved.

I guess I can always add the author term and ppma_authors_name post meta using core functions, but I thought the plugin might have its own function for creating a guest author and attaching him/her to a post.

Thanks. That looks like it requires the author to already exist, so that you can add by ID. What if this is a new author you need to create first?

Also, is their php method that doesn’t require using the REST API?

Those are pretty straightforward questions to be outside the scope of your support. But thanks anyway.

Hey Pepe,
Thanks for your detailed answer. I’m not really looking for help troubleshooting the problem right now. I’m just looking for answers to two specific questions:

1. Is there a specific endpoint the plugin uses to receive payment complete messages back from Braintree?
2. Does the Braintree gateway use the Soap PHP client?

Sorry if that wasn’t clear in my original post.

Thanks!

Thanks. We use the <pre> (“Verse block”) on tons of pages, so those url-based filters don’t work for us. I’ll just turn off HTML minifying for now, until a fix is released.