Carlos Bravo
@cbravobernal on WordPress.org and Slack
Bio
Contributions
- Member Since: February 22nd, 2017
- Location: Spain
- Website: carlosbravo.blog
- GitHub: cbravobernal
- Job Title: Software Engineer
- Employer: Automattic
Contribution History
Carlos Bravo’s badges:- Core Contributor
- Core Team
- Documentation Contributor
- Meta Contributor
- Test Contributor
- Translation Contributor
- WordCamp Organizer
- WordCamp Speaker
-
Posted a reply to SCF custom fields disappearing when used as dynamic value in Divi5, on the site WordPress.org Forums:
I'm afraid that is not enough for us to debug. Can you please contact your… -
Posted a reply to SCF custom fields disappearing when used as dynamic value in Divi5, on the site WordPress.org Forums:
Hi there! Could you please share the entire error message? That way we can try… -
Wrote a comment on the post Block Bindings improvements in WordPress 6.9, on the site Make WordPress Core:
Hi there! The UI should appear every time a source is available for a compatible… -
Submitted pull request #73552 to WordPress/gutenberg:
Block Bindings: Remove caption from edit on `EditWithGeneratedProps`. -
Mentioned in [61288] on WordPress SVN:
Editor: Rename block visibility support key to `visibility`. -
Submitted pull request #253 to WordPress/secure-custom-fields:
Feature: Add binding connector to the site editor. -
Mentioned in [61285] on WordPress SVN:
Editor: Rename block visibility support key to `visibility`. -
Pull request #73481 merged into WordPress/gutenberg:
Active Templates: Remove duplicated inline script -
Closed issue #251 on the WordPress/secure-custom-fields repository:
SCF v6.6.0 Broke Free into ACF -
Submitted pull request #73481 to WordPress/gutenberg:
Active Templates: Remove duplicated inline script -
Translated 3 strings on translate.wordpress.org.
-
Closed pull request #249 on WordPress/secure-custom-fields:
Translations: Update pot file for .org translations. -
Suggested 12 strings on translate.wordpress.org.
-
Submitted pull request #249 to WordPress/secure-custom-fields:
Translations: Update pot file for .org translations. -
Submitted pull request #246 to WordPress/secure-custom-fields:
Release: Update stable tag to 6.6.0 -
Merged pull request #246 into WordPress/secure-custom-fields:
Release: Update stable tag to 6.6.0 -
Committed [3399031] to Plugins SVN:
Update stable tag to 6.6.0. -
Merged pull request #237 into WordPress/secure-custom-fields:
Prepare 6.6.0 Release -
Committed [3398869] to Plugins SVN:
Add 6.6.0 release tag. -
Created issue #73427 in the WordPress/gutenberg repository:
Release tooling: Cherry-pick script fails on line 71:14. -
Committed [3398367] to Plugins SVN:
JSON Schema: prevent fatal if schemas are missing. -
Merged pull request #245 into WordPress/secure-custom-fields:
Fix: Validate required JSON schemas before registering abilities -
Created issue #73403 in the WordPress/gutenberg repository:
Block Visibility attribute conflicts with Block Visibility plugin. -
Committed [3398154] to Plugins SVN:
Release 6.6.0 - Include schemas folder. -
Committed [3398130] to Plugins SVN:
Release: prepare 6.6.0 - Add blocks v3 JS files. - Add abilities ... -
Merged pull request #241 into WordPress/secure-custom-fields:
Blocks V3: Fix flexible content not working in sidebar - modal. -
Pull request #72585 merged into WordPress/gutenberg:
Block Bindings: Error handling for external sources. -
Wrote a comment on the post Block Bindings improvements in WordPress 6.9, on the site Make WordPress Core:
Partial syncing patters support blocks bindings, like the paragraph content. But if you connect them… -
Closed pull request #72663 on WordPress/gutenberg:
Block Bindings: Only show in the UI for sourced attributes. -
Closed pull request #72668 on WordPress/gutenberg:
Block Bindings: Use an attribute display to indicate UI behaviour. -
Closed pull request #72534 on WordPress/gutenberg:
Block Bindings: Set blocks as read-only UI. -
Closed pull request #67745 on WordPress/gutenberg:
Block Bindings: Use role content to enable block bindings attributes/ -
Merged pull request #243 into WordPress/secure-custom-fields:
Do not show the panel if there are no attributes (V3 blocks) -
Submitted pull request #243 to WordPress/secure-custom-fields:
Do not show the panel if there are no attributes (V3 blocks) -
Submitted pull request #241 to WordPress/secure-custom-fields:
Blocks V3: Fix flexible content not working in sidebar - modal. -
Committed [3395245] to Plugins SVN:
Prepare the 6.6.0 release. It still needs to add a couple of bug ... -
Submitted pull request #237 to WordPress/secure-custom-fields:
Prepare 6.6.0 Release -
Merged pull request #235 into WordPress/secure-custom-fields:
Blocks V3: Sidebar form disappeard when opened the modal. -
Submitted pull request #235 to WordPress/secure-custom-fields:
Blocks V3: Sidebar form disappeard when opened the modal. -
Merged pull request #229 into WordPress/secure-custom-fields:
Backports: Updates 6.6.0, 6.6.1, 6.6.2 -
Wrote a new post, Block Bindings improvements in WordPress 6.9, on the site Make WordPress Core:
For WordPress users. The Block Bindings user interface has been upgraded to improve how different… -
Merged pull request #230 into WordPress/secure-custom-fields:
Add props bot -
Submitted pull request #229 to WordPress/secure-custom-fields:
Backports: Updates 6.6.0, 6.6.1, 6.6.2 -
Pushed 1 commit to WordPress/WordPress:
Command Palette: Revert Use `HTLM_Tag_Processor` to get the menu label... -
Committed [61142] to Core SVN:
Command Palette: Revert Use `HTLM_Tag_Processor` to get the menu label ... -
Closed issue #72789 on the WordPress/gutenberg repository:
Gutenberg 22.0 release checklist -
Wrote a new post, What’s new in Gutenberg 22.0? (5 November), on the site Make WordPress Core:
“What’s new in Gutenberg…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg… -
Mentioned in [61127] on WordPress SVN:
Command Palette: Ensure `$menu_label` is initialized before using it. -
Mentioned in [61126] on WordPress SVN:
Command Palette: Use `HTML_Tag_Processor` to get the menu label when enqueueing assets, not regex. -
Submitted pull request #10461 to WordPress/wordpress-develop:
Command Palette: Use Tag processor instead of regex in the enqueue function.
