Dovid Levine
Dovid Levine
In the interim as a workaround, you can add your necessary `$query_vars` using WP's built in `request` filter ([source code](https://github.com/wp-graphql/wp-graphql/blob/3182a5cfbb8fd9fa6613d002a162067ba06953e9/src/Data/NodeResolver.php#L346)). E.g. (written from my phone, double check for typos )....
@jasonbahl > I think we could move the filter down lower, right above line 352 (after all the context is established), but before the resolvers begin. Either that or introduce...
@renatonascalves fundamentally I agree (see my note on [the pr](https://github.com/wp-graphql/wp-graphql/pull/2386) and my comment on [this one](https://github.com/wp-graphql/wp-graphql/pull/2341#issuecomment-1128719980) ). But.... if the consensus on #2341 is to provide a way for customization...
Related: #2486 (can probably be temporarily resolved before #2491) cc: #2513
Hey @andrewmumblebee , Are you still facing this issue? Recent plugin releases have fixed a lot of issues with pagination cursors, so it's possible this got fixed as well, but...
@tobiasorosa Permalink Manager works by [modifying the `request`](https://plugins.trac.wordpress.org/browser/permalink-manager/trunk/includes/core/permalink-manager-core-functions.php#L52) in a way that is essentially dependent on the PHP `$_SERVER[`REQUEST_URI`], and thus likely incompatible with WPGraphQL (where the request URI is...
A screenshot from a fresh multisite instance with v1.8.0. Should be easy to add `SUPER_ADMIN` as an enum value. 
+1 As someone working to bring WP plugin support to graphql, I can see immediate benefit for a centralizing something like this. Currently WPGraphQL for GF only supports WPGatsby from...
Seems this issue stems from [various name sanitation `preg_replace()` calls](https://github.com/wp-graphql/wp-graphql/search?q=A-Za-z0-9) that strip out non-ASCII characters instead of replacing them, causing them to be registered as a duplicate e.g `Template_`. Also...