Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating a GravityForm from JSON doesn't update its GravityFlow feed #22

Open
dcoder2099 opened this issue Jan 11, 2024 · 1 comment
Open

Comments

@dcoder2099
Copy link

We use GravityForms along with GravityFlow to allow our website to interact with several third-party systems.

We are experimenting with PowerBoost's Local JSON and Replace Forms feature to sync configuration between our dev/stage/production environments.

Inspecting the JSON from one of our forms that was saved using the Local JSON feature, there is a top-level "feeds" property where the GravityFlow workflow configuration is serialized (see attached).

However, when trying to move a form from one environment to the next, the replaced a form does not pick up the GravityFlow configuration.

I see in this code, that PowerBoost is delegating the update to GFAPI::update_form().

What I don't know is whether GFPB_Form_Replacer::update_forms() should also be responsible for calling GFAPI:update_feed()?

Or if this may be an issue in GFAPI in that it should detect that the form has a feeds property and attempt to update the feeds as well?

Or it could be that GravityFlow is hooking into GravityForms incorrectly?

Sorry, I'm not an experienced WordPress plugin developer. I'm just trying to figure out a way for us to migrate the workflows between environments and avoid having to manually rebuild them.

Any guidance or recommendations would be appreciated.

Thanks, Daniel.

12.json

@csalzano
Copy link
Owner

Thanks for trying my plugin. I don't have a copy of Gravity Flow. That's my problem, not yours. I'd look for a Gravity Flow save hook and start reading the nearby code to see how the feeds data is placed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants