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

Could not determine type of attribute "templateLock" #127

Open
olie-larner opened this issue Oct 19, 2021 · 6 comments · May be fixed by #141
Open

Could not determine type of attribute "templateLock" #127

olie-larner opened this issue Oct 19, 2021 · 6 comments · May be fixed by #141

Comments

@olie-larner
Copy link

I am now getting the following error below the GraphQL options on an "Add New Field Group" page:
Warning: Could not determine type of attribute "templateLock" in "CoreColumnBlockAttributes" in /var/www/html/cms/wp-content/plugins/wp-graphql-gutenberg-0.3.11/src/Schema/Types/BlockTypes.php on line 87

@acafourek
Copy link

acafourek commented Oct 22, 2021

I see the same error on each request when WP_DEBUG is on.

The get_attribute_type function expects $attribute to be an array with a type value; it switches over $attribute['type']. But for the templateBlock. that attribute variable looks like this:

[
    [enum] => [
            [0] => all
            [1] => insert
            [2] => 
        ]
]

Using plugin v 0.3.11

@vstrelianyi
Copy link

I'm having the warning on editing Advanced Custom Fields graphql options
image

@rauluranga
Copy link

rauluranga commented Jan 12, 2022

Same here!, currently on WordPress 5.8, wp-graphql 1.6.11, wp-graphql-acf v0.5.3 and wp-graphql-gutenberg 0.3.11.
as @vstrelianyi mentions, I'm having the warning on editing Advanced Custom Fields graphql options

Screen Shot 2022-01-12 at 11 09 30

@Bjornjansfelt
Copy link

Anyone managed to solve this?

@nonlinearcom
Copy link

same here 👀

@rodrigo-arias rodrigo-arias linked a pull request Mar 21, 2022 that will close this issue
@Dev-Ditrict-Web
Copy link

Same here.

Anybody ever found a solution ?

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

Successfully merging a pull request may close this issue.

7 participants