Tom Cafferkey
@tomjcafferkey on WordPress.org, @Tom Cafferkey on Slack
Bio
- Member Since: September 18th, 2020
- Location: Manchester, UK.
- Website: codebytom.blog
- GitHub: tjcafferkey
- Job Title: Software Engineer
- Employer: Automattic
Contribution History
Tom Cafferkey’s badges:- Core Contributor
-
Posted a reply to PTK Pattern Store, on the site WordPress.org Forums:
@telesante I have merged the PR above which should be released in WooCommerce 9.6 on… -
Posted a reply to PTK Pattern Store, on the site WordPress.org Forums:
Yeah that will be the cause. What is happening is that we are: Scheduling a… -
Posted a reply to PTK Pattern Store, on the site WordPress.org Forums:
@telesante I have proposed a change to improve the log warnings to only happen once… -
Posted a reply to PTK Pattern Store, on the site WordPress.org Forums:
@telesante could you possibly conduct this conflict test on a staging site, not your live… -
Posted a reply to PTK Pattern Store, on the site WordPress.org Forums:
I suspect you're getting this error because there is a plugin conflict. I notice in… -
Posted a reply to PTK Pattern Store, on the site WordPress.org Forums:
@telesante can you click "Edit" on the transient in Transient Manager and paste the full… -
Posted a reply to PTK Pattern Store, on the site WordPress.org Forums:
Thanks @telesante, can you please install the plugin Transient Manager (https://wordpress.org/plugins/transients-manager/) and in Tools >… -
Posted a reply to PTK Pattern Store, on the site WordPress.org Forums:
@telesante Could you please share a copy of your site’s System Status? You can find… -
Closed issue #51299 on the WordPress/gutenberg repository:
Query Pagination: Remove unwanted bottom margins from links -
Merged pull request #64874 into WordPress/gutenberg:
Pagination Block: Fix inconsistent margins between editor and frontend -
Submitted pull request #64874 to WordPress/gutenberg:
Pagination Block: Fix inconsistent margins between editor and frontend -
Submitted pull request #64141 to WordPress/gutenberg:
Zoom Out: Remove unlock() from getSettings -
Closed pull request #62732 on WordPress/gutenberg:
Block Hooks API: Update Template Part block for first and last child... -
Mentioned in [58614] on Core SVN:
Block Hooks: Allow child insertion into Template Part block. -
Mentioned in [58578] on Core SVN:
Block Hooks: Refactor controller filter to use meta_input. -
Created ticket #61495 on Core Trac:
Block Hooks: Refactor update_ignored_hooked_blocks_postmeta to use ... -
Submitted pull request #6885 to WordPress/wordpress-develop:
Refactor update_ignored_hooked_blocks_postmeta to use meta_input -
Submitted pull request #62732 to WordPress/gutenberg:
Block Hooks API: Update Template Part block for first and last child... -
Submitted pull request #6867 to WordPress/wordpress-develop:
Block Hooks API: Update block-template-utils for first-last child template parts -
Submitted pull request #62658 to WordPress/gutenberg:
Block Hooks API: Refactor Navigation to account for get_hooked_blocks_by_anchor_block -
Closed pull request #6233 on WordPress/wordpress-develop:
TT3: Wrap Navigation block in Row within the header.html template part -
Closed pull request #6234 on WordPress/wordpress-develop:
TT2: Wrap Navigation block in Row within the header.html template part -
Closed issue #62176 on the WordPress/gutenberg repository:
Parser: applyBlockValidation revalidating original block instead of fixed -
Mentioned in [58291] on Core SVN:
Block Hooks: Move ignoredHookedBlocks metadata injection logic. -
Submitted pull request #62178 to WordPress/gutenberg:
Parser: Update validateBlock to use fixedBlock -
Created issue #62176 in the WordPress/gutenberg repository:
Parser: applyBlockValidation revalidating original block instead of fixed -
Closed pull request #6550 on WordPress/wordpress-develop:
Block Hooks API: Harmonize ignoredHookedBlocks metadata injection logic -
Pull request #61903 merged into WordPress/gutenberg:
Navigation block: Check for update_ignored_hooked_blocks_postmeta in core -
Mentioned in [58186] on Core SVN:
Block Hooks API: Insert metadata at the same time as hooked blocks. -
Submitted pull request #61903 to WordPress/gutenberg:
Navigation block: Check for update_ignored_hooked_blocks_postmeta in core -
Submitted pull request #61864 to WordPress/gutenberg:
Block variations: Add block-supports flag to add variation specific classname -
Submitted pull request #6604 to WordPress/wordpress-develop:
Block Hooks API: Move ignoredHookedBlocks metadata injection logic -
Submitted pull request #6584 to WordPress/wordpress-develop:
Block Hooks API: Consolidate approach to get all hooked blocks -
Submitted pull request #6582 to WordPress/wordpress-develop:
Block API: Render alias block with canonical block class name -
Submitted pull request #6580 to WordPress/wordpress-develop:
Block API: Set alias_name on block class instances. -
Submitted pull request #6555 to WordPress/wordpress-develop:
Try: Render variation alias blocks -
Submitted pull request #6550 to WordPress/wordpress-develop:
Block Hooks API: Harmonize ignoredHookedBlocks metadata injection logic -
Closed pull request #6471 on WordPress/wordpress-develop:
Block API: Register alias block on server -
Closed pull request #61279 on WordPress/gutenberg:
Block API: Register alias blocks as standalone block types on the client -
Submitted pull request #61481 to WordPress/gutenberg:
Block API: Convert block alias into canonical block (PoC) -
Submitted pull request #6523 to WordPress/wordpress-develop:
Block API: Add support for block aliases (PoC) -
Submitted pull request #6471 to WordPress/wordpress-develop:
Block API: Register alias block on server -
Submitted pull request #61279 to WordPress/gutenberg:
Block API: Register alias blocks as standalone block types on the client -
Mentioned in [58041] on Core SVN:
Block Hooks: Pass correct context to filters. -
Mentioned in [58034] on Core SVN:
Twenty Twenty-Three: Wraps navigation block in row within header template part. -
Mentioned in [58004] on Core SVN:
Twenty Twenty Two: Wraps Navigation block in row. -
Submitted pull request #6358 to WordPress/wordpress-develop:
Block Hooks API: Insert metadata at the same time as hooked blocks -
Mentioned in [57919] on Core SVN:
Block Hooks: Pass correct context to filters. -
Submitted pull request #6330 to WordPress/wordpress-develop:
Block Hooks API: Add ignoredHookedBlocks meta when preparing REST API response -
Created issue #649 in the WordPress/pattern-directory repository:
Pattern update: Simple header with dark background