Skip to content

Conversation

@dgwatkins
Copy link
Collaborator

@dgwatkins
Copy link
Collaborator Author

dgwatkins commented Nov 12, 2025

@strategio These are the builtin widgets that didn't have a configuration yet.

As you can see, some of them are empty. This is because they have translatable controls that we don't want to translate.

For example, the nav-menu widget has a menu_name but it isn't displayed in the frontend.

Others have fields that I have not been able to set in the UI, maybe leftovers? maybe unreleased features? (ie: arrows_normal_background_video_link in loop-carousel).

My question is, is it acceptable to add those widgets here with no fields?

@dgwatkins dgwatkins marked this pull request as ready for review November 12, 2025 17:45
Copy link
Member

@strategio strategio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dgwatkins, yes I think it's valid to have empty widget configuration. At least it will ensure we won't attempt to guess a config with our new mechanism.

Copy link
Member

@strategio strategio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dgwatkins
Copy link
Collaborator Author

merged and deployed

@dgwatkins dgwatkins merged commit 4591c1f into master Nov 12, 2025
1 check passed
@dgwatkins dgwatkins deleted the wpmlpb-737 branch November 12, 2025 18:45
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 this pull request may close these issues.

3 participants