Query gutenberg blocks with wp-graphql

Overview
Comments
  • Error with Gatsby V3

    Error with Gatsby V3

    Hello, thank you for this great plugin.

    Unfortunately I can't make it work with Gatsby V3. The build phase just stops with this error:

    Interfaces with thenodeInterfaceextension must have a fieldidof typeID!. Check the type definition ofWpBlockEditorContentNode.

    Deactivating Wp GraphQL Gutenberg Wordpress plugin the error disappears, but obviously I can't get the gutenberg blocks fields using GraphQL. Note that from the Wordpress graphiql client everythings works correctly, but Gatsby, using Wordpress source v5 (the Gatsby v3 updated version) just seems not to compile.

    Is there any way to fix this issue? Thank you!

    opened by tiggeymone 17
  • Revisions Blocks not populated

    Revisions Blocks not populated

    On revisions, blocks do not get resolved data when you use saveContent the data comes in

    See example:

    {
      "data": {
        "pageBy": {
          "title": "Test Page 2",
          "pageId": 544,
          "revisions": {
            "nodes": [
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page edited HI</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              },
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page edited sdd</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              },
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page edited 2</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              },
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page edited</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              },
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              },
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              },
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              },
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              },
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              },
              {
                "content": "\n<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\">\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page</p>\n</div></div>\n\n\n\n\n\n\n\n<p></p>\n",
                "blocks": []
              }
            ]
          },
          "blocks": [
            {
              "saveContent": "<div class=\"wp-block-cover has-background-dim\" style=\"background-image:url(http://localhost:8080/app/uploads/2019/11/1000-24.jpg)\"><div class=\"wp-block-cover__inner-container\"><!-- wp:paragraph {\"align\":\"center\",\"placeholder\":\"Write title…\",\"fontSize\":\"large\"} -->\n<p style=\"text-align:center\" class=\"has-large-font-size\">Test Page edited sdd</p>\n<!-- /wp:paragraph --></div></div>",
              "name": "core/cover"
            },
            {
              "saveContent": "",
              "name": "lndev-blocks/post-list-by-category"
            },
            {
              "saveContent": "",
              "name": "lndev-blocks/post-list-by-category"
            },
            {
              "saveContent": "<p></p>",
              "name": "core/paragraph"
            }
          ]
        }
      }
    }
    

    query

    # Try to write your query here
    query {
      pageBy(pageId: 544) {
        title
        pageId
        revisions{
          nodes{
            content
            blocks{
              name
              saveContent
            }
          }
        }
        blocks{
          saveContent
          name
              
        }
      }
    }
    
    opened by lnesi 16
  • Plugin breaks with PHP 8

    Plugin breaks with PHP 8

    We've encountered various issues with this plugin when running PHP 8 that do not appear when running PHP 7.

    A user of our Next.js starter repo pointed to the ivome/graphql-relay-php dependency as a potential culprit.

    One issue we've been able to replicate on several devices:

    1. Add a paragraph block to a page with some text
    2. Change WP to PHP 8
    3. Query page: (this should work without error)
    query MyQuery {
      page(id: "<ID>", idType: DATABASE_ID) {
        blocksJSON
      }
    }
    
    1. Edit paragraph block to set a custom font-size
    2. Re-query page (it should throw an error this time) *
    3. Change WP to PHP 7
    4. Re-query page again (it should not throw an error now)

    Error thrown when querying page:

    {
      "errors": [
        {
          "debugMessage": "get_object_vars(): Argument #1 ($object) must be of type object, array given",
          "message": "Internal server error",
          "extensions": {
            "category": "internal"
          },
          "locations": [
            {
              "line": 3,
              "column": 5
            }
          ],
          "path": [
            "page",
            "blocksJSON"
          ],
          "trace": [
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/vendor/opis/json-schema/src/Validator.php",
              "line": 1792,
              "function": "get_object_vars(array(1))"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/vendor/opis/json-schema/src/Validator.php",
              "line": 953,
              "call": "Opis\\JsonSchema\\Validator::validateObject(instance of stdClass, array(1), array(1), array(0), instance of Opis\\JsonSchema\\Schema, instance of stdClass, instance of Opis\\JsonSchema\\ValidationResult, null)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/vendor/opis/json-schema/src/Validator.php",
              "line": 519,
              "call": "Opis\\JsonSchema\\Validator::validateProperties(instance of stdClass, array(1), array(1), array(0), instance of Opis\\JsonSchema\\Schema, instance of stdClass, instance of Opis\\JsonSchema\\ValidationResult, null)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/vendor/opis/json-schema/src/Validator.php",
              "line": 332,
              "call": "Opis\\JsonSchema\\Validator::validateKeywords(instance of stdClass, array(1), array(1), array(0), instance of Opis\\JsonSchema\\Schema, instance of stdClass, instance of Opis\\JsonSchema\\ValidationResult)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/vendor/opis/json-schema/src/Validator.php",
              "line": 1915,
              "call": "Opis\\JsonSchema\\Validator::validateSchema(instance of stdClass, array(1), array(1), array(0), instance of Opis\\JsonSchema\\Schema, instance of stdClass, instance of Opis\\JsonSchema\\ValidationResult)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/vendor/opis/json-schema/src/Validator.php",
              "line": 953,
              "call": "Opis\\JsonSchema\\Validator::validateObject(instance of stdClass, instance of stdClass, array(1), array(0), instance of Opis\\JsonSchema\\Schema, instance of stdClass, instance of Opis\\JsonSchema\\ValidationResult, array(2))"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/vendor/opis/json-schema/src/Validator.php",
              "line": 519,
              "call": "Opis\\JsonSchema\\Validator::validateProperties(instance of stdClass, instance of stdClass, array(0), array(0), instance of Opis\\JsonSchema\\Schema, instance of stdClass, instance of Opis\\JsonSchema\\ValidationResult, array(2))"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/vendor/opis/json-schema/src/Validator.php",
              "line": 332,
              "call": "Opis\\JsonSchema\\Validator::validateKeywords(instance of stdClass, instance of stdClass, array(0), array(0), instance of Opis\\JsonSchema\\Schema, instance of stdClass, instance of Opis\\JsonSchema\\ValidationResult)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/vendor/opis/json-schema/src/Validator.php",
              "line": 97,
              "call": "Opis\\JsonSchema\\Validator::validateSchema(instance of stdClass, instance of stdClass, array(0), array(0), instance of Opis\\JsonSchema\\Schema, instance of stdClass, instance of Opis\\JsonSchema\\ValidationResult)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/src/Blocks/Block.php",
              "line": 145,
              "call": "Opis\\JsonSchema\\Validator::schemaValidation(instance of stdClass, instance of Opis\\JsonSchema\\Schema)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/src/Blocks/Block.php",
              "line": 177,
              "call": "WPGraphQLGutenberg\\Blocks\\Block::parse_attributes(array(5), array(14))"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/src/Blocks/Block.php",
              "line": 25,
              "call": "WPGraphQLGutenberg\\Blocks\\Block::__construct(array(5), 15, array(36), 0, null)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql-gutenberg/src/Schema/Types/InterfaceType/BlockEditorContentNode.php",
              "line": 36,
              "call": "WPGraphQLGutenberg\\Blocks\\Block::create_blocks(array(1), 15, array(36))"
            },
            {
              "call": "WPGraphQLGutenberg\\Schema\\Types\\InterfaceType\\BlockEditorContentNode::WPGraphQLGutenberg\\Schema\\Types\\InterfaceType\\{closure}(instance of WPGraphQL\\Model\\Post, array(0), instance of WPGraphQL\\AppContext, instance of GraphQL\\Type\\Definition\\ResolveInfo)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/src/Utils/InstrumentSchema.php",
              "line": 177,
              "function": "call_user_func(instance of Closure, instance of WPGraphQL\\Model\\Post, array(0), instance of WPGraphQL\\AppContext, instance of GraphQL\\Type\\Definition\\ResolveInfo)"
            },
            {
              "call": "WPGraphQL\\Utils\\InstrumentSchema::WPGraphQL\\Utils\\{closure}(instance of WPGraphQL\\Model\\Post, array(0), instance of WPGraphQL\\AppContext, instance of GraphQL\\Type\\Definition\\ResolveInfo)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/src/Utils/InstrumentSchema.php",
              "line": 177,
              "function": "call_user_func(instance of Closure, instance of WPGraphQL\\Model\\Post, array(0), instance of WPGraphQL\\AppContext, instance of GraphQL\\Type\\Definition\\ResolveInfo)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php",
              "line": 624,
              "call": "WPGraphQL\\Utils\\InstrumentSchema::WPGraphQL\\Utils\\{closure}(instance of WPGraphQL\\Model\\Post, array(0), instance of WPGraphQL\\AppContext, instance of GraphQL\\Type\\Definition\\ResolveInfo)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php",
              "line": 550,
              "call": "GraphQL\\Executor\\ReferenceExecutor::resolveFieldValueOrError(instance of GraphQL\\Type\\Definition\\FieldDefinition, instance of GraphQL\\Language\\AST\\FieldNode, instance of Closure, instance of WPGraphQL\\Model\\Post, instance of GraphQL\\Type\\Definition\\ResolveInfo)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php",
              "line": 1196,
              "call": "GraphQL\\Executor\\ReferenceExecutor::resolveField(GraphQLType: Page, instance of WPGraphQL\\Model\\Post, instance of ArrayObject(1), array(2))"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php",
              "line": 1146,
              "call": "GraphQL\\Executor\\ReferenceExecutor::executeFields(GraphQLType: Page, instance of WPGraphQL\\Model\\Post, array(1), instance of ArrayObject(1))"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php",
              "line": 1107,
              "call": "GraphQL\\Executor\\ReferenceExecutor::collectAndExecuteSubfields(GraphQLType: Page, instance of ArrayObject(1), array(1), instance of WPGraphQL\\Model\\Post)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php",
              "line": 794,
              "call": "GraphQL\\Executor\\ReferenceExecutor::completeObjectValue(GraphQLType: Page, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(1), instance of WPGraphQL\\Model\\Post)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php",
              "line": 652,
              "call": "GraphQL\\Executor\\ReferenceExecutor::completeValue(GraphQLType: Page, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(1), instance of WPGraphQL\\Model\\Post)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/Promise/Adapter/SyncPromise.php",
              "line": 148,
              "call": "GraphQL\\Executor\\ReferenceExecutor::GraphQL\\Executor\\{closure}(instance of WPGraphQL\\Model\\Post)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/Promise/Adapter/SyncPromise.php",
              "line": 53,
              "call": "GraphQL\\Executor\\Promise\\Adapter\\SyncPromise::GraphQL\\Executor\\Promise\\Adapter\\{closure}()"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Executor/Promise/Adapter/SyncPromiseAdapter.php",
              "line": 149,
              "call": "GraphQL\\Executor\\Promise\\Adapter\\SyncPromise::runQueue()"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Server/Helper.php",
              "line": 214,
              "call": "GraphQL\\Executor\\Promise\\Adapter\\SyncPromiseAdapter::wait(instance of GraphQL\\Executor\\Promise\\Promise)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/vendor/webonyx/graphql-php/src/Server/StandardServer.php",
              "line": 136,
              "call": "GraphQL\\Server\\Helper::executeOperation(instance of GraphQL\\Server\\ServerConfig, instance of GraphQL\\Server\\OperationParams)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/src/Request.php",
              "line": 602,
              "call": "GraphQL\\Server\\StandardServer::executeRequest(instance of GraphQL\\Server\\OperationParams)"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/src/Router.php",
              "line": 465,
              "call": "WPGraphQL\\Request::execute_http()"
            },
            {
              "file": ".../app/public/wp-content/plugins/wp-graphql/src/Router.php",
              "line": 270,
              "call": "WPGraphQL\\Router::process_http_request()"
            },
            {
              "file": ".../app/public/wp-includes/class-wp-hook.php",
              "line": 292,
              "call": "WPGraphQL\\Router::resolve_http_request(instance of WP)"
            },
            {
              "file": ".../app/public/wp-includes/class-wp-hook.php",
              "line": 316,
              "call": "WP_Hook::apply_filters(null, array(1))"
            },
            {
              "file": ".../app/public/wp-includes/plugin.php",
              "line": 551,
              "call": "WP_Hook::do_action(array(1))"
            },
            {
              "file": ".../app/public/wp-includes/class-wp.php",
              "line": 388,
              "function": "do_action_ref_array('parse_request', array(1))"
            },
            {
              "file": ".../app/public/wp-includes/class-wp.php",
              "line": 750,
              "call": "WP::parse_request((empty string))"
            },
            {
              "file": ".../app/public/wp-includes/functions.php",
              "line": 1291,
              "call": "WP::main((empty string))"
            },
            {
              "file": ".../app/public/wp-blog-header.php",
              "line": 16,
              "function": "wp()"
            },
            {
              "file": ".../app/public/index.php",
              "line": 17,
              "function": "require('.../app/public/wp-blog-header.php')"
            }
          ]
        }
      ],
      "data": {
        "page": {
          "blocksJSON": null
        }
      },
      "extensions": {
        "debug": []
      }
    }
    
    opened by ravewebdev 13
  • Type conflict when pulling entire schema

    Type conflict when pulling entire schema

    Hey Peter! Hope the new plugin is going well :) I'm testing out this one with the upcoming gatsby-source-wordpress@v4. The new version uses introspection to generate full-schema queries in order to pull the entire WPGQL schema, and while doing so I'm running into some type conflicts.

    When I run this query

    query NODE_LIST_QUERY {
      pages {
        nodes {
          blocks {
            __typename
            ... on CoreParagraphBlock {
              attributes {
                __typename
                ... on CoreParagraphBlockAttributesV2 {
                  fontSize
                }
                ... on CoreParagraphBlockAttributesV3 {
                  content
                  fontSize
                }
              }
            }
            ... on CoreCodeBlock {
              attributes {
                content
              }
            }
          }
        }
      }
    }
    
    

    I get these errors:

    {
      "errors": [
        {
          "message": "Fields \"attributes\" conflict because subfields \"content\" conflict because they return conflicting types String! and String. Use different aliases on the fields to fetch both if this was intentional.",
          "category": "graphql",
          "locations": [
            {
              "line": 7,
              "column": 11
            },
            {
              "line": 13,
              "column": 15
            },
            {
              "line": 19,
              "column": 11
            },
            {
              "line": 20,
              "column": 13
            }
          ]
        },
        {
          "message": "Fields \"fontSize\" conflict because they return conflicting types Float and String. Use different aliases on the fields to fetch both if this was intentional.",
          "category": "graphql",
          "locations": [
            {
              "line": 10,
              "column": 15
            },
            {
              "line": 14,
              "column": 15
            }
          ]
        }
      ]
    }
    

    I think it's because different block types that are implementing the Block interface are defining fields with the same name but the fields have different types. Any thoughts on a quick fix? @jasonbahl curious if you have any ideas as well

    opened by TylerBarnes 10
  • Internal server error when quering blocks

    Internal server error when quering blocks

    Hi,

    It's me again. I have updated the plugin to the latest version as well as pulled requested plugin dependencies: WP GraphQL 0.9.1 WP GraphQL Gutenberg 0.3.1 WP GraphQL GutenbergACF 0.3.0

    I can't query any block. I get the following response on page query no matter what client I use(Postman, GraphQL, Gatsby GraphQL Client)

      "errors": [
        {
          "message": "Internal server error",
          "extensions": {
            "category": "internal"
          },
          "locations": [
            {
              "line": 4,
              "column": 7
            }
          ],
          "path": [
            "pages",
            "nodes",
            0,
            "blocks"
          ]
        }
      ],
      "data": {
        "pages": {
          "nodes": [
            {
              "blocks": null,
              "id": "cG9zdDozODU="
            }
          ]
        }
      }
    }
    

    Example query: query MyQuery { pages { nodes { id blocks { name } } } }

    Kind regards, Marcin

    opened by mmazurowski 8
  • Unable to run Gutenberg Admin

    Unable to run Gutenberg Admin

    When I try to update all my posts to be ready for the plugin, I get the following error on the third posts.

    Failed to update post with id 1716. The response is not a valid JSON response.

    WP version: 5.2.3

    opened by jedifunk 7
  • Added connection from CoreImageBlock to MediaItem

    Added connection from CoreImageBlock to MediaItem

    Hi.

    Based on a personal problem, and to answer this issue, I propose this PR.

    I'm of course welcome to modifications/advices. Note that this is my first ever PR to an open source project :)

    opened by Bryndille1701 6
  • PHP Fatal error: Uncaught Error: Cannot use object of type GraphQL\\Type\\SchemaConfig as array

    PHP Fatal error: Uncaught Error: Cannot use object of type GraphQL\\Type\\SchemaConfig as array

    Wordpress instance just auto-updated WPGraphQL plugin, and now getting a 500 error when trying to load the schema in the wp-admin GraphiQL viewer.

    PHP Fatal error: Uncaught Error: Cannot use object of type GraphQL\Type\SchemaConfig as array in wp-content/plugins/wp-graphql-gutenberg-0.3.6/src/Schema/Types/BlockTypes.php:272 Stack trace: #0 wp-includes/class-wp-hook.php(287): WPGraphQLGutenberg\Schema\Types\BlockTypes->WPGraphQLGutenberg\Schema\Types\{closure}(Object(GraphQL\Type\SchemaConfig)) 1 wp-includes/plugin.php(212): WP_Hook->apply_filters(Object(GraphQL\Type\SchemaConfig), Array) 2 wp-content/plugins/wp-graphql/src/WPSchema.php(50): apply_filters('graphql_schema_...', Object(GraphQL\Type\SchemaConfig)) 3 wp-content/plugins/wp-graphql/src/Registry/SchemaRegistry.php(50): WPGraphQL\WPSchema->__construct(Object(GraphQL\Type\SchemaConfig)) 4 wp-content/plugins/wp-graphql/wp-graphql.php(602): WPGraphQL\Registry\SchemaRegistry->get_schema() 5 wp-content/plugins/wp-graphql/src/Request. in wp-content/plugins/wp-graphql-gutenberg-0.3.6/src/Schema/Types/BlockTypes.php on line 272, referer: https://domain.com/wp-admin/admin.php?page=graphiql-ide

    Version of wpgraphql plugin before, that was working, was 1.0.5, version now is 1.1.1.

    opened by jaydiablo 6
  • 500 error with wordpress 5.6

    500 error with wordpress 5.6

    Hi, we have a 500 error with the last version of WP Graphql Gutenberg plugin : PHP Fatal error: Uncaught Error: Cannot use object of type GraphQL\Type\SchemaConfig as array in \wp-content\plugins\wp-graphql-gutenberg\plugin.php:1080

    And we have not access to graphql endpoint, we have 500 too on the site.com/graphql, but when we deactivate WP GraphQL Gutenberg, all is ok

    opened by ahsynv 5
  • Content editor whitescreen: The editor has encountered an unexpected error.

    Content editor whitescreen: The editor has encountered an unexpected error.

    Hey there!

    For some reason, the content editor fails to load when this plugin is activated 🤔. This is for Pages and Posts.

    image

    What's the best way to troubleshoot this?

    FYI - I am able to run queries on a page with blocks via GraphiQL on WordPress. image

    Using: -wp-graphql: 0.9.1 -wp-gatsby: 0.4.1 -wp-graphql-gutenberg: 0.3.4 -Wordpress: 5.2.4

    The dialogue that pops up allows me to copy the error. Here's the dump of that:

    ue@*****/wp-content/plugins/wp-graphql-gutenberg-0.3.4/build/index.js?ver=fd9cc99659d1d150b19d0f988a85b971:24:8591
    Td@*****/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:82:11
    hi@*****/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:102:385
    Qg@*****/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:144:219
    Rg@*****/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:145:76
    Sc@*****/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:158:109
    Z@*****/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:156:494
    Kc@*****/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:155:52
    ya@*****/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:153:159
    enqueueSetState@*****/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:202:411
    t.prototype.setState@*****/wp-includes/js/dist/vendor/react.min.js?ver=16.8.4:20:433
    value@*****/wp-includes/js/dist/data.min.js?ver=4.4.0:1:16219
    value/this.unsubscribe<@*****/wp-includes/js/dist/data.min.js?ver=4.4.0:1:16397
    n/<@*****/wp-includes/js/dist/data.min.js?ver=4.4.0:1:11659
    n@*****/wp-includes/js/dist/data.min.js?ver=4.4.0:1:11632
    m/y</<@*****/wp-includes/js/dist/data.min.js?ver=4.4.0:1:8807
    v@*****/wp-includes/js/dist/data.min.js?ver=4.4.0:1:29557
    b/</<@*****/wp-includes/js/dist/data.min.js?ver=4.4.0:1:5879
    O/</</<@*****/wp-includes/js/dist/data.min.js?ver=4.4.0:1:6307
    a/</</<@*****/wp-includes/js/dist/redux-routine.min.js?ver=3.2.0:1:9567
    dispatch@*****/wp-includes/js/dist/data.min.js?ver=4.4.0:1:32017
    i/<@*****/wp-includes/js/dist/redux-routine.min.js?ver=3.2.0:1:9218
    e/<@*****/wp-includes/js/dist/redux-routine.min.js?ver=3.2.0:1:5434
    e@*****/wp-includes/js/dist/redux-routine.min.js?ver=3.2.0:1:5410
    o/<@*****/wp-includes/js/dist/redux-routine.min.js?ver=3.2.0:1:5364
    
    
    opened by jacobarriola 5
  • Unable to create/update pages with block type

    Unable to create/update pages with block type "Cover"

    Hi there!

    Thanks for putting this together, so far it's been working quite well for me for the block types I've tried so far.

    The block type "cover" however seems to not be working correctly, however. Any create/update of a page with this built in block gets stuck loading, and doesn't finish. The content is also not updated, proving to be a bit of a blocker.

    There is an error message that is presented when loading hangs

    PHP Notice:  Undefined variable: post in /var/www/html/wp-content/plugins/a/plugin.php on line 680
    

    Finding this line in the code, I suppose it is possible for $post to be undefined as it is a parameter of the calling function and potentially simply nothing passed in. Unfortunately I can't get a stack trace out to give you more detail. Also not sure if this is the root cause or just a coincidence either, as it is just a warning I don't think it is throwing here.

    WordPress: 5.2.2 PHP: 7.2 wp-graphql-gutenberg: 0.0.2 Docker Image: https://hub.docker.com/_/wordpress - wordpress:5-php7.2 (Alpine Linux)

    opened by yjimk 5
  • Bump json5 from 1.0.1 to 1.0.2

    Bump json5 from 1.0.1 to 1.0.2

    Bumps json5 from 1.0.1 to 1.0.2.

    Release notes

    Sourced from json5's releases.

    v1.0.2

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295). This has been backported to v1. (#298)
    Changelog

    Sourced from json5's changelog.

    Unreleased [code, diff]

    v2.2.3 [code, diff]

    v2.2.2 [code, diff]

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1 [code, diff]

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0 [code, diff]

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2 [code, diff]

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump json5 from 1.0.1 to 1.0.2 in /docs

    Bump json5 from 1.0.1 to 1.0.2 in /docs

    Bumps json5 from 1.0.1 to 1.0.2.

    Release notes

    Sourced from json5's releases.

    v1.0.2

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295). This has been backported to v1. (#298)
    Changelog

    Sourced from json5's changelog.

    Unreleased [code, diff]

    v2.2.3 [code, diff]

    v2.2.2 [code, diff]

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1 [code, diff]

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0 [code, diff]

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2 [code, diff]

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump express from 4.17.1 to 4.18.2 in /docs

    Bump express from 4.17.1 to 4.18.2 in /docs

    Bumps express from 4.17.1 to 4.18.2.

    Release notes

    Sourced from express's releases.

    4.18.2

    4.18.1

    • Fix hanging on large stack of sync routes

    4.18.0

    ... (truncated)

    Changelog

    Sourced from express's changelog.

    4.18.2 / 2022-10-08

    4.18.1 / 2022-04-29

    • Fix hanging on large stack of sync routes

    4.18.0 / 2022-04-25

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump express from 4.17.1 to 4.18.2

    Bump express from 4.17.1 to 4.18.2

    Bumps express from 4.17.1 to 4.18.2.

    Release notes

    Sourced from express's releases.

    4.18.2

    4.18.1

    • Fix hanging on large stack of sync routes

    4.18.0

    ... (truncated)

    Changelog

    Sourced from express's changelog.

    4.18.2 / 2022-10-08

    4.18.1 / 2022-04-29

    • Fix hanging on large stack of sync routes

    4.18.0 / 2022-04-25

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump qs from 6.5.2 to 6.5.3 in /docs

    Bump qs from 6.5.2 to 6.5.3 in /docs

    Bumps qs from 6.5.2 to 6.5.3.

    Changelog

    Sourced from qs's changelog.

    6.5.3

    • [Fix] parse: ignore __proto__ keys (#428)
    • [Fix] utils.merge: avoid a crash with a null target and a truthy non-array source
    • [Fix] correctly parse nested arrays
    • [Fix] stringify: fix a crash with strictNullHandling and a custom filter/serializeDate (#279)
    • [Fix] utils: merge: fix crash when source is a truthy primitive & no options are provided
    • [Fix] when parseArrays is false, properly handle keys ending in []
    • [Fix] fix for an impossible situation: when the formatter is called with a non-string value
    • [Fix] utils.merge: avoid a crash with a null target and an array source
    • [Refactor] utils: reduce observable [[Get]]s
    • [Refactor] use cached Array.isArray
    • [Refactor] stringify: Avoid arr = arr.concat(...), push to the existing instance (#269)
    • [Refactor] parse: only need to reassign the var once
    • [Robustness] stringify: avoid relying on a global undefined (#427)
    • [readme] remove travis badge; add github actions/codecov badges; update URLs
    • [Docs] Clean up license text so it’s properly detected as BSD-3-Clause
    • [Docs] Clarify the need for "arrayLimit" option
    • [meta] fix README.md (#399)
    • [meta] add FUNDING.yml
    • [actions] backport actions from main
    • [Tests] always use String(x) over x.toString()
    • [Tests] remove nonexistent tape option
    • [Dev Deps] backport from main
    Commits
    • 298bfa5 v6.5.3
    • ed0f5dc [Fix] parse: ignore __proto__ keys (#428)
    • 691e739 [Robustness] stringify: avoid relying on a global undefined (#427)
    • 1072d57 [readme] remove travis badge; add github actions/codecov badges; update URLs
    • 12ac1c4 [meta] fix README.md (#399)
    • 0338716 [actions] backport actions from main
    • 5639c20 Clean up license text so it’s properly detected as BSD-3-Clause
    • 51b8a0b add FUNDING.yml
    • 45f6759 [Fix] fix for an impossible situation: when the formatter is called with a no...
    • f814a7f [Dev Deps] backport from main
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump qs from 6.5.2 to 6.5.3

    Bump qs from 6.5.2 to 6.5.3

    Bumps qs from 6.5.2 to 6.5.3.

    Changelog

    Sourced from qs's changelog.

    6.5.3

    • [Fix] parse: ignore __proto__ keys (#428)
    • [Fix] utils.merge: avoid a crash with a null target and a truthy non-array source
    • [Fix] correctly parse nested arrays
    • [Fix] stringify: fix a crash with strictNullHandling and a custom filter/serializeDate (#279)
    • [Fix] utils: merge: fix crash when source is a truthy primitive & no options are provided
    • [Fix] when parseArrays is false, properly handle keys ending in []
    • [Fix] fix for an impossible situation: when the formatter is called with a non-string value
    • [Fix] utils.merge: avoid a crash with a null target and an array source
    • [Refactor] utils: reduce observable [[Get]]s
    • [Refactor] use cached Array.isArray
    • [Refactor] stringify: Avoid arr = arr.concat(...), push to the existing instance (#269)
    • [Refactor] parse: only need to reassign the var once
    • [Robustness] stringify: avoid relying on a global undefined (#427)
    • [readme] remove travis badge; add github actions/codecov badges; update URLs
    • [Docs] Clean up license text so it’s properly detected as BSD-3-Clause
    • [Docs] Clarify the need for "arrayLimit" option
    • [meta] fix README.md (#399)
    • [meta] add FUNDING.yml
    • [actions] backport actions from main
    • [Tests] always use String(x) over x.toString()
    • [Tests] remove nonexistent tape option
    • [Dev Deps] backport from main
    Commits
    • 298bfa5 v6.5.3
    • ed0f5dc [Fix] parse: ignore __proto__ keys (#428)
    • 691e739 [Robustness] stringify: avoid relying on a global undefined (#427)
    • 1072d57 [readme] remove travis badge; add github actions/codecov badges; update URLs
    • 12ac1c4 [meta] fix README.md (#399)
    • 0338716 [actions] backport actions from main
    • 5639c20 Clean up license text so it’s properly detected as BSD-3-Clause
    • 51b8a0b add FUNDING.yml
    • 45f6759 [Fix] fix for an impossible situation: when the formatter is called with a no...
    • f814a7f [Dev Deps] backport from main
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
Releases(v0.4.1)
  • v0.4.1(Dec 5, 2022)

  • v0.4.0(Dec 2, 2022)

    What's Changed

    • fix: WPGraphQL v1.13+ compatibility by @jasonbahl in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/165
    • v0.3.12 by @pristas-peter in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/148
    • Update composer autoload by @kuuak in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/149
    • Bump loader-utils and webpack-cli by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/163
    • Bump terser from 4.6.11 to 4.8.1 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/154
    • Bump async from 2.6.3 to 2.6.4 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/146
    • Bump minimist from 1.2.5 to 1.2.6 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/144
    • Bump ajv from 6.12.0 to 6.12.6 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/137
    • Bump path-parse from 1.0.6 to 1.0.7 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/121
    • Bump postcss from 7.0.27 to 7.0.36 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/110
    • Bump ws from 5.2.2 to 5.2.3 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/108
    • Bump merge-deep from 3.0.2 to 3.0.3 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/106
    • Bump browserslist from 4.11.1 to 4.16.6 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/105
    • Bump hosted-git-info from 2.8.8 to 2.8.9 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/103
    • Bump lodash from 4.17.15 to 4.17.21 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/102
    • Bump ssri from 6.0.1 to 6.0.2 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/101
    • Bump elliptic from 6.5.2 to 6.5.4 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/88
    • Bump ini from 1.3.5 to 1.3.7 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/69
    • Bump websocket-extensions from 0.1.3 to 0.1.4 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/48
    • Bump tmpl from 1.0.4 to 1.0.5 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/125
    • Bump decode-uri-component from 0.2.0 to 0.2.2 in /docs by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/166
    • Bump socket.io-parser from 3.3.0 to 3.3.3 in /docs by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/167
    • Bump y18n from 4.0.0 to 4.0.3 by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/168
    • Fix value reference warning with PHP 8 by @colis in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/157
    • Bump terser from 4.6.4 to 4.8.1 in /docs by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/170
    • Bump moment from 2.24.0 to 2.29.4 in /docs by @dependabot in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/171

    New Contributors

    • @kuuak made their first contribution in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/149
    • @dependabot made their first contribution in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/163
    • @colis made their first contribution in https://github.com/pristas-peter/wp-graphql-gutenberg/pull/157

    Full Changelog: https://github.com/pristas-peter/wp-graphql-gutenberg/compare/v0.3.12...v0.4.0

    Source code(tar.gz)
    Source code(zip)
  • v0.3.12(May 19, 2022)

  • v0.3.11(Aug 16, 2021)

  • v0.3.10(Aug 6, 2021)

  • v0.3.9(Aug 6, 2021)

  • v0.3.8(Mar 5, 2021)

  • v0.3.7(Jan 18, 2021)

  • v0.3.6(Dec 10, 2020)

  • v0.3.5(Nov 21, 2020)

  • v0.3.4(Jun 25, 2020)

    Release Notes

    Breaking Changes

    Bug Fixes

    • Change BlockEditorPreview internals to ensure compability with gatsby-source-wordpress-experimental
    Source code(tar.gz)
    Source code(zip)
  • v0.3.3(Jun 16, 2020)

    Release Notes

    Breaking Changes

    Bug Fixes

    • Fix accessing optional 'selector' key without checking for its presence first
    • Mark block as core/freeform when innerHTML is not empty and block has no name #52
    Source code(tar.gz)
    Source code(zip)
  • v0.3.2(Jun 12, 2020)

    Release Notes

    Breaking Changes

    Bug Fixes

    • Add a workaround when translations are not working properly when importing @wordpress/blocks directly #49
    • Fix attributes parsing when there is a multiline html source
    Source code(tar.gz)
    Source code(zip)
  • v0.3.1(Jun 2, 2020)

  • v0.3.0(May 28, 2020)

    Release Notes

    Breaking Changes

    • the parsing of blocks has been moved to PHP codebase. Now the plugin is only dependant on the client side block registry
    • clientId, isValid, validationIssues fields have been removed due to changes above

    Bug Fixes

    N/A

    Source code(tar.gz)
    Source code(zip)
  • v0.2.2(May 21, 2020)

    Release Notes

    Breaking Changes

    n/a. Please open an issue if you discover otherwise.

    Bug Fixes

    Support for wp-graphql 0.9.0 changes

    • Fix register_graphql_scalar call signature updated in upstream
    • Change interfaces registration to existing types to use new upstream method
    Source code(tar.gz)
    Source code(zip)
  • v0.2.1(May 11, 2020)

    Release Notes

    Breaking Changes

    n/a. Please open an issue if you discover otherwise.

    Bug Fixes

    • Scalar types now use register_graphql_scalar API
    • Attribute types with query field are now properly typed
    • Fix registering attributes types with no fields (#35)
    Source code(tar.gz)
    Source code(zip)
  • v0.2.0(Apr 30, 2020)

    Release Notes

    Summary

    This is a complete rewrite of the plugin. Please read carefully before upgrading.

    New Features

    • Adds support for revisions
    • Adds new optional Server component written in JS (more info in docs)
    • Adds new Previews functionality (more info in docs)
    • New docs
    • Upgrading of stale content in admin uses new faster technique
    • Adds ReusableBlock type

    Breaking Changes

    • Resolver will now throw exception if the parsed content is missing, or out of sync (stale)
    • Attributes type name without the suffix is always the latest definition, deprecated attribute types now have DeprecatedV1, DeprecatedV2 suffix, for example the CoreParagraphBlockAtrributesV4 is now just CoreParagraphBlockAtrributes and CoreParagraphBlockAtrributesV1 -> CoreParagraphBlockAtrributesDeprecatedV1 and so...
    • some fields on RootQuery were renamed to match the base plugin naming, like postsWithBlocks to blockEditorContentNodes
    • reusable blocks now have their own CoreBlock type with reference to ReusableBlock type
    Source code(tar.gz)
    Source code(zip)
  • v0.1.4(Jan 8, 2020)

  • v0.1.3(Dec 5, 2019)

    Bugfixes:

    • Fix checking of meta update return value, add postWithBlocks field

    Other:

    • Update JS packages
    • Add postsWithBlocks field to RootQuery
    • Add new union types for posts
    Source code(tar.gz)
    Source code(zip)
  • v0.1.2(Dec 2, 2019)

  • 0.1.0(Oct 30, 2019)

The easiest way to develop and release Gutenberg blocks (components) for WordPress

Contents Install Comparison with competition Future Plans Usage Creating a Block Install npm install gutenblock -g This is a Gutenberg plugin creator

Zach Silveira 239 Nov 11, 2022
Scaffold plugin for creating and managing Blocks, Block Patterns, Block Styles and Block Editor Sidebars in the WordPress Block Editor (aka Gutenberg).

WordPress Block Editor Scaffold This project is a template repo for developing WordPress Blocks, Block Patterns, Block Styles and Block Editor Sidebar

Rareview 6 Aug 2, 2022
Enable query locking for WPGraphQL by implementing persisted GraphQL queries.

?? WP GraphQL Lock This plugin enables query locking for WPGraphQL by implementing persisted GraphQL queries. Persisted GraphQL queries allow a GraphQ

Valu Digital 21 Oct 9, 2022
An WPGraphQL extension that adds SearchWP's query functionality to the GraphQL server

QL Search What is QL Search? An extension that integrates SearchWP into WPGraphQL. Quick Install Install & activate SearchWP v3.1.9+ Install & activat

Funkhaus 11 May 5, 2022
📦 A zero-configuration #0CJS developer toolkit for building WordPress Gutenberg block plugins.

create-guten-block is zero configuration dev-toolkit (#0CJS) to develop WordPress Gutenberg blocks in a matter of minutes without configuring React, w

Ahmad Awais ⚡️ 3.1k Dec 23, 2022
Gutenberg Custom Fields... wait what?

Gutenberg Custom Fields Gutenberg Custom Fields allows you to control the content of the Gutenberg edit screen by creating pre-filled templates. Navig

Riad Benguella 192 Dec 24, 2022
Documents WordPress Classic Editor integration points and their Gutenberg equivalents

Gutenberg Migration Guide This repository documents WordPress Classic Editor customization points and their Gutenberg equivalents (if such exist). Its

Daniel Bachhuber 185 Nov 16, 2022
A plugin to disable the drop cap option in Gutenberg editor paragraph block. This is version 2.

Disable Drop Cap (v2) A plugin to disable drop cap option in the Gutenberg editor block editor paragraph block. Note for WordPress 5.8 With WordPress

Johannes Siipola 4 Jan 4, 2022
Structured content blocks for WPGraphQL

WPGraphQL Content Blocks (Structured Content) This WPGraphQL plugin returns a WordPress post’s content as a shallow tree of blocks and allows for some

Quartz 72 Oct 3, 2022
:rocket: GraphQL API for WordPress

WPGraphQL WPGraphQL is a free, open-source WordPress plugin that provides an extendable GraphQL schema and API for any WordPress site. Below are some

WPGraphQL 3.4k Jan 5, 2023
Makes WP GraphQL's authetication "just work". It does this by customizing the CORS headers.

WP GraphQL CORS The primary purpose of this plugin is to make the WP GraphQL plugin authentication "just work". It does this by allowing you set the C

Funkhaus 86 Jan 5, 2023
Adds meta data registered via register_meta() to the GraphQL output.

WP GraphQL Meta This plugin is an add-on for the awesome WP GraphQL It builds on top of both WP GraphQL and the REST API. Any meta data you register u

Robert O'Rourke 18 Aug 4, 2021
Offset pagination for WP GraphQL

WP GraphQL Offset Pagination This is an extension for the WPGraphQL plugin for WordPress. It adds basic offset pagination as opposed to the standard C

Daryll Doyle 13 Sep 19, 2022
Bringing the power of GraphQL to BuddyPress.

WPGraphQL BuddyPress Bringing the power of GraphQL to BuddyPress. Docs (soon) • Join Slack System Requirements PHP >= 7.1 WP >= 4.9 WPGraphQL >= lates

WPGraphQL 31 Jan 2, 2023
GraphQL API for interacting with Gravity Forms.

?? ?? WPGraphQL for Gravity Forms A WordPress plugin that provides a GraphQL API for interacting with Gravity Forms. Join the WPGraphQL community on S

Harness Software 135 Jan 2, 2023
Query gutenberg blocks with wp-graphql

WPGraphQL Gutenberg Query gutenberg blocks through wp-graphql Usage Docs Join our community through WpGraphQL Slack Install Requires PHP 7.0+ Requires

null 270 Jan 3, 2023
Twill GraphQL provides easy access to query-specific fields from Twill CMS modules and user-defined modules with GraphQL

Twill CMS GraphQL ?? WIP - not stable Twill GraphQL provides easy access to query-specific fields from Twill CMS modules and user-defined modules with

Izet Mulalic 8 Dec 6, 2022
Syntax to query GraphQL through URL params, which grants a GraphQL API the capability to be cached on the server.

Field Query Syntax to query GraphQL through URL params, which grants a GraphQL API the capability to be cached on the server. Install Via Composer com

PoP 4 Jan 7, 2022
Examples for extending WordPress/Gutenberg with blocks.

Gutenberg Examples Examples for extending Gutenberg with plugins which create blocks. See also: Gutenberg developer documentation Installation Gutenbe

null 1.1k Dec 29, 2022
The easiest way to develop and release Gutenberg blocks (components) for WordPress

Contents Install Comparison with competition Future Plans Usage Creating a Block Install npm install gutenblock -g This is a Gutenberg plugin creator

Zach Silveira 239 Nov 11, 2022