10up / block-catalog Goto Github PK
View Code? Open in Web Editor NEWEasily keep track of which Gutenberg Blocks are used across your WordPress site.
Home Page: https://wordpress.org/plugins/block-catalog/
License: GNU General Public License v2.0
Easily keep track of which Gutenberg Blocks are used across your WordPress site.
Home Page: https://wordpress.org/plugins/block-catalog/
License: GNU General Public License v2.0
More info: #10
There a few PHP Warnings in the plugin when running on PHP 8.2.
Deprecated: Optional parameter $sites declared before required parameter $opts is implicitly treated as a required parameter in /chroot/var/www/wp-content/plugins/block-catalog/includes/classes/CatalogCommand.php on line 410
Deprecated: Optional parameter $args declared before required parameter $opts is implicitly treated as a required parameter in /chroot/var/www/wp-content/plugins/block-catalog/includes/classes/CatalogCommand.php on line 431
wp --help
.No response
This issue is for tracking changes for the 1.5.2 release. Target release date: November 2023.
develop
, cut a release branch named release/1.5.2
for your changes.block-catalog.php
, package-lock.json
, package.json
, and readme.txt
if it does not already reflect the version being released. In block-catalog.php
update both the plugin "Version:" property and the plugin BLOCK_CATALOG_PLUGIN_VERSION
constant.CHANGELOG.md
and readme.txt
.CREDITS.md
file with any new contributors, confirm maintainers are accurate..gitattributes
.README.md
is geared toward GitHub and readme.txt
contains WordPress.org-specific content. The two are slightly different.develop
(or merge the pull request), then do the same for develop
into trunk
, ensuring you pull the most recent changes into develop
first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop
). trunk
contains the stable development version.git push origin trunk
).trunk
to develop
to ensure no additional changes were missed.trunk
branch. Paste the changelog from CHANGELOG.md
into the body of the release and include a link to the closed issues on the milestone.Due date (optional)
field) and link to GitHub release (in the Description field
), then close the milestone.1.5.1
do not make it into the release, update their milestone to 1.6.0
or Future Release
.This is to align with the current tooling versions used by WordPress - https://make.wordpress.org/core/2023/12/20/updating-wordpress-to-use-more-modern-versions-of-node-js-npm-2/
More info: #10
This issue is for tracking changes for the 1.5.4 release. Target release date: February 2024.
develop
, cut a release branch named release/1.5.4
for your changes.block-catalog.php
, package-lock.json
, package.json
, and readme.txt
if it does not already reflect the version being released. In block-catalog.php
update both the plugin "Version:" property and the plugin BLOCK_CATALOG_PLUGIN_VERSION
constant.CHANGELOG.md
and readme.txt
.CREDITS.md
file with any new contributors, confirm maintainers are accurate..gitattributes
.README.md
is geared toward GitHub and readme.txt
contains WordPress.org-specific content. The two are slightly different.develop
(or merge the pull request), then do the same for develop
into trunk
, ensuring you pull the most recent changes into develop
first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop
). trunk
contains the stable development version.git push origin trunk
).trunk
to develop
to ensure no additional changes were missed.trunk
branch. Paste the changelog from CHANGELOG.md
into the body of the release and include a link to the closed issues on the milestone.Due date (optional)
field) and link to GitHub release (in the Description field
), then close the milestone.1.5.4
do not make it into the release, update their milestone to 1.6.0
or Future Release
.More info: #10
There is a new WordPress version that the plugin hasn't been tested with. Please test it and then change the "Tested up to" field in the plugin readme.
Tested up to: 6.3
Latest version: 6.4
This issue will be closed automatically when the versions match.
Oddly, when viewing the catalog page (e.g. wp-admin/edit.php?block-catalog=core-preformatted) that contain a particular block, when that block is used as an inner block, that page is not listed in the GUI.
However, when using the wp block-catalog find
command, posts containing blocks that are used as inner blocks are returned in the results.
I am able to reproduce in both instances when the posts have published status or draft status.
<!-- wp:group {"layout":{"type":"flex","flexWrap":"nowrap"}} -->
<div class="wp-block-group"><!-- wp:paragraph -->
<p>this is an example of within a group block</p>
<!-- /wp:paragraph -->
<!-- wp:preformatted -->
<pre class="wp-block-preformatted">this is preformatted text within a group block</pre>
<!-- /wp:preformatted --></div>
<!-- /wp:group -->
n/a
gutenberg 15.8.1, WP 6.2.1
This issue is for tracking changes for the 1.6.1 release. Target release date: July 2024.
develop
, cut a release branch named release/1.6.1
for your changes.block-catalog.php
, package-lock.json
, package.json
, and readme.txt
if it does not already reflect the version being released. In block-catalog.php
update both the plugin "Version:" property and the plugin BLOCK_CATALOG_PLUGIN_VERSION
constant.CHANGELOG.md
and readme.txt
.CREDITS.md
file with any new contributors, confirm maintainers are accurate..gitattributes
.README.md
is geared toward GitHub and readme.txt
contains WordPress.org-specific content. The two are slightly different.develop
(or merge the pull request), then do the same for develop
into trunk
, ensuring you pull the most recent changes into develop
first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop
). trunk
contains the stable development version.git push origin trunk
).trunk
to develop
to ensure no additional changes were missed.trunk
branch. Paste the changelog from CHANGELOG.md
into the body of the release and include a link to the closed issues on the milestone.Due date (optional)
field) and link to GitHub release (in the Description field
), then close the milestone.1.6.1
do not make it into the release, update their milestone to 1.7.0
or Future Release
.I am running my site on PHP 8.2 with WP_DEBUG
set to true
. The error logs at the top of the screen flag the use of variables in strings.
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/www/html/wp-content/plugins/block-catalog/includes/core.php on line 166
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/www/html/wp-content/plugins/block-catalog/includes/core.php on line 184
No response
No response
WordPress 6.2.2
More info: #10
Is some kind of dashboard planned for a future release where a content editor can view all instances where a specific block is used, rather than relying on the post type/taxonomy screen?
No response
No response
This GitHub issue will serve as a task to prepare Critical Flow (also known as Test Cases) for this repository/plugin.
Please comment on this issue if you don't have:
There is an upcoming WordPress version in the release candidate stage that the plugin hasn't been tested with. Please test it and then change the "Tested up to" field in the plugin readme.
Tested up to: 6.5
Upcoming version: 6.6
This issue will be closed automatically when the versions match.
This issue is for tracking changes for the 1.5.1 release. Target release date: October 2023.
develop
, cut a release branch named release/1.5.1
for your changes.block-catalog.php
, package-lock.json
, package.json
, and readme.txt
if it does not already reflect the version being released. In block-catalog.php
update both the plugin "Version:" property and the plugin BLOCK_CATALOG_PLUGIN_VERSION
constant.CHANGELOG.md
and readme.txt
.CREDITS.md
file with any new contributors, confirm maintainers are accurate..gitattributes
.README.md
is geared toward GitHub and readme.txt
contains WordPress.org-specific content. The two are slightly different.develop
(or merge the pull request), then do the same for develop
into trunk
, ensuring you pull the most recent changes into develop
first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop
). trunk
contains the stable development version.git push origin trunk
).trunk
to develop
to ensure no additional changes were missed.trunk
branch. Paste the changelog from CHANGELOG.md
into the body of the release and include a link to the closed issues on the milestone.Due date (optional)
field) and link to GitHub release (in the Description field
), then close the milestone.1.5.1
do not make it into the release, update their milestone to 1.5.2
, 1.6.0
or Future Release
.This issue is for tracking changes for the 1.6.0 release. Target release date: May 2024.
develop
, cut a release branch named release/1.6.0
for your changes.block-catalog.php
, package-lock.json
, package.json
, and readme.txt
if it does not already reflect the version being released. In block-catalog.php
update both the plugin "Version:" property and the plugin BLOCK_CATALOG_PLUGIN_VERSION
constant.CHANGELOG.md
and readme.txt
.CREDITS.md
file with any new contributors, confirm maintainers are accurate..gitattributes
.README.md
is geared toward GitHub and readme.txt
contains WordPress.org-specific content. The two are slightly different.develop
(or merge the pull request), then do the same for develop
into trunk
, ensuring you pull the most recent changes into develop
first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop
). trunk
contains the stable development version.git push origin trunk
).trunk
to develop
to ensure no additional changes were missed.trunk
branch. Paste the changelog from CHANGELOG.md
into the body of the release and include a link to the closed issues on the milestone.Due date (optional)
field) and link to GitHub release (in the Description field
), then close the milestone.1.6.0
do not make it into the release, update their milestone to 1.7.0
or Future Release
.The current main PHP file is named plugin.php
whereas our OSS standard is to usually match the project name, in this case could/should be block-catalog.php
. So this issue documents the need to update the filename and any other references within the codebase.
n/a
n/a
This issue is for tracking changes for the 1.5.2 release. Target release date: November 2023.
develop
, cut a release branch named release/1.5.3
for your changes.block-catalog.php
, package-lock.json
, package.json
, and readme.txt
if it does not already reflect the version being released. In block-catalog.php
update both the plugin "Version:" property and the plugin BLOCK_CATALOG_PLUGIN_VERSION
constant.CHANGELOG.md
and readme.txt
.CREDITS.md
file with any new contributors, confirm maintainers are accurate..gitattributes
.README.md
is geared toward GitHub and readme.txt
contains WordPress.org-specific content. The two are slightly different.develop
(or merge the pull request), then do the same for develop
into trunk
, ensuring you pull the most recent changes into develop
first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop
). trunk
contains the stable development version.git push origin trunk
).trunk
to develop
to ensure no additional changes were missed.trunk
branch. Paste the changelog from CHANGELOG.md
into the body of the release and include a link to the closed issues on the milestone.Due date (optional)
field) and link to GitHub release (in the Description field
), then close the milestone.1.5.3
do not make it into the release, update their milestone to 1.6.0
or Future Release
.There is a new WordPress version that the plugin hasn't been tested with. Please test it and then change the "Tested up to" field in the plugin readme.
Tested up to: 6.4
Latest version: 6.5
This issue will be closed automatically when the versions match.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.