Skip to content
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.

Feature request: mutation #72

Closed
iMohamedSamir opened this issue Oct 21, 2019 · 7 comments
Closed

Feature request: mutation #72

iMohamedSamir opened this issue Oct 21, 2019 · 7 comments
Labels
enhancement New feature or request New Feature

Comments

@iMohamedSamir
Copy link

Sup, wouldn't it be awesome if wp-graphql-acf supported mutation? since acf doesn't support post/get value in api as far as I know, I tried, very hard even with ACF to REST API plugin

@Mambi
Copy link

Mambi commented Nov 11, 2019

yes, it would be useful

@jasonbahl jasonbahl added enhancement New feature or request New Feature labels Feb 24, 2020
@ivanjeremic
Copy link

For now, I need to use strapi or hasura because of this missing feature in wpgraphql-acf, any new status on when it will be implemented?

@imarindam
Copy link

Yes please! Much required!!

@lance-anderson
Copy link

Perhaps it's worth noting that wp-graphql exposes the register_graphql_mutation function which be used to leverage ACF's update_field function and other APIs for updating WP data.

@vstrelianyi
Copy link

would be great to have mutations build in the plugin. or at least there should be some kind of step-by-step instruction how to implement that...
I have tried what you have advised.. but without any success.

@colmobildev
Copy link

It would be very useful!

@jasonbahl
Copy link
Contributor

👋🏻 We are re-building WPGraphQL for ACF over here: https://github.com/wp-graphql/wpgraphql-acf.

I've created a new issue to track mutation support (and explain some current blockers). see: wp-graphql/wpgraphql-acf#109

I'm going to close this in favor of tracking it in the new repo.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request New Feature
Projects
None yet
Development

No branches or pull requests

8 participants