Release 1.11.0 - #811
Merged
Merged
Conversation
The 10up/action-wordpress-plugin-deploy action (v2.3.0) automatically checks for SVN availability and installs it if needed, making the explicit installation step unnecessary. This removes the redundancy and slightly improves workflow execution time.
Enable the "Live Preview" feature on WordPress.org by adding a blueprint configuration that demonstrates the liveblog plugin's key features. The blueprint creates a sports event scenario (Champions League Final) with: - Two reporter users for multi-author demonstration - Seven liveblog entries showing real-time coverage - Key events system with highlighted moments - Hashtags and rich HTML formatting - Landing page opens to the frontend to showcase the liveblog Inspired by Automattic/edit-flow#885. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The Liveblog metabox Enable/Archive buttons were non-functional in v1.10.0 because the admin JavaScript bundle was inadvertently excluded from the webpack build. The original implementation incorrectly referenced build/app.asset.php instead of the correct admin asset file. This commit renames src/dashboard to src/admin for consistency with WordPress terminology, updates the webpack entry point accordingly, and corrects the asset references in liveblog.php. Integration tests verify that the source file exists and the webpack configuration includes the admin entry point, which prevents regression of this issue. Fixes #804 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The "Visit the liveblog" link in the admin metabox was generating 404 errors when clicked on unpublished posts, as these posts don't yet have publicly accessible permalinks. This created confusion for editors working with draft liveblogs. Added a check for published status before including the permalink link in the metabox status messages. Unpublished posts now display the status text without the link, whilst published posts continue to show the clickable link. Also added proper URL escaping with esc_url() to improve security. Fixes #806 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The backend already supported a 'disable' state that removes liveblog post meta, but there was no UI to trigger it. Users could only enable or archive a liveblog, with no way to completely remove it from a post. This adds a Disable button to the metabox that: - Removes the liveblog meta from the post - Keeps existing entries as comments - Is disabled when there's no active liveblog Fixes #807 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add `liveblog_load_default_styles` filter that allows themes and plugins to disable the plugin's default CSS. This makes it easier for themes to provide their own styling for better visual integration. The filter applies to: - Admin styles (post editor metabox) - Frontend styles (liveblog display) - AMP styles Usage: ```php add_filter( 'liveblog_load_default_styles', '__return_false' ); ``` Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The previous code attempted to use wp_strip_all_tags() with an allowed tags parameter, but this function doesn't support that - its second parameter is $remove_breaks (boolean). The string was coerced to true, so all tags were stripped anyway, but not intentionally. This fix properly uses wp_strip_all_tags() without parameters to produce clean plain text titles for the key events widget. Images and other HTML content no longer leak into key event headings. Fixes #464 Co-Authored-By: cnaples79 <cnaples79@users.noreply.github.com> Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 1.11.0
Added
Fixed
See CHANGELOG.md for full details.