-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Post meta not saved if attributes not included in block JS #7425
Labels
[Feature] Block API
API that allows to express the block paradigm.
Needs Testing
Needs further testing to be confirmed.
[Type] Question
Questions about the design or development of the editor.
Comments
mtias
added
[Type] Question
Questions about the design or development of the editor.
[Feature] Block API
API that allows to express the block paradigm.
labels
Jul 19, 2018
Is this still the case? I don't see why it wouldn't work. |
@noisysocks that was a very long time ago and I honestly can't remember what I was doing then. This could potentially be closed and reopened in the future if needed. |
Thanks @LABCAT! Let's do that. |
This was referenced Dec 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
[Feature] Block API
API that allows to express the block paradigm.
Needs Testing
Needs further testing to be confirmed.
[Type] Question
Questions about the design or development of the editor.
Not sure if this is a bug or if this expected behaviour but I think the post_meta should save if the attributes have been registered in PHP (and not in JS).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Post meta is saved/updated
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
If I include the following in my block JS the meta value gets saved but if this is only included in PHP it does not:
attributes: { myMeta: { type: 'string', source: 'meta', meta: 'my_meta' } },
The text was updated successfully, but these errors were encountered: