-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Legacy Widget: Ensure the control form's IDs have a consistent number #31485
Conversation
Size Change: +51 B (0%) Total Size: 1.31 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Followed the testing steps, and this is working well.
@manooweb Would be great if you get a chance to test this in the upcoming version of Gutenberg.
a61b9e5
to
5bdb6dd
Compare
Wow! Thanks @noisysocks. |
Thanks for the really good instructions and sample code @manooweb! |
@noisysocks, @talldan It seems ok 👍 to me on the trunk and with the legacy widget example I provided. Wait for 10.6.x release and my other tests to confirm however it seems good. |
@noisysocks, @talldan it's ok for me with Gutenberg 10.6.1, I was able to adapt our jQuery javascript code of our legacy widget fields and make it work as expected. However I have another problem with the preview in the iframe but it's something else that doesn't concern this current PR and issue. |
Description
Fixes #28668.
Requires #31444.
Ensures that all of the IDs in a Legacy Widget block's form's inputs have the same number.
/widget-types/:type/encode
endpoint to accept anumber
param which controls the number used to generate the widget HTML that is returned.Control
to send its fakenumber
to the endpoint so that all of the form fields in the control have a consistent ID.How has this been tested?
Follow the steps in #28668 (comment).
Checklist:
*.native.js
files for terms that need renaming or removal).