WP to SF update record not pushed

Ok Jonathan, I understand ??
It is not very urgent, but your plugin is very useful for us and seems to be the best one for what we need, so let us know about the solving!

Thanks !

I’m also having these same issues in version 2.1.1. I can pull from Salesforce just fine, but pushing doesn’t work. When I turn on debug mode, I get the following messages:

“Debug: mapping object transient ID a0E5a00001gsMctEAE is currently pulling, so we do not push it.” Which the others have also reported.

I noticed as well that I almost always have at least 5 items in my pull queue, no matter what. Not sure if that is relevant, but I thought I’d bring it up.

I also get “Debug Salesforce API call: read the full log entry for request and response details. There is not an SOQL query included in this request.”

And lastly, in my error log file I got the following Fatal error once: “PHP Fatal error: Uncaught RuntimeException: Unable to claim actions. Database error. in /home/<sitename>/public_html/wp-content/plugins/object-sync-for-salesforce/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:683”

Not sure if any of this information helps with the issue, but I thought I’d include it.

Hi,
Thanks for your report knightwebaholics
I have the same errors : “5 items in my pull queue” and “Debug Salesforce API call: read the full log entry for request and response details. There is not an SOQL query included in this request.”

I don’t know where to find the error with Woocommerce, maybe I have too

@jonathan : did you have time to investigate in order to fix this issues?

Thanks !

To give an update on this, I’ve released a version 2.1.2 that I believe fixes many, and possibly all, of the reported issues with 2.1.1. I’m not going to close this (or the others) yet, to give folks some time to verify whether the issues are still happening.

Hi Jonathan,

Thanks, it works on my side ! 

I have an other issue, that is still here since some updates.
When I duplicate a wordpress custom post, and I modify the new one (the description field actualy), this is the "old" text which is pushed to SF.. Even if I update the text on WordPress side, this is the description of the "original" post which still stay in SF...

I have tried everything (empty cache, etc..) nothing to solve this ! 
And curiously, other text field work fine..

>> Do you know what could cause this error?

Thanks Jonathan !
Vincent

That seems like a separate issue to me. But here are the questions I would initially ask:

1. I’m assuming that you use a third party plugin to duplicate posts. If so, what plugin is it?
2. If you duplicate a core post (that is, not a custom post type) does it work, or does it have the same issue?

I ask both of those questions because my assumption is that it’s related to how the third party plugin works when it duplicates posts, but certainly I don’t know that for sure.

If that’s correct, I don’t prioritize supporting third party plugins. That just isn’t something this plugin has the capacity to do. But if there are ways I can support them without causing problems for other users who don’t use those plugins, I’m not opposed to it.

Hi Jonathan,

We have updated to version 2.1.2 and everything seems to be working well now.

Thank you very much for this!

I’m going to go ahead and close these 2.1.1-specific issues with the assumption that 2.1.2 is working well for everyone else as well.