peteratomic

P.S. There’s budget for this if custom investigation and solutions are required, we could likely hire your team to solve this.

Hope my last comment didn’t come across that I was blaming you @jonathanstegall. Think you’ve done something amazing with this plugin and I can appreciate if you can’t support what seems to be an outlier case with this one.

There may be some budget available if you or your team are able to look in to this “on the clock”.

And another problem… repeatedly trying to import a SF post (possibly deleted in WP from an earlier test). Never works. Other records update just fine, but can’t get this ‘orphaned’ one to show.

Can’t make sense out of any of this. Close to telling my client they’ll have to hire someone else to do this. Seems so incredibly buggy the whole process.

Think we’re going in circles a bit. I only used bulk edit to change all imported posts to publish. Mentioned it only to be thorough in describing the total experience.

The code snippet to set automatically to publish definitely works. But it doesn’t solve the problem, as the posts still won’t show up unless I manually click Update inside each one. Could live with it if we have to, but definitely isn’t as efficient.

So from everything you said, I thought I was supposed to write a custom function to make sure save_post fires after data is imported into WP.

FYI – once the post is manually saved using the Update button, then all data changes ARE getting instantly saved, so its just the first initial save that is needed.

Excellent, thanks for the clarification @jonathanstegall .

Thanks for the code snippet. Works! (Duh.)

So in order to get the save_post action, I’d need a special filter, right? Looking at this:

https://github.com/MinnPost/object-sync-for-salesforce/blob/master/docs/extending-before-and-after-saving.md#salesforce-pull

My first guess is to use the ‘after success’ one, since this needs to fire after data is pulled in, but this code comment (“do things if the save succeeded”) makes it sound like it is for AFTER save_post fires. Or is the “save succeeded” rather “pull succeeded”?

hey @jonathanstegall thanks for the quick response. Apologies for the murky post… realized part way thru that it was a bit more complicated to describe than I thought, but was rushed to get it posted.

thanks for confirming #1 and #2… that’s all I was hoping for.

The bulk edit feature I mentioned is when you’re in post list view and you can click the checkbox in the header to select all posts and then reset various properties, like from “draft” to “published”. If in #3 “this plugin” refers to ACF (rather than yours) then I would seem to have confirmed that this bulk edit feature doesn’t trigger save_post from what I’ve seen. (Since nothing showed up until I’d manually clicked “update’.) But sounds like that also won’t happen with your suggestion in #1/2? Will check the link above and see… ??

Oh dear. Found that the client had randomly used a different record type than all the rest.

Solved!

Thank you @3sonsdevelopment !

Curious though… was this something that changed with a new version of Woocommerce? The default we’ve had since launch was a product page link on the add to cart button, then it suddenly changed, but can’t say exactly when.

Also noticed something odd… whether using storefront or our regular theme, the link on the product image is correct:

https://fourvisionsmarket.com/product/handmade-one-of-a-kind-seed-bead-earrings-7/

But the Add to Cart button is:
https://fourvisionsmarket.com/product-category/feminine-tools/earrings-feminine-tools/?add-to-cart=987468929

Tried two or three times to do plugin + theme resets, but that had no effect.

Actually found that this is happening on ALL product links, not just shortcodes. Tried disabling plugins and using storefront, but neither helped. Tried permalink reset, no help.

Followed from the documentation here: https://docs.woocommerce.com/document/woocommerce-shortcodes/#section-9

Here’s an order page: https://monc.net/wye-valley-sessions/

FANTASTIC! That worked like a charm!

Thank you so much @mcampal !

Same for me. Can’t use as is.

Problem went away for us, so maybe was a plugin conflict after all.