WordPress Update User Action keeps adding {{pc_skip_field}} to empty fields

Marlon M

Member
Your Workflow URL
https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjcwNTZkMDYzNDA0MzE1MjZiNTUzNTUxMzAi_pc
Consent to Access & Modify
I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
WordPress Update User ction keeps adding {{pc_skip_field}} to empty fields, how do I stop this?

I only want to update fields I add data to but Pabbly Connect seems to be sending data to everfield in the wordpress user profile and litterally puts the {{pc_skip_field}} insyead of leaving fields blank.
 

Preeti Paryani

Well-known member
Staff member
Hi @Marlon M,

Thank you for bringing this to our attention.

The issue has now been resolved. When performing the WordPress – Update User action, empty fields will no longer be populated with {{pc_skip_field}}. Instead, they will be left unchanged, and only the fields where you provide values will be updated.

Please try running the action again and let us know if you notice anything unexpected.
 

Marlon M

Member
Hi, I just tested the update feature again, and unfortunately, it still has the same problem.

Please see the workflow in my account.
For now, I am going to use an alternative solution to the update, as I cannot put my project on hold much longer.
I would still like this to be fixed, though, as I shouldn't have to go elsewhere just to update a user.

Thanks, again
 

Marlon M

Member
Hi, thanks for the follow-up. I can now confirm that NEW wordpress steps work; however, the existing ones do not work, so I will have to replace all of them (not fun).

Just so I can have some confidence going forward, can you please tell me in basic terms:

1. What caused the problem in the first place
2. Is there anything I can do to prevent it from happening in future

Since I use WordPress heavily, I don't want to have this happen again, as it creates a mess and costs a lot of time and energy to resolve. Thats why I am currently still going to use another platform that seems to be more reliable for these types of WordPress automations.

I will continue to test this on non-critical automations until I can be confident that I won't have to deal with this issue.
 

Preeti Paryani

Well-known member
Staff member
Hi @Marlon M,

Thanks for the update. The issue was due to a backend action configuration problem on our end, and it has now been fixed.

Your existing WordPress Update User steps should work fine now as well. Could you please run them once again and confirm? If it still persists, share the step details you are updating and we’ll check further.
 

Marlon M

Member
Hi @Marlon M,

Thanks for the update. The issue was due to a backend action configuration problem on our end, and it has now been fixed.

Your existing WordPress Update User steps should work fine now as well. Could you please run them once again and confirm? If it still persists, share the step details you are updating and we’ll check further.
Ok it does now. But only after I made a change to it. I will have to see if that is the case with other steps as well, but I don't have the time now.
Let's leave it for now. Thanks for working on it
 
Top