diff --git a/.github/workflows/tests-php-eva.yml b/.github/workflows/tests-php-eva.yml new file mode 100644 index 0000000000..c5e7d40a0f --- /dev/null +++ b/.github/workflows/tests-php-eva.yml @@ -0,0 +1,283 @@ +name: 'EVA Codeception Tests' +on: [ pull_request ] +jobs: + test: + strategy: + matrix: + suite: [ eva_integration, restv1, restv1_et, end2end ] + runs-on: ubuntu-latest + steps: + # ------------------------------------------------------------------------------ + # Checkout the repo + # ------------------------------------------------------------------------------ + - name: Checkout the repository + uses: actions/checkout@v2 + with: + fetch-depth: 1000 + token: ${{ secrets.GH_BOT_TOKEN }} + submodules: recursive + # ------------------------------------------------------------------------------ + # Check if any PHP files have changed + # ------------------------------------------------------------------------------ + - name: Check changed files + id: skip + run: | + num_php_files=$(git diff ${{ github.event.pull_request.base.sha }} HEAD --name-only | grep -P "\.php" | wc -l) + if [[ -z "$num_php_files" ]]; then + echo "::set-output name=value::1" + elif [[ "$num_php_files" == "0" || "$num_php_files" == "" ]]; then + echo "::set-output name=value::1" + else + echo "::set-output name=value::0" + fi + # ------------------------------------------------------------------------------ + # Checkout slic + # ------------------------------------------------------------------------------ + - name: Checkout slic + uses: actions/checkout@v2 + if: steps.skip.outputs.value != 1 + with: + repository: stellarwp/slic + ref: main + path: slic + fetch-depth: 1 + # ------------------------------------------------------------------------------ + # Prepare our composer cache directory + # ------------------------------------------------------------------------------ + - name: Get Composer Cache Directory + id: get-composer-cache-dir + if: steps.skip.outputs.value != 1 + run: | + echo "::set-output name=dir::$(composer config cache-files-dir)" + - uses: actions/cache@v2 + id: composer-cache + if: steps.skip.outputs.value != 1 + with: + path: ${{ steps.get-composer-cache-dir.outputs.dir }} + key: ${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }} + restore-keys: | + ${{ runner.os }}-composer- + # ------------------------------------------------------------------------------ + # Initialize slic + # ------------------------------------------------------------------------------ + - name: Move slic directory up + if: steps.skip.outputs.value != 1 + run: | + mv slic ./../slic + - name: Set up slic env vars + if: steps.skip.outputs.value != 1 + run: | + echo "SLIC_COMPOSER_VERSION=2" >> $GITHUB_ENV + echo "SLIC_BIN=${GITHUB_WORKSPACE}/../slic/slic" >> $GITHUB_ENV + echo "SLIC_WP_DIR=${GITHUB_WORKSPACE}/../slic/_wordpress" >> $GITHUB_ENV + - name: Set run context for slic + if: steps.skip.outputs.value != 1 + run: echo "SLIC=1" >> $GITHUB_ENV && echo "CI=1" >> $GITHUB_ENV + - name: Start ssh-agent + if: steps.skip.outputs.value != 1 + run: | + mkdir -p "${HOME}/.ssh"; + ssh-agent -a /tmp/ssh_agent.sock; + - name: Export SSH_AUTH_SOCK env var + if: steps.skip.outputs.value != 1 + run: echo "SSH_AUTH_SOCK=/tmp/ssh_agent.sock" >> $GITHUB_ENV + - name: Set up slic for CI + if: steps.skip.outputs.value != 1 + run: | + cd ${GITHUB_WORKSPACE}/.. + ${SLIC_BIN} here + ${SLIC_BIN} interactive off + ${SLIC_BIN} build-prompt off + ${SLIC_BIN} build-subdir off + ${SLIC_BIN} xdebug off + ${SLIC_BIN} composer-cache set /home/runner/.cache/composer + ${SLIC_BIN} debug on + ${SLIC_BIN} info + ${SLIC_BIN} config + # ------------------------------------------------------------------------------ + # Fetch branches for dependent repos + # ------------------------------------------------------------------------------ + - name: Fetch head branch from TEC + uses: octokit/request-action@v2.x + if: steps.skip.outputs.value != 1 + id: fetch-tec-head-branch + with: + route: GET /repos/{owner}/{repo}/branches/${{ github.head_ref }} + owner: the-events-calendar + repo: the-events-calendar + env: + GITHUB_TOKEN: ${{ secrets.GH_BOT_TOKEN }} + continue-on-error: true + - name: Fetch base branch from TEC + uses: octokit/request-action@v2.x + id: fetch-tec-base-branch + if: steps.skip.outputs.value != 1 && steps.fetch-tec-head-branch.outcome != 'success' + with: + route: GET /repos/{owner}/{repo}/branches/${{ github.base_ref }} + owner: the-events-calendar + repo: the-events-calendar + env: + GITHUB_TOKEN: ${{ secrets.GH_BOT_TOKEN }} + continue-on-error: true + - name: Fetch head branch from ET + uses: octokit/request-action@v2.x + id: fetch-et-head-branch + if: steps.skip.outputs.value != 1 + with: + route: GET /repos/{owner}/{repo}/branches/${{ github.head_ref }} + owner: the-events-calendar + repo: event-tickets + env: + GITHUB_TOKEN: ${{ secrets.GH_BOT_TOKEN }} + continue-on-error: true + - name: Fetch base branch from ET + uses: octokit/request-action@v2.x + id: fetch-et-base-branch + if: steps.skip.outputs.value != 1 && steps.fetch-et-head-branch.outcome != 'success' + with: + route: GET /repos/{owner}/{repo}/branches/${{ github.base_ref }} + owner: the-events-calendar + repo: event-tickets + env: + GITHUB_TOKEN: ${{ secrets.GH_BOT_TOKEN }} + continue-on-error: true + # ------------------------------------------------------------------------------ + # Set TEC branch + # ------------------------------------------------------------------------------ + - name: Set TEC with head branch + if: steps.skip.outputs.value != 1 && steps.fetch-tec-head-branch.outcome == 'success' + run: echo "TEC_BRANCH=${{ github.head_ref }}" >> $GITHUB_ENV + - name: Set TEC with base branch + if: steps.skip.outputs.value != 1 && steps.fetch-tec-head-branch.outcome != 'success' && steps.fetch-tec-base-branch.outcome == 'success' + run: echo "TEC_BRANCH=${{ github.base_ref }}" >> $GITHUB_ENV + - name: Set TEC with master branch + if: steps.skip.outputs.value != 1 && steps.fetch-tec-head-branch.outcome != 'success' && steps.fetch-tec-base-branch.outcome != 'success' + run: echo "TEC_BRANCH=master" >> $GITHUB_ENV + # ------------------------------------------------------------------------------ + # Set ET branch + # ------------------------------------------------------------------------------ + - name: Set ET with head branch + if: steps.skip.outputs.value != 1 && steps.fetch-et-head-branch.outcome == 'success' + run: echo "ET_BRANCH=${{ github.head_ref }}" >> $GITHUB_ENV + - name: Set ET with base branch + if: steps.skip.outputs.value != 1 && steps.fetch-et-head-branch.outcome != 'success' && steps.fetch-et-base-branch.outcome == 'success' + run: echo "ET_BRANCH=${{ github.base_ref }}" >> $GITHUB_ENV + - name: Set ET with master branch + if: steps.skip.outputs.value != 1 && steps.fetch-et-head-branch.outcome != 'success' && steps.fetch-et-base-branch.outcome != 'success' + run: echo "ET_BRANCH=master" >> $GITHUB_ENV + # ------------------------------------------------------------------------------ + # Set ET+ branch + # ------------------------------------------------------------------------------ + - name: Set ET+ with head branch + if: steps.skip.outputs.value != 1 && steps.fetch-et-plus-head-branch.outcome == 'success' + run: echo "ET_PLUS_BRANCH=${{ github.head_ref }}" >> $GITHUB_ENV + - name: Set ET+ with base branch + if: steps.skip.outputs.value != 1 && steps.fetch-et-plus-head-branch.outcome != 'success' && steps.fetch-et-plus-base-branch.outcome == 'success' + run: echo "ET_PLUS_BRANCH=${{ github.base_ref }}" >> $GITHUB_ENV + - name: Set ET+ with master branch + if: steps.skip.outputs.value != 1 && steps.fetch-et-plus-head-branch.outcome != 'success' && steps.fetch-et-plus-base-branch.outcome != 'success' + run: echo "ET_PLUS_BRANCH=master" >> $GITHUB_ENV + # ------------------------------------------------------------------------------ + # Clone and init TEC + # ------------------------------------------------------------------------------ + - name: Clone TEC + uses: actions/checkout@v2 + if: steps.skip.outputs.value != 1 + with: + fetch-depth: 1 + repository: the-events-calendar/the-events-calendar + ref: ${{ env.TEC_BRANCH }} + token: ${{ secrets.GH_BOT_TOKEN }} + path: the-events-calendar + submodules: recursive + - name: Init TEC + if: steps.skip.outputs.value != 1 + run: | + mv ${GITHUB_WORKSPACE}/the-events-calendar ${GITHUB_WORKSPACE}/../the-events-calendar + docker network prune -f + ${SLIC_BIN} use the-events-calendar + ${SLIC_BIN} composer install --no-dev + # ------------------------------------------------------------------------------ + # Clone and init ET + # ------------------------------------------------------------------------------ + - name: Clone ET + uses: actions/checkout@v2 + if: steps.skip.outputs.value != 1 + with: + fetch-depth: 1 + repository: the-events-calendar/event-tickets + ref: ${{ env.ET_BRANCH }} + token: ${{ secrets.GH_BOT_TOKEN }} + path: event-tickets + submodules: recursive + - name: Init ET + if: steps.skip.outputs.value != 1 + run: | + mv ${GITHUB_WORKSPACE}/event-tickets ${GITHUB_WORKSPACE}/../event-tickets + docker network prune -f + ${SLIC_BIN} use event-tickets + ${SLIC_BIN} composer install --no-dev + - name: Set up Common + if: steps.skip.outputs.value != 1 + run: | + docker network prune -f + ${SLIC_BIN} use event-tickets/common + ${SLIC_BIN} composer install --no-dev + # ------------------------------------------------------------------------------ + # Clone and init ET+ + # ------------------------------------------------------------------------------ + - name: Clone ET+ + uses: actions/checkout@v2 + if: steps.skip.outputs.value != 1 + with: + fetch-depth: 1 + repository: the-events-calendar/event-tickets-plus + ref: ${{ env.ET_PLUS_BRANCH }} + token: ${{ secrets.GH_BOT_TOKEN }} + path: event-tickets-plus + submodules: recursive + - name: Init ET + if: steps.skip.outputs.value != 1 + run: | + mv ${GITHUB_WORKSPACE}/event-tickets-plus ${GITHUB_WORKSPACE}/../event-tickets-plus + docker network prune -f + ${SLIC_BIN} use event-tickets-plus + ${SLIC_BIN} composer install --no-dev + # ------------------------------------------------------------------------------ + # Install and activate WooCommerce + # ------------------------------------------------------------------------------ + - name: Install WooCommerce + if: steps.skip.outputs.value != 1 + run: ${SLIC_BIN} site-cli plugin install woocommerce --version='8.2.2' + # ------------------------------------------------------------------------------ + # Install and activate Easy Digital Downloads + # ------------------------------------------------------------------------------ + - name: Install Easy Digital Downloads + if: steps.skip.outputs.value != 1 + run: ${SLIC_BIN} site-cli plugin install easy-digital-downloads + # ------------------------------------------------------------------------------ + # Set up Common + # ------------------------------------------------------------------------------ + - name: Move Common inside TEC + if: steps.skip.outputs.value != 1 + run: | + rm -rf ${GITHUB_WORKSPACE}/../the-events-calendar/common + cp -r ${GITHUB_WORKSPACE} ${GITHUB_WORKSPACE}/../the-events-calendar/common + # ------------------------------------------------------------------------------ + # Set up Common and run tests + # ------------------------------------------------------------------------------ + - name: Set up Common + if: steps.skip.outputs.value != 1 + run: | + ${SLIC_BIN} use the-events-calendar/common + ${SLIC_BIN} composer install + - name: Init the WordPress container + if: steps.skip.outputs.value != 1 + run: | + ${SLIC_BIN} up wordpress + ${SLIC_BIN} wp core version + ${SLIC_BIN} wp core update --force --version=6.4.1 + ${SLIC_BIN} wp core version + - name: Run suite tests + if: steps.skip.outputs.value != 1 + run: ${SLIC_BIN} run ${{ matrix.suite }} --debug --ext DotReporter diff --git a/.github/workflows/tests-php.yml b/.github/workflows/tests-php.yml index 9bfa7119f0..f5ebf018f4 100644 --- a/.github/workflows/tests-php.yml +++ b/.github/workflows/tests-php.yml @@ -175,7 +175,7 @@ jobs: run: | ${SLIC_BIN} up wordpress ${SLIC_BIN} wp core version - ${SLIC_BIN} wp core update --force --version=6.3.1 + ${SLIC_BIN} wp core update --force --version=6.4.1 ${SLIC_BIN} wp core version - name: Run suite tests if: steps.skip.outputs.value != 1 diff --git a/composer.lock b/composer.lock index 415ce03047..e4d9ce1a50 100644 --- a/composer.lock +++ b/composer.lock @@ -70,16 +70,16 @@ }, { "name": "lucatume/di52", - "version": "3.3.5", + "version": "3.3.7", "source": { "type": "git", "url": "https://github.com/lucatume/di52.git", - "reference": "d39d1cbbc57eb41c7aa21fab106e17b6938ec6b3" + "reference": "76c0c2ad0422ce595e2e38138456f3475888e32c" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/lucatume/di52/zipball/d39d1cbbc57eb41c7aa21fab106e17b6938ec6b3", - "reference": "d39d1cbbc57eb41c7aa21fab106e17b6938ec6b3", + "url": "https://api.github.com/repos/lucatume/di52/zipball/76c0c2ad0422ce595e2e38138456f3475888e32c", + "reference": "76c0c2ad0422ce595e2e38138456f3475888e32c", "shasum": "" }, "require": { @@ -109,9 +109,9 @@ "description": "A PHP 5.6 compatible dependency injection container.", "support": { "issues": "https://github.com/lucatume/di52/issues", - "source": "https://github.com/lucatume/di52/tree/3.3.5" + "source": "https://github.com/lucatume/di52/tree/3.3.7" }, - "time": "2023-09-01T08:49:32+00:00" + "time": "2024-04-26T14:46:26+00:00" }, { "name": "monolog/monolog", @@ -455,12 +455,12 @@ "source": { "type": "git", "url": "https://github.com/stellarwp/models.git", - "reference": "1e364cc54883ac43fc25f7fce652259439af0a89" + "reference": "7c21d232c06a6670e5845570945791f2887ead48" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/stellarwp/models/zipball/1e364cc54883ac43fc25f7fce652259439af0a89", - "reference": "1e364cc54883ac43fc25f7fce652259439af0a89", + "url": "https://api.github.com/repos/stellarwp/models/zipball/7c21d232c06a6670e5845570945791f2887ead48", + "reference": "7c21d232c06a6670e5845570945791f2887ead48", "shasum": "" }, "require": { @@ -502,9 +502,9 @@ ], "support": { "issues": "https://github.com/stellarwp/models/issues", - "source": "https://github.com/stellarwp/models/tree/1.2.1" + "source": "https://github.com/stellarwp/models/tree/main" }, - "time": "2023-09-12T15:59:24+00:00" + "time": "2024-05-10T21:20:20+00:00" }, { "name": "stellarwp/schema", @@ -666,32 +666,32 @@ }, { "name": "automattic/vipwpcs", - "version": "3.0.0", + "version": "3.0.1", "source": { "type": "git", "url": "https://github.com/Automattic/VIP-Coding-Standards.git", - "reference": "1b8960ebff9ea3eb482258a906ece4d1ee1e25fd" + "reference": "2b1d206d81b74ed999023cffd924f862ff2753c8" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/Automattic/VIP-Coding-Standards/zipball/1b8960ebff9ea3eb482258a906ece4d1ee1e25fd", - "reference": "1b8960ebff9ea3eb482258a906ece4d1ee1e25fd", + "url": "https://api.github.com/repos/Automattic/VIP-Coding-Standards/zipball/2b1d206d81b74ed999023cffd924f862ff2753c8", + "reference": "2b1d206d81b74ed999023cffd924f862ff2753c8", "shasum": "" }, "require": { "php": ">=5.4", - "phpcsstandards/phpcsextra": "^1.1.0", - "phpcsstandards/phpcsutils": "^1.0.8", - "sirbrillig/phpcs-variable-analysis": "^2.11.17", - "squizlabs/php_codesniffer": "^3.7.2", - "wp-coding-standards/wpcs": "^3.0" + "phpcsstandards/phpcsextra": "^1.2.1", + "phpcsstandards/phpcsutils": "^1.0.11", + "sirbrillig/phpcs-variable-analysis": "^2.11.18", + "squizlabs/php_codesniffer": "^3.9.2", + "wp-coding-standards/wpcs": "^3.1.0" }, "require-dev": { "php-parallel-lint/php-console-highlighter": "^1.0.0", "php-parallel-lint/php-parallel-lint": "^1.3.2", "phpcompatibility/php-compatibility": "^9", "phpcsstandards/phpcsdevtools": "^1.0", - "phpunit/phpunit": "^4 || ^5 || ^6 || ^7" + "phpunit/phpunit": "^4 || ^5 || ^6 || ^7 || ^8 || ^9" }, "type": "phpcodesniffer-standard", "notification-url": "https://packagist.org/downloads/", @@ -716,7 +716,7 @@ "source": "https://github.com/Automattic/VIP-Coding-Standards", "wiki": "https://github.com/Automattic/VIP-Coding-Standards/wiki" }, - "time": "2023-09-05T11:01:05+00:00" + "time": "2024-05-10T20:31:09+00:00" }, { "name": "behat/gherkin", @@ -2807,22 +2807,22 @@ }, { "name": "phpcsstandards/phpcsutils", - "version": "1.0.10", + "version": "1.0.12", "source": { "type": "git", "url": "https://github.com/PHPCSStandards/PHPCSUtils.git", - "reference": "51609a5b89f928e0c463d6df80eb38eff1eaf544" + "reference": "87b233b00daf83fb70f40c9a28692be017ea7c6c" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/PHPCSStandards/PHPCSUtils/zipball/51609a5b89f928e0c463d6df80eb38eff1eaf544", - "reference": "51609a5b89f928e0c463d6df80eb38eff1eaf544", + "url": "https://api.github.com/repos/PHPCSStandards/PHPCSUtils/zipball/87b233b00daf83fb70f40c9a28692be017ea7c6c", + "reference": "87b233b00daf83fb70f40c9a28692be017ea7c6c", "shasum": "" }, "require": { "dealerdirect/phpcodesniffer-composer-installer": "^0.4.1 || ^0.5 || ^0.6.2 || ^0.7 || ^1.0", "php": ">=5.4", - "squizlabs/php_codesniffer": "^3.9.0 || 4.0.x-dev@dev" + "squizlabs/php_codesniffer": "^3.10.0 || 4.0.x-dev@dev" }, "require-dev": { "ext-filter": "*", @@ -2891,7 +2891,7 @@ "type": "open_collective" } ], - "time": "2024-03-17T23:44:50+00:00" + "time": "2024-05-20T13:34:27+00:00" }, { "name": "phpdocumentor/reflection-common", @@ -2948,28 +2948,35 @@ }, { "name": "phpdocumentor/reflection-docblock", - "version": "5.3.0", + "version": "5.4.1", "source": { "type": "git", "url": "https://github.com/phpDocumentor/ReflectionDocBlock.git", - "reference": "622548b623e81ca6d78b721c5e029f4ce664f170" + "reference": "9d07b3f7fdcf5efec5d1609cba3c19c5ea2bdc9c" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/phpDocumentor/ReflectionDocBlock/zipball/622548b623e81ca6d78b721c5e029f4ce664f170", - "reference": "622548b623e81ca6d78b721c5e029f4ce664f170", + "url": "https://api.github.com/repos/phpDocumentor/ReflectionDocBlock/zipball/9d07b3f7fdcf5efec5d1609cba3c19c5ea2bdc9c", + "reference": "9d07b3f7fdcf5efec5d1609cba3c19c5ea2bdc9c", "shasum": "" }, "require": { + "doctrine/deprecations": "^1.1", "ext-filter": "*", - "php": "^7.2 || ^8.0", + "php": "^7.4 || ^8.0", "phpdocumentor/reflection-common": "^2.2", - "phpdocumentor/type-resolver": "^1.3", + "phpdocumentor/type-resolver": "^1.7", + "phpstan/phpdoc-parser": "^1.7", "webmozart/assert": "^1.9.1" }, "require-dev": { - "mockery/mockery": "~1.3.2", - "psalm/phar": "^4.8" + "mockery/mockery": "~1.3.5", + "phpstan/extension-installer": "^1.1", + "phpstan/phpstan": "^1.8", + "phpstan/phpstan-mockery": "^1.1", + "phpstan/phpstan-webmozart-assert": "^1.2", + "phpunit/phpunit": "^9.5", + "vimeo/psalm": "^5.13" }, "type": "library", "extra": { @@ -2993,15 +3000,15 @@ }, { "name": "Jaap van Otterdijk", - "email": "account@ijaap.nl" + "email": "opensource@ijaap.nl" } ], "description": "With this component, a library can provide support for annotations via DocBlocks or otherwise retrieve information that is embedded in a DocBlock.", "support": { "issues": "https://github.com/phpDocumentor/ReflectionDocBlock/issues", - "source": "https://github.com/phpDocumentor/ReflectionDocBlock/tree/5.3.0" + "source": "https://github.com/phpDocumentor/ReflectionDocBlock/tree/5.4.1" }, - "time": "2021-10-19T17:43:47+00:00" + "time": "2024-05-21T05:55:05+00:00" }, { "name": "phpdocumentor/type-resolver", @@ -3132,16 +3139,16 @@ }, { "name": "phpstan/phpdoc-parser", - "version": "1.26.0", + "version": "1.29.0", "source": { "type": "git", "url": "https://github.com/phpstan/phpdoc-parser.git", - "reference": "231e3186624c03d7e7c890ec662b81e6b0405227" + "reference": "536889f2b340489d328f5ffb7b02bb6b183ddedc" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/phpstan/phpdoc-parser/zipball/231e3186624c03d7e7c890ec662b81e6b0405227", - "reference": "231e3186624c03d7e7c890ec662b81e6b0405227", + "url": "https://api.github.com/repos/phpstan/phpdoc-parser/zipball/536889f2b340489d328f5ffb7b02bb6b183ddedc", + "reference": "536889f2b340489d328f5ffb7b02bb6b183ddedc", "shasum": "" }, "require": { @@ -3173,9 +3180,9 @@ "description": "PHPDoc parser with support for nullable, intersection and generic types", "support": { "issues": "https://github.com/phpstan/phpdoc-parser/issues", - "source": "https://github.com/phpstan/phpdoc-parser/tree/1.26.0" + "source": "https://github.com/phpstan/phpdoc-parser/tree/1.29.0" }, - "time": "2024-02-23T16:05:55+00:00" + "time": "2024-05-06T12:04:23+00:00" }, { "name": "phpunit/php-code-coverage", @@ -4417,16 +4424,16 @@ }, { "name": "sirbrillig/phpcs-variable-analysis", - "version": "v2.11.17", + "version": "v2.11.18", "source": { "type": "git", "url": "https://github.com/sirbrillig/phpcs-variable-analysis.git", - "reference": "3b71162a6bf0cde2bff1752e40a1788d8273d049" + "reference": "ca242a0b7309e0f9d1f73b236e04ecf4ca3248d0" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/sirbrillig/phpcs-variable-analysis/zipball/3b71162a6bf0cde2bff1752e40a1788d8273d049", - "reference": "3b71162a6bf0cde2bff1752e40a1788d8273d049", + "url": "https://api.github.com/repos/sirbrillig/phpcs-variable-analysis/zipball/ca242a0b7309e0f9d1f73b236e04ecf4ca3248d0", + "reference": "ca242a0b7309e0f9d1f73b236e04ecf4ca3248d0", "shasum": "" }, "require": { @@ -4471,7 +4478,7 @@ "source": "https://github.com/sirbrillig/phpcs-variable-analysis", "wiki": "https://github.com/sirbrillig/phpcs-variable-analysis/wiki" }, - "time": "2023-08-05T23:46:11+00:00" + "time": "2024-04-13T16:42:46+00:00" }, { "name": "slevomat/coding-standard", @@ -4540,16 +4547,16 @@ }, { "name": "squizlabs/php_codesniffer", - "version": "3.9.0", + "version": "3.10.1", "source": { "type": "git", "url": "https://github.com/PHPCSStandards/PHP_CodeSniffer.git", - "reference": "d63cee4890a8afaf86a22e51ad4d97c91dd4579b" + "reference": "8f90f7a53ce271935282967f53d0894f8f1ff877" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/PHPCSStandards/PHP_CodeSniffer/zipball/d63cee4890a8afaf86a22e51ad4d97c91dd4579b", - "reference": "d63cee4890a8afaf86a22e51ad4d97c91dd4579b", + "url": "https://api.github.com/repos/PHPCSStandards/PHP_CodeSniffer/zipball/8f90f7a53ce271935282967f53d0894f8f1ff877", + "reference": "8f90f7a53ce271935282967f53d0894f8f1ff877", "shasum": "" }, "require": { @@ -4616,7 +4623,7 @@ "type": "open_collective" } ], - "time": "2024-02-16T15:06:51+00:00" + "time": "2024-05-22T21:24:41+00:00" }, { "name": "stellarwp/coding-standards", @@ -4903,16 +4910,16 @@ }, { "name": "symfony/deprecation-contracts", - "version": "v2.5.2", + "version": "v2.5.3", "source": { "type": "git", "url": "https://github.com/symfony/deprecation-contracts.git", - "reference": "e8b495ea28c1d97b5e0c121748d6f9b53d075c66" + "reference": "80d075412b557d41002320b96a096ca65aa2c98d" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/symfony/deprecation-contracts/zipball/e8b495ea28c1d97b5e0c121748d6f9b53d075c66", - "reference": "e8b495ea28c1d97b5e0c121748d6f9b53d075c66", + "url": "https://api.github.com/repos/symfony/deprecation-contracts/zipball/80d075412b557d41002320b96a096ca65aa2c98d", + "reference": "80d075412b557d41002320b96a096ca65aa2c98d", "shasum": "" }, "require": { @@ -4950,7 +4957,7 @@ "description": "A generic function and convention to trigger deprecation notices", "homepage": "https://symfony.com", "support": { - "source": "https://github.com/symfony/deprecation-contracts/tree/v2.5.2" + "source": "https://github.com/symfony/deprecation-contracts/tree/v2.5.3" }, "funding": [ { @@ -4966,7 +4973,7 @@ "type": "tidelift" } ], - "time": "2022-01-02T09:53:40+00:00" + "time": "2023-01-24T14:02:46+00:00" }, { "name": "symfony/dom-crawler", @@ -5884,16 +5891,16 @@ }, { "name": "symfony/service-contracts", - "version": "v2.5.2", + "version": "v2.5.3", "source": { "type": "git", "url": "https://github.com/symfony/service-contracts.git", - "reference": "4b426aac47d6427cc1a1d0f7e2ac724627f5966c" + "reference": "a2329596ddc8fd568900e3fc76cba42489ecc7f3" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/symfony/service-contracts/zipball/4b426aac47d6427cc1a1d0f7e2ac724627f5966c", - "reference": "4b426aac47d6427cc1a1d0f7e2ac724627f5966c", + "url": "https://api.github.com/repos/symfony/service-contracts/zipball/a2329596ddc8fd568900e3fc76cba42489ecc7f3", + "reference": "a2329596ddc8fd568900e3fc76cba42489ecc7f3", "shasum": "" }, "require": { @@ -5947,7 +5954,7 @@ "standards" ], "support": { - "source": "https://github.com/symfony/service-contracts/tree/v2.5.2" + "source": "https://github.com/symfony/service-contracts/tree/v2.5.3" }, "funding": [ { @@ -5963,7 +5970,7 @@ "type": "tidelift" } ], - "time": "2022-05-30T19:17:29+00:00" + "time": "2023-04-21T15:04:16+00:00" }, { "name": "symfony/translation", @@ -6062,16 +6069,16 @@ }, { "name": "symfony/translation-contracts", - "version": "v2.5.2", + "version": "v2.5.3", "source": { "type": "git", "url": "https://github.com/symfony/translation-contracts.git", - "reference": "136b19dd05cdf0709db6537d058bcab6dd6e2dbe" + "reference": "b0073a77ac0b7ea55131020e87b1e3af540f4664" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/symfony/translation-contracts/zipball/136b19dd05cdf0709db6537d058bcab6dd6e2dbe", - "reference": "136b19dd05cdf0709db6537d058bcab6dd6e2dbe", + "url": "https://api.github.com/repos/symfony/translation-contracts/zipball/b0073a77ac0b7ea55131020e87b1e3af540f4664", + "reference": "b0073a77ac0b7ea55131020e87b1e3af540f4664", "shasum": "" }, "require": { @@ -6120,7 +6127,7 @@ "standards" ], "support": { - "source": "https://github.com/symfony/translation-contracts/tree/v2.5.2" + "source": "https://github.com/symfony/translation-contracts/tree/v2.5.3" }, "funding": [ { @@ -6136,7 +6143,7 @@ "type": "tidelift" } ], - "time": "2022-06-27T16:58:25+00:00" + "time": "2024-01-23T13:51:25+00:00" }, { "name": "symfony/yaml", @@ -6215,22 +6222,22 @@ "source": { "type": "git", "url": "https://github.com/the-events-calendar/tec-testing-facilities.git", - "reference": "6c66235042c4389079a0c98ff8e70ad0ac227eb0" + "reference": "0b5909300805b8844ce4720cee72ea7389eb2e58" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/the-events-calendar/tec-testing-facilities/zipball/6c66235042c4389079a0c98ff8e70ad0ac227eb0", - "reference": "6c66235042c4389079a0c98ff8e70ad0ac227eb0", + "url": "https://api.github.com/repos/the-events-calendar/tec-testing-facilities/zipball/0b5909300805b8844ce4720cee72ea7389eb2e58", + "reference": "0b5909300805b8844ce4720cee72ea7389eb2e58", "shasum": "" }, "require": { "lucatume/wp-browser": "^2.0 || ^3.0", "nilportugues/sql-query-formatter": "^1.2", - "php": ">=7.0" + "php": ">=7.4" }, "require-dev": { "codeception/codeception": "^3.0", - "dealerdirect/phpcodesniffer-composer-installer": "^0.5.0", + "dealerdirect/phpcodesniffer-composer-installer": "^0.7.2", "phpunit/phpunit": "^6.0", "vlucas/phpdotenv": "^3.0", "wordpress/wordpress": "dev-master", @@ -6261,7 +6268,7 @@ "issues": "https://github.com/the-events-calendar/tec-testing-facilities/issues", "source": "https://github.com/the-events-calendar/tec-testing-facilities/tree/master" }, - "time": "2022-05-20T15:21:07+00:00" + "time": "2024-04-15T14:14:23+00:00" }, { "name": "theseer/tokenizer", @@ -6739,16 +6746,16 @@ }, { "name": "wp-coding-standards/wpcs", - "version": "3.0.1", + "version": "3.1.0", "source": { "type": "git", "url": "https://github.com/WordPress/WordPress-Coding-Standards.git", - "reference": "b4caf9689f1a0e4a4c632679a44e638c1c67aff1" + "reference": "9333efcbff231f10dfd9c56bb7b65818b4733ca7" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/WordPress/WordPress-Coding-Standards/zipball/b4caf9689f1a0e4a4c632679a44e638c1c67aff1", - "reference": "b4caf9689f1a0e4a4c632679a44e638c1c67aff1", + "url": "https://api.github.com/repos/WordPress/WordPress-Coding-Standards/zipball/9333efcbff231f10dfd9c56bb7b65818b4733ca7", + "reference": "9333efcbff231f10dfd9c56bb7b65818b4733ca7", "shasum": "" }, "require": { @@ -6757,16 +6764,16 @@ "ext-tokenizer": "*", "ext-xmlreader": "*", "php": ">=5.4", - "phpcsstandards/phpcsextra": "^1.1.0", - "phpcsstandards/phpcsutils": "^1.0.8", - "squizlabs/php_codesniffer": "^3.7.2" + "phpcsstandards/phpcsextra": "^1.2.1", + "phpcsstandards/phpcsutils": "^1.0.10", + "squizlabs/php_codesniffer": "^3.9.0" }, "require-dev": { "php-parallel-lint/php-console-highlighter": "^1.0.0", "php-parallel-lint/php-parallel-lint": "^1.3.2", "phpcompatibility/php-compatibility": "^9.0", "phpcsstandards/phpcsdevtools": "^1.2.0", - "phpunit/phpunit": "^4.0 || ^5.0 || ^6.0 || ^7.0" + "phpunit/phpunit": "^4.0 || ^5.0 || ^6.0 || ^7.0 || ^8.0 || ^9.0" }, "suggest": { "ext-iconv": "For improved results", @@ -6797,11 +6804,11 @@ }, "funding": [ { - "url": "https://opencollective.com/thewpcc/contribute/wp-php-63406", + "url": "https://opencollective.com/php_codesniffer", "type": "custom" } ], - "time": "2023-09-14T07:06:09+00:00" + "time": "2024-03-25T16:39:00+00:00" }, { "name": "zordius/lightncandy", diff --git a/package.json b/package.json index c3a5c5728d..8c077c1740 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "tribe-common", - "version": "5.2.7", + "version": "6.0.0", "repository": "git@github.com:the-events-calendar/tribe-common.git", "_resourcepath": "src/resources", "_domainPath": "lang", diff --git a/src/Common/Event_Automator/Power_Automate/Triggers/Attendees.php b/src/Common/Event_Automator/Power_Automate/Triggers/Attendees.php index b57dd85c84..520052959e 100644 --- a/src/Common/Event_Automator/Power_Automate/Triggers/Attendees.php +++ b/src/Common/Event_Automator/Power_Automate/Triggers/Attendees.php @@ -10,7 +10,7 @@ namespace TEC\Event_Automator\Power_Automate\Triggers; use TEC\Event_Automator\Power_Automate\Trigger_Queue\Abstract_Trigger_Queue; -use Tribe__Tickets__Tickets; +use Tribe__Tickets__Tickets as Tribe__Tickets__TicketsAlias; /** * Class Attendees @@ -39,7 +39,7 @@ protected function validate_for_trigger( $post_id, $data ) { } $provider = tribe_tickets_get_ticket_provider( $post_id ); - if ( ! $provider instanceof Tribe__Tickets__Tickets ) { + if ( ! $provider instanceof Tribe__Tickets__TicketsAlias ) { return false; } diff --git a/src/Tribe/Main.php b/src/Tribe/Main.php index 85b4a44780..7044e3749c 100644 --- a/src/Tribe/Main.php +++ b/src/Tribe/Main.php @@ -18,7 +18,7 @@ class Tribe__Main { const OPTIONNAME = 'tribe_events_calendar_options'; const OPTIONNAMENETWORK = 'tribe_events_calendar_network_options'; const FEED_URL = 'https://theeventscalendar.com/feed/'; - const VERSION = '5.3.0-dev'; + const VERSION = '6.0.0'; protected $plugin_context; protected $plugin_context_class; diff --git a/tests/_bootstrap.php b/tests/_bootstrap.php index a68ccf1ade..639d91fe04 100644 --- a/tests/_bootstrap.php +++ b/tests/_bootstrap.php @@ -3,7 +3,84 @@ use Codeception\Util\Autoload; -require_once dirname( __FILE__, 2 ) . '/tribe-autoload.php'; +require_once dirname( __DIR__, 1 ) . '/tribe-autoload.php'; Autoload::addNamespace( 'Tribe\\Tests', __DIR__ . '/_support' ); // Silence the logger in the tests. $_ENV['TEC_DISABLE_LOGGING'] = 1; + + +if ( in_array( 'eva_integration', $GLOBALS['argv'] ) || in_array( 'restv1', $GLOBALS['argv'] ) || in_array( 'end2end', $GLOBALS['argv'] ) ) { + /** + * Bootstrap for Event Automator Tests. + * + */ + + // TEC Test Support. + $tec_dir = dirname( __DIR__, 2 ); + $tec_tests_dir = $tec_dir . '/tests'; + $tec_support_dir = $tec_tests_dir . '/_support'; + if ( ! is_dir( $tec_tests_dir ) ) { + throw new RuntimeException( "Event Automator tests require The Events Calendar installed in a \"the-events-calendar\" sibling folder: {$tec_tests_dir} not found." ); + } + + // ET Test Support. + $et_dir = dirname( __DIR__, 3 ) . '/event-tickets'; + $et_tests_dir = $et_dir . '/tests'; + $et_support_dir = $et_tests_dir . '/_support'; + if ( ! is_dir( $et_tests_dir ) ) { + throw new RuntimeException( "Event Automator tests require Event Tickets installed in a \"event-tickets\" sibling folder: {$et_tests_dir} not found." ); + } + + // ET+ Test Support. + $etplus_dir = dirname( __DIR__, 3 ) . '/event-tickets-plus'; + $etplus_tests_dir = $etplus_dir . '/tests'; + $etplus_support_dir = $etplus_tests_dir . '/_support'; + if ( ! is_dir( $etplus_tests_dir ) ) { + throw new RuntimeException( "Event Automator tests require Event Tickets Plus installed in a \"event-tickets-plus\" sibling folder: {$etplus_tests_dir} not found." ); + } + + /** + * Manually include the file here as we might need it in a suite configuration file. + * Suites fire before the autoload below is used so we need to gather what we need without + * autoloading. + */ + require_once $tec_support_dir . '/Helper/TribeDb.php'; + + Autoload::addNamespace( '\\Tribe\\Events\\Test', $tec_support_dir ); + Autoload::addNamespace( '\\Helper', $tec_support_dir ); + Autoload::addNamespace( '\\TEC\\Event_Automator\\Tests', __DIR__ . '/_support' ); + Autoload::addNamespace( '\\Tribe\\Extensions', __DIR__ . '/_data/classes/Tribe/Extensions' ); + Autoload::addNamespace( '\Tribe\Tickets\Test', $et_support_dir ); + Autoload::addNamespace( '\Tribe\Tickets_Plus\Test', $etplus_support_dir ); + + + /** + * Codeception will regenerate snapshots on `--debug`, while the `spatie/snapshot-assertions` + * library will do the same on `--update-snapshots`. + * Since Codeception has strict check on the CLI arguments appending `--update-snapshots` to the + * `vendor/bin/codecept run` command will throw an error. + * We handle that intention here. + */ + if ( in_array( '--debug', $_SERVER['argv'], true ) ) { + $_SERVER['argv'][] = '--update-snapshots'; + } + + // If the `uopz` extension is installed, then ensure `exit` and `die` to work normally. + if ( function_exists( 'uopz_allow_exit' ) ) { + uopz_allow_exit( true ); + } + + // Let's make sure Tickets Commerce is activated. + putenv( 'TEC_TICKETS_COMMERCE=1' ); + $_ENV['TEC_TICKETS_COMMERCE'] = 1; + + // Disabled SSL check. + putenv( 'TEC_EVENT_AUTOMATOR_INTEGRATION_SSL_DISABLED=1' ); + $_ENV['TEC_EVENT_AUTOMATOR_INTEGRATION_SSL_DISABLED'] = 1; + + + // By default, do not enable the Custom Tables v1 implementation in tests. + putenv( 'TEC_CUSTOM_TABLES_V1_DISABLED=1' ); + $_ENV['TEC_CUSTOM_TABLES_V1_DISABLED'] = 1; + +} diff --git a/tests/_data/Power_Automate/Connections/200-account-valid-key-pair-2.json b/tests/_data/Power_Automate/Connections/200-account-valid-key-pair-2.json new file mode 100644 index 0000000000..500bf22a7a --- /dev/null +++ b/tests/_data/Power_Automate/Connections/200-account-valid-key-pair-2.json @@ -0,0 +1,9 @@ +{ + "consumer_id": "2ed61a7fd3ec668ec3e82e00f22e0c8230d353a5", + "consumer_secret": "e712e1a4a698214c3537016f633e06cc8fcbbd0e", + "has_pair": "true", + "permissions": "read", + "last_access": "2022-10-18 06:35:55", + "user_id": "1", + "name": "Automated Tests PA 15" +} \ No newline at end of file diff --git a/tests/_data/Power_Automate/Connections/200-account-valid-key-pair.json b/tests/_data/Power_Automate/Connections/200-account-valid-key-pair.json new file mode 100644 index 0000000000..7045d638b9 --- /dev/null +++ b/tests/_data/Power_Automate/Connections/200-account-valid-key-pair.json @@ -0,0 +1,9 @@ +{ + "consumer_id": "efbe2a4f41ad592da9afe3cef24a5b358e9c6ab395e8c86e39593ab7a374815b", + "consumer_secret": "f1c9b5d880695649df16689a39d574fb0802150397d9728c511c8fcc87415c29", + "has_pair": "true", + "permissions": "read", + "last_access": "", + "user_id": "1", + "name": "Automated Tests PA 1" +} \ No newline at end of file diff --git a/tests/_data/Power_Automate/Endpoints/attendee.json b/tests/_data/Power_Automate/Endpoints/attendee.json new file mode 100644 index 0000000000..b4e4e7ca60 --- /dev/null +++ b/tests/_data/Power_Automate/Endpoints/attendee.json @@ -0,0 +1,8 @@ +{ + "id": "attendees", + "display_name": "Attendees", + "type" : "queue", + "last_access" : "", + "count" : "5", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Power_Automate/Endpoints/canceled_events.json b/tests/_data/Power_Automate/Endpoints/canceled_events.json new file mode 100644 index 0000000000..fa83b1f981 --- /dev/null +++ b/tests/_data/Power_Automate/Endpoints/canceled_events.json @@ -0,0 +1,8 @@ +{ + "id": "canceled_events", + "display_name": "Canceled Events", + "type" : "queue", + "last_access" : "", + "count" : "8", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Power_Automate/Endpoints/checkin.json b/tests/_data/Power_Automate/Endpoints/checkin.json new file mode 100644 index 0000000000..c9588b450e --- /dev/null +++ b/tests/_data/Power_Automate/Endpoints/checkin.json @@ -0,0 +1,8 @@ +{ + "id": "checkin", + "display_name": "Checkin", + "type" : "queue", + "last_access" : "", + "count" : "5", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Power_Automate/Endpoints/new_events.json b/tests/_data/Power_Automate/Endpoints/new_events.json new file mode 100644 index 0000000000..abc719ebb2 --- /dev/null +++ b/tests/_data/Power_Automate/Endpoints/new_events.json @@ -0,0 +1,8 @@ +{ + "id": "new_events", + "display_name": "New Events", + "type" : "queue", + "last_access" : "", + "count" : "7", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Power_Automate/Endpoints/orders.json b/tests/_data/Power_Automate/Endpoints/orders.json new file mode 100644 index 0000000000..a4996dd010 --- /dev/null +++ b/tests/_data/Power_Automate/Endpoints/orders.json @@ -0,0 +1,8 @@ +{ + "id": "orders", + "display_name": "Orders", + "type" : "queue", + "last_access" : "", + "count" : "23", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Power_Automate/Endpoints/refunded_orders.json b/tests/_data/Power_Automate/Endpoints/refunded_orders.json new file mode 100644 index 0000000000..d83338e22d --- /dev/null +++ b/tests/_data/Power_Automate/Endpoints/refunded_orders.json @@ -0,0 +1,8 @@ +{ + "id": "refunded_orders", + "display_name": "Refunded Orders", + "type" : "queue", + "last_access" : "", + "count" : "3", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Power_Automate/Endpoints/updated_attendee.json b/tests/_data/Power_Automate/Endpoints/updated_attendee.json new file mode 100644 index 0000000000..de2093f731 --- /dev/null +++ b/tests/_data/Power_Automate/Endpoints/updated_attendee.json @@ -0,0 +1,8 @@ +{ + "id": "updated_attendees", + "display_name": "Updated Attendees", + "type" : "queue", + "last_access" : "", + "count" : "7", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Power_Automate/Endpoints/updated_events.json b/tests/_data/Power_Automate/Endpoints/updated_events.json new file mode 100644 index 0000000000..a952162a0a --- /dev/null +++ b/tests/_data/Power_Automate/Endpoints/updated_events.json @@ -0,0 +1,8 @@ +{ + "id": "updated_events", + "display_name": "Updated Events", + "type" : "queue", + "last_access" : "", + "count" : "3", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Zapier/API-Keys/200-account-valid-key-pair-2.json b/tests/_data/Zapier/API-Keys/200-account-valid-key-pair-2.json new file mode 100644 index 0000000000..fdce6075ab --- /dev/null +++ b/tests/_data/Zapier/API-Keys/200-account-valid-key-pair-2.json @@ -0,0 +1,9 @@ +{ + "consumer_id": "2ed61a7fd3ec668ec3e82e00f22e0c8230d353a5", + "consumer_secret": "e712e1a4a698214c3537016f633e06cc8fcbbd0e", + "has_pair": "true", + "permissions": "read", + "last_access": "2022-10-18 06:35:55", + "user_id": "1", + "name": "Automated Tests 12" +} \ No newline at end of file diff --git a/tests/_data/Zapier/API-Keys/200-account-valid-key-pair.json b/tests/_data/Zapier/API-Keys/200-account-valid-key-pair.json new file mode 100644 index 0000000000..518807ce50 --- /dev/null +++ b/tests/_data/Zapier/API-Keys/200-account-valid-key-pair.json @@ -0,0 +1,9 @@ +{ + "consumer_id": "efbe2a4f41ad592da9afe3cef24a5b358e9c6ab395e8c86e39593ab7a374815b", + "consumer_secret": "f1c9b5d880695649df16689a39d574fb0802150397d9728c511c8fcc87415c29", + "has_pair": "true", + "permissions": "read", + "last_access": "", + "user_id": "1", + "name": "Automated Tests 1" +} \ No newline at end of file diff --git a/tests/_data/Zapier/Endpoints/attendee.json b/tests/_data/Zapier/Endpoints/attendee.json new file mode 100644 index 0000000000..b4e4e7ca60 --- /dev/null +++ b/tests/_data/Zapier/Endpoints/attendee.json @@ -0,0 +1,8 @@ +{ + "id": "attendees", + "display_name": "Attendees", + "type" : "queue", + "last_access" : "", + "count" : "5", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Zapier/Endpoints/authorize.json b/tests/_data/Zapier/Endpoints/authorize.json new file mode 100644 index 0000000000..3d8551a2e5 --- /dev/null +++ b/tests/_data/Zapier/Endpoints/authorize.json @@ -0,0 +1,8 @@ +{ + "id": "authorize", + "display_name": "Authorize", + "type" : "authorize", + "last_access" : "", + "count" : "0", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Zapier/Endpoints/canceled_events.json b/tests/_data/Zapier/Endpoints/canceled_events.json new file mode 100644 index 0000000000..fa83b1f981 --- /dev/null +++ b/tests/_data/Zapier/Endpoints/canceled_events.json @@ -0,0 +1,8 @@ +{ + "id": "canceled_events", + "display_name": "Canceled Events", + "type" : "queue", + "last_access" : "", + "count" : "8", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Zapier/Endpoints/checkin.json b/tests/_data/Zapier/Endpoints/checkin.json new file mode 100644 index 0000000000..c9588b450e --- /dev/null +++ b/tests/_data/Zapier/Endpoints/checkin.json @@ -0,0 +1,8 @@ +{ + "id": "checkin", + "display_name": "Checkin", + "type" : "queue", + "last_access" : "", + "count" : "5", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Zapier/Endpoints/new_events.json b/tests/_data/Zapier/Endpoints/new_events.json new file mode 100644 index 0000000000..abc719ebb2 --- /dev/null +++ b/tests/_data/Zapier/Endpoints/new_events.json @@ -0,0 +1,8 @@ +{ + "id": "new_events", + "display_name": "New Events", + "type" : "queue", + "last_access" : "", + "count" : "7", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Zapier/Endpoints/orders.json b/tests/_data/Zapier/Endpoints/orders.json new file mode 100644 index 0000000000..a4996dd010 --- /dev/null +++ b/tests/_data/Zapier/Endpoints/orders.json @@ -0,0 +1,8 @@ +{ + "id": "orders", + "display_name": "Orders", + "type" : "queue", + "last_access" : "", + "count" : "23", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Zapier/Endpoints/refunded_orders.json b/tests/_data/Zapier/Endpoints/refunded_orders.json new file mode 100644 index 0000000000..d83338e22d --- /dev/null +++ b/tests/_data/Zapier/Endpoints/refunded_orders.json @@ -0,0 +1,8 @@ +{ + "id": "refunded_orders", + "display_name": "Refunded Orders", + "type" : "queue", + "last_access" : "", + "count" : "3", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Zapier/Endpoints/updated_attendee.json b/tests/_data/Zapier/Endpoints/updated_attendee.json new file mode 100644 index 0000000000..2636d4d0d9 --- /dev/null +++ b/tests/_data/Zapier/Endpoints/updated_attendee.json @@ -0,0 +1,8 @@ +{ + "id": "updated_attendees", + "display_name": "Updated Attendees", + "type" : "queue", + "last_access" : "", + "count" : "5", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/Zapier/Endpoints/updated_events.json b/tests/_data/Zapier/Endpoints/updated_events.json new file mode 100644 index 0000000000..a952162a0a --- /dev/null +++ b/tests/_data/Zapier/Endpoints/updated_events.json @@ -0,0 +1,8 @@ +{ + "id": "updated_events", + "display_name": "Updated Events", + "type" : "queue", + "last_access" : "", + "count" : "3", + "enabled" : "true" +} \ No newline at end of file diff --git a/tests/_data/dump.sql b/tests/_data/dump.sql new file mode 100644 index 0000000000..f9a1ff4d7e --- /dev/null +++ b/tests/_data/dump.sql @@ -0,0 +1,594 @@ +-- MariaDB dump 10.19 Distrib 10.5.21-MariaDB, for debian-linux-gnu (x86_64) +-- +-- Host: db Database: test +-- ------------------------------------------------------ +-- Server version 10.7.8-MariaDB-1:10.7.8+maria~ubu2004 + +/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; +/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; +/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; +/*!40101 SET NAMES utf8mb4 */; +/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; +/*!40103 SET TIME_ZONE='+00:00' */; +/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; +/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; +/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; +/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; + +-- +-- Table structure for table `wp_actionscheduler_actions` +-- + +DROP TABLE IF EXISTS `wp_actionscheduler_actions`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_actionscheduler_actions` ( + `action_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `hook` varchar(191) NOT NULL, + `status` varchar(20) NOT NULL, + `scheduled_date_gmt` datetime DEFAULT '0000-00-00 00:00:00', + `scheduled_date_local` datetime DEFAULT '0000-00-00 00:00:00', + `priority` tinyint(3) unsigned NOT NULL DEFAULT 10, + `args` varchar(191) DEFAULT NULL, + `schedule` longtext DEFAULT NULL, + `group_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `attempts` int(11) NOT NULL DEFAULT 0, + `last_attempt_gmt` datetime DEFAULT '0000-00-00 00:00:00', + `last_attempt_local` datetime DEFAULT '0000-00-00 00:00:00', + `claim_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `extended_args` varchar(8000) DEFAULT NULL, + PRIMARY KEY (`action_id`), + KEY `hook` (`hook`), + KEY `status` (`status`), + KEY `scheduled_date_gmt` (`scheduled_date_gmt`), + KEY `args` (`args`), + KEY `group_id` (`group_id`), + KEY `last_attempt_gmt` (`last_attempt_gmt`), + KEY `claim_id_status_scheduled_date_gmt` (`claim_id`,`status`,`scheduled_date_gmt`) +) ENGINE=InnoDB AUTO_INCREMENT=10 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_actionscheduler_actions` +-- + +LOCK TABLES `wp_actionscheduler_actions` WRITE; +/*!40000 ALTER TABLE `wp_actionscheduler_actions` DISABLE KEYS */; +INSERT INTO `wp_actionscheduler_actions` VALUES (7,'action_scheduler/migration_hook','failed','2023-11-28 12:15:16','2023-11-28 12:15:16',10,'[]','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1701173716;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1701173716;}',1,1,'2023-11-29 15:37:29','2023-11-29 15:37:29',0,NULL),(8,'action_scheduler/migration_hook','complete','2023-11-29 15:49:08','2023-11-29 15:49:08',10,'[]','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1701272948;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1701272948;}',1,1,'2024-01-28 15:14:51','2024-01-28 15:14:51',0,NULL),(9,'action_scheduler/migration_hook','pending','2024-01-28 15:23:26','2024-01-28 15:23:26',10,'[]','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1706455406;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1706455406;}',1,0,'0000-00-00 00:00:00','0000-00-00 00:00:00',0,NULL); +/*!40000 ALTER TABLE `wp_actionscheduler_actions` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_actionscheduler_claims` +-- + +DROP TABLE IF EXISTS `wp_actionscheduler_claims`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_actionscheduler_claims` ( + `claim_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `date_created_gmt` datetime DEFAULT '0000-00-00 00:00:00', + PRIMARY KEY (`claim_id`), + KEY `date_created_gmt` (`date_created_gmt`) +) ENGINE=InnoDB AUTO_INCREMENT=9 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_actionscheduler_claims` +-- + +LOCK TABLES `wp_actionscheduler_claims` WRITE; +/*!40000 ALTER TABLE `wp_actionscheduler_claims` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_actionscheduler_claims` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_actionscheduler_groups` +-- + +DROP TABLE IF EXISTS `wp_actionscheduler_groups`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_actionscheduler_groups` ( + `group_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `slug` varchar(255) NOT NULL, + PRIMARY KEY (`group_id`), + KEY `slug` (`slug`(191)) +) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_actionscheduler_groups` +-- + +LOCK TABLES `wp_actionscheduler_groups` WRITE; +/*!40000 ALTER TABLE `wp_actionscheduler_groups` DISABLE KEYS */; +INSERT INTO `wp_actionscheduler_groups` VALUES (1,'action-scheduler-migration'); +/*!40000 ALTER TABLE `wp_actionscheduler_groups` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_actionscheduler_logs` +-- + +DROP TABLE IF EXISTS `wp_actionscheduler_logs`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_actionscheduler_logs` ( + `log_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `action_id` bigint(20) unsigned NOT NULL, + `message` text NOT NULL, + `log_date_gmt` datetime DEFAULT '0000-00-00 00:00:00', + `log_date_local` datetime DEFAULT '0000-00-00 00:00:00', + PRIMARY KEY (`log_id`), + KEY `action_id` (`action_id`), + KEY `log_date_gmt` (`log_date_gmt`) +) ENGINE=InnoDB AUTO_INCREMENT=14 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_actionscheduler_logs` +-- + +LOCK TABLES `wp_actionscheduler_logs` WRITE; +/*!40000 ALTER TABLE `wp_actionscheduler_logs` DISABLE KEYS */; +INSERT INTO `wp_actionscheduler_logs` VALUES (7,7,'action created','2023-11-28 12:14:16','2023-11-28 12:14:16'),(8,7,'action started via Async Request','2023-11-29 15:37:29','2023-11-29 15:37:29'),(9,7,'action failed via Async Request: Scheduled action for action_scheduler/migration_hook will not be executed as no callbacks are registered.','2023-11-29 15:37:29','2023-11-29 15:37:29'),(10,8,'action created','2023-11-29 15:48:08','2023-11-29 15:48:08'),(11,8,'action started via Async Request','2024-01-28 15:14:51','2024-01-28 15:14:51'),(12,8,'action complete via Async Request','2024-01-28 15:14:51','2024-01-28 15:14:51'),(13,9,'action created','2024-01-28 15:22:26','2024-01-28 15:22:26'); +/*!40000 ALTER TABLE `wp_actionscheduler_logs` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_commentmeta` +-- + +DROP TABLE IF EXISTS `wp_commentmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_commentmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `comment_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `comment_id` (`comment_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_commentmeta` +-- + +LOCK TABLES `wp_commentmeta` WRITE; +/*!40000 ALTER TABLE `wp_commentmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_commentmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_comments` +-- + +DROP TABLE IF EXISTS `wp_comments`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_comments` ( + `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT 0, + `comment_author` tinytext NOT NULL, + `comment_author_email` varchar(100) NOT NULL DEFAULT '', + `comment_author_url` varchar(200) NOT NULL DEFAULT '', + `comment_author_IP` varchar(100) NOT NULL DEFAULT '', + `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `comment_content` text NOT NULL, + `comment_karma` int(11) NOT NULL DEFAULT 0, + `comment_approved` varchar(20) NOT NULL DEFAULT '1', + `comment_agent` varchar(255) NOT NULL DEFAULT '', + `comment_type` varchar(20) NOT NULL DEFAULT 'comment', + `comment_parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + PRIMARY KEY (`comment_ID`), + KEY `comment_post_ID` (`comment_post_ID`), + KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), + KEY `comment_date_gmt` (`comment_date_gmt`), + KEY `comment_parent` (`comment_parent`), + KEY `comment_author_email` (`comment_author_email`(10)) +) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_comments` +-- + +LOCK TABLES `wp_comments` WRITE; +/*!40000 ALTER TABLE `wp_comments` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_comments` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_links` +-- + +DROP TABLE IF EXISTS `wp_links`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_links` ( + `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `link_url` varchar(255) NOT NULL DEFAULT '', + `link_name` varchar(255) NOT NULL DEFAULT '', + `link_image` varchar(255) NOT NULL DEFAULT '', + `link_target` varchar(25) NOT NULL DEFAULT '', + `link_description` varchar(255) NOT NULL DEFAULT '', + `link_visible` varchar(20) NOT NULL DEFAULT 'Y', + `link_owner` bigint(20) unsigned NOT NULL DEFAULT 1, + `link_rating` int(11) NOT NULL DEFAULT 0, + `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `link_rel` varchar(255) NOT NULL DEFAULT '', + `link_notes` mediumtext NOT NULL, + `link_rss` varchar(255) NOT NULL DEFAULT '', + PRIMARY KEY (`link_id`), + KEY `link_visible` (`link_visible`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_links` +-- + +LOCK TABLES `wp_links` WRITE; +/*!40000 ALTER TABLE `wp_links` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_links` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_options` +-- + +DROP TABLE IF EXISTS `wp_options`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_options` ( + `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `option_name` varchar(191) NOT NULL DEFAULT '', + `option_value` longtext NOT NULL, + `autoload` varchar(20) NOT NULL DEFAULT 'yes', + PRIMARY KEY (`option_id`), + UNIQUE KEY `option_name` (`option_name`), + KEY `autoload` (`autoload`) +) ENGINE=InnoDB AUTO_INCREMENT=406 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_options` +-- + +LOCK TABLES `wp_options` WRITE; +/*!40000 ALTER TABLE `wp_options` DISABLE KEYS */; +INSERT INTO `wp_options` VALUES (2,'siteurl','http://wordpress.test','yes'),(3,'home','http://wordpress.test','yes'),(4,'blogname','Event Automator','yes'),(5,'blogdescription','','yes'),(6,'users_can_register','0','yes'),(7,'admin_email','you@example.com','yes'),(8,'start_of_week','1','yes'),(9,'use_balanceTags','0','yes'),(10,'use_smilies','1','yes'),(11,'require_name_email','1','yes'),(12,'comments_notify','1','yes'),(13,'posts_per_rss','10','yes'),(14,'rss_use_excerpt','0','yes'),(15,'mailserver_url','mail.example.com','yes'),(16,'mailserver_login','login@example.com','yes'),(17,'mailserver_pass','password','yes'),(18,'mailserver_port','110','yes'),(19,'default_category','1','yes'),(20,'default_comment_status','open','yes'),(21,'default_ping_status','open','yes'),(22,'default_pingback_flag','1','yes'),(23,'posts_per_page','10','yes'),(24,'date_format','F j, Y','yes'),(25,'time_format','g:i a','yes'),(26,'links_updated_date_format','F j, Y g:i a','yes'),(27,'comment_moderation','0','yes'),(28,'moderation_notify','1','yes'),(30,'hack_file','0','yes'),(31,'blog_charset','UTF-8','yes'),(32,'moderation_keys','','no'),(33,'active_plugins','a:0:{}','yes'),(34,'category_base','','yes'),(35,'ping_sites','http://rpc.pingomatic.com/','yes'),(36,'comment_max_links','2','yes'),(37,'gmt_offset','0','yes'),(38,'default_email_category','1','yes'),(39,'recently_edited','','no'),(40,'template','twentytwentythree','yes'),(41,'stylesheet','twentytwentythree','yes'),(42,'comment_registration','0','yes'),(43,'html_type','text/html','yes'),(44,'use_trackback','0','yes'),(45,'default_role','subscriber','yes'),(46,'db_version','53496','yes'),(47,'uploads_use_yearmonth_folders','1','yes'),(48,'upload_path','','yes'),(49,'blog_public','1','yes'),(50,'default_link_category','2','yes'),(51,'show_on_front','posts','yes'),(52,'tag_base','','yes'),(53,'show_avatars','1','yes'),(54,'avatar_rating','G','yes'),(55,'upload_url_path','','yes'),(56,'thumbnail_size_w','150','yes'),(57,'thumbnail_size_h','150','yes'),(58,'thumbnail_crop','1','yes'),(59,'medium_size_w','300','yes'),(60,'medium_size_h','300','yes'),(61,'avatar_default','mystery','yes'),(62,'large_size_w','1024','yes'),(63,'large_size_h','1024','yes'),(64,'image_default_link_type','none','yes'),(65,'image_default_size','','yes'),(66,'image_default_align','','yes'),(67,'close_comments_for_old_posts','0','yes'),(68,'close_comments_days_old','14','yes'),(69,'thread_comments','1','yes'),(70,'thread_comments_depth','5','yes'),(71,'page_comments','0','yes'),(72,'comments_per_page','50','yes'),(73,'default_comments_page','newest','yes'),(74,'comment_order','asc','yes'),(75,'sticky_posts','a:0:{}','yes'),(76,'widget_categories','a:0:{}','yes'),(77,'widget_text','a:0:{}','yes'),(78,'widget_rss','a:0:{}','yes'),(79,'uninstall_plugins','a:1:{s:35:\"event-automator/event-automator.php\";s:23:\"tec_automator_uninstall\";}','no'),(80,'timezone_string','','yes'),(81,'page_for_posts','0','yes'),(82,'page_on_front','0','yes'),(83,'default_post_format','0','yes'),(84,'link_manager_enabled','0','yes'),(85,'finished_splitting_shared_terms','1','yes'),(86,'site_icon','0','yes'),(87,'medium_large_size_w','768','yes'),(88,'medium_large_size_h','0','yes'),(89,'wp_page_for_privacy_policy','3','yes'),(90,'show_comments_cookies_opt_in','1','yes'),(92,'disallowed_keys','','no'),(93,'comment_previously_approved','1','yes'),(94,'auto_plugin_theme_update_emails','a:0:{}','no'),(95,'auto_update_core_dev','enabled','yes'),(96,'auto_update_core_minor','enabled','yes'),(97,'auto_update_core_major','enabled','yes'),(98,'wp_force_deactivated_plugins','a:0:{}','yes'),(99,'initial_db_version','53496','yes'),(100,'wp_user_roles','a:5:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:71:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;s:31:\"read_private_aggregator-records\";b:1;s:23:\"edit_aggregator-records\";b:1;s:30:\"edit_others_aggregator-records\";b:1;s:31:\"edit_private_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:32:\"delete_others_aggregator-records\";b:1;s:33:\"delete_private_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:44:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:31:\"read_private_aggregator-records\";b:1;s:23:\"edit_aggregator-records\";b:1;s:30:\"edit_others_aggregator-records\";b:1;s:31:\"edit_private_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:32:\"delete_others_aggregator-records\";b:1;s:33:\"delete_private_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:15:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:23:\"edit_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:7:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:23:\"edit_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}}','yes'),(101,'fresh_site','1','yes'),(102,'user_count','1','no'),(103,'widget_block','a:6:{i:2;a:1:{s:7:\"content\";s:19:\"\";}i:3;a:1:{s:7:\"content\";s:154:\"
This month’s customer spotlight features Trail Pei, a website designed to help users find the best trails to hike and run all around the world. They utilize The Events Calendar products to help them achieve their goals of displaying multiple calendars on their website, giving their users all of the information they need in one…
\nThe post Featured Calendar: Trail Pei appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"Jaime\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:13665:\"\nThis month’s customer spotlight features Trail Pei, a website designed to help users find the best trails to hike and run all around the world. They utilize The Events Calendar products to help them achieve their goals of displaying multiple calendars on their website, giving their users all of the information they need in one place.
\n\n\n\nLet’s take a look at how they make that happen below.
\n\n\n\nStarting with the homepage, Trail Pei gives you everything you need to navigate through their website.
\n\n\n\n\n\n\n\nThe website is displayed by default in French, but it easily translates to any language. We love the simple hero image on the homepage with a saying that invites you right in. Beyond that, you’ll find a main navigation that’ll take you anywhere you want to go on the website.
\n\n\n\nScroll down, and you’ll see the events that are displayed right on the homepage. They’ve created multiple tracks with event categories so that you can easily find events in your area. We’ve got lots of widgets and blocks available to help you display your events.
\n\n\n\n\n\n\n\nOn the main calendar page, all of the events that exist on the entire website live. Trail Pei chose to display their events in List View by default, but there are lots of different view options, depending on how many events you have and how much information you’d like to display.
\n\n\n\n\n\n\n\nHere, they also show the default Events Bar, which can be easily customized. In addition, they have an additional filter bar, available with our Filter Bar add-on. This allows users to search through their plethora of events by category, country, city, and more. For a website with so many events, this is a great option to let users feel like they can find what they’re looking for.
\n\n\n\nLastly, once you find an event you’d like to learn more about, you can visit one of their single event pages. Theses highly-customized pages contain additional features and integrations, including maps, gear to purchase, and your current location. Although these features aren’t available out of the box with our plugins, the good news is that our plugins work on a templating system that make them very easy to personalize to suit your needs.
\n\n\n\n\n\n\n\n\n\n\n\nTrail Pei created an effective calendar of events and you can too! Not quite sure where to start? No worries, we’ve got you covered! Simply request a free demo site and try out all of our plugins on one test site. Feel free to add your current plugins and themes to get a sense of what things would look like on your own website. Get started today!
\nThe post Featured Calendar: Trail Pei appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"The Events Calendar 6.2.8.1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:163:\"https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-2-8-1/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 20 Nov 2023 19:35:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:19:\"The Events Calendar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543324\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:607:\"Summary Maintenance Release This new version of The Events Calendar includes a fix to ensure password-protected posts have their settings respected. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing! ✅ Fixed Bugs that were squashed in this release: 🗣 Translations Updated language files and strings:
\nThe post The Events Calendar 6.2.8.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2627:\"\n\n\n\n\nMaintenance Release
\nThis new version of The Events Calendar includes a fix to ensure password-protected posts have their settings respected.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing!
\nBugs that were squashed in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post The Events Calendar 6.2.8.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"Introducing Wallet Plus\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:135:\"https://theeventscalendar.com/blog/news/introducing-wallet-plus/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 16:40:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:10:\"What\'s New\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:4:\"blog\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2542896\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:578:\"We’re here to announce our exciting new innovation, Wallet Plus. This product creates digital and portable tickets for your event attendees and truly modernizes all of our current offerings, including Event Tickets and Event Tickets Plus. We’ve made this process simpler for your attendees so that they can now save their tickets to digital wallets,…
\nThe post Introducing Wallet Plus appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"Jaime\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4277:\"\nWe’re here to announce our exciting new innovation, Wallet Plus. This product creates digital and portable tickets for your event attendees and truly modernizes all of our current offerings, including Event Tickets and Event Tickets Plus.
\n\n\n\nWe’ve made this process simpler for your attendees so that they can now save their tickets to digital wallets, like Apple Wallet or PassWallet, and download PDF tickets to have them with them at any time.
\n\n\n\nPlus, you can personalize digital tickets by adding your logo, picking your brand colors, and customizing your Apple wallet passes and PDFs.
\n\n\n\nWallet Plus is a game-changer for day-of-event management. Your attendees will have easy access to their tickets, and the QR check-in process will be simpler and faster.
\n\n\n\nBelow, we’ll break down all of the exciting new features
\n\n\n\nAllow users to save their tickets in Apple Wallet.
\n\n\n\nCustomize your PDF tickets and allow your event attendees to download them or receive them by email.
\n\n\n\nInclude digital tickets in ticket confirmation emails and during the checkout process.
\n\n\n\nAllow attendees to save their tickets into their favorite digital platform so they can access their tickets anytime.
\n\n\n\nEasily customize your digital tickets with the look and feel of your brand in a few simple clicks.
\n\n\n\nStart providing digital tickets in a few clicks. Just install the plugin and set up the look and feel of your digital tickets via settings.
\n\n\n\nInclude attendee registration fields into digital tickets when using Event Tickets Plus.
\n\n\n\nInclude QR on digital tickets, and make day-of event management a breeze.
\n\n\n\nWe can’t wait for you to see Wallet Plus in action; we know you’re going to love it! Get started today!
\nThe post Introducing Wallet Plus appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:21:\"Virtual Events 1.15.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:152:\"https://theeventscalendar.com/release-notes/virtual-events/virtual-events-1-15-5/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:33:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:14:\"Virtual Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543276\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:575:\"Summary Maintenance Release The latest version of Virtual Events introduces compatibility features with the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✨ New New tweaks and enhancements in this release: 🗣 Translations Updated language files and strings:
\nThe post Virtual Events 1.15.5 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2620:\"\n\n\n\n\nMaintenance Release
\nThe latest version of Virtual Events introduces compatibility features with the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nNew tweaks and enhancements in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Virtual Events 1.15.5 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:24:\"Event Tickets Plus 5.8.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:159:\"https://theeventscalendar.com/release-notes/event-tickets-plus/event-tickets-plus-5-8-0/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:33:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Event Tickets Plus\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543273\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:595:\"Summary Maintenance Release The latest version of Event Tickets Plus introduces compatibility features with the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing.Event Tickets Plus 5.8.0 is only compatible with Event Tickets 5.7.0 and higher. ✨ New New tweaks and enhancements…
\nThe post Event Tickets Plus 5.8.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2901:\"\n\n\n\n\nMaintenance Release
\nThe latest version of Event Tickets Plus introduces compatibility features with the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
Event Tickets Plus 5.8.0 is only compatible with Event Tickets 5.7.0 and higher.
New tweaks and enhancements in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Event Tickets Plus 5.8.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Event Tickets 5.7.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:149:\"https://theeventscalendar.com/release-notes/event-tickets/event-tickets-5-7-0/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:32:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:13:\"Event Tickets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543271\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:584:\"Summary Maintenance Release The latest version of Event Tickets introduces compatibility features with the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. Event Tickets 5.7.0 is only compatible with The Events Calendar 6.2.7 and higher.Event Tickets 5.7.0 is only compatible with…
\nThe post Event Tickets 5.7.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3889:\"\n\n\n\n\nMaintenance Release
\nThe latest version of Event Tickets introduces compatibility features with the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
Event Tickets 5.7.0 is only compatible with The Events Calendar 6.2.7 and higher.
Event Tickets 5.7.0 is only compatible with Event Tickets Plus 5.8.0 and higher.
New tweaks and enhancements in this release:
\n\n\n\nBugs that were squashed in this release:
\n\n\n\ntype=\"module\"
added on all scenarios.Updated language files and strings:
\n\n\n\nThe post Event Tickets 5.7.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"The Events Calendar 6.2.8\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:161:\"https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-2-8/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:31:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:19:\"The Events Calendar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543267\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:615:\"Summary Maintenance Release This new version of The Events Calendar includes compatibility improvements for the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing! The Events Calendar 6.2.8 is only compatible with Event Tickets 5.7.0 and higher. ✨ New New features and tweaks included…
\nThe post The Events Calendar 6.2.8 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2854:\"\n\n\n\n\nMaintenance Release
\nThis new version of The Events Calendar includes compatibility improvements for the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing!
\n\n\n\nThe Events Calendar 6.2.8 is only compatible with Event Tickets 5.7.0 and higher.
\nNew features and tweaks included in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post The Events Calendar 6.2.8 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"The Events Calendar 6.2.7\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:161:\"https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-2-7/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 17:50:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:19:\"The Events Calendar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543207\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:621:\"Summary Maintenance Release The latest update includes fixes for nonce generation and regressions along with various errors and deprecation notices. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✅ Fixed Bugs that were squashed in this release: ✨ Tweaks New tweaks in this release: 🗣 Translations Updated…
\nThe post The Events Calendar 6.2.7 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4757:\"\n\n\n\n\n\n\n\n\nMaintenance Release
\nThe latest update includes fixes for nonce generation and regressions along with various errors and deprecation notices.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nBugs that were squashed in this release:
\n\n\n\nNew tweaks in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post The Events Calendar 6.2.7 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"Events Calendar Pro 6.2.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:161:\"https://theeventscalendar.com/release-notes/events-calendar-pro/events-calendar-pro-6-2-4/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 17:49:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:19:\"Events Calendar Pro\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"Release Notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543209\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:579:\"Summary Maintenance Release The latest update resolves several deprecation notices and WPML permalink query on single posts. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✅ Fixed Bugs that were squashed in this release: 🗣 Translations Updated language files and strings:
\nThe post Events Calendar Pro 6.2.4 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3117:\"\n\n\n\n\nMaintenance Release
\nThe latest update resolves several deprecation notices and WPML permalink query on single posts.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nBugs that were squashed in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Events Calendar Pro 6.2.4 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"Introducing: Event Schedule Manager\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:146:\"https://theeventscalendar.com/blog/news/introducing-event-schedule-manager/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 17:53:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:10:\"What\'s New\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:4:\"blog\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2542727\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:582:\"Are you tired of juggling multiple systems, calendars, and custom coding while planning your events? Do you wish there was a more efficient way to manage your event schedules? Look no further! We are thrilled to introduce you to the all-new Event Schedule Manager – your ultimate event planning companion. Simplify your event planning Event…
\nThe post Introducing: Event Schedule Manager appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"Jaime\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3667:\"\nAre you tired of juggling multiple systems, calendars, and custom coding while planning your events? Do you wish there was a more efficient way to manage your event schedules? Look no further! We are thrilled to introduce you to the all-new Event Schedule Manager – your ultimate event planning companion.
\n\n\n\nEvent planning can be a daunting task, whether you’re organizing a corporate conference, a wedding, a music festival, or any other large-scale event. Event Schedule Manager is designed to simplify this process and make it more efficient than ever before.
\n\n\n\nWith Event Schedule Manager, you can say goodbye to custom coding a schedule with multiple tracks. Our user-friendly plugin provides a centralized hub where you can easily manage all aspects of your event, from scheduling to guest lists and beyond. There’s no need for multiple plugins and services to display your schedule tracks; everything you need is right at your fingertips.
\n\n\n\nLet’s take a closer look at some of the standout features that make Event Schedule Manager the go-to tool for event planners:
\n\n\n\nEvent Schedule Manager is more than just a scheduling tool; it’s a comprehensive event planning solution. Here’s why you should make it an integral part of your event planning process:
\n\n\n\nAre you ready to revolutionize your event schedule planning experience? Event Schedule Manager is here to make your life easier and your events more successful. Say goodbye to the chaos of event creation and hello to streamlined event planning.
\n\n\n\nCheck it out here!
\nThe post Introducing: Event Schedule Manager appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:35:\"https://theeventscalendar.com/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:14:{s:4:\"date\";s:29:\"Wed, 29 Nov 2023 15:37:28 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:6:\"cf-ray\";s:20:\"82dbee9cdfaf9c3c-IAD\";s:15:\"cf-cache-status\";s:6:\"BYPASS\";s:4:\"etag\";s:36:\"W/\"64a2ff63f5492637547ac1f2a407c8cf\"\";s:13:\"last-modified\";s:29:\"Tue, 28 Nov 2023 18:01:29 GMT\";s:4:\"link\";s:117:\"In the latest WordPress Briefing, Executive Director Josepha Haden Chomphosy revisits our roots in blogging and breaks down the essentials of starting your first WordPress blog. Tune in to Episode 71 for practical tips and inspiration to kickstart your blogging journey.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, we’ve got a throwback episode about blogging. If you’re like me, you sometimes miss the early days of blogs, where the words were a little more pensive, and the images were a little less professional. If you’re on a slow hobby journey like so many of us are right now, give this one a listen.
\n\n\n\n[00:00:58] (music interlude)
\n\n\n\n[00:01:05] Josepha: You may be one of these contributors I keep mentioning. You may be an agency owner or freelancer. Maybe you’ve wondered how to make a WordPress blog for your big idea. Or maybe you’re one of the many people who use WordPress for their own project or business.
\n\n\n\nBefore WordPress was known as a content management system, as a way to get sites online fast, it was a blogging tool. We have long since outgrown that, but even 20 years into our journey, blogging is still a key part of what WordPress enables you to do. That’s because, even after those 20 years, the mission of WordPress is still the same, and that is to democratize publishing.
\n\n\n\nTo help people have a place online where they can tell their stories, or share their projects, or set up their businesses. If you’ve ever tried to set up a blog, you know that there isn’t a lot of information about what to know before you get going at all. So, I’m going to talk about that a little bit today.
\n\n\n\n[00:02:06] Josepha: And just by the way, if you heard the word blog right now and thought, Oh, Jospeha, how old fashioned. I think it’s important to remember that there’s a business advantage to having well-written, relevant content on your website. And if you’re not blogging for business, because not all of us are, then the benefits are a little different but still important to my mind. Things like the cathartic benefits of journaling, a chance to build community, and the general importance of preserving wisdom for the ages.
\n\n\n\nAnyway, back to the topic at hand, before we can get to any of the fancy things that WordPress can do nowadays, it’s important to know a few things as you get ready to set up your first-ever website. So let’s dive in.
\n\n\n\nHere is how you need to get yourself started. First, have an idea and a plan. So, have an idea for what you’re doing, the concept of your content, who you want to reach, but also some concept of a domain name. I would encourage you to not necessarily get your heart set on a domain name at first, cause like, if you want the domain name WordPress.org, like, we own that, you can’t have that. But if you know that you want a domain like ‘WordPressbloggingforthefuture.com’ like, that one might be more available. And if you know kind of the words you want in your domain, then you can be a bit flexible about what is there.
\n\n\n\n[00:03:30] Josepha: The second thing that you need to do is that if you are just getting started, ask yourself the question, what sort of host do I want? We kind of mention all along the WordPress process that, like, you need a good host, but it’s not always clear where that decision has to happen. It happens right here at the start before you even know what WordPress is most of the time. So, the earliest question that you have to answer for yourself is, what sort of host do I want? Where do I want my site to live? So ask yourself how much you want to get into the maintenance and configuration of your website and the hardware that it lives on versus creating content or keeping your shop up to date. There’s this whole spectrum of hosting options, and they range from full service, where they will keep your WordPress software up to date and provide daily backups, and have customer support if something goes really wrong.
\n\n\n\n[00:04:23] Josepha: So it ranges all the way from full service like that, all the way down to essentially zero service, just kind of hands off. They give you a space to keep your WordPress software, to keep your WordPress site, but they leave everything else up to you. They leave the backups up to you; they leave updating up to you, things like that.
\n\n\n\nSo that’s the first thing you have to ask yourself and the first question you have to be able to answer. Most of the time, you will want to start with one of the full-service options. That way, you know that your software is set up correctly and safely from the start. And as you learn more about the software, and what you want, and what you need, and you have the ability to learn in the time that you have, the more that you can add on either services with the existing host that you chose or moving to a different host; however, that works out for you.
\n\n\n\n[00:05:09] Josepha: So if that one sounds like the right option, then you choose a host, go to their site, and actually, most of them will have a way to walk you through how to set up a WordPress site inside their system. Most of the time, it’s just one click, and then they ask you some questions to get some configurations right.
\n\n\n\nThe other option that on the like zero, zero service side, that’s not quite fair, but you know, on the other side of that spectrum, that probably will be appealing to you if you are already familiar with code or already know how to manage a server, or you know how to work in this thing called cPanel, etc. So if you already have a lot of information on how all of that works, you can, if you want to, head over to WordPress.org/download and you can download a zip file of the WordPress software and set that up in your own environment. Okay, quick check here. If this all sounds roughly doable to you, or at least it feels like we’re in the right starting point, but you find yourself thinking, gosh, I just wish she would slow down a little, I’ve got you covered.
\n\n\n\n[00:06:17] Josepha: In the show notes, you’ll find a link to one of the LearnWP courses for getting started with WordPress. There’s a section on choosing a host, as well as various other early steps of this process. If you felt like I blazed through all of that, which, honestly, I kind of did. You can work through those lessons in that course at your own pace, and it’s really a very good guide.
\n\n\n\nAll right. So let’s pretend we did all of that. Now you’ve got yourself a website. The thing that you will want to do next, or rather the first thing that you’ll notice once you get your site up and running, is that there’s this ‘Hello World’ post. There’s a post that already exists in there. The Hello World post is a placeholder for the common features of a blog post.
\n\n\n\n[00:07:03] Josepha: There, you can find your featured image, your title, your content, and even some fake comments. You can either edit this post so that you can see how your writing will look from the start, and you can kind of compare, like, okay, the Hello World part over here on this page exists in this field over here on this page. So you can kind of see where everything works, how it all looks together. Or, if you’re more familiar with WordPress or CMSs in general, you can simply remove that and start fresh. We’ve got now a website. We know kind of how to look at our posts and create posts, where comments are, where they can be moderated, and stuff.
\n\n\n\nAnd so, the most fun task for everyone is choosing a theme. But if it doesn’t sound like a fun task to you, I can help you kind of do some choose-your-own-adventure guiding questions here. Firstly, you can ask yourself how you want the site to look. Do you want it to mostly be a lot of photos or entirely words? Mostly animations? You can head to the theme directory and search for a theme with most of the features that you want. There’s like a filtering system where you can put in, like, you want, three columns so that you can have three columns of text if you want it to look kind of like an old school newspaper kind of layout and things like that.
\n\n\n\n[00:08:24] Josepha: There’s also a way to look for themes inside your instance, your WordPress site, but like, if you haven’t set that up yet, but you do still want to see kind of what your theme options are, you can go to WordPress.org/themes and take a look at what’s out there. Just as a quick side note, if you get to that theme directory, if you get to WordPress.org/themes, and it feels overwhelming, which I can understand, I recommend starting with a theme that is designed for blogging specifically, so that you can see how things look right away. And there’s actually a theme that does come with every WordPress site, so if you’re not ready, you can skip this thing entirely. And just work with the theme that’s already there. Every WordPress instance ships with a theme, and it is fully functional when you get your site up and running, so you don’t need to choose a theme right now if you don’t feel ready. And then the other very fun thing that people do with their WordPress sites, is to add plugins to them.
\n\n\n\n[00:09:20] Josepha: Plugins are these little pieces of software that you add on to the WordPress software that lets it do additional things. It adds additional functionality to it. The questions that you can ask to kind of guide yourself through what sorts of plugins you might want what sorts of functionality you might want to add to your site are a little similar to the ones that you want to ask for figuring out which themes.
\n\n\n\nSo, figure out if there are tasks that you need visitors to do. Do you need them to contact you? Do you want them to watch a video? Should they review and respond to questions? If you have a concept of the things that you want users to do on your website, then you can head to the plugin directory and search for a plugin with features that you need.
\n\n\n\n[00:10:05] Josepha: Also, there are just endless lists of recommended plugins out there. If that is something that you find valuable as part of your research, those are also easy to find. And as a general side note here as well, there are even more plugins than there are themes. So if you have gotten to this point and feel like you don’t quite know the answers to the questions that I shared, and it’s going to be a while until you feel like you can know what those answers are. That’s totally fine. I’ll tell you this, I have never seen a site without a contact form. So feel free to begin your journey there. There are a lot of great plugins for contact forms, and it can kind of help you figure out how to work with plugins in that way. So, yeah, I made it sound like you can get a WordPress website built in like seven minutes.
\n\n\n\nAnd on the one hand, you definitely can. And on the other hand, it’s still a little bit more complicated. So here I have a final note for everyone. You will hear around the WordPress ecosystem and, obviously, hear some things that could make you feel a little nervous about doing this for the first time.
\n\n\n\n[00:11:10] Josepha: Things like the five-second installation, which WordPress has been famous for for years, but also about how easy and simple it all is. And as somebody who was once in the position of learning WordPress for the first time, like I first encountered a WordPress site in 2009, and I started learning how to use WordPress in 2010.
\n\n\n\nI can say with confidence that once you learn it, it’s easy. We are the easiest of the hard options for CMSs like content management systems are just complicated. But we are the easiest one out there. And so, as you’re learning, I want to just remind you to celebrate your small wins along the way. If you feel like you’re late to this blogging game like you should have had a website for years, I mean, sure, that could be true.
\n\n\n\n[00:12:01] Josepha: And yes, the best time to plant a tree was 20 years ago, but the second best time to plant that tree is today. WordPress didn’t start out powering over 40% of the web, and your first site can’t be immediately measured in the millions of readers. So, what will your small beginning lead you to?
\n\n\n\n[00:12:18] (Music interlude)
\n\n\n\n[00:12:25] Josepha: And now, our small list of big things. Today we’ve got some look-back items and some look-forward items. So let’s hop right in.
\n\n\n\nFirst thing is we have a year in review with the themes team. So much amazing work has been done by the themes team over the past year, both for reviewing themes and creating them. So I’ll leave a link to those in the show notes.
\n\n\n\nWe also have a post out that just has some general celebrations from teams around the community. I’ll leave a link to that. It probably has been linked in quite a few places, but you know, we don’t always embrace those moments of celebration. We don’t always embrace our wins. And so it’s always good to share those early and often. There are probably more than just those two. So if you posted one or you saw a really interesting one that you think that we should know about, don’t forget to share it.
\n\n\n\n[00:13:16] Josepha: Next, we have a leap into 2024 with Site Editor tools. So, on the new Developer Blog, if you haven’t seen it yet, there is a lot of excellent content there for whether you are like an advanced developer in WordPress or you’re kind of intermediate and ready to move into your advanced developer era.
\n\n\n\nThe Site Editor will give you a powerful way to visually create every part of your site and tell your story. And this post will help you to kind of see how to handle everything from big style changes to simple copy updates, all in a single place. We want to make sure that you get the most out of your WordPress this year. And that post will give you a few standout tools and features that you’ll want to try.
\n\n\n\nYou’ll also want to keep an eye out for updates as we move into 2024 around team reps. So each team in the WordPress project goes through a process to review and elect team reps, and elections are happening now.
\n\n\n\n[00:14:12] Josepha: Along with things that are happening now that you should keep an eye on, the annual goals, our big picture post has gone out as well. It went out at the end of the week last week. There’ll be a link to all of these in the show notes. And yeah, keep an eye out for, hopefully, a fantastic 2024 in WordPress.
\n\n\n\nAnd that, my friends, is your small list of big things. Don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there’s a new episode. And if you like what you heard today, share it with a fellow WordPresser, or if you have questions about what you heard, you can share those with me at WPbriefing@WordPress.org. I’m your host, Josepha Haden Chomphosy. Thanks for tuning in today for the WordPress Briefing, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:14:57] (Music outro)
\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16745\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"Data Liberation in 2024\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wordpress.org/news/2024/01/data-liberation-in-2024/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 12 Jan 2024 16:58:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16736\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:314:\"Imagine a more open web where people can switch between any platform of their choosing. A web where being locked into a system is a thing of the past. This is the web I’ve always wanted to see. That’s why I announced a new initiative called Data Liberation for 2024. Migrating your site to WordPress, […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2885:\"\n
Imagine a more open web where people can switch between any platform of their choosing. A web where being locked into a system is a thing of the past. This is the web I’ve always wanted to see. That’s why I announced a new initiative called Data Liberation for 2024. Migrating your site to WordPress, or exporting all your content from WordPress, should be possible in one click. I want WordPress’ export format to become the lingua franca of CMSes, whether coming to WordPress or moving within WordPress.
\n\n\n\nI often hear about folks across the WordPress community duplicating efforts when creating scripts and workflows to move users to WordPress. Imagine if we shared those resources instead and built community-owned plugins that anyone could use!
\n\n\n\nBut it should be more than plugins; workflows, tutorials, and helper scripts should be shared, too. I want this resource to have space to include moving from social networks, moving from a page builder to core blocks, switching from classic to blocks, and improving WordPress current canonical plugins for importing.
\n\n\n\nOf course, the heart of any open source project is the community that shows up to build it. My hope is that this marks the start of a new contribution pathway, separate from core teams, that allows folks to contribute what they’ve learned and what they’ve created to help others move to WordPress. I expect this emphasis on migration will also influence future development, both in core and with recommended community or canonical plugins.
\n\n\n\nThere are a few things that I think will be key to making this project a success:
\n\n\n\nBy complementing the community’s existing efforts—the Five for the Future program, the Learn WordPress initiative, a focus on internationalization, etc.—my hope is that this will help even more people see themselves in the WordPress project, providing fresh momentum for WordCamps and meetups.
\n\n\n\nIt’s never been more crucial to champion openness on the web. Bringing focused attention to improved portability will untether users and increase their freedom like never before.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16736\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"WP Briefing: Episode 70: A Look Ahead at WordPress in 2024\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wordpress.org/news/2024/01/episode-70-a-look-ahead-at-wordpress-in-2024/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 08 Jan 2024 13:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16677\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:264:\"Curious about WordPress\'s big-picture items for 2024? Phase 3, Data Liberation, new meetups, and more, get the spotlight in this episode. Join Executive Director Josepha Haden Chomphosy for all this, plus a small list of big things coming up in the next two weeks.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:50:\"https://wordpress.org/news/files/2024/01/WP070.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:8342:\"\nCurious about WordPress’s big-picture items for 2024? Phase 3, Data Liberation, new meetups, and more, get the spotlight in this episode. Join Executive Director Josepha Haden Chomphosy for all this, plus a small list of big things coming up in the next two weeks.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Hello, my dears, and welcome to 2024. I hope you’ve had a lovely break. At the top of the year, I like to look around and gather the projects that the community is interested in. We can’t always commit to everything, and sometimes even the things we plan to do can’t make it across the finish line. In the next few weeks, I’ll be publishing kind of the big picture goals for the year, but I wanted to share a little bit about what I’ve collected so far.
\n\n\n\n[00:01:05] Josepha: Firstly, we’ve got Phase 3. This has been called a few things over the years: collaborative editing, multiplayer, co-editing. But whatever it’s been called, the biggest changes to writing and design workflows are likely to happen in this phase. A redesigned workflow can be a bit of a shock. But fortunately, we already have a prototype out there.
\n\n\n\nI’ll include a link to some resources in the show notes, or of course, you can always stop by make.WordPress.org/core for some insights. But I would encourage you to, at the very least, get your hands on that prototype to see what it looks like is coming in Phase 3 so that you can be aware and provide your feedback.
\n\n\n\nThe next thing on our list is Data Liberation. This is a new-to-us project that was introduced at State of the Word. Fortunately, though, it’s not a new concept overall. Data Liberation is actually one of the earliest ideas that sold me on WordPress. The idea that you could set up a site for a client, or yourself, and that hard work wasn’t lost if something went wrong, was really important to me. It’s been a long time since we put any effort into our importers and exporters, and I think this will be a good focus for the year.
\n\n\n\n[00:02:14] Josepha: The next thing that I’ve picked up, kind of a list of three things, but there are three mid-sized areas that I want us to pay attention to this year: plugins, old tickets, and new meetups.
\n\n\n\nPlugins, because they really have turned a corner on where they ended 2023. A lot of work has been done to make sure that they’ve streamlined some efforts, gotten some better onboarding for folks as they’re going in, and we could really use a hand to keep that momentum going.
\n\n\n\nOld tickets, because it’s something that we hope for year after year when we’re talking to people about what they want in new releases. So often, part of what they say is some way to work through all of these old things that have been around forever, some with patches. And why not, after all?
\n\n\n\nAnd then new meetups, because I really still think that meetups are the best intro to WordPress. No matter whether you’re wanting to become a developer eventually or, like, the community-building aspect is the thing that hooks you forever. Meetups are the place to encourage those and discover those.
\n\n\n\n[00:03:20] Josepha: The next thing on my list is also two things. It’s two things, but kind of a guess at the moment. There are two summit items that I want us to try to consider this year.
\n\n\n\nSo the first one is contributor recognition. Acknowledgment and recognition, I think, are two different things, and there was an entire series of sessions at the summit where we talked about it. And so I think that it’s worth us digging in on that.
\n\n\n\nThe other thing from the summit that I would really like us to all kind of dig in on is accessibility, how we do it, how we confirm it, what we think we should do versus what we actually do, and see what we can move on the needle there.
\n\n\n\nAnd the last thing is sort of a personal wish. I think it’s about time that we take a look at the way that we kind of manage ourselves as a project, the way that we do our meetings and report on our successes, things like that. And I realize that this is a big thing, and it might be a little bit scary. But, I mean, we’ve been doing this for a really long time, and it’s probably as good a time as any, frankly, to look at what we’re doing by habit or tradition and see if it still suits us.
\n\n\n\nSo, that’s my back of the napkin set of notes so far. Keep an eye out in the next couple of weeks for the annual Big Picture post so you can get some context, notes, and discussion opportunities. And, of course, anything that has shown up that’s a bit bigger, a bit more final will be in there as well.
\n\n\n\nBut first, our small list of big things.
\n\n\n\n[00:04:52] (Music interlude)
\n\n\n\n[00:05:00] Josepha: Firstly, State of the Word had nearly 200 questions submitted, and Matt has been answering the overflow on make.WordPress.org/project. So, I’ll include a link, but head on over there to that post if you would like to catch up on those.
\n\n\n\nAnd then the second item, and last item, is that you’ve got a few more days left to give us feedback on WordPress meetups in 2023, and give us an idea of what we can do to improve those. I believe those close on January 14th. I really love my local meetup, and I hope that we can get some of that same sort of feeling going in all of yours, too.
\n\n\n\n[00:05:33] Josepha: And that, my friends, is your small list of big things. Don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there’s a new episode. If you liked what you heard today, share it with a fellow WordPresser, or if you had questions about what you heard, you can share those with me at wpbriefing@WordPress.org.
\n\n\n\nI’m your host, Josepha Haden Chomphosy. Thanks again for tuning in for the WordPress Briefing, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:06:02] (Music outro)
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16677\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"The Month in WordPress – December 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2024/01/the-month-in-wordpress-december-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 05 Jan 2024 10:10:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:18:\"month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16680\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:331:\"As 2023 came to a close, WordPress bid farewell with the much-anticipated annual State of the Word and the 6.5 roadmap, among other exciting updates. Read on to learn more about the community’s end-of-year celebrations and catch a sneak peek of what’s in store for the year ahead. Highlights from State of the Word On […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Reyes Martínez\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:11236:\"\nAs 2023 came to a close, WordPress bid farewell with the much-anticipated annual State of the Word and the 6.5 roadmap, among other exciting updates.
\n\n\n\nRead on to learn more about the community’s end-of-year celebrations and catch a sneak peek of what’s in store for the year ahead.
\n\n\n\n\n\n\n\nOn December 11, WordPress co-founder Matt Mullenweg delivered his annual State of the Word keynote in Madrid, Spain, marking the first international edition of the event. Nearly 200 WordPress enthusiasts and tech industry leaders gathered in person to hear what’s next for WordPress—with a large audience joining online or from one of the 47 watch parties held across 18 countries.
\n\n\n\nThe keynote highlighted last year’s milestones and showcased compelling demos, providing a glimpse into the upcoming developments for the Site Editor, Collaboration phase, and Admin redesign. Matt also introduced 2024’s focus on Data Liberation, aiming to unlock digital barriers and frictionless migrations into WordPress for a more open web.
\n\n\n\n\n\n\n\nThe event concluded with a Q&A session and this follow-up post.
\n\n\n\n\n\n\n\nWordPress 6.5 is scheduled for release on March 26, 2024. This major release is set to introduce a new Font Library for easy global font management, support for Appearance Tools in Classic Themes, Data Views for templates and patterns, and more robust revisions across the editing experience, among other highlights.
\n\n\n\n6.5 will also include new APIs like Interactivity, Custom Fields, and Block Binding that expand block capabilities and underpin features like Synced Pattern Overrides.
\n\n\n\nLearn more about the features planned for WordPress 6.5 in this roadmap post.
\n\n\n\n\n\n\n\n\n\n\n\n\nDon’t wait for the next release to optimize your creative workflows with these powerful Site Editor tools.
\n
Two new versions of Gutenberg shipped in December:
\n\n\n\nHave a story we should include in the next issue of The Month in WordPress? Fill out this quick form to let us know.
\n\n\n\nThank you to Bernard Meyer, Nicholas Garofalo, and Lauren Stein for contributing to this edition of The Month in WordPress.
\n\n\n\nJoin other subscribers and receive WordPress news directly in your inbox.
\n\n\n\n Subscribe\n
\nThe Site Editor gives you a powerful way to visually create every part of your site and tell your story. It lets you handle everything from big stylistic changes to simple copy updates all in a single place. To help you make the most of this new way to WordPress, here are a few standout tools and features you’ll want to try.
\n\n\n\nThink of the Command Palette as the ultimate shortcut tool, letting you do more with less clicks and without needing to remember where each option might be. It’s available across the editing experience, whether you’re switching between templates in the Site Editor or toggling open settings in the Post Editor, with specific contextual options depending on where you are. You can use the keyboard shortcut Cmd+K on Mac or Ctrl+K on Windows to activate it and get started.
\n\n\n\nIf you think of a command that doesn’t exist yet that would help with your workflow, open a feature request issue so we can consider adding it.
\n\n\n\n\n\n\n\nRead more about everything you can do with the Command Palette, including a list of available commands.
\n\n\n\nThe Style Book helps you see all the blocks on your site as you style them. It’s built into the Styles section and can be toggled on/off as you’d like. This is especially useful when you’re aiming for design consistency for a client, trying to see how a change might impact a block that might not be visible, or wanting to get a different look at how a style variation will switch things up.
\n\n\n\nWork is also underway for the next WordPress release to integrate the Style Book into Style revisions to allow for an at-a-glance view of changes made.
\n\n\n\n\n\n\n\nLearn more about how best to use the Style Book.
\n\n\n\nSometimes you get a design just right—the color contrast, the perfect padding, the exact font size. Instead of needing to manually recreate the design or copy/paste the block to fill in with new content, you have two powerful options built into the editing experience: copy/paste styles and apply styles globally for all instances of the desired block.
\n\n\n\nCopying and pasting styles is perfect for more nuanced and smaller changes, like headings on a landing page that you intentionally want to be distinct. Applying changes globally is best for blocks like buttons and for changes that are likely to work well across layouts, like setting a specific border radius and color. This helps keep the creativity flowing and makes achieving design consistency across your site much easier.
\n\n\n\n\n\n\n\nRead more about the various styling options available.
\n\n\n\nJust like an artist might need to take a few steps back to view their in-progress artwork, sometimes we need to get a different view of our site before diving back in. Distraction free offers you that alternate perspective with a pared-down experience that lets you focus purely on creating, like:
\n\n\n\nIt’s worth noting that this mode can be used when writing posts and pages too! For an added bonus and more views of your site, you can use the preview options to see how your site might look across different devices.
\n\n\n\n\n\n\n\nLearn more about making the most out of Distraction free mode.
\n\n\n\nPatterns are a collection of blocks that make it simple to add complex layouts and designs to any WordPress site without starting from scratch. They save time by reducing duplication and ensuring consistency. You can create your own, use theme-provided patterns, or lean on the Pattern Directory.
\n\n\n\nYou can also specify whether to sync your patterns so that one change applies to all parts of your site, or to keep them unsynced so you can customize each instance. For any patterns you create, you can assign categories to make them easy to find and organize. Use the Inserter with easy filtering options to add patterns to your content, and head to the dedicated Patterns section in the Site Editor to create or edit patterns to your liking.
\n\n\n\n\n\n\n\nLearn more about creating patterns.
\n\n\n\nList View is the go-to tool for navigating between layers of your content, selecting exactly what you need, and getting a sense of how everything fits together. Similar to the Style Book and Distraction free mode, you can toggle it on/off as you’d like. It’s currently visible in the Top Toolbar and will remain open as you navigate through your site. Beyond providing a simple view of the layers of your site, there are more recent additions to List View that makes the tool even more powerful:
\n\n\n\nHere’s how a few of these improvements come together:
\n\n\n\n\n\n\n\nLearn more about using List View.
\n\n\n\nAs you explore these tools, remember that, except for the Style Book, you can use these features when writing posts and pages too. Expect the Site Editor and other tools to evolve with each release. To get a sneak peek at what’s planned for the next major WordPress release in March, check out the roadmap and stay tuned.
\n\n\n\nJoin other subscribers and receive WordPress news directly in your inbox.
\n\n\n\n Subscribe\n
\nThank you to the contributors who collaborated on this post: Nicholas Garofalo, Lauren Stein, Joen Asmussen.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16658\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WP Briefing: Episode 69: Reflections on State of the Word\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wordpress.org/news/2023/12/episode-69-reflections-on-state-of-the-word/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 26 Dec 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16654\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:232:\"In this episode, WordPress Executive Director Josepha Haden Chomphosy reflects on the recent 2023 State of the Word, which took place in Madrid, Spain, and some of the highlights of the work across the WordPress open source project.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:51:\"https://wordpress.org/news/files/2023/12/WPB069.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:10686:\"\nIn this episode, WordPress Executive Director Josepha Haden Chomphosy reflects on the recent 2023 State of the Word, which took place in Madrid, Spain, and some of the highlights of the work across the WordPress open source project.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@WordPress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: We wrapped up State of the Word earlier this month, and while I was sitting there being the only person to clap for the love of cake, I realized just how much we have been able to accomplish this year. And on the one hand, I shouldn’t be surprised.
\n\n\n\nAfter all, progress is radical over time yet incremental in time. But all told, 2023 has been a big year for WordPress. There’s been some radical progress in a few places. There are the things you know because you’ve heard them all year. You heard them in State of the Word.
\n\n\n\nWe turned 20, for instance. We shipped three on-time releases. We had three well-organized flagship events, and we prototyped essential parts of phase 3. But there’s a lot of work that happens outside of flagship events and software releases, and I’d like to highlight a few examples of operational excellence in our community and ecosystem.
\n\n\n\n[00:01:31] Josepha: First highlight goes to the contributors who are building community. Going back to 2021, we’ve been working to bring people back together in person.
\n\n\n\nAnd in that year, we had 19 events. In 2022, we had 24 events, so a modest increase of just over 30%. But then, in 2023, the WordPress community banded together on a campaign to reignite passion in our Meetup groups and encourage playfulness in our WordCamp planning. And not only did we see a 57% increase in active Meetup groups, But we also saw a 116% increase in WordCamps, 54 WordCamps in all. That’s about a third of the way to our all-time annual high of 142.
\n\n\n\nAnd to complement these in-person opportunities, Learn also shipped 104 pieces of new content and hosted 258 online workshops because location should never be a barrier to entry for joining WordPress.
\n\n\n\n[00:02:32] Josepha: Second highlight goes to the contributors who are managing our directories. We do have a lot of directories. We have Plugins, Themes, Photos, Block plugins. We got a lot.
\n\n\n\nAnd I’m sure that everyone saw the consistent and borderline pleading calls to join the Plugin team this year. And for folks who’ve been around a bit, you probably recall a similar set of consistent and pleading calls to join the Theme team a few years back. Concurrent with the work to refill that contribution pipeline, folks over in Meta and across the project generally, were working on automating as many checks as possible, loosening guidelines where it was reasonable, and modernizing as many processes as we could.
\n\n\n\nI’m happy to share that the theme wait time is at a historic low, with their longest wait sometimes just at a week. And as anxious as I am about the plugin wait times, we’re actually seeing a lot of progress there as well. As we follow a process similar to the one that we did on themes, I imagine it’s only gonna get better. So, in 2023, we’ve onboarded six new team members. And since September, the number of plugins awaiting initial review has been cut in half.
\n\n\n\nAnd then coming up in Q1 of 2024, we’ll have a project focused entirely on automating as many checks as possible. So I still need you, but I also need you to know that your work there matters and is having an impact.
\n\n\n\n[00:03:55] Josepha: The third highlight goes to the contributors who are doing outreach. This year, we launched a mentorship program with an 89% completion rate because we’ve seen time and again that our most prolific contributors had someone at the start that they felt safe asking dumb questions with. We launched and nurtured the developer blog, which was a need identified by the community because there was no place for intermediate and advanced developers to get excited about their cool explorations. And there were 53 posts there this year with thirteen thousand views, which is a 251% increase for the record, which is a ridiculous increase, but it’s a lot. Thirteen thousand views is a lot.
\n\n\n\nWe have focused on documentation as we suggested in Porto of 2022. And marketing, I know not always our favorite topic, but marketing, our ability to talk about ourselves to more than just ourselves, has increased dramatically this year.
\n\n\n\nNot only have we started rolling out a modern design across our website, but we also are present and engaged on eight different platforms with 20-plus episodes of this very podcast and also video content that netted us seven and a half million views this year. That’s a lot of numbers, and there’s a post that goes with it.
\n\n\n\n[00:05:10] Josepha: Check out the show notes. But if you’re not gonna check out the show notes because you listen to this on Pocket Casts or Google or something, go to make.WordPress.org/project, and it’ll be over there. But the point is, it’s been a banner year for the software, and I am grateful for every tester, designer, and developer that showed up for it. But I also know that what makes WordPress truly irreplaceable is our ecosystem, and it’s contributions like this and the contributors who do them that make our ecosystem vibrant and responsive and thriving on into the future.
\n\n\n\nSo, thank you all for the contributions you make to WordPress. Thank you for the shining example of how to do open source at scale, and thank you for another great year together.
\n\n\n\n[00:06:04] Josepha: Which brings us now to our small list of big things. It is indeed a small this time. First up, I would like to introduce our enhanced content safety features on Openverse. By default, search results now exclude openly licensed media containing sensitive textual content. But this new feature adds additional filtering based on titles, tags, and descriptions of the work as well.
\n\n\n\n[00:06:27] Josepha: The second thing on our small list of big things is that there is just a general alert. There’s a WordPress security team impersonation scam that’s going on out there. The team is aware of multiple ongoing phishing scams impersonating both the WordPress team and the WordPress security team in an attempt to convince administrators to install a plugin on their website which contains malware. I’ll include a link to that post just in case you have anyone that you think might need to be aware of that, but also all of our site administrators know. Like, WordPress is not gonna email you asking for passwords or anything ever.
\n\n\n\n[00:07:02] Josepha: And item number three, I would like you to join the Plugin review team. I know I just said it in the body of the episode. But, the Plugin review team is looking for new members still who believe in our mission of guiding plugin authors in responsibly transforming their innovative ideas into reality and ensuring a great WordPress plugin experience for end users. There is a deadline to apply; it’s December 31st. And so you can get that done over the holidays, over a glass of eggnog if that’s how you choose to celebrate whatever it is that you do.
\n\n\n\nAnd that’s it for your small list of big things.
\n\n\n\nDon’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there’s a new episode. If you liked what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard, you can share those with me at wpbriefing@WordPress.org. I’m your host, Josepha Haden Chomphosy. See you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16654\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"State of the Word 2023 Recap\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://wordpress.org/news/2023/12/state-of-the-word-2023-recap/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 11 Dec 2023 22:55:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:17:\"state of the word\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16617\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:384:\"On December 11, WordPress co-founder Matt Mullenweg traveled to beautiful Madrid, Spain, to deliver his annual State of the Word keynote. It was the first time this event took place outside the United States. Against the backdrop of Palacio Neptuno—an iconic architectural gem and UNESCO World Heritage site—nearly 200 contributors, developers, extenders, and friends of […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Nicholas Garofalo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:20461:\"\nOn December 11, WordPress co-founder Matt Mullenweg traveled to beautiful Madrid, Spain, to deliver his annual State of the Word keynote. It was the first time this event took place outside the United States. Against the backdrop of Palacio Neptuno—an iconic architectural gem and UNESCO World Heritage site—nearly 200 contributors, developers, extenders, and friends of the project came together to hear from Matt, with millions more joining online.
\n\n\n\n\n\n\n\nKicking off the event, Josepha Haden Chomphosy, Executive Director of the WordPress project, spoke about the community’s heart and spirit as what fuels hope for the future, ensuring the freedoms of the open web for all. She invited Matt on stage with a closing statement of confidence that such values and characteristics will move the project forward into the next 20 years as it has for the last 20.
\n\n\n\n\n\n\n\nTaking the stage, Matt shared his excitement about the event being the first international State of the Word. He honored the Spanish WordPress community for hosting, citing their past WordCamp accomplishments. From there, Matt jumped right into a reflection of this year’s notable moments. He recalled the project’s 20th-anniversary celebrations, how the software has evolved, and how much more the community came together this year—doubling the number of WordCamps to 70, taking place in 33 countries.
\n\n\n\nWe’re always aiming to learn and improve. Tell us how to make meetups better.
\n\n\n\n \nMatt continued with callouts to several resources on WordPress.org: the all-new Events page, the redesigned Showcase, a new WordPress Remembers memorial, and the award-winning Openverse. He also demoed WordPress Playground, a tool allowing users to experiment with WordPress directly in their browsers, as well as the versatile Twenty Twenty-Four default theme.
\n\n\n\n\n\n\n\nMatt recapped the four phases of the Gutenberg project, noting that work has begun on Phase 3: Collaboration before passing the microphone to Matías Ventura, Lead Architect of Gutenberg.
\n\n\n\nAfter a quick interlude in Spanish, Matías acknowledged how much progress had been made on the software this year. He spoke about the aim of the Site Editor to become both an exemplary writing environment and a superior design tool while noting improvements to the Footnotes Block and the ease of Distraction Free mode.
\n\n\n\nWhile there was no set timeline for collaboration and workflows, Matías was excited to share a working prototype in the Editor. He showcased some of the most interesting aspects of collaborative editing, including establishing a sync engine that allows real-time edits to be visible across sessions. He invited contributors to test the prototype in the Gutenberg plugin and share their feedback in Github.
\n\n\n\nFrom there, Matías highlighted other exciting developments, including the emphasis on Patterns and their continued evolution as a powerful tool for workflows, and the ability to connect blocks to custom fields. He was thrilled to speak about performance improvements, noting that work is in progress to make the Editor at least twice as fast. Speaking about front-end performance, he shared what’s to come with a demo of the Interactivity API, showcasing how it can make transitions, search, and other interactions instant—all with standard WordPress blocks and features.
\n\n\n\nMatías concluded with a look at how the Admin redesign will take cues from the Site Editor, eventually allowing users to shape their WordPress Admin experience based on their unique needs.
\n\n\n\n\n\n\n\nMatt returned to the stage to expand on the future of WordPress, reinforcing his past advice to learn AI deeply. He expressed his excitement about what can be accomplished with the wealth of AI tools available, how contributors are already experimenting with natural language processing and WordPress Playground to create and build.
\n\n\n\nFinally, Matt introduced an additional focus for the project in 2024: Data Liberation, with the goal to make importing from other platforms into WordPress as frictionless as possible. He spoke about the tendency of content management systems to keep users locked in as part of his motivation to unlock digital barriers. The Data Liberation initiative will work on one-click migration and the export format from WordPress.
\n\n\n\nMore than just tools, Data Liberation reflects the project’s ethos to allow seamless contributions. With that, Matt invited anyone interested to jump into the action, noting a new Data Liberation GitHub repository and forthcoming Making WordPress Slack channels as places to get started.
\n\n\n\nFollowing the presentation, Matt fielded questions from the live-stream and in-person audiences during an interactive question-and-answer session hosted by Jose Ramón Padrón (Moncho).
\n\n\n\n\n\n\n\nAdditional questions from the live session will be answered in a follow-up post on make.WordPress.org/project. Subscribe to our blog notifications to be sure you don’t miss it. And don’t forget to mark your calendars for next year’s WordCamp Asia (Taipei, Taiwan), WordCamp Europe (Torino, Italy), and WordCamp US (Portland, Oregon, United States).
\n\n\n\n\n\n\n\nThank you to @laurlittle, @eidolonnight, @nilovelez, @fepr, @cbringmann, and the many others who made this event and post possible.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16617\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WP Briefing: Episode 68: Toward a More Interconnected Web\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wordpress.org/news/2023/12/episode-68-toward-a-more-interconnected-web/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 11 Dec 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16569\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:235:\"In this episode, WordPress Executive Director, Josepha Haden Chomphosy articulates the vision for a collaborative ecosystem where knowledge sharing and contributions to open source tools lead to a more interconnected and empowered web.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:51:\"https://wordpress.org/news/files/2023/12/WPB068.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:14552:\"\nIn this episode, WordPress Executive Director, Josepha Haden Chomphosy articulates the vision for a collaborative ecosystem where knowledge sharing and contributions to open source tools lead to a more interconnected and empowered web.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@WordPress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: If you’re already familiar with the WordPress project, and if you’re listening to this podcast, I feel like it’s a safe assumption that you’re probably also familiar with the fact that we are what’s considered a free and open source software project. We adhere to the four freedoms of open source. We track bugs in the open, and we believe that knowledge sharing can only improve our products.
\n\n\n\nBut you might not be aware of the other open source projects that are foundational to ours and otherwise are integral to our commitment to the open web. At last year’s State of the Word, Matt mentioned that one of the coolest things about being a plugin or theme author in WordPress is that you get to run your open source project on the same infrastructure that WordPress runs on. So, no matter whether you have five installs or five thousand, you’re getting the benefits of our bug trackers, messaging, and network of project sites. But beyond those, which are, of course, near and dear to us, we also support projects like PHP and its foundation. Openverse and its founding organization Creative Commons, and of course, the two that we’re hearing a lot about this year and next, Playground and Matrix.
\n\n\n\n[00:01:52] Josepha: That’s a lot of projects and not even a comprehensive list. And honestly, it can seem, I don’t know, a little weird. Like, we’re a FOSS CMS, right? You probably know why we contribute back to PHP. It’s the same reason we ask people to contribute to WordPress. But why are we giving so much time to a media search engine, or a Web Assembly implementation, or even a messaging protocol?
\n\n\n\nAt first glance, there are, of course, a lot of quick and easy answers. For instance, like, open source is open source. Any open source contribution is going to be a good contribution. All open source in the world increases good and freedom in the world. Like, open source is open source. Makes sense, right?
\n\n\n\nAnother quick and easy answer is, you know, they’re part of us. And that’s true, definitely, for PHP, like, they’re part of us, and so we should be contributing back to them. Because we rely on them so much. And then a third quick and easy answer is that we, as the biggest open source CMS on the planet, basically, we can, spare a lending hand. We can offer a little bit of help to those around us.
\n\n\n\n[00:03:03] Josepha: And those are all true. I don’t think that anyone would disagree with any of that. But the thing that ties it all together for me is something that’s a little harder to see. In the 2022 goals that I posted, I said that my second goal for our year was to support open source alternatives for all site-building necessities.
\n\n\n\nAt the time, I was primarily talking about Openverse and the directory of photos that was being created as a CC-first source. But that also applies to all of our directories. It did then, just as it does now. And Trac, and our vast network of WordPress sites. All the tools we use in order to collaborate with, and lead for, and learn from each other.
\n\n\n\nI want us to be able to do everything it takes to build an online presence using open source tools and methods because WordPress is just a glorious little microcosm of the interconnected web. It reminds me of this art installation I had the privilege of experiencing. It’s called Meow Wolf. I went to the one in Denver, but there are a few different installations across the U.S. The one that I went to is this massive art installation, and it is designed to be interactive, but it wasn’t until you started sharing your experience sharing your knowledge with other people that you realized it was also collaborative, a set of buttons you pushed in one room would cause a light show in some other room.
\n\n\n\n[00:04:34] Josepha: So you were enhancing the experience of strangers in some completely disconnected room to yours, and they couldn’t distinguish it from an automation or something they did, or just plain old magic. And that’s what we’re doing by supporting these other open source tools. Yes, every new open source contribution results in more freedom in the world. Yes, we owe support to the components that got us where we are today. And yes, we absolutely can and should pay it forward. But more importantly than all that, we’re creating the opportunity for new interactions, new brilliance, and new defenders of the open web every time that we work on these open source products.
\n\n\n\n[00:05:20] Josepha: And it doesn’t matter if we will ever see any of those people. And it doesn’t matter if they will ever thank us. What matters is that we see that knowledge like this is worth preserving and worth sharing. Because knowledge shared, information shared is like light. The more you share it, the more there is.
\n\n\n\nAnd I want you to be able to take that sharing and use it to light the world. I want you to be able to go out and tell people how open source has changed your life, how WordPress has opened doors for you, or how much these tools have empowered your clients. I want you to remember why you came to WordPress in the first place, and I need you to hear me when I say that I need you here in WordPress today because every little ripple of good that we create makes the world a little more good.
\n\n\n\n[00:06:12] (Music interlude)
\n\n\n\n[00:06:20] Josepha: (SLBT) And now, my friends, that brings us to our time for the small list of big things. I’ve got a kind of a big list because I always kind of have a big list anymore, but the first thing on my list is Gutenberg 17.1. That has been released and is available for download. It includes several new enhancements, loads of bug fixes, and continues that work on phase three features that we are starting to see come through. If you don’t have it already, go out and grab it, test it, break it, and tell us what you tested and how it broke things.
\n\n\n\n[00:06:52] Josepha: The second thing on my small list of big things is that there is currently an annual meetup survey out. So, we’ve had an increase in our meetup events, and certainly an increase in the active number of meetup groups that we have, but the community team is proposing a unified survey for all meetup members and organizers, and if you haven’t participated in it yet go and fill it out. You don’t have to have actually gone to a meetup event recently in order to take it, but, you know, it might be helpful. Either way, you have until January 14, 2024, to fill that out.
\n\n\n\n[00:07:30] Josepha: The third thing on my small list of big things is a request for feedback. The training team is working toward launching Learning Pathways in 2024. They’re looking to create a new set of content creation guidelines that enables the learning pathways to scale with a straightforward process for developing, reviewing, and updating that content. There’s a Google doc for you where you can contribute your ideas, and that doc will be open for feedback through this week and into next week. I believe it closes on Tuesday, the 19th of December, 2023.
\n\n\n\n[00:08:04] Josepha: And then the final thing on my small list of big things is actually, it’s a dual call-in. I already said with my first one about the Gutenberg plugin: get in there and test it and break it, and then tell us how it broke and what you were doing when you were testing it and broke it. And I encourage you to do that also for Matrix and Playground.
\n\n\n\nSo Playground has been a really big deal all year long. It was a big deal at the end of last year. It showed up for us in November 2022 and has been really just growing in surprising ways all the way through 2023. So if you have not yet seen it, you haven’t gotten your hands on it yet, it’s a WordPress installation that is loaded entirely in the browser, totally server-free, and we’re looking at a couple of new implementations that make it easier for users who are trying to, like, kick the tires of WordPress before they decide, and developers who are wanting to test new pull requests and things like that.
\n\n\n\nSo keep an eye out if it sounds interesting; it is interesting. And wander over and figure out how that’s working. And the other thing in that last call for collective testing is Matrix. So Matrix is an open source federated messaging protocol, and like so many technology projects out there at the moment, we are trying to make sure that we are preparing ourselves for the future arrival of Web 3 and all of the things that are coming along with current advancements in federated everything and AI and etc., etc.
\n\n\n\nAnd so, Matrix is an open source messaging protocol. There are a lot of different ways to get connected. I’ll share a link to one of the posts in the show notes over on WordPress.org/news. But if you’re interested in learning a bit about it and you don’t really want to like figure out what sort of client is comfortable for you to use. There’s also on-site chat implementations for, I want to say, like 10 or 12 of our largest or most regularly meeting groups that we have. You can go to parts of the website like make.WordPress.org/core/chat and check those out. If you have a WordPress.org account, then you can have access to that on-site chat, and that is it.
\n\n\n\nThat’s the whole low barrier to entryway of figuring that out with us. Come and break stuff with us, everyone, and tell us how to make it better.
\n\n\n\n[00:10:33] Josepha: And that, my friends, is your small list of big things. Don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there’s a new episode. If you liked what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard, you can share those with me at wpbriefing@WordPress.org. I’m your host, Josepha Haden Chomphosy. Thank you for tuning in today for the WordPress Briefing, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:11:00] (Music outro)
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16569\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"The Month in WordPress – November 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2023/12/the-month-in-wordpress-november-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 08 Dec 2023 11:20:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:18:\"month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16575\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:251:\"November is usually a busy month for the WordPress project, and this year is no different. Following the empowering release of WordPress 6.4, the energy continues to build, setting the stage for the anticipated State of the Word and upcoming projects.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Reyes Martínez\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:11827:\"\nNovember is usually a busy month for the WordPress project, and this year is no different. Following the empowering release of WordPress 6.4, the energy continues to build, setting the stage for the anticipated State of the Word and upcoming projects.
\n\n\n\nRead on for all the exciting updates that marked the past month.
\n\n\n\n\n\n\n\nMark your calendars—State of the Word 2023 is approaching fast. In this annual keynote, WordPress co-founder Matt Mullenweg celebrates the progress of the open source project and offers a glimpse into its future.
\n\n\n\nFor the first time in WordPress history, the event will be held outside North America, in the vibrant city of Madrid, Spain, on December 11, 2023.
\n\n\n\nIf you’re unable to attend the State of the Word in person, you can watch it live on the WordPress YouTube channel or join one of the many community-led watch parties. Find one near you or organize one.
\n\n\n\n \n\n\n\n\n\n\n\nAlong with the release of WordPress 6.4 “Shirley,” the new default Twenty Twenty-Four theme was introduced.
\n\n\n\nThis theme breaks away from the tradition of previous default themes that focused on a specific topic or style. Instead, Twenty Twenty-Four was created to fit any website and explore different use cases for entrepreneurs, artists, and writers.
\n\n\n\nYou’ll find more than 35 beautiful patterns, including full-page patterns for templates like homepage, search, and more. Twenty Twenty-Four boasts the latest site editing capabilities and a sophisticated aesthetic inspired by contemporary design trends.
\n\n\n\n \n\n\n\n\n\n\n\nHave a story we should include in the next issue of The Month in WordPress? Fill out this quick form to let us know.
\n\n\n\nThank you to Bernard Meyer for contributing to this edition of The Month in WordPress.
\n\n\n\nJoin other subscribers and receive WordPress news directly in your inbox.
\n\n\n\n Subscribe\n
\nThis minor release features 7 bug fixes in Core. The fixes include a bug fix for an issue causing stylesheet and theme directories to sometimes return incorrect results.
\n\n\n\nThis release also features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
\n\n\n\nYou can download WordPress 6.4.2 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.
\n\n\n\nWordPress 6.4.2 is a short-cycle release. The next major release will be version 6.5 released in early 2024.
\n\n\n\nFor more information on this release, please visit the HelpHub site.
\n\n\n\nThe security team addressed the following vulnerability in this release.
\n\n\n\nTo help the security team and WordPressers around the world, you are encouraged to responsibly report vulnerabilities. This allows vulnerabilities to be fixed in future releases.
\n\n\n\nThis release was led by Aaron Jorbin.
\n\n\n\nWordPress 6.4.2 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance and security fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\n\nAaron Jorbin, Aki Hamano, Akira Tachibana, Alex Concha, Angela Jin, Anton Vlasenko, Barry, bernhard-reiter, Caleb Burks, Corey Worrell, crstauf, Darren Ethier (nerrad), David Baumwald, Dennis Snell, Dion Hulse, Erik, Fabian Todt, Felix Arntz, Héctor Prieto, ironprogrammer, Isabel Brison, Jb Audras, Jeffrey Paul, Jessica Lyschik, Joe McGill, John Blackbourn, Jonathan Desrosiers, Kharis Sulistiyono, Krupal Panchal, Kylen Downs, meta4, Mike Schroder, Mukesh Panchal, partyfrikadelle, Peter Wilson, Pieterjan Deneys, rawrly, rebasaurus, Sergey Biryukov, Tonya Mork, vortfu
\n\n\n\nTo get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core. Need help? Check out the Core Contributor Handbook.
\n\n\n\nAs a final reminder, The WordPress Security Team will never email you requesting that you install a plugin or theme on your site, and will never ask for an administrator username and password. Please stay vigilant against phishing attacks.
\n\n\n\nThanks to @angelasjin and @desrosj for proofreading.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16562\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:12:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Sun, 28 Jan 2024 15:14:46 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:25:\"strict-transport-security\";s:12:\"max-age=3600\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Mon, 22 Jan 2024 12:00:00 GMT\";s:4:\"link\";s:63:\"You tear me apart. The greatest city in the world. (San Francisco has its allure.) I am so drawn to the impeccability excellence of uptown. Just at a baby shower at 111 West 57th… wow! You have never seen a better building, everything is executed to the highest degree par none.
\n\n\n\nYet, I’m so drawn to downtown. The jazz. The creativity, the spark, the drive.
\n\n\n\nAutomattic’s office at 166 Crosby feels like a creative center. We’ve built something pretty cool there to inspire and delight people in space.
\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 27 Jan 2024 20:33:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"Gutenberg Times: Dynamic Blocks, WordPress for Enterprise and Attachment Templates — Weekend Edition 282\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=27116\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:112:\"https://gutenbergtimes.com/dynamic-blocks-wordpress-for-enterprise-and-attachment-templates-weekend-edition-282/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:15950:\"Howdy,
\n\n\n\nPart of life is change and adjustment to new situations, and being adaptive is a skill that needs to be practiced. It’s never easy. For my personal life as well as for web development, when I am entrenched in the minutia of change, and it drags me down, I stop and get to a higher level and reminder myself about Wabi Sabi and marvel at the impermanence, the imperfections and the incomplete state of things and of life, really. In other words, nothing is finished, nothing is perfect and nothing lasts. Ever.
\n\n\n\nIn that sense, we are all learners, and the best way to learn from another is by experimenting, building, using and developing on top of open source. and share learned lessons and processes with others.
\n\n\n\nBelow you’ll find fabulous links to articles that teach, and share. Enjoy!
\n\n\n\nYours, 💕
Birgit
Anne McCarthy published another post in the series of Core Editor Improvement about the Robust revisions feature in the Site Editor coming to WordPress 6.5. Revisions now show a summary of changes, and consistent pagination. They are also available in the context of the Stylebook, and allow for redo and undo functionality. All the features help designers to trust the site editor to build from scratch and not loose designs, just because one changes their minds about things.
\n\n\n\n🎙️ Latest episode: Gutenberg Changelog #95 – Gutenberg 17.5, Early Testing of WordPress 6.5 and Block Themes with special guest: Carolina Nymark
\n\n\n\nJoen Asmussen shared in his bi-weekly update post about the work by members of the WordPress Design team. There are quite some interesting projects and discussion.
\n\n\n\nThe early discussion around how states might provide a UI for anything from animation over pseudo states, to perhaps even responsive editing seems to be the one that needs the biggest input from users, designers developers. It’s happening on GitHub and could use your feedback, too.
\n\n\n\n\n\n\n\nMatt Mullenweg was interviewed by the host of WP Tonic, Jonathan Denwood & Kurt von Ahnen, on Gutenberg, and the state of WordPress Community and open-source.
\n\n\n\n\n\n\n\nNathan Wrigley discussed in the 106th episode of the Jukebox podcast with Anil Gupta on the Challenges Posed by Multi Collaboration in WordPress. “Anil talks about how his team at Multidots decided to tackle this problem for their plugin, and he explains some of the hurdles they’ve experienced along the way. They’ve taken a cautious approach, developing different features one at a time, working through the technical challenges with commenting, before moving onto real-time editing. ” Listening to this episode is quite fascinating as it brings listeners into the headspace of real-time collaboration and upcoming Phase 3 of the Gutenberg projects.
\n\n\n\nChuck Grimmett redesign his website and walks you through the process in the post 2024 Redesign. Based on a child theme of Twenty-Twenty-four and with the help of the create-block theme plugin, Grimmett went to work to set up template parts, templates, and patterns for this tie. What I found also helpful is the list of resources and inspiration for the next iteration of Grimmett’s website.
\n\n\n\nNick Diego announced the new version of the Block Visibility plugin (3.3.0) with a few improvements. Among them, a nod towards the ACF (Advanced Custom Fields) Pro users, as fields stored in options pages are now supported by the plugin. It also offers some Author controls as well a Demo link to load it into a WordPress Playground instance.
\n\n\n\nAlex Aspinall, head of marketing at HumanMade, shared the links to the recording of last week’s WordPress for Enterprise event:
\n\n\n\nYou can also hop on YouTube directly and watch the recordings from the Playlist
\n\n\n\nTammie Lister started a new site: Editortips.com, a site with frequently to do with the WordPress block and site editor. The site already sports information about the Style Book, Style Revisions, how to switch moved and add custom color. If you haven’t worked with the site editor before, bookmark the site or, better yet, add it to your feed reader’s list.
\n\n\n\nBuddy Boss has launched Reactions Feature, allowing users to visually interact with the content through various reaction icons. This kind of interactivity is also coming to the block editor with the Interactivity API in WordPress 6.5.
\n\n\n\nBjarne Oldrup posted Improve block editor UX with MRW Simplified Editor, using the plugin my Mark Root-Wiley that allows site builders to make the Block Editor user experience better with cleaner options.
\n\n\n\nThe last three news items were brought to you be Davinder Singh Kainth, publisher of the WP Weekly newsletter, a must-read for any WordPress professional.
\n\n\n\nJustin Tadlock published Building dynamic block-based attachment templates in themes. “Love ‘em or hate ‘em, attachments are a reality of theme development, especially if you are publicly distributing your theme. Just because they are disabled for new installations doesn’t mean that there aren’t millions of WordPress sites that still have them turned on or that new users won’t enable them.” he wrote.
\n\n\n\nEmily Rapport wrote about her journey From Builder to Blocks: A Rebuild Experiment on her blog. “Rebuilding in the site editor this year was an opportunity for me to explore (and learn) what might be possible in a block theme on a “real” website. ” she wrote. You’ll learn about her working out the right approach and the tools she used, among those the Create-Block-Theme plugin. Rapport made clear that it took a a major shift in her mental model to be to grasp the difference between writing CSS in a file and using the site editor to store changes to the design in the database. I also found it quite an interesting read to learn, what exactly is still missing from block theme development via the site editor: (current page styling, custom CSS, landmarks and display of custom fields.)
\n\n\n\n\n “Keeping up with Gutenberg – Index 2022”
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2021 on. Updated by yours truly. The index 2020 is here
Brian Coords published a video and blog post on How to Build Dynamic (PHP) Blocks in WordPress. “Along the way we’ll discuss the difference between static and dynamic blocks, when to use them, WP_Query, what ServerSideRender is and what the best approach for performance is.” Coords wrote.
\n\n\n\nIf you need an additional resource on the difference between static and dynamic blocks, you can also learn about it from Joni Halabi’s post on the Developer Blog Static vs. dynamic blocks: What’s the difference?
\n\n\n\nThomas Roberts shared in his monthly WooCommerce Blocks Extensibility Snaps about the Additional Checkout Fields Progress, and ways to collect and display contact information.
\n\n\n\n\nRequire a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph.
\n\n\n\nFor questions to be answered on the Gutenberg Changelog, send them to changelog@gutenbergtimes.com
\n\n\n\nFeatured Image: CC0 licensed photo by KafleG from the WordPress Photo Directory.
\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nAki Hamano is from Tokyo, Japan. Several years ago he found a flaw in Gutenberg and submitted a patch for just four characters. Now he is a Gutenberg Core Contributor.
\n\n\n\nI was so excited to imagine that the code I had written, even though it was just a small change, would become part of WordPress itself and be spread around the world.
\n\n\n\nAki’s essay is available on HeroPress.com.
\nThis week’s WPPhotos Info is called “Free to fly“.
\n\n\n\nBigul Malayi was able to catch this rare owl at his sister in law’s house, one Sunday in Kerala, India.
\n\n\n\nUnlikely, he added, this type of owl is traded in black market – https://wildlifesos.org/chronological-news/wildlife-sos-seizes-barn-owl-in-gujarat-raid/
\n\n\n\n\nThere were twenty-six WordPress podcast episodes released this week!
\n\n\n\nThere are new episodes every single day, so be sure to stop by WPPodcasts.com and search for things that interest you!
\nHere are some of the great photos submitted to the WPPhotos project this week!
\n\n\n\n\nCC0 licensed photo by Jonathan Desrosiers from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Jonathan Desrosiers from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Jamie VanRaalte from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by quizzycal from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Topher from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Bigul Malayi from the WordPress Photo Directory.\n\n\n\n\nBe sure to check out the hundreds of other great photos!
\nThe header photo for this post is a CC0 licensed photo by mahfuznafi from the WordPress Photo Directory.
\n\n\n\n\n\n\nThat’s it for this week! If you’d like to get this post in your email every week, make sure you sign up!
\n\nThe post Changing WordPress Core By Four Characters appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 26 Jan 2024 17:42:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"Do The Woo Community: Do the Woo is an Official Media Partner at CloudFest 2024\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78954\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://dothewoo.io/do-the-woo-is-an-official-media-partner-and-cloudfest/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:404:\"Do the Woo will be covering both the hackathon and the conference during CloudFest 2024 at Europa-Park in Germany.
\n>> The post Do the Woo is an Official Media Partner at CloudFest 2024 appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 26 Jan 2024 11:36:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"Do The Woo Community: Woo Feature Request Board and WooCommerce Plugins for Sale\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78945\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://dothewoo.io/woo-feature-request-board-and-woo-plugins-for-sale/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:427:\"In WooBits I amplify a hidden feature request board on Woo.com and 5 WooCommerce premium plugins for sale by our host Katie Keith at Barn2.
\n>> The post Woo Feature Request Board and WooCommerce Plugins for Sale appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 26 Jan 2024 08:46:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"Do The Woo Community: The Importance of Product Testing in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78926\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"https://dothewoo.io/importance-of-product-testing-in-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:390:\"WordPress contributors Pooja, Brian and Anand discuss how product testing is crucial and the learning process behind it.
\n>> The post The Importance of Product Testing in WordPress appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 25 Jan 2024 08:33:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"BuddyPress: BP Classic 1.3.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=332939\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://buddypress.org/2024/01/bp-classic-1-3-0/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2102:\"Dear end users & site owners,
\n\n\n\nPlease note BP Classic 1.3.0 is now available for upgrade/download. 1.3.0 is a maintenance release of the BuddyPress backwards compatibility Add-on helping you to stay classic so that you can carry on:
\n\n\n\n4 issues have been fixed:
\n\n\n\n[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name. Is Nathan Wrigley.
\n\n\n\nJukebox has a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, advocating for accessibility and diversity in the WordPress community.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you, and hopefully get you, or your idea, featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox, and use the form there.
\n\n\n\nSo on the podcast today we have Michelle Frechette.
\n\n\n\nThis is going to sound like a lot, and that’s because it is.
\n\n\n\nMichelle Frechette is the director of community engagement for StellarWP at Liquid Web. She was called the busiest woman in WordPress by Matt Mullenweg at WordCamp US 2022. She is also the host of the WP Coffee Talk Podcast, co-founder of Underrepresented in Tech creator of WP Speakers and WP Career Pages, president of the board for Big Orange Heart, Director of Community Relations and contributor at Post Status, co-host of the WP Motivate and Audacity Marketing Podcasts, host of the WP Constellations Podcast, author, and frequent organizer and speaker at WordPress events. Michelle lives outside of Rochester, New York, where she’s an avid nature photographer. You can learn more about Michelle at meetmichelle.online.
\n\n\n\nYou see, like I said, that’s a lot.
\n\n\n\nThis willingness to engage in all manner of WordPress projects has given Michelle a voice. And she’s on the podcast today to discuss a topic which is close to her heart. Diversity equity, inclusion and belonging.
\n\n\n\nShe talks about her experiences at WordPress events, and how they were not always easy for her to attend and be a part of. Michelle uses a scooter to get around, and there have been situations in which she could not enter venues and access all the facilities.
\n\n\n\nThis frustration made her take action, and, as you’ll hear, effect change at subsequent event she attended.
\n\n\n\nIt’s not all about events though. Michelle talks about the wider goals of making all aspects of the WordPress community more open and inclusive.
\n\n\n\nBeing one of the voices promoting this message has not always been easy. And we hear about how Michelle copes with those who disagree with her quest to create change.
\n\n\n\nIf you’re interested in thinking about inclusivity and how embracing diverse perspectives can impact the WordPress community, this episode is for you.
\n\n\n\nIf you want to find out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast, where you’ll find all the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Michelle Frechette.
\n\n\n\nI am joined on the podcast by Michelle Frechette. Hello Michelle.
\n\n\n\n[00:03:40] Michelle Frechette: Hi Nathan, how are you?
\n\n\n\n[00:03:41] Nathan Wrigley: I am very good. Michelle has been called the busiest woman in WordPress, I think that’s the right wording, by Matt Mullenweg. And if I was to read out her bio, which I’m not going to do, I’ll let Michelle introduce herself. You would have some understanding of why that happened.
\n\n\n\nSo I’m going to give you an opportunity right at the beginning, you can go as deep as you like, Michelle. Give us your bio, give us your story about your relationship with WordPress, and the different projects that you are in, before we begin our conversation.
\n\n\n\n[00:04:09] Michelle Frechette: So my day job, I always feel like a superhero when I say that. By day I am the Director of Community Engagement for StellarWP, and all of our plugins and themes, that are part of that company at Liquid Web. And my external projects though, are the ones that I think you are more interested in talking about today, perhaps.
\n\n\n\nWhich are things like WP Career Pages, WP Speakers, and underrepresentedintech.com. So a lot of the side projects that I do, and the things that I do within the WordPress community, really are community oriented projects that are to help others find their footing and move forward in the work that they want to do within WordPress, and within the WordPress community. So I really enjoy doing those kinds of things.
\n\n\n\n[00:04:52] Nathan Wrigley: How did you discover WordPress?
\n\n\n\n[00:04:55] Michelle Frechette: Oh, that’s a good story actually. It has to do with spaghetti. So actually, one of my best friends and I, we had started a nonprofit together. I was working at a massage school, as the director of the massage school. She was a massage therapist, and graduate of the program. And she came to me and she said, after a thousand hours of working in this program, you graduate, you take an exam, and then you’re just on your own spinning in the wind. Because you really have no idea how to build a business, how to get clientele, all of these things. You know how to do massage, but that’s about it.
\n\n\n\nAnd so we started a nonprofit to help massage therapists actually have careers. So we did classes, we had, you know, meetings. We did all of these different things, special education and continuing education, those kinds of things. And so we decided we needed a website, and her husband was a WordPress developer.
\n\n\n\nSo he created this beautiful website for us. And so we started sending him content. And he’s like, hold up ladies, no. These are your logins, you log in and you put your content in. I built you the frame. Have fun. I was terrified. I like logged in and I thought, what button am I going to press that’s going to make the whole thing come crashing down? And I’m going to have to say to him, I broke this site.
\n\n\n\nBut of course that doesn’t happen really. So I remember putting information on the homepage, hitting update, and then quickly opening a new tab to see what happened, right? And the fact that there was all of these words that I just wrote, out there for the whole world to see. Nobody saw it, because nobody knew about the site at that particular moment. But the idea that they could, that somebody in Europe could open up this website, and see that I had put words out into the universe, was incredibly intoxicating.
\n\n\n\nAnd so I started doing more and more with that site. I decided I could do this for a living, or at least for a side project. And so I contacted him and I said, okay, I understand how to use WordPress, and I understand how to buy a domain. What I don’t understand is, how do I have hosting in one spot and a domain in the other, and actually put those two things together so that I have a domain on the web?
\n\n\n\nHe said, Christine’s working almost every night this week, if you come over and make spaghetti for the kids, because they had four kids, I will show you how to do WordPress. And so I went over there, the kids helped me. We made spaghetti, all of the things that go with the dinner like that. The kids cleaned up dinner. We sat down at his dining room table, opened up, and he showed me how to buy a domain, how to buy hosting, and then how to put WordPress on that hosting.
\n\n\n\nI wish I still had it. I had a little blue piece of paper that had four steps. The third step I remember was, change the salt keys. We don’t really do any of that anymore, right. But I remember doing that. And so from that, I started building websites for other people. I left higher education at some point and said, I think I could do this as a full-time job. Hung a shingle, figuratively. And within a few weeks I had so many clients that I was doing marketing for, and building websites for. Yeah, it’s kind of like the rest is history.
\n\n\n\n[00:07:46] Nathan Wrigley: That’s absolutely fascinating. The thing that I’ve noticed about you, apart from the fact that you’ve built websites, is you’re heavily, heavily involved in the WordPress community. And it can be quite a jump, going from WordPress user to WordPress community member. In fact, I’d go as far as saying that, you know, most people that have contact with WordPress, probably have absolutely no idea that there is a community of any description at all.
\n\n\n\nSo how did that happen? How did it become such an integral part your life? How did you discover the community, events and so on? And how did it become the fulcrum of so much in your life?
\n\n\n\n[00:08:20] Michelle Frechette: Same person. So, you know, shout out to Christine’s husband, Rob. But he said, hey, you know, we have this meetup in Rochester for WordPress users. And I said, okay. He said, well, this is the next one, this is where it is. And I showed up to that meetup. It was in a darkened room, because they had a slide projector, you know, overhead going so they could show what’s going on with this website.
\n\n\n\nThe topic that day was Digital Ocean. I had no idea what was happening. And then they showed some CSS, and I was like CS what? And so I was the only woman, in a dark room filled with men, talking about things I had no concept of. And it took me two years to go back.
\n\n\n\nAfter two years, he had also said, look, you got to look at this thing called WordCamps. And so I went to WordCamp Buffalo, and I literally sat there all day learning from people whose names I had heard of but had never been, you know, in their presence. And thought for $25, I think at that time it was $20, I just got so much information, and lunch. You know, it was amazing. And so I thought that’s pretty cool.
\n\n\n\nAnd so the next year, Rob said, I can’t, first of all, he was organising meetups on a whim. Hey, we haven’t had one in a while, is everybody free next Tuesday? My brain can’t operate that way. It’s like, I need structure. So when he said, I can’t run this anymore, does anybody want to step in? I was like, me, I’ll do it, I’ll do it.
\n\n\n\nAnd so we have regular meetups, at the same time every month. Same day, every month. And things got a little organised that way. I went to WordCamp US, and said to Andrea Middleton at the time, yeah, maybe someday we’ll have a Word camp in Rochester. And she said, why not this year? And so I was like, okay. So we had the first WordCamp Rochester.
\n\n\n\nI was speaking at that time at different WordCamps all over New York and Canada, actually, eastern part of Canada. And things just kind of started to snowball from there, I guess, where I got asked to speak in more places. My name started to be recognised here and there, and I’m not a developer, so I was constantly surprised that people wanted to hear what I had to say. But that’s where I really started to learn that the majority of our community are WordPress users, not necessarily developers.
\n\n\n\nAnd that it takes everybody in our ecosystem to make WordPress the product that it is today, and that you can be a marketer and contribute to WordPress. You can be an, you know, a community person, contribute to WordPress, and that it really takes everybody. If it was just software, without the rest of us, it would not be nearly what we are today as WordPress, and what we know as WordPress. So, yeah, I don’t know if I answered question.
\n\n\n\n[00:10:46] Nathan Wrigley: No, that’s really interesting. There’s an awful lot that’s gone on. And you’ve obviously, right from the get go of finding WordPress decided that you wanted to, well, you had that 2 year hiatus, but after that you were in with both feet.
\n\n\n\nMore recently, I think it’s fair to say that there are some areas of the WordPress community that you’ve taken on as, well, crusade is the wrong word, but you’ve got issues which you think are important. And you’ve made them the focus and the fulcrum of what you do. And we’re going to get into some of these today.
\n\n\n\nSo let’s, first of all, just introduce the acronym under discussion a lot today, and it’s the acronym DEIB. It may very well be that people have no idea what that means. So first of all, can we unpick that? What do those letters stand for, and how does it in any way go with WordPress and community, and all of that?
\n\n\n\n[00:11:33] Michelle Frechette: So DEIB, the acronym itself stands for diversity, equity, inclusion and belonging. And so the idea is that there are entire groups of underrepresented folks in any organisation, in any community. And those are going to be the people that are either minority groups of some sort or another, whether it’s racial, ethnic minority, whether it’s ability minority, whether it’s age.
\n\n\n\nThere’s so many different ways that somebody can be in an underrepresented group, the LGBTQ+ community for example. And so, what DEIB activities try to do is kind of level the play field a little bit, and make sure that everybody has access to whatever the community is. So in our case, of course, WordPress.
\n\n\n\nAnd not just access to WordPress, anybody can download WordPress, as long as you’re in a country that doesn’t restrict access. Of course, we know that that does exist too. But it’s more than just having access to the software, it’s having access to representation within the community.
\n\n\n\nAnd so what we do at Underrepresented in Tech, what I’ve done with some of the other projects that I do, is really seek to make sure that everybody has an opportunity to be heard. Have a voice in the community. And see others like themselves on stages, in podcasts, writing for blogs, and CEO or C-suite positions, things like that.
\n\n\n\nSo we actually have a better community when it isn’t just one homogeneous group. I don’t know why that never rolls off my tongue right. But we don’t just have one group of people. In our case, you know, white, straight, males, who are running everything.
\n\n\n\nIt’s important, if we are going to have truly the best product that we could ever have, that different voices, different perspectives, different experiences help shape what that looks like going forward. And so DEIB really does, the DEIB movements and the things that we can do for that, is super important in order for us to have the best product ever.
\n\n\n\nA lot of times you’ll hear it referred to just as DEI. A lot of companies have DEI. But the B part of it, that belonging part of it, that brings it from tokenisation to actually inclusion. That inclusive part of it is so important.
\n\n\n\nIt’s not just enough that a CEO decides that they have a black person on the cover of their website, or on the cover of their brochure, and things like that to show, hey, look at us, we’re with it. We know what this is all about. Anybody can use a stock photo, but what do you really do? How are you really including people and how are you celebrating differences? That’s what’s important.
\n\n\n\n[00:13:52] Nathan Wrigley: I don’t know what your experience is outside of WordPress in the recent past, but do you feel, do you have an intuition that the WordPress community is actually quite open to these kind of discussions? Do you sense that there’s an acceptance that this is an issue, which needs to be air and talked about?
\n\n\n\nBecause I can well imagine that in any community, there’s going to be people who think, well, you know what, the core thing is, for example, the code. That’s the thing that counts, so that’s what we should all concentrate on, and all these other things are not for me to worry about, and we don’t need to worry about them.
\n\n\n\nI have this intuition that WordPress might be ahead of the curve on these kind of things, and addressing these issues, but, what do you think?
\n\n\n\n[00:14:27] Michelle Frechette: I think it’s grown over the last few years. So few years back, we had the first, what was originally called the all women’s release squad. And then it was the all women non-binary release. And at that point in time, lots of people got behind it. It was a wonderful thing.
\n\n\n\nBut there’s always a faction of people who grumble and say it’s not necessary. I think it was Joost de Valk posted in the Advanced WordPress Facebook Group, how exciting it was that this was all happening. And I think by the time they closed that thread, there were over 300 responses to that one post. The majority of which were negative, and then replies to those negative responses.
\n\n\n\nAnd this was what, three years ago? It wasn’t that long ago. And so, to be able to look at that and say, wow, that many people, not just men, but majority men, were against having a release squad that was all women and non-binary folks. Saying that it couldn’t possibly be the best release that it ever could be, because men weren’t involved.
\n\n\n\nAssuming that, just because it was women and non-binary folks, that it would not be the best that it could be. And that’s just, that’s just rubbish, to use a British term. It’s rubbish. There are women and non-binary people, who can absolutely code as good as any man, and we can lead, we can do other things.
\n\n\n\nAnd so I think that that really was, perhaps not the beginning, but that was that snowball starting to get some more traction, and build bigger as we came down that hill. Because we had champions behind that, like Josepha, because Matt was behind that kind of movement as well.
\n\n\n\nAfter that, and because my voice started to grow within our community, people would start to approach me and Ali Nimmons and say, we really do want to have like more diversity at this WordCamp, or at this event. Do you know a black person who would be willing to speak? Do you know a woman who would be willing to speak there?
\n\n\n\nAnd we thought, well, how do we respond to this, right? How do we tell people, well, check with this person, check with that person. And so we started to build a spreadsheet for ourselves, of people that we could recommend. And about 20 people into that spreadsheet, and literally two days after we started it, were like this doesn’t feel right.
\n\n\n\nNumber one, we don’t know everybody, right? Believe it or not, I don’t know every black person in WordPress. I just don’t. I don’t know every disabled person. I don’t know every woman in WordPress. And so for me to only recommend 20 or 30 people, means that the other people aren’t necessarily getting recommended by me.
\n\n\n\nAnd I understand networking, you know who you know. But we started to talk about the fact that we could build something that people could opt into, and others could search without us have to either gatekeep or be the go-between. And so we built Underrepresented in Tech for that reason. There’s a whole database there.
\n\n\n\nIf you want to find somebody for your podcast, you’re looking to hire somebody, you can go there. You don’t necessarily know why they’re underrepresented, so you might look at something, you might search WordPress and see what looks like a white male. Which you don’t know if he’s sitting in a wheelchair, because you only see his face, or you don’t see anything. You don’t know if he’s part of the LGBTQ+ community.
\n\n\n\nBecause it’s not our job to out people with what their disability or their gender is, or their sexual preference and orientation, or their abilities, things like that. So that’s not up to us. We do vet everybody that’s in the database. You have to trust that that person is who they say they are, and that we’ve vetted that.
\n\n\n\nBut we wanted to give an opportunity for people to be found. That grew into what we started as a vlog. Because we were like, well, let’s be cutting edge. Let’s go back, let’s be retro, let’s have a vlog. Which quickly like, all right, we scrapped that idea, and turned it into a podcast. We have over a hundred episodes, over 10,000 downloads of our podcast, which is Underrepresented in Tech, where we talk about those issues.
\n\n\n\nWe talk about what it’s like to be an underrepresented person in technology. We sometimes bring in guests, so we get their perspectives as well. But the whole idea is that me as a 50 something year old woman, 55 now, but at the time wasn’t right. 50 something year old woman who has a disability, in tech, and a young black queer woman in tech, we kind of ticked a lot of those boxes, right, of what it means to be underrepresented.
\n\n\n\nAnd so we have perspectives, and we have ways that we can engage with people. But also people started listening, and people started learning. And the things that we write, and the things that we say, sometimes come under incredible scrutiny. But more often than not help inform, and also effect change within organisations, and within the community, to be more inclusive, and to at least understand and be aware of the fact that not everybody experiences the world and the WordPress community in the way that the person listening to it does.
\n\n\n\n[00:19:06] Nathan Wrigley: I wonder if geography has anything to play here. So there’s a whole raft of things that I want to ask you on back of what you’ve just said, but let’s begin there. So, for example, if I live in your part of the world, so you are in North America. The complexion of countries in North America may very well be different to, I don’t know, for example, South America, or the Middle East, or Australia, you know, pick any part of the world.
\n\n\n\nIs there anything in that, or do the proclivities of North America, do they spread across the board? So let’s just take two events. Let’s take Word Camp US and Word Camp Asia. If we were to try to apply criteria, would they be the same criteria in your estimation? Or, does geography in any way play a role in how you would want that event to look, based upon where it is?
\n\n\n\n[00:19:55] Michelle Frechette: It’s definitely going to play a role, because underrepresentation is going to look different ethnically, within different places. It’s not going to change how many women are included. It’s not going to change the LGBTQ+ acceptance, in a particular community. It’s not going to change ability and disabilities.
\n\n\n\nSo if I go to an event and nobody at all, there’s very few women on stage. Everybody looks the same. Everybody has the same physical abilities. Then I’m not seeing a lot of diversity there. That’s not to say that people aren’t, right? Sometimes you don’t see diversity. You can’t know that somebody is disabled necessarily, because they can walk. I don’t, but other people do, and still are disabled folks.
\n\n\n\nAnd so, yes, you’re not always going to be able to tell just by looking at the lineup, or looking at the room. And certainly, ethnic inclusion around the world is going to look different. After we started Underrepresented in Tech, Nigel Rogers invited me to speak to his meetup, which was, and I’m never going to remember, I never remember where he is. But he is in one of the African nations.
\n\n\n\nAnd so I get online, I’m talking to this group of, it was all men I believe, all black men. And one of them said, we’re not minorities. And I said, I understand that in your community, you are not minorities. I would be the minority in your community.
\n\n\n\nHowever, globally, if you look at the entire WordPress community globally, yes. If you look at all the people who have contributed to core. If you look at all the people who have been part of release squads. If you look at the stages of all of the WordCamps around the world, you are still the minority.
\n\n\n\nYour faces do not have equal representation, in the entire community, and all of the different places. And that’s what we’re striving for, is that when we look at a global level, who is holding power? Who are the people who are being uplifted? And, can we make sure that other people have those opportunities too?
\n\n\n\n[00:21:43] Nathan Wrigley: Yeah, it’s a difficult tightrope to tread that one, isn’t it? Because obviously if you were to, for example, put on an event in, as you just described, say Africa, or in the center of Europe, the makeup of those communities would be different. And so casting the net wider and saying, well, this is about the world, that’s kind of interesting, isn’t it?
\n\n\n\nBecause we’re really in the first generation of people that have been able to sort of do that really. Because we’ve got, you know, we’ve got instant communication, and things like that. And so we can have this much bigger perspective.
\n\n\n\nOkay, so that’s really interesting. If somebody’s putting an event on, and again, we’ll just take those as an example, let’s say Africa, or Europe, or wherever you know, something different from North America. Is there a correct amount of different things that you need to do, to satisfy these DEIB, well, I think criteria is the wrong word, but recommendations is maybe a better word, I’m not sure?
\n\n\n\nIn other words, do we have to see in the speaker lineup, okay, there needs to be 4 of this thing, and 8 of this thing, and 12 of this thing and, you get what saying? Does need to be so prescriptive, or is it more of, okay, we’ll try our best? We’ll do what we can, and we’ll accept what comes out the other end.
\n\n\n\n[00:22:54] Michelle Frechette: There’s a little bit of a combination, that’s kind of a spectrum. And somewhere in the middle of those two things that you just said is what I would love to expect. And part of that is, take a look at the, what you’re doing to recruit. If all you do is put it out, and just say anybody, this is what I’ve been told. It’s out there, anybody can apply. I can’t help it if minorities aren’t applying.
\n\n\n\nWell, yes and no, because you can invite people to apply. If traditionally your event has had white faces, and mostly male on stage, do people who are not white faces and mostly male, feel encouraged to apply? Do they feel that’s a space that they’re welcomed in? Do they feel that that’s a space where they have a voice?
\n\n\n\nWhat have you done to make sure that those people feel that they could be included, and not excluded, because of what you historically have had on stage, or historically have had as your outreach, or historically have had as your organising team?
\n\n\n\nSo if you really do want to make a difference going forward, what can we do? We can invite people to speak. Just because we have always had it as the luck of the draw, doesn’t mean it has to be that way. We can say, I want to make sure that I am inviting people to apply.
\n\n\n\nAnd one of the things that I’ve suggested in the past is, don’t just say, Sarah Smith over here, you have a darker face than Michelle does, we want you to speak. And then hope that she’s going to suggest a topic, or apply with a topic that fits. So what I’ve always said is, we really do want you to speak, I want to make sure you’re in our lineup, can you suggest three topics? And then we can make sure that one of those topics fits within everything else.
\n\n\n\nSo for example, if everybody wants to talk about SEO, unless it’s an SEO conference, that’s not a good lineup, right? So you need to make sure that the topics work too. But if Sarah Smith says, I could talk about SEO, I can talk about building your public persona, and I can talk about outreach to underrepresented communities.
\n\n\n\nYou’ve given Sarah three different things, and one of those topics is most likely to be able to be in your speaker sessions, in your topics, without overlapping other people’s topics. So there are definite ways that you can increase your diversity on your stage, by making sure that you’re inviting people to speak, at the very least encouraging.
\n\n\n\n[00:24:55] Nathan Wrigley: So there is a process of, there’s work to be done basically. If you are, let’s say you are putting on an event as described, in the scenario that you are suggesting, merely saying there’s the form, it’s online, everybody can access that form. That’s possibly not going to be enough because of history, really.
\n\n\n\nIf you’ve been to a WordPress event as me, then all of the pieces of the jigsaw puzzle kind of fit. I should probably say, if you haven’t seen my face before, I am a white male. And so, you know, if I attend any of these events, there’s really no impediment to anything for me.
\n\n\n\nBut is what you are saying that, if it’s not a situation where you see people on the stage that look like you, think like you, behave like you, it’s unlikely that you are going to make the effort to go in the first place. And so you need to take steps to redress that balance. And those steps have to be proactive, because it’s not going to happen by accident, given what we’ve got in the past, the history of these things.
\n\n\n\n[00:25:55] Michelle Frechette: And think about the history of a disabled person. Think about the history of a minority person. Think about the history of women. Not only have we not seen ourselves there, but in many cases, we’ve been discouraged and actively barred from access to those kinds of events.
\n\n\n\nSo, if as a disabled person, I’ve tried to go someplace, there’s no curb cuts, there’s stairs, there’s escalators. I have to go in through the kitchen to have access to an event. I would be discouraged from attending that event. Would I love to be on stage, yeah. But if I can’t actually get on the stage, what good is it, right?
\n\n\n\nAnd that’s just from the perspective of a disabled person. If I walked into a dark room of a meetup, and I’m the only woman, with 10 men in a darkened room, how does that make me feel welcomed? That doesn’t. Because now I’ve put myself in a position where mothers all over the world say, never put yourself in a dark room with a bunch of men, right?
\n\n\n\nSo there’s just history that comes along with being in an underrepresented group, that says to us, and whether that’s passed on through oral tradition or, you know, our families have taught us, or it’s just our own experiences in the past. We can sense, by looking at something in the history of something, whether or not we would traditionally be included in that event.
\n\n\n\nAnd we have people like me, who just like try to break those barriers open. Because I have broad shoulders and thick skin. I want to make sure that other people behind me feel welcomed, and have the access to those things. So I’m willing to be the person to suffer the slings and arrows, as Shakespeare would say, to make sure that it’s easier for other people to go through.
\n\n\n\nI think of myself as that icebreaker ship, that’s going through, you know, the Arctic, making it possible for other ships to follow through in my path. It’s not easy. And sometimes there are sleepless nights involved with some of those things, because you put yourself out there in a way that says, I need to see access for more people.
\n\n\n\nAnd other people who have traditionally held those positions, aren’t necessarily willing to give them up. And I understand that because power is a powerful thing, and we like being in a position of power, traditionally. And so the idea of seeding some of that power to other people, whether that’s a space on a stage, whether that’s in a boardroom, you know, that you bring people on your board, whatever that looks like. It’s not easy to include people that don’t look like us, and might have other ideas than us.
\n\n\n\nBut that’s truly how we make a better community, and better products. I use this example all the time when I talk about inclusion. Back in the forties and fifties, they marketed vacuum cleaners to men, by showing pictures of vacuum cleaners with women in their pearls, and there are high heels and beautiful smiles, vacuuming their houses. Do you know how we market vacuum cleaners today? It’s how they work.
\n\n\n\nYou know, we see a picture, a dog is knocked over a plant, and the Roomba, or somebody else is vacuuming it up. Kids spill Cheerios, let’s cut to a picture of that vacuum cleaner picking up the Cheerios. We talk about what the product does, not how pretty the woman looks using it. Because guess how many women actually want a vacuum cleaner for Christmas? Zero. That should not be a gift.
\n\n\n\nAnd so the idea is, more women started to join boardrooms, and more women started to be marketing and ad people, in the seventies and eighties, and we started to see some of that change. Because traditionally, women are the one now buying those kinds of products for the home. Let’s appeal to her, instead of show a man how happy your wife will be if you bring home a vacuum cleaner.
\n\n\n\nThe same thing is true in every place, is you bring more people who have different experiences into those decision making processes, and you make a better product or a better service, to appeal for more sales. So it’s just good business. For your bottom line, much less, let’s be inclusive and let’s do the right thing.
\n\n\n\n[00:29:27] Nathan Wrigley: Do you prefer carrot or stick for this? And, is it necessary to sometimes deploy both. My intuition is that you are going to prefer carrot. But maybe the stick has to come out at various times. And I have seen those, I don’t really know what the right word is, but I’ve seen those miniature battles, if you know what I mean, where people have said one thing, and then there’s been people reacting and saying, we don’t need this, and they’re trying to explain it, and what have you.
\n\n\n\nSo yeah, carrots or stick? Would you rather that we were able to introduce this idea and everybody came on board? Or, do we have to at some point say, look, nope, this is just what’s going to happen, you’ve got to come along for the ride?
\n\n\n\n[00:30:05] Michelle Frechette: Obviously carrot would be the better thing. If we can show people why inclusion is better, and how they can make their products and services better by bringing in more perspectives, and bringing in more experiences that people have. Those lived experiences are really what enrich the whole product and the whole process.
\n\n\n\nLike I said, whether it’s a service or it’s a product. How are people using it? If we only approach things from one perspective, we could only sell to that perspective, plus or minus maybe one standard deviation. But if we can make that bell curve wider instead of narrower, we have an opportunity to do more, and affect good for more people through what it is that we have created.
\n\n\n\nIn order to do that, we have to understand how more people are using our products and services, or what we intend our products and service to be, so that we can appeal to all of those people.
\n\n\n\n[00:30:50] Nathan Wrigley: Do you have a sense that during the time that you’ve been in the community, things have changed? Can you, for example, give us an anecdote or a story about something that you know has changed, as a result of something maybe that you said, or somebody else said, which can just deliver the message that, well, everything is not set in stone. Things that were once the way they were can be altered.
\n\n\n\n[00:31:09] Michelle Frechette: So WordCamp US, the first one after the pandemic had shut everything down, was in San Diego. It was a very small event. They only sold, I think, 650 tickets, including sponsors and speakers. So it was, you know, that’s still a big event, don’t get me wrong, but as a global event, a very, very small.
\n\n\n\nI was there with my scooter, and tried to navigate an entire event. And by the end of the second day, I was in tears, because it was so difficult to be there as a disabled person. I got stuck in the bathroom, in the lobby bathroom, not in my hotel room. But in the lobby bathroom, because of the way that the room was built, and the exit was built, and where the trash can was, I couldn’t get close enough to the door to be able to open it, pull it to the side, and then go through the door. I literally had to wait until somebody came through. I would’ve texted somebody, I would’ve called somebody if somebody hadn’t come through, you know, fairly soon.
\n\n\n\nBut somebody else had to come through that door to let me out. And that’s not, we’d like to be as independent as possible. When you’re a disabled person, you don’t want to have to rely on people to do everything for you. That doesn’t ingratiate you to the community, when you’re constantly begging and asking for assistance.
\n\n\n\nBut that wasn’t the only problem that I had there. Several of the doors to access buildings didn’t have paddles, so they wouldn’t open themselves. So I had to ask people to help me get in and out of doors. My room, which was tagged as a handicapped accessible room, had a tub that I would’ve had to step over and into, which is dangerous for me. So I wasn’t able to actually take a shower or a bath. I had to, you know, sink bathe for five days.
\n\n\n\nAnd there was just so many things that just were inaccessible for me. And at the end of that, I did talk to people about it, and told them that it was coming. But I wrote an article for Post Status called Five Days Without a Shower. I very unemotionally explained what had happened, and how things were difficult for me. I pointed out what worked, and the people who were very helpful in it. But then I also gave a list of things that I think could be done, looking at future events, to make them more accessible to other people.
\n\n\n\nI know that I have a voice in our community. I know that people, you know, I’ve thousands of followers on Twitter, and I speak a lot, and that people know who I am. And so I realised that what I say in the community might be listened to more than people who don’t have that kind of following. And I don’t take that lightly. And I do try to use that for good.
\n\n\n\nAnd so I wrote this article. I gave copies of it to, you know, to Angela Gin, and I sent it to Matt Mullenweg and just, this is the experience, this is what I think we could do better. As a result of that, Wordcamp Asia, which I attended this year, reached out to me and said, we want to make sure, but this is what we’ve put in place and I think that everything is accessible to you. And it was.
\n\n\n\nThe places that had stairs, they had put temporary ramps, so that I could get to them. The stage I was speaking on, I didn’t have to try to walk up three stairs, they had a ramp there for me. So everything was accessible.
\n\n\n\nWordCamp US this year, we had a team specifically for accessibility. You know, Alex was on that team, and he was looking at the accessibility from, no pun intended, looking at the accessibilities from the perspective of blind man.
\n\n\n\nBut he was looking over the website. He was making sure that there were things in place, that he couldn’t get lost in a space that big if he wasn’t, you know, always having somebody on his side. So we had phone numbers in place where, if he literally couldn’t find his way out, somebody could come to him, and help him navigate.
\n\n\n\nWe made sure that every place was accessible with wheels. We made sure that people who were neurodivergent, who might need quiet spaces, had the ability to step out and find a space that was just listed as a quiet space. We made sure that there were rooms for nursing mothers, that they could sit and nurse their children, or pump if they needed to. And not have to do that in a bathroom, which is not sanitary.
\n\n\n\nThat was one of my suggestions, is that we had a person or a committee to look at the venue, to see what needed to change, in order for it to be an accessible event. So that was just one thing. One article that I wrote that was taken seriously, and that there’s a page in the handbook now for WordCamps, to make sure that you’re looking at things like curb cuts, like elevators. That there’s no place that, in a WordCamp, is inaccessible to somebody who can’t walk.
\n\n\n\nAnd so there’s lots of things that I’ve been able to, because I have a voice in this community, put out there, that have then been able to be accommodated. WordCamp Europe was terrified, that because it was old, such an old city, that I would have difficulty.
\n\n\n\nBut I was in constant contact with Estela Rueda, who made sure that everything that there was, you know, she said, this is where you can go. Some places have stairs, but this is the way to get around that. If you get stuck, here’s my number. Like there was lots of things, there was constant communication, in order to be able to know that not just me, but anybody with, physical disabilities would be accommodated.
\n\n\n\nAnd so, is it easy to put myself out there as the disabled person who needs accommodations all the time? It’s not, right? So nobody likes to say, hey, my legs don’t work. I’m not a perfect person, and I can’t do the things that everybody else does. But by me being able to do that, hopefully means that I’ve, not only opened doors electronically for other folks, but put ramps in place, and given access to people who might not have had access otherwise. And so, yeah, I think there’s things that I’ve been able to say and do that have had an impact, positively, in our community.
\n\n\n\n[00:36:13] Nathan Wrigley: The curious thing, especially in terms of events, which is what we’ve just been talking about, is it doesn’t lessen the experience for people that don’t require it. You know, if there’s a ramp there, it’s no more difficult for me to use that. And so I think that’s brilliant. That’s such a nice tale of something actually changing, not in a heartbeat, but in a fairly short space of time. And so, well, bravo, firstly for writing the article.
\n\n\n\nI guess it does beg the question, do these things get thought about, unless there is somebody like you who has to go through, well, let’s call it the pain or something like that? You know, somebody’s got to go through it, in order to live that experience, so that they can report back on what needs to be fixed.
\n\n\n\nDo you sense that there’s still people having to go through pain in the future, or do you think that as a community we are getting better, you know, at a fair pace, so that it’ll be approaching perfect soon? Anything like perfect soon, have we still got a long way to go?
\n\n\n\n[00:37:11] Michelle Frechette: I think it depends on the location. I think some cities, some countries, it’s not as easy for them to pivot and be as accessible, just because of the history of the city. You know, there are places I said, oh, I’d love to go there. And somebody said, I don’t think you’d be able to. Disabled people in that city have a tremendous difficulty getting around.
\n\n\n\nEven in Asia. So, in Thailand, the cars are smaller, so to accommodate, to put me in an Uber, and also my scooter, which does come apart, some of that had to be at my feet and on the seat next to me, because it didn’t all fit in their trunk, for example. And so there are places that it might not be possible.
\n\n\n\nAlso, like, I was in Phoenix Arizona earlier this year, and I called for an Uber, and I knew exactly what the person looked like, I knew what their car looked like, and I knew what their license plate was because that’s on the app. And this person pulled up, saw me in my scooter and sped away, because they didn’t want to deal with my scooter.
\n\n\n\nThey canceled it, but they didn’t say, hey, I’m sorry I don’t have room in my trunk. Like they didn’t even communicate with me. They literally just drove away, and that was a terrible experience. And that was here in the United States, where we’re supposedly really accommodating to people with disabilities.
\n\n\n\nAnd so, yeah, it’s not always easy. I don’t think we’re ever going to not have to look at it, and make sure that things are accessible. And I think that there will always be places that are historically more accessible than others.
\n\n\n\nThey actually, in Athens now you can, with a wheelchair, go up on the Acropolis. I didn’t because my daughter didn’t want to, even though I wanted to. But I was also told that once you get up the top of there, of course it’s just this ruins. And that’s not easy to navigate in wheels either. But they’ve done everything they can, even to make things like the Acropolis accessible.
\n\n\n\nAnd so is everything always going to be accessible? No. There are apartments with only stairs. I will never be able to visit friends who live upstairs, in apartments that have only stairs. But being able to access public spaces, and finding ways to accommodate with temporary ramps, and things like that, I think is super important.
\n\n\n\nAnd I hope that as long as I’m in the community, and I continue to talk about these things, that people will think about them for their events. And make sure that as many people possible can attend.
\n\n\n\n[00:39:13] Nathan Wrigley: You always seem very jolly, and we would say in the UK, fairly chipper. You know, you’ve got the glass is half full, kind of approach. Or at least that’s the impression that I have. But does this, so we’re going to stray into something maybe personal, you may not wish to reveal this, it’s entirely up to you.
\n\n\n\nDo these issues make you angry? Do you get a little bit annoyed on behalf of other people? Is there a bit of you that thinks, this is just not on? You know, it cannot be that events haven’t thought this through. It cannot be that these people aren’t represented. I’m just wondering, what the emotions it stirs in you are.
\n\n\n\n[00:39:44] Michelle Frechette: I would say frustration more than anger. It’s frustrating to me. Anger would come into place, if people acknowledged it and chose not to act. That’s anger. Not even looking, or not even thinking about it is the frustration. I think, traditionally, if somebody thinks about it, then they will try to be as accommodating as possible.
\n\n\n\nBut to think about it and then not act, which is to make a deliberate decision not to include others. That’s when anger would come into play. But traditionally, anytime I’ve challenged or I’ve said, hey, have you thought about, most people are like, oh my gosh, I never even thought about that.
\n\n\n\nFor example, WordCamp Buffalo this year. I was the mentor, I was part of the organising team for that event. And it was in an old school building. And the only way for me to get there was to go in the back of the building, up a little delivery ramp. And, was I angry? No, because I could still get in there. It was an old building that that was the only way to accommodate me, that’s fine.
\n\n\n\nIf I’m going into a restaurant, I don’t want to come in through the kitchen. To me, that’s anger. They haven’t thought about it. They don’t want to include people in wheelchairs, if there’s no way to get in, when you’re trying to be open to the whole public. There’s ways that you can be accommodating. There’s just lack of understanding, lack of thinking, lack of thought to inclusion, that’s frustration. Deliberately denying access, that’s anger.
\n\n\n\n[00:40:59] Nathan Wrigley: Are you ever on the receiving end of other people’s frustration and anger? Do the causes that you champion, do sometimes you find that your social media is full of people who disagree with you, and perhaps, maybe disagree as too polite term there? Does it sometimes descend into things that you’d rather didn’t happen? In other words, is it always equanimous, the kind of conversations you have, or does it sometimes get a little bit fraught and frayed?
\n\n\n\n[00:41:24] Michelle Frechette: It does. A year and a half ago, I think, I wrote an article for a Post Status, called Misogyny In WordPress Is Real. And talked about the fact that women are still denied access, and still undervalued in a lot of places. And, you know, specifically, I pointed to that thread of all those people talking about the all women non-binary release, when Joost had posted about it in Advanced WordPress and Facebook.
\n\n\n\nThere are other things that I’ve pointed to specifically, some of it tech related, some of it’s specific to WordPress. And the amount of people that attacked me, men, I will say. The number of men who posted replies to that post or comments on that post, completely misogynistic. It’s like, oh, look you’ve proven my point.
\n\n\n\nAnd attacked me openly on, you know, Twitter and things like that. I mean, it irritating, right? But it doesn’t anger me, because I’m like, okay, so you are just set in your misogynistic ways. Block. I will just block you.
\n\n\n\nPeople talk about me all the time. They don’t necessarily say kind things. I can’t own what somebody else thinks of me, that’s on them. So, you know, block them and move on. That’s the best way to be. I could be all angsty and carry it with me in a negative way, but I know that the work that I’m doing in our community, to try to level the playing field, to try to forward inclusion, the DEIB work, means that I’m going to encounter people that don’t agree with me.
\n\n\n\nOkay, fine. Move on. I’m going to try to talk to the people who do, who want to learn. If I can educate in a way that helps people learn, and they at least consider, if not actually enact change, I’ve done some good. And if there are people who are absolutely going to stonewall, because they like the way that things are, I can’t move a stonewall. I’m going to move on to the people that I can help. And so those are the kinds of things that I look at.
\n\n\n\nAnd, am I always cheery? No. That is what you’re going to see publicly, of course. But you know, I referenced the fact that, by day two of WordCamp, I was literally bursting into tears, because I was so frustrated by the fact that I couldn’t access things.
\n\n\n\nDoes it feel good when you get attacked? No, it doesn’t. You know, I challenged WordCamp Europe this past year, because the first couple of, it was three or four I think, announcements of the speaker lineup were less than 20% women.
\n\n\n\nIt’s always hard to judge ethnicity, and you can never tell by looking at a person that they might not be an ethnic minority. You can’t tell if somebody’s part of the LGBTQ+ community. You don’t know if somebody’s non-binary. I acknowledged all of that, and I said I really hope that we see more of a balance going forward, with the rest of the announcement.
\n\n\n\nAnd that one tweet has almost 30,000 impressions, because people either said, yes, absolutely, we need this, or you don’t understand how it is in Europe, Michelle. It’s not the same as it is in the US. I acknowledge that. But you have women in Europe, right? You do have minorities, you have people of color, you have people with different abilities. You have all of the different things that make up underrepresentation. So to only show us a bunch of white men, really starts to make you wonder, well, what is the rest of the lineup going to look like?
\n\n\n\nI say I created controversy, I actually pointed out the controversy. I did not create controversy. The controversy already existed. I was simply the conduit, by which the rest of the world started to notice it. Because we’re so used to seeing so many white men in every lineup, but we need to make sure that that changes.
\n\n\n\nAnd so I had people, I mean, I went to WordCamp Europe. I had people there telling me things like, you don’t understand. I had people sign up on my calendar, just to tell me how wrong I was, and to say that you have a big voice in this community, you need to use it better. And I said, well, I did.
\n\n\n\nI’m not always going to be everybody’s favorite person. I actually have a sticker, I will bring one to you next time I see you, Nathan, that says, I’m not everybody’s cup of tea, and I’m okay with that. Because if you’re going to be a change agent, if you’re going to try to help things be better, there will be people who don’t like what you do.
\n\n\n\nThere will be people who feel challenged by what you’re doing. And there will be people who just flat out disagree with you. And that’s okay. Those are not the people that I’m going to change. The people that you can actually influence, are the people who want to do better, and don’t realise that they haven’t been to that point.
\n\n\n\nAnd so, if you listen to my words and you think, gosh, I could be more accommodating, I could outreach to people who don’t look like me, and really make the speaker lineup more diverse. If those people have listened to me and enact a change, and really think about the way they do things, then I can say my work is done. Or at least you know, part of my work is done, and I will continue to fight the good fight.
\n\n\n\n[00:45:46] Nathan Wrigley: That’s the perfect segue then to probably round it off. And if I ask you, Michelle, where can people contact you? Should they have those intuitions, and they do wish to speak to you. Where’s the best place? What’s the selection of things that you, are you most frequently using?
\n\n\n\n[00:46:01] Michelle Frechette: Yeah. So I am still on, I like to call Twitter, but X. You can’t change your name on there, once you have so many links back to you. Yes, you physically can change your name, but I’m still @michelleames on Twitter and X. But if you go to meetmichelle.online, you will find access to all of the different things that I’ve done, my projects, WP Speakers, Underrepresented in Tech, WP Career Pages. All of those things that I’ve done for the community, to try to help people find jobs, help people find speakers, and just make the world a little bit more balanced.
\n\n\n\n[00:46:31] Nathan Wrigley: I will make sure that every single one of those is listed in the show notes. So if you head to WP Tavern, at the very least, you’ll know that they are there. Michelle Frechette, thank you so much for chatting to me on the podcast today. I really appreciate it.
\n\n\n\n[00:46:44] Michelle Frechette: It was my pleasure. Thank you for having me.
\nOn the podcast today we have Michelle Frechette.
\n\n\n\nThis is going to sound like a lot, and that’s because it is.
\n\n\n\nMichelle Frechette is the Director of Community Engagement for StellarWP at Liquid Web. She was called “The busiest woman in WordPress,” by Matt Mullenweg at WCUS 2022. She is also the host of the WP Coffee Talk podcast, co-founder of Underrepresented in Tech, creator of WP Speakers and WP Career Pages, president of the board for Big Orange Heart, Director of Community Relations and contributor at Post Status, co-host of the WP Motivate and Audacity Marketing podcasts, host of the WP Constellations podcast, author, and a frequent organiser and speaker at WordPress events. Michelle lives outside of Rochester, NY where she’s an avid nature photographer. You can learn more about Michelle at meetmichelle.online.
\n\n\n\nYou see, like I said, that’s a lot.
\n\n\n\nThis willingness to engage in all manner of WordPress projects has given Michelle a voice, and she’s on the podcast today to discuss a topic which is close to her heart, diversity, equity, inclusion, and belonging.
\n\n\n\nShe talks about her experiences at WordPress events, and how they were not always easy for her to attend and be a part of. Michelle uses a scooter to get around and there have been situations in which she could not enter venues and access all the facilities. This frustration made her take action and, as you’ll hear, effect change at subsequent events she attended.
\n\n\n\nIt’s not all about events though. Michelle talks about the wider goals of making all aspects of the WordPress community more opening and inclusive.
\n\n\n\nBeing one of the voices promoting this message has not always been easy, and we hear about how Michelle copes with those who disagree with her quest to create change.
\n\n\n\nIf you’re interested in thinking about inclusivity, and how embracing diverse perspectives can impact the WordPress community, this episode is for you.
\n\n\n\nFive Days Without a Shower article
\n\n\n\nMisogyny in WordPress is Real article
\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 24 Jan 2024 15:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"Do The Woo Community: Content Strategies for Woo and WordPress Businesses with Adam and Emma\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78922\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://dothewoo.io/content-strategies-for-woo-and-wordpress-businesses/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:438:\"Adam and Emma talking about all things content when it comes to building brand recognition and trust for your Woo and WordPress business.
\n>> The post Content Strategies for Woo and WordPress Businesses with Adam and Emma appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 24 Jan 2024 10:30:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"HeroPress: My Journey as an Engineer with WordPress – エンジニアとしての WordPress の旅\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=6450\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:154:\"https://heropress.com/essays/my-journey-as-an-engineer-with-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=my-journey-as-an-engineer-with-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:20935:\"\n\n\n\nI currently live in Tokyo, Japan, and work as a freelance engineer. I would like to talk about what my life was like before I met WordPress, how I met WordPress, and the freedom it has brought me.
\n\n\n\nIf I remember correctly, the first time I touched a computer was when I was in junior high school. I remember a big all-in-one desktop machine coming to my house with Windows 3.1 OS.
\n\n\n\nIn Japan at the time, magazines dealing with computers and programming were being published for users. It’s unthinkable now, but the magazine had pages and pages of “printed” code to run small tools and games! I remember typing that code line by line into the computer and being so excited to see the incredibly simple racing game working.
\n\n\n\nAround the same time I was in middle school, I met the guitar. From then on, I fell in love with music and spent most of my time from middle school to my 20s playing the guitar, forming bands with friends, and performing at live shows.
\n\n\n\nHowever, of course, it is not easy to earn money in the music world and make it my lifelong career. When I was around 30 years old, I started thinking about my future.
\n\n\n\nUp until then, I had experienced various jobs in order to earn income for my music activities. Many of these jobs were Internet and computer-related, such as helping end-users improve their Internet experience and configure hardware over the phone. At the same time, I was also using music software to compose music. I decided to take advantage of these experiences and become an engineer.
\n\n\n\nHowever, at that time I was already over 30 years old. Generally speaking, it’s probably a late age to start programming or gain experience as an engineer.
\n\n\n\nIn order to fill that gap, I studied hard and obtained several qualifications necessary to become an engineer. Fortunately, I was able to get a job as a programmer even though I had no experience as an engineer.
\n\n\n\nAt that company, I was able to work on languages such as HTML, CSS, PHP, and C#. However, in a desperate attempt to make up for the lack of experience, I probably pushed myself too hard. After two years of work, I lost my mental and physical balance and quit my job.
\n\n\n\nOf course, we need money to survive. I started working as a freelancer, and at first I gradually increased my abilities and experience through small projects.
\n\n\n\nSome of those projects involved customizing already published WordPress sites. The first time I met WordPress was around 2018.
\n\n\n\nAfter that, I developed WordPress sites from the beginning by myself and got involved in larger projects, so projects related to WordPress started to take up most of my work.
\n\n\n\nWhile searching for information about WordPress on the internet, I learned about the existence of the community. In 2020, I also attended an online Meetup event for the first time. At that time, I didn’t fully understand what “open source” or “contribution” meant. However, as I met people who were willing to generously share their technology and experience and who were contributing to making open source better, I became more fascinated with WordPress and wanted to get involved in the community in some way and contribute in any way I could.
\n\n\n\nI was just developing a WordPress theme. I was looking through the browser’s developer tools to see what CSS was applied to the block on the block editor. By chance, I discovered a small CSS typo.
\n\n\n\nAt the time, I knew very little about Git and had never used a CLI tool. However, it turns out that this code is contained in a project called Gutenberg, which is managed on GitHub.
\n\n\n\nThis is my first ever pull request to the Gutenberg project, and my first contribution with code to the WordPress community. Just one line change!
\n\n\n\nMy first pull request to the Gutenberg GitHub repository\n\n\n\nI was so excited to imagine that the code I had written, even though it was just a small change, would become part of WordPress itself and be spread around the world.
\n\n\n\nAfter that, I started checking out Gutenberg issues and sending small pull request whenever I had time. Through that experience, I learned that WordPress was created by a huge number of people and is evolving at an alarming speed every day.
\n\n\n\nIn February 2022, I became part of the Gutenberg team. In June 2023, I was honored to be invited to join the Gutenberg Core team. I became more immersed in contributing to Gutenberg, discussing things with other members through Slack and GitHub Issues, and working on solving more complex problems.
\n\n\n\nMany members of the WordPress community contribute as volunteers. I’m one of them, and I was struggling to find time to contribute to the WordPress community while also working to make money.
\n\n\n\nIn July 2023, LOOS Co., Ltd., a company represented by a member of the Japanese WordPress community that sells WordPress themes and plugins, will support my contribution activities to WordPress. Thanks to his support, I have been able to spend more time contributing to WordPress and earn a good income at the same time.
\n\n\n\nMy contributions to the Gutenberg project also made my GitHub account very active. I believe that this, more than any other resume, objectively proves what I can do. I believe that there are clients who have come to commission work from me after seeing my history of activities like this.
\n\n\n\nIn October 2023, I attended WordCamp Tokyo 2023 held in Japan. This was the first offline WordCamp I ever attended, and the first time I was a WordCamp speaker. I was able to meet many friends that I had only interacted with through the internet and video calls.
\n\n\n\n Photo by Chiharu Nagatomi / CC BY 4.0\n\n\n\nWhether it’s an issue or a pull request, the WordPress community raises, discusses, and makes decisions every day.
\n\n\n\nThere are three things that I think are very important in this process:
\n\n\n\nAlmost every discussion and decision made in the WordPress community should be based on these three ideals. With the development of social media, we now have many opportunities to come into contact with negative emotions, and this psychological safety is soothing to my spirit.
\n\n\n\nNeither WordPress Core nor Gutenberg is perfect. There are tons of problems to solve, just like there are tons of tickets and issues.
\n\n\n\nIt doesn’t necessarily mean you have to write code. If you have the courage to take a step forward and share what you think is a problem or challenge in an open space, those who see it may be able to solve it and help other WordPress users around the world.
\n\n\n\n私は現在、日本の東京に住んでおり、フリーランスエンジニアとして活動しています。WordPress に出会う前の自分がどのような人生を送ってきたのか、どのようにして WordPress と出会ったのか、そして WordPress が私にどのような自由をもたらしたのかをお話ししたいと思います。
\n\n\n\n私がはじめてコンピュータに触れたのは、記憶が確かならば中学生の頃です。Windows 3.1 OS を搭載した大きな一体型のデスクトップマシンが自宅にやってきたことを覚えています。
\n\n\n\n当時の日本では、ユーザー向けにコンピュータやプログラミングを扱う雑誌が刊行されていました。今では考えられないことですが、その雑誌には小さなツールやゲームを動かすためのコードが何ページにも渡って「印刷」されていました ! 私はわけも分からず、BASIC 言語で書かれたそのコードを一行一行コンピュータに打ち込み、おそろしくシンプルなレースゲームが動いた事にとても興奮していた事を覚えています。
\n\n\n\nちょうど同じ中学生の頃、私はギターに出会いました。それからというもの、私は音楽にのめりこみ、中学生から20代までのほとんどの時間を、ギターを演奏したり、友人たちとバンドを結成したり、ライブに出演する事に費やしてきました。
\n\n\n\nしかし、もちろん音楽の世界で収入を得て、それを一生の仕事とする事は簡単なことではありません。30才頃のとき、私は将来の事を考えるようになりました。
\n\n\n\n私は、音楽活動のための収入を得るために、それまでに色んな仕事を経験してきました。それらの多くはインターネットやコンピュータに関連するものであり、例えば電話を通じて、エンドユーザーのインターネット環境の改善、ハードウェアの設定を手助けする仕事でした。また同時に、作曲のために音楽ソフトウェアも使用していました。私はこれらの経験を活かし、エンジニアとなる事を決意しました。
\n\n\n\nしかし、私はその時にもう30才を超えていました。一般的に言えば、プログラミングを始めたりエンジニアとして経験を積み始めるには遅い年齢でしょう。
\n\n\n\n私はその溝を埋めるために必死で勉強し、エンジニアとして必要ないくつかの資格を取得しました。そして幸いにも、エンジニアとしての経験が無いにも関わらず、プログラマとしての職を得る事が出来ました。
\n\n\n\n私はその会社で、HTML、CSS、PHP、C# といった言語に関わる事が出来ました。しかし、足りない経験を必死で埋めようと、私は無理をしてしまったのでしょう。2年間の仕事を通じて、私は心身のバランスを崩し、退職しました。
\n\n\n\nもちろん、生きていくためにはお金が必要です。私はフリーランスとして活動をはじめ、最初は小さなプロジェクトを通じて、自分が出来る事や経験を少しずつ高めていきました。
\n\n\n\nそれらのプロジェクトの中には、既に公開されている WordPress サイトをカスタマイズするものも含まれていました。はじめて WordPress に触れたのは 2018年の頃です。
\n\n\n\nそれから、自分1人で最初から WordPressサイトを開発したり、より大きなプロジェクトに関わる事で、自分の仕事の多くを WordPress に関するプロジェクトが占めるようになっていきました。
\n\n\n\nWordPress に関する情報をインターネット上で調べているうちに、コミュニティの存在を知りました。2020年に、初めてオンラインの Meeup イベントにも参加しました。私はその頃、「オープンソース」や「貢献」とは何なのかという事も十分に理解していませんでした。しかし、自身の技術や経験を惜しみなく共有したいと考える人たちが集まり、そのオープンソースをより良くしていこうと貢献している人たちに出会った事で、より WordPress の魅力に惹かれ、自分も何らかの形でコミュニティに関わり、自分が出来る方法で貢献したいと考えるようになりました。
\n\n\n\nちょうど WordPress テーマを開発していた時です。私は、ブラウザーの開発者ツールを介して、ブロックエディター上のブロックにどのような CSS が適用されているかを調べていました。偶然にも、小さな CSS のタイポを発見しました。
\n\n\n\n私はその頃、Git についてもほとんど理解していませんでしたし、CLI ツールも使った事がありませんでした。しかし、このコードは Gutenberg と呼ばれるプロジェクトに含まれており、そのプロジェクトは GitHub で管理されている事が分かりました。
\n\n\n\nこれは、私が人生で初めて、かつ Gutenberg プロジェクトに初めて送ったプルリクエストであり、初めての WordPress コミュニティへのコードによる貢献です。たった一行の変更だけです !
\n\n\n\nGutenberg GitHub リポジトリに初めて送ったプルリクエスト\n\n\n\nほんの僅かな修正ですが、私が自分で書いたコードが WordPress そのものの一部となり、それが全世界に広がる事を想像し、私はとても興奮しました。
\n\n\n\nそれから、私は時間がある時に Gutenberg の issue を調べたり、小さなプルリクエストを送る事を繰り返すようになりました。その経験を通じて、WordPress は膨大の人の手で作り上げられており、毎日恐ろしいスピードで進化している事を知りました。
\n\n\n\n2022年2月に、私は Gutenberg チームの一員となりました。2023年6月には、光栄な事に Gutenberg Core チームにも招待されました。Slack や GitHub Issue を通じた他のメンバーとの議論、より複雑な問題の解決に取り組みながら、私はより Gutenberg へ貢献する事に没頭するようになりました。
\n\n\n\nWordPress コミュニティの多くのメンバーは、ボランティアとしての貢献しています。私もその1人であり、お金を得るための仕事をこなしながら、WordPress コミュニティへ貢献するための時間を確保する事にとても苦労していました。
\n\n\n\n2023年7月、日本の WordPress コミュニティの仲間が代表を務める会社であり、WordPress テーマ・プラグインを販売している株式会社 LOOS 様が、WordPress への貢献活動をサポートしてくれる事になりました。彼の支援のおかげで、私はより多くの時間を WordPress への貢献活動に充てる事ができるようになり、同時に十分な収入を得る事が出来るようになりました。
\n\n\n\nまた Gutenberg プロジェクトへの貢献を通じて、私のGitHub アカウントの活動履歴は非常に活発なものとなりました。これはどんなレジュメよりも、私がどのような事が出来るかを客観的に証明するものだと考えます。このような活動履歴を目にしてに、自分に仕事を依頼してくれるようになったクライアントも存在すると信じています。
\n\n\n\n2023年10月、日本で開催された WordCamp Tokyo 2023 に参加しました。これは、私が初めて参加したオフラインの WordCamp であり、初めて WordCamp にスピーカーとして登壇したイベントでもあります。これまで、インターネットやビデオ通話を通じてしか交流した事のない沢山の仲間たちと会う事ができました。
\n\n\n\n Photo by Chiharu Nagatomi / CC BY 4.0\n\n\n\nissue や プルリクエストに関わらず、WordPress コミュニティでは日々沢山の問題提起がなされ、議論され、決定がなされます。
\n\n\n\nこのプロセスの中で、私が非常に重要だと思う事は以下の三点です。
\n\n\n\nWordPress コミュニティで行われている議論や決定は、ほぼすべてこの三つの理念に基づいているはずです。ソーシャルメディアの発達にともない、沢山のネガティブな感情に触れる機会が多くなってしまった現在、この心理的安全性は私の精神を癒してくれます。
\n\n\n\nWordPress コアも Gutenberg も完全ではありません。膨大なチケットや issue があるように、解決すべき問題は山積みです。
\n\n\n\n必ずしもコードを書かなければならないというわけではありません。勇気を出して一歩踏み出し、自分が問題や課題だと思っている事をオープンな場で共有すれば、それを目にした人達がその問題を解決し、世界の WordPress ユーザーの役に立つかもしれません。
\nThe post My Journey as an Engineer with WordPress – エンジニアとしての WordPress の旅 appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 23 Jan 2024 23:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Aki Hamano\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"BuddyPress: BuddyPress 12.2.0 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=332922\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://buddypress.org/2024/01/buddypress-12-2-0-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1399:\"Immediately available is BuddyPress 12.2.0. This maintenance release fixes four bugs. One of them was pretty annoying for users first activating BuddyPress with version 12.1.1. In this particular case, the 12.0 deprecated code wasn’t loaded which could cause nasty errors with 3rd party BP plugins / themes not ready yet for the modern BuddyPress (12.0.0 & up). That’s the reason why we’ve been working hard and as fast as possible to quickly wipe this bug.
\n\n\n\nFor details on all changes, please read the 12.2.0 release notes.
\n\n\n\nUpdate to BuddyPress 12.2.0 today in your WordPress Dashboard, or by downloading it from the WordPress.org plugin repository.
\n\n\n\n\n\n\n\njnie, roberthemsing, vapvarun, emaralive, & imath.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 23 Jan 2024 21:15:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"Do The Woo Community: More Takeaways from State of the Word with Miriam, Nik, Patricia and Mariano\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78917\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://dothewoo.io/more-takeaways-from-state-of-the-word/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:366:\"One more show with reflections and takeaways from State of the Word 2023.
\n>> The post More Takeaways from State of the Word with Miriam, Nik, Patricia and Mariano appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 23 Jan 2024 09:48:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:24:\"Matt: Art No One Can See\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=110719\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://ma.tt/2024/01/art-no-one-can-see/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:492:\"\n\n\n\n\nProprietary software is like creating art which no-one can see. Open Source elevates software engineering to a collaborative art form. Code is poetry.
\n— Tom Willmot
Some choice words from Tom Willmot, who was watching Kirby Fergusen’s Everything is a Remix, which I’ll check out now.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 22 Jan 2024 21:51:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"Matt: Open Source Creed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=110716\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://ma.tt/2024/01/open-source-creed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:247:\"Every human has an intrinsic right to put their creative work into the commons. Once freed, work can never be withdrawn, and it has the opportunity—but not the obligation!—for everyone to improve upon it.
\n\n\n\n(v1)
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 22 Jan 2024 14:27:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WordPress.org blog: WP Briefing: Episode 71: New Year, New Blog!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16745\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://wordpress.org/news/2024/01/episode-71-new-year-new-blog/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:18615:\"In the latest WordPress Briefing, Executive Director Josepha Haden Chomphosy revisits our roots in blogging and breaks down the essentials of starting your first WordPress blog. Tune in to Episode 71 for practical tips and inspiration to kickstart your blogging journey.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, we’ve got a throwback episode about blogging. If you’re like me, you sometimes miss the early days of blogs, where the words were a little more pensive, and the images were a little less professional. If you’re on a slow hobby journey like so many of us are right now, give this one a listen.
\n\n\n\n[00:00:58] (music interlude)
\n\n\n\n[00:01:05] Josepha: You may be one of these contributors I keep mentioning. You may be an agency owner or freelancer. Maybe you’ve wondered how to make a WordPress blog for your big idea. Or maybe you’re one of the many people who use WordPress for their own project or business.
\n\n\n\nBefore WordPress was known as a content management system, as a way to get sites online fast, it was a blogging tool. We have long since outgrown that, but even 20 years into our journey, blogging is still a key part of what WordPress enables you to do. That’s because, even after those 20 years, the mission of WordPress is still the same, and that is to democratize publishing.
\n\n\n\nTo help people have a place online where they can tell their stories, or share their projects, or set up their businesses. If you’ve ever tried to set up a blog, you know that there isn’t a lot of information about what to know before you get going at all. So, I’m going to talk about that a little bit today.
\n\n\n\n[00:02:06] Josepha: And just by the way, if you heard the word blog right now and thought, Oh, Jospeha, how old fashioned. I think it’s important to remember that there’s a business advantage to having well-written, relevant content on your website. And if you’re not blogging for business, because not all of us are, then the benefits are a little different but still important to my mind. Things like the cathartic benefits of journaling, a chance to build community, and the general importance of preserving wisdom for the ages.
\n\n\n\nAnyway, back to the topic at hand, before we can get to any of the fancy things that WordPress can do nowadays, it’s important to know a few things as you get ready to set up your first-ever website. So let’s dive in.
\n\n\n\nHere is how you need to get yourself started. First, have an idea and a plan. So, have an idea for what you’re doing, the concept of your content, who you want to reach, but also some concept of a domain name. I would encourage you to not necessarily get your heart set on a domain name at first, cause like, if you want the domain name WordPress.org, like, we own that, you can’t have that. But if you know that you want a domain like ‘WordPressbloggingforthefuture.com’ like, that one might be more available. And if you know kind of the words you want in your domain, then you can be a bit flexible about what is there.
\n\n\n\n[00:03:30] Josepha: The second thing that you need to do is that if you are just getting started, ask yourself the question, what sort of host do I want? We kind of mention all along the WordPress process that, like, you need a good host, but it’s not always clear where that decision has to happen. It happens right here at the start before you even know what WordPress is most of the time. So, the earliest question that you have to answer for yourself is, what sort of host do I want? Where do I want my site to live? So ask yourself how much you want to get into the maintenance and configuration of your website and the hardware that it lives on versus creating content or keeping your shop up to date. There’s this whole spectrum of hosting options, and they range from full service, where they will keep your WordPress software up to date and provide daily backups, and have customer support if something goes really wrong.
\n\n\n\n[00:04:23] Josepha: So it ranges all the way from full service like that, all the way down to essentially zero service, just kind of hands off. They give you a space to keep your WordPress software, to keep your WordPress site, but they leave everything else up to you. They leave the backups up to you; they leave updating up to you, things like that.
\n\n\n\nSo that’s the first thing you have to ask yourself and the first question you have to be able to answer. Most of the time, you will want to start with one of the full-service options. That way, you know that your software is set up correctly and safely from the start. And as you learn more about the software, and what you want, and what you need, and you have the ability to learn in the time that you have, the more that you can add on either services with the existing host that you chose or moving to a different host; however, that works out for you.
\n\n\n\n[00:05:09] Josepha: So if that one sounds like the right option, then you choose a host, go to their site, and actually, most of them will have a way to walk you through how to set up a WordPress site inside their system. Most of the time, it’s just one click, and then they ask you some questions to get some configurations right.
\n\n\n\nThe other option that on the like zero, zero service side, that’s not quite fair, but you know, on the other side of that spectrum, that probably will be appealing to you if you are already familiar with code or already know how to manage a server, or you know how to work in this thing called cPanel, etc. So if you already have a lot of information on how all of that works, you can, if you want to, head over to WordPress.org/download and you can download a zip file of the WordPress software and set that up in your own environment. Okay, quick check here. If this all sounds roughly doable to you, or at least it feels like we’re in the right starting point, but you find yourself thinking, gosh, I just wish she would slow down a little, I’ve got you covered.
\n\n\n\n[00:06:17] Josepha: In the show notes, you’ll find a link to one of the LearnWP courses for getting started with WordPress. There’s a section on choosing a host, as well as various other early steps of this process. If you felt like I blazed through all of that, which, honestly, I kind of did. You can work through those lessons in that course at your own pace, and it’s really a very good guide.
\n\n\n\nAll right. So let’s pretend we did all of that. Now you’ve got yourself a website. The thing that you will want to do next, or rather the first thing that you’ll notice once you get your site up and running, is that there’s this ‘Hello World’ post. There’s a post that already exists in there. The Hello World post is a placeholder for the common features of a blog post.
\n\n\n\n[00:07:03] Josepha: There, you can find your featured image, your title, your content, and even some fake comments. You can either edit this post so that you can see how your writing will look from the start, and you can kind of compare, like, okay, the Hello World part over here on this page exists in this field over here on this page. So you can kind of see where everything works, how it all looks together. Or, if you’re more familiar with WordPress or CMSs in general, you can simply remove that and start fresh. We’ve got now a website. We know kind of how to look at our posts and create posts, where comments are, where they can be moderated, and stuff.
\n\n\n\nAnd so, the most fun task for everyone is choosing a theme. But if it doesn’t sound like a fun task to you, I can help you kind of do some choose-your-own-adventure guiding questions here. Firstly, you can ask yourself how you want the site to look. Do you want it to mostly be a lot of photos or entirely words? Mostly animations? You can head to the theme directory and search for a theme with most of the features that you want. There’s like a filtering system where you can put in, like, you want, three columns so that you can have three columns of text if you want it to look kind of like an old school newspaper kind of layout and things like that.
\n\n\n\n[00:08:24] Josepha: There’s also a way to look for themes inside your instance, your WordPress site, but like, if you haven’t set that up yet, but you do still want to see kind of what your theme options are, you can go to WordPress.org/themes and take a look at what’s out there. Just as a quick side note, if you get to that theme directory, if you get to WordPress.org/themes, and it feels overwhelming, which I can understand, I recommend starting with a theme that is designed for blogging specifically, so that you can see how things look right away. And there’s actually a theme that does come with every WordPress site, so if you’re not ready, you can skip this thing entirely. And just work with the theme that’s already there. Every WordPress instance ships with a theme, and it is fully functional when you get your site up and running, so you don’t need to choose a theme right now if you don’t feel ready. And then the other very fun thing that people do with their WordPress sites, is to add plugins to them.
\n\n\n\n[00:09:20] Josepha: Plugins are these little pieces of software that you add on to the WordPress software that lets it do additional things. It adds additional functionality to it. The questions that you can ask to kind of guide yourself through what sorts of plugins you might want what sorts of functionality you might want to add to your site are a little similar to the ones that you want to ask for figuring out which themes.
\n\n\n\nSo, figure out if there are tasks that you need visitors to do. Do you need them to contact you? Do you want them to watch a video? Should they review and respond to questions? If you have a concept of the things that you want users to do on your website, then you can head to the plugin directory and search for a plugin with features that you need.
\n\n\n\n[00:10:05] Josepha: Also, there are just endless lists of recommended plugins out there. If that is something that you find valuable as part of your research, those are also easy to find. And as a general side note here as well, there are even more plugins than there are themes. So if you have gotten to this point and feel like you don’t quite know the answers to the questions that I shared, and it’s going to be a while until you feel like you can know what those answers are. That’s totally fine. I’ll tell you this, I have never seen a site without a contact form. So feel free to begin your journey there. There are a lot of great plugins for contact forms, and it can kind of help you figure out how to work with plugins in that way. So, yeah, I made it sound like you can get a WordPress website built in like seven minutes.
\n\n\n\nAnd on the one hand, you definitely can. And on the other hand, it’s still a little bit more complicated. So here I have a final note for everyone. You will hear around the WordPress ecosystem and, obviously, hear some things that could make you feel a little nervous about doing this for the first time.
\n\n\n\n[00:11:10] Josepha: Things like the five-second installation, which WordPress has been famous for for years, but also about how easy and simple it all is. And as somebody who was once in the position of learning WordPress for the first time, like I first encountered a WordPress site in 2009, and I started learning how to use WordPress in 2010.
\n\n\n\nI can say with confidence that once you learn it, it’s easy. We are the easiest of the hard options for CMSs like content management systems are just complicated. But we are the easiest one out there. And so, as you’re learning, I want to just remind you to celebrate your small wins along the way. If you feel like you’re late to this blogging game like you should have had a website for years, I mean, sure, that could be true.
\n\n\n\n[00:12:01] Josepha: And yes, the best time to plant a tree was 20 years ago, but the second best time to plant that tree is today. WordPress didn’t start out powering over 40% of the web, and your first site can’t be immediately measured in the millions of readers. So, what will your small beginning lead you to?
\n\n\n\n[00:12:18] (Music interlude)
\n\n\n\n[00:12:25] Josepha: And now, our small list of big things. Today we’ve got some look-back items and some look-forward items. So let’s hop right in.
\n\n\n\nFirst thing is we have a year in review with the themes team. So much amazing work has been done by the themes team over the past year, both for reviewing themes and creating them. So I’ll leave a link to those in the show notes.
\n\n\n\nWe also have a post out that just has some general celebrations from teams around the community. I’ll leave a link to that. It probably has been linked in quite a few places, but you know, we don’t always embrace those moments of celebration. We don’t always embrace our wins. And so it’s always good to share those early and often. There are probably more than just those two. So if you posted one or you saw a really interesting one that you think that we should know about, don’t forget to share it.
\n\n\n\n[00:13:16] Josepha: Next, we have a leap into 2024 with Site Editor tools. So, on the new Developer Blog, if you haven’t seen it yet, there is a lot of excellent content there for whether you are like an advanced developer in WordPress or you’re kind of intermediate and ready to move into your advanced developer era.
\n\n\n\nThe Site Editor will give you a powerful way to visually create every part of your site and tell your story. And this post will help you to kind of see how to handle everything from big style changes to simple copy updates, all in a single place. We want to make sure that you get the most out of your WordPress this year. And that post will give you a few standout tools and features that you’ll want to try.
\n\n\n\nYou’ll also want to keep an eye out for updates as we move into 2024 around team reps. So each team in the WordPress project goes through a process to review and elect team reps, and elections are happening now.
\n\n\n\n[00:14:12] Josepha: Along with things that are happening now that you should keep an eye on, the annual goals, our big picture post has gone out as well. It went out at the end of the week last week. There’ll be a link to all of these in the show notes. And yeah, keep an eye out for, hopefully, a fantastic 2024 in WordPress.
\n\n\n\nAnd that, my friends, is your small list of big things. Don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there’s a new episode. And if you like what you heard today, share it with a fellow WordPresser, or if you have questions about what you heard, you can share those with me at WPbriefing@WordPress.org. I’m your host, Josepha Haden Chomphosy. Thanks for tuning in today for the WordPress Briefing, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:14:57] (Music outro)
\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 22 Jan 2024 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"Matt: Upcoming Ignite Talk\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=110700\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://ma.tt/2024/01/upcoming-ignite-talk/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1255:\"
On January 25th, this upcoming Thursday, I will be speaking at Ignite San Francisco on the topic of Automattic’s sabbatical benefit and my upcoming one, alongside Adam Savage, Shelby Devlin, Elise Hu, Leanne Gluck, Kat Lague, Amanda Nagai, Joshua Schachter, Emily Quinn, Rose Bloomin, Jamie Joyce, MaSovaida Morgan, Todd Kerpelman, Brett Kistler, Shary Niv, and Connie Yang. The event will sell out so get your tickets soon!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 22 Jan 2024 07:27:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"Gutenberg Times: Gutenberg Changelog #95 – Gutenberg 17.5, Early Testing of WordPress 6.5 and Block Themes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://gutenbergtimes.com/?post_type=podcast&p=27107\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://gutenbergtimes.com/podcast/gutenberg-changelog-95-gutenberg-17-5-early-testing-of-wordpress-6-5-and-block-themes/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:57531:\"In this episode, Carolina Nymark and Birgit Pauli-Haack discuss Gutenberg 17.5, early testing of WordPress 6.5 and block themes
\n\n\n\n\n\n\n\nShow Notes
\n\n\n\nLive Q & As with Carolina Nymark
\n\n\n\nQuick Tip: How to use a classic menu in the navigation block of a block theme
\n\n\n\nStay in Touch
\n\n\n\nTranscript
\n\n\n\nBirgit Pauli-Haack: Hello, and welcome to our 95th episode of the Gutenberg Changelog podcast. In today’s episode, we will talk about Gutenberg 17.5, early testing on WordPress 6.5 and block themes, and everything in between. I’m your host, Birgit Pauli-Haack, curator at the Gutenberg Times and a full-time core contributor for the WordPress open source project sponsored by Automattic’s Five for the Future Program. I’m so thrilled we were finally able to make it happen. Carolina Nymark is on the show today. Carolina is a core contributor sponsored by Yoast and has been an evangelist, educator and blogger about block themes when we all knew that it was coming but had no clue what it will be and when we still called it full-site editing.
\n\n\n\nMany of you might have visited her site, fullsiteediting.com where she teaches developers and site builders how to use the block themes. Carolina also joined us on the Gutenberg Live Q&As multiple times to talk about that. And I’m so happy to have you finally also on the podcast. Welcome, Carolina, and how are you today?
\n\n\n\nCarolina Nymark: Thank you. I am very well. Thank you. So we are recording this on a Friday in January, and I have been back at work maybe only two weeks.
\n\n\n\nBirgit Pauli-Haack: Okay.
\n\n\n\nCarolina Nymark: I had December off, which was very, very nice. I used WordPress, but I did not code anything for almost five weeks, so it was a really nice break.
\n\n\n\nBirgit Pauli-Haack: Oh, yeah, I imagine that. I got about two and a half weeks off over the holidays, but I’m back. Also two weeks. So it’s all a new year and I hope you got into the new year well.
\n\n\n\nSo there have been early discussions, you and I and with others that we’re working on it, early discussions about the block themes in 2020 if not 2019. I’m a little bit unsure and I really want to thank you for being such a great advocate and educator for block themes. I think it has changed WordPress quite a bit. We are not there yet entirely, but how do you feel about block themes now that you have to work with them over four years?
\n\n\n\nCarolina Nymark: Well, it doesn’t feel like four years. It feels like it’s been much shorter. I agree, it’s not there yet. While I love working with the site editor and creating visual layouts that I can tweak as a coder, I do love that, but I still wish that we would have come further.
\n\n\n\nBirgit Pauli-Haack: Yeah. So what do you think is missing? Do you have examples of what you find missing from when you go from a classic theme building and want to recreate the magic also in block themes?
\n\n\n\nCarolina Nymark: Yeah. So one of the big parts is that when we use PHP to build our themes, we use a lot of conditions if else to display different things depending on what’s happening, what the user is doing, what they’re viewing. We can’t really do that with blocks. At least not with the current core blocks that we have. What is also missing is a way to manage and base custom fields. Of course, the Gutenberg developers are very aware about the need for custom fields management, and it has been of course ongoing discussions for several months and it will happen in some form.
\n\n\n\nRight now it has had to step back a little bit because a lot of the Gutenberg developers need to focus on the new data views, which is part of the… Well, it’s going to be a part of the admin redesign.
\n\n\n\nBirgit Pauli-Haack: So yeah, custom fields that I have seen so early. So there was this whole hangout last week with early views on what’s in the roadmap of 6.5 and also even if it wasn’t on the roadmap to go to 6.5, but it’s actively worked on, and one of them was to have in the block toolbar a button that you can connect something in the content of the block with a custom field.
\n\n\n\nI don’t know how that all surfaces, but that is really interesting approach because you don’t have to go out and go into a different interface. You can all do it there. But apart from there, the conditions are pretty big. I think what it comes down to is that you build a lot of templates for different kind of cases, use cases, and that duplicates code quite a bit. So when you want to migrate a site from a classic theme to a block theme, there is no one click conversion.
\n\n\n\nBut what would you think a site editor should do? So I had the same conversation with Sarah two weeks ago and because I’m doing that for the Gutenberg Times, and I’m trying to find a good approach that other people could follow. So let me tell you what I do. I installed the health and troubleshooting plugin on my life site and then switched off all the other themes and switched on the themes that I wanted to use.
\n\n\n\nI was testing the twenty twenty four I was testing Frost and some other of the block themes, one or two of them from Edna Snoren or Ellen Bauer and then see how my site changes with the new block theme. And then I made notes what needs to be changed. So this archive page needs to change and that needs to change, and here the block don’t. The biggest hurdle was that my featured image on the block loop, on the archive page is a landscape, and most of the themes that I tested, the feature image was portrait format. So that kind of thing, but that’s I think not a big… That’s an easy fix. You can change the template, you can change your aspect ratio and you’re done with it.
\n\n\n\nSo I have my notes. I have my scope of the changes that I need to make, and then I’ll create a staging site, install the create block theme plugin, and then make my changes there. And then I can export that theme and import it into my live theme. Is that a good process or as good as any?
\n\n\n\nCarolina Nymark: I do think it’s as good as any right now, but it really does sound way too complicated for the, how do I say it, the average user. And it’s difficult. How are we going to help them? How are we going to make it easier? But it also depends. It all depends on how complex your existing theme and your existing site is. But yes, start with pen and paper. Really write down the already must haves and do spring cleaning. If there are things that you don’t need, remove them. And then you won’t have the problem of trying to recreate at least those spots.
\n\n\n\nBirgit Pauli-Haack: Yeah.
\n\n\n\nCarolina Nymark: I mean if you’re switching to a completely new theme, of course, there are going to be a lot of things that don’t match your current website. So they’re definitely going to be tweaking. And create a block theme is a great tool because yes, you can activate any block theme and export it as your own. So of course you’re not limited to using the default themes. If there is a block theme to define that matches what you want closer, pick any of them. What you want to look at though is the last updated date. You don’t want to pick a block theme that was updated in 2020 or 2022. You want one that is…
\n\n\n\nBirgit Pauli-Haack: Good reminder.
\n\n\n\nCarolina Nymark: … continued, developed, and supported.
\n\n\n\nBirgit Pauli-Haack: Good reminder. So it should be 2023 or something like that and not the default theme, but the update should be at least in 2023 if not in the last three months or so. That’s definitely a good point.
\n\n\n\nCarolina Nymark: So if you’re picking from wordpress.org. Look at the reviews of this theme. Look at the support firm. Is the developer responsive or maybe they’re directing you to a different support firm where they’re active. That’s also absolutely fine. But just look to see that there is someone who’s able to help you if you run into bugs or if you’re blocked somewhere.
\n\n\n\nBirgit Pauli-Haack: Yeah. Well, most of the time when I switched themes before with classic theme to classic theme, there were always tweaks. There was no one switch and everything was good. There was always a little bit… CSS kind of change here and template missing here, and the condition are not working right. So I think that’s pretty much to expect when you switch themes and normally you don’t. It’s the third switch in five years for the site. So I think it’s pretty much on par with that. And I’m also late, but I also want to do some experimentation with the new features that are there, that are coming out, like the interactivity of PI and the block hooks and that kind of thing.
\n\n\n\nIt was really hard to do this without the block theme because they’re all built for block themes and the latest. So that’s why I’m switching over on the site. So that’s one thing, the site migration… But you come from the classic theme building. You’ve been a theme team rep for many, many years and have been… So if you are a theme builder and you want to create a block theme, what are the hurdles to overcome? Are there any blockers, pun intended, especially mental blockers? Are there something that is something people need to get on with it, so to speak?
\n\n\n\nCarolina Nymark: Yes. Mental blocker absolutely are big at perhaps the code challenges, unless you’re building something very, very highly custom and specialized. So as a coder, if you really enjoy coding, you might love PHP, and then suddenly, if you’re not working with a designer, of course because we have two different… Of course, more than two different ways to do this. But if you’re on your own and then suddenly switching from writing your templates in your code editor, and you have to go to this visual interface, you really need to learn how to maximize the blocks.
\n\n\n\nYou do need to learn how to sketch, draft the layout in the editor, and then you will go and make your tweaks. Once you have exported your base layouts for one template or 10 or maybe four is more realistic. When you have four templates, you have what font sizes, what colors, what spacing you’re using then you’re going to tweak the details in your exported theme.json file and you tweak the code in your templates. But you still have that element where you need to go to the visual interface and actually move things around, change the alignment, etc. And it’s a big change of course.
\n\n\n\nBirgit Pauli-Haack: But it’s also lowering the barrier for those who don’t know how to code to create their own themes. So I think it’s a good balance to get more people involved in creativity and creating themes and do some designs. A lot of designers are actually not coders per se, and they might… I think what’s still missing, going back to the earlier question, is actually a user interface for editing the theme.json file. I know it’s all in the database and you can export it, but you still have to fiddle with that long and the theme.json files, the more features come in, the longer it’s going to become and the more unwilling it comes.
\n\n\n\nCarolina Nymark: Oh yes.
\n\n\n\nBirgit Pauli-Haack: Yeah. There are VS Code extensions that help with that, but I think you need to really squint quite a bit when you read the code to get into the right settings and all that.
\n\n\n\nCarolina Nymark: I absolutely three. So not all the settings in theme.json actually have an interface. It probably shouldn’t be exposed to all users, and that’s where do we draw the line? Do we really add an advanced view to the site editor or does it need to be in a plugin? And several people of course have tried to build this plugin because we do need it and have not succeeded or have needed to stop halfway because… Well, I can’t really tell why.
\n\n\n\nBirgit Pauli-Haack: One reason is probably…
\n\n\n\nCarolina Nymark: It’s just not easy. The base coding in Gutenberg, it just doesn’t make it easy to do that kind of option page, or at least not right now.
\n\n\n\nBirgit Pauli-Haack: I can also see that it’s really taxing to build a feature for something that’s so inactive development and has updates every two weeks to keep up with it, especially when you have a product. So I can see that the initial momentum getting this, “Oh, this is a great idea and let’s build it,” kind of weans away when after a year or two you still have to go in every month and update this thing because there’s new features or things have changed.
\n\n\n\nWell, I think great way to talk about block themes and thank you for that. Are you planning to work further on the fullsiteediting.com or do you think that the new block handbook has been overhauled enough to say, “Oh yeah, now documentation.” I think there was a reason why you graded that because there was no documentation and there was a lot of need for explaining the concept and all. But the new developer theme handbook has been overhauled in the last, I don’t know, four or five months. Do you think that the documentation is up to par now?
\n\n\n\nCarolina Nymark: Yes. So Justin Tadlock who did most of their work on the handbook has been amazing. The handbook has been greatly updated and fullsiteediting.com has not, because I have not had the time. And it’s a bit of a stressor. I guess I do want to keep it up to date. I want to fight about what I’m exploring, what I’m finding, what problems I’m running into, and of course maybe some more code examples. It’s difficult for me to prioritize.
\n\n\n\nBirgit Pauli-Haack: I imagine.
\n\n\n\nCarolina Nymark: So there’s room for both. So fullsiteediting.com of course I can express opinions in a whole different way that you can’t do in a handbook, which needs to be very strict and act even a bit friendly.
\n\n\n\nBirgit Pauli-Haack: Neutral.
\n\n\n\nCarolina Nymark: Yeah, I’m still a little bit apprehensive about how we’re going to keep it up to date. So even if we only have now three releases per year, that goes into WordPress Core, it’s still a lot to keep up with.
\n\n\n\nBirgit Pauli-Haack: You need more volunteers.
\n\n\n\nCarolina Nymark: Yes.
\n\n\n\nBirgit Pauli-Haack: So if somebody wants to contribute to documentation specifically for the theme handbook, what would be the steps apart from having a Slack account and having a wp.org account, and a GitHub account?
\n\n\n\nCarolina Nymark: The easiest way is to, first of all, reach out in the theme review Slack channel from your account, and we can guide you a little bit more from there. So the team handbook is currently written in WordPress on the website. So the content is not managed right now on GitHub. It’s not marked on files. It’s actually WordPress. It’s a poster page custom post type.
\n\n\n\nBirgit Pauli-Haack: Oh, that lowers a lot of barriers actually.
\n\n\n\nCarolina Nymark: But all the issues when we see that the page needs to be updated, we add our issues to the documentation teams issue tracker on GitHub.
\n\n\n\nBirgit Pauli-Haack: Oh, cool. So if you’re on the documentation team, you already know how the process works. That is really good. So dear listeners, if you have an aptitude for technical writing, your English is good enough, so Carolina is a non-native speaker, and I as a non-native speaker can read it. You are in it. You can join the team and you’ll have some great people there that help you. I know that Justin Tadlock has quite some onboarding and he’s happy to help anybody also with writing and do some copy editing.
\n\n\n\nSo you don’t have to be scared just because you’re not a native English speaker to do that. All right. So this was all about block themes and I’m really glad that we talked about some of the issues there. So let’s get on with the show.
\n\n\n\nWe sometimes also answer some questions that we get either from Twitter or listener question. And this question came through Twitter and that is how to use a classic menu in the navigation for block theme. And it’s very hard to find when you… And so I put it a little tutorial together, a quick tick I call it because it’s less than a hundred words or so on how to use it.
\n\n\n\nIt’s mainly the screenshot and where to find things, a little video. So you need to grab the header in the site editor and then the menu that is there from your theme. And then there is on the right hand side, there’s this toolbar or the sidebar where the block settings are normally and there’s one three-dot menu where the switcher where you can see all the classic menus listed that you had previously on your site and then you select it and it’ll magically appear in the navigation block.
\n\n\n\nSo I think you don’t have to recreate all the classic menus that you had before when you switch it. That is definitely a hidden gem. I don’t know if you can surface it even better. We need to kind of talk to design about that, but that’s where you find it and it’s your secret superpower to know where it is now.
\n\n\n\nNormally, I think, if I understood this correctly and Carolina you help me out, when you only have one menu, the block theme magically adds it. If a navigation block is in the template, it will be added to the navigation block as a default. But if you have more than one classic menu, it doesn’t know which one to pick. So it kind of makes it up as it goes along. I think when you switch from twenty twenty to twenty twenty four, it takes the social menu, which is kind of weird, but that’s the randomness of this feature. But it also points you right there, this is something to fix.
\n\n\n\nCarolina Nymark: At least that problem is quite obvious because it’s not the correct content inside the block.
\n\n\n\nBirgit Pauli-Haack: Yeah. So, listeners, that was our quick tip of the week.
\n\n\n\nWe also have some upcoming events that are on the list that happen in all kinds of different places. So first of all on February 7th at 12 noon UTC, the media component maintainers come together in a meeting to discuss phase three media items that could be ahead of development or phase three. And Anthony Burchell who is one of the maintainers, invites you to be part of it. And if you haven’t contributed to any code yet in the recent years, that is definitely a good place to see what work needs to be done and how it’s organized.
\n\n\n\nThen February 8th, a day later, there will be a hallway hangout to discuss intrinsic design and how to use it in a real life projects with the block editor and the block themes and we will have some interesting people there. Fabian Kagy is going to be there, Tammie Lister, Justin Tadlock. They’re all proponents of the intrinsic design testing. Tadlock wrote a nice introduction to that on the developer blog a few months ago, but it’s definitely… But Fabian and Tammie, they have also some ideas of what’s still missing, what you can’t do with intrinsic design, which you still would need to do with your own CSS and some conditional coding and templates to get this going.
\n\n\n\nAnd they bring some solutions with them. Then not so far out January 25th at 15:30 or 3:30 UTC, there’s a developer livestream reviewing Gutenberg 17.5 by Ryan Welcher. He does it on Twitch. It’s not a scripted show, he just dives in into a topic or multiple topics and shows some code. If you haven’t followed Ryan on the Twitch stream, you can also follow him on YouTube. And he has this fabulous series of the block development cookbook. Every show is a little recipe on how to do things with a block editor development. And then also next week is the extensibility issued triage meeting on January 23rd at noon UTC.
\n\n\n\nThere’s a project board with increasing Gutenberg extensibility and we go over some of the columns there and see if we can move some of the issues or PRs forward to be slated for some of the major releases this year. So it’s going to be a real good… Yeah, there’s some agency developers in there. We also have joined by Gutenberg developers. So this is a chat meeting. It’s not a video meeting or something like that. Carolina, do you know of any events that listeners might, we could let them know about?
\n\n\n\nCarolina Nymark: There’s rumors that there might be an upcoming hallway hangout about migrating from classic themes to block themes. But it’s not scheduled yet, but if you have the chance, definitely join one of these that we just spoke about.
\n\n\n\nBirgit Pauli-Haack: And speaking of events, there’s always in the theme review channel, there’s a theme meeting. When do they happen?
\n\n\n\nCarolina Nymark: It’s every other Tuesday. I’m sorry, I believe it’s at 4:00 UTC. I’m usually unable to attend because of the timing, so I don’t have the exact time.
\n\n\n\nBirgit Pauli-Haack: Oh, okay. Well, we can look it up. Tuesday testing JavaScript. Theme biweekly 4:00 PM, Yes. 4:00 PM UTC. And the next one is, it’s on the 23rd. So next week, Tuesday is the fourth Tuesday. So it’s on the second and the fourth Tuesday, 4:00 PM UTC. And so if you want to be part of the theme development or theme review documentation team, you can join there and meet all the people there.
\n\n\n\nCarolina Nymark: So during these meetings, we usually recap how many new themes went live this week, for example. We also repeatedly bring up things like, are the requirements still correct? We need to update them. What are we going to do about react-based themes, settings, pages, onboarding of users when we have a block theme of a need, an easier way for them to select the front page. So both about theme reviews, but also really wide topics. But they are, again, just posted that you can read of course, and also proposed topics too.
\n\n\n\nBirgit Pauli-Haack: And if you want to follow up on some of them, the summaries are posted on the make theme blog as well. Cool, cool, cool. Those are the events and meetings. There’s under make.wordpress.org/meetings, a calendar of all the teams meetings, not only the theme team but all the teams. So it gets a little bit overwhelming and you shouldn’t join every channel on WP Slack, but pick the team that you’re involved in or you want to be involved in. You can definitely be in a meeting every day of the week.
\n\n\n\nCarolina Nymark: Oh yes. There are often meetings that collide as well if you’re interested in several topics.
\n\n\n\nBirgit Pauli-Haack: And sometimes they’re Slack meetings, so you can actually switch between the meetings a bit because people need to type things.
\n\n\n\nSo speaking of extensibility, Fabian Kagy from 10up and also has been a guest on the show quite often, he started a conversation about extensibility for the new admin views, and Riad Benguella posted a great response on how extensibility is actually approached and what they’re planning once they have the APIs are finalized and they want to create APIs for retracing new fields, new layouts, new field types.
\n\n\n\nI like the new layouts. The grid layout and the preview layouts and all that. Also, defining default views and fields and allowing third-party developers to have their own views for their pages. What they haven’t yet put in there, and they want to still do this before any extensibility is considered is inline editing and editing the fields and views in the UI.
\n\n\n\nSo I have not seen any design views for those interfaces yet, so that might still be a little bit off, but I’ll share the issue and the comment in the show notes, of course, like everything else that we talked about. But Riad is also summarizing the approach that the built the APIs, then UIs, and then if it all works together and the APIs are stable, then open that up to third-party developers to using plugins and themes.
\n\n\n\nBut he also has a suggestion on how third-party developers can start experimenting with it, and that is using the WordPress data views NPM package and start testing those. Documentation is available on the packages read me file, and you definitely can connect with Riad if you have any questions or something like that. But I think it’s time to start looking at that if you’re a plugin developer or a theme developer, just to make sure that you start getting the mindset and you see what the users are going to see. Any comments?
\n\n\n\nCarolina Nymark: So glad that this question was asked and highlighted, and I’m happy with the answer. And as always, when this is like, “We want it now,” we can’t have it yet. And third-party extenders, plugin developers, we really do need to help testing. Again, we need to be very clear in our feedback on what we need because we have to leave that feedback when there is still a chance to make changes. If something is not what we expect, the earlier the feedback, the better. Easier it is to respond to and address. I also do my part of the data views.
\n\n\n\nI need to use it more to really get used to it. I have problems with the very, very narrow list. So on the left side you have a brief description, the name of your, for example, your template or your post. This part is very narrow, but I do like that you can switch views. So you can choose if you want the list, grid or a table. And there are so many more things that you can customize with filters already. So I really like that.
\n\n\n\nBirgit Pauli-Haack: Yeah. Also, like the grid layout patterns in the pattern data views or for… It would be really beautiful for the media library to have a grid layout like it is now. And even posts. If you want the feature image and you don’t need a list, but you want also kind of see how… Which have featured images and which don’t.
\n\n\n\nWhich brings us to the next topic that we have here that is early opportunities for testing. Thank you for bringing that up. Test, test, test.
\n\n\n\nCarolina Nymark: Yes.
\n\n\n\nBirgit Pauli-Haack: So Anne McCarthy has published a post called Early Opportunities to Test WordPress 6.5 ahead of beta 6.5 that is scheduled for February 13th. These are early opportunities to feedback and testing it for your own sake. It’s only a selection of features in the post, but it’s very good in the instructions of what you can do and what you should test. So a part of the burden for testing is you have to come up with what is it that I actually want to do? Have those decisions and make a list of it. And Anne McCarthy has done that particular work for you and shows you how to test the data views. Also, the pattern overrides and the font library, of course that has been in the works for quite a bit, and the robust revisions.
\n\n\n\nSo for templates and styles you now can have… In 6.4, we already have revisions, but now those are actually getting to the next step and being really cool.
\n\n\n\nCarolina Nymark: The revisions are a really nice update. I also hope that we can do something to improve the post-op block editor revisions, which are not as easy to use, say, style visions.
\n\n\n\nBirgit Pauli-Haack: Yes, absolutely. And in the post you also find ways on how to set up test websites for that. I also will share a link to the playground with the Gutenberg nightly that actually… At least for the data views, because you need to enable the experiments to do that for the data views as well as for the pattern overrides. So we have some playground instances… Not have some, but we build the blueprints for those so you can call them up in WordPress playground, which is a nice browser-based WordPress instance. It’s really amazing how that would work for someone who has done work with so many servers.
\n\n\n\nIt’s a long, long post, but it has all the details that you need for each feature. It’s divided up into explaining the feature, prerequisites and then test instructions and what you could do with it. Feedback, you could leave it on the post if you have some feedback or if something is not working, or you could do that as a bug report on the GitHub repository or just post it into the co-editor channel and we’ll figure out which part of your experience is actually the bug report or a feature request or something like that.
\n\n\n\nSo it’s not always easy to get it right for a GitHub issue, but there are people here to help you. Definitely. Have you tested any of those features or looked at those apart from the revisions you said?
\n\n\n\nCarolina Nymark: No, I’ve tested them on my own. I haven’t read the full testing instructions. I mean, I have some feedback that I need to add, document and write down, and perhaps why not start working on fixing it as well. So I need to do that maybe next week.
\n\n\n\nBirgit Pauli-Haack: Yeah. Do you have something else that we could talk about it in community contributions?
\n\n\n\nCarolina Nymark: We spoke a little bit about how to find the team’s team and how to help with the handbook or just join the meetings. But of course there are so many teams that you can contribute to, and the application for the contributor mentorship program has opened. So this is for the first quarter of 2024. It is open for both mentors and mentees. So if you’re an experienced, well actually, user. You don’t even have to be a developer. If you’re an experienced WordPress user, contributor, you can apply as a mentor. To be a mentee you do not have to have any previous experience, just be engaged and want to join.
\n\n\n\nSo the mentorship program is a one-on-one mentorship or a group mentorship, which is new. So the group mentorship is new. You can actually apply to work on a specific project together with others with your mentor, which is really interesting. Nice idea. It’s great to meet more people and collaborate, which is a really nice opportunity.
\n\n\n\nBirgit Pauli-Haack: Thank you for bringing that up. Is there a deadline on it?
\n\n\n\nCarolina Nymark: The application deadline is February 7, and you can find the application by going to make.wordpress.org/community and it’ll be one of the pinned articles on the top of that page.
\n\n\n\nBirgit Pauli-Haack: Yeah. And of course we’re going to share the link to it in the show notes of this episode. That is a great new program for getting more contributors. It’s also meant to create contributor leadership as well, and also to have more sustained contribution. We have in many teams the problem that are these flyby contributors and sometimes you need continued contributions to make a team work and we need both. But I think it’s harder for contributors to have an ongoing relationship with a team, especially when they’re not sponsored and their work life or their life.
\n\n\n\nNow, if you have a family, your free time is all but WordPress. If you work as a freelance or in an agency, the workload can be up and down and sometimes you don’t have two months in a row where you can contribute. So this mentorship group is also meant for those who do feel they can do ongoing contributions.
\n\n\n\nAll right. I think we come to the stage where we talk about what’s released and we have to talk about three releases. One is the release squad for WordPress 6.5 has been announced and release lead is again, Matt Mullenweg, release coordinators, Akshaya Rane, Hector Prieto, and Mary Baum. And core tech leads are David Baumwald and Pascal Bircher. And editor tech leads are David Smith and Riad Benguella. But there are in total 27 contributors on the list of release leads.
\n\n\n\nSo there’s also editor triage and design and all that. Carolina, you are also part of the release squad in 6.5. Thank you for raising your hand. And you are named as a default themes lead. That seems to be a new role on the release squad. What does that include for a release that doesn’t have a default theme?
\n\n\n\nCarolina Nymark: It means that you are continuing doing what a bundled theme component maintainer does. It is triaging track tickets, looking at new report issues. But the part that I wanted to focus on that we haven’t really done before is that we need to know what the new features are in the editor. Mostly that can affect our themes.
\n\n\n\nBirgit Pauli-Haack: When you say our themes, you mean previous default themes?
\n\n\n\nCarolina Nymark: I mean, the default themes. Are there new features that should be implemented? Doesn’t have to be implemented, or shouldn’t. We have to make decisions about this and then we have to start looking at the code. Can we solve this? Do we need to fix CSS conflicts? We have to test on multiple, multiple workers expressions to see that we’re not causing problems.
\n\n\n\nBirgit Pauli-Haack: It’s pretty good. I really like that role, but it takes a lot of work because how many default teams are there? 15 or so?
\n\n\n\nCarolina Nymark: I’m hoping that we’re going to focus on the ones that are actually bonded when you install WordPress.
\n\n\n\nBirgit Pauli-Haack: Okay. Yeah.
\n\n\n\nCarolina Nymark: Not the ones that you download. At least not in this round. We haven’t brought this up, but there is a proposal to have a default theme task force. This was proposed in December and you can volunteer for it. We’re still waiting for more information, but the idea is that we do need more contributors to help triage all of the open issues. And triaging issues means that we read these issues and confirm is this actually a bundled theme issue or does it belong to a different component?
\n\n\n\nFor example, if the reported issue is a problem with a block, it probably needs to be moved to the Gutenberg repository and solved there because it affects more than the bundled themes. It affects all themes. So that’s one of the kind of sorting that this group would need to do.
\n\n\n\nBirgit Pauli-Haack: Yeah. I think it’s a brilliant idea, especially because it’s an early warning for changes in the block editor or in block themes that might trickle down to classic themes and changes CSS behavior. There’s one discussion right now about the specificity of elements and block themes and does that affect… If it’s changed, what’s the trade-off? It makes it the work that it would cause to update existing themes, but moving forward lessens the work. So I think with your role in there, you definitely can chime in early warning and also say, “Okay, well this is something we need to have in the developer notes because theme developers will have to take a look at that also for their theme.”
\n\n\n\nSo this was missing. It’s the first release that I won’t be part of since 6.0 on my first release that I was part of on documentation, 6.0 to 6.4, all five releases. I was part of documentation or editor triage and it was really interesting to see how documentation actually surfaces there. That early warning part could have saved some of the hard work that was done retroactively when there was even a new note there or even a new minor version needed to be cut very early after the release.
\n\n\n\nSo to iterate on the release schedule, I think we talked about it earlier, but you can always look it up about beta one is scheduled for February 13th. 25 days left. So if you want to control it or you have some features that need to be moved forward, get on it. There are two more Gutenberg plugins, 17.6 and 17.7 with features that will go into 6.5. Afterwards it’s just bug fixing or maybe a little bit enhancement.
\n\n\n\nAnd then release candidate one and with field guide and dev notes deadline is March 5th, and that’s just before WordCamp Asia. So we all go release 6.5 and then head out to Taipei because WordCamp Asia starts on March 7th. The final release is on March 26th, 2024. It sounds also far away, but it’s really not a whole lot of time anymore to see what’s getting in there. So looking at the hallway hangout where contributors kind walk through all the features might be a good idea to just get up to par with that.
\n\n\n\nBefore we get 6.5, we get a minor release, 6.4.3. Aaron Jorbin is the release lead for that and he announced the schedule for this minor release for January 24th, 17:00 UTC is the release party scheduled, and I’ll share the announcement post in the show notes where he also listed the tickets, the bug fixes that are solved for this final release is also maintenance release, so it’s automatically updated. So watch out next week.
\n\n\n\nAnd that brings us to Gutenberg 17.5, the latest Gutenberg release. There’s not a whole lot of in there, but there’s a lot of… There are big topics in there, but not many specific things. So the continued work on the editor unification, meaning that the site editor and the post editor have the same features, the same panels, the same preferences, and can be reused. And so developers as well as users don’t have to learn two interfaces for almost the same thing.
\n\n\n\nCarolina Nymark: There’s some randomized quality of life changes.
\n\n\n\nBirgit Pauli-Haack: Yeah, absolutely. And then of course that’s related to the history of how Gutenberg progressed, the post editors from the phase one and the site editors from phase two, and now they’re making them being the same. Especially the unified distraction free preferences. I’m really glad that it comes to the site editor now. Also spotlight mode and the show breadcrumbs, broad cramps. Yeah, there’s some German kind of cohort going in there. Sometimes I have that. It wasn’t as prominent when I was living in the United States because I was talking English all day long, but now with the German interacting with Germans, sometimes my English kind of sucks.
\n\n\n\nCarolina Nymark: It happens.
\n\n\n\nBirgit Pauli-Haack: As long as you all still understand me, dear listeners, I’m not stopping with this episode with Gutenberg Changelog. There are some component updates and the font library updates that are going into 6.5 to get the final touches done. They had to refactor some of the rest API interactions for the font library, but that is well on the way for the editor or the block library. We have two changes that I want to point out.
\n\n\n\nOne is that in the post featured image block, there is now an attribute that you can set to use the first image that’s in post as a featured image. I think that’s a great enhancement. That’s a feature that was missing from the classic editor or from some of the themes because I was really missing that. Oh, I have pictures in there. So use one of those and sometimes that would work and then sometimes it wouldn’t work. But now having that as an attribute in the block is really cool. Is there a user interface for that or is it just for the template?
\n\n\n\nCarolina Nymark: As far as I know, it’s just for… Well, developers are advanced users. We have the user interface.
\n\n\n\nBirgit Pauli-Haack: Yeah. Okay. And then the second one is the gallery block. Now, you can just do a random setting, order setting for the pictures in the gallery so you don’t have to fiddle around with the order and moving around and you just… It’s a toggle switch in the site editor, in the blog editor sidebar where you can just switch it on and off and it orders the picture at random. Pretty cool.
\n\n\n\nIt definitely streamlines your production time of things and you don’t have to spend an hour forming an opinion what order you want and then executing on that opinion. If you don’t have an opinion, that’s fine. Is there anything in there that you want to point out, Carolina?
\n\n\n\nCarolina Nymark: In the update or in the block library?
\n\n\n\nBirgit Pauli-Haack: The change log. The change log.
\n\n\n\nCarolina Nymark: There are many small permits. We have some exchanges for the pattern overrides, which is their partially synced pattern with a new name.
\n\n\n\nBirgit Pauli-Haack: Yeah. Naming is so hard.
\n\n\n\nCarolina Nymark: It is. It is so hard.
\n\n\n\nBirgit Pauli-Haack: Yeah.
\n\n\n\nCarolina Nymark: We’ll see. Eventually we’ll see where it actually lands when we have to write a documentation.
\n\n\n\nBirgit Pauli-Haack: Yeah. And then once the documentation is written, it’s kind of set in stone because nobody knows when you rename things. There are so many people out there who still talk about full site editing in new posts in 2024. So not on the WordPress site, but people here write the portals and all that. The pattern overrides have a lot of expectations and I think the 6.5 first iteration will be very limited in features that I think for paragraphs, for heading and for images.
\n\n\n\nCarolina Nymark: It needs to be limited, I guess. Well, we need more time, but also it just makes it easier to test and to receive feedback for it and not as overwhelming hopefully for users to actually learn.
\n\n\n\nBirgit Pauli-Haack: Yeah, good point. Good point. I like it. And of course the data views, there are a lot of people working on the data views and it’s still under experimental flag, but it’s coming a long way. It really has some great attention right now. You can use it on the one store feature is enabled in the experiments. You can use it on the patterns page. On the pages page it’s already by default available for templates. I think template parts are still under the experimental flag, but those things will all come out of experiments hopefully very soon. So we can all test everything.
\n\n\n\nCarolina Nymark: It’s moving very fast. It is still unclear what will actually be in 6.5. But we’ll see.
\n\n\n\nBirgit Pauli-Haack: I think every release in the last so 16 point… This is 17.5. So 17.3, I think, had the first data views or 17.2 even. And every release had over 20 PRs kind of going in into that feature. So it’s really moving fast and it’s beautiful now. I really like it. There’s quite some excitement out there in the community as well for those who have looked at it. And if you have an opinion, dear listeners, send them to changelog@gutenbergtimes.com, changelog@gutenbergtimes.com.
\n\n\n\nSo there are two items in the documentation section. There’s a lot of changes in documentation, but two, I want to point out because it’s for beginners on the block development. There’s a new section in the quick starter guide. If you haven’t seen the quick start guide for block development, I only use it to talk about other things. So the quick start guide for block development walks you through a tutorial on grading a block for copyright, dynamic copyright year on your website and use that block.
\n\n\n\nThere was a developer just last week and the recording is up on YouTube where Nick Diego and Ryan Welcher go through that tutorial and show how this all meant to be. It’s one thing to read a tutorial and try to follow along yourself than to watch somebody else go through a tutorial and then follow along. It’s a much richer experience. And the documentation changes here are all about the local development environment. What are the tools that you can use for local development on your machine?
\n\n\n\nAnd one of them is WP-env, which is the built-in WordPress development based on Dhaka. There are actually, I don’t know if you use them already, efforts to make the WordPress playground a local development. You don’t need local development. You can use the WordPress playground for development and have code editor in there. So I’ve seen some great mockups from that.
\n\n\n\nCarolina Nymark: I have not tried it yet. It’s on my very long to-do list because I’m absolutely curious about it.
\n\n\n\nBirgit Pauli-Haack: Yeah, it’s amazing. But the WP-env script also, you can call it together with a create block scaffolding and you have almost instantaneous a good block development environment set up. There were some changes to block.json as well as theme.json And documentation and that’s pretty much what I wanted to point out. Code quantity is all very technical and all the efforts to write all the end-to-end tests and playwright migrating fast. And to build tools have been updated to the latest things.
\n\n\n\nAll right. Oh, here it was, yes. So that was a change log for 17.5. It was not a whole lot in there for a WebPress user. It’s more like the future of things. It’s really cool, but not for immediate use. But sometimes you have these releases where there’s some foundation work being done.
\n\n\n\nCarolina Nymark: The releases are some frequency, yes. Sometimes there will be these kind of releases but with less new ready features and more work on what’s coming.
\n\n\n\nBirgit Pauli-Haack: Yeah, absolutely. Absolutely.
\n\n\n\nSo speaking of what’s coming there is this active discussion. I mentioned it before. There is an effort on PR that reduce the specificity on the global styles, CNS by, I think it was Isabel, Brison tele machines. She’s working on that quite a bit. And there is a call for testing, especially for classic themes to see how impact that will have on your custom CSS or even on block themes because the high specificity makes you create workarounds on all the different places. And if it’s reduced, you’re losing your targets. So how much work would it take? I’ll share the related ticket in the show notes, but did you take a look at that?
\n\n\n\nCarolina Nymark: I have read it. I have planned, sets time away in my calendar to do some testing and this is where it would really help to know what specifically to test for, like having something to help us get started because it’s a bit wide right now. It’s just test if your sales is still correct. This is also where tool like visual regression testing would have really helped. But in the next couple of days, of course we are going to have a little bit more testing done. We’re going to have some more comments on these issues, tickets and narrow it down a little bit so that we can have tests in the instructions and test results presented there.
\n\n\n\nBirgit Pauli-Haack: Yeah. Aaron Robishaw who’s also working on those, he did some explorations on the current approach to see… I think his summary also helps with figuring out as a theme developer, “Okay, where do I need to look in my theme to test this rate?”
\n\n\n\nCarolina Nymark: That sounds good.
\n\n\n\nBirgit Pauli-Haack: Yeah, I share both of them in the show notes of the show. And it seems that we are at the end of our show. Carolina, you made it.
\n\n\n\nCarolina Nymark: We made it. Thank you.
\n\n\n\nBirgit Pauli-Haack: We made it, yes. It’s an awesome show. You have some great discussions on block development and block themes, and contributions, and a call for contributors. So it’s a full rounded show. Is there anything, Carolina, that you want people to know that you didn’t get to mention before, while you have an audience and think about it, and you could also tell me where people that want to connect with you, where they find you?
\n\n\n\nCarolina Nymark: Well, you can find me on Twitter, @carolinapoena. You can message me there. If you go to fullsiteediting.com, in the footer is also actually a link to a Slack channel that you can join if you like.
\n\n\n\nBirgit Pauli-Haack: Okay.
\n\n\n\nCarolina Nymark: And on the WordPress Slack, my nickname is Poena. Yeah, that’s the easiest way to reach me.
\n\n\n\nBirgit Pauli-Haack: All right.
\n\n\n\nCarolina Nymark: I think that we need to mention everything a little bit about, but to think about when you’re switching your website to a block theme or what we need help with in testing the upcoming release and what we need help with for the bundled themes that we need more contributors and we need more testing.
\n\n\n\nBirgit Pauli-Haack: All right then. Before we end the show, remind you, there’s these events out there February 7th, that phase three media library. February 8th is the intrinsic design hallway hangout. There will be developer hours in February. I don’t have a date yet, but keep up on the meetup extensibility issues. Triage meeting is January 23rd. And then there is a livestream on Twitch about reviewing Gutenberg 17.5. I’m going to watch it and see what Ryan Welcher is digging up from this change log that we might have missed.
\n\n\n\nDear listeners, thank you all for listening again, and if you have any news or questions, or suggestions, send them to changelog@gutenbergtimes.com. That’s changelog@gutenbergtimes.com. Again, thank you, Carolina Nymark for being on the show and sharing all your wisdom here. Thanks for listening, and goodbye for me.
\n\n\n\nCarolina Nymark: Bye.
\n\n\n\nBirgit Pauli-Haack: Bye.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 21 Jan 2024 13:34:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:118:\"Gutenberg Times: Media Experiments, WordPress 6.5, Gutenberg 17.5 and block building tutorials — Weekend Edition 281\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=27026\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://gutenbergtimes.com/media-experiments-wordpress-6-5-gutenberg-17-5-and-block-building-updates-weekend-edition-218/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:23480:\"Howdy,
\n\n\n\nWork on the next major WordPress release, 6.5 is in full swing. Two more Gutenberg plugin releases and Beta 1 will be upon us. You’ll find more information below, including additional resources. It’s the first release since 6.0 that I won’t be on the release squad, by choice. I will, of course, support it anyway I can.
\n\n\n\nMore about block editor, themes, plugins and tutorials, as always, below.
\n\n\n\nWishing everyone in the Northern Hemisphere to stay warm and a wonderful weekend for all of us.
\n\n\n\nYours, 💕
Birgit
PS for WordCamp Attendees:
\n\n\n\n\n\n\n\nIf you’d like to meet with me, feel free to use my Calendly link to my public calendar to schedule a get-together. I’ll be in Taipei, Taiwan a couple of days early in will scout out some meeting locations.
\n\n\n\nMy friend and college Ryan Welcher will also be in Taipei, Taiwan. If you want to meet with him as well, you can use his Calendly link to schedule a meeting
\n\n\n\n\nHector Prieto, co-release coordinator, posted the full release squad for WordPress 6.5: WordPress 6.5 release squad formation – a new role is Default Themes lead, suggested by Carolina Nymark, who will also lead the first time around. In her suggestion, she mentioned that it would be great to make sure default themes bundled with WordPress are all compatible with the improvements and features of the Block editor. The abbreviated release schedule:
\n\n\n\nFrom the Dev Chat Summary by Abha Thakor
“Note update on the Font Library API design proposal, with a particular note for REST API folks to view as per this comment. The navigation overlay has been punted from the 6.5 roadmap by the contributors working on this feature.”
More resources:
\n\n\n\nAnne McCarthy invited contributors to a Hallway Hangout to explore WordPress 6.5 at its current stage and posted a Recap with links and video recording. You learn more about the upcoming Data views, the new Drag and Drop features in the editor, as well as the work behind the Pattern Overrides (former partially synched patterns) and the improved Style revision screens. Demos by Anne McCarthy, Isabel Brison and Saxon Fletcher.
\n\n\n\nIf you want to dive in a little deeper into the various features, here is your reminder: Anne McCarthy also posted Early Opportunities to Test WordPress 6.5 with clear instructions on what exactly to test, and how to set up a test site for this exercise. All. feedback is welcome, post it either on GitHub or as a comment on the post.
\n\n\n\nAaron Jorbin, release lead for 6.4.3 just announced the schedule and content for the next minor WordPress release. 6.4.3: An upcoming maintenance release. Final release is scheduled for next week, January 30, 2024.
\n\n\n\nBen Dwyer managed this week’s Gutenberg plugin release and published What’s new in Gutenberg 17.5? (17 January 2024) . 178 PRs were merged for this release by 45 contributors, two of them first timers. This release is dominated by a lot of foundational work on site editor to allow for feature parity with the post editor and for the Data views, that are still experimental. Dwyer highlighted:
\n\n\n\nuseFirstImageFromPost
attribute. (56573)Gutenberg 17.5 was also part of the Gutenberg Changelog chat with Carolina Nymark. We discussed block themes, migration to block themes, the new role on the release squad and lots more. It was wonderful to finally catch up again and talk about her fantastic work on fullsiteediting.com and on the themes team for all those years. The episode will drop into your favorite podcast app over the weekend.
\n\n\n\n\n\n\n\n🎙️ Latest episode: Gutenberg Changelog #95 – Gutenberg 17.5, Early Testing of WordPress 6.5 and Block Themes with special guest: Carolina Nymark
\n\n\n\nJanuary 23, 2024, at 12:00 UTC. Extensibility Issues Triage meeting We will go over the project board’s columns: Triage, Needs discussion and PR in reviews. It will be a Slack meeting in the #core-editor channel.
\n\n\n\nJanuary 25, 2024, at 15:30 UTC – Developer Live stream: Reviewing Gutenberg 17.5 Ryan Welcher is also doing a review of Gutenberg 17.5 on Twitch. It’s a live stream, so not prepared slide etc.
\n\n\n\nPhase 3 Media Meeting: February 7, 2024, at 12:00 UTC, Anthony Burchell wrote: “kick off a round table discussion about some opportunities and challenges ahead in the development of Phase 3. The Media Component Maintainers hope to find areas of focus where contributors can lean in to align efforts with folks working on Phase 3.”
\n\n\n\nFebruary 8th, 2024 15:00 UTC: There will be a Hallway Hangout to discuss Intrinsic Design and how to use it on real life projects
\n\n\n\nFebruary 13, 2024, at 16:00 UTC Developer Hours: JavaScript for modern WordPress development
\n\n\n\nIn Doo the Woo Product podcast episode: Gutenberg, the Beginning to the Present, Tammie Lister and Jonathan Wold discuss block editor and WordPress. They cover State of the Word, upcoming changes and what it means to Woo and WordPress as a whole. Learn more about the progress on the WordPress way.
\n\n\n\nRobert DeVore posted Introducing BoostBox: The 1st WordPress popup builder for the core editor about his journey to push his newest plugin BoostBox over the finish line. It’s available via the WordPress repo.
\n\n\n\nA user posted in the forum, that it wasn’t clear if he needed to recreate all the menus he used in the classic theme, again to display them on the block theme. The answer is no; however, it’s not as obvious where to find the menu item to make a classic menu available to the block theme navigation block. Here are the instructions and a video. Quick Tip: How to use a classic menu in the navigation block of a block theme
\n\n\n\nAna Segota, of Anariel Design, published a new Woo Theme, Fuel, meant for food related businesses. It entails plenty of patterns and color options to style the site of a food store.
\n\n\n\n\n\n\n\nJohn Hughes found four methods on How to Create a Sticky Header in WordPress and in his post he walks you through all of them. Hughes also explains some consideration and best practices for using Sticky headers in the first place.
\n\n\n\nPascal Birchler, core contributor sponsored by Google, and Core Co-release lead for WordPress 6.5 experimented with media handling in Gutenberg and WordPress. He centralized all his experiments in the plugin Media Experiments that available on GitHub.
\n\n\n\nNathan Wrigley had Birchler on as a guest on the WPTavern Jukebox podcast. #105 – Pascal Birchler on Revolutionizing Image and Video Processing Within WordPress, where they discussed the power of WebAssembly, the future potential for moving desktop activities to the web, and Birchler’s innovative work in image and video processing.
\n\n\n\nThe list of features of the plugin is spectacular, yet all experimental, more proof-of-concept rather than production ready. For some of them, you’ll find short videos on how they work:
\n\n\n\nAfter the revamp of the Theme Handbook to include making block themes, Justin Tadlock posted about the project and what will be next: New Block-Focused Theme Handbook Docs and What’s Coming in 2024.
\n\n\n\nIf you haven’t explored the Theme Handbook lately, the team create five new chapters in 2023:
\n\n\n\nFor 2024, the team is also onboarding new contributors, to do the heavy lifting of creating the Advanced Topics for Themes.
\n\n\n\n\n “Keeping up with Gutenberg – Index 2022”
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2021 on. Updated by yours truly. The index 2020 is here
Nathan Schneider posted a tutorial on Extending the New Product Editor with React on the Woo Developer Blog and covered how to create two blocks that enforce minimum and maximum quantity on text inputs.
\n\n\n\nBrian Coords shared his Thoughts on Version Control for Block Themes and what he thinks could work and make his life as a developer easier.
\n\n\n\nThe recording of the latest Developer Hours is now available. Nick Diego and Ryan Welcher walked attendees through the official Getting Started tutorial of the Block Editor Handbook and explained every step of the journey.
\n\n\n\nMatt Cohen, engineer lead at Woo Marketplace, published how he built a terms list block for WordPress. He shared his research and approach, as well as his code on GitHub. you learn how to add a custom control to select taxonomies, and his lesson’s learned.
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph.
\n\n\n\nFor questions to be answered on the Gutenberg Changelog, send them to changelog@gutenbergtimes.com
\n\n\n\nFeatured Image: Industrial Storage Space CC0 licensed photo by Makarand G. Mane from the WordPress Photo Directory.
\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nWe can’t thank Bluehost enough for renewing their support as a global sponsor for the global WordPress community in 2024! Their support of WordPress community events at our Gold level worldwide goes a really long way. They support WordPress communities all over the world!
\n\n\n\n\n\nBluehost has been a WordPress partner since 2005 and powers over 1 million WordPress sites worldwide. Their objective is to help customers, whether novice or pro, create a thriving online presence at an affordable price. With a team of in-house tech experts available 24/7, Bluehost dedicates time and resources to providing the best support and services in the industry. Join millions of other site owners and see what Bluehost can do for you and your online presence.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 19 Jan 2024 15:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Isotta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"Akismet: Forum Spam: How to Permanently Stop Spam Bot Registrations\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://akismet.com/?p=283701\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:36:\"https://akismet.com/blog/forum-spam/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:24851:\"Creating a forum for your organization can be an excellent way to build a community around your product or service. And the information provided in a forum can help customers resolve issues on their own — reducing customer service costs and improving satisfaction. But if you’re not careful, forum spam can detract from the entire experience for members and reflect poorly on your brand.
\n\n\nFortunately, there are tools you can use to stop forum spam. When you leverage this kind of software, your customers won’t have to sift through pesky fake comments and posts to find what they’re looking for. They won’t be directed off‑site for malicious purposes, and you’ll be able to maintain a more professional environment.
\n\nThis guide will start by discussing forum spam and all its variations. Then, it will outline the negative effects of spam and why certain anti‑spam techniques fail to block it. Finally, it will show you how Akismet’s enterprise anti‑spam services can stop spam registrations on your website.
\n\n\n\n\n\nWhether you run a small business or a global enterprise, creating a forum is an effective way to connect with your customers. They provide people with a space to discuss (and potentially resolve) their doubts and issues. And a forum can even lighten the load on your customer support team.
\n\n\nThe only problem is that forums can become a den for spammers.
\n\nBy definition, web spam is any sort of unwanted message shared with a large number of people online. This can appear in email inboxes, the comments section of a blog post or YouTube video, a contact form, and, of course, a forum.
\n\n\n\n\n\n\nTypically, forum spam is generated by bots with a particular goal in mind. For instance, a forum spammer may want to promote a certain product to the members. This is usually quite obvious, as they clutter the forum with messages spouting the benefits of whatever they’re selling.
\n\n\n\nOther times, spam can be harder to spot. These cases can be even more dangerous, as instances can contain hidden links to malicious sites.
\n\n\nThere are several different types of forum spam, like content spam, profile spam, signature spam, and private messages. We’ll cover these later in the post.
\n\nIf a forum doesn’t have a moderator or anti‑spam software in place, spam can get out of hand quickly. And even if it does have a moderator, sifting through huge volumes of spam can be a poor use of time.
\n\nYou might be wondering why spam happens. Here are some common goals of spammers:
\n\n\nThese are some of the most common motivations for posting forum spam. Unfortunately, spam is always evolving, so it’s important to be wary of any suspicious activity on your forum.
\n\nTo stop spam, you’ll need to understand its various formats. Here are the four most common types of spam:
\n\nContent spam refers to anything that’s off-topic or irrelevant to the page that it appears on. Forums are usually centered around a niche subject, so this type of spam should be easy to spot.
\n\n\n\nContent spam is usually employed to promote a product or service and can contain links to another website.
\n\n\nTo participate in an online forum, members will likely need to create a profile or an account. Forum spammers can use these profiles to spread spam without anyone noticing.
\n\nA spam account can embed hidden links into its profile. The most common example is a link in the username. But spammers might also include a link in the bio section of the profile.
\n\nEach time a forum spammer posts a message or someone views their profile, this link will be visible to members. But unless someone clicks on it, no one would know it’s there.
\n\nThis type of forum spam is commonly used in an attempt to trick search engines or promote a product.
\n\nSignature spam is a type of profile spam. Instead of hiding links in usernames and profiles, spammers include them in their signatures.
\n\n\n\nThat means that they embed a link each time they comment or post. The rest of their comment might be completely legitimate — and thus their work is less likely to be detected. This is another way to manipulate search engines for higher rankings.
\n\n\nAs the name suggests, private message spam is sent to members of a forum. Considering that these messages don’t impact search engine rankings, this type of spam almost always has an intention of direct harm to your forum members.
\n\nWith private messaging, forum spammers can promote products, harvest personal data through malware in links, or set up phishing scams. This can be particularly dangerous because moderators are unable to see or stop this spam. It’s up to forum members to flag it.
\n\nThis section will discuss the consequences of spam on a forum. These apply to both enterprises and small businesses.
\n\n\nOnline forums are intended to create a dedicated space on the internet for a specific community. Forum members can post questions and raise concerns, or simply start a conversation around a certain topic that they find interesting or important.
\n\nIn many cases, online forums can provide additional value to customers in the form of educational content. But if a forum is cluttered with spam, its members will likely have a hard time sifting through its posts. It will be up to them to figure out which comments are genuine and which ones are spam.
\n\nThis will lead to a degraded user experience. It could even prompt members to abandon your forum.
\n\nIf a forum becomes overrun by spam, most members will assume that there aren’t any moderators to manage it. They might also think that the business or enterprise behind the forum hasn’t invested in any security measures to prevent forum spam and protect visitors.
\n\nThese perceptions can damage your reputation. Plus, it might prompt some people to look for other, more credible online communities.
\n\nSearch engine bots are always implementing new ways to spot untrustworthy web pages. This is because Google (and other search sites) want to provide internet users with the best experience possible.
\n\n\nIf your forum is littered with content that spammers are posting to manipulate their rankings, or links to malware and untrustworthy sites, there’s a good chance that search engines will catch on.
\n\n\n\nSince software like Googlebot can’t tell who is attempting to manipulate it, it could end up penalizing your forum, rather than the perpetrators using it to do harm.
\n\n\nThis means forum spammers can hurt your website’s search engine rankings while attempting to boost their own. Your web pages may be removed from search results until you can prove their legitimacy. This will involve removing spam links and asking Google to recrawl your site.
\n\nSome of the more nefarious types of spam include malware and phishing attempts. These can have serious consequences for your business and customers.
\n\n\nThat’s because this type of spam puts sensitive data at risk. Spammers can gain access to personal information like names, email addresses, and phone numbers. As a result, affected individuals will receive spammy messages through email or SMS, or their data may be sold off.
\n\n\nWhen your forum is plagued with spam, you’ll end up wasting resources on eliminating it.
\n\n\n\nFor instance, if you employ someone to moderate and block spam comments as part of their daily work routine, they may be spending too much time on these messages. That means less time to focus on more important tasks, like answering customer queries.
\n\n\n\nSimilarly, any spammer is consuming your website’s server resources. Depending on the level of spam you’re dealing with, this could result in lots of wasted server space.
\n\n\nThe costs associated with hosting for enterprise organizations can get out of hand quickly. Working with efficiency in mind and proactively protecting resources is important. And for small businesses with a modest hosting plan, large volumes of spam could even impact site performance.
\n\nHaving an understanding of the different types of forum spam can help you identify spam more easily. Still, it’s always better to stop spam before it can infiltrate your forum.
\n\nHere are some of the common characteristics of spambot registrations:
\n\nSpambots aren’t very creative. So, one way to spot them is by looking out for generic usernames.
\n\n\nThese include usernames like “lucky_guy” or “shy_gal”. Of course, spambots can also incorporate fake generic names into their handles.
\n\nSome of the most common email domains are gmail.com, yahoo.com, and outlook.com. They are all associated with reputable email providers.
\n\n\n\nA suspicious or unfamiliar email domain could indicate a forum spammer. Spam accounts are more likely to use these email providers as they may not meet the security requirements to create a legitimate address.
\n\n\nIf you suspect that a forum spammer has infiltrated your online community, you can look into the IP address associated with that spam account. This can help you confirm or deny the legitimacy of the account.
\n\nYou’ll have to look at the server logs and find the IP address associated with the spammy comment. Note that you won’t be able to do this with private message spam, as you’ll need access to the comment or post.
\n\n\n\n\n\nThis section will outline some of the most common actions by forum spammers. Hopefully, this will help you identify them more easily.
\n\n\nIf a forum spammer wants to utilize your website’s authority to boost their search engine rankings, they’ll often reply to old and inactive threads.
\n\nThat’s because older forum threads will have received more traffic and better rankings in search results. If your forum has been active for several years, these actions should be easy to spot.
\n\nSince a spammer has no intention of actually contributing to your online community, they tend to leave short replies with a link included.
\n\n\n\nWhile they may offer a brief comment, this is likely something generic that has been programmed into the spambot’s capabilities. For instance, you might get something like “great content!” or “love this!”.
\n\n\nProfile spam is very common on online forums. You’ll often see a spammer place a link and website description in their profile. In this scenario, the spammer is likely trying to promote a product or manipulate search engines.
\n\nIf a member uses a topic title that seems relevant to the forum, but then talks about something different in the thread, this is a major red flag.
\n\n\nEssentially, this type of spam is trying to lure members into clicking on a thread by suggesting that it will contain valuable information for them. Once they’ve clicked on the thread, forum members will likely find promotional or otherwise spammy content.
\n\nAnother clear giveaway is off‑topic comments. Similar to misleading topic titles (but more blatant), off‑topic comments are explicitly pushing the spammer’s agenda without even pretending to contribute to the forum.
\n\nMany forum spammers use a website as their username. This could be a spammy marketing tactic, plain and simple. It could also include a link, which would have bigger implications for search engine optimization.
\n\nThe great thing about the internet is that people have access to forums in almost every country and every language. People often tend to congregate on forums with like‑minded individuals as well as those with similar backgrounds, so while it’s definitely not a guarantee, a new user that posts in a language rarely used by other members of the forum can signal that they’re not there for anything good.
\n\nForum spam can be a serious problem, and common anti‑spam techniques might not always be efficient in spotting it. This section will discuss some of the reasons why these approaches fail.
\n\n\nOne of the most common anti‑spam methods involves CAPTCHAs. This is particularly common for online forms (like contact forms) and user registration forms.
\n\n\n\n\n\n\nA CAPTCHA presents a challenge or puzzle that spambots should be unable to complete. The theory is that it will prevent them from submitting content, but CAPTCHAs have several limitations.
\n\n\nFirst of all, they’re not 100 percent effective, since many bots can bypass CAPTCHAs. Plus, they’re not the most accessible anti‑spam tactic, as they can alienate people who have varying impairments.
\n\n\nIn the past, CAPTCHAs were pretty straightforward. For example, you would have had to interpret some blurry letters and numbers.
\n\n\nBut CAPTCHAs have become more difficult, even for authentic users who are likely to become pretty frustrated after the first or second failed attempt. These real people might even end up abandoning your site altogether.
\n\n\nNewer versions ask users to do things like “find all the images with stoplights.” But they’re just as annoying for humans and still not very effective against robots.
\n\n\n\nAnd even the latest option — reCAPTCHA v3 — seems like an improvement for users, since there’s no visible test required to gain access, but it comes with some serious downsides.
\n\n\n\nFor example, it provides Google with a lot of data that many are concerned violates the privacy of users. It can deter good bots like search engine crawlers. Finally, and perhaps the most annoying, real users can be flagged as spam without any way to prove their legitimacy.
\n\n\nQuestion‑based challenges are another common anti‑spam tactic. Although they aren’t as ubiquitous as CAPTCHAs and reCAPTCHAs, they come with the same limitations.
\n\nThey can create an obstacle for individuals with different abilities. If they become frustrated enough, they could give up on the challenge. As a result, you could end up losing conversions (or, in this context, new forum members).
\n\n\nEmail verification is another popular way to prevent spambots from infiltrating websites. It’s a bit more user-friendly than a CAPTCHA, but still creates an additional step in the registration process.
\n\n\nSince getting conversions is hard enough, this tactic isn’t ideal. You’ll want to avoid any friction and streamline the signup process as much as possible.
\n\nSo how can you eliminate forum spam without deterring real users? This section will introduce you to an efficient anti-spam tool: Akismet.
\n\n\nAkismet is an automated anti-spam tool that uses advanced AI technology to identify spam without any input from users. It works in the background and has an incredible 99.99% accuracy rate. There are no annoying puzzles to solve, no questions to answer, and no spam in your forums.
\n\n\nWhether you run a small business or work at a large company, Akismet is by far the easiest and most effective way to stop forum spam.
\n\n\n\n\n\nWhile it’s known throughout the WordPress community for its considered to be the best anti‑spam plugin that’s easy to install, it also supports other platforms like Joomla! and Drupal. Developers can even build it into any application thanks to Akismet’s flexible API.
\n\n\nWhen you sign up for an Akismet plan, you’ll be protected from comment and form spam, including spambot registrations and comments on forums.
\n\n\nAt the time of writing, Akismet has protected more than 100 million websites and blocked over 500 billion instances of spam.
\n\n\nThe value is immediately evident — it’s proven to boost conversions by an average of 3.6% when replacing CAPTCHA. That’s an instant boost in website performance!
\n\n\nAkismet is software that you can install on your website. If you have a WordPress website, all you have to do is purchase a plan, and then install and activate the plugin through your dashboard.
\n\n\nDepending on your web hosting plan, the free version of the tool may come pre-installed on your website. Non-commercial WordPress sites can use it completely for free.
\n\n\nBusinesses and other professional organizations can quickly find the ideal plan for them and the elimination of spam and improved user experience will immediately make it worthwhile.
\n\nFor major organizations, the good news is that Akismet offers custom enterprise plans. In fact, with over 100 million users, it’s the go‑to choice for businesses like ConvertKit that use Akismet to boost the performance of their platform by protecting their wide network of business customers from spam.
\n\n\n\n\n\n\nOnce Akismet is set up, it uses AI filtering and a robust spam database to identify and block spam. Plus, it operates on the cloud, so these processes won’t impact your website’s performance.
\n\n\nIf you’re using WordPress, Akismet integrates seamlessly with some of the most popular plugins, like Jetpack and Formidable Forms.
\n\nHere are some of the main benefits of using Akismet to stop forum spam:
\n\n\nIn a nutshell, Akismet is powerful software that can stop spam in its tracks. It’s highly effective, easy to configure, and works on multiple platforms. Plus, Akismet stands out from other anti‑spam solutions because it doesn’t add any obstacles for legitimate site visitors.
\n\nA seamless anti‑spam solution can greatly improve the effectiveness of your forums. When it comes to contact forms, Akismet can help increase your conversion rates, too!
\n\nIf you’re currently running a forum or want to start one, you’ll need a strategy to prevent spam. Otherwise, your members could be driven away in annoyance. Plus, if your forum is plagued with spam, it could lead to a drop in your site’s search engine rankings.
\n\nThat’s why your forum needs an enterprise solution like Akismet. This powerful software uses AI filtering, cloud storage, and seamless integrations to block 99.99% of spam without impacting the user experience or your site’s performance.
\n\nAre you ready to stop forum spam? Reach out to the Akismet team today!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 19 Jan 2024 14:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Jen Swisher\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"WordCamp Central: Thanks to Woo for sponsoring community events worldwide\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://central.wordcamp.org/?p=5109963\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"https://central.wordcamp.org/news/2024/01/thanks-to-woo-for-sponsoring-community-events-worldwide/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1012:\"We couldn’t be happier to welcome Woo to the WordPress global community sponsorship program in 2024! This year, they’re sponsoring at the Gold level in all regions, supporting official WordPress community events across the globe.
\n\n\n\n\n\nWoo is the leading open-source ecommerce platform, powering 31.4% of the top million online stores.* Built on WordPress, Woo empowers anyone, anywhere, to sell anything with truly unlimited extensibility, flexibility, and control over how they build and evolve their business.
\n\n\n\n* StoreLeads, StoreLeads.app, January 2024.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 18 Jan 2024 15:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Isotta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:21;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"Do The Woo Community: AI, Accessibility, Security and Privacy in 2024 with Robbie and Robert\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78883\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://dothewoo.io/woo-agencychat-look-at-2024/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:415:\"Hosts Robbie Adair and Robert Jacobi discuss their predictions for 2024, focusing on the acronym ASP: Accessibility, Security, and Privacy
\n>> The post AI, Accessibility, Security and Privacy in 2024 with Robbie and Robert appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 18 Jan 2024 10:39:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"Akismet: Version 5.3.1 of the Akismet WordPress plugin is ready to download\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://akismet.com/?p=283692\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"https://akismet.com/blog/version-5-3-1-of-the-akismet-wordpress-plugin-is-ready-to-download/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1004:\"Version 5.3.1 of the Akismet plugin for WordPress is now available.
\n\nIn this release, we’ve added a quick link to get to your Akismet.com account overview. This enables you to see summary of activity across all sites using your API key, and manage your Akismet subscription.
\n\n\n\n\n\nThere are also a number of bug fixes and improvements and we recommend upgrading if you’re using an earlier version of the plugin.
\n\nTo upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins directory.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 18 Jan 2024 00:36:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Chris Rosser 🏔\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:23;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"WordCamp Central: Automattic sponsors WordPress community events across the globe\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://central.wordcamp.org/?p=5109965\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"https://central.wordcamp.org/news/2024/01/automattic-sponsors-wordpress-community-events-across-the-globe/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2763:\"We’d like to welcome Automattic to the 2024 Global Sponsorship program! By sponsoring at the Gold level across the globe, Automattic helps make local community events better for WordPress enthusiasts and easier to organize for our wonderful group of hardworking volunteers.
\n\n\n\n\n\nAt Automattic, we are passionate about making the web a better place.
\n\n\n\nWe are the people behind WordPress.com, WooCommerce, Jetpack, WordPress VIP, Simplenote, Longreads, WPScan, Akismet, Gravatar, Crowdsignal, Cloudup, Tumblr, Day One, Pocket Casts, and more. We believe in making the web a better place.
\n\n\n\nWe’re a distributed company with 2,007 Automatticians in 97 countries speaking 123 different languages. We’re committed to diversity, equity, and inclusion, and our common goal is to democratize publishing and commerce so that anyone with a story can tell it, and anyone with a product can sell it, regardless of income, gender, politics, language, or where they live in the world.
\n\n\n\nWe believe in Open Source and the vast majority of our work is available under the GPL.
\n\n\n\nWe strive to live by the Automattic Creed.
\n\n\n\nAutomattic is a Most Loved Company and Disability Confident Committed. (Here’s what that might mean for you.) Come work with us.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 17 Jan 2024 15:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Isotta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"WPTavern: #106 – Anil Gupta on the Challenges Posed by Multi Collaboration in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=152488\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:103:\"https://wptavern.com/podcast/106-anil-gupta-on-the-challenges-posed-by-multi-collaboration-in-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:52438:\"Transcript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.
\n\n\n\nJukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, the challenges posed by multi collaboration in WordPress.
\n\n\n\nIf you’d like to subscribe to the podcast, you could do that by searching for WP Tavern in your podcast player of choice. Or by going to WPTavern.com forward slash feed forward slash podcast, and you can use that URL in most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you, and hopefully get you, or your idea featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox, and use the form there.
\n\n\n\nSo on the podcast today, we have Anil Gupta. Anil is the CEO and co-founder of Multidots, Multicollab, and DotStore. His companies serve a wide range of customers, from large publishers and news companies to WordPress users.
\n\n\n\nOf specific interest to this episode of the podcast is Multicollab, which offers a WordPress plugin that allows for Google docs style collaboration, including commenting, suggestions, and real time editing.
\n\n\n\nWhen Google docs was first brought to the market, it was a pretty big deal. Perhaps not the first to offer a real time collaborative interface, it was certainly the first to gain widespread adoption.
\n\n\n\nFast-forward to today, and it’s more or less inconceivable that you’d create documents which were not editable by multiple people at the same time. Most modern online software ships with this built in. The extraordinary became the norm and the expectation.
\n\n\n\nBut what’s about WordPress? As the largest CMS, WordPress still lacks this functionality, but hopefully not for long.
\n\n\n\nPhase three of the Gutenberg project, the phase that we’re in at the moment, aims to make it possible for many users to amend content at the same time. The beguiling simplicity of the Google docs interface makes it seem like this would be a trivial feature to add into WordPress, but this is not the case. Unlike proprietary software, in which the vendor owns and manages the whole stack, WordPress is used by many different people, in many different ways. They might have a shared server, or a range of plugins, and this all complicates the picture.
\n\n\n\nAnil talks about how his team decided to tackle this problem for their own plugin, and he explains some of the hurdles that they’ve experienced along the way. They’ve taken a cautious approach, developing different features one at a time, working through the technical challenges with commenting before moving on to real time editing.
\n\n\n\nAnil paints a picture of a bright future for WordPress, once this new feature set is completed. But it’s also interesting to see how many challenges the developers will need to overcome before it can be shipped in a future WordPress update.
\n\n\n\nIf you’re interested in finding out about the future of editing content in WordPress, this episode is for you.
\n\n\n\nIf you want to find out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast.
\n\n\n\nAnd so without further delay, I bring you Anil Gupta.
\n\n\n\nI am joined on the podcast today by Anil Gupta. Hello Anil.
\n\n\n\n[00:03:56] Anil Gupta: Hey Nathan, how are you?
\n\n\n\n[00:03:58] Nathan Wrigley: Yeah, great. It is an absolute pleasure to have you on the podcast. Anil and I have spoken on various occasions before, but we’ve never had a one-to-one conversation, certainly not about this subject. But we’re going to be talking today about phase three of the Gutenberg project, and in particular, about the ability to collaborate on documents inside of WordPress. How that might come about. What some of the technical barriers might be.
\n\n\n\nNow in order for Anil to be a credible person on this podcast, it’s probably a good idea to give him the opportunity to introduce himself, and let him talk briefly about the projects that he’s working on, or worked on which overlap what we’re going to talk about.
\n\n\n\nSo Anil, this is just an opportunity really to give your bio, so that our audience know that you know what you’re talking about. So over to you.
\n\n\n\n[00:04:42] Anil Gupta: Absolutely. So I’m a CEO and co-founder of Multidots, Multicollab and Dotstore. So these three brands serve very different group of customers. Multidots is more like our WordPress agency side of the business, where we help large publishers, news and media companies for their WordPress migration. So whatever CMS they’re using, we help them to migrate to WordPress.
\n\n\n\nOur second brand Multicollab, which is a WordPress plugin, a Google Doc style collaboration, that doesn’t exist at this moment in WordPress. But with this plugin, you can use commenting, suggestions and real time editing. And that’s one of the topics that we are going to talk about today.
\n\n\n\nAnd the third brand is called Dotstore, which serves small e-commerce business owners. So if you have a WooCommerce store, we provide bunch of different WooCommerce plugins that helps you to get more sales and better performance, and all those good stuff.
\n\n\n\nApart from these three brands, I also have a podcast called Peaceful Growth, where we talk about some of the strategies on how to grow in life and business, in a more peaceful and balanced way.
\n\n\n\n[00:05:43] Nathan Wrigley: Well, thank you so much. That’s great. So now we know all about you, well, not all about you, but some things about you. Let’s get into the subject at hand, which is going to be multi collaboration inside of WordPress. And I think really, to begin with, let’s imagine in the conversation that we’re going to have, that we are just creating posts and pages. Let’s leave it at that for now, because that will mean that the conversation is easier to understand. And I guess I’m just going to hand it over to you to ask why we need this kind of feature inside of WordPress.
\n\n\n\nAnd just before you begin answering that, I’ll say, if you’ve never used Google Docs or Office 365, then it may be that you don’t even know what we’re talking about. So this is the ability for a variety of people to log into something at the same time, the same document, and be editing it synchronously. So if you were to edit something, I would see your edits the moment that you made them, and in that way we can collaborate.
\n\n\n\nIt is still a mystery to me how this actually happens on the backend, but it certainly isn’t a part of WordPress. At the moment if somebody’s editing something, you are locked out, if it’s not you. And you have to wait until they’re finished, and that might even mean a phone call or an email to tell them, are you finished yet? And this all seems a little bit Victorian, you might say. It’s really from a different era, now that everybody’s got collaborative editing. But, why do we need it in WordPress? What’s wrong with what we’ve got right now?
\n\n\n\n[00:07:04] Anil Gupta: Good question. I would say there are multiple reasons, as well as benefits, of collaboration. But let’s start with the reasons. Traditionally if we go back, when WordPress was launched 18, 20 years ago, the sole purpose of the WordPress was to provide a platform where content creators, publishers, or bloggers, they can create the content easily and quickly, right? And it solved the purpose.
\n\n\n\nBut, in the last 10 years we have observed that anything that we do digitally now, it’s not a single or solo creation. You collaborate, we collaborate with others in regards to creating and producing stuff. Now, if you look at the content publishing, content creation applications, I think Google Docs or Microsoft Word, or any application for that sake, you know, if you look, they kind of like already saw this need, as the internet bandwidth and infrastructure got better. The need to collaborate together and create content together, actually increased, right?
\n\n\n\nSo 10 years ago, when Google Doc and all other content creation app, they already kind of started working on adding the collaboration as a part of their content creation platform. And in last five years, all the modern content creation platform, whether it’s Canva or Notion, they kind of all also have started introducing the collaboration.
\n\n\n\nAnd unfortunately, WordPress doesn’t have collaboration. And why we need a collaboration, you know, the one reason I see is like, now we are not creating the content alone. You know, like even if you are a blogger, you have at least someone you know, that you would like to share your piece of content before you publish it. And then they will share some of the ideas like, okay, you know we should add some graphics here. And just that collaborative communication.
\n\n\n\nAnd now, yes, there are other apps that we use, maybe Slack, Zoom, Loom. Like a lot of different other communication apps that we might be using, in order to achieve this feature. But because all other content creation apps has all these features inbuilt, now it has become an expectation for anyone who is either using WordPress or switching to WordPress, that I would have the same collaborative tools that I was using in my previous content creation apps.
\n\n\n\nLast thing I would say is since pandemic, you know, that like earlier a lot of people were kind of like working from the same office, so they will be more collaborating over the floor, and just like, you know, or the tea and coffee conversation. Now, as we all are virtual, working from remote places and all that. So then it’s not real time, where like, you know, two people can be available. The time zone differences, and a lot of things actually creates that space, where the need for async communication has also been increased. And that is where also, if we have all the collaboration features in the WordPress, that will be helpful.
\n\n\n\n[00:09:54] Nathan Wrigley: Yeah, it’s interesting because I am of a certain age, and I started using WordPress at a time when, well, not necessarily WordPress, but I started using CMSs at a time where there was absolutely no expectation that anything was collaborative. And so I’m kind of okay with it. It’s not perfect, I would love for collaboration to be in there, but I’m used to it, and this is just how WordPress works. I understand that if somebody’s editing something, I have to wait a little bit.
\n\n\n\nBut I’m thinking in particular about my children, and the fact that they’ve been brought up in an era where this is the bare minimum of what a document workflow would be like. You begin creating it, you put a title in, and then maybe even the next step, rather than writing the content, is to click the share icon, wherever that may be, and to get your fellow collaborators in.
\n\n\n\nSo I know, for example, that schools throughout the UK are using all the different suites that you mentioned, to enable them to hand homework in. And their staff can edit things, and modify things, and correct their work and all of that. And it’s just the bare essentials. And so somebody like me, it’s fine. I’m used to it. But the next generation, the people that are growing up, the people who are, let’s say, I don’t know, 20 or below, there’s no way that it’s acceptable to not have collaborative editing. It’s just too strange, alien. And if that’s the case, it will probably not be used.
\n\n\n\nYou know, you log into WordPress for the first time, see it cannot do that, and then think, well, I’ll go to somewhere that can. And as we know, WordPress is in a competitive landscape. We’ve got the SaaS apps out there, the Wixs and the Squarespaces, and I don’t actually know if they can do these features.
\n\n\n\n[00:11:36] Anil Gupta: I think Wix does, yeah.
\n\n\n\n[00:11:37] Nathan Wrigley: Right, okay. So we think that some of them do, and the fact that they’ve got their own architecture, you know, they own all of the infrastructure, and they can put the resources into place for that. It’s probably more straightforward to them to do that. So that leads us to the next thing really, which is, when we’re talking about this, are you able to just flesh out the landscape a little bit?
\n\n\n\nDo you have any insight into what specifically is in the proposal for sharing within WordPress? Because Google Docs, you share a doc. Google spreadsheets, you share a spreadsheet, and it’s fairly constrained. We’d be sharing something, which can be filled up with a myriad of different things, little blocks. You know, it might be a paragraph block, or a YouTube block, or a image block, or goodness knows what array of blocks you may put in. Do you have some insight into exactly what’s inside the spec for Gutenberg phase three, this collaborative era?
\n\n\n\n[00:12:30] Anil Gupta: Yeah. So Matías, lead architecture of Gutenberg, he kind of shared a full roadmap of what we can expect in phase three, which is a collaboration phase of Gutenberg. It has workflows. So the one thing is, as soon as you have this, all the collaboration features, you know, we need to also control the workflow. Like who will approve, who will publish, because multiple people are on the document. You know, where we want to control, or design a workflow in a way so that, if somebody’s still drafting, someone else doesn’t just publish it accidentally, right? So there are like a lot of, I would say, some workflows.
\n\n\n\nAnd then second I would say, which is their async communication. So async is where multiple people can update, contribute to a piece of content, without need of being online. All the changes are synced. And then, it also has some inline commenting. So we can provide some, select any piece of content, a block, a text, table or image, and leave some comments that like, hey, I don’t like this image. Can we change that? Or, what do you think? Like, ask someone else’s opinion.
\n\n\n\nAnd then, specifically talking about the phase three, I think they also have the whole admin panel. So I think they’re working on the admin panel. I’m not sure if directly related to collaboration, but as a part of the phase three, they are working on revamping the admin interface.
\n\n\n\nIf we look at the focus only on the collaboration, I would say async communication, inline commenting, and some level of workflows. You know, those are the three big things that I see will be there in phase three.
\n\n\n\n[00:14:00] Nathan Wrigley: Yeah, there’s an awful lot packaged into that, isn’t there? Just as you were speaking there, a whole myriad of things were coming into my head. And I should probably rewind and say, if this is achieved, it will be in a vanilla version of WordPress. I know that you have a solution where you can add a plugin, and we’ll come to that later. You can talk about some of the hurdles that you’ve had to overcome.
\n\n\n\nBut in a vanilla version of WordPress, everybody will have this functionality, should it be achieved. And at the moment, in a vanilla version of WordPress, the publishing flow is really, pretty straightforward. You log in, and you basically click publish. But you’ve just introduced a whole raft of different things.
\n\n\n\nSo workflows, let’s take that. You know, if you’ve got seven people, eight people, a hundred, who knows. Any number of people who are editing in there, there may be a myriad of different permissions. This person is able to do this, and this person is able to do that. But finally, only these three people can publish things.
\n\n\n\nSo we need to come up with a visual way of surfacing that inside the UI so that, I don’t know, if six people have been in, and they’ve edited this, is everything that they’ve done okay? Can we just have a quick scan through it? None of that exists, really, at the moment. Third party solutions can bring that to bear, but none of that really exists.
\n\n\n\nThe whole async thing, well, that’s removed entirely at the moment, because you just click either update or, you know, you click publish, and whatever you’ve got on the page or the post is what is saved. And it’s as simple as that. Where, you’re saying that maybe if somebody, I don’t know, it goes offline temporarily. We have to have some way to keep their content, so that when they come back online, it somehow gets synced.
\n\n\n\nAnd anybody that’s been involved in building or developing realises, you know, if things get outta sync pretty quickly, it’s a hot mess. And trying to untangle, well, when did that happen? Who put that in, and when did they do it? That’s going to be interesting.
\n\n\n\nAnd then yes, of course, the whole inline commenting thing. You forget, don’t you? If you don’t use the comments in a, let’s say a Google Doc again, you forget that there’s that whole interface, which doesn’t come to bear unless you use it, which enables you to give commentary on things. To say, I think you should modify this, this is fine. And you can tick things off, and it’s almost like a little task management system.
\n\n\n\nAnd then it sends out a slew of emails to say, oh, somebody’s edited this, that, and the other thing. And, you know, it makes decisions about how many emails to send out based upon the rapidity of the changes going on. So there really, really is a lot in there that needs to be, first of all, figured out, and then made visible to us in a way which is intuitive, and that the next generation can understand without having to think too hard. That’s a lot, isn’t it?
\n\n\n\n[00:16:42] Anil Gupta: It is, yeah. And I think, all these little things, if we keep it into account, like email notification that you mentioned, and if somebody’s already editing a document, there are some changes which are not approved, you know, whether we should be able to publish it or not. There are a lot of little things that we need to think about when we are creating this solution.
\n\n\n\nBut most importantly, people who used to use WordPress, you know, the way as we talked about, you know, you go on a post and start drafting the content, and select some blocks here and there, and then you go ahead and publish it. So now when multiple people are collaborating, yeah, you need to pay attention to all those different things.
\n\n\n\nPermissions that you mentioned, yeah, I think that’s something that, even in our plugin, we are kind of getting a lot. That the default WordPress roles, we kind of think a little bit more about on that too, in regards to like, hey, I don’t want this person to approve any changes, you know. It should be this person. Though that person can edit anything, but they will not be able to accept any changes, or close the comments.
\n\n\n\nSo those are like a lot of little things that need to be there. And user experience, I think will be a very big thing that we need to pay attention to as well, so that we don’t overwhelm the people who love WordPress, simplicity of the WordPress, and when they see all this stuff, is like, why? What’s going on?
\n\n\n\n[00:17:55] Nathan Wrigley: I do wonder on what level the granularity of permissions works. So, is it all done by the role-based system? So, you know, if you have a certain role, you can go in and edit any post or any page. Or, would it be nice to have it on a more granular level? So, okay, although this person has this particular role, which would preclude them from editing this, I want to allow them to edit this one special thing, because it’s right in their wheelhouse. So, okay, even though they’ve got this role, I want them to adopt a different role, just for this one post.
\n\n\n\nAnd then maybe even delving deeper inside the post or the page itself. What about the ability to just edit certain blocks? So paragraph blocks, yes, go for it. But the YouTube block, no, no, no, that’s not for you to be editing. Or the images, no, you can’t do that. You know what I mean? You can get really granular. And I guess it’s a question of how granular we want that to be, and how do you surface that in a way which is easy to understand?
\n\n\n\nAnd then you mentioned also, the visual cues that you’re getting inside of these third party solutions, like Google Docs. You can really see what somebody is doing. So you get this little icon, which is within the document, it kind of stays out the way a little bit. You know, it’s a very thin, little couple of pixels wide icon with a color. But you can see, okay, that’s where somebody’s cursor is, and if they highlight a portion of text, because they want to delete it or something, you can see that that’s highlighted.
\n\n\n\nIn WordPress that might span several blocks. Whereas in a Google Doc it’s just, it’s all one thing so it doesn’t really matter. But it may be that it highlights, you know, you highlight two paragraph blocks and a heading block, then you’re going to delete those. How does that all get done? How does it get saved? How can you revert changes that are made? Boy, there really is a lot going on in here.
\n\n\n\n[00:19:34] Anil Gupta: It’s a massive technical problem that we need to solve, in order to provide this feature, as well as offer that in a way so that it still is helpful. You know, to help them to create and published content faster, not slowing them down.
\n\n\n\n[00:19:47] Nathan Wrigley: The thing about this is, you can’t really release something that isn’t working perfectly, in the scenario that it’s been created for. I don’t know, we tackle, user permissions first. That has to be perfect before it’s released. It can’t be kind of, okay, just test this out a little bit and see how it goes.
\n\n\n\nIt has to be bulletproof, the moment it ships into WordPress Core. And I think that some of the things that came into Gutenberg, and went out of Gutenberg, and got changed in Gutenberg, that was more or less okay, because it didn’t interrupt the publishing workflow. It just, maybe things surfaced on the front end slightly differently. Or there was a block that was suddenly now available, which wasn’t available there before. And all of that was okay. But if we’ve suddenly got things which mean, well, no I can’t publish anymore, that’s not working for me. Oh, okay, that’s not so good.
\n\n\n\nSo in the background, what are you thinking ought to be in view here? You know, are you thinking that it should just be core blocks at the beginning, the blocks which WordPress ships with? Should they be the things that are tackled? Should it be attached to just posts and pages and custom post types, leave all of that. Templates, leave all of that. Patterns, leave all of that. Do you have any intuition as to how deep it should go at the beginning, to make it even feasible to get off the ground?
\n\n\n\n[00:21:00] Anil Gupta: Yeah, so I think that’s a really good question. The reason is, as we talked about, like collaboration is a massive problem. And you can’t try to change everything in one go, you know. So you need to take a different part of the collaboration, and slowly build it in a way so that, yeah, you don’t basically put the whole house down, right?
\n\n\n\nI’m not sure what’s the WordPress Core’s approach is, but when we started working on Multicollab, our approach was, let’s focus on the one feature at that time. So what we did is, we first launched only inline commenting, so no real time editing, so we don’t have to worry about the permissions and all that. No real time editing, just inline commenting.
\n\n\n\nSo in any piece of content, you can select it, whether it’s a blog, whether it’s media, whether it’s a text. You select it, and it’ll give you little comment box, where you can add a comment like, hey, I need some feedback on this, or changes here. And you can also mention anyone who is a WordPress user. So you type in at, then you can select a user, and they will be notified, and they can see and come back to the WordPress post. And they will see like, oh, somebody wants my feedback and opinion on that, and they can reply there.
\n\n\n\nSo that was the first thing we launched. And we perfected that inline commenting almost for like a two years. So we focused on that, to make sure that works. And what you mentioned, one of the big challenge with the WordPress is, everyone has themes, plugins, and blocks, right? So, what sort of blocks are they using in Gutenberg setup, or what sort of plugins are they using?
\n\n\n\nLike Yoast SEO also manipulates the page editing interface and workflow. So that’s why we decided like, alright, we’ll just start with the inline commenting. We slowly increased it. We still have a compatibility metrics where we continue to tell them like, hey, at this moment, this 20, 25, or 30, or 60, however many blocks are like, this is what it supports.
\n\n\n\nAnd then we slowly started focusing on more popular plugins, and their blocks. So then, slowly, we are increasing the compatibility to more blocks. But that’s something that it’s very hard to do it in a day one.
\n\n\n\n[00:22:59] Nathan Wrigley: Do you mind if I just interrupt there? So, that’s really interesting. So, did you have to take each of the Core blocks one at a time, and provide some engineering in the background that made it so that that block was available to be editable in a Multicollab setup? So you had to do the paragraph block, and then the heading block and then, okay, aspects of the group block, which might break something else, we had to deal with that.
\n\n\n\nSo you had to do that first. And then, because all the third party vendors who’ve got the blocks and the block suites and, you know, there’s a lot of those now. You’re having to tackle those because they don’t necessarily work. So immediately my head is this multiplying problem of, how do we reign that back in? How do we get it so that everything is engineered, so that it will be collaborative? So let me just ask that question again. Did you have to do the blocks one at a time, is basically what I’m asking?
\n\n\n\n[00:23:51] Anil Gupta: So the approach that we took, first, we actually, instead of blocks, we were focusing on the type of content. So whether it’s a text, whether it’s media, you know, or whether it’s a dynamic content. Dynamic content is, you know, where you are not typing it in, but it’s just pulling in from, let’s say, from the database, and pulling in like featured post, right? Or let’s say testimonials. So you don’t type in and it’s already coming in from somewhere else like, you know, and then you just curating that.
\n\n\n\nSo we kind of started that like, okay, how should we actually treat a text? And it doesn’t matter whether it’s a custom block, native block, or someone else’s block. As long as there is a text in that, how we should treat that. If there is a media, how we should treat that. We kind of started that. And that was our phase one. So it doesn’t matter what block you have, as long as you have text media and like couple of things, it will work.
\n\n\n\nLater on, once we achieved that, the second phase was how we make sure that we don’t have to edit anything in the code, but still our inline commenting works for whatever the blocks are. Our developer observed that, if blocks are custom blocks, are designed and developed based on following the Gutenberg’s guideline then our plugin was working. But if they don’t follow the Gutenberg guideline, if you just kind of, you know, do on your own thing, that’s where our inline commenting, and some of the things that we were doing was not functioning.
\n\n\n\nSo now in our phase three. So right now we have, as long as your Gutenberg blocks is following, custom blocks, they’re following Gutenberg guideline, doesn’t matter what kind of blocks you have, it will work. And we also did an approach where, if for some reason your block is very complex, then instead of the content inside the block, you can highlight the entire block.
\n\n\n\nSo that’s where we started with like, okay, we can’t actually do much about what is in the block, but you can still give a comment on entire block. It’s working, like most of the blocks where we doesn’t support, you can still select the entire block, and leave a comment on the block. Like, hey, there’s something needs to look in there. But they will not be able to select a particular text, or image inside the block and highlight that.
\n\n\n\nIn our phase three, that is where we are working on. Doesn’t matter what blocks you have, but how we can manipulate the HTML DOM model. So it’s called Document Object Model, right? So the entire page is basically a DOM structure. So now we are working on how we can use the DOM JavaScript and HTML manipulation, so that you don’t need to worry about any block compatibility, it will automatically work with all the blocks. That’s our phase three.
\n\n\n\n[00:26:20] Nathan Wrigley: It does sound like there is going to be a lot of work for the Core WordPress team, to tackle this from some of the experiences that you’ve just highlighted. It is very much an iterative approach. And I guess time will tell how they decide to tackle that.
\n\n\n\nDo you have any intuition on the, backend I guess is the wrong word. But there are some people who are able to afford really complicated server setups and, you know, they’ve got powerful hosting and all of that. And you kind of get the impression that a lot of this is going to be calling back and forth to the server, constantly. Because if you imagine that there’s seven people editing a document at once, that’s seven bits of information that needs to be flying, more or less in real time, the entire time.
\n\n\n\nWhilst that might be possible to have, if you’ve got an expensive hosting set up, which is configured for this. Do you have any intuitions that if you’re on more affordable hosting, like a shared host and you’ve just got a basic plan, do you see this becoming a problem, because of the amount of data that’s going to be flying back and forth, and the power of that computer, acting as a server? What do you think?
\n\n\n\n[00:27:21] Anil Gupta: So when it comes to collaboration, and as we talked about, inline commenting, suggestions, like any edits that you make becomes suggestion, and then the real time editing. So I feel like these three are the big pillars of collaboration. Now when we launched Multicollab, you know, we launched with inline commenting, and then we launched suggestion mode, and now recently we launched the real time editing. The third piece of the collaboration.
\n\n\n\nFirst two piece, inline commenting and suggestion mode. So that’s something that we tested, and we found that it doesn’t require any fancy server configuration. Whatever server or hosting that you’re using right now, that will be sufficient. Because in that we are not using any peer to peer connection, because we haven’t introduced the real time editing yet. As long as you’re using those two features for the collaboration, you’ll be good with pretty much whatever server you have right now.
\n\n\n\nBut the moment you introduce real time editing, that is where the server and the whole performance thing actually becomes very critical. And that’s where the challenge with the WordPress is, that all other content creation apps, and the platform, they are cloud. They’re hosted in cloud, so they have a control on the computing power, and the cloud infrastructure. They can scale the cloud infrastructure because everyone sign in and access the same cloud. One other way, they don’t go and take a piece of source code and install and use it on their own server, right?
\n\n\n\nSo for that, especially this real time editing, where multiple users simultaneously can edit, and all those things that we talked about. That you highlight the cursor where other users are in the post, and if they make any changes, the changes also sync with the other people who are editing, or working on right now.
\n\n\n\nThat is where a server comes into the picture, and our team actually put together a server requirement. Like, what’s the minimum level of server configuration that we need in order for real time editing to work? And that is actually a challenge that we are still working on, and finding a way to see that, what are those major hosting companies, like managed hosting, the big hosting companies. And if their current server infrastructure meets the realtime editing or not.
\n\n\n\nAnd that’s why we launched the realtime editing, at this moment. But it’s still on a beta and it’s by default off. One way we are handling this problem, is we are giving them an option like, hey, if you want to use the realtime editing, it requires certain level of server performance and power. If you have it, then here is the instruction that you can follow, and then you can use the real time editing. If you don’t have it, then you can use our server. So we have created our own server, you know, a massive server where all these async communication happens. The data is encrypted and all of that, but yes, we are giving the choice that, hey, if your server doesn’t support it, then you can use our server. So it’s kind of like cloud, so we have created our own little cloud, which they can use for this async communication.
\n\n\n\n[00:30:19] Nathan Wrigley: So, is that a fairly seamless experience? So firstly, that answer is fascinating. So there is a roadblock, there is a server configuration, at least in your experience, which renders the whole enterprise of synchronous editing painful, impossible, perhaps. And if you are prepared to read the documentation, and get yourself onto a server which you have determined is suitable, then it’ll work. Otherwise, here’s a button for you to press.
\n\n\n\nIs it as straightforward as that? You just sort of click a button and you are taking over that heavy lifting on the server. But it’s purely just for those sync transactions. It’s not for anything else. It’s not for keeping the content of the post, it’s just the bits and pieces that are firing to do the synchronous work, right?
\n\n\n\n[00:31:00] Anil Gupta: That’s very true, yeah. So the way we have done is, right now, if you download multi collab, it’s default, set it to our server, because we want to have them try it and test it. And then they can change it like, no, I don’t want to use your server, I want to, let’s say, configure my own server. Then you just turn that feature off, and you can take over.
\n\n\n\nBut if you want to use our server, you don’t have to do anything. It’s just built in, and it’s already all the server variables, and everything we have already put into the plugin. So when you go, you just turn on the real time editing, and you can start using the real time editing without making any changes in your server.
\n\n\n\n[00:31:35] Nathan Wrigley: It’s kind of an interesting idea because, on the one hand, it creates a marketplace for people such as yourself to offer that service. You know, if you want to have synchronous editing for a hundred people, and for it to be absolutely bulletproof, here’s a plugin which connects to a service, which will give you the horsepower in order to do that.
\n\n\n\nBut at the same time, the way that it’s been described, phase three feels like the enterprise is to get this working for everybody, out of the box. And from what you are saying, obviously, you know, maybe technology will improve, and browser capabilities will improve, and all sorts of things will improve. Maybe this will be possible.
\n\n\n\nBut it does feel like the offering is, this is going to be available to everybody. And it would be strange for a Core feature like that to have some kind of paywall attached to it. Now, I know that we’ve got examples throughout the ecosystem of obviously extra things that you can add in. But if it’s going to be available in Core, it seems odd to then be saying, well actually, your version of Core on that server isn’t going to cut it. I’m sorry, you’re going to have to part with some money.
\n\n\n\nThat feels almost like straying away from what the promise of it is. Do you understand what I’m trying to say? It feels odd to offer something in Core, which then you have to pay for because your server doesn’t live up to it. But then again, that’s just the way it might have to be, I suppose.
\n\n\n\n[00:32:57] Anil Gupta: Yeah. I think that’s where I’m also curious to see how WordPress Core is going to address this problem. Because, based on our research, for last one and a half year we have been working on async and real time editing. We tried WebSocket, WebRTC, pretty much like bunch of different, all of the protocols, we tested it out.
\n\n\n\nAnd one thing that we are seeing repeatedly is that, yeah, the server plays a very, very big role, hosting, specifically plays a big role. And the WebSocket needs to be enabled, and also depending on how many requests, and all of that. So there are like a lot of things that needs to be happen, before even you can turn on and use the real time editing.
\n\n\n\nAnd if WordPress Core is targeting that it will work seamlessly out of the box as you install the plugin. And especially like, you know, if you don’t have all this WebRTC, WebSocket, or whatever the server infrastructure is required. It’s a big question for me, how they’re going to tackle that problem, because at this moment we don’t have a solution.
\n\n\n\nAnd that’s why we created this. Like we bought this massive server computing power so that it can support that. The people who are using our plugin, they’re paying for that services, and they’re aware about it. But WordPress Core, I think the goal is to kind of like have that for free, so that you can use and install it. And I’m not sure how they’re going to solve this problem.
\n\n\n\n[00:34:13] Nathan Wrigley: Yeah and, what does graceful failure look like in that scenario? So if a modest server can cope with one or two people, what happens when you reach the limit of that? So you’ve added in another five people, and suddenly everything’s under strain, it’s no longer working. How do you inform, or how do you encourage the user to do things differently?
\n\n\n\nBecause the last thing you want to do is lock people out of the editor, or something goes wrong in the editor, and it all becomes a problem, I can no longer publish things. Three of us are locked out, and now we can no longer get back in, or we couldn’t collaborate in the way that we thought we could. It was working better yesterday than it’s working today. Those kind of things.
\n\n\n\nAnd that seems an almost insurmountable technical challenge to at the moment anyway. We’re recording this at the end of 2023. It seems like an almost insurmountable challenge to be able to do that and provide it for everybody out of the box, even on the most straightforward, modest hosting package. So, yeah, I guess only time will tell.
\n\n\n\nAre there any other things that you’ve had to tackle, trying to get this done, that you would like to share? Is there any technical challenges that you’ve faced, or quirky experiences that you’ve had and things that you didn’t anticipate on the road that you now look back and think, oh, oh boy, I wish we’d thought of that in advance.
\n\n\n\n[00:35:32] Anil Gupta: Yeah, I think the big piece, what I see is the inline commenting, suggestion, and real time editing like beside this server configuration for the real time editing. I think one is, it’s whole new learning curve. You know, so let’s say when you’re using the WordPress and now when you introduce all these features, there is a learning curve for the content creators.
\n\n\n\nIt’s not a technical challenge, but I think it’s more like adaptation challenge. And one thing that I think we did good and it was a decision, like a very deliberate decision that we want to keep the interface as close to Google Doc. Because Google Doc, I believe, is something that has already set a bar, you know. So when people are very familiar with like how to use the share button, how to invite someone, and leave the inline commenting. And if you kind of like try to introduce completely new interface for the collaboration, then that will also be a big learning curve.
\n\n\n\nSo that’s kind of like feedback that we got initially, when we try to be a little bit more innovative, like, let’s try to, you know, provide the best collaboration interface. It didn’t go well. We were like no, we want Google Doc. We want Google Doc style and that kind of like become our roadmap.. So if you are using MultiCollab right now, using the share button, the sidebar activities, inline commenting, suggestion mode, pretty much like all those features works very similar to how you use the Google Doc.
\n\n\n\nSo you will not see that big difference when you come to WordPress, that you will feel like it’s Google doc style interface. And challenge for us was to build that on the top of Gutenberg. I think that was a big, both technical, as well as a UI and user experience challenge.
\n\n\n\n[00:37:13] Nathan Wrigley: Given that this is coming down the road and, let’s imagine a future where everything works and the team that are behind this managed to pull everything off, and it’s absolutely perfectly working and everything’s fine. How did you decide that you wanted to get into this business?
\n\n\n\nBecause before we hit record, I asked you that question. I said, did you decide to have this business knowing that it was coming into Core? And if that’s the case, why did you do that? Because it seems almost like you’re setting yourself up to have a business which is going to be replaced by something that’s free.
\n\n\n\nBut you’ve got intuitions around that. I guess it’s around what you can package, which may exceed what the endeavor of Core is. We’ve been assuming that it would try to do everything all at once for everybody, and of course that may not be the case. It may be a very, a slim implementation. So just talk us through that. How anxious are you about phase three eating your company’s lunch?
\n\n\n\n[00:38:11] Anil Gupta: So when we started working on MultiCollab, I already was aware the phase three was already announced. They already mentioned that we are going to focus on collaboration. So it wasn’t a surprise in the beginning. The way I saw that as an opportunity, I feel like even where we know that when WordPress Core built or design anything, they try to focus on the 48% of the web. You know, it’s like a lot of small, medium businesses, bloggers. So basically they have to kind of like put it to together, something that’s targeting for a very wide audience.
\n\n\n\nOn the other side, we focus, a lot of our features, like real time editing, inline commenting, these are all free, so you don’t have to pay for using those features. There are some pro level features while custom roles and permissions is concerned, Slack integration. So some of our publishers who use collaboration, they also like integrate that with their Slack and some enterprise tools they use.
\n\n\n\nSo that’s where we see an opportunity that we can provide the tailored, custom solutions, to this 20, 30% of the pro users who wants things a little bit differently and more customizations.
\n\n\n\nAlso by design, you know, the WordPress Core is going to be slow because, you know, everything they have to build, they have to do. It’s a massive force. And on the other side, like we have only one thing, this is the only project that we have. We don’t have like bunch of other phases that we have to worry about. So, that’s something that we, in last two years, we had made a new release every month. You know, so every month we have a new release, fix a bunch of different things, improve different things.
\n\n\n\nSo I think that turn around is something that we were able to do much faster than probably WordPress Core can do. And the support is something that I feel like that is the only focus that we have. And I think we have seen that again and again in the WordPress and all other economy where, we have so many page builders, right?
\n\n\n\nLike still they’re thriving, despite Gutenberg is free. It’s in built and all that, but still, Elementor. And same goes for the bunch of other features like commenting for example. There are like bunch of different commenting solutions because what WordPress offer, post commenting is not enough, or not the way other people wants it.
\n\n\n\n[00:40:20] Nathan Wrigley: Yeah, I think it’s really interesting, and my guess is that the conversation in the WordPress space for the next 18 months at least will be highly focused on this topic. And the fact that people are talking about it, and the fact that you’ve already done a lot of work inside that space. Actually, when I think about it a little bit more, maybe it puts you in a kind of a pole position to have those conversations.
\n\n\n\nAnd also you can build on top of what Core produces. And it may be that there’s parts of the code that you’ve already written that can be removed or replaced by what’s in Core, and you can build on top of that. So yeah, that’s an interesting approach, and WordPress’ history does show that, doesn’t it?
\n\n\n\nAnd the page builder example is perfect. There isn’t just space for one. The audience inside the WordPress community is so vast that you can have myriad different solutions to the same problem. And although WordPress might be tackling collaboration in some form, it may be that other people wish to have a different form of collaboration, or an extended feature set in the collaboration space. So yeah, that’s a nice answer and it, certainly implies that you’ll be around for the foreseeable future.
\n\n\n\nAnil, before we wrap it up, I just want to give you an opportunity to tell us where people can find you if they want to reach out to you, where would be the best place to do that?
\n\n\n\n[00:41:41] Anil Gupta: For me personally, I have a newsletter slash blog, where I write a lot about different things that I’m experimenting, and talk a lot about my businesses and podcast and all that. So that place would be my blog, that is anilg.substack.com. But for MultiCollab, it’s very simple, we have actually very good advantage if you search for WordPress collaboration or just multi collab, you’ll see a lot of resources that we have published and our website comes because we don’t have a competition at this moment.
\n\n\n\n[00:42:10] Nathan Wrigley: Google is your best friend, and probably will be for the foreseeable future. So Anil, thank you so much for sharing your insights into multi collaboration in the WordPress space. We’ll see how this all develops, but thank you so much for chatting to me today, I really appreciate it.
\n\n\n\n[00:42:24] Anil Gupta: Thanks for having me. And uh, yeah, it was a blast.
\nOn the podcast today we have Anil Gupta.
\n\n\n\nAnil is the CEO and co-founder of Multidots, Multicollab, and DotStore. His companies serve a wide range of customers, from large publishers and news companies to WordPress users.
\n\n\n\nOf specific interest to this episode of the podcast is Multicollab, which offers a WordPress plugin that allows for Google Doc-style collaboration, including commenting, suggestions, and real-time editing.
\n\n\n\nWhen Google Docs was first brought to the market, it was a pretty big deal. Perhaps not the first to offer a real time collaborative interface, it was certainly the first to gain widespread adoption. Fast forward to today and it’s more or less inconceivable that you’d create documents which were not editable by multiple people at the same time. Most modern online software ships with this built in. The extraordinary became the norm, and the expectation.
\n\n\n\nBy what about WordPress? As the largest CMS, WordPress still lacks this functionality, but hopefully not for long. Phase 3 of the Gutenberg project, the phase that we are in at the moment, aims to make it possible for many users to amend content at the same time.
\n\n\n\nThe beguiling simplicity of the Google Docs interface makes it seem that this would be a trivial feature to add into WordPress, but this is not the case. Unlike proprietary software in which the vendor owns and manages the whole stack, WordPress is used by many different people, in many different ways. They might have a shared server, or a range of plugins, and this all complicates the picture.
\n\n\n\nAnil talks about how his team decided to tackle this problem for their own plugin, and he explains some of the hurdles they’ve experienced along the way. They’ve taken a cautious approach, developing different features one at a time, working through the technical challenges with commenting, before moving onto real time editing.
\n\n\n\nAnil paints a picture of a bright future for WordPress, once this new feature set is completed, but it’s also interesting to see how many challenges the developers will need to overcome before it can be shipped in a future WordPress update.
\n\n\n\nIf you’re interested in finding out about the future of editing content in WordPress, this episode is for you.
\n\n\n\nHosts Jonathan and Tammie reflect on their experiences with the Gutenberg project in WordPress.
\n>> The post Gutenberg, the Beginning to the Present with Tammie and Jonathan appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 17 Jan 2024 09:23:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"HeroPress: With WordPress Another Life Is Possible – Con WordPress otra vida es posible\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=6397\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:152:\"https://heropress.com/essays/with-wordpress-another-life-is-possible/#utm_source=rss&utm_medium=rss&utm_campaign=with-wordpress-another-life-is-possible\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:19748:\"Este ensayo también está disponible en español.
\n\n\n\nDecember 11, 2023, Palacio Neptuno (Madrid). I am sitting, surrounded by many people, we are all looking towards a stage with a screen that reads “State of the Word 2023”. I look at the clock, it reads 16:05, and two thoughts come to my mind: the first one is “It seems that Matt is late”; the second one is caused by having seen the date that read “11 Dec”, my brain wants to remind me something… “Holy moly! It was 15 years ago today that I read my doctoral thesis in neuroscience”.
\n\n\n\nI hope this resource of starting “in media res” has caught your attention and you have some interest in knowing how I got there.
\n\n\n\nI have always been a curious person and a career in biology seemed like a good candidate where I could apply that trait. During my college years I got pretty good grades that allowed me to apply for a fellowship to develop a doctoral thesis.
\n\n\n\nDuring the years I spent on that thesis, among other things, I became an expert in the molecular mechanisms involved in programmed cell death in cerebral ischemia. You didn’t think you were going to read that combination of words in a post related to WordPress, did you? And I didn’t want to use more technical words like “apoptosis”, which is the “cool” way we scientists refer to programmed cell death.
\n\n\n\nAfter submitting the thesis (yes, indeed, on December 11, 2008, I like you to keep your attention) I continued researching neurodegenerative diseases in several postdocs. My trajectory was not aiming for Nobel (nor was it my intention), but I was “progressing adequately” within the “scientific career”.
\n\n\n\nSo what happened, Nahuai?
\n\n\n\nWhat went wrong to make you stop practicing as a scientist and start building websites with WordPress?
\n\n\n\nWhat happened is that I had an unpleasant work experience in the postdoc I was doing in a research center in Italy (back in 2014).
\n\n\n\nThe reason is not as important as the reflection it forced me to make. I realized that, although I loved doing research, the researcher’s lifestyle was not aligned with how I wanted to live.
\n\n\n\nThus began another investigation, one in which I intended to find a job that would allow me to have more freedom of schedule and location.
\n\n\n\nYou can imagine that the start of that new research, which meant putting aside around 15 years of training as a neuroscientist, was not easy.
\n\n\n\nThe general concept was to be a freelance and work on something online. Indeed, it was very general, but it fulfilled the requirements to achieve the freedom I was looking for. Luckily, WordPress came fairly early into the equation (in the same 2014) and I immediately felt comfortable with the tool.
\n\n\n\nI started training myself in the CMS. I created a technology website and a travel website to apply what I was learning. I did part of this process while I was still working as a scientist and another with unemployment benefits and the support of my partner.
\n\n\n\nYears later, when I felt able to create websites for clients and I managed to shake off the “imposter syndrome”, I started to offer my services on my personal website (created with WordPress, logically). The first clients were “friends, fools and family” and then I started to get clients thanks to the articles about WordPress and photography that I wrote in my blog.
\n\n\n\nWhen I was in Italy I started following WordPress news, mainly through podcasts, and I was surprised to hear how many events were taking place in Spain. So, as soon as I returned to Spain I started attending Meetups in and around Barcelona.
\n\n\n\nThat was followed by several WordCamps around the peninsula and by the time I realized it I was totally in love with the community. I soon realized that it was the “secret ingredient” behind the popularity of WordPress.
\n\n\n\nTaking advantage of the “falling in love phase”, I started participating in the community by giving talks, volunteering and later creating a WordPress Meetup in Terrassa, the city where I live now, and where I will soon celebrate 5 years as an organizer.
\n\n\n\nAt WordCamp Barcelona 2018 I met Esther Solà, a web developer I was following online (because she had a fantastic blog about WordPress) and we quickly made friends. A few months later we launched the podcast Freelandev, where we have been telling for almost 5 years how we make a living as WordPress developers (and many more things). The podcast served as an incubator to launch another common project, OsomPress, where we have been creating plugins and themes for WordPress for more than 3 years.
\n\n\n\nOnce I realized my love for the Spanish WordPress community, I also wanted to get to know the international community better (part of which I read and listened to), and that’s why I went to WordCamp Europe 2019 as a volunteer. The experience was so good that since then it’s an annual appointment that I don’t miss (conditions permitting).
\n\n\n\nI could go on for hours writing about the goodness of the community, but if I had to sum it up, I would say that it has given me many intangible things, but others that are tangible:
\n\n\n\nI think this sentiment, with personal variations, is shared by quite a few members of the WordPress community. There’s a phrase that gets repeated quite a bit, with different variations, but it goes something like “I came for the software and stayed for the people.”
\n\n\n\nOnce I proved to myself that I could make a living as a freelance WordPress developer, I put the focus on how I could contribute to “a better world”, within my modest means, of course.
\n\n\n\nOn the one hand, I started to be more selective with the projects I accepted, prioritizing those that were going to have a positive impact, and on the other hand I started to create content about web sustainability.
\n\n\n\nI owe the inspiration for the latter to a talk by Roberto Vazquez at WordCamp Pontevedra 2019, in which he talked about the environmental impact of websites. Another example of the “snowball” effect that comes driven by being part of the community.
\n\n\n\nAnd speaking of snowballs. Thanks to meeting Hannah Smith at WordCamp Europe 2019, I discovered the Green Web Foundation fellowship I got last year. Thanks to it I was able to create the limited series podcast Sustain WP, which is all about digital sustainability and WordPress, which allowed me to interview a lot of interesting people in the community.
\n\n\n\nHannah was also involved in the creation of the WordPress sustainability initiative which months later became the official Sustainability Team. If you’re interested in learning more about the process and what we’re doing on the team I invite you to listen to the episode where we explain it in detail.
\n\n\n\nAs a culmination of 2023, I was honored to be elected, along with 3 other fantastic colleagues, as a representative of the Sustainability Team.
\n\n\n\nThese types of articles are always difficult for me to write (I don’t do it often either). The intention is to inspire others, but I am also aware that we all start from different circumstances. In that sense, I feel privileged and can’t help but worry that the small personal “successes” I share will have the opposite effect to the one I’m looking for.
\n\n\n\nMaybe it’s an unfounded fear and I’ve managed to convey my enthusiasm for life in general and the WordPress community in particular. Hopefully it inspires you to apply it in your own way.
\n\n\n\nWhether I’ve achieved one thing or the other, I’ll be happy to read you in the comments. :)
\n\n\n\n11 de diciembre de 2023, Palacio Neptuno (Madrid). Estoy sentado, rodeado de mucha gente, todos estamos mirando hacia un escenario con una pantalla donde se lee “State of the Word 2023”. Miro el reloj, marca las 16:05, y me vienen dos pensamientos a la cabeza: el primero es “Parece que Matt llega tarde”; el segundo viene provocado por haber visto la fecha que indicaba “11 dic”, mi cerebro quiere recordarme algo… “¡Leche! Que hoy hace justo 15 años que leí mi tesis doctoral en neurociencia”.
\n\n\n\nEspero que este recurso de empezar “in media res” haya captado tu atención y tengas cierto interés en saber cómo he llegado hasta ahí.
\n\n\n\nSiempre he sido una persona curiosa y la carrera de biología me pareció una buena candidata donde poder aplicar ese rasgo. Durante los años de universidad obtuve calificaciones bastante buenas que me permitieron optar a una beca para desarrollar una tesis doctoral.
\n\n\n\nDurante los años que dediqué a esa tesis, entre otras cosas, me convertí en un experto en los mecanismos moleculares implicados en la muerte celular programada en la isquemia cerebral. ¿A que no pensabas que ibas a leer esa combinación de palabras en un post relacionado con WordPress, eh? Y eso que no he querido usar palabras más técnicas como “apoptosis”, que es la forma “cool” con la que nos referimos los científicos a la muerte celular programada.
\n\n\n\nDespués de presentar la tesis (sí, efectivamente, el 11 de diciembre de 2008, me gusta que mantengas la atención) continué investigando enfermedades neurodegenerativas en varios postdocs. Mi trayectoria no apuntaba al Nobel (ni era mi intención), pero sí “progresaba adecuadamente” dentro de la “carrera científica”.
\n\n\n\nEntonces ¿qué pasó, Nahuai?
\n\n\n\n¿Qué se torció para que dejaras de ejercer como científico y empezaras a montar webs con WordPress?
\n\n\n\nLo que ocurrió es que tuve una experiencia laboral desagradable en el postdoc que estaba realizando en un centro de investigación en Italia (allá por 2014).
\n\n\n\nEl motivo no es tan importante como lo es la reflexión que me obligó a realizar. Me di cuenta de que, aunque me encantaba investigar, el modo de vida del investigador no estaba alineado con cómo quería vivir.
\n\n\n\nAsí empezó otra investigación, una en la que pretendía encontrar un trabajo que me permitiera tener más libertad de horario y ubicación.
\n\n\n\nTe puedes imaginar que el comienzo de esa nueva investigación, que suponía dejar de lado unos 15 años de formación como neurocientífico, no fue fácil.
\n\n\n\nEl concepto general era hacerme freelance y trabajar en algo online. Efectivamente, era muy general, pero cumplía los requisitos para ganar esa libertad que buscaba. Por suerte, WordPress apareció bastante pronto en la ecuación (el mismo 2014) y en seguida me sentí cómodo con la herramienta.
\n\n\n\nEmpecé a formarme en el CMS. Creé una web de tecnología y otra de viajes para aplicar lo que iba aprendiendo. Parte de este proceso lo hice mientras seguía trabajando como científico y otro con la prestación de desempleo y el apoyo de mi pareja.
\n\n\n\nAños más tarde, cuando me sentí capaz de crear webs para clientes y conseguí sacudirme un poco el “síndrome del impostor”, empecé a ofrecer mis servicios en mi web personal (creada con WordPress, lógicamente). Los primeros clientes fueron “friends, fools and family” y después me empezaron a llegar clientes gracias a los artículos sobre WordPress y fotografía que escribía en mi blog.
\n\n\n\nCuando estaba en Italia empecé a seguir noticias sobre WordPress, principalmente a través de podcasts, y me sorprendía escuchar la cantidad de eventos que tenían lugar en España. Por eso, en cuanto regresé a España empecé a acudir a las Meetups de Barcelona y sus alrededores.
\n\n\n\nA eso le siguieron varias WordCamps por la península y para cuando me quise dar cuenta ya estaba totalmente enamorado de la comunidad. Pronto me di cuenta de que era el “ingrediente secreto” detrás de la popularidad de WordPress.
\n\n\n\nAprovechando la “fase de enamoramiento”, empecé a participar en la comunidad dando ponencias, acudiendo como voluntario y más adelante creando la Meetup Terrassa, cuidad donde resido ahora, y donde pronto cumpliré 5 años como organizador.
\n\n\n\nEn la WordCamp Barcelona de 2018 conocí a Esther Solà, una desarrolladora web que seguía online (porque tenía un fantástico blog sobre WordPress) y rápidamente hicimos migas. Pocos meses después lanzamos el podcast Freelandev, en el que llevamos casi 5 años contando cómo nos ganamos la vida como desarrolladores WordPress (y muchas más cosas). El podcast sirvió de incubadora para sacar otro proyecto común, OsomPress, donde creamos plugins y temas para WordPress desde hace más de 3 años.
\n\n\n\nUna vez constatado mi amor por la comunidad española de WordPress, quise conocer mejor también a la comunidad internacional (parte de la cual leía y escuchaba), y por eso fui a la WordCamp Europe 2019 como voluntario. La experiencia fue tan buena que desde entonces es una cita anual que no me pierdo (siempre que las condiciones lo permitan).
\n\n\n\nPodría, seguir durante horas escribiendo sobre las bondades de la comunidad, pero si tuviera que resumirlo diría que me ha aportado muchas cosas intangibles, pero otras que sí lo son:
\n\n\n\nCreo que este sentimiento, con variaciones personales, lo comparten bastantes miembros de la comunidad de WordPress. Hay una frase que se repite bastante, con distintas variaciones, pero dice algo así como “Llegué por el software y me quedé por la gente”.
\n\n\n\nUna vez que me demostré a mí mismo que podía ganarme la vida como desarrollador WordPress freelance, puse el foco en cómo podía contribuir a “un mundo mejor”, dentro de mis modestas posibilidades, claro.
\n\n\n\nPor un lado, empecé a ser más selectivo con los proyectos que aceptaba, priorizando los que iban a tener un impacto positivo, y por otro empecé a crear contenido sobre sostenibilidad web.
\n\n\n\nLa inspiración de esto último se lo debo a una charla de Roberto Vazquez en la WordCamp de Pontevedra 2019, en la que habló del impacto medioambiental de las páginas web. Otro ejemplo del efecto “bola de nieve” que viene impulsada por ser parte de la comunidad.
\n\n\n\nY hablando de bolas de nieve. Gracias a haber conocido a Hannah Smith en la WordCamp Europe 2019, descubrí la beca de Green Web Foundation que obtuve el año pasado. Gracias a ella pude crear el podcast de serie limitada Sustain WP, que trata sobre sostenibilidad digital y WordPress, el cual me permitió entrevistar a un montón de personas interesantes de la comunidad.
\n\n\n\nHannah también estuvo involucrada en la creación de la iniciativa de sostenibilidad de WordPress que meses más tarde se convirtió en el equipo oficial de sostenibilidad. Si estás interesado en conocer más sobre el proceso y lo que estamos haciendo en el equipo te invito a escuchar el episodio donde lo explicamos con detalle.
\n\n\n\nComo colofón de 2023, tuve el honor de ser elegido, junto a otros 3 fantásticos compañeros, como representante del equipo de sostenibilidad.
\n\n\n\nEste tipo de artículos siempre me resultan difíciles de escribir (tampoco lo hago a menudo). La intención es inspirar a otras personas, pero también soy consciente de que todos partimos de circunstancias distintas. En ese sentido, me siento un privilegiado y no puedo evitar preocuparme de que los pequeños “éxitos” personales que comparto tengan el efecto contrario al que busco.
\n\n\n\nIgual es un temor infundado y he conseguido trasmitir mi entusiasmo por la vida en general y la comunidad WordPress en particular. Ojalá te inspire para aplicarlo a tu manera.
\n\n\n\nTanto si he conseguido una cosa como otra, estaré encantado de leerte en los comentarios. :)
\nThe post With WordPress Another Life Is Possible – Con WordPress otra vida es posible appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 17 Jan 2024 08:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nahuai Badiola\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:27;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"BuddyPress: BuddyPress 12.1.1 Maintenance & Security release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=332779\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"https://buddypress.org/2024/01/buddypress-12-1-1-maintenance-security-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2603:\"BuddyPress 12.1.1 is now available. This is a security and maintenance release. Please update your BuddyPress as soon as possible.
\n\n\n\nThe 12.1.1 release addresses the following minor security issue:
\n\n\n\nThis vulnerability was reported privately to the BuddyPress team, in accordance with WordPress’s security policies. Our thanks to the reporter for practicing coordinated disclosure.
\n\n\n\nBuddyPress 12.1.1 also fixes 10 bugs. For complete details, visit the 12.1.1 changelog.
\n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\nYou can get the latest version by clicking on the above button, downloading it from the WordPress.org plugin directory or checking it out from our Subversion repository.
\n\n\n\n\n\n\n\nsabernhardt, emaralive, shawfactor, strategio, vapvarun, perchenet & imath.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 16 Jan 2024 23:43:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:28;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"WordCamp Central: WPBeginner joins the WordPress global community sponsorship program in 2024\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://central.wordcamp.org/?p=5109967\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:118:\"https://central.wordcamp.org/news/2024/01/wpbeginner-joins-the-wordpress-global-community-sponsorship-program-in-2024/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3704:\"Please join us in welcoming WPBeginner to the 2024 WordPress global community sponsorship program! WPBeginner’s pledge to sponsor all official WordPress community events (WordCamps, Meetups, and more) all around the world provides support and stability to our hardworking crew of volunteer event organizers. Thanks for everything, WPBeginner!
\n\n\n\n\n\nAt WPBeginner, we provide cutting-edge, helpful WordPress tutorials that are easy to understand for small businesses, bloggers, and non-techy WordPress website owners. Since 2009, our free WordPress video courses and tutorials are watched by over 56 millions WordPress users worldwide.
\n\n\n\nWhether you’re looking to learn how to build a WordPress website, decide which WordPress plugins to pick, or just learn the WordPress best practices to grow your website, WPBeginner’s free resources can help:
\n\n\n\nOver the last 14 years working closely with WordPress users and listening to their feedback, we have also created some of the most popular WordPress plugins including WPForms, AIOSEO (All in One SEO for WordPress), OptinMonster, MonsterInsights, and dozens more. Collectively over 25 million websites are using our free and premium WordPress plugins.
\n\n\n\nWPBeginner is part of the Awesome Motive family, and we’re on a mission to help small businesses grow & compete with the big guys using the power of open source.
\n\n\n\nIf you’re a WordPress professional looking for a remote role, we’re hiring. Come join our team.
\n\n\n\nIf you’re a WordPress product owner looking for an investment or selling your WordPress business, check out the WPBeginner Growth Fund.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 16 Jan 2024 15:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Isotta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"Do The Woo Community: The Future of SEO, Content and AI with Alex Moss\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78837\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"https://dothewoo.io/future-seo-content-ai/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:370:\"Discover how AI SEO and content creation impacts the future of WordPress and WooCommerce with Dave Lockie and Alex Moss.
\n>> The post The Future of SEO, Content and AI with Alex Moss appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 16 Jan 2024 09:46:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"WordCamp Central: GoDaddy sponsors WordPress community events worldwide\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://central.wordcamp.org/?p=5109971\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"https://central.wordcamp.org/news/2024/01/godaddy-sponsors-wordpress-community-events-worldwide/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3636:\"What would we do without our sponsors? We’re so grateful to GoDaddy for sponsoring WordPress community events all around the globe at the Gold level in 2024! GoDaddy’s support enhances local community events, such as WordPress meetup and WordCamps, improving the experience for WordPress enthusiasts and simplifying the organization process for our dedicated team of volunteers.
\n\n\n\n\n\nAt GoDaddy, our mission is to empower a worldwide community of entrepreneurs by giving them all the help and tools they need to grow online — including a simpler, safer WordPress experience.
\n\n\n\nWe champion our Makers of the Web by delivering a suite of WordPress solutions that enable fast and easy setup and then enables users to harness all the power of the world’s most popular CMS.
\n\n\n\nThe GoDaddy Pro Community was built by and for website designers and developers. Whether you’re new to web design or growing your existing business, you’ll find free tools, products, education, and expert support to help you more efficiently create and maintain beautiful sites — and wow clients.
\n\n\n\nWe provide a Managed WordPress experience that is as easy as it is effective. The latest version of WordPress comes pre-installed with exclusive themes, plugins, and tools to get you up and running quickly, with automated backups, updates, and malware removal so our Pros can spend less time on monotonous maintenance, and more time building their businesses.GoDaddy Pro works tirelessly to foster an active, nurturing community, with initiatives including the sponsorship of WordCamps globally, weekly GoDaddy Pro Meetups, our free GoDaddy Pro Academy courses, and our GoDaddy Pro Discussions Group. We’re proud to be a partner of the WordPress community and look forward to witnessing all the individual greatness that our efforts help support.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 15 Jan 2024 15:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Isotta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"Gutenberg Times: Quick Tip: How to use a classic menu in the navigation block of a block theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=27030\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:104:\"https://gutenbergtimes.com/quick-tip-how-to-use-a-classic-menu-in-the-navigation-block-of-a-block-theme/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1883:\"There was a question in the forums, if one needs to rebuild all the menus when switching from a classic theme to a block theme. In other words, how can you add an existing menu to the Navigation block.
\n\n\n\nIf there is only one classic menu, it will be displayed in the navigation block. But if there are multiple classic menus on the site, it doesn’t automatically convert it to a navigation block. In that case, it takes a manual step after you switched the theme, but you don’t have to recreate the menus.
\n\n\n\nHere are the steps to follow along with a separate test environment.
\n\n\n\nNow the steps on how to get the classic menu back into the template?
\n\n\n\nAnd here is the video of the whole process:
\n\n\n\n\n\n\n\nThank you to JuanMa Garrido for the testing instructions.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 15 Jan 2024 12:13:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:32;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:122:\"Gutenberg Times: Call for testing WordPress 6.5, page builders yes or no, Data Liberation and more — Weekend Edition 280\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=26964\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:127:\"https://gutenbergtimes.com/call-for-testing-wordpress-6-5-page-builders-yes-or-no-data-liberation-and-more-weekend-edition-280/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:13852:\"Howdy,
\n\n\n\nWe are 31 days away from WordPress 6.5 Beta 1, the version that closes the new version for new features. In so far it’s early, lots of work can still go into the next major upgrade. On the other hand, we are only three Gutenberg plugin versions away from WordPress beta 1. Gutenberg 17.5 RC is available for testing. If you have some time, it would be wonderful if you can use Anne McCarthy‘s instructions to take early opportunities to test WordPress 6.5. If you would rather not set up a local test site, you can also use the Gutenberg Nightly via WordPress playground for your early test.
\n\n\n\nMunich is again powered by snow and it freezing once more. Hubby and I are getting used to it; somewhat. Definitely longing for warmer weather.
\n\n\n\nI hope you stay warm and have a joyful weekend!
\n\n\n\nYours, 💕
Birgit
PS: If you intend to go to WordCamp Asia, I again opened up my calendar so we can schedule a 1:1 meeting, to chat about your products, what you need to be successful as a developer or how to contribute to WordPress or just catch up on life. And if you are not going to make it to WordCamp Asia, we can always get together at WordCamp Europe in June. 🤗
\n\n\n\n\nWordPress co-founder, Matt Mullenweg, elaborated on the WordPress blog the Data Liberation in 2024 project, he announced during State of the Word in Madrid. “Migrating your site to WordPress, or exporting all your content from WordPress, should be possible in one click. I want WordPress’ export format to become the lingua franca of CMSs, whether coming to WordPress or moving within WordPress. “, he wrote.
\n\n\n\nJustin Tadlock has again compiles the list of changes in Core and Gutenberg in What’s new for developers? (January 2024). “It’s a new year and time for exciting new things happening in the WordPress world. Catch the latest monthly roundup aimed at extenders.” he wrote. It’s a list of updates interesting for plugin, and theme authors as well as freelance and agency developers.
\n\n\n\n🎙️ Latest episode: Gutenberg Changelog #95 – Gutenberg 17.5, Early Testing of WordPress 6.5 and Block Themes with special guest: Carolina Nymark
\n\n\n\nJoen Asmussen, summarize the work of the WordPress design team in his post: Design Share: Dec 1-Dec 29. The team worked on
\n\n\n\nEric Karkovack wondered in his post Can Gutenberg and WordPress Page Builders Coexist?
\n\n\n\nMatt Medeiros asks: Is 2024 the Year of Page Builders? on the WPMinute episode 198.
\n\n\n\nIn his post, I Tried Building a Layout With the WordPress Block Editor And it Didn’t Go Very Well, Kevin Geary walks us through his learnings, trying the site editor for the first time.
\n\n\n\nOn YouTube, Anne McCarthy and Riad Benguella, Gutenberg Core Developer, chimed in with additional links and information
\n\n\n\nUsing Geary’s video and post as inspiration, Brian Coords walks us through how he would solve the layout problem Geary struggled with. Building an example layout in Gutenberg (response video). He covers this “demo layout using core blocks and a few lines of CSS (via register_block_style). Along the way, I discuss alignments and widths in Gutenberg, semantic elements, flex box tools for layout, custom CSS, and whether the block editor is a “page builder”.
\n\n\n\nJamie Marsland, PootlePress, created a tutorial to help Beginners understand the core concept around WordPress Block Themes: Three Key Principles for Beginners. “WordPress block themes revolutionize the way websites are built and designed, simplifying the process down to three core elements: Blocks Templates and Styles.” he wrote.
\n\n\n\nFor the WordPress themes team, Justin Tadlock updated the community of contributors on New Block-Focused Theme Handbook Docs and What’s Coming in 2024. After the revamp of the theme handbook, and publishing five new chapters, with eight still in draft. The next steps are the documentation of Patterns, Advanced topics and Classic Themes.
\n\n\n\nJacob Martella has some sound advice when you are on the quest of Converting Your Website to the Block Editor. “The biggest thing is that the site editor gives you so much control over how your website looks. You can customize the fonts and colors, change how your header and footer look and edit any template you want right from your dashboard. You don’t need to know CSS or PHP or have to worry about editing any files to do it” he wrote.
\n\n\n\n\n “Keeping up with Gutenberg – Index 2022”
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2021 on. Updated by yours truly. The index 2020 is here
Reminder! You are invited to the January Developers Hours for January 16th, 2024 at 15:00 UTC (10 am EDT) to Build your first WordPress block. In this online event, you’ll be on a walk-through the new tutorial in the Block editor handbook, and you will also learn more about the block development examples on GitHub.
\n\n\n\n\n\n\n\nThe page in the Block Editor Handbook experienced a rewrite: “Static or Dynamic rendering of a block” With the help of diagrams and new code examples, developers learn the main differences, advantages, and disadvantages of each approach of block development.
\n\n\n\n\n\n\n\nRyan Welcher released a new version of his Advance Query Loop plugin. Now ACF developer will see their meta keys in the auto-complete list for Post Meta queries.
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph.
\n\n\n\nFor questions to be answered on the Gutenberg Changelog, send them to changelog@gutenbergtimes.com
\n\n\n\nFeatured Image: Building blocks game. Free public domain CC0 image.
\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nImagine a more open web where people can switch between any platform of their choosing. A web where being locked into a system is a thing of the past. This is the web I’ve always wanted to see. That’s why I announced a new initiative called Data Liberation for 2024. Migrating your site to WordPress, or exporting all your content from WordPress, should be possible in one click. I want WordPress’ export format to become the lingua franca of CMSes, whether coming to WordPress or moving within WordPress.
\n\n\n\nI often hear about folks across the WordPress community duplicating efforts when creating scripts and workflows to move users to WordPress. Imagine if we shared those resources instead and built community-owned plugins that anyone could use!
\n\n\n\nBut it should be more than plugins; workflows, tutorials, and helper scripts should be shared, too. I want this resource to have space to include moving from social networks, moving from a page builder to core blocks, switching from classic to blocks, and improving WordPress current canonical plugins for importing.
\n\n\n\nOf course, the heart of any open source project is the community that shows up to build it. My hope is that this marks the start of a new contribution pathway, separate from core teams, that allows folks to contribute what they’ve learned and what they’ve created to help others move to WordPress. I expect this emphasis on migration will also influence future development, both in core and with recommended community or canonical plugins.
\n\n\n\nThere are a few things that I think will be key to making this project a success:
\n\n\n\nBy complementing the community’s existing efforts—the Five for the Future program, the Learn WordPress initiative, a focus on internationalization, etc.—my hope is that this will help even more people see themselves in the WordPress project, providing fresh momentum for WordCamps and meetups.
\n\n\n\nIt’s never been more crucial to champion openness on the web. Bringing focused attention to improved portability will untether users and increase their freedom like never before.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 12 Jan 2024 16:58:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:34;a:6:{s:4:\"data\";s:11:\"\n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"HeroPress: Foundational Pillars From Tokyo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://heropress.com/?p=6380\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:129:\"https://heropress.com/foundational-pillars-from-tokyo/#utm_source=rss&utm_medium=rss&utm_campaign=foundational-pillars-from-tokyo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11551:\"HeroPresser Anne McCarthy wrote an excellent article pointing out how much is different in WordPress these days, and asks the question above.
\n\n\n\nWhat’s your answer?
\nDestiny Kanno is from Tokyo, Japan, and works in Education about WordPress.
\n\n\n\nAs a Community Education Manager I work to break down perceived barriers for folks who want to contribute to the Make WordPress Training Team’s goals, and work as a close partner with the Training Team Representatives and members to empower them to excel in their leadership, goals, and strategy.
\n\n\n\nDestiny’s essay is available on HeroPress.com.
\nThere were twenty-three WordPress podcast episodes released this week!
\n\n\n\nThere are new episodes every single day, so be sure to stop by WPPodcasts.com and search for things that interest you!
\nHere are some of the great photos submitted to the WPPhotos project this week!
\n\n\n\n\nCC0 licensed photo by Anupam Bista from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Sharankrishna VP from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by keshavsamarpan from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Jonathan Desrosiers from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Bhuwan Bdr. Rokaha from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Sharankrishna VP from the WordPress Photo Directory.\n\n\n\n\nBe sure to check out the hundreds of other great photos!
\nThe header photo for this post is a CC0 licensed photo by Bhuwan Bdr. Rokaha from the WordPress Photo Directory.
\n\n\n\n\n\n\nThat’s it for this week! If you’d like to get this post in your email every week, make sure you sign up!
\n\nThe post Foundational Pillars From Tokyo appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 12 Jan 2024 16:39:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:35;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Matt: Forty!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=110348\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://ma.tt/2024/01/forty/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5122:\"Birthdays are so great because they’re about generosity.
\n\n\n\nThe act of giving, helping, is so generative.
\n\n\n\nIt’s what we can all do for ourselves and each other.
\n\n\n\nBut accepting is really hard, too! Gosh! Let it in.
\n\n\n\nSometimes we don’t let the gifts in.
\n\n\n\nApproaching forty has felt impossibly light and heavy at the same time for me.
\n\n\n\nIt’s so cool to be typing this into something we made together. I want you to really think about that. Ponder the enormity of all that came before that allowed you to be here today, and I want you to get a little bit excited, in that sacred hidden part of your heart that yearns for more.
\n\n\n\nLet’s keep doing that. And let’s make it better and share it so everyone can enjoy it. We make the world.
\n\n\n\nI’ve been enjoying so much all the posts coming in for the birthday gift. I’m reading them as fast as I can.
\n\n\n\nSpecifically, my failure mode is I share too much. I’m too generous. I like to err on the side of open. Here’s some amazing code I wrote that you have a legal license to use however you like. If you ask those closest to me how I mess up, it’s that I over-extend myself and try to do too much.
\n\n\n\nI’ve never shared this publicly, but when the Bay Lights wasn’t going to make it the first time, I mortgaged my apartment and used that money to get it over the line. My personal finances were messy for years after that. I think a lot about being impeccable with my word.
\n\n\n\nI want people to give the smallest $10 donation to the Bay Lights and encourage others to do the same so that we can all share in feeling that together, we can build things. And every time you see the light or bridge or think of San Francisco, you’ll think of that sacred hidden part of your heart that yearns for more, wants to leave everything better than you found it.
\n\n\n\nAdd some light.
\n\n\n\nLet the gift in.
\n\n\n\nThis is the part where the sounds come in and you hear it’s the remix.
\n\n\n\nI find myself returning, again and again, to the Automattic Creed, especially the first line:
\n\n\n\n\n\n\n\n\nI will never stop learning. I won’t just work on things that are assigned to me. I know there’s no such thing as a status quo. I will build our business sustainably through passionate and loyal customers. I will never pass up an opportunity to help out a colleague, and I’ll remember the days before I knew everything. I am more motivated by impact than money, and I know that Open Source is one of the most powerful ideas of our generation. I will communicate as much as possible, because it’s the oxygen of a distributed company. I am in a marathon, not a sprint, and no matter how far away the goal is, the only way to get there is by putting one foot in front of another every day. Given time, there is no problem that’s insurmountable.
\n
I’m having the most amazing day reading everything that people are sharing. I want to re-share the quote I shared on Tim’s podcast from Will Durant:
\n\n\n\n\n\n\n\n\nHealth lies in action, and so it graces youth. To be busy is the secret of grace, and half the secret of content. Let us ask the gods not for possessions, but for things to do; happiness is in making things rather than in consuming them.
\n
All birthday posts: 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 11 Jan 2024 21:57:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"Do The Woo Community: Share Your Do the Woo Experience with a Guest Post on the BobWP Blog\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78794\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"https://dothewoo.io/share-your-do-the-woo-experience-with-a-guest-post-on-the-bobwp-blog/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:438:\"If you have been a past sponsor, guest or guest host on our shows, consider a follow-up guest blog post on BobWP.com blog.
\n>> The post Share Your Do the Woo Experience with a Guest Post on the BobWP Blog appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 11 Jan 2024 10:28:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"Akismet: The Top 6 CAPTCHA Alternatives That Won’t Frustrate Users\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://akismet.com/?p=283673\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:46:\"https://akismet.com/blog/captcha-alternatives/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:16458:\"You know the drill. You’re super excited about a new purchase, commenting on a thrilling discussion in a forum, or providing feedback to an organization. You spend your time completing forms, writing thoughtful comments, or customizing your order only to find yourself trying to “check all the boxes with a stoplight in them” before actually submitting your information.
\n\nEveryone hates CAPTCHA puzzles, yet businesses continue to use them to filter out spam. Today, we’re going to explore the six best alternatives to CAPTCHA, all of which can protect you from spam activities without frustrating your prospects and customers. Finally, we’ll show you how Akismet uses machine learning to get progressively smarter about permanent spam removal.
\n\n\n\n\n\nFor years, users have been patient with CAPTCHA, which was one of the first solutions that helped pave the way to spam‑free websites. It stands for “Completely Automated Public Turing test to tell Computers and Humans Apart.” But like all solutions, there’s always room for improvement, and in today’s day and age, we need to find a better way to fight spam.
\n\nFirst, CAPTCHA puzzles are problematic for those with visual impairments, requiring not only the ability to see the CAPTCHA challenge but often to decipher extremely nuanced details within the images. Tests that require the user to type a string of characters can be difficult for dyslexic individuals, and some may be unfamiliar with cultural icons or graphics in visual ones.
\n\n\nSecond, with so many technologies focused on enhancing user experience, frustrations like the inability to solve a CAPTCHA puzzle will stand out more, negatively affecting your conversion and engagement rates. Typically, CAPTCHA puzzles can take ten seconds or more to solve and interrupt your user at a critical point in their engagement journey — right before they check out, submit a comment, or request more information.
\n\n\n\nOne study by SEO software company, Moz, found that many users abandon forms when they encounter a CAPTCHA — resulting in an overall conversion rate drop of three percent. Another study by Stanford found that only 71 percent of users even attempt to solve a CAPTCHA before abandoning the page altogether.
\n\n\n\nIf that’s not enough, a CAPTCHA may incorrectly identify a real human being as a bot, blocking further interaction with a site, while allowing more sophisticated, advanced bots through.
\n\n\nResearchers at the University of California in Irvine recently conducted a study testing both humans and bots on popular CAPTCHA puzzles. The study found that bots solved distorted‑text CAPTCHA tests almost perfectly in less than a second, while human beings had an accuracy rate of between 50 percent and 84 percent, spending up to 15 seconds per puzzle.
\n\nFinally, it takes some significant computing power for CAPTCHAs to work properly, slowing down load times for web pages and adding to user frustration.
\n\nUnfortunately, efforts to improve CAPTCHA puzzles are still lacking. Audio versions were supposed to be a solid solution, but analysis shows that they’re more time intensive and significantly more difficult for certain users depending on their native language. Another study noted a 50 percent failure rate with audio options.
\n\n\nForcing people to complete any kind of test is simply not the best option if you want to maximize engagement and conversions.
\n\n\nBefore jumping into the six alternatives to CAPTCHA puzzles, here are some key things you’ll want to look for when choosing your bot‑detecting solution.
\n\nFirst, you’ll want to be sure that your solution can successfully block bots and spam while allowing prospects and customers easy access to your site and offerings. Unfortunately, a static software solution won’t work, as bad actors are continuously trying to up their game with more sophisticated, human‑like bots all the time. Be sure your selected alternative can stay ahead of the bot creators.
\n\nSecond, be sure your alternative is either much easier to complete, or, better yet, invisible to your prospects, customers, and visitors. Your goal is to reduce or eliminate friction to create a more positive overall user experience.
\n\n\nAlong the same lines, look for a cloud-based solution so that your page load times are unaffected by the bot-catching activities.
\n\n\n\nFinally, you must ensure that your solution complies with global and local government data privacy rules and regulations. Remember that CAPTCHA alternatives cannot protect your site alone; instead, they must be one component of an overall security program to protect your site from malicious activity and threats.
\n\n\nFortunately, several alternatives to CAPTCHA are available on the market today, working to block spam effectively, without negatively affecting your user experience. Here are the top six to consider:
\n\n\n\n\n\n\nFounded in 2005, Akismet has been on a mission to rid the world of spam for nearly two decades. Its solution is different from CAPTCHA, primarily because it works completely in the background of a website and does not rely on user input to identify bot or spam attacks. As a result, it protects sites from unwanted bot activity without relying on prospects, customers, or visitors to prove they’re human.
\n\nMore than 100 million customer websites rely on Akismet, which has successfully removed more than 500 billion pieces of online spam from the web. Used by both WordPress sites and others, Akismet has generated one of the largest databases of spam activity in the world.
\n\nIn addition, the solution relies on advanced machine learning technology to continuously improve, staying ahead of the bad actors who are always looking for new ways to break through site protections.
\n\nSelf‑hosted spam‑fighting solutions can negatively affect the performance of the site itself, slowing down page load speeds. Akismet is a cloud‑based solution, removing the operating activity from your site while delivering the protection you desire.
\n\nA honeypot anti‑spam trap is designed to trick harmful bots and spam generation programs into identifying themselves as spam. Like a real honeypot that attracts various people, animals, and insects, a honeypot anti‑spam trap lures bots and spam programs with something that’s not visible to human beings.
\n\nOne of the most common honeypot anti‑spam traps is to incorporate a field within the code that is not required or even seen by a human completing the real contact, order, or comment form. A bot, however, will scan that field and complete it, revealing its identity as a robot spammer.
\n\nThe honeypot then filters out and deletes that submission. While this method of spam detection can be effective for some basic bots, the honeypot anti‑spam trap can be circumvented by more sophisticated spam efforts.
\n\nAnother CAPTCHA alternative is time‑based form submissions. The idea is that humans will take a certain amount of time to complete a form, submit an order, or write a comment, while bots typically submit spam responses much faster.
\n\nAlthough time‑based form submissions can work in theory to weed out the most basic bots, bad actors who are set on spam attacks can easily program a bot to slow down its activity. So companies that use this method are hoping that spammers targeting their site will be too unsophisticated to slow down their bot submissions and will just move on to other targets. This is, frankly, a fairly weak form of protection.
\n\n\n\n\n\nreCAPTCHA v3 is a more advanced bot detection solution, helping site owners identify spam activity on their website and customize the level of protection to suit their risk tolerance.
\n\n\nLike the other CAPTCHA alternatives, version three doesn’t rely on user interaction to make the bot or spam determination, but works in the background of a website. It uses adaptive risk analysis to alert site owners of suspicious behaviors and should be placed on multiple pages so that patterns of abusive activities are more accurate.
\n\n\nWhile this sounds pretty lovely, there are a fair number of downsides to using reCAPTCHA v3. First, though it allows for more customized control by site owners, it also requires advanced setup and integration with Google’s API, which could be difficult for the average site owner.
\n\nThere’s some pushback around privacy, as it provides Google with a lot of data, and it can also prevent the functioning of certain positive bots, like SEO crawlers.
\n\n\nAnd while it’s good at detecting spammers, it’s known to falsely label real user interactions as spam without providing recourse for these individuals.
\n\n\nWith reducing friction is the number one reason businesses want to find a CAPTCHA alternative, there have been developments in simplifying the puzzles themselves. For example, instead of presenting blurry pictures and asking users to identify some random item in each of them, organizations have added a field at the end of their form asking for the solution to a simple math problem.
\n\nSimilar solutions require checking a box to indicate that visitors are human, using a slider bar before completing the submission, or playing a short drag‑and‑drop game to continue.
\n\n\nAll of these function very much like popular CAPTCHA puzzles, but may be less frustrating for the user. Unfortunately, more sophisticated bots may be able to find ways to complete these tasks as easily or better than human beings. And any barrier, even if it’s quick to get through, will deter some positive activity.
\n\n\nIf you run a site, you already know the importance of site security and probably have some general protections like firewalls, multifactor authentication, and malware detection in place.
\n\n\nWhile these can protect your site from a wide variety of cybersecurity threats and may prevent some spammy behavior in the process, they aren’t really designed to specifically address spam.
\n\n\nIt’s important for every website to find a solution for this specific problem to keep your comment sections, form submissions, and order process free from spam and bot activity.
\n\nWhether you’re a WordPress user or rely on another website platform, Akismet is the best alternative to CAPTCHA. First and foremost, its ability to work completely behind the scenes means that your website visitors are released from the task of solving time‑consuming, frustrating puzzles before completing an order, leaving a comment, or filling out a form.
\n\nThis fact alone means that you’ll improve your user experience, reduce friction in engaging with your organization, and increase conversions. All of those benefits ultimately lead to higher profits and long‑term success.
\n\nIn addition, because Akismet has been on a mission to remove spam from the web for nearly 20 years, it has amassed a significant database of spam information and taken advantage of machine learning technology to stay ahead of spam creators. This experience and massive database means that Akismet is incredibly effective at identifying spam and is continuously improving its performance.
\n\nWith 99.9% accuracy, though, it’s already at the top of the game.
\n\nFinally, Akismet doesn’t negatively affect the performance of your website because it operates in the cloud. This means that page load times don’t decrease, even as Akismet is busy protecting your organization from bot attacks and spam.
\n\nTo learn more about how Akismet can protect your business, reach out today.
\n\nA CAPTCHA is a computer‑generated test used to differentiate humans from bots. It became a popular way to block spam attacks automatically in the early 2000s. CAPTCHA tests may include checking a box, typing a series of characters, or solving a visual puzzle before comments, forms, or orders are submitted.
\n\nCAPTCHA tasks can be extremely frustrating to users, especially when they’re difficult to solve or incorrectly identify a human as a bot. They create a poor user experience, reduce conversions, and can leave a negative brand impression. They also limit engagement with visually impaired visitors.
\n\nYes, fortunately, there are alternatives to fight spam effectively without using CAPTCHA puzzles. The most effective is Akismet, which not only successfully removes and blocks spam from websites, but continuously improves its performance through machine learning.
\n\nAkismet is a cloud‑based, spam‑fighting solution that works completely in the background to rid your site of malicious activity. It requires no interaction from your users, which means no added friction in your user experience. Akismet has successfully removed more than 500 billion pieces of spam from the web.
\n\nAkismet is the best alternative to CAPTCHA because it successfully blocks spam by working behind the scenes, freeing your visitors from frustrating puzzles. With nearly two decades of experience, Akismet has one of the largest spam databases available and continues to improve its detection capabilities through machine learning technology.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 10 Jan 2024 15:16:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Jen Swisher\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"WPTavern: #105 – Pascal Birchler on Revolutionizing Image and Video Processing Within WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=152160\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:111:\"https://wptavern.com/podcast/105-pascal-birchler-on-revolutionizing-image-and-video-processing-within-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:45214:\"Transcript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.
\n\n\n\nJukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, new ways to interact with your media within WordPress.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast, and you can copy that URL into most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox, and use the form there.
\n\n\n\nSo on the podcast today, we have Pascal Birchler. Pascal is a longstanding WordPress community member, and Core committer, with a focus on internationalization, WP-CLI, and performance.
\n\n\n\nHe’s been working on a project for the past six months to enhance the media capabilities of the WordPress block editor. His work includes client side image optimization, image compression, video enhancements, and speech to text features such as subtitle generation.
\n\n\n\nIt’s unlike anything that I’ve ever seen, you upload media into the block editor and it’s manipulated right there inside the editor, by the browser, not by some remote server.
\n\n\n\nThis is all achieved by harnessing the power of WebAssembly, and we discover what Pascal has managed to achieve thus far, and how he thinks that there’s going to be so much more to come.
\n\n\n\nWe talk about how you can change images from legacy formats, like JPEG and GIF, into other, more modern formats, such as WebP and AVIF. Pascal explains how this is actually achieved, and why the new format so desirable. It’s all about reducing file sizes, server resource consumption, and the speed boost your site will gain as a result.
\n\n\n\nWe also get into the conversion of animated GIFs into videos, and creating videos with transcripts on the fly. And remember, this is all done in the block editor, with the browser itself as the workhorse.
\n\n\n\nPascal seems to be onto something here, and it’s really compelling listening to him argue that something like his plugin might be worthy of inclusion into WordPress Core at some point.
\n\n\n\nHe explained some other projects, which he’s been working on inspired by the high volume of feedback he received after releasing his plugin.
\n\n\n\nIf you’re interested in pushing the boundaries of user experience, performance optimization, and compliance with evolving web standards this episode is for you.
\n\n\n\nIf you want to find out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast, where you’ll find all the other episodes as well. And so without further delay, I bring you Pascal Birchler.
\n\n\n\nI am joined on the podcast today by Pascal Birchler. Hello, Pascal.
\n\n\n\n[00:03:42] Pascal Birchler: Hello. Hi there.
\n\n\n\n[00:03:43] Nathan Wrigley: Very, very nice to have you with us. We’re going to talk today, well, I think it’s broadly, we’re going to be talking about images. But there’s an awful lot of different technologies that Pascal has been working on over the, well, I don’t know how long. But I’ve only recently caught sight of the projects that you’ve been working on.
\n\n\n\nPascal, just before we begin that, would you just tell us a little bit about yourself? Perhaps what your day job is, what your relationship is with WordPress, and so on. Just a little bio time really.
\n\n\n\n[00:04:10] Pascal Birchler: Sure, yeah. So my name is Pascal, and I’ve been a WordPress community member for, I don’t know, 15 years now or so. So I’ve been doing a lot of contributions around internationalisation, so like anything multilingual. But recently also performance, and day-to-day, that’s really what I’m focusing on.
\n\n\n\nSo I started as a WordPress contributor. Then I joined Google, as part of a team that is trying to make the web faster, that includes making WordPress faster.
\n\n\n\n[00:04:36] Nathan Wrigley: Yeah, the performance team have been doing great work over the last, well, I’m going to say about 18 months it feels like they’ve been in existence. But WordPress itself has been made significantly quicker, over the various iterations of the project recently.
\n\n\n\nBut I know that the browsers themselves have become better at doing an awful lot of things. And so I think what we’re going to talk about today will probably involve conversations around what the browsers can handle, and things like that.
\n\n\n\nBut it’s very rare, Pascal, that I watch something online to do with WordPress, or technology, and I am actually having to lift my jaw away from the floor. But a little video that Pascal posted onto Twitter, not that long ago, maybe 10 days ago or something like that, really did make my jaw hit the floor. Because you were showing things that you’ve been working on that I had never seen before.
\n\n\n\nNot just that, I had no intuition that it was even possible. It’s going to make your WordPress life much better in the future, let’s hope.
\n\n\n\nDo you want to tell us a little bit about the project that you’ve been working on? And then we’ll get into the weeds of all of the different things that it can do, and yeah, just tell us how long you’ve been working on it, and what it really does.
\n\n\n\n[00:05:42] Pascal Birchler: Sure. Absolutely. First of all, that’s exactly the reaction that I hoped to get from people, as I’ve been working on this project, or these media experiments, how I would like to call them, for maybe half a year or so. Like I occasionally started working on it and didn’t stop, and start again.
\n\n\n\nIt’s basically a collection of things that enhance the media capabilities of WordPress, or specifically the block editor. Most of the things are around like client side image optimisation, image compression. But also anything related to videos or speech to text, like subtitle generation.
\n\n\n\n[00:06:18] Nathan Wrigley: So you just swept it to one side, really, how impressive it is. But the key component there, that was so amazing to me, was the fact that it’s all done client side. So perhaps, dear listener, the best thing to do would be to pause this episode, go and search for it over on WP Tavern, and watch from the links, the two little Twitter videos that Pascal put together, and you’ll be in a much better position.
\n\n\n\nBut what you’re going to see is truly remarkable. So it’s block editor based, so you’re in the Gutenberg editor. I don’t know if it’ll work in any other scenario of WordPress, with page builders or what have you. But that’s the paradigm that we’re talking about.
\n\n\n\nAnd Pascal is sitting there, and he decides that he wants to have an image which is currently a jpeg, and he doesn’t want it to be a jpeg. He wants to reduce the size of it, so that it consumes less resources on the server, but also can be served up to the end user. He wants to pass Core Web Vitals, because he’s a good Googler.
\n\n\n\nAnd so he throws it into Gutenberg, and Gutenberg seemingly converts it. Now I’m obviously doing it injustice. Please tell me what’s happening, because I haven’t the faintest idea how you’ve achieved this. So you put an image directly onto the Gutenberg canvas, and it’s no longer a jpeg. It’s been converted in some way, in the background, disconnected from the internet. This could be on a computer, completely disconnected from the internet. So it’s happening in the browser. How is it happening?
\n\n\n\n[00:07:40] Pascal Birchler: So first of all, browsers are extremely capable of doing image compression, or even image conversion. But they’re also a little bit limited in like to what extent they can do that. So to overcome those limits, I’m using a technology called WebAssembly. Which allows basically like regular software that you would otherwise install on a computer, and bring that to the browser.
\n\n\n\nAnd in this case, this is an image processing library that I’m using. For example, I’m using the VIPS, or libvips image library. And using WebAssembly I can do all sorts of image rotation, thumbnail generation, directly in the browser. And then from there I will upload it to WordPress.
\n\n\n\n[00:08:19] Nathan Wrigley: So is this, therefore a plugin, that you have pre-installed into the version of WordPress that you were using for the demo there. So this is a plugin that you’ve built, you’ve installed it, and I don’t if there are any settings in there. But even if you just activate it, as soon as you begin throwing images, there is the option to convert them to different formats, right out of the box. You don’t have to do anything else.
\n\n\n\n[00:08:42] Pascal Birchler: Correct. It’s a plugin that I started. It works without any additional configuration, but of course, if you prefer not changing the image format, but just want to compress images. Or if you prefer, let’s say WebP or AVIF over jpeg, you can say so as well. And there are a few more settings that I added, but mostly for like testing and like, trying different things out.
\n\n\n\n[00:09:04] Nathan Wrigley: Yeah. I mean, it’s a first run at this project, so maybe we’ll see some things in the future. We’re recording this at the end of 2023, so it’s still really hot off the press.
\n\n\n\nBut just to digress a little bit, and move away from the technology. Why have you done this? What is the purpose of it? Now I’m guessing that there’s maybe some sort of environmental impact here. There’s the cost of storage, and all of those kind of things. What’s the point? Why would you even want to convert images from one format to another? After all, it looks the same, broadly, once you’re viewing it. What’s the purpose?
\n\n\n\n[00:09:36] Pascal Birchler: Doing this has many advantages. So one is that if you want to do this, but you’re limited in server resources, now this allows anyone to use this technology and compress their images. And compressing images, or using a different file format, as you say, has like good impact on file size. Which means less bandwidth used, has a nice side effect of like images loading faster on your website, which is great for passing all these Core Web Vitals.
\n\n\n\nBut it’s also a user experience benefit. Your visitors will see the images faster. And I think that’s the nice thing about this project, is that it has some performance aspects, but in the end it’s a lot about user experience.
\n\n\n\n[00:10:18] Nathan Wrigley: So the modern versions of image formats, it may be that some of the listeners aren’t really familiar with those. I’m pretty sure that if you’ve been on the internet for any length of time, you’re familiar with jpegs, and pngs, and GIFs, or GIFs, however you wish to pronounce it. But you’re trying, well, in the video at least, you are converting them into an image format, which maybe people haven’t heard of before.
\n\n\n\nIt’s called AVIF, but also I think you mentioned WebP as well. I know it’s maybe not in your wheelhouse directly, but can you just give us an idea of what’s going on there? What kind of reduction could we have? Let’s say if we took a, I don’t know, a two megabyte jpeg and pushed it through to be an AVIF. Roughly speaking, and I know it’s dependent upon what is in the image, but broadly speaking, what kind of benefits can you get in terms of percentages that are cut away?
\n\n\n\n[00:11:04] Pascal Birchler: Oh, that’s a great question. I think in my test video, I saw a reduction of like maybe 40% or so in file size.
\n\n\n\n[00:11:11] Nathan Wrigley: Good grief. Right.
\n\n\n\n[00:11:12] Pascal Birchler: And there was like no noticeable differences to the eye. But there are like quality settings that you can change. Depending on the level of quality that you like for your use case, you can get it even further down.
\n\n\n\n[00:11:24] Nathan Wrigley: So really significant amounts of data. You know, if your website is image heavy, then doing this, and there’s no noticeable loss to the viewer. Perhaps there is some sort of degradation, if you were to expand it, and you were a professional photographer, who knows? But something in the region of a 40% decrease.
\n\n\n\nDo you know if, at this point, so again we’re in December 2023. Is it possible for all browsers to be able to show these images back to us? So it’d be fabulous to be able to use AVIFs, but then obviously if a significant proportion of the internet out there can’t actually see them, because their browsers don’t support that, that would be troublesome. So do you have any inclination as to what the compatibility is with browsers, displaying WebPs and AVIFs?
\n\n\n\n[00:12:08] Pascal Birchler: I think last I checked, WebP is supported by all browsers. So that includes Chrome, Firefox, Safari, Edge, and so on. And AVIF is not currently supported by default in Edge. All the other browsers support it. And in Edge, it needs to be enabled with a flag.
\n\n\n\n[00:12:25] Nathan Wrigley: Oh, so there is support, it just merely isn’t enabled. So if you’re an Edge user, you can make it available.
\n\n\n\nSo really there’s no reason not to do this if pretty much every browser is able to support this, why wouldn’t you do this? And I guess the beauty of your system that you’ve built, is that there’s no, there’s literally no thing to do. You just put the image onto the page, or the post, or whatever it may be, in the same way that you would always do, and it just happens on the fly.
\n\n\n\nIs there a little bit of a wait there? So let’s say, again, my image of two megabytes, something like that, jpeg uploaded. Is this happening more or less instantly in a typical modern computer, or do I have to sit there and twiddle my thumbs for a little while, as I might have done in the past if I was using a server side technology to do this?
\n\n\n\n[00:13:13] Pascal Birchler: It’s pretty much instantly, but only because you don’t see what’s going on in the background. So when you drop the image in the editor, you can already see it, you can already, you know, add some gradients in the block editor, or continue writing your post. And in the background, the image is compressed, and all the thumbnails are being generated, and finally uploaded to WordPress. But you can already continue editing.
\n\n\n\n[00:13:37] Nathan Wrigley: Okay. So really you can just carry on with your day, keep editing as normal, and in the background this will happen.
\n\n\n\nSo what’s the flow in terms of where this is getting saved? So, again, we’ll use my example, I’m using a jpeg. Will the jpeg be saved in the media library, ultimately, as well? Or will just the converted image get kept? Because I know that a lot of the other server side solutions, some commercial solutions and what have you, which compress images, they have loads of options and many of them are, for example, keep the original. We’ll convert it for you, we’ll compress it for you, but we’ll also keep the original. And it may not be that that’s what your plugin does. So how does it handle the original? Where does it put that?
\n\n\n\n[00:14:15] Pascal Birchler: Right now it keeps uploading the original to WordPress, in case you want to restore that or use that for, I don’t know, downloads or something. But this can be made optional, because everyone has different needs. For example, photographers prefer to have the full size images available, just in case, maybe for their clients. But this can be turned off if you prefer to save resources.
\n\n\n\n[00:14:37] Nathan Wrigley: Okay. So that, I guess, brings me to the next question. What are the settings that you have at the moment? So, you’ve mentioned that you know, you can keep the original, or delete the original, or what have you. Are you able to specify, okay, every time I upload a jpeg, turn it into an AVIF, every time I upload a WebP, turn it into an AVIF? Are there different settings in the backend there that I can configure, so that it just meets my exact requirements?
\n\n\n\n[00:14:58] Pascal Birchler: You pretty much nailed it. Right now the setting is limited, like you can choose your preferred format, and it uses that. But the next step is to provide a setting per file type, so that you can really specify what you want to be for every type of file that you upload.
\n\n\n\nThe settings are really fine grained in that regard. I hope them to be fine grained. There are also more settings, for example, for thumbnail generation. You can choose whether the thumbnail should be generated on the server, or in the browser as well, which is the default.
\n\n\n\nAnd the third option is to have the client side thumbnail generation, but make it smarter. So for example, if you have a photo of a person somewhere, right now WordPress just crops like these 150 by 150 thumbnails from the center of the image. But with the smart option, it will focus on the person’s face to be in the center, just so much more useful.
\n\n\n\n[00:15:50] Nathan Wrigley: Wait, it makes a decision about what to crop, based upon the content of the picture. So it’s intelligent enough to know that there’s an object over here which is of significance, crop around that. That’s great.
\n\n\n\nHow would that work for other things? This is going to go off in a strange direction. Let’s say I had a, I don’t know, a cat or something like that in the picture, but there was nothing else. There was just this singular cat, and it was top right. Is it able to intuit that there’s an object in this picture which needs focus?
\n\n\n\n[00:16:16] Pascal Birchler: Yeah, so the image library that I’m using tries to detect the most prominent object in a photo. So there could be an animal, or something else. Of course it’s not perfect when it’s, I don’t know, a photo of like a group of people or something, but it’s better than nothing.
\n\n\n\n[00:16:30] Nathan Wrigley: Yeah, it has to make a decision about which person is more important in that picture. But again, just to emphasise, if you’re listening to this, we’re not talking about this data leaving your computer, getting crunched on somebody else’s machine, and then being sent back. This is all happening inside the browser, right before your eyes, or not before your eyes. It’s really just happening, and the result comes out before your eyes.
\n\n\n\nYou may not know the answer to this, I hope that you do. But, why do browsers have all of this technology baked into them? What’s the reason for that? I mean, I could guess what some of the reasons would be, but I’m interested to know if you’ve got more concrete data on that. Why would a browser ship with all of these image conversion, formatting options, all the other things you’ve described?
\n\n\n\n[00:17:14] Pascal Birchler: Well, as I said, the browser does have some image formatting or conversion options, but they’re limited. That’s why I’m able to use external libraries, through Web Assembly. And the reason that Web Assembly is a thing is it just, it makes the web so much more powerful. It allows things like Photoshop to run on the web, which previously wasn’t possible. I think for the web to still matter in years to come, browsers and websites and web technologies need to evolve, support use cases like that.
\n\n\n\n[00:17:41] Nathan Wrigley: Yeah, I have this intuition, I could be wrong. But I have this intuition that in a decade from now, more and more of the things that I’m still holding out on my computer at home, will have gone over to the browser. And it feels like video and images are still in the domain of the desktop computer often, just because of, well, the amount of data that has to fly around for a start.
\n\n\n\nBut also, if you’ve got an hour long video and you’re trying to edit little bits, it does seem that online solutions don’t quite make the grade yet boy, it’s changing quickly. And if we stare into our crystal ball, a year into the future, two years, five years, I feel that a lot of this will have been taken over by online tools.
\n\n\n\nSo we talked about the fact that you can upload an image, but it goes a lot further than that, because you can take a bunch of images. Now I don’t know how much you’ve battle tested this, whether or not you’ve put in 500, 1,000, 10,000 images. But in the example you used, I think you put three images in, and it did the same thing.
\n\n\n\nSo if you were a photographer, or you had a post that was heavy with images, this can all be done. You don’t have to do one at a time, wait for it to happen. It’ll just put them all into a queue, I’m guessing, and tackle them one at a time.
\n\n\n\n[00:18:43] Pascal Birchler: That’s exactly right. Yeah, I have this sort of queuing system that I built. It can do multiple images at a time, or only one. That depends on a lot of factors. For example, like how many CPU cores that you have on your machine.
\n\n\n\nThe good thing is that everything happens in the background in so-called Web Workers. And these are separate threads from the main website, which means even if you throw more than one image at it, it will be separate from the main thread, so you’re not blocked from writing any more content. I don’t have 10,000 images on my computer to test it with, but maybe I should.
\n\n\n\n[00:19:15] Nathan Wrigley: But it will cue them, and so we’re expecting it to work in the normal way. But certainly for a normal amount of images, it’s going to handle it correctly. Let’s say though, that I did throw 100 images at it, which is going to consume a little bit of time. I’m imagining, you know, there would be some human noticeable amount of time for that to happen.
\n\n\n\nAnd then I was to stray away from that post. Close it down, for example, or go to a different screen inside a WordPress. Does the browser continue that operation? What is the connection? How is it bound? Does the post need to be open for all of this to happen? And also, what about just failure? If something fails to happen, do we get a notification to say, whoops, it didn’t do what it was anticipating to do?
\n\n\n\n[00:19:55] Pascal Birchler: So yes, you definitely need to stay in the editor while the upload is in progress. There will be a warning if you try to navigate away. Of course, if this were like a single page application, where you’re not actually like changing origins, going to another website that could continue to upload. But for the upload to finish, you need to stay in the editor.
\n\n\n\nIf an upload errors, there will be notifications of course. Thanks to this queuing system, it’s even possible to change your mind and cancel uploads, if you prefer. For example, if you notice, oh dang, I uploaded wrong image. You don’t have to wait for the upload to finish to fix that mistake, so you can just cancel it.
\n\n\n\n[00:20:29] Nathan Wrigley: Yeah, that’s great. Now, it’s not just images though, it will handle a whole load of other things. And there’s a couple that you demonstrate. The first one is something which is, obviously something that irritates you a little bit. Animated GIFs or GIFs, however you wish to pronounce them. You’d rather that they were made into videos, and so it will do that as well.
\n\n\n\nIf you were to throw an animated GIF into it, it will recycle that as an actual image, with a play and stop button, so that you’ve got some agency about what’s actually happening on the screen there. Again, so that’s presumably just for GIFs. I can’t think of any other image format off the top of my head, which has that animation possibility. But that will create a video of the same dimensions or, what’s it doing there?
\n\n\n\n[00:21:11] Pascal Birchler: So yeah, animated GIFs or GIFs are painful. WebP also supports animation, but it’s not that common. But for animated GIFs, they’re really bad for, not just performance, but also user experience, because you can’t stop them. They just autoplay, they’re super heavy in file size usually. And if you, for example, prefer reduced motion, which is like a setting in most operating systems and browsers. A GIF won’t stop. But a video can be stopped, but it can also be preloaded, can have a poster image. So it’s just way better from a user experience.
\n\n\n\nAnd the plugin converts GIF or GIF to a video with the same size. Creates a poster image as well. So if the video is stopped, or still being loaded, you will see a preview image as well. You can have either the controls to play, pause, or it just loops and autoplays, like a GIF. You don’t see the difference.
\n\n\n\n[00:21:59] Nathan Wrigley: It’s what we need. Agency over animated GIFs, that’s for sure. And it just all happens seamlessly. But again, another jaw off the floor moment was when I saw that you were creating video content inside the post editor. So, you know, imagine, dear listener, that you are in a post, you’ve clicked add new post, and there you are.
\n\n\n\nShoot video from the webcam, or I’m guessing any camera that might be attached to the machine. Shoot it, save it into the media library inside the post. As if that wasn’t enough, also transcribe it in real time. Now, I don’t know if that transcription gets burned onto the video, or if it’s just something that’s happening as you are watching it.
\n\n\n\nBut that’s truly remarkable as well. And it leads me to all sorts of thoughts about being able to, I don’t know, communicate with other people, with synchronous video, a bit like we have with Zoom, or something like that, inside of a post. I’m not entirely sure why you would wish to do that, but those kind of possibilities becoming available. How did you do that? How does that work?
\n\n\n\n[00:23:05] Pascal Birchler: You bring something interesting up, because there’s like this collaboration feature being worked on in the block editor. So just imagine having a video call, and maybe saving that video afterwards, who knows?
\n\n\n\nSo for this particular feature I’m again, using the powers of Web Assembly to use the FFmpeg video library in the browser. So FFmpeg is a really powerful tool set. It can do video conversion, all sort of things. And I use that in a browser to basically record the video, or take the recorded video and convert it to like a MP4, whatever is a good format for you.
\n\n\n\nAnd for the subtitles, I’m using a different solution, which is based on an open source machine learning models, that do transcription, like speech to text. And that generates a vtt captions file. Similar to srt, it’s a separate file, it’s not burned into the video. And you can use other tools to then edit the captions, or you could even build a caption editor directly in WordPress.
\n\n\n\n[00:24:04] Nathan Wrigley: Most video solutions allow you to upload and combine the two, don’t they? So it’s got timestamping in, so it knows when a particular word is about to appear on the screen. And so it can handle all of that. But it creates that file on the fly. So it not only creates the video file, stores that into the media library, but if you have the option set for the vtt file, it will also save that. And presumably, because of the time that they were saved, there’s a very high probability they’ll end up right next to each other in the media library. So you could associate the two.
\n\n\n\nThat is truly impressive. I can only imagine what could be possible with that. Because all you are doing is showing that it can be done, and it can be saved right there. But yeah, I kind of feel that once that gets out into the wild, other developers will have intuitions as to what to do with that, aside from you, and may well wish to do something.
\n\n\n\nBut you’re right, you know, can you imagine a scenario where, I don’t know, a graphic designer wants to talk to another graphic designer about a particular post, or a particular page that they’re working on and, well, let’s just hop in, and actually work on it together whilst we’re in the page. We don’t need another third party solution. I don’t know, maybe that’s a bit extreme. But absolutely fascinating how you’ve managed to pull all of this off.
\n\n\n\nYou mentioned the libraries that you were using there to do the video transcoding. Again, is all of that bundled in with the plugin, or is any of this going out of our computer, out of our browser somewhere, and getting converted, and then being sent back? Or is it all happening on our machine?
\n\n\n\n[00:25:27] Pascal Birchler: It’s all happening on your machine. I know it’s sometimes crazy to believe, but yeah.
\n\n\n\n[00:25:32] Nathan Wrigley: I mean, really, truly crazy. One thing that you own that I don’t own is you have an iPhone, which it turns out also has an unusual, well not unusual because there’s a lot of iPhones out there. But it’s not a web friendly image format. I didn’t even know what it was called until you showed it on the screen, it’s HEIC or HEIF. And it’s simply for Apple devices.
\n\n\n\nSo I’m guessing if you’ve got a Mac or an iPhone, it will show it just fine. But if you’re trying to upload that to the media library, you’re going to have a problem. So conversion has to happen there. And you’ve got a nice, another nice little option there. If you throw that in, that will also get converted, again to your preferred one. So it could be, I don’t know, AVIF or WebP, whatever you’d like.
\n\n\n\n[00:26:13] Pascal Birchler: Yeah. So it’s a super annoying format to use on the web. Right now, it will convert to WebP or AVIF, whatever you have set. The file format itself also supports like multiple frames, because on iPhone, you have this feature called live photos, where the photo is sort of like a video. So you could technically even convert this image to a video when you upload it. So you have this live photo effect also on the web.
\n\n\n\n[00:26:36] Nathan Wrigley: But it’ll do all of that out of the box. So all of that is absolutely fascinating, and we’ll get to something else that you showed in a slightly different video in a moment. The purpose of this, obviously, you’re scratching your own itch, you’ve done something which will definitely be helpful in the future. It does strike me that a lot of this is definitely within the scope of being put into core.
\n\n\n\nNow, I know that an awful lot of stuff comes through the news outlets each and every week about amazing WordPress products, and some of it clearly is really out of the scope of core. But do you have an intuition that some of this really could be baked into core, would be useful in core? Is that something you are going to be trying to push for in 2024?
\n\n\n\n[00:27:19] Pascal Birchler: Well based on the reactions of people to the demos I’ve shared, there’s definitely interest. Seems to be useful for many people. Be that the HEIC conversion or the thumbnail generation. So I definitely see potential for this to be in core, and it’s something that I want to strive for in the next year. But it will be definitely limited in scope. Like, you won’t see fancy video recording or something in core, I would say. So I would want to start small, focus on like an M.V.P. solution, and bring that into core and then we can go from there.
\n\n\n\n[00:27:51] Nathan Wrigley: Yeah. That’ll be an interesting thing to see. One last thing, just before we move on to your upload an image with your friend idea. Another thing which you do is, and this is curious because we had a chat about this before we clicked record. If you upload an image and that image is going to take a few moments, an opaque, hazy version of the image is shown. And it almost looks like you’re squinting your eye or something, you know, it’s gone a little bit blurred.
\n\n\n\nBut the technical side of how you’ve done that is really interesting, because I was anticipating it was just another image, but it’s not, there’s some really interesting work going in the background there, and gradients and CSS. Just explain what’s going on whilst we have the image load. You show us something, which kind of looks like a faded out version of the image. What’s happening?
\n\n\n\n[00:28:33] Pascal Birchler: So the itch that I wanted to scratch there, is that the experience when you have to wait for images to load is really not great. Let’s say if you’re on a 3G connection on a train, or something. So what I wanted to do is have like a blurred version of the image showing. So as soon as you open the page you immediately see something. You know, oh, there’s an image that might be loaded here, and it looks interesting.
\n\n\n\nAnd what I’m using for that is a technology, or an algorithm called BlurHash, which generates these blurry placeholders. And usually to display that placeholder on the website, you would need JavaScript. But I’m converting this blurriness to simple CSS gradients instead. So that when you load the page, you’re not seeing another image while the main image is loaded, it’s just all CSS gradients.
\n\n\n\n[00:29:18] Nathan Wrigley: So no JavaScript in sight, it’s just CSS, which obviously has its benefits. So upon successful completion of that image, what are you doing with the CSS that you’ve created there? Where is that data going when it’s no longer needed? Do you just expunge it and get rid of it?
\n\n\n\n[00:29:33] Pascal Birchler: Well, you will still need it for like the next page load, right? So it’s always there, it’s always in the database. And it’s super small, like even for a larger image. The amount of gradients is not that big, so it doesn’t really impact performance.
\n\n\n\n[00:29:47] Nathan Wrigley: Yeah it’s a really nice experience, because it just gives you, well, you’ve all been there where an image hasn’t even begun to load, and you get all this cumulative layout shift where things are being pushed around, and buttons go further down and everything moves. It kind of gets rid of that, because right away you get this block, which is going to be the same size and shape as the image, which will eventually load.
\n\n\n\nI think in most cases these days, certainly in the part of the world where I live, we’re really not faced with those problems too much these days. But as you said, if you’re in a place where there’s a slower network or a, let’s say a 3G network or something like that, then having that as an option is great. So yeah, fascinating solution to that problem, I really like that.
\n\n\n\nNow, I think you probably got a little bit of interest, and I don’t know if the second Twitter video came along after the first one that I saw. So we’ve just discussed what I believe is probably the first one, and we’ll discuss the second one. And I’m hoping, Pascal, in the days and weeks to come, we’ve got Christmas in the way, I realise that. But in the days and weeks to come we’re going to see many more such videos.
\n\n\n\nYou’ve got this really interesting idea of being able to upload images into a post, with a link, or a QR code, which I guess is a link of a different kind. But you could send it to a friend, who could then upload an image into a post, without being logged into the WordPress website. Where did that need arise? What was the scenario that you were thinking, okay, I need people to upload images into my posts, which they don’t have access to edit, and so on? What’s going on there? It’s fascinating.
\n\n\n\n[00:31:13] Pascal Birchler: I have to admit, I did not come up with this idea actually. So after I published the first demo on Twitter, John Blackburn, I actually opened an issue on GitHub and he was like, hey, you know, on apps like eBay or online banking apps, for example. There’s the option to upload your receipts or something from your phone. So why not make that possible in WordPress? And I was like, oh, that’s interesting. So I built it.
\n\n\n\nIt’s really cool because, I think the scenario is, you’re editing a blog post, you want to add this nice picture and you realise, oh, it’s on the phone. Maybe it’s on your friend’s phone, or like colleague’s phone. So you can scan the QR code, or send the link for that code to someone else. And then they’re able to upload the image to WordPress. And after that is done, and you’re still in the editor, so once they’re done uploading the image, you’ll immediately see the image in your editor, you can continue editing.
\n\n\n\n[00:32:04] Nathan Wrigley: So you wouldn’t need to refresh that post and come back to it, it would just appear. So let’s say, for example, that I send you that link, and I’ve got my post, it’s half completed, but I just know that I need that image to finish it off. And I know that you, Pascal, have got your hands on it. I could send you the link. You click on the link, select the image in question, and there it is, right inside my post, immediately without a need for a refresh or anything.
\n\n\n\nThat’s so great. That’s just such a curious thing. But now I get the point, and I guess the idea of being able to send it to somebody else is quite interesting. But the idea, certainly for me, you are right, there’s a lot which is held on my phone, there’s a lot which is held on other computers. I have a detachable hard disc over there, and quite often the computer that it’s attached to is, you know, in no way connected to this one. So being able to send myself another link over there, that’s really curious.
\n\n\n\nIt feels to me, Pascal, as if you are just getting your feet wet here. You’ve just got yourself all excited about images and what you can do with them inside of WordPress. So that’s the next question. Do you have any intuition as to what’s coming next? What fun projects you might work on.
\n\n\n\n[00:33:09] Pascal Birchler: Well, you know, just talking about this with you, gives me a lot of ideas. And sharing these demos with people also sparks ideas in them. And you mentioned that holidays are coming up, so maybe, I don’t know, over the holidays I’ll build something new. We’ll see.
\n\n\n\n[00:33:22] Nathan Wrigley: Well, I would very much like to see the outcome of your endeavors. Yeah, I’ve definitely got a few ideas of what I would like. For example, being able to record a podcast directly inside the editor. I know that, obviously, video and audio are very similar, it may well already be possible with everything that you’ve done.
\n\n\n\nBut the ability to do things like that inside the post editor, and not have to save it elsewhere, would be kind of interesting. You know, what we’re doing right now, we’re using a third party SaaS app to record this. I can’t see any reason why all of this couldn’t potentially happen inside the block editor as well.
\n\n\n\nAnyway, exciting times. And Pascal, I do thank you for piquing my curiosity. It really was quite a moment when I saw that video.
\n\n\n\nIf anybody wants to contact you, if anybody has been intrigued by what you’ve said, and they want to reach out, where are the best places? We know that you’re on Twitter, but tell us what your handle is, and where else we can find you.
\n\n\n\n[00:34:10] Pascal Birchler: So my Twitter handle, or WordPress.org, everywhere else is swissspidy with three S’s in the middle. That’s the best place to reach me.
\n\n\n\n[00:34:19] Nathan Wrigley: Alright. Well, thank you so much. And Pascal, I really appreciate you coming on the podcast and chatting to us today. Thank you so much.
\n\n\n\n[00:34:25] Pascal Birchler: Thanks for having me.
\nOn the podcast today we have Pascal Birchler.
\n\n\n\nPascal is a long-standing WordPress community member and Core committer, with a focus on internationalisation, WP-CLI, and performance.
\n\n\n\nHe’s been working on a project for the past six months to enhance the media capabilities of the WordPress block editor. His work includes client-side image optimisation, image compression, video enhancements, and speech-to-text features, such as subtitle generation. It’s unlike anything that I’ve ever seen. You upload media into the block editor, and it’s manipulated right there, inside the editor, by the browser, not by some remote server.
\n\n\n\nThis is all achieved by harnessing the power of WebAssembly, and we discover what Pascal has managed to achieve thus far, and how he thinks that there’s going to be so much more to come.
\n\n\n\nWe talk about how you can change images from legacy formats like jpg and gif, into other, more modern formats such as WebP and Avif. Pascal explains how this is actually achieved, and why the new formats are desirable. It’s all about reducing file sizes, server resource consumption, and the speed boost your site will gain as a result.
\n\n\n\nWe also get into the conversion of animated Gifs into videos, and creating videos with transcripts on-the-fly, and remember, this is all done in the block editor with the browser itself as the workhorse.
\n\n\n\nPascal seems to be onto something here, and it’s really compelling listening to him argue that something like his plugin might be worthy of inclusion into WordPress Core at some point.
\n\n\n\nHe explains some other projects which he’s been working on, inspired by the high volume of feedback he received after releasing his plugin.
\n\n\n\nIf you’re interested in pushing the boundaries of user experience, performance optimisation, and compliance with evolving web standards, this episode is for you.
\n\n\n\nIf you’re obsessed with Sonos like I am, a nice MacOS utility is the Menu Bar Controller. Hat tip to Mike Tatum, who happened to be the gentleman who convinced my parents it was okay for me to drop out of college and move to San Francisco to take a job at CNET. Mike’s now at Sonos and in October arranged for some top execs at Automattic to go to Santa Barbara to meet with their peers at Sonos, and Patrick Spence and I did a joint CEO town hall that was broadcast to both of our companies. It was I think fascinating for both sides because of a shared passion for craft, design, culture, and execution, but our companies are in no way competitive, so it allowed for a lot of transparency. I learned a ton, and I think that kind of sharing is what increases the mimetic evolutionary speed of companies.
\n\n\n\nAtoms are hard! I think I’ll stick mostly to bits.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 10 Jan 2024 01:50:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"Do The Woo Community: Do the Woo is a Sponsor and Media Partner for WordCamp Asia 2024\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78784\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://dothewoo.io/sponsor-and-media-partner-wordcamp-asia-2024/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:402:\"We are returning to WordCamp Asia again, and proud to be a Media Partner again as well as a sponsor for the event.
\n>> The post Do the Woo is a Sponsor and Media Partner for WordCamp Asia 2024 appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 09 Jan 2024 08:09:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"WordPress.org blog: WP Briefing: Episode 70: A Look Ahead at WordPress in 2024\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16677\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wordpress.org/news/2024/01/episode-70-a-look-ahead-at-wordpress-in-2024/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8348:\"Curious about WordPress’s big-picture items for 2024? Phase 3, Data Liberation, new meetups, and more, get the spotlight in this episode. Join Executive Director Josepha Haden Chomphosy for all this, plus a small list of big things coming up in the next two weeks.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Hello, my dears, and welcome to 2024. I hope you’ve had a lovely break. At the top of the year, I like to look around and gather the projects that the community is interested in. We can’t always commit to everything, and sometimes even the things we plan to do can’t make it across the finish line. In the next few weeks, I’ll be publishing kind of the big picture goals for the year, but I wanted to share a little bit about what I’ve collected so far.
\n\n\n\n[00:01:05] Josepha: Firstly, we’ve got Phase 3. This has been called a few things over the years: collaborative editing, multiplayer, co-editing. But whatever it’s been called, the biggest changes to writing and design workflows are likely to happen in this phase. A redesigned workflow can be a bit of a shock. But fortunately, we already have a prototype out there.
\n\n\n\nI’ll include a link to some resources in the show notes, or of course, you can always stop by make.WordPress.org/core for some insights. But I would encourage you to, at the very least, get your hands on that prototype to see what it looks like is coming in Phase 3 so that you can be aware and provide your feedback.
\n\n\n\nThe next thing on our list is Data Liberation. This is a new-to-us project that was introduced at State of the Word. Fortunately, though, it’s not a new concept overall. Data Liberation is actually one of the earliest ideas that sold me on WordPress. The idea that you could set up a site for a client, or yourself, and that hard work wasn’t lost if something went wrong, was really important to me. It’s been a long time since we put any effort into our importers and exporters, and I think this will be a good focus for the year.
\n\n\n\n[00:02:14] Josepha: The next thing that I’ve picked up, kind of a list of three things, but there are three mid-sized areas that I want us to pay attention to this year: plugins, old tickets, and new meetups.
\n\n\n\nPlugins, because they really have turned a corner on where they ended 2023. A lot of work has been done to make sure that they’ve streamlined some efforts, gotten some better onboarding for folks as they’re going in, and we could really use a hand to keep that momentum going.
\n\n\n\nOld tickets, because it’s something that we hope for year after year when we’re talking to people about what they want in new releases. So often, part of what they say is some way to work through all of these old things that have been around forever, some with patches. And why not, after all?
\n\n\n\nAnd then new meetups, because I really still think that meetups are the best intro to WordPress. No matter whether you’re wanting to become a developer eventually or, like, the community-building aspect is the thing that hooks you forever. Meetups are the place to encourage those and discover those.
\n\n\n\n[00:03:20] Josepha: The next thing on my list is also two things. It’s two things, but kind of a guess at the moment. There are two summit items that I want us to try to consider this year.
\n\n\n\nSo the first one is contributor recognition. Acknowledgment and recognition, I think, are two different things, and there was an entire series of sessions at the summit where we talked about it. And so I think that it’s worth us digging in on that.
\n\n\n\nThe other thing from the summit that I would really like us to all kind of dig in on is accessibility, how we do it, how we confirm it, what we think we should do versus what we actually do, and see what we can move on the needle there.
\n\n\n\nAnd the last thing is sort of a personal wish. I think it’s about time that we take a look at the way that we kind of manage ourselves as a project, the way that we do our meetings and report on our successes, things like that. And I realize that this is a big thing, and it might be a little bit scary. But, I mean, we’ve been doing this for a really long time, and it’s probably as good a time as any, frankly, to look at what we’re doing by habit or tradition and see if it still suits us.
\n\n\n\nSo, that’s my back of the napkin set of notes so far. Keep an eye out in the next couple of weeks for the annual Big Picture post so you can get some context, notes, and discussion opportunities. And, of course, anything that has shown up that’s a bit bigger, a bit more final will be in there as well.
\n\n\n\nBut first, our small list of big things.
\n\n\n\n[00:04:52] (Music interlude)
\n\n\n\n[00:05:00] Josepha: Firstly, State of the Word had nearly 200 questions submitted, and Matt has been answering the overflow on make.WordPress.org/project. So, I’ll include a link, but head on over there to that post if you would like to catch up on those.
\n\n\n\nAnd then the second item, and last item, is that you’ve got a few more days left to give us feedback on WordPress meetups in 2023, and give us an idea of what we can do to improve those. I believe those close on January 14th. I really love my local meetup, and I hope that we can get some of that same sort of feeling going in all of yours, too.
\n\n\n\n[00:05:33] Josepha: And that, my friends, is your small list of big things. Don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there’s a new episode. If you liked what you heard today, share it with a fellow WordPresser, or if you had questions about what you heard, you can share those with me at wpbriefing@WordPress.org.
\n\n\n\nI’m your host, Josepha Haden Chomphosy. Thanks again for tuning in for the WordPress Briefing, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:06:02] (Music outro)
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 08 Jan 2024 13:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:153:\"Gutenberg Times: Gutenberg Changelog #94 – State of the Word, Gutenberg 17.2, 17.3 and 17.4, WordPress 6.5, Migrating from Classic Theme to Block Theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://gutenbergtimes.com/?post_type=podcast&p=26968\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:163:\"https://gutenbergtimes.com/podcast/gutenberg-changelog-94-state-of-the-word-gutenberg-17-2-17-3-and-17-4-wordpress-6-5-migrating-from-classic-theme-to-block-theme/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:61310:\"In this episode, Sarah Norris and Birgit discuss State of the Word, Gutenberg 17.2, 17.3 and 17.4. They take a sneak peek at the WordPress 6.5 roadmap, and they discuss steps on migrating from a classic theme to a block theme.
\n\n\n\n\n\n\n\nShow Notes
\n\n\n\nJavaScript Developer 6.4 editor tech co-lead
\n\n\n\nStay in Touch
\n\n\n\nTranscript
\n\n\n\nBirgit Pauli-Haack: Hello, and welcome to our 94th episode of the Gutenberg Changelog Podcast and a happy New Year, dear listeners. I hope you all had a great time off during the holidays and a great start to the year 2024. I like the year 2024. 2023 wasn’t so good, but 2024 was good. In today’s episode, we will talk about State of the Word, Gutenberg 17.2, 3 and 4, and we take a sneak peek at the 6.5 WordPress roadmap, and we also discuss steps on migrating from a classic theme to a block theme.
\n\n\n\nI’m your host, Birgit Pauli-Haack, curator at the Gutenberg Times and a full-time core contributor for WordPress open source project sponsored by Automattic’s Five for the Future program. And I’m thrilled to have as a guest today, Sarah Norris, JavaScript developer, theme builder and core contributor and editor core tech lead for WordPress 6.4, also sponsored by Automattic. Happy New Year to you too, Sarah. How are you today?
\n\n\n\nSarah Norris: Happy New Year. I’m really good, thank you. I’m very ready to talk about all the work that’s been happening over the last few weeks, especially as we lead up to a fast approaching 6.5.
\n\n\n\nBirgit Pauli-Haack: Yes, it’s fast approaching and we are going to talk about that. But yeah, catching up on everything. The year-end vacation kind of always puts a little bit of a dent in being up-to-date with Gutenberg and the block editor and this is your chance to catch up on it. We have a big show, so it might go over the hour limit, but I hope we can get it brief.
\n\n\n\nSo State of the Word, there was a lot of celebration around 2023 in the State of the Word and brought it to the WordPress community. And if you haven’t watched the keynote yet, there is a YouTube video. There’s also a YouTube video about the Q&A afterwards and I’ll share the link to the Weekend Edition 228. That’s the last one on Good Work Times where I shared a ton of links, so this will be in the show notes, but it was the first State of the Word outside of US, a huge success with livestream on multiple channels. And is there anything that stood out for you, Sarah?
\n\n\n\nSarah Norris: Yes. Yeah, so much fun. It was such a good State of the Word. So it was discussed how many… the number of WordCamps that’s increased. So I think we’ve doubled the number of WordCamps and Meetups, and that has to come in more and more countries as well. I attended the first UK WordCamp, so the first UK WordCamp since the pandemic last September. It was so much fun. It was held in Whitley Bay, which is in the northeast of England, and I’d just love for everyone in the WordPress community to experience this, and as the number of meets and word camps grow, I hope everyone is able to attend. It’s almost like… unable to put it into words how good it is attending local events and being part of your local community as well.
\n\n\n\nBirgit Pauli-Haack: Yeah, I agree with that. Yeah, it’s the live, the person-to-person interaction. It’s kind of how relationships are built and it’s such a richer experience than just doing it online. And I just happened to think of it, but there is a new page on wordpress.org, it’s called Events, it’s wordpress.org/events and it has a big map with all the events happening and a list and you can filter down to location or what type of events. And so you learn about all the local Meetups, so if there isn’t one near you, there is the chance that you could actually start one. Yeah, it’s a lot of work and it’s a ton of fun. For about four years, I organized the meetup in Florida when I was still living there and I had so much fun with the local community, and I was always up-to-date on WordPress because I had to do a little intro every time and… Great speakers. So it’s a ton of fun.
\n\n\n\nSo if you want to do that, the make.community… No, make.wordpress.org/community, that’s a handbook for meetup organizers and work group organizers, and out of the small cell of a local meetup will grow the bigger one. That’s the WordCamp. Yeah, thank you for letting me rant on about this. I’m by heart a community organizer, so I’m kind of really happy about… That those come back. Although we doubled the number of WordCamps, there is still a lot of work to be done to get on the level of pre-pandemic. So 2018 and ’19, we had about 140 WordCamps around the world, which is double the number that we had last year. So we are on the way because it’s going to be maybe a hockey stick growth rate there with all the local Meetups coming back. All right, so back to State of the Word, what else stood out for you?
\n\n\n\nSarah Norris: I’d also like to give Playground a shout-out. It’s become one of my absolute favorite tools to use when developing and testing for Gutenberg and also when building themes and plugins. I’m just so excited for what the future holds for this tool and just well done to everyone involved in building such an amazing tool as well. Yeah, I’d recommend everyone check it out if you haven’t already.
\n\n\n\nBirgit Pauli-Haack: Yeah, check it out. WordPress Playground. It’s actually WordPress in a browser. You don’t need a local server and you can have a plugin, can use it for demos as can themes, but it’s also… Some of the tutorial educational content will have some Playground links as well so you can see how it actually works and… Without having you setting up all your local development and all that, so it’s really cool. Yeah. I think they’re also working on a VS Code extension, so you get a little WordPress button in your left taskbar and then you click on it, and then from the directory you can call up the Playground instance. So that would be really cool. It’s still in the works, but I think that’s the goal for it, yeah. Anything else that stood out from State of the Word?
\n\n\n\nSarah Norris: Yes. Yeah, I’m also excited about the admin redesign, so yeah, I’m just looking forward to… I think this is another maybe long anticipated feature. Yeah, like anything, any big redesign of any long-standing tool is always exciting and I think this is… Yeah, it’s just going to be incredible.
\n\n\n\nBirgit Pauli-Haack: Yeah, it is. Yeah. And that’s the unification of all the list views on… List of posts, list of pages, list of categories that I haven’t tackled yet, but the list of templates. So it’s all a unified kind of system. So I really excited about that too. And it looks so modern. It looks so… Like, “Oh, this is from the 21st century.” Yeah.
\n\n\n\nSarah Norris: Exactly.
\n\n\n\nBirgit Pauli-Haack: Well, what stood out for me was kind of a little bit a higher level thing from State of the Word. There was a data liberation project that Matt Mullenweg announced. That’s a community initiative to bring all the tools that agencies and hosting companies put together for migration in and out of WordPress. So in and out of… From Wix to WordPress, from Squarespace to WordPress, from Google Docs to WordPress and all that. And I think that is a really good step forward to the open web, that a user or a site owner can take a hold of their own data and they’re not beholden to a centralized kind of system that doesn’t let you get out of it once you have signed up for it because the switching costs are too high or not possible at all and you have to start all over again.
\n\n\n\nSo I think that is a really good initiative. We’ll see how it plays out in the next year of course, but there are some… So I’ll share a few links in the show notes about that. And the other thing that stood out for me was everybody was waiting for the date of WordCamp US, which is September 20… No, what is it?
\n\n\n\nSarah Norris: September 17th to September 20th. Yeah, September next… This year.
\n\n\n\nBirgit Pauli-Haack: September was good. So September 17th through the 20th, and if you count the dates right, there are two days… Contributor day and two-day conference. So this is kind of a new format and I’m excited to see that and how that plays out. So that’s it from the State of the Word. Anything else?
\n\n\n\nSarah Norris: No, I think that’s it from the State of the Word.
\n\n\n\nBirgit Pauli-Haack: Yeah. Of course, we also have a lot of recap posts if you’re not into video watching, it’s also on the link then.
\n\n\n\nSo next up, WordPress 6.5, that’s the release coming now and it’s fast approaching. We have a schedule, so Beta 1 is scheduled for February 13th, 2024. That is feature freeze kind of thing. And I did a calculation, 38 days from today, and today’s January 5th. And the last Gutenberg release that’s going to make it new, feature-wise, will be 17.7, which is actually only three Gutenberg releases away. It’s fast approaching. After Beta 1 comes weekly Beta 2 and Beta 3 with bug fixes after testing and then brings us to release candidate one for March 5th, though in exactly two months, March 5th, 2024. That is the deadline for string freeze and also for developer notes to be published and collected in the field guide that accompanies every major release release candidate is actually right before WordCamp Asia, which takes place on March 7th through ninth.
\n\n\n\nSo this is great timing because everybody who wants to go to WordCamp Asia already has a release candidate. Whoever is on the release squad can… Oh, release candidate’s done. So the major work for the release is probably done by that time and that’s a good thing. You don’t want to be on a WordCamp and have to deal with releases at all. Yeah. Final release is scheduled for March 26th, 2024. So here is your schedule for that. That seems to be a pretty good schedule in terms of spacing out the betas and release candidate, that’s some kind of tradition with WordPress release. You were on 6.4. How is the weekly kind of updates and what goes into next beta and all that? Is it particularly important?
\n\n\n\nSarah Norris: Yeah, yeah, the dates are important. It’s almost like time… If you didn’t think time went quick enough already, being part of a WordPress release. Yeah, I think one of my ways to deal with the release dates is usually I have a deadline for myself that’s just ahead of the important dates. So usually the Friday before a date, but also that reduces the time, because I don’t know if I’m stressing myself out more. No, it’s all good.
\n\n\n\nBirgit Pauli-Haack: No, it’s all good. I think you need the Monday to do all the backboards and then… The beta releases and release candidates are all on Tuesdays because Wednesday is too late, and if you want to move it, you could move it to Wednesdays, but you don’t want to release anything on Thursday or Friday because then the whole weekend is kind of full with anxiety and communication and feedback, kind of that.
\n\n\n\nYeah, so early December, Anne McCarthy has published the roadmap for 6.4, and it’s a very long post and we are certainly not going to… We would need to have another two-hour show to go through it in detail, but let’s look at the highlights for it.
\n\n\n\nSo it has four major topics from the editor part, that’s design tools, that’s adoption pathways, the foundational experience, which is some of the redesign, and new APIs. And I think the first three are really interesting for users and those who build interfaces for others but not… Or do site builders that are no-code. So the fonts library, we are waiting for that for quite a while now, but I think it’s coming into 6.5 eventually, right?
\n\n\n\nSarah Norris: Yes. Yeah, a long anticipated feature coming to core. Yeah, so this brings font management directly to core, allowing users to edit and remove custom fonts all within the editor. It has been available from Gutenberg 16.7, so there’s some underlying changes currently going on, but if you do want to test it, you can already test it using the Gutenberg plugin. But yes, a brand new redesigned API and the UI will be coming to 6.5 and yes, it’s extremely exciting. I know I’ve spoken to so many users who are looking forward to this.
\n\n\n\nBirgit Pauli-Haack: And the waiting was really hard on those users that are looking forward to them because it got pulled from the 6.4 release at pretty much last minute, like Beta 2 or something like that, because it wasn’t ready for the REST API kind of thing. What’s also coming is sync specific blocks and patterns. We have sync patterns, but it’s the partially synced patterns where you can change layout and styling of a pattern, but not the content. Right now, synced patterns are when you change something on the pattern and it changes through all the instances that it was synced, but if you have partially synced, you can kind of have a little bit… You have a granular control on what should be synced, a role of the pattern instance that it was used, and what shouldn’t, and I think that is pretty much, as of this week, ready for testing. We probably need to wait for 17.5 to get it into Gutenberg plugin, but look out for that release to start testing on this.
\n\n\n\nAnd the third item in the design tools was the section specific theme.json and Colorways. So you have multiple palettes that introduce some of the sections that you use in your theme and have a different color palette that you can style it with. I think that’s the idea there. I think the work is on the Group Block right now.
\n\n\n\nSarah Norris: Yeah, that’s right. Yeah, it’s like sectioning off the theme.json… Well, specifically at the moment just for colors, but I think this will be great. It’s kind of like a great gateway into expanding the design tools, especially for theme builders. And like you say, this is only going to apply to the Group Block, but it’s a good example, for instance, of a theme author being able to provide colors that work well together, but in a specific instance, so just for the Group Block. So you could make sure that text is accessible in that specific instance. I think it plays a really exciting future for splitting up theme.json, also because theme.json can get really long as well and that file can get big. So yeah, I think it’s heading in the right direction with this as well, to splitting it all.
\n\n\n\nBirgit Pauli-Haack: I think it also bridges the gaps between… I don’t know if that’s part of it, I need to test it out, but when you have styling for certain blocks or block styles, those don’t have the design tools to further style them later on. And I think this will be one that’s built out, not just for the group log or for a certain instance, it could help with the additional styles that theme developers offer their users to also give additional styling to them.
\n\n\n\nSarah Norris: Yeah.
\n\n\n\nBirgit Pauli-Haack: All right. And then on the roadmap, there’s a section adoption pathways, and that is to make certain features available for classic themes or make them easier to handle support for appearance tools and classic themes. So I think we have one of the change log items that we discussed further is about colors and dual tone and color settings, and then also improved pattern management for classic themes. Yeah. You wanted to say?
\n\n\n\nSarah Norris: I was just saying yes to the features that are coming up in the Gutenberg releases we’re talking about. Yeah, I noticed there was a lot in relation to the appearance but also the classic themes. Yeah.
\n\n\n\nBirgit Pauli-Haack: Yeah. And then for the foundational experience, that’s the part where the data views come in on the roadmap and they will come in for templates, template parts and patterns in the site editor. At least that’s on the roadmap, but they are also… You can already test those, but you need to open up the experiments tab for that to switch them on and then you can see them for pages, you can see them for… Patterns? No, not patterns. Patterns is the only one that doesn’t work yet, but for templates and template parts, and definitely a feature that needs feedback, that needs definitely testing and bug fixing, especially for backwards compatibility for the previous versions. That’s definitely something, if you want to dive into how things are going. The next one, it’s called robust revisions. Do you know what that is about, Sarah?
\n\n\n\nSarah Norris: So this is improving revisions but across multiple places. So I think we’ve started templates and template parts, so they’ll now show revisions alongside style revisions and you can also compare this revision side-by-side as well, which I think is brand new. And we’ve also added pagination. So yeah, a whole ton of improvements for revisions.
\n\n\n\nBirgit Pauli-Haack: Right. Yeah, definitely.
\n\n\n\nSarah Norris: We’re also integrated with the style book now. This may be coming up as well, I think in the change log, but yeah, we integrated with the style book.
\n\n\n\nBirgit Pauli-Haack: Yeah, it’s definitely something you need to test, you want to test and it’s a part of the bigger project also to have revisions for any post metadata, which hasn’t happened in WordPress before. So a lot of plugins probably will be happy to use those revisions screen when they’re ready and available for extensions as well. And then one thing I’m pretty excited about, but it has also seemed to be quite a complex issue to actually have a customizable Navigation Block for mobile headings or navigation, the little hamburger, what goes in and what goes out because it’s never going…
\n\n\n\nMost of the time it’s not one-to-one with the normal site navigation, but there will be an overlay that you can switch in and out, but it seems to be quite complicated. I looked at some of the issues, one of the issues exactly, and it has a long discussion on which way to go on it. So it’s still in the design phase, I believe. Not sure if it’s going to make it to 6.5, but maybe it’s easy once the design questions are all answered to then dive into the development. But yeah, computers are involved, so nothing is really easy. I don’t know how you see that, if you have some insight into that.
\n\n\n\nSarah Norris: I know it’s a lot. So I think on the face of it, especially because it sounds like it’s a section of the Navigation Block, but I think when if… Anyone who’s built a responsive navigation knows it’s not simple, so then as soon as you start trying to do it, to cater for so many of the people to be able to build this kind of tool. Yeah, it’s pretty complicated, but there’s some really good work going into this, some good conversations. Yeah, we’ll get there. And I think all the discussions and a long design discussion, it always ends up with a good first pass.
\n\n\n\nBirgit Pauli-Haack: And then there are three new APIs coming with different outlooks, kind of, or goals. The Interactivity API we have been talking about for about a year now, and some of the Core Blocks are using it in a private API, but for 6.5 it’s coming out of experimental and will be a public API for everybody who develops blocks to be able to use the custom fields API and binding API, I’m not quite sure how far along they are. They haven’t been released yet in a private API kind of setting. I’m not sure they’re actually going to make it. There will be underlying… They will support some of the new features but in a private API to see if they all work as they’re supposed to be working. I think that’s pretty much the high level idea about that. And then lastly there will be some… There’s PHB compatibility work.
\n\n\n\nThere’s a rollback between plugin and themes, updates with automatic updates. That has been testing also for quite a few months and is supposed to come also a better handling of plugin dependencies. And of course, the performance team does a fantastic job in going after all those performance improvements that are possible with WordPress, be it for the block editor or for PHP or for the backend as well. So those are also coming to 6.5. But as Matias and Matt said, just because we say phase two is done, doesn’t mean the work is done. So there will be UX iterations and quite a few listview background image support for Group Block, some of it is already there. Then revisiting template versus content editing modes. That kind of confuses a lot of people. “Are we adding a template or am I adding a page or what am I doing here?”
\n\n\n\nThose questions come up with testing quite a bit. And then what has been progressed quite a while is to align the edit features that are available in the site editor and the post editor. So it can be reused is pretty much… That’s one thing. And users, the advantage of it is that users don’t have to relearn what’s available in which editor because they… Maybe that’s also part of the confusion that we have on, are we editing templates or content. And so the background image support and the aligning the features are ready for testing. I think there has been some great progress made in the Gutenberg releases. And then the last point is adding box shadow component. There is box shadow support, but I think it’s only made available for theme.json level but not for user interfaces. Is that right?
\n\n\n\nSarah Norris: Yeah, that’s right. Yeah. So the work for 6.5 will expose this to the UI as well, so end users can use the box shadow component as well.
\n\n\n\nBirgit Pauli-Haack: Yeah. We’ll see how that all… And then the last thing that’s on the roadmap is that the minimum version for MySQL is going to be raised from 5.0 to 5.5.5. Very specific, but look out for it and talk to your hosting company to make sure that there is an upgrade path if you’re still on an older MySQL version. All right, so anything else about the roadmap that you want to add?
\n\n\n\nSarah Norris: No, I think that was everything. It’s a very long roadmap.
\n\n\n\nBirgit Pauli-Haack: Yeah, it’s ambitious. Yeah. Roadmaps are always quite ambitious. And then you see on Gutenberg 17.6, we’ll see how we wiggle down that ambition a little bit and kind of what’s realistic and then we’ll see what’s coming into 17.7. Yeah, that’s the last one.
\n\n\n\nAll right, so let’s go into the weeds. And we start with Gutenberg 17.2, it was released on December 6th. Wow, that’s a month ago. And there were a few things that stand out and one was the data views, and that added extra context to… So the data views are the ones that are in the admin section, the list of things, list of properties or entities or whatever you call it, I call them things.
\n\n\n\nAnd so there are quite a few features in the old admin screen that needed to come in a better way into the new admin screen. And there was kind of a filter row, the table header pagination and there’s extra… You can now scroll down and have the larger data sets. You don’t have to scroll up and down. So there’s a sticky table header that’s really good. That wasn’t available in the old one. So that’s the first… Yay.
\n\n\n\nSarah Norris: Yeah, it’s very helpful, especially when the scroll bar is really long, so you don’t have to remember… The pagination is also sticky as well.
\n\n\n\nBirgit Pauli-Haack: Oh yeah, that’s great.
\n\n\n\nSarah Norris: Same with that, you don’t have to scroll… Yeah.
\n\n\n\nBirgit Pauli-Haack: Good. And then one of the things is that drag and drop is now a little bit more refined. There was a problem to drag and drop to the beginning of a post or page and to the end, and contributors have figured out how to make this better and actually functioning. And so it kind of virtually enlarges the area. It was really irritating that you could do it in the second one. You can drag into between the first one and the second one, and then you had to move it up if you wanted to get a block to the beginning of something. So it’s really good.
\n\n\n\nSarah Norris: Yeah, yeah, it was really finicky. It was like you were fighting with the top on the blocks. It was just like it wants to drag you into this, but yeah, and now you don’t have to fight.
\n\n\n\nBirgit Pauli-Haack: Yeah, yeah. I also think that the drop zones are better marked now than at the previous versions of the block editor. So I’m really grateful for that. I just it saw, that the list view… You can also now drag into a collapse block in the list view, which is really cool. So you don’t have to just first expand a block to put additional blocks into a Group Block or a Columns Block or something like that. So you can just drag it there. Of course, the order of that, that’s random. But yeah, once you get them in, you can organize it.
\n\n\n\nSarah Norris: Yeah, that’s cool. It’s less clicks, it should be less clicks.
\n\n\n\nBirgit Pauli-Haack: Do you want to take the next one?
\n\n\n\nSarah Norris: Yeah, what else have we got? So we’ve also got the adding the toolbar for distraction free mode. So distraction free mode removes all of the UI? All the UI. So you are only looking at your content and you’re only… So you can write a long blog post hopefully. The problem with this is that it could be hard to format some of the content. So this brings in the toolbar when you mouse over the top of the editor, it’ll bring in toolbar when you’re in distraction free mode. So yeah, I recommend checking that out as well, if you haven’t checked that distraction free one.
\n\n\n\nBirgit Pauli-Haack: Yeah, I really like it. And it should be actually a default setting for the writers of the users that still like the white box from the old classic block editor that… And there is no distraction, every time you move the mouse or you move the keyword, there’s something popping up and coming down and you don’t remember where it was and what it was and it kind of totally gets you out of the flow for your writing session. So distraction free mode is a really… Extension there, and refinement definitely helps with all the writing tools in the block editor.
\n\n\n\nSo the Gallery Block now has styled scroll bars for the image captions, which is really an additional design tool because the image captions were always a little bit randomly placed on the Gallery Block. Yeah. The Interactivity API, they add… Luis Herranz, I think, did the proposal to have the Interactivity API use modals instead of scripts on the front end, which kind of makes it native JavaScript… A little bit closer to native JavaScript. So I think that’s for the developers amongst us to check out. And do you have any thoughts about that?
\n\n\n\nSarah Norris: I’m really excited about the Interactivity API going out into the world. I think it really opens up… Well, so I’m from a front-end development background, so if I wasn’t already working at Gutenberg and I was building WordPress sites, I would be really excited about this. I’d be looking forward to using it so much. Yeah, it’s basically… I don’t want to say it’s React and you can look under the hood, what it actually is, but yeah, it basically surfaces so much functionality to the WordPress front end.
\n\n\n\nBirgit Pauli-Haack: There wasn’t before.
\n\n\n\nSarah Norris: Especially you’re building custom block.
\n\n\n\nBirgit Pauli-Haack: So check it out as it’s coming to 6.5 as a public API, so let’s definitely start checking it out. There are efforts to bring introductions to the Interactivity API as well as case studies to the developer blog. I’m not quite sure they will be ready by March, but definitely subscribe to the WordPress developer blog on developer.org… wordpress.org/news. So you get notifications when there’s a new post coming up, and it actually has some great additional tutorials in there.
\n\n\n\nTalking about documentation, there was an initiative to put the fundamentals of block development, rewrite some of that or put it in a different order. So when you’re trying to learn more about block development, that the official documentation in the block editor handbook helps you get started and learn all the concepts about the file structure, registration of a block, the block wrapper, working with JavaScript and the block, what block.json can do for you, landing and first pages and the landing pages and all. And they’re all kind of getting a revamp.
\n\n\n\nAt the same time, Riad, I think it’s mainly Riad Benguella who is also writing the documentation for using Gutenberg as a framework, as a platform outside the WordPress context. It hasn’t been published yet, but if you fork the Gutenberg repo and you can start reading it. And he has some great tutorials on attributes, definitions, transform pages and blocks, and also the block supports for the framework, which is a little bit… Works a little bit differently than in the WordPress context, of course. So this is pretty new on the… And then, of course, there’s always some work to be done on the documentation with the new components, theme.json, and also template names and web pack options and all that. So this is highly technical and I would suggest you read the change log on the documentation part, if you’re interested in that and learning about new things.
\n\n\n\nAnd I think, yeah, it’s also the Create Block scaffolding. I don’t know if you have used it, Sarah, but I’m a big fan of that scaffolding tool since the beginning because I don’t have to remember all the things I need for a plugin that has a block. And you can also use an interactive template that makes the new block ready-to-use Interactivity API. And because there’s a new Store API for the Interactivity API, the Create Block scaffolding tool has already been updated to use that. So this is pretty cool.
\n\n\n\nSarah Norris: Yeah, it’s very cool.
\n\n\n\nBirgit Pauli-Haack: Very cool. And I think that’s it from Gutenberg 17.2, and we go right headfirst into 17.3. Do you want to start us off?
\n\n\n\nSarah Norris: Yeah, sure. So this also included many improvements to the revision changes like we highlighted before 6.5. So 17.3 included adding a brief summary of the revision changes to global styles. So when you view the revisions in global styles and you click on the dates, it’ll now give you a brief summary of the blocks that would change and the styles… Yeah, the blocks that would change with the style changes. Yeah, it’s very good.
\n\n\n\nBirgit Pauli-Haack: Yeah, that’s excellent. And there’s also enhancement of the social icons that is now using or adding the Gravatar service and it’s also updated. Well, sometimes I’m really cool. I’m really excited when I see consistency be applied to all the controls. So the default typography controls are now consistent across all the blocks, because different contributors write the different pieces of it, and then once you have the pieces you kind of need to see, okay, how can it make this a little bit more consistent, because then it’s easier on the eye end. You don’t have to worry, why is that distance longer than the other one, or whatever. So that is really good work. It’s God’s work, but it’s not always appreciated or seen that much. So I wanted to point that out. The same is also… Or the color dimensions of the List items Block, I think that’s new. That’s an enhancement for the List Block. So you can do the margins and the padding around list items. You can also have controls over it. It’s really cool.
\n\n\n\nSarah Norris: The preference is modal as well. It’s also had a nice update, maybe something you wouldn’t expect to see updates for, but in 17.3, it’s had an organization update with the introduction of some new panels for appearance and accessibility settings.
\n\n\n\nBirgit Pauli-Haack: Yeah, that’s really cool.
\n\n\n\nSarah Norris: Nice UX enhancement.
\n\n\n\nBirgit Pauli-Haack: Oh yeah, there were also some updates to the external… Have you ever noticed the external images panel in the Post publish sidebar?
\n\n\n\nSarah Norris: Yes. Yeah, right.
\n\n\n\nBirgit Pauli-Haack: That’s such a cool feature. So what does it do? And it kind of seems to be unnoticed, but it helps you. So if you copy paste from a different webpage or from Google Docs into your block editor canvas, out of the box or automatically, it links the images from the original space. So once you publish it and you delete the Google doc where… Yeah, all of a sudden your images go away or if you migrated from a different webpage, those external images don’t come automatically over. So each of the images in the toolbar has an upload to your own media library. But if you have 10 images, you don’t want to do it one at a time. And when you publish the post, the pre-published view has kind of thumbnails of all the images that are external and gives you a button to upload them all at once into your media library before you publish your post. I think that’s genius.
\n\n\n\nSarah Norris: It is.
\n\n\n\nBirgit Pauli-Haack: Because in the preview you see the images because the original place still has them, and all of a sudden the post goes away. We actually have met the developer blog quite a bit when… So it’s a really cool feature.
\n\n\n\nSarah Norris: Yeah, it is. It’s something that’s maybe easily forgotten about as well because like you say, if you’re copying and pasting, like a lot of people do, and then you’re just like, “Yeah, they’re showing, they’re fine,” and you can just easily forget about them. Yeah, so really good feature.
\n\n\n\nBirgit Pauli-Haack: Yeah, really good. Well done, Ella. So was that all that we had? I think there wasn’t a whole lot of… In that release, but I like all the accessibility improvements that are listed in there and the performance as well. There’s quite a few performance improvements, just because improving the code quality and having not so many calls to the same feature or same store kind of reduces that load times and the reloading of things. The experiments, I’m pretty much done with that. Are we? 17.3?
\n\n\n\nSarah Norris: I think there’s one about the update for matching the front-end layout class names between the editor and the front end. So it’s a minor change, but I think anyone who’s working with CSS, especially with WordPress, will appreciate any updates like this where the generated layout class name in the editor will now match to the front end.
\n\n\n\nBirgit Pauli-Haack: Yay.
\n\n\n\nSarah Norris: So yeah, it’s a nice little enhancement.
\n\n\n\nBirgit Pauli-Haack: So those who have dealt with that before, they need to revisit the code to not… Are there compatibility issues with that or…?
\n\n\n\nSarah Norris: No, I don’t think so. I think just going forward the class names will match. So I guess previously there would be a lot more work involved, so things should be more simple going forward. So I don’t think there’s any backwards compatibility.
\n\n\n\nBirgit Pauli-Haack: Good, good, good. Yeah, sometimes I wonder when CSS changes come. And we had a few hiccups with releases there as well. Yeah. All right, well, we are really good.
\n\n\n\nWe are through 17.3, and then this week Gutenberg 17.4 was released and also had a few highlights, and definitely the unification between site and post editor has progressed rapidly. So now we have Page Attributes panel, post taxonomies panel, the view link thing, panel. Discussion panel and feature image panels are now available also in the site editor. And that’s really good. So when you create pages and edit pages, you have all the tools that you need there.
\n\n\n\nSarah Norris: Next one, there’s so many improvements to the DataViews as well with this release. So we’ve stabilized the experience of the template screen, making it available outside the experiments flag and without the additional views options, but templates have been marked as stable. Yeah.
\n\n\n\nBirgit Pauli-Haack: Yeah. So DataViews testing is now on. If you install, you can use the plugin also on the test site or on Playground and install it there and test those template pages. So the DataViews of that is really… You can start now. For the design tools, the 17.4 has the first iteration of support background image in the Group… Well, we had background image in the Group Block before, but now it also has some tools, controls for the background size and also for tiling or repeat feature on the background image. So there’s a cover option there that means it covers the whole size of the Group Block, or you could have a contains option that it contains the aspect ratio and the Group Block can display something on top or below. But with that you can also enable the repeat feature and then it would only repeat in one dimension.
\n\n\n\nSo if the block is longer than the image, then it would repeat in the height of it and if the Group Block is wider than the background image, then it would tile it in the width of it. And then there’s a custom size. So you can say, “Okay, use that background image but only in the size of 200 width and then repeat it.” And then it gives you the repetition over the full set of the Group Block. Did I explain this right?
\n\n\n\nSarah Norris: Yeah, I think so. Yeah, expanding the background image options to include cover and contain, and then with all those options you just described. Yeah.
\n\n\n\nBirgit Pauli-Haack: And I think that’s pretty cool because then you can have some great… Well, some people say it reminds them of GeoCities, but that’s not a bad thing. Giving more controls to the user and to designers to make some interesting layouts and interesting designs for the websites.
\n\n\n\nSarah Norris: And I think anything that reminds me of GeoCities can only be a good thing. Maybe that’s just my age showing.
\n\n\n\nBirgit Pauli-Haack: Or mine. I love it. Played quite a bit of a part. The next step?
\n\n\n\nSarah Norris: We’ve also got some updates… Yeah, the global Styles revision. So we mentioned these as part of the 6.5 roadmap, but as part of 17.4 we’ve got some updates to the revisions for adding pagination and the integration into the Style Book. So global Styles revisions, you can now navigate between lots of different revisions over multiple pages of revisions and you can also see them from the Style Book itself as well. And I think that that really highlights the Style Book as such a useful tool as well, especially for styling. It’s in the name, Style Book, but especially for styling many blocks, many blocks at a different… Sorry, at the same time, rather than… I don’t know if maybe some people who are new to the editor may feel that they have to edit certain sections in different places because things feel new and they’re all over the place. If you start with the style book and you can see all the blocks in one place, I think it may help understand how they all interact with the different styling and how they interact with each other as well.
\n\n\n\nBirgit Pauli-Haack: And the Style Book is actually something that I, at the beginning of the block editor when I was trying to figure out if they… In 2018 actually, trying to figure out if we should enable the block editor for certain websites, and I was putting all the blocks in one post and then make them available for that particular site. And then we were able to look through it, how do the blocks behave? Whereas the styles need to be adjusted so they actually show the cover block and all that. And the Style Book is really replacing that totally. But it’s really helpful for… As you said, you have so many places where you can change the appearance of a block, of an element, more of a… That, or of a section, that it… Or in a post or globally on the style IU, you sometimes have a hard time figuring out, “Where did I change that or where is that red line coming from?” So the Style Book really helps you with that, to kind of track that down.
\n\n\n\nSarah Norris: We’ve also got the right-click for blocks. So yeah. So in the list view, yeah. So you can now right-click blocks in the list view, so on the left-hand side when you’re in the editor, and it’ll open the block settings panel for that block. And I think this is super cool because it makes Gutenberg feel a lot more like an app. It already feels like an app. And then we’ve got the admin redesign coming as well, and now we’re going to have right-click menus. Yeah.
\n\n\n\nBirgit Pauli-Haack: Yeah, right-click menus. Yay.
\n\n\n\nSarah Norris: Right, yeah. Right-click menus, yeah.
\n\n\n\nBirgit Pauli-Haack: Yeah. And that’s the block settings menu that will come up. That’s where you have add, before and after, copy things, create patterns. Those are the menu items that are in the block settings menu that shows up when you right-click on a block in the list view. It also makes you streamline the whole process quite a bit because you only have one list view and you don’t have to scroll up and down the canvas, you can just kind of collapse and expand on the list view and do some fine-tuning there. What’s also quite interesting here is in 17.4, all the performance enhancements or improvements that people are working on as well, most of them, again, also store subscriptions and improvements that take down the load times and the reload times. So that is definitely yay to the performance improvements. There are quite… I don’t know, I haven’t counted them, but it might be 40 or so items that are concerning the data view.
\n\n\n\nSo that experiment is really progressing quite a bit. So even if that’s the template part, you can enable the experiment and then get all the other data views as well to test things. Yeah, list view, the sync patterns is kind of working. Yeah, the documentation updates, one is that there is a new build your first block tutorial in the Getting Started section of the block editor handbook. And I’m not quite sure how finished that is, but it’s definitely something to keep an eye out for that, as it made the start of your block development experience easier than before. At least, that’s the hope. And if it doesn’t, yell at us. It’s good to get your frustrations out because that’s how we learn, we’ve got to get over it, then we need to get back to it. I did one of the courses, the data layer introduction course on learn.wordpress.org, and I’ve really found it quite interesting to go through that.
\n\n\n\nAnd I learned so much about using the components also for plugin outside the block editor context and a plugin settings page, and also how to interact with the WordPress data. And I shared my enthusiasm for that course on Twitter. And then someone who also went through that said, “Well, it’s not always quite clear which code examples need to be changed to get to the next step.” And I said, “Yeah, you’re not alone.” And I definitely have a set of notes for that, for the faculty member who created the course, but I also found it quite satisfying that I actually figured out what needs to happen. And that’s part of the learning piece, that you cement the learning so much better when you figure it out yourself than somebody spoon feeding that to you. So I’m in two minds about that. But yeah.
\n\n\n\nSarah Norris: You can fall into the trap of just copying and pasting everything, if everything is there. But I also understand examples are amazing to be in docs. So yeah, we need a good balance of just enough examples to get people to figure out the next thing on their own so they feel like they’ve learned something too.
\n\n\n\nBirgit Pauli-Haack: And I think it’s also… It might be the experience of a web developer that we had to figure out so much before on our own that it’s kind of part of the habit, too. “Yeah, it’s not working the first time.” That expectation is not there, so we always have to figure it out. Same with using different scripts and all that. As I said, computers are involved, easy is not always easy as it seems. But if you are on the developer path and you’re listening and want to learn something, they have some great courses on the learn.wordpress.org site, and they’re relatively fast to get through. Not always easy, as we said, but yeah. And speaking of which, the easy part, I think we are through with Gutenberg 17.4, right? So this time you got it, three Gutenberg releases in one hour, just about.
\n\n\n\nYeah. But I sat down on a quest during the holidays… Or between the holidays or between the year, as we say in Germany, between the year, I sat on a quest to migrate the Gutenberg Times to block theme, and I now take the opportunity to have discussed that with Sarah, who’s the professional theme developer and builder of tools, to see if I’m on the right track. So I migrated Gutenberg Times off to a different hosting to Pressable. They’re very impressive. It’s a really great hosting company, but that was the first part of it. So now I wanted to scope out what needs to change visibly, and I thought, “Okay, how can I look at 2024 without changing my front end and without getting all my site door mixed up?” And I remembered there is this site health and troubleshooting plugin from the WordPress community where you can kind of switch to a different theme for the admin, but the front end stays the same.
\n\n\n\nThe visitor sees what they see and you don’t change it. So I enabled the 2024 and the necessary plugins that I needed for content, like the plugin… The podcast plugin or the blocks that I have from a different plugin. I use the Post Grid block from the Genesis Blocks for a long time. So I needed to enable that. And then I navigated the site like I was the visitor and took notes. I have a list of to-do items, and so I get the scope for that. And now, but how do I execute that? So I was thinking, and I wanted to check with you, Sarah, if that’s the right approach or if there’s a better way to do this. So I would create a clone of my site, then install the Create Block Theme plugin, which is in the repository. Then I would activate for real the 2024 theme and then make the changes to the template, create new templates, change the styles of things, and then, what? I export the new theme and then upload it to the live site? Would that be a good place? Good way to do it?
\n\n\n\nSarah Norris: Yes, I think so. A really good shout out to the Site Health plugin as well, I never would’ve thought of it. Yeah, it’s a good starting point. Yes, I think… So you’ve already created a clone of the site, so you’ve isolated a copy of your site, you’re working on that as a separate theme and then you’re going to export that as the new theme in order to activate it on your live site. So yeah, I think that sounds like a perfect workflow. The only other option I was thinking was that… But I don’t think in your specific case… I’m not sure how much it’d help, but just to put another option out there, Create Block Theme also has the option to start from scratch, so create a blank theme rather than starting with an existing theme.
\n\n\n\nBut I definitely would recommend starting with 2024, but I know that some people, especially if you’re used to designing from scratch or a blank canvas, some people might like to start from a blank theme and you do have that option with Create Block Theme. So yeah, you’ll get completely empty templates, empty pages, but it will be a block theme starting point, so you don’t have to figure out how to actually get started.
\n\n\n\nBirgit Pauli-Haack: Oh, good. Yeah.
\n\n\n\nSarah Norris: In the theme technical terms. But yeah, you’re ready to start inserting things into the page templates and creating new menus. So yeah, probably if you’ve got an existing site. I guess it depends on the layout, and you could also choose another existing block theme that maybe matches the current classic theme more closely. But yeah, so it depends on your use case. I guess the biggest thing to decide is where your starting point is going to be, whether it’s an existing theme, a default theme, or the blank theme that comes with Create Block Theme. But yeah, the approach you suggested sounds perfect. Yeah, export a new theme and then you can upload it somewhere. Yeah.
\n\n\n\nBirgit Pauli-Haack: Okay. Yeah. All right. Okay. Yeah, so I’m not missing any step and then be surprised, like, “Oh no, that doesn’t work.” And start from scratch again. No, I think I want to start from an existing theme. So with the step on the Site Health and troubleshooting plugin, you could install… Or before you enable the troubleshooting mode on the plugin, install other plug themes. So I would think maybe Brian Gardner has some… Two block themes, the Frost and the Powder. Then Ellen Bauer has two great themes. One is the AinoBlock and the other of the Aino theme, but I think it was an earlier block theme. And then the latest one is MOOC, which is actually for magazine sites, which I am going to review again to see if that matches up. It’s quite a nice theme. And then my classic theme is Excel from… And there’s Norén, who also has quite a few block themes, and is actually an early adopter of block themes. And he has, I think, four or five block themes in there.
\n\n\n\nSo I’m not yet quite sure on my decision on the 2024 theme, but Eat Your Own Dog Food is probably… That’s where I’m going to end up. But I like exploring the different themes. And the troubleshooting mode on the plugin, SiteHealth plugin, is definitely helping quite easily because you don’t have to set up a new site and all that to just test out some of the themes. And of course I could do Playground… No, I can’t. Well, there are ideas around Playground to actually create a copy of your site and then you can test things out. But I think that’s not that far yet. But keep out, watch out for Playground, it can really help you with things.
\n\n\n\nSarah Norris: At the moment, with Playground, you could install the Create Block Theme plugin in a Playground instance and then build a theme in that instance and then export it from there. So again, maybe not a hundred percent for your use case, but just to know there’s another option, yet another option out there. It’s good for isolating the WordPress instance, and you don’t have to worry about all the other things that come with it, like hosting and setting up WordPress, obviously all the benefits of Playground. So you can just start from Create Block Theme, basically.
\n\n\n\nBirgit Pauli-Haack: That’s so true. So any designer could just use Playground, click on one button on the Playground site and then install the plugin. And then once you… The Create Block Theme and then create from scratch or use the 2024 one and then export it and use it on any other site. But it goes away, right? Playground goes away again, when you close the browser, right?
\n\n\n\nSarah Norris: You can now change the option so it will persist. So yeah, there are other options. So if you’re looking for these options, they’re in the top right when you visit the Playground site. But yeah, so not everything disappears now when you close the Playground, you can persist it in the browser, in the browser history.
\n\n\n\nBirgit Pauli-Haack: Wow, that’s fantastic. You don’t even need anything, any websites. Yeah, you can just use Playground to persist it. All right, well, this has been such a great show to talk to you about and chat about. Thank you so much, Sarah. So when people want to reach you, where do they find you?
\n\n\n\nSarah Norris: I am mikachan or mikachan underscore. Someone else has already taken my username on everywhere, basically, on wordpress.org and Twitter and yeah. Yeah.
\n\n\n\nBirgit Pauli-Haack: All right.
\n\n\n\nSarah Norris: Please reach out. Yeah.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I will share the contact information in the show notes so you can follow up with them. Well, this was the first show of 2024. Thank you so much, Sarah, for being here and being my… Keep me straight on the straight and narrow here. And as always, the show notes will be published on the gutenbergtimes.com/podcast. This is episode 94, and if you have questions or suggestions or news, just send them to changelog@gutenbergtimes.com. That’s changelog@gutenbergtimes.com. So thank you all for listening. Hope you all have a great 2024, and until the next time. Bye. Bye, Sarah.
\n\n\n\nSarah Norris: Bye.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 08 Jan 2024 11:48:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:43;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:119:\"Gutenberg Times: Happy New Year, WordPress Enterprise, Developer Hours and an Interactive Game – Weekend Edition 279\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=26820\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://gutenbergtimes.com/happy-new-year-wordpress-enterprise-weekend-edition-279/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:21731:\"Howdy,
\n\n\n\nWishing you and yours a prosperous, happy and healthy 2024, with a lot of success, lots of laughter and a lot of love. 🤗
\n\n\n\nAfter two weeks of vacation, it’s been inspiring to catch up. Many developers, freelancers, and site builders use the downtime around the holidays to work on their side projects or sit down to write about their learnings. What was your side or writing project? I want to know!
\n\n\n\nFor me, it meant moving the Gutenberg Times to a new hosting space. I feared it to be difficult going from a very opinionated hosting environment to Pressable. I was pleasantly surprised how, with the help of customer service, we got it done in a matter of minutes. What took the longest was the propagation of the DNS server changes over the Internet, that took roughly an hour. The main reasons for the switch was that using WordPress Playground with Gutenberg Nightly didn’t work at the old host. After testing various configuration also on other hosting spaces, I am excited that it worked out of the box on Pressable.
\n\n\n\nNow, let’s see what others published in the WordPress editor space in the past three weeks.
\n\n\n\nYours, 💕
Birgit
PS: The sixth anniversary of the start of Gutenberg Times is coming up this week, and I just wanted to say, it has been a great pleasure curating all the things around Gutenberg for you. So glad you are here with me.
\n\n\n\n\nUpdates on Gutenberg Times
\n\n\n\n🆕 As mentioned above, you can now use the Gutenberg Nightly plugin built with WordPress Playground and land right in the site editor screen. If you are interested in the blueprint, it’s available here
\n\n\n\n \n\n\n\nAnne McCarthy invites you to Leap into 2024 with these Site Editor Tools and gives you a list of features and tools, that might have slipped your mind, or you haven’t had a chance to explore. This is an excellent run-down of use cases and update on the current state of the site editor. Learn more about the Command Palette, the Style Book, styling short-cuts, Distraction-free mode, Patterns, and the List view.
\n\n\n\nOnce you are ready to dive deeper into any of the topics, the WordPress Developer Blog covered quite a few topics this year. Justin Tadlock published 2023 Year in Review, citing some numbers and listing all the articles in a sorted way. It’s the best way to catch-up on things you might have missed. And if you don’t want to miss any more articles on the Developer blog, it’s time to subscribe to it. Scroll down on any post of page and enter your email address 🙂 Or subscribe to the RSS feed with your favorite reader.
\n\n\n\nIn his post What’s new in Gutenberg 17.3? (20 December),release lead Madhu Dollu, highlighted:
\n\n\n\nIn total, the release included 184 merged PRs by 56 contributors, 6 of them contributed for the first time. Congratulations to the team.
\n\n\n\n\n\n\n\nOn January 3rd, 2024, Gutenberg 17.4 was released. What’s new in Gutenberg 17.4? (03 January). As release lead, I highlighted the following features:
\n\n\n\nSarah Norris joined me on the recording for the Gutenberg Changelog episode 94, and it was a lovely chat about the past three Gutenberg plugin releases and the upcoming roadmap for WordPress 6.5.
\n\n\n\n\n\n\n\nWe also covered the process of how to migrate a site from a classic theme to a block theme, something, that’s on my to-do list for the Gutenberg Times in the upcoming weeks. Spoiler: The plugin Health Check & Troubleshooting and Create a Block Theme will play big roles. Did you move a site from a classic theme to a block theme? How did you go about it, and what were the greatest challenges? Please let us know in the comments or email me, pauli@gutenbergtimes.com.
\n\n\n\nThe podcast episode will drop in your favorite podcast app over the weekend.
\n\n\n\n🎙️ Latest episode: Gutenberg Changelog #95 – Gutenberg 17.5, Early Testing of WordPress 6.5 and Block Themes with special guest: Carolina Nymark
\n\n\n\nHumanMade and BigBite invite you to a WordPress for Enterprise event on January 18th, 2024 to Hear from the global brands doing incredible things with WordPress. It’ll start at 16:00 UTC and will take until about 21:00 UTC “Over the course of 6 sessions, we’ll be sharing the stories behind these amazing projects. Expect case studies, deep dives, and behind-the-scenes access on topics such as security, performance, editorial optimization, AI, and how open source is making a difference in the enterprise setting.” with speaker such as Adam Silverstein, Google, Brian Alvey, WordPress VIP, or Luke Sikkema, The Times, and a few more.
\n\n\n\n\n\n\n\nIn her post joyful flow state, Anne McCarthy shares her creative process and musing about creating block patterns for the Museum of Block Art. “Using the same software I spend my days toiling over in a creative, unserious way expands my relationship to the work, both energy and perspective wise.” she wrote.
\n\n\n\nMunir Kamal did some research and shares with the world in this post: Discover the Best Block Slider Plugins for WordPress. A block that has been missing from the core blocks, several plugins offer their variation of the slider. It’s not always the best user experience and there is a school of web developer who like to dissuade site owners from using sliders and even built a slider site with some good reasons why you shouldn’t use a carousel, which is just another word for slider.
\n\n\n\nLifter LMS updated their documentation and showcase their Lifter LMS Blocks with videos and instructions on how to use them. Now one of the leading Learning Management systems, built on top of WordPress, enters the next product phase and allows for faster content creation with the already known Block interface built into WordPress.
\n\n\n\n\n\n\n\n\n\n\n\n\n “Keeping up with Gutenberg – Index 2022”
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2021 on. Updated by yours truly. The index 2020 is here
For the Developer Hours in December, Nick Diego and Ryan Welcher selected the topic: Modern WordPress development with the wp-scripts package. The recording is available on YouTube, and they shared the mentioned resources as a Google Doc. They wrote: “We explored how the wp-scripts package has become an essential tool for modern WordPress development, such as when building blocks and block themes. If you are looking to streamline your development process, harness the power of build tools, and simplify tasks such as checking for compliance with WordPress coding standards, this session recording is for you.”
\n\n\n\nYou are invited to the January Developers Hours for January 16th, 2024 at 15:00 UTC (10 am EDT) to Build your first WordPress block. In this online event, you’ll be on a walk-through the new tutorial in the Block editor handbook, and you will also learn more about the block development examples on GitHub.
\n\n\n\n\n\n\n\nJonathan Desrosiers informed developers about Updating WordPress to use more modern versions of Node.js/npm: Part 2.
\n\n\n\nIn his tutorial, Extending plugins using custom SlotFills, Ryan Welcher explains how you can use custom SlotFills to extend both an internal and external codebase.
\n\n\n\nJonathan Bossenger experimented with the Interactivity API and used WordPress as a game development platform. It’s a fun game, where the logos of other web development platform chase after the WordPress logo. I lasted 25 seconds. How long did you last? “There is still a lot of work to be done to turn this into a working game, but I’m excited about the possibilities. Stay tuned because I can see this turning into a bit of a series of posts”. Bossenger wrote. If you would rather not wait so long, you can take a sneak peek at the code via the GitHub repository: WP-Interactive Game.
\n\n\n\nDaniel Post created a two-part tutorial on Creating a WordPress options page using React and Gutenberg. “This guide is primarily aimed at people who have some WordPress experience but have never tried “the React way”, but it should be useful for anyone trying to get into into modern WordPress development.” It’s a very thorough tutorial. Post explains all the basic pieces other tutorials might assume prior knowledge of, and steps through almost every line of the code, in PHP as well as in JavaScript, he uses to build this example.
\n\n\n\nOn YouTube, Ryan Welcher posted his latest stream in the Block Developer Cookbook series, Block Developer Cookbook Recipe: Command Palette. “In this flavorful cooking demonstration, initially aired on November 16, we whip up a special culinary command for the all-new Command Palette. Our goal? To deftly toggle the custom fields meta box in the post editor, just like a chef skillfully adjusting the seasoning levels in a signature dish. Let’s embark on this culinary coding adventure together!” he wrote.
\n\n\n\nNyasha Green just published her WordPress: Introduction to Custom Block Building on the LinkedIn Learning Network. The course starts with a brief introduction to the Block editor and how to add blocks to a post’s canvas and explain block attributes. In the second module you’ll learn to set up your local environment with LocalWP, 2021 default theme and Node.js. In the chapter Custom Blocks without code, Green explains how to create patterns and synched patterns, and you’ll learn about the Pattern Directory. The fourth chapter, Green, covers Custom Block Building with code, and introduces the learner to the create-block scaffolding tool. The topic covers creating a card with three blocks and some InnerBlocks rules and how to modify the styles for the custom block. It’s a great starting point. The LinkedIn Learning space is a subscription-based learning environment, but you can use a free trial for the first month.
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph.
\n\n\n\nFor questions to be answered on the Gutenberg Changelog, send them to changelog@gutenbergtimes.com
\n\n\n\nFeatured Image:
\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nLesley Sim is a WordPress product owner, and has navigated the waters of whether to offer a free version and has struggled with the idea of whether Open Source is even a good idea.
\n\n\n\n[WordPress] helps so many people grow their businesses, communicate, and simply share their thoughts with everyone on the internet. There is no such thing as only good without the bad. And I’m glad WordPress exists.
\n\n\n\nLesley’s essay is available on HeroPress.com.
\nThis week’s WPPhotos Info is called “The snowy peaks“.
\n\n\n\nAmazing view captured by Trinisha. This is Ganjala Range seen from Kyanjin Ri Peak (4773m/15655 ft).
\n\n\n\n\nThere were fourteen WordPress podcast episodes released this week!
\n\n\n\nThere are new episodes every single day, so be sure to stop by WPPodcasts.com and search for things that interest you!
\nHere are some of the great photos submitted to the WPPhotos project this week!
\n\n\n\n\nCC0 licensed photo by Balu B from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Balu B from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Bhuwan Bdr. Rokaha from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Balu B from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Sadie-Michaela Harris from the WordPress Photo Directory.\n\n\n\nCC0 licensed photo by Sadie-Michaela Harris from the WordPress Photo Directory.\n\n\n\n\nBe sure to check out the hundreds of other great photos!
\nThe header photo for this post is a CC0 licensed photo by mahfuznafi from the WordPress Photo Directory.
\n\n\n\n\n\n\nThat’s it for this week! If you’d like to get this post in your email every week, make sure you sign up!
\n\nThe post Is Open Source Good For WordPress? See Who Says Yes! appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 05 Jan 2024 18:25:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WordPress.org blog: The Month in WordPress – December 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16680\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2024/01/the-month-in-wordpress-december-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9933:\"As 2023 came to a close, WordPress bid farewell with the much-anticipated annual State of the Word and the 6.5 roadmap, among other exciting updates.
\n\n\n\nRead on to learn more about the community’s end-of-year celebrations and catch a sneak peek of what’s in store for the year ahead.
\n\n\n\n\n\n\n\nOn December 11, WordPress co-founder Matt Mullenweg delivered his annual State of the Word keynote in Madrid, Spain, marking the first international edition of the event. Nearly 200 WordPress enthusiasts and tech industry leaders gathered in person to hear what’s next for WordPress—with a large audience joining online or from one of the 47 watch parties held across 18 countries.
\n\n\n\nThe keynote highlighted last year’s milestones and showcased compelling demos, providing a glimpse into the upcoming developments for the Site Editor, Collaboration phase, and Admin redesign. Matt also introduced 2024’s focus on Data Liberation, aiming to unlock digital barriers and frictionless migrations into WordPress for a more open web.
\n\n\n\n \n\n\n\nThe event concluded with a Q&A session and this follow-up post.
\n\n\n\n\n\n\n\nWordPress 6.5 is scheduled for release on March 26, 2024. This major release is set to introduce a new Font Library for easy global font management, support for Appearance Tools in Classic Themes, Data Views for templates and patterns, and more robust revisions across the editing experience, among other highlights.
\n\n\n\n6.5 will also include new APIs like Interactivity, Custom Fields, and Block Binding that expand block capabilities and underpin features like Synced Pattern Overrides.
\n\n\n\nLearn more about the features planned for WordPress 6.5 in this roadmap post.
\n\n\n\n\n\n\n\n\n\n\n\n\nDon’t wait for the next release to optimize your creative workflows with these powerful Site Editor tools.
\n
Two new versions of Gutenberg shipped in December:
\n\n\n\nHave a story we should include in the next issue of The Month in WordPress? Fill out this quick form to let us know.
\n\n\n\nThank you to Bernard Meyer, Nicholas Garofalo, and Lauren Stein for contributing to this edition of The Month in WordPress.
\n\n\n\nJoin other subscribers and receive WordPress news directly in your inbox.
\n\n\n\n Subscribe\n
\nStarting 2024 on an optimistic note as I noticed more of my fellow WordPressers feeling more optimistic and happy about WordPress.
\n>> The post Make. WordPress. Happy. appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 05 Jan 2024 09:31:55 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"Matt: Fred Again Tiny Desk\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=110139\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://ma.tt/2024/01/fred-again-tiny-desk/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:140:\"You think you’ve seen Tiny Desk performances, but you haven’t seen this.
\n\n\n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 05 Jan 2024 06:50:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Matt: On Mastodon\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=110133\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://ma.tt/2024/01/on-mastodon/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:177:\"This is me on Mastodon, it’s really me, also added to my Gravatar.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 05 Jan 2024 02:31:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"Akismet: What is a Honeypot in Spam Protection and Cybersecurity?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://akismet.com/?p=283657\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"https://akismet.com/blog/what-is-a-honeypot/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:21930:\"If your enterprise handles large volumes of sensitive content, cybersecurity should be a top priority. You likely already have measures in place to block hacking attempts. But did you know that you can also create honeypots to further protect your business?
\n\n\nWhat is a honeypot? In a nutshell, this is a web app or system that mimics your company’s network. It’s designed to lure in hackers so that the security team can study their tactics and identify weak areas in your organization.
\n\n\nIn this guide, we’ll take a closer look at how honeypots work and the different ways you can implement them. We’ll also discuss the benefits of honeypots in cybersecurity and spam protection. So, let’s dive right in!
\n\n\n\n\n\nLet’s start by answering the most important question: what is a honeypot?
\n\n\nEssentially, a honeypot is a network that’s designed to serve as a decoy for hackers. It’s made to appear as part of an organization’s IT infrastructure, but in fact, it’s completely isolated from it.
\n\n\n\nThe primary purpose of honeypots is to attract cyber threats. This way, security experts can get a close look at the attackers’ tactics and behavior in a safe and controlled environment. Using this information, they can then enhance the overall security of the actual infrastructure.
\n\n\nThis technique is usually deployed by enterprises that handle large amounts of data. By being proactive, your organization can identify vulnerabilities in its network before they’re discovered by hackers. This ultimately helps prevent serious hacking events that can negatively impact your revenue or damage your reputation.
\n\nPlus, creating a honeypot can help you test the effectiveness of pre‑existing security measures against cyber threats. Your enterprise can then use these findings to fortify its system.
\n\nNow that we’ve answered the basic question on what a honeypot is, let’s look at the different types of decoys you can use:
\n\n\nBots will often fill out forms on your site to send spam or attempt to inject malicious code into your site. No, that fishy-sounding company didn’t really find “30 SEO errors on your site!” They used a bot to send spam to thousands of site owners hoping to catch someone off guard.
\n\n\n\nSince bots typically fill out any available field, you can trick them into identifying themselves by essentially creating an invisible field that the bot can read in the code, but that won’t appear to users. If one fills it out, you know it’s a fake submission.
\n\n\n\nWhile this is a decent way to catch spam, it’s not without its faults as bots can increasingly decipher these traps and work around them.
\n\n\nAs you might have guessed, email or spam trap honeypots are designed to catch malicious emails that are sent to your organization. The way they work is quite simple.
\n\nA spam trap honeypot would consist of “fake” email addresses linked to your organization. You might place these contact details on your website or any other online platform to lure in spammers.
\n\nYour security team can then review and examine any unsolicited emails that come into the honeypot. This will help them design effective filters and spam protection measures for the “real” email addresses, thus protecting employees against phishing attacks and other malicious activities.
\n\n\nTo avoid any confusion, we’d like to mention that you may have also heard about these in the context of email marketing or email deliverability. That’s because email spam trap honeypots are also used by blocklists and inbox service providers to catch mass email senders who acquire email lists via unauthorized methods. However, this isn’t something the cybersecurity division of your organization typically needs to worry about.
\n\n\nYou already know about web crawlers or “spiders” — the bots that scan the contents of a website. Google uses these web crawlers to index the pages of your website and display them in relevant search results.
\n\n\nBut web crawlers are also used by hackers to discover vulnerabilities in websites. Spider honeypots are therefore designed to attract these bots to identify weaknesses in a web application or website.
\n\n\nBy simulating your web application and inviting these crawlers to do their work, you can study their behavior as they try to find a way in. This will help your team identify any specific attack patterns or common exploits, and take the necessary measures to protect your enterprise against web-based attacks.
\n\n\nIf your organization has a malware problem, this type of honeypot can help you get to the bottom of it.
\n\n\n\nMalware honeypots are designed to emulate systems or services that are usually affected by malicious software. Your security team can use this system to study the origins and workings of the malware in a controlled environment.
\n\n\nThis will enable them to implement effective measures against this threat. For example, they might develop a sturdier and more intelligent antivirus program for your enterprise.
\n\nOne of the most common threats for enterprises is a data breach. If your company stores sensitive information, like customer details and financial records, it could be an attractive target among hackers.
\n\n\nA decoy database is a type of honeypot that entices attackers who are looking to steal your data. It mimics your organization’s database but, of course, the information it contains would be fake.
\n\n\nThis type of honeypot can help you spot vulnerabilities in your database and study the techniques hackers use to access your data. This way, you’ll be able to implement stricter access controls in your database and develop more effective protection solutions.
\n\nClient honeypots are another popular decoy. These mimic client‑side applications and personal devices.
\n\nFor example, you might set up a client honeypot to find security flaws in your company’s applications and software. This can be particularly useful if you have a large number of employees or customers using an online app. For instance, you might create a client honeypot for a learning management system (LMS) or an ecommerce app for loyal shoppers.
\n\n\nA client honeypot serves as a trap for hackers that target enterprise software or web applications. Plus, it enables you to find better ways to protect your users from potential exploits.
\n\n\n\nThis is possibly the most advanced decoy you could opt for. Basically, a honeynet is a large network of interconnected honeypots. It’s meant to emulate a complete enterprise network.
\n\n\n\nHoneynets can be very useful in studying sophisticated cyberattacks and testing your company’s overall security. By implementing this strategy, your security team can gain a deeper understanding of the evolving techniques used by cyber criminals.
\n\n\nThese insights will then help them develop a comprehensive security strategy for your enterprise.
\n\nEach type of honeypot that we outlined above can be implemented on different levels. With this in mind, let’s take a look at the main tiers of honeypot deployment.
\n\nPure honeypots are designed to appear as real as possible, so they can attract highly skilled attackers. They are a form of high‑interaction honeypots (which we’ll be looking at more closely in a minute) and are deployed with minimal interaction capabilities.
\n\nSecurity professionals use pure honeypots to gather in‑depth information about the strategies employed by sophisticated attackers. In particular, they’re concerned with tactics that can affect an organization’s entire system. For example, they can gain valuable insights into previously unknown vulnerabilities in your network.
\n\n\nLow-interaction honeypots have limited interaction capabilities and only emulate specific parts of a real system. This makes them easier to deploy and manage compared to high-interaction honeypots. As such, they’re mostly ideal for analyzing common attacks.
\n\n\n\nLow-interaction honeypots simulate services and applications at a basic level. This enables your security team to capture basic data without exposing your real (and potentially vulnerable) systems.
\n\n\n\nWhile these honeypots do not provide the same level of depth as more advanced systems, they can be quite effective in detecting known threats and preventing attacks.
\n\n\n\nMid-interaction honeypots offer a moderate level of realism and interaction. They’re built to emulate different services and applications, providing more “exploit opportunities” for attackers.
\n\n\nWith these honeypots, your security team can observe malicious activities in a relatively realistic setting. This enables them to collect more detailed data and fine‑tune your company’s existing security measures.
\n\n\nHigh-interaction honeypots provide the most authentic simulation of real-world systems and applications. Unlike low or mid-interaction honeypots, they allow attackers to interact with a full-fledged, genuine environment.
\n\n\n\nThese honeypots are set up with real operating systems and applications. This makes them highly attractive to attackers seeking valuable targets.
\n\n\nAs you can probably tell, these high‑interaction honeypots carry a higher risk as they use a legitimate environment, but they offer unparalleled insights into advanced attacks. Plus, they enable your team to study zero‑day vulnerabilities (more on this in a minute) and develop effective strategies to counter these sophisticated threats.
\n\nWe’ve already touched upon the benefits of honeypots for your company’s cybersecurity. But let’s take a closer look at how they can help protect your organization.
\n\n\nA zero-day vulnerability is a flaw in software that is discovered by hackers before developers become aware of it. Therefore, attackers that target zero-day exploits do not give organizations or developers time to patch these vulnerabilities.
\n\n\nAs we have seen, honeypots (particularly high‑interaction ones) create a controlled environment where attackers engage with authentic applications. By analyzing the tactics used in these attacks, you can uncover unknown vulnerabilities in your company’s software. This will enable you to develop patches proactively or reach out to the software’s developers for an immediate fix.
\n\nAs we mentioned earlier, honeypots are completely isolated from the real system. This means that any attack on the simulated environment will not affect your company’s operations.
\n\n\n\nAdditionally, since they have no legitimate purpose, any activity in these environments will immediately spark suspicion. This means that your security team can detect threats at an early stage and respond to them swiftly.
\n\n\nEarly threat detection can prevent attacks from spreading to other parts of the network.
\n\nHoneypots also provide real-time attack monitoring. This means security professionals can observe the hackers’ movements and activities as they happen.
\n\n\n\nYou might use real-time visualization tools like graphs and heatmaps so that it’s easier to identify attack patterns and targets. Plus, these visualization tools can enable you to comprehend the scope and impact of the threats. This way, you can ensure that you implement a solution that encompasses all possible vulnerabilities.
\n\n\nWhen implemented effectively, honeypots can tell you a lot about the individuals behind the attack. This includes information about the attackers’ methods, preferred targets, and geographic locations.
\n\nYour security team can then use this data to create intruder profiles. Such information is essential for understanding the motives behind the attacks.
\n\nIf you have accurate intruder profiles, you can collaborate with law enforcement agencies or other security organizations to track down cyber criminals.
\n\nHoneypots can also be an effective measure in identifying and blocking spam. Here are a few different ways to use them for spam detection:
\n\nContact form spam affects many businesses and can be very annoying. When it occurs, emails from genuine customers can be easily lost in a sea of spammy ones.
\n\n\nYour organization can integrate honeypot fields within contact forms to trap automated bots. This way, you can automatically filter out spammy submissions and make it easier for your company’s administrators to manage their inboxes.
\n\nLikewise, honeypots can be used to prevent comment spam. This can be particularly useful if you have a blog on your company website.
\n\n\n\nWhen bots attempt to fill out the honeypot fields, their submissions will instantly be recognized as spam. Stopping comment spam can help you maintain a professional community.
\n\n\nBots can also take over your user registration process. If you have an online store or membership site, these fake and malicious entries can make it nearly impossible to effectively manage your users.
\n\n\nHoneypots can be integrated into user registration forms to thwart malicious registrations. By taking a proactive approach, you can find an effective way to prevent fake accounts and hackers from infiltrating your user database.
\n\nSpammers might also try to insert links into your content. Typically, they do this to manipulate their search engine rankings or drive users to harmful websites.
\n\n\nHoneypots can be instrumental in preventing link spam. You can use honeypots strategically to attract spammers, study their behavior, and design more effective security solutions that guard access to edit permissions for your content.
\n\nYou might already be using CAPTCHA and challenge-response mechanisms on your website. These make it more difficult for automated bots to submit spammy content, but they’re not always effective.
\n\n\n\nHoneypots act as an additional layer of defense. They make it nearly impossible for malicious actors to interact with your forms undetected.
\n\n\nBut, you don’t need to implement CAPTCHAs to prevent spam on your website, and these kinds of tests are distracting for users and are likely negatively impacting your conversions.
\n\nA comprehensive anti‑spam solution like Akismet can provide a better way to defend your site against spam.
\n\n\n\n\n\n\nThis tool can identify spammy behavior without the need for a challenge-response mechanism. It does this with an AI-powered system that detects spam signals utilizing things like blocklists, IP addresses, names, and emails associated with suspicious activities.
\n\n\n\nAnd it works with nearly 100% accuracy.
\n\n\nAdditionally, Akismet offers a better user experience for visitors, as it doesn’t require them to solve any puzzles. Instead, it analyzes their behavior and blocks any suspicious entries.
\n\nBy combining honeypots with powerful tools like Akismet, you can ensure that only genuine human users can engage with your website.
\n\nAkismet is a spam prevention plugin for WordPress websites. To date, it has blocked more than 525,000,000,000 spam comments. This is thanks to its powerful and advanced AI technology.
\n\n\n\nAkismet is free for personal use and affordable for every level of commercial organization. The improved user experience and resulting boost in conversion rates will more than justify the investment in this valuable tool. If you’re ready to try it out, you can download it from the WordPress plugin directory.
\n\n\n\n\n\n\nAlternatively, if you’re dealing with a larger volume of sensitive user data, you might want to request a custom enterprise plan. This will be tailored to your company’s needs and will give you access to personalized support.
\n\nAkismet offers an automated spam protection solution. It checks all submissions on your site and filters out spammy entries. This enables your admin team to handle queries more efficiently.
\n\nAdditionally, Akismet is a cloud‑based solution. This means that it doesn’t store any data on your website. As a result, it won’t have any impact on your website’s speed and performance.
\n\n\nBut perhaps the best thing about Akismet is that it integrates with a wide variety of tools. These include popular plugins like Jetpack, Contact Form 7, Gravity Forms, and Formidable Forms.
\n\n\nYou might be wondering what makes Akismet a good alternative to other spam protection solutions.
\n\n\nUnlike most anti‑spam tools, Akismet does not use CAPTCHA to block bots. This is typically a puzzle or challenge that users must complete to submit their entries. Its purpose is to make it more difficult for automated bots to submit spammy content.
\n\nBut CAPTCHA can be off‑putting for human users. It adds friction to the form submission process, and users with certain physical or cognitive disabilities might struggle to complete certain CAPTCHA prompts. This can cause people to abandon the entire process, and lead to fewer queries and conversions for your business.
\n\n\nWith Akismet, you won’t need to worry about CAPTCHAs creating a poor user experience for legitimate visitors. This plugin is powered by machine learning, which enables it to automatically spot spam through suspicious behavior. It does all of this in the background, without interfering with the experience of real users.
\n\n\n\nThat means you’ll be able to provide a smoother user registration process. Plus, site visitors won’t need to complete a challenge just to send a quick message through your contact form or subscribe to your newsletter.
\n\n\nAkismet is a leading spam protection tool, used across 100 million sites. These include popular companies like WordPress.com, Bluehost, and ConvertKit.
\n\n\nAre you ready to block spam with Akismet? Get in touch today for a tailored enterprise solution.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 03 Jan 2024 14:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Jen Swisher\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Sun, 28 Jan 2024 15:14:46 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:13:\"last-modified\";s:29:\"Sun, 28 Jan 2024 15:00:36 GMT\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:16:\"content-encoding\";s:2:\"br\";s:7:\"alt-svc\";s:19:\"h3=\":443\"; ma=86400\";s:4:\"x-nc\";s:9:\"HIT ord 1\";}}s:5:\"build\";s:14:\"20211221003300\";}','no'),(373,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1706498087','no'),(374,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1706454887','no'),(375,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1706498087','no'),(376,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b',' ','no'),(382,'_transient_timeout_as-post-store-dependencies-met','1706541288','no'),(383,'_transient_as-post-store-dependencies-met','yes','no'),(387,'_transient_timeout_tribe_aggregator_services_list','1706541289','no'),(388,'_transient_tribe_aggregator_services_list','a:1:{s:6:\"origin\";a:1:{i:0;O:8:\"stdClass\":2:{s:2:\"id\";s:3:\"csv\";s:4:\"name\";s:8:\"CSV File\";}}}','no'),(389,'_transient_timeout__tribe_admin_notices','1709049224','no'),(390,'_transient__tribe_admin_notices','a:0:{}','no'),(392,'_transient_timeout_action_scheduler_last_pastdue_actions_check','1706476492','no'),(393,'_transient_action_scheduler_last_pastdue_actions_check','1706454892','no'),(394,'_transient_timeout__tribe_tickets_activation_redirect','1706455518','no'),(395,'_transient__tribe_tickets_activation_redirect','1','no'),(396,'_transient_doing_cron','1706457241.2754778861999511718750','yes'),(397,'admin_email_lifespan','1722007097','yes'),(398,'_site_transient_timeout_browser_54140f3964ad48219c4ac743dca17665','1707059898','no'),(399,'_site_transient_browser_54140f3964ad48219c4ac743dca17665','a:10:{s:4:\"name\";s:7:\"Firefox\";s:7:\"version\";s:5:\"122.0\";s:8:\"platform\";s:9:\"Macintosh\";s:10:\"update_url\";s:32:\"https://www.mozilla.org/firefox/\";s:7:\"img_src\";s:44:\"http://s.w.org/images/browsers/firefox.png?1\";s:11:\"img_src_ssl\";s:45:\"https://s.w.org/images/browsers/firefox.png?1\";s:15:\"current_version\";s:2:\"56\";s:7:\"upgrade\";b:0;s:8:\"insecure\";b:0;s:6:\"mobile\";b:0;}','no'),(401,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1706455326;s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:8:{s:33:\"coupon-creator/coupon_creator.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:28:\"w.org/plugins/coupon-creator\";s:4:\"slug\";s:14:\"coupon-creator\";s:6:\"plugin\";s:33:\"coupon-creator/coupon_creator.php\";s:11:\"new_version\";s:5:\"3.3.0\";s:3:\"url\";s:45:\"https://wordpress.org/plugins/coupon-creator/\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/plugin/coupon-creator.3.3.0.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:59:\"https://ps.w.org/coupon-creator/assets/icon.svg?rev=2688941\";s:3:\"svg\";s:59:\"https://ps.w.org/coupon-creator/assets/icon.svg?rev=2688941\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:70:\"https://ps.w.org/coupon-creator/assets/banner-1544x500.png?rev=2688941\";s:2:\"1x\";s:69:\"https://ps.w.org/coupon-creator/assets/banner-772x250.png?rev=2688941\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.9\";}s:49:\"easy-digital-downloads/easy-digital-downloads.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:36:\"w.org/plugins/easy-digital-downloads\";s:4:\"slug\";s:22:\"easy-digital-downloads\";s:6:\"plugin\";s:49:\"easy-digital-downloads/easy-digital-downloads.php\";s:11:\"new_version\";s:5:\"3.2.6\";s:3:\"url\";s:53:\"https://wordpress.org/plugins/easy-digital-downloads/\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/plugin/easy-digital-downloads.3.2.6.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:66:\"https://ps.w.org/easy-digital-downloads/assets/icon.svg?rev=971968\";s:3:\"svg\";s:66:\"https://ps.w.org/easy-digital-downloads/assets/icon.svg?rev=971968\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:78:\"https://ps.w.org/easy-digital-downloads/assets/banner-1544x500.png?rev=2636140\";s:2:\"1x\";s:77:\"https://ps.w.org/easy-digital-downloads/assets/banner-772x250.png?rev=2636140\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.8\";}s:31:\"event-tickets/event-tickets.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:27:\"w.org/plugins/event-tickets\";s:4:\"slug\";s:13:\"event-tickets\";s:6:\"plugin\";s:31:\"event-tickets/event-tickets.php\";s:11:\"new_version\";s:5:\"5.8.0\";s:3:\"url\";s:44:\"https://wordpress.org/plugins/event-tickets/\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/plugin/event-tickets.5.8.0.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:58:\"https://ps.w.org/event-tickets/assets/icon.svg?rev=2259340\";s:3:\"svg\";s:58:\"https://ps.w.org/event-tickets/assets/icon.svg?rev=2259340\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:69:\"https://ps.w.org/event-tickets/assets/banner-1544x500.png?rev=2257626\";s:2:\"1x\";s:68:\"https://ps.w.org/event-tickets/assets/banner-772x250.png?rev=2257626\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"6.2\";}s:27:\"redis-cache/redis-cache.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:25:\"w.org/plugins/redis-cache\";s:4:\"slug\";s:11:\"redis-cache\";s:6:\"plugin\";s:27:\"redis-cache/redis-cache.php\";s:11:\"new_version\";s:5:\"2.5.0\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/redis-cache/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/redis-cache.2.5.0.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/redis-cache/assets/icon-256x256.gif?rev=2568513\";s:2:\"1x\";s:64:\"https://ps.w.org/redis-cache/assets/icon-128x128.gif?rev=2568513\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/redis-cache/assets/banner-1544x500.png?rev=2315420\";s:2:\"1x\";s:66:\"https://ps.w.org/redis-cache/assets/banner-772x250.png?rev=2315420\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.6\";}s:43:\"the-events-calendar/the-events-calendar.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:33:\"w.org/plugins/the-events-calendar\";s:4:\"slug\";s:19:\"the-events-calendar\";s:6:\"plugin\";s:43:\"the-events-calendar/the-events-calendar.php\";s:11:\"new_version\";s:5:\"6.3.1\";s:3:\"url\";s:50:\"https://wordpress.org/plugins/the-events-calendar/\";s:7:\"package\";s:68:\"https://downloads.wordpress.org/plugin/the-events-calendar.6.3.1.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-256x256.gif?rev=2516440\";s:2:\"1x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-128x128.gif?rev=2516440\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:75:\"https://ps.w.org/the-events-calendar/assets/banner-1544x500.png?rev=2257622\";s:2:\"1x\";s:74:\"https://ps.w.org/the-events-calendar/assets/banner-772x250.png?rev=2257622\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:5:\"6.2.0\";}s:27:\"woocommerce/woocommerce.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:25:\"w.org/plugins/woocommerce\";s:4:\"slug\";s:11:\"woocommerce\";s:6:\"plugin\";s:27:\"woocommerce/woocommerce.php\";s:11:\"new_version\";s:5:\"8.5.2\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/woocommerce/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/woocommerce.8.5.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/woocommerce/assets/icon-256x256.gif?rev=2869506\";s:2:\"1x\";s:64:\"https://ps.w.org/woocommerce/assets/icon-128x128.gif?rev=2869506\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/woocommerce/assets/banner-1544x500.png?rev=3000842\";s:2:\"1x\";s:66:\"https://ps.w.org/woocommerce/assets/banner-772x250.png?rev=3000842\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"6.3\";s:6:\"tested\";s:5:\"6.4.2\";s:12:\"requires_php\";s:3:\"7.4\";}s:29:\"wp-downgrade/wp-downgrade.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:26:\"w.org/plugins/wp-downgrade\";s:4:\"slug\";s:12:\"wp-downgrade\";s:6:\"plugin\";s:29:\"wp-downgrade/wp-downgrade.php\";s:11:\"new_version\";s:5:\"1.2.6\";s:3:\"url\";s:43:\"https://wordpress.org/plugins/wp-downgrade/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/plugin/wp-downgrade.1.2.6.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:65:\"https://ps.w.org/wp-downgrade/assets/icon-256x256.png?rev=1412844\";s:2:\"1x\";s:65:\"https://ps.w.org/wp-downgrade/assets/icon-128x128.png?rev=1412844\";}s:7:\"banners\";a:0:{}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:5:\"3.0.1\";}s:27:\"wp-rollback/wp-rollback.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:25:\"w.org/plugins/wp-rollback\";s:4:\"slug\";s:11:\"wp-rollback\";s:6:\"plugin\";s:27:\"wp-rollback/wp-rollback.php\";s:11:\"new_version\";s:5:\"2.0.6\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/wp-rollback/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/wp-rollback.2.0.6.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/wp-rollback/assets/icon-256x256.jpg?rev=3014868\";s:2:\"1x\";s:64:\"https://ps.w.org/wp-rollback/assets/icon-128x128.jpg?rev=3014868\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/wp-rollback/assets/banner-1544x500.jpg?rev=3014868\";s:2:\"1x\";s:66:\"https://ps.w.org/wp-rollback/assets/banner-772x250.jpg?rev=3014872\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.0\";}}s:7:\"checked\";a:18:{s:33:\"ai-development/ai-development.php\";s:5:\"0.1.0\";s:33:\"coupon-creator/coupon_creator.php\";s:5:\"3.3.0\";s:49:\"coupon-creator-add-ons/coupon-creator-add-ons.php\";s:5:\"3.3.0\";s:41:\"coupon-creator-pro/coupon-creator-pro.php\";s:5:\"3.3.0\";s:49:\"easy-digital-downloads/easy-digital-downloads.php\";s:5:\"3.2.6\";s:49:\"event-schedule-manager/event-schedule-manager.php\";s:5:\"1.1.0\";s:31:\"event-tickets/event-tickets.php\";s:5:\"5.8.0\";s:41:\"event-tickets-plus/event-tickets-plus.php\";s:5:\"5.9.0\";s:27:\"redis-cache/redis-cache.php\";s:5:\"2.5.0\";s:43:\"the-events-calendar/the-events-calendar.php\";s:5:\"6.3.1\";s:35:\"event-automator/event-automator.php\";s:5:\"1.6.0\";s:33:\"events-virtual/events-virtual.php\";s:6:\"1.15.5\";s:34:\"events-pro/events-calendar-pro.php\";s:5:\"6.3.1\";s:29:\"volt-vectors/volt-vectors.php\";s:5:\"0.1.0\";s:37:\"volt-vectors-pro/volt-vectors-pro.php\";s:5:\"0.1.0\";s:27:\"woocommerce/woocommerce.php\";s:5:\"8.2.2\";s:29:\"wp-downgrade/wp-downgrade.php\";s:5:\"1.2.6\";s:27:\"wp-rollback/wp-rollback.php\";s:5:\"2.0.6\";}}','no'); +/*!40000 ALTER TABLE `wp_options` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_postmeta` +-- + +DROP TABLE IF EXISTS `wp_postmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_postmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `post_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `post_id` (`post_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_postmeta` +-- + +LOCK TABLES `wp_postmeta` WRITE; +/*!40000 ALTER TABLE `wp_postmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_postmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_posts` +-- + +DROP TABLE IF EXISTS `wp_posts`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_posts` ( + `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `post_author` bigint(20) unsigned NOT NULL DEFAULT 0, + `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `post_content` longtext NOT NULL, + `post_title` text NOT NULL, + `post_excerpt` text NOT NULL, + `post_status` varchar(20) NOT NULL DEFAULT 'publish', + `comment_status` varchar(20) NOT NULL DEFAULT 'open', + `ping_status` varchar(20) NOT NULL DEFAULT 'open', + `post_password` varchar(255) NOT NULL DEFAULT '', + `post_name` varchar(200) NOT NULL DEFAULT '', + `to_ping` text NOT NULL, + `pinged` text NOT NULL, + `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `post_content_filtered` longtext NOT NULL, + `post_parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `guid` varchar(255) NOT NULL DEFAULT '', + `menu_order` int(11) NOT NULL DEFAULT 0, + `post_type` varchar(20) NOT NULL DEFAULT 'post', + `post_mime_type` varchar(100) NOT NULL DEFAULT '', + `comment_count` bigint(20) NOT NULL DEFAULT 0, + PRIMARY KEY (`ID`), + KEY `post_name` (`post_name`(191)), + KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), + KEY `post_parent` (`post_parent`), + KEY `post_author` (`post_author`) +) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_posts` +-- + +LOCK TABLES `wp_posts` WRITE; +/*!40000 ALTER TABLE `wp_posts` DISABLE KEYS */; +INSERT INTO `wp_posts` VALUES (4,1,'2023-10-17 09:40:27','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2023-10-17 09:40:27','0000-00-00 00:00:00','',0,'http://localhost:8888/?p=4',0,'post','',0),(5,0,'2023-11-28 12:24:59','2023-11-28 12:24:59','','Navigation','','publish','closed','closed','','navigation','','','2023-11-28 12:24:59','2023-11-28 12:24:59','',0,'http://localhost:8888/?p=5',0,'wp_navigation','',0),(6,1,'2024-01-28 15:23:50','2024-01-28 15:23:50','\n\n\n','Calendar Views (Event Archive)','Displays the calendar views.','publish','closed','closed','','archive-events','','','2024-01-28 15:23:50','2024-01-28 15:23:50','',0,'http://localhost:8888/?p=6',0,'wp_template','',0),(7,1,'2024-01-28 15:23:50','2024-01-28 15:23:50','\n\n\n','Event Single','Displays a single event.','publish','closed','closed','','single-event','','','2024-01-28 15:23:50','2024-01-28 15:23:50','',0,'http://localhost:8888/?p=7',0,'wp_template','',0); +/*!40000 ALTER TABLE `wp_posts` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_tec_events` +-- + +DROP TABLE IF EXISTS `wp_tec_events`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_tec_events` ( + `event_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `post_id` bigint(20) unsigned NOT NULL, + `start_date` varchar(19) NOT NULL, + `end_date` varchar(19) DEFAULT NULL, + `timezone` varchar(30) NOT NULL DEFAULT 'UTC', + `start_date_utc` varchar(19) NOT NULL, + `end_date_utc` varchar(19) DEFAULT NULL, + `duration` mediumint(30) DEFAULT 7200, + `updated_at` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), + `hash` varchar(40) NOT NULL, + PRIMARY KEY (`event_id`), + UNIQUE KEY `post_id` (`post_id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_tec_events` +-- + +LOCK TABLES `wp_tec_events` WRITE; +/*!40000 ALTER TABLE `wp_tec_events` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_tec_events` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_tec_occurrences` +-- + +DROP TABLE IF EXISTS `wp_tec_occurrences`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_tec_occurrences` ( + `occurrence_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `event_id` bigint(20) unsigned NOT NULL, + `post_id` bigint(20) unsigned NOT NULL, + `start_date` varchar(19) NOT NULL, + `start_date_utc` varchar(19) NOT NULL, + `end_date` varchar(19) NOT NULL, + `end_date_utc` varchar(19) NOT NULL, + `duration` mediumint(30) DEFAULT 7200, + `hash` varchar(40) NOT NULL, + `updated_at` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), + PRIMARY KEY (`occurrence_id`), + UNIQUE KEY `hash` (`hash`), + KEY `event_id` (`event_id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_tec_occurrences` +-- + +LOCK TABLES `wp_tec_occurrences` WRITE; +/*!40000 ALTER TABLE `wp_tec_occurrences` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_tec_occurrences` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_term_relationships` +-- + +DROP TABLE IF EXISTS `wp_term_relationships`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_term_relationships` ( + `object_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `term_order` int(11) NOT NULL DEFAULT 0, + PRIMARY KEY (`object_id`,`term_taxonomy_id`), + KEY `term_taxonomy_id` (`term_taxonomy_id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_term_relationships` +-- + +LOCK TABLES `wp_term_relationships` WRITE; +/*!40000 ALTER TABLE `wp_term_relationships` DISABLE KEYS */; +INSERT INTO `wp_term_relationships` VALUES (6,2,0),(7,2,0); +/*!40000 ALTER TABLE `wp_term_relationships` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_term_taxonomy` +-- + +DROP TABLE IF EXISTS `wp_term_taxonomy`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_term_taxonomy` ( + `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `taxonomy` varchar(32) NOT NULL DEFAULT '', + `description` longtext NOT NULL, + `parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `count` bigint(20) NOT NULL DEFAULT 0, + PRIMARY KEY (`term_taxonomy_id`), + UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), + KEY `taxonomy` (`taxonomy`) +) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_term_taxonomy` +-- + +LOCK TABLES `wp_term_taxonomy` WRITE; +/*!40000 ALTER TABLE `wp_term_taxonomy` DISABLE KEYS */; +INSERT INTO `wp_term_taxonomy` VALUES (1,1,'category','',0,0),(2,2,'wp_theme','',0,2); +/*!40000 ALTER TABLE `wp_term_taxonomy` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_termmeta` +-- + +DROP TABLE IF EXISTS `wp_termmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_termmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `term_id` (`term_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_termmeta` +-- + +LOCK TABLES `wp_termmeta` WRITE; +/*!40000 ALTER TABLE `wp_termmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_termmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_terms` +-- + +DROP TABLE IF EXISTS `wp_terms`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_terms` ( + `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `name` varchar(200) NOT NULL DEFAULT '', + `slug` varchar(200) NOT NULL DEFAULT '', + `term_group` bigint(10) NOT NULL DEFAULT 0, + PRIMARY KEY (`term_id`), + KEY `slug` (`slug`(191)), + KEY `name` (`name`(191)) +) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_terms` +-- + +LOCK TABLES `wp_terms` WRITE; +/*!40000 ALTER TABLE `wp_terms` DISABLE KEYS */; +INSERT INTO `wp_terms` VALUES (1,'Uncategorized','uncategorized',0),(2,'tec','tec',0); +/*!40000 ALTER TABLE `wp_terms` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_usermeta` +-- + +DROP TABLE IF EXISTS `wp_usermeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_usermeta` ( + `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`umeta_id`), + KEY `user_id` (`user_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB AUTO_INCREMENT=21 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_usermeta` +-- + +LOCK TABLES `wp_usermeta` WRITE; +/*!40000 ALTER TABLE `wp_usermeta` DISABLE KEYS */; +INSERT INTO `wp_usermeta` VALUES (1,1,'nickname','admin'),(2,1,'first_name',''),(3,1,'last_name',''),(4,1,'description',''),(5,1,'rich_editing','true'),(6,1,'syntax_highlighting','true'),(7,1,'comment_shortcuts','false'),(8,1,'admin_color','fresh'),(9,1,'use_ssl','0'),(10,1,'show_admin_bar_front','true'),(11,1,'locale',''),(12,1,'wp_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wp_user_level','10'),(14,1,'dismissed_wp_pointers',''),(15,1,'show_welcome_panel','0'),(16,1,'session_tokens','a:2:{s:64:\"54e0a133fb0678671cf04a8886c6909f49ba0a7b53dc5f92bf8059b7b3e40346\";a:4:{s:10:\"expiration\";i:1706627684;s:2:\"ip\";s:10:\"172.18.0.5\";s:2:\"ua\";s:114:\"Mozilla/5.0 (X11; Linux aarch64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/98.0.4758.102 Safari/537.36\";s:5:\"login\";i:1706454884;}s:64:\"6fae7d352e959b6b6f4b30ef72f8bd250b076e657ff938127c343c5fbd08daeb\";a:4:{s:10:\"expiration\";i:1706627812;s:2:\"ip\";s:10:\"172.18.0.1\";s:2:\"ua\";s:84:\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:122.0) Gecko/20100101 Firefox/122.0\";s:5:\"login\";i:1706455012;}}'),(17,1,'wp_user-settings','mfold=o'),(18,1,'wp_user-settings-time','1697535621'),(19,1,'wp_dashboard_quick_press_last_post_id','4'),(20,1,'community-events-location','a:1:{s:2:\"ip\";s:10:\"172.18.0.0\";}'); +/*!40000 ALTER TABLE `wp_usermeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_users` +-- + +DROP TABLE IF EXISTS `wp_users`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_users` ( + `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_login` varchar(60) NOT NULL DEFAULT '', + `user_pass` varchar(255) NOT NULL DEFAULT '', + `user_nicename` varchar(50) NOT NULL DEFAULT '', + `user_email` varchar(100) NOT NULL DEFAULT '', + `user_url` varchar(100) NOT NULL DEFAULT '', + `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `user_activation_key` varchar(255) NOT NULL DEFAULT '', + `user_status` int(11) NOT NULL DEFAULT 0, + `display_name` varchar(250) NOT NULL DEFAULT '', + PRIMARY KEY (`ID`), + KEY `user_login_key` (`user_login`), + KEY `user_nicename` (`user_nicename`), + KEY `user_email` (`user_email`) +) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_users` +-- + +LOCK TABLES `wp_users` WRITE; +/*!40000 ALTER TABLE `wp_users` DISABLE KEYS */; +INSERT INTO `wp_users` VALUES (1,'admin','$P$BcXEl2qeHY.vvWz0MdOCCjwWXopOrO.','admin','','http://wordpress.test','2023-10-17 09:31:26','',0,'admin'); +/*!40000 ALTER TABLE `wp_users` ENABLE KEYS */; +UNLOCK TABLES; +/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; + +/*!40101 SET SQL_MODE=@OLD_SQL_MODE */; +/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; +/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; +/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; +/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; +/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; +/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; + +-- Dump completed on 2024-01-28 15:54:45 diff --git a/tests/_data/empty.sql b/tests/_data/empty.sql index 8c699d7aa3..23e8081c3a 100644 --- a/tests/_data/empty.sql +++ b/tests/_data/empty.sql @@ -1,8 +1,8 @@ --- MariaDB dump 10.19 Distrib 10.5.15-MariaDB, for debian-linux-gnu (x86_64) +-- MariaDB dump 10.19 Distrib 10.5.23-MariaDB, for debian-linux-gnu (aarch64) -- -- Host: db Database: test -- ------------------------------------------------------ --- Server version 10.7.3-MariaDB-1:10.7.3+maria~focal +-- Server version 10.7.8-MariaDB-1:10.7.8+maria~ubu2004 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; @@ -24,18 +24,18 @@ DROP TABLE IF EXISTS `wp_actionscheduler_actions`; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_actionscheduler_actions` ( `action_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `hook` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL, - `status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL, + `hook` varchar(191) NOT NULL, + `status` varchar(20) NOT NULL, `scheduled_date_gmt` datetime DEFAULT '0000-00-00 00:00:00', `scheduled_date_local` datetime DEFAULT '0000-00-00 00:00:00', - `args` varchar(191) COLLATE utf8mb4_unicode_ci DEFAULT NULL, - `schedule` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL, + `args` varchar(191) DEFAULT NULL, + `schedule` longtext DEFAULT NULL, `group_id` bigint(20) unsigned NOT NULL DEFAULT 0, `attempts` int(11) NOT NULL DEFAULT 0, `last_attempt_gmt` datetime DEFAULT '0000-00-00 00:00:00', `last_attempt_local` datetime DEFAULT '0000-00-00 00:00:00', `claim_id` bigint(20) unsigned NOT NULL DEFAULT 0, - `extended_args` varchar(8000) COLLATE utf8mb4_unicode_ci DEFAULT NULL, + `extended_args` varchar(8000) DEFAULT NULL, PRIMARY KEY (`action_id`), KEY `hook` (`hook`), KEY `status` (`status`), @@ -90,7 +90,7 @@ DROP TABLE IF EXISTS `wp_actionscheduler_groups`; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_actionscheduler_groups` ( `group_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `slug` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, + `slug` varchar(255) NOT NULL, PRIMARY KEY (`group_id`), KEY `slug` (`slug`(191)) ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; @@ -116,7 +116,7 @@ DROP TABLE IF EXISTS `wp_actionscheduler_logs`; CREATE TABLE `wp_actionscheduler_logs` ( `log_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `action_id` bigint(20) unsigned NOT NULL, - `message` text COLLATE utf8mb4_unicode_ci NOT NULL, + `message` text NOT NULL, `log_date_gmt` datetime DEFAULT '0000-00-00 00:00:00', `log_date_local` datetime DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`log_id`), @@ -145,8 +145,8 @@ DROP TABLE IF EXISTS `wp_commentmeta`; CREATE TABLE `wp_commentmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_id` bigint(20) unsigned NOT NULL DEFAULT 0, - `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, - `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, PRIMARY KEY (`meta_id`), KEY `comment_id` (`comment_id`), KEY `meta_key` (`meta_key`(191)) @@ -172,17 +172,17 @@ DROP TABLE IF EXISTS `wp_comments`; CREATE TABLE `wp_comments` ( `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT 0, - `comment_author` tinytext COLLATE utf8mb4_unicode_ci NOT NULL, - `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', + `comment_author` tinytext NOT NULL, + `comment_author_email` varchar(100) NOT NULL DEFAULT '', + `comment_author_url` varchar(200) NOT NULL DEFAULT '', + `comment_author_IP` varchar(100) NOT NULL DEFAULT '', `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `comment_content` text COLLATE utf8mb4_unicode_ci NOT NULL, + `comment_content` text NOT NULL, `comment_karma` int(11) NOT NULL DEFAULT 0, - `comment_approved` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '1', - `comment_agent` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `comment_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'comment', + `comment_approved` varchar(20) NOT NULL DEFAULT '1', + `comment_agent` varchar(255) NOT NULL DEFAULT '', + `comment_type` varchar(20) NOT NULL DEFAULT 'comment', `comment_parent` bigint(20) unsigned NOT NULL DEFAULT 0, `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, PRIMARY KEY (`comment_ID`), @@ -212,18 +212,18 @@ DROP TABLE IF EXISTS `wp_links`; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_links` ( `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `link_url` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `link_name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `link_image` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `link_target` varchar(25) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `link_description` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `link_visible` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'Y', + `link_url` varchar(255) NOT NULL DEFAULT '', + `link_name` varchar(255) NOT NULL DEFAULT '', + `link_image` varchar(255) NOT NULL DEFAULT '', + `link_target` varchar(25) NOT NULL DEFAULT '', + `link_description` varchar(255) NOT NULL DEFAULT '', + `link_visible` varchar(20) NOT NULL DEFAULT 'Y', `link_owner` bigint(20) unsigned NOT NULL DEFAULT 1, `link_rating` int(11) NOT NULL DEFAULT 0, `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `link_rel` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `link_notes` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL, - `link_rss` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', + `link_rel` varchar(255) NOT NULL DEFAULT '', + `link_notes` mediumtext NOT NULL, + `link_rss` varchar(255) NOT NULL DEFAULT '', PRIMARY KEY (`link_id`), KEY `link_visible` (`link_visible`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; @@ -247,13 +247,13 @@ DROP TABLE IF EXISTS `wp_options`; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_options` ( `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `option_name` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `option_value` longtext COLLATE utf8mb4_unicode_ci NOT NULL, - `autoload` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'yes', + `option_name` varchar(191) NOT NULL DEFAULT '', + `option_value` longtext NOT NULL, + `autoload` varchar(20) NOT NULL DEFAULT 'yes', PRIMARY KEY (`option_id`), UNIQUE KEY `option_name` (`option_name`), KEY `autoload` (`autoload`) -) ENGINE=InnoDB AUTO_INCREMENT=229 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +) ENGINE=InnoDB AUTO_INCREMENT=234 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- @@ -262,7 +262,7 @@ CREATE TABLE `wp_options` ( LOCK TABLES `wp_options` WRITE; /*!40000 ALTER TABLE `wp_options` DISABLE KEYS */; -INSERT INTO `wp_options` VALUES (1,'siteurl','http://wordpress.test','yes'),(2,'home','http://wordpress.test','yes'),(3,'blogname','tribe','yes'),(4,'blogdescription','Just another WordPress site','yes'),(5,'users_can_register','0','yes'),(6,'admin_email','dev-email@flywheel.local','yes'),(7,'start_of_week','1','yes'),(8,'use_balanceTags','0','yes'),(9,'use_smilies','1','yes'),(10,'require_name_email','1','yes'),(11,'comments_notify','1','yes'),(12,'posts_per_rss','10','yes'),(13,'rss_use_excerpt','0','yes'),(14,'mailserver_url','mail.example.com','yes'),(15,'mailserver_login','login@example.com','yes'),(16,'mailserver_pass','password','yes'),(17,'mailserver_port','110','yes'),(18,'default_category','1','yes'),(19,'default_comment_status','open','yes'),(20,'default_ping_status','open','yes'),(21,'default_pingback_flag','1','yes'),(22,'posts_per_page','10','yes'),(23,'date_format','F j, Y','yes'),(24,'time_format','g:i a','yes'),(25,'links_updated_date_format','F j, Y g:i a','yes'),(26,'comment_moderation','0','yes'),(27,'moderation_notify','1','yes'),(28,'permalink_structure','/%postname%/','yes'),(30,'hack_file','0','yes'),(31,'blog_charset','UTF-8','yes'),(32,'moderation_keys','','no'),(34,'category_base','','yes'),(35,'ping_sites','http://rpc.pingomatic.com/','yes'),(36,'comment_max_links','2','yes'),(37,'gmt_offset','0','yes'),(38,'default_email_category','1','yes'),(39,'recently_edited','','no'),(40,'template','twentynineteen','yes'),(41,'stylesheet','twentynineteen','yes'),(44,'comment_registration','0','yes'),(45,'html_type','text/html','yes'),(46,'use_trackback','0','yes'),(47,'default_role','subscriber','yes'),(48,'db_version','53496','yes'),(49,'uploads_use_yearmonth_folders','1','yes'),(50,'upload_path','','yes'),(51,'blog_public','1','yes'),(52,'default_link_category','2','yes'),(53,'show_on_front','posts','yes'),(54,'tag_base','','yes'),(55,'show_avatars','1','yes'),(56,'avatar_rating','G','yes'),(57,'upload_url_path','','yes'),(58,'thumbnail_size_w','150','yes'),(59,'thumbnail_size_h','150','yes'),(60,'thumbnail_crop','1','yes'),(61,'medium_size_w','300','yes'),(62,'medium_size_h','300','yes'),(63,'avatar_default','mystery','yes'),(64,'large_size_w','1024','yes'),(65,'large_size_h','1024','yes'),(66,'image_default_link_type','none','yes'),(67,'image_default_size','','yes'),(68,'image_default_align','','yes'),(69,'close_comments_for_old_posts','0','yes'),(70,'close_comments_days_old','14','yes'),(71,'thread_comments','1','yes'),(72,'thread_comments_depth','5','yes'),(73,'page_comments','0','yes'),(74,'comments_per_page','50','yes'),(75,'default_comments_page','newest','yes'),(76,'comment_order','asc','yes'),(77,'sticky_posts','a:0:{}','yes'),(78,'widget_categories','a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(79,'widget_text','a:0:{}','yes'),(80,'widget_rss','a:0:{}','yes'),(81,'uninstall_plugins','a:0:{}','no'),(82,'timezone_string','','yes'),(83,'page_for_posts','0','yes'),(84,'page_on_front','0','yes'),(85,'default_post_format','0','yes'),(86,'link_manager_enabled','0','yes'),(87,'finished_splitting_shared_terms','1','yes'),(88,'site_icon','0','yes'),(89,'medium_large_size_w','768','yes'),(90,'medium_large_size_h','0','yes'),(91,'wp_page_for_privacy_policy','0','yes'),(92,'show_comments_cookies_opt_in','0','yes'),(93,'initial_db_version','43764','yes'),(94,'wp_user_roles','a:5:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:71:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;s:31:\"read_private_aggregator-records\";b:1;s:23:\"edit_aggregator-records\";b:1;s:30:\"edit_others_aggregator-records\";b:1;s:31:\"edit_private_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:32:\"delete_others_aggregator-records\";b:1;s:33:\"delete_private_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:44:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:31:\"read_private_aggregator-records\";b:1;s:23:\"edit_aggregator-records\";b:1;s:30:\"edit_others_aggregator-records\";b:1;s:31:\"edit_private_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:32:\"delete_others_aggregator-records\";b:1;s:33:\"delete_private_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:15:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:23:\"edit_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:7:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:23:\"edit_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}}','yes'),(95,'fresh_site','1','yes'),(96,'widget_search','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(97,'widget_recent-posts','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(98,'widget_recent-comments','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(99,'widget_archives','a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(100,'widget_meta','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(101,'sidebars_widgets','a:3:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:13:\"array_version\";i:3;}','yes'),(102,'widget_pages','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(103,'widget_calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(104,'widget_media_audio','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(105,'widget_media_image','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(106,'widget_media_gallery','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(107,'widget_media_video','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(108,'nonce_key','cUt`#XO9(ILxCXqfajr1eWn1D?Bt c_`_`Z)&Mc,GtB@s)R.z0{6cH9eAX~z|&lH','no'),(109,'nonce_salt','aO8e;;h]BHqZ#/Nl.9ono5S}r~@falSDm:lJ)UI6%gwL.s20[+2$HmbUUY},wTH{','no'),(110,'widget_tag_cloud','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(111,'widget_nav_menu','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(112,'widget_custom_html','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(113,'cron','a:9:{i:1615573959;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1615595559;a:3:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1615646716;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1615646901;a:1:{s:24:\"tribe_common_log_cleanup\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1615654192;a:1:{s:21:\"tribe-recurrence-cron\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1615655640;a:2:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1615655794;a:1:{s:16:\"tribe_daily_cron\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1648813472;a:1:{s:18:\"wp_https_detection\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}s:7:\"version\";i:2;}','yes'),(114,'theme_mods_twentynineteen','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(141,'recently_activated','a:2:{s:43:\"the-events-calendar/the-events-calendar.php\";i:1648813540;s:34:\"events-pro/events-calendar-pro.php\";i:1547485439;}','yes'),(144,'tribe_events_calendar_options','a:10:{s:14:\"schema-version\";s:3:\"3.9\";s:27:\"recurring_events_are_hidden\";s:6:\"hidden\";s:21:\"previous_ecp_versions\";a:3:{i:0;s:1:\"0\";i:1;s:3:\"4.8\";i:2;s:5:\"5.5.0\";}s:18:\"latest_ecp_version\";s:6:\"5.14.1\";s:39:\"last-update-message-the-events-calendar\";s:5:\"4.7.3\";s:16:\"tribeEnableViews\";a:6:{i:0;s:4:\"list\";i:1;s:5:\"month\";i:2;s:3:\"day\";i:3;s:5:\"photo\";i:4;s:3:\"map\";i:5;s:4:\"week\";}s:18:\"pro-schema-version\";s:3:\"3.9\";s:8:\"did_init\";b:1;s:19:\"tribeEventsTemplate\";s:0:\"\";s:10:\"viewOption\";s:4:\"list\";}','yes'),(145,'widget_tribe-events-list-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(146,'tribe_last_save_post','1648813540.9972','yes'),(162,'auto_core_update_notified','a:4:{s:4:\"type\";s:7:\"success\";s:5:\"email\";s:24:\"dev-email@flywheel.local\";s:7:\"version\";s:5:\"5.0.3\";s:9:\"timestamp\";i:1547484249;}','no'),(184,'widget_tribe-events-adv-list-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(185,'widget_tribe-events-countdown-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(186,'widget_tribe-mini-calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(187,'widget_tribe-events-venue-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(188,'widget_tribe-this-week-events-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(191,'admin_email_lifespan','0','yes'),(192,'disallowed_keys','','no'),(193,'comment_previously_approved','1','yes'),(194,'auto_plugin_theme_update_emails','a:0:{}','no'),(195,'finished_updating_comment_type','1','yes'),(196,'db_upgraded','1','yes'),(200,'tribe_last_updated_option','1648813540.997','yes'),(203,'tribe_last_generate_rewrite_rules','1648813521.3266','yes'),(207,'_site_transient_update_themes','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1615569401;s:7:\"checked\";a:3:{s:14:\"twentynineteen\";s:3:\"1.7\";s:15:\"twentyseventeen\";s:3:\"2.4\";s:12:\"twentytwenty\";s:3:\"1.5\";}s:8:\"response\";a:3:{s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"2.0\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.2.0.zip\";s:8:\"requires\";s:5:\"4.9.6\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentyseventeen\";a:6:{s:5:\"theme\";s:15:\"twentyseventeen\";s:11:\"new_version\";s:3:\"2.6\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentyseventeen/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentyseventeen.2.6.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:12:\"twentytwenty\";a:6:{s:5:\"theme\";s:12:\"twentytwenty\";s:11:\"new_version\";s:3:\"1.7\";s:3:\"url\";s:42:\"https://wordpress.org/themes/twentytwenty/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/twentytwenty.1.7.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}}s:9:\"no_update\";a:0:{}s:12:\"translations\";a:0:{}}','no'),(208,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1648813521;s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:1:{s:43:\"the-events-calendar/the-events-calendar.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:33:\"w.org/plugins/the-events-calendar\";s:4:\"slug\";s:19:\"the-events-calendar\";s:6:\"plugin\";s:43:\"the-events-calendar/the-events-calendar.php\";s:11:\"new_version\";s:6:\"5.14.1\";s:3:\"url\";s:50:\"https://wordpress.org/plugins/the-events-calendar/\";s:7:\"package\";s:69:\"https://downloads.wordpress.org/plugin/the-events-calendar.5.14.1.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-256x256.gif?rev=2516440\";s:2:\"1x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-128x128.gif?rev=2516440\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:75:\"https://ps.w.org/the-events-calendar/assets/banner-1544x500.png?rev=2257622\";s:2:\"1x\";s:74:\"https://ps.w.org/the-events-calendar/assets/banner-772x250.png?rev=2257622\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.6\";}}s:7:\"checked\";a:2:{s:43:\"the-events-calendar/the-events-calendar.php\";s:6:\"5.14.1\";s:27:\"tec-common/tribe-common.php\";s:7:\"4.14.16\";}}','no'),(209,'recovery_keys','a:0:{}','yes'),(212,'widget_block','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(214,'_transient_doing_cron','1648816124.1598310470581054687500','yes'),(218,'active_plugins','a:0:{}','yes'),(223,'rewrite_rules','','yes'),(224,'auto_update_core_dev','enabled','yes'),(225,'auto_update_core_minor','enabled','yes'),(226,'auto_update_core_major','unset','yes'),(227,'wp_force_deactivated_plugins','a:0:{}','yes'),(228,'user_count','1','no'); +INSERT INTO `wp_options` VALUES (1,'siteurl','http://wordpress.test','yes'),(2,'home','http://wordpress.test','yes'),(3,'blogname','tribe','yes'),(4,'blogdescription','Just another WordPress site','yes'),(5,'users_can_register','0','yes'),(6,'admin_email','dev-email@flywheel.local','yes'),(7,'start_of_week','1','yes'),(8,'use_balanceTags','0','yes'),(9,'use_smilies','1','yes'),(10,'require_name_email','1','yes'),(11,'comments_notify','1','yes'),(12,'posts_per_rss','10','yes'),(13,'rss_use_excerpt','0','yes'),(14,'mailserver_url','mail.example.com','yes'),(15,'mailserver_login','login@example.com','yes'),(16,'mailserver_pass','password','yes'),(17,'mailserver_port','110','yes'),(18,'default_category','1','yes'),(19,'default_comment_status','open','yes'),(20,'default_ping_status','open','yes'),(21,'default_pingback_flag','1','yes'),(22,'posts_per_page','10','yes'),(23,'date_format','F j, Y','yes'),(24,'time_format','g:i a','yes'),(25,'links_updated_date_format','F j, Y g:i a','yes'),(26,'comment_moderation','0','yes'),(27,'moderation_notify','1','yes'),(28,'permalink_structure','/%postname%/','yes'),(30,'hack_file','0','yes'),(31,'blog_charset','UTF-8','yes'),(32,'moderation_keys','','no'),(34,'category_base','','yes'),(35,'ping_sites','http://rpc.pingomatic.com/','yes'),(36,'comment_max_links','2','yes'),(37,'gmt_offset','0','yes'),(38,'default_email_category','1','yes'),(39,'recently_edited','','no'),(40,'template','twentynineteen','yes'),(41,'stylesheet','twentynineteen','yes'),(44,'comment_registration','0','yes'),(45,'html_type','text/html','yes'),(46,'use_trackback','0','yes'),(47,'default_role','subscriber','yes'),(48,'db_version','56657','yes'),(49,'uploads_use_yearmonth_folders','1','yes'),(50,'upload_path','','yes'),(51,'blog_public','1','yes'),(52,'default_link_category','2','yes'),(53,'show_on_front','posts','yes'),(54,'tag_base','','yes'),(55,'show_avatars','1','yes'),(56,'avatar_rating','G','yes'),(57,'upload_url_path','','yes'),(58,'thumbnail_size_w','150','yes'),(59,'thumbnail_size_h','150','yes'),(60,'thumbnail_crop','1','yes'),(61,'medium_size_w','300','yes'),(62,'medium_size_h','300','yes'),(63,'avatar_default','mystery','yes'),(64,'large_size_w','1024','yes'),(65,'large_size_h','1024','yes'),(66,'image_default_link_type','none','yes'),(67,'image_default_size','','yes'),(68,'image_default_align','','yes'),(69,'close_comments_for_old_posts','0','yes'),(70,'close_comments_days_old','14','yes'),(71,'thread_comments','1','yes'),(72,'thread_comments_depth','5','yes'),(73,'page_comments','0','yes'),(74,'comments_per_page','50','yes'),(75,'default_comments_page','newest','yes'),(76,'comment_order','asc','yes'),(77,'sticky_posts','a:0:{}','yes'),(78,'widget_categories','a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(79,'widget_text','a:0:{}','yes'),(80,'widget_rss','a:0:{}','yes'),(81,'uninstall_plugins','a:0:{}','no'),(82,'timezone_string','','yes'),(83,'page_for_posts','0','yes'),(84,'page_on_front','0','yes'),(85,'default_post_format','0','yes'),(86,'link_manager_enabled','0','yes'),(87,'finished_splitting_shared_terms','1','yes'),(88,'site_icon','0','yes'),(89,'medium_large_size_w','768','yes'),(90,'medium_large_size_h','0','yes'),(91,'wp_page_for_privacy_policy','0','yes'),(92,'show_comments_cookies_opt_in','0','yes'),(93,'initial_db_version','43764','yes'),(94,'wp_user_roles','a:5:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:71:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;s:31:\"read_private_aggregator-records\";b:1;s:23:\"edit_aggregator-records\";b:1;s:30:\"edit_others_aggregator-records\";b:1;s:31:\"edit_private_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:32:\"delete_others_aggregator-records\";b:1;s:33:\"delete_private_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:44:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:31:\"read_private_aggregator-records\";b:1;s:23:\"edit_aggregator-records\";b:1;s:30:\"edit_others_aggregator-records\";b:1;s:31:\"edit_private_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:32:\"delete_others_aggregator-records\";b:1;s:33:\"delete_private_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:15:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:23:\"edit_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:7:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:23:\"edit_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}}','yes'),(95,'fresh_site','1','yes'),(96,'widget_search','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(97,'widget_recent-posts','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(98,'widget_recent-comments','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(99,'widget_archives','a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(100,'widget_meta','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(101,'sidebars_widgets','a:3:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:13:\"array_version\";i:3;}','yes'),(102,'widget_pages','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(103,'widget_calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(104,'widget_media_audio','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(105,'widget_media_image','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(106,'widget_media_gallery','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(107,'widget_media_video','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(108,'nonce_key','cUt`#XO9(ILxCXqfajr1eWn1D?Bt c_`_`Z)&Mc,GtB@s)R.z0{6cH9eAX~z|&lH','no'),(109,'nonce_salt','aO8e;;h]BHqZ#/Nl.9ono5S}r~@falSDm:lJ)UI6%gwL.s20[+2$HmbUUY},wTH{','no'),(110,'widget_tag_cloud','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(111,'widget_nav_menu','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(112,'widget_custom_html','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(113,'cron','a:9:{i:1717144359;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1717158759;a:3:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1717166716;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1717166901;a:1:{s:24:\"tribe_common_log_cleanup\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1717174192;a:1:{s:21:\"tribe-recurrence-cron\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1717175640;a:1:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1717175794;a:1:{s:16:\"tribe_daily_cron\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1717262040;a:1:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}s:7:\"version\";i:2;}','yes'),(114,'theme_mods_twentynineteen','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(141,'recently_activated','a:2:{s:43:\"the-events-calendar/the-events-calendar.php\";i:1648813540;s:34:\"events-pro/events-calendar-pro.php\";i:1547485439;}','yes'),(144,'tribe_events_calendar_options','a:10:{s:14:\"schema-version\";s:3:\"3.9\";s:27:\"recurring_events_are_hidden\";s:6:\"hidden\";s:21:\"previous_ecp_versions\";a:3:{i:0;s:1:\"0\";i:1;s:3:\"4.8\";i:2;s:5:\"5.5.0\";}s:18:\"latest_ecp_version\";s:6:\"5.14.1\";s:39:\"last-update-message-the-events-calendar\";s:5:\"4.7.3\";s:16:\"tribeEnableViews\";a:6:{i:0;s:4:\"list\";i:1;s:5:\"month\";i:2;s:3:\"day\";i:3;s:5:\"photo\";i:4;s:3:\"map\";i:5;s:4:\"week\";}s:18:\"pro-schema-version\";s:3:\"3.9\";s:8:\"did_init\";b:1;s:19:\"tribeEventsTemplate\";s:0:\"\";s:10:\"viewOption\";s:4:\"list\";}','yes'),(145,'widget_tribe-events-list-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(146,'tribe_last_save_post','1648813540.9972','yes'),(162,'auto_core_update_notified','a:4:{s:4:\"type\";s:7:\"success\";s:5:\"email\";s:24:\"dev-email@flywheel.local\";s:7:\"version\";s:5:\"5.0.3\";s:9:\"timestamp\";i:1547484249;}','no'),(184,'widget_tribe-events-adv-list-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(185,'widget_tribe-events-countdown-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(186,'widget_tribe-mini-calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(187,'widget_tribe-events-venue-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(188,'widget_tribe-this-week-events-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(191,'admin_email_lifespan','0','yes'),(192,'disallowed_keys','','no'),(193,'comment_previously_approved','1','yes'),(194,'auto_plugin_theme_update_emails','a:0:{}','no'),(195,'finished_updating_comment_type','1','yes'),(196,'db_upgraded','1','yes'),(200,'tribe_last_updated_option','1648813540.997','yes'),(203,'tribe_last_generate_rewrite_rules','1648813521.3266','yes'),(207,'_site_transient_update_themes','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1615569401;s:7:\"checked\";a:3:{s:14:\"twentynineteen\";s:3:\"1.7\";s:15:\"twentyseventeen\";s:3:\"2.4\";s:12:\"twentytwenty\";s:3:\"1.5\";}s:8:\"response\";a:3:{s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"2.0\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.2.0.zip\";s:8:\"requires\";s:5:\"4.9.6\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentyseventeen\";a:6:{s:5:\"theme\";s:15:\"twentyseventeen\";s:11:\"new_version\";s:3:\"2.6\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentyseventeen/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentyseventeen.2.6.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:12:\"twentytwenty\";a:6:{s:5:\"theme\";s:12:\"twentytwenty\";s:11:\"new_version\";s:3:\"1.7\";s:3:\"url\";s:42:\"https://wordpress.org/themes/twentytwenty/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/twentytwenty.1.7.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}}s:9:\"no_update\";a:0:{}s:12:\"translations\";a:0:{}}','no'),(208,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1648813521;s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:1:{s:43:\"the-events-calendar/the-events-calendar.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:33:\"w.org/plugins/the-events-calendar\";s:4:\"slug\";s:19:\"the-events-calendar\";s:6:\"plugin\";s:43:\"the-events-calendar/the-events-calendar.php\";s:11:\"new_version\";s:6:\"5.14.1\";s:3:\"url\";s:50:\"https://wordpress.org/plugins/the-events-calendar/\";s:7:\"package\";s:69:\"https://downloads.wordpress.org/plugin/the-events-calendar.5.14.1.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-256x256.gif?rev=2516440\";s:2:\"1x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-128x128.gif?rev=2516440\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:75:\"https://ps.w.org/the-events-calendar/assets/banner-1544x500.png?rev=2257622\";s:2:\"1x\";s:74:\"https://ps.w.org/the-events-calendar/assets/banner-772x250.png?rev=2257622\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.6\";}}s:7:\"checked\";a:2:{s:43:\"the-events-calendar/the-events-calendar.php\";s:6:\"5.14.1\";s:27:\"tec-common/tribe-common.php\";s:7:\"4.14.16\";}}','no'),(209,'recovery_keys','a:0:{}','yes'),(212,'widget_block','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(218,'active_plugins','a:0:{}','yes'),(223,'rewrite_rules','a:93:{s:11:\"^wp-json/?$\";s:22:\"index.php?rest_route=/\";s:14:\"^wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:21:\"^index.php/wp-json/?$\";s:22:\"index.php?rest_route=/\";s:24:\"^index.php/wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:17:\"^wp-sitemap\\.xml$\";s:23:\"index.php?sitemap=index\";s:17:\"^wp-sitemap\\.xsl$\";s:36:\"index.php?sitemap-stylesheet=sitemap\";s:23:\"^wp-sitemap-index\\.xsl$\";s:34:\"index.php?sitemap-stylesheet=index\";s:48:\"^wp-sitemap-([a-z]+?)-([a-z\\d_-]+?)-(\\d+?)\\.xml$\";s:75:\"index.php?sitemap=$matches[1]&sitemap-subtype=$matches[2]&paged=$matches[3]\";s:34:\"^wp-sitemap-([a-z]+?)-(\\d+?)\\.xml$\";s:47:\"index.php?sitemap=$matches[1]&paged=$matches[2]\";s:47:\"category/(.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:42:\"category/(.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:23:\"category/(.+?)/embed/?$\";s:46:\"index.php?category_name=$matches[1]&embed=true\";s:35:\"category/(.+?)/page/?([0-9]{1,})/?$\";s:53:\"index.php?category_name=$matches[1]&paged=$matches[2]\";s:17:\"category/(.+?)/?$\";s:35:\"index.php?category_name=$matches[1]\";s:44:\"tag/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:39:\"tag/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:20:\"tag/([^/]+)/embed/?$\";s:36:\"index.php?tag=$matches[1]&embed=true\";s:32:\"tag/([^/]+)/page/?([0-9]{1,})/?$\";s:43:\"index.php?tag=$matches[1]&paged=$matches[2]\";s:14:\"tag/([^/]+)/?$\";s:25:\"index.php?tag=$matches[1]\";s:45:\"type/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:40:\"type/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:21:\"type/([^/]+)/embed/?$\";s:44:\"index.php?post_format=$matches[1]&embed=true\";s:33:\"type/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?post_format=$matches[1]&paged=$matches[2]\";s:15:\"type/([^/]+)/?$\";s:33:\"index.php?post_format=$matches[1]\";s:12:\"robots\\.txt$\";s:18:\"index.php?robots=1\";s:13:\"favicon\\.ico$\";s:19:\"index.php?favicon=1\";s:48:\".*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$\";s:18:\"index.php?feed=old\";s:20:\".*wp-app\\.php(/.*)?$\";s:19:\"index.php?error=403\";s:18:\".*wp-register.php$\";s:23:\"index.php?register=true\";s:32:\"feed/(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:27:\"(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:8:\"embed/?$\";s:21:\"index.php?&embed=true\";s:20:\"page/?([0-9]{1,})/?$\";s:28:\"index.php?&paged=$matches[1]\";s:41:\"comments/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:36:\"comments/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:17:\"comments/embed/?$\";s:21:\"index.php?&embed=true\";s:44:\"search/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:39:\"search/(.+)/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:20:\"search/(.+)/embed/?$\";s:34:\"index.php?s=$matches[1]&embed=true\";s:32:\"search/(.+)/page/?([0-9]{1,})/?$\";s:41:\"index.php?s=$matches[1]&paged=$matches[2]\";s:14:\"search/(.+)/?$\";s:23:\"index.php?s=$matches[1]\";s:47:\"author/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:42:\"author/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:23:\"author/([^/]+)/embed/?$\";s:44:\"index.php?author_name=$matches[1]&embed=true\";s:35:\"author/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?author_name=$matches[1]&paged=$matches[2]\";s:17:\"author/([^/]+)/?$\";s:33:\"index.php?author_name=$matches[1]\";s:69:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:64:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:45:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/embed/?$\";s:74:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&embed=true\";s:57:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:81:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&paged=$matches[4]\";s:39:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/?$\";s:63:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]\";s:56:\"([0-9]{4})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:51:\"([0-9]{4})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:32:\"([0-9]{4})/([0-9]{1,2})/embed/?$\";s:58:\"index.php?year=$matches[1]&monthnum=$matches[2]&embed=true\";s:44:\"([0-9]{4})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:65:\"index.php?year=$matches[1]&monthnum=$matches[2]&paged=$matches[3]\";s:26:\"([0-9]{4})/([0-9]{1,2})/?$\";s:47:\"index.php?year=$matches[1]&monthnum=$matches[2]\";s:43:\"([0-9]{4})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:38:\"([0-9]{4})/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:19:\"([0-9]{4})/embed/?$\";s:37:\"index.php?year=$matches[1]&embed=true\";s:31:\"([0-9]{4})/page/?([0-9]{1,})/?$\";s:44:\"index.php?year=$matches[1]&paged=$matches[2]\";s:13:\"([0-9]{4})/?$\";s:26:\"index.php?year=$matches[1]\";s:27:\".?.+?/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:37:\".?.+?/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:57:\".?.+?/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:33:\".?.+?/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:16:\"(.?.+?)/embed/?$\";s:41:\"index.php?pagename=$matches[1]&embed=true\";s:20:\"(.?.+?)/trackback/?$\";s:35:\"index.php?pagename=$matches[1]&tb=1\";s:40:\"(.?.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:35:\"(.?.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:28:\"(.?.+?)/page/?([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&paged=$matches[2]\";s:35:\"(.?.+?)/comment-page-([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&cpage=$matches[2]\";s:24:\"(.?.+?)(?:/([0-9]+))?/?$\";s:47:\"index.php?pagename=$matches[1]&page=$matches[2]\";s:27:\"[^/]+/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:37:\"[^/]+/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:57:\"[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\"[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\"[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:33:\"[^/]+/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:16:\"([^/]+)/embed/?$\";s:37:\"index.php?name=$matches[1]&embed=true\";s:20:\"([^/]+)/trackback/?$\";s:31:\"index.php?name=$matches[1]&tb=1\";s:40:\"([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?name=$matches[1]&feed=$matches[2]\";s:35:\"([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?name=$matches[1]&feed=$matches[2]\";s:28:\"([^/]+)/page/?([0-9]{1,})/?$\";s:44:\"index.php?name=$matches[1]&paged=$matches[2]\";s:35:\"([^/]+)/comment-page-([0-9]{1,})/?$\";s:44:\"index.php?name=$matches[1]&cpage=$matches[2]\";s:24:\"([^/]+)(?:/([0-9]+))?/?$\";s:43:\"index.php?name=$matches[1]&page=$matches[2]\";s:16:\"[^/]+/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:26:\"[^/]+/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:46:\"[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:41:\"[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:41:\"[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:22:\"[^/]+/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";}','yes'),(224,'auto_update_core_dev','enabled','yes'),(225,'auto_update_core_minor','enabled','yes'),(226,'auto_update_core_major','unset','yes'),(227,'wp_force_deactivated_plugins','a:0:{}','yes'),(228,'user_count','1','no'),(229,'_site_transient_timeout_theme_roots','1717145856','no'),(230,'_site_transient_theme_roots','a:5:{s:12:\"twentytwenty\";s:7:\"/themes\";s:16:\"twentytwentyfour\";s:7:\"/themes\";s:15:\"twentytwentyone\";s:7:\"/themes\";s:17:\"twentytwentythree\";s:7:\"/themes\";s:15:\"twentytwentytwo\";s:7:\"/themes\";}','no'),(231,'https_detection_errors','a:1:{s:20:\"https_request_failed\";a:1:{i:0;s:21:\"HTTPS request failed.\";}}','yes'),(232,'_transient_health-check-site-status-result','{\"good\":14,\"recommended\":5,\"critical\":4}','yes'),(233,'wp_attachment_pages_enabled','1','yes'); /*!40000 ALTER TABLE `wp_options` ENABLE KEYS */; UNLOCK TABLES; @@ -276,8 +276,8 @@ DROP TABLE IF EXISTS `wp_postmeta`; CREATE TABLE `wp_postmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_id` bigint(20) unsigned NOT NULL DEFAULT 0, - `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, - `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`(191)) @@ -305,24 +305,24 @@ CREATE TABLE `wp_posts` ( `post_author` bigint(20) unsigned NOT NULL DEFAULT 0, `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `post_content` longtext COLLATE utf8mb4_unicode_ci NOT NULL, - `post_title` text COLLATE utf8mb4_unicode_ci NOT NULL, - `post_excerpt` text COLLATE utf8mb4_unicode_ci NOT NULL, - `post_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'publish', - `comment_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', - `ping_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', - `post_password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `post_name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `to_ping` text COLLATE utf8mb4_unicode_ci NOT NULL, - `pinged` text COLLATE utf8mb4_unicode_ci NOT NULL, + `post_content` longtext NOT NULL, + `post_title` text NOT NULL, + `post_excerpt` text NOT NULL, + `post_status` varchar(20) NOT NULL DEFAULT 'publish', + `comment_status` varchar(20) NOT NULL DEFAULT 'open', + `ping_status` varchar(20) NOT NULL DEFAULT 'open', + `post_password` varchar(255) NOT NULL DEFAULT '', + `post_name` varchar(200) NOT NULL DEFAULT '', + `to_ping` text NOT NULL, + `pinged` text NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `post_content_filtered` longtext COLLATE utf8mb4_unicode_ci NOT NULL, + `post_content_filtered` longtext NOT NULL, `post_parent` bigint(20) unsigned NOT NULL DEFAULT 0, - `guid` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', + `guid` varchar(255) NOT NULL DEFAULT '', `menu_order` int(11) NOT NULL DEFAULT 0, - `post_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'post', - `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', + `post_type` varchar(20) NOT NULL DEFAULT 'post', + `post_mime_type` varchar(100) NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT 0, PRIMARY KEY (`ID`), KEY `post_name` (`post_name`(191)), @@ -353,12 +353,12 @@ CREATE TABLE `wp_tec_events` ( `post_id` bigint(20) unsigned NOT NULL, `start_date` datetime NOT NULL, `end_date` datetime DEFAULT NULL, - `timezone` varchar(30) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'UTC', + `timezone` varchar(30) NOT NULL DEFAULT 'UTC', `start_date_utc` datetime NOT NULL, `end_date_utc` datetime DEFAULT NULL, `duration` mediumint(30) DEFAULT 7200, `updated_at` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), - `hash` varchar(40) COLLATE utf8mb4_unicode_ci NOT NULL, + `hash` varchar(40) NOT NULL, PRIMARY KEY (`event_id`), UNIQUE KEY `post_id` (`post_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; @@ -389,7 +389,7 @@ CREATE TABLE `wp_tec_occurrences` ( `end_date` datetime NOT NULL, `end_date_utc` datetime NOT NULL, `duration` mediumint(30) DEFAULT 7200, - `hash` varchar(40) COLLATE utf8mb4_unicode_ci NOT NULL, + `hash` varchar(40) NOT NULL, `updated_at` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), PRIMARY KEY (`occurrence_id`), UNIQUE KEY `hash` (`hash`), @@ -444,8 +444,8 @@ DROP TABLE IF EXISTS `wp_term_taxonomy`; CREATE TABLE `wp_term_taxonomy` ( `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, - `taxonomy` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `description` longtext COLLATE utf8mb4_unicode_ci NOT NULL, + `taxonomy` varchar(32) NOT NULL DEFAULT '', + `description` longtext NOT NULL, `parent` bigint(20) unsigned NOT NULL DEFAULT 0, `count` bigint(20) NOT NULL DEFAULT 0, PRIMARY KEY (`term_taxonomy_id`), @@ -474,8 +474,8 @@ DROP TABLE IF EXISTS `wp_termmeta`; CREATE TABLE `wp_termmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, - `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, - `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, PRIMARY KEY (`meta_id`), KEY `term_id` (`term_id`), KEY `meta_key` (`meta_key`(191)) @@ -500,8 +500,8 @@ DROP TABLE IF EXISTS `wp_terms`; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_terms` ( `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `slug` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', + `name` varchar(200) NOT NULL DEFAULT '', + `slug` varchar(200) NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT 0, PRIMARY KEY (`term_id`), KEY `slug` (`slug`(191)), @@ -529,8 +529,8 @@ DROP TABLE IF EXISTS `wp_usermeta`; CREATE TABLE `wp_usermeta` ( `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, - `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, - `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, PRIMARY KEY (`umeta_id`), KEY `user_id` (`user_id`), KEY `meta_key` (`meta_key`(191)) @@ -556,15 +556,15 @@ DROP TABLE IF EXISTS `wp_users`; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_users` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `user_login` varchar(60) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `user_pass` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `user_nicename` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `user_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', - `user_url` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', + `user_login` varchar(60) NOT NULL DEFAULT '', + `user_pass` varchar(255) NOT NULL DEFAULT '', + `user_nicename` varchar(50) NOT NULL DEFAULT '', + `user_email` varchar(100) NOT NULL DEFAULT '', + `user_url` varchar(100) NOT NULL DEFAULT '', `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', + `user_activation_key` varchar(255) NOT NULL DEFAULT '', `user_status` int(11) NOT NULL DEFAULT 0, - `display_name` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', + `display_name` varchar(250) NOT NULL DEFAULT '', PRIMARY KEY (`ID`), KEY `user_login_key` (`user_login`), KEY `user_nicename` (`user_nicename`), @@ -591,4 +591,4 @@ UNLOCK TABLES; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; --- Dump completed on 2022-09-06 11:51:59 +-- Dump completed on 2024-05-31 8:28:56 diff --git a/tests/_data/remap/organizers/1.json b/tests/_data/remap/organizers/1.json new file mode 100644 index 0000000000..a07613e729 --- /dev/null +++ b/tests/_data/remap/organizers/1.json @@ -0,0 +1,39 @@ +{ + "ID": 3344, + "post_author": 1, + "post_date": "2019-09-18 15:22:45", + "post_date_gmt": "2019-09-18 13:22:45", + "post_content": "Organizer 3344 content", + "post_title": "Organizer 3344", + "post_excerpt": "Organizer 3344 excerpt", + "post_status": "publish", + "comment_status": "closed", + "ping_status": "closed", + "post_password": "", + "post_name": "organizer-3344", + "to_ping": "", + "pinged": "", + "post_modified": "2019-09-18 15:22:45", + "post_modified_gmt": "2019-09-18 13:22:45", + "post_content_filtered": "", + "post_parent": 0, + "guid": "http://products.tribe/?post_type=tribe_organizer&p=3344", + "menu_order": 0, + "post_type": "tribe_organizer", + "post_mime_type": "", + "comment_count": 0, + "meta_input": { + "_OrganizerOrigin": [ + "events-calendar" + ], + "_OrganizerPhone": [ + "111223344" + ], + "_OrganizerWebsite": [ + "http://organizer.org" + ], + "_OrganizerEmail": [ + "organizer@organizer.org" + ] + } +} diff --git a/tests/_data/remap/organizers/1.template.json b/tests/_data/remap/organizers/1.template.json new file mode 100644 index 0000000000..14981df2fc --- /dev/null +++ b/tests/_data/remap/organizers/1.template.json @@ -0,0 +1,39 @@ +{ + "ID": {{ id }}, + "post_author": 1, + "post_date": "2019-09-18 15:22:45", + "post_date_gmt": "2019-09-18 13:22:45", + "post_content": "Organizer {{ id }} content", + "post_title": "Organizer {{ id }}", + "post_excerpt": "Organizer {{ id }} excerpt", + "post_status": "publish", + "comment_status": "closed", + "ping_status": "closed", + "post_password": "", + "post_name": "organizer-{{ id }}", + "to_ping": "", + "pinged": "", + "post_modified": "2019-09-18 15:22:45", + "post_modified_gmt": "2019-09-18 13:22:45", + "post_content_filtered": "", + "post_parent": 0, + "guid": "http://products.tribe/?post_type=tribe_organizer&p={{ id }}", + "menu_order": 0, + "post_type": "tribe_organizer", + "post_mime_type": "", + "comment_count": 0, + "meta_input": { + "_OrganizerOrigin": [ + "events-calendar" + ], + "_OrganizerPhone": [ + "111223344" + ], + "_OrganizerWebsite": [ + "http://organizer.org" + ], + "_OrganizerEmail": [ + "organizer@organizer.org" + ] + } +} diff --git a/tests/_data/remap/organizers/2.json b/tests/_data/remap/organizers/2.json new file mode 100644 index 0000000000..a61855c5a4 --- /dev/null +++ b/tests/_data/remap/organizers/2.json @@ -0,0 +1,39 @@ +{ + "ID": 4344, + "post_author": 1, + "post_date": "2019-09-18 15:22:45", + "post_date_gmt": "2019-09-18 13:22:45", + "post_content": "Organizer 4344 content", + "post_title": "Organizer 4344", + "post_excerpt": "Organizer 4344 excerpt", + "post_status": "publish", + "comment_status": "closed", + "ping_status": "closed", + "post_password": "", + "post_name": "organizer-4344", + "to_ping": "", + "pinged": "", + "post_modified": "2019-09-18 15:22:45", + "post_modified_gmt": "2019-09-18 13:22:45", + "post_content_filtered": "", + "post_parent": 0, + "guid": "http://products.tribe/?post_type=tribe_organizer&p=4344", + "menu_order": 0, + "post_type": "tribe_organizer", + "post_mime_type": "", + "comment_count": 0, + "meta_input": { + "_OrganizerOrigin": [ + "tec" + ], + "_OrganizerPhone": [ + "2027856948" + ], + "_OrganizerWebsite": [ + "http://tec.org" + ], + "_OrganizerEmail": [ + "organizer@tec.org" + ] + } +} diff --git a/tests/_data/remap/organizers/2.template.json b/tests/_data/remap/organizers/2.template.json new file mode 100644 index 0000000000..14981df2fc --- /dev/null +++ b/tests/_data/remap/organizers/2.template.json @@ -0,0 +1,39 @@ +{ + "ID": {{ id }}, + "post_author": 1, + "post_date": "2019-09-18 15:22:45", + "post_date_gmt": "2019-09-18 13:22:45", + "post_content": "Organizer {{ id }} content", + "post_title": "Organizer {{ id }}", + "post_excerpt": "Organizer {{ id }} excerpt", + "post_status": "publish", + "comment_status": "closed", + "ping_status": "closed", + "post_password": "", + "post_name": "organizer-{{ id }}", + "to_ping": "", + "pinged": "", + "post_modified": "2019-09-18 15:22:45", + "post_modified_gmt": "2019-09-18 13:22:45", + "post_content_filtered": "", + "post_parent": 0, + "guid": "http://products.tribe/?post_type=tribe_organizer&p={{ id }}", + "menu_order": 0, + "post_type": "tribe_organizer", + "post_mime_type": "", + "comment_count": 0, + "meta_input": { + "_OrganizerOrigin": [ + "events-calendar" + ], + "_OrganizerPhone": [ + "111223344" + ], + "_OrganizerWebsite": [ + "http://organizer.org" + ], + "_OrganizerEmail": [ + "organizer@organizer.org" + ] + } +} diff --git a/tests/_data/remap/venues/1.json b/tests/_data/remap/venues/1.json new file mode 100644 index 0000000000..b87e7543f6 --- /dev/null +++ b/tests/_data/remap/venues/1.json @@ -0,0 +1,82 @@ +{ + "ID": 2233, + "post_author": 1, + "post_date": "2019-09-17 16:00:32", + "post_date_gmt": "2019-09-17 14:00:32", + "post_content": "Venue 2233 content", + "post_title": "Venue 2233 title", + "post_excerpt": "Venue 2233 excerpt", + "post_status": "publish", + "comment_status": "closed", + "ping_status": "closed", + "post_password": "", + "post_name": "venue-2233", + "to_ping": "", + "pinged": "", + "post_modified": "2019-09-17 16:00:32", + "post_modified_gmt": "2019-09-17 14:00:32", + "post_content_filtered": "", + "post_parent": 0, + "guid": "http://products.tribe/?post_type=tribe_venue&p=2233", + "menu_order": 0, + "post_type": "tribe_venue", + "post_mime_type": "", + "comment_count": 0, + "filter": "raw", + "meta_input": { + "_VenueOrigin": [ + "events-calendar" + ], + "_EventShowMapLink": [ + "1" + ], + "_EventShowMap": [ + "1" + ], + "_VenueShowMapLink": [ + "1" + ], + "_VenueShowMap": [ + "1" + ], + "_VenueAddress": [ + "801 Mt Vernon Pl NW" + ], + "_VenueCity": [ + "Washington" + ], + "_VenueCountry": [ + "United States" + ], + "_VenueProvince": [ + "DC" + ], + "_VenueState": [ + "DC" + ], + "_VenueZip": [ + "20001" + ], + "_VenuePhone": [ + "2024578944" + ], + "_VenueURL": [ + "http://venue.org" + ], + "_VenueStateProvince": [ + "DC" + ], + "_VenueOverwriteCoords": [ + "0" + ], + "_VenueGeoAddress": [ + "801 Mt Vernon Pl NW, Washington, DC 20001" + ], + "_VenueLat": [ + "38.905140" + ], + "_VenueLng": [ + "-77.023140" + ] + } +} \ No newline at end of file diff --git a/tests/_data/remap/venues/1.template.json b/tests/_data/remap/venues/1.template.json new file mode 100644 index 0000000000..dd04a828a9 --- /dev/null +++ b/tests/_data/remap/venues/1.template.json @@ -0,0 +1,82 @@ +{ + "ID": {{ id }}, + "post_author": 1, + "post_date": "2019-09-17 16:00:32", + "post_date_gmt": "2019-09-17 14:00:32", + "post_content": "Venue {{ id }} content", + "post_title": "Venue {{ id }} title", + "post_excerpt": "Venue {{ id }} excerpt", + "post_status": "publish", + "comment_status": "closed", + "ping_status": "closed", + "post_password": "", + "post_name": "venue-{{ id }}", + "to_ping": "", + "pinged": "", + "post_modified": "2019-09-17 16:00:32", + "post_modified_gmt": "2019-09-17 14:00:32", + "post_content_filtered": "", + "post_parent": 0, + "guid": "http://products.tribe/?post_type=tribe_venue&p={{ id }}", + "menu_order": 0, + "post_type": "tribe_venue", + "post_mime_type": "", + "comment_count": 0, + "filter": "raw", + "meta_input": { + "_VenueOrigin": [ + "events-calendar" + ], + "_EventShowMapLink": [ + "1" + ], + "_EventShowMap": [ + "1" + ], + "_VenueShowMapLink": [ + "1" + ], + "_VenueShowMap": [ + "1" + ], + "_VenueAddress": [ + "100 Rue de Le Chat" + ], + "_VenueCity": [ + "Paris" + ], + "_VenueCountry": [ + "France" + ], + "_VenueProvince": [ + "Ile de France" + ], + "_VenueState": [ + "Ile de France" + ], + "_VenueZip": [ + "75019" + ], + "_VenuePhone": [ + "11223344" + ], + "_VenueURL": [ + "http://venue.org" + ], + "_VenueStateProvince": [ + "Ile de France" + ], + "_VenueOverwriteCoords": [ + "0" + ], + "_VenueGeoAddress": [ + "100 Rue de Le Chat Ile de France Paris 75019 France" + ], + "_VenueLat": [ + "48.8624784" + ], + "_VenueLng": [ + "2.3648085" + ] + } +} \ No newline at end of file diff --git a/tests/_data/restv1-dump.sql b/tests/_data/restv1-dump.sql new file mode 100644 index 0000000000..39ce05c449 --- /dev/null +++ b/tests/_data/restv1-dump.sql @@ -0,0 +1,2432 @@ +-- MariaDB dump 10.19 Distrib 10.5.19-MariaDB, for debian-linux-gnu (x86_64) +-- +-- Host: db Database: test +-- ------------------------------------------------------ +-- Server version 10.7.8-MariaDB-1:10.7.8+maria~ubu2004 + +/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; +/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; +/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; +/*!40101 SET NAMES utf8mb4 */; +/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; +/*!40103 SET TIME_ZONE='+00:00' */; +/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; +/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; +/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; +/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; + +-- +-- Table structure for table `wp_actionscheduler_actions` +-- + +DROP TABLE IF EXISTS `wp_actionscheduler_actions`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_actionscheduler_actions` ( + `action_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `hook` varchar(191) NOT NULL, + `status` varchar(20) NOT NULL, + `scheduled_date_gmt` datetime DEFAULT '0000-00-00 00:00:00', + `scheduled_date_local` datetime DEFAULT '0000-00-00 00:00:00', + `args` varchar(191) DEFAULT NULL, + `schedule` longtext DEFAULT NULL, + `group_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `attempts` int(11) NOT NULL DEFAULT 0, + `last_attempt_gmt` datetime DEFAULT '0000-00-00 00:00:00', + `last_attempt_local` datetime DEFAULT '0000-00-00 00:00:00', + `claim_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `extended_args` varchar(8000) DEFAULT NULL, + `priority` tinyint(3) unsigned NOT NULL DEFAULT 10, + PRIMARY KEY (`action_id`), + KEY `hook` (`hook`), + KEY `status` (`status`), + KEY `scheduled_date_gmt` (`scheduled_date_gmt`), + KEY `args` (`args`), + KEY `group_id` (`group_id`), + KEY `last_attempt_gmt` (`last_attempt_gmt`), + KEY `claim_id_status_scheduled_date_gmt` (`claim_id`,`status`,`scheduled_date_gmt`) +) ENGINE=InnoDB AUTO_INCREMENT=19 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_actionscheduler_actions` +-- + +LOCK TABLES `wp_actionscheduler_actions` WRITE; +/*!40000 ALTER TABLE `wp_actionscheduler_actions` DISABLE KEYS */; +INSERT INTO `wp_actionscheduler_actions` VALUES (4,'action_scheduler/migration_hook','complete','2022-12-06 11:25:48','2022-12-06 11:25:48','[]','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1670325948;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1670325948;}',1,1,'2023-01-05 13:11:28','2023-01-05 13:11:28',0,NULL,10),(5,'woocommerce_cleanup_draft_orders','failed','2023-01-05 13:11:56','2023-01-05 13:11:56','[]','O:32:\"ActionScheduler_IntervalSchedule\":5:{s:22:\"\0*\0scheduled_timestamp\";i:1672924316;s:18:\"\0*\0first_timestamp\";i:1672924316;s:13:\"\0*\0recurrence\";i:86400;s:49:\"\0ActionScheduler_IntervalSchedule\0start_timestamp\";i:1672924316;s:53:\"\0ActionScheduler_IntervalSchedule\0interval_in_seconds\";i:86400;}',0,1,'2023-01-05 13:11:56','2023-01-05 13:11:56',0,NULL,10),(6,'woocommerce_cleanup_draft_orders','complete','2023-01-06 13:11:56','2023-01-06 13:11:56','[]','O:32:\"ActionScheduler_IntervalSchedule\":5:{s:22:\"\0*\0scheduled_timestamp\";i:1673010716;s:18:\"\0*\0first_timestamp\";i:1672924316;s:13:\"\0*\0recurrence\";i:86400;s:49:\"\0ActionScheduler_IntervalSchedule\0start_timestamp\";i:1673010716;s:53:\"\0ActionScheduler_IntervalSchedule\0interval_in_seconds\";i:86400;}',0,1,'2023-01-09 14:29:21','2023-01-09 14:29:21',0,NULL,10),(7,'woocommerce_cleanup_draft_orders','complete','2023-01-10 14:29:21','2023-01-10 14:29:21','[]','O:32:\"ActionScheduler_IntervalSchedule\":5:{s:22:\"\0*\0scheduled_timestamp\";i:1673360961;s:18:\"\0*\0first_timestamp\";i:1672924316;s:13:\"\0*\0recurrence\";i:86400;s:49:\"\0ActionScheduler_IntervalSchedule\0start_timestamp\";i:1673360961;s:53:\"\0ActionScheduler_IntervalSchedule\0interval_in_seconds\";i:86400;}',0,1,'2023-11-17 13:20:23','2023-11-17 08:20:23',0,NULL,10),(8,'woocommerce_run_product_attribute_lookup_regeneration_callback','complete','2023-11-17 12:51:37','2023-11-17 07:51:37','[]','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1700225497;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1700225497;}',2,1,'2023-11-17 13:57:26','2023-11-17 08:57:26',0,NULL,10),(9,'woocommerce_run_on_woocommerce_admin_updated','complete','2023-11-17 12:51:36','2023-11-17 07:51:36','[]','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1700225496;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1700225496;}',3,1,'2023-11-17 13:57:15','2023-11-17 08:57:15',0,NULL,10),(10,'woocommerce_run_update_callback','complete','2023-11-17 13:10:23','2023-11-17 08:10:23','{\"update_callback\":\"wc_update_750_add_columns_to_order_stats_table\"}','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1700226623;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1700226623;}',2,1,'2023-11-17 13:54:10','2023-11-17 08:54:10',0,NULL,10),(11,'woocommerce_run_update_callback','complete','2023-11-17 13:10:24','2023-11-17 08:10:24','{\"update_callback\":\"wc_update_750_disable_new_product_management_experience\"}','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1700226624;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1700226624;}',2,1,'2023-11-17 13:54:22','2023-11-17 08:54:22',0,NULL,10),(12,'woocommerce_run_update_callback','complete','2023-11-17 13:10:25','2023-11-17 08:10:25','{\"update_callback\":\"wc_update_770_remove_multichannel_marketing_feature_options\"}','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1700226625;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1700226625;}',2,1,'2023-11-17 13:54:36','2023-11-17 08:54:36',0,NULL,10),(13,'woocommerce_run_update_callback','complete','2023-11-17 13:10:26','2023-11-17 08:10:26','{\"update_callback\":\"wc_update_810_migrate_transactional_metadata_for_hpos\"}','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1700226626;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1700226626;}',2,1,'2023-11-17 13:54:48','2023-11-17 08:54:48',0,NULL,10),(14,'woocommerce_update_db_to_current_version','complete','2023-11-17 13:10:27','2023-11-17 08:10:27','{\"version\":\"8.2.2\"}','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1700226627;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1700226627;}',2,1,'2023-11-17 13:57:37','2023-11-17 08:57:37',0,NULL,10),(15,'woocommerce_cleanup_draft_orders','canceled','2023-11-18 13:20:23','2023-11-18 08:20:23','[]','O:32:\"ActionScheduler_IntervalSchedule\":5:{s:22:\"\0*\0scheduled_timestamp\";i:1700313623;s:18:\"\0*\0first_timestamp\";i:1672924316;s:13:\"\0*\0recurrence\";i:86400;s:49:\"\0ActionScheduler_IntervalSchedule\0start_timestamp\";i:1700313623;s:53:\"\0ActionScheduler_IntervalSchedule\0interval_in_seconds\";i:86400;}',4,0,'0000-00-00 00:00:00','0000-00-00 00:00:00',0,NULL,10),(17,'woocommerce_cleanup_draft_orders','pending','2023-11-17 13:58:44','2023-11-17 08:58:44','[]','O:32:\"ActionScheduler_IntervalSchedule\":5:{s:22:\"\0*\0scheduled_timestamp\";i:1700229524;s:18:\"\0*\0first_timestamp\";i:1700229524;s:13:\"\0*\0recurrence\";i:86400;s:49:\"\0ActionScheduler_IntervalSchedule\0start_timestamp\";i:1700229524;s:53:\"\0ActionScheduler_IntervalSchedule\0interval_in_seconds\";i:86400;}',4,0,'0000-00-00 00:00:00','0000-00-00 00:00:00',0,NULL,10),(18,'action_scheduler/migration_hook','pending','2023-11-17 14:05:59','2023-11-17 09:05:59','[]','O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1700229959;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1700229959;}',1,0,'0000-00-00 00:00:00','0000-00-00 00:00:00',0,NULL,10); +/*!40000 ALTER TABLE `wp_actionscheduler_actions` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_actionscheduler_claims` +-- + +DROP TABLE IF EXISTS `wp_actionscheduler_claims`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_actionscheduler_claims` ( + `claim_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `date_created_gmt` datetime DEFAULT '0000-00-00 00:00:00', + PRIMARY KEY (`claim_id`), + KEY `date_created_gmt` (`date_created_gmt`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_actionscheduler_claims` +-- + +LOCK TABLES `wp_actionscheduler_claims` WRITE; +/*!40000 ALTER TABLE `wp_actionscheduler_claims` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_actionscheduler_claims` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_actionscheduler_groups` +-- + +DROP TABLE IF EXISTS `wp_actionscheduler_groups`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_actionscheduler_groups` ( + `group_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `slug` varchar(255) NOT NULL, + PRIMARY KEY (`group_id`), + KEY `slug` (`slug`(191)) +) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_actionscheduler_groups` +-- + +LOCK TABLES `wp_actionscheduler_groups` WRITE; +/*!40000 ALTER TABLE `wp_actionscheduler_groups` DISABLE KEYS */; +INSERT INTO `wp_actionscheduler_groups` VALUES (1,'action-scheduler-migration'),(2,'woocommerce-db-updates'),(3,'woocommerce-remote-inbox-engine'),(4,''); +/*!40000 ALTER TABLE `wp_actionscheduler_groups` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_actionscheduler_logs` +-- + +DROP TABLE IF EXISTS `wp_actionscheduler_logs`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_actionscheduler_logs` ( + `log_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `action_id` bigint(20) unsigned NOT NULL, + `message` text NOT NULL, + `log_date_gmt` datetime DEFAULT '0000-00-00 00:00:00', + `log_date_local` datetime DEFAULT '0000-00-00 00:00:00', + PRIMARY KEY (`log_id`), + KEY `action_id` (`action_id`), + KEY `log_date_gmt` (`log_date_gmt`) +) ENGINE=InnoDB AUTO_INCREMENT=45 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_actionscheduler_logs` +-- + +LOCK TABLES `wp_actionscheduler_logs` WRITE; +/*!40000 ALTER TABLE `wp_actionscheduler_logs` DISABLE KEYS */; +INSERT INTO `wp_actionscheduler_logs` VALUES (7,4,'action created','2022-12-06 11:24:48','2022-12-06 11:24:48'),(8,4,'action started via Async Request','2023-01-05 13:11:28','2023-01-05 13:11:28'),(9,4,'action complete via Async Request','2023-01-05 13:11:28','2023-01-05 13:11:28'),(10,5,'action created','2023-01-05 13:11:56','2023-01-05 13:11:56'),(11,5,'action started via WP Cron','2023-01-05 13:11:56','2023-01-05 13:11:56'),(12,5,'action failed via WP Cron: Scheduled action for woocommerce_cleanup_draft_orders will not be executed as no callbacks are registered.','2023-01-05 13:11:56','2023-01-05 13:11:56'),(13,6,'action created','2023-01-05 13:11:56','2023-01-05 13:11:56'),(14,6,'action started via Async Request','2023-01-09 14:29:21','2023-01-09 14:29:21'),(15,6,'action complete via Async Request','2023-01-09 14:29:21','2023-01-09 14:29:21'),(16,7,'action created','2023-01-09 14:29:21','2023-01-09 14:29:21'),(17,8,'action created','2023-11-17 12:51:36','2023-11-17 07:51:36'),(18,9,'action created','2023-11-17 12:51:36','2023-11-17 07:51:36'),(19,10,'action created','2023-11-17 13:10:23','2023-11-17 08:10:23'),(20,11,'action created','2023-11-17 13:10:23','2023-11-17 08:10:23'),(21,12,'action created','2023-11-17 13:10:23','2023-11-17 08:10:23'),(22,13,'action created','2023-11-17 13:10:23','2023-11-17 08:10:23'),(23,14,'action created','2023-11-17 13:10:23','2023-11-17 08:10:23'),(24,7,'action started via Admin List Table','2023-11-17 13:20:23','2023-11-17 08:20:23'),(25,7,'action complete via Admin List Table','2023-11-17 13:20:23','2023-11-17 08:20:23'),(26,15,'action created','2023-11-17 13:20:23','2023-11-17 08:20:23'),(27,10,'action started via Admin List Table','2023-11-17 13:54:10','2023-11-17 08:54:10'),(28,10,'action complete via Admin List Table','2023-11-17 13:54:10','2023-11-17 08:54:10'),(29,11,'action started via Admin List Table','2023-11-17 13:54:22','2023-11-17 08:54:22'),(30,11,'action complete via Admin List Table','2023-11-17 13:54:22','2023-11-17 08:54:22'),(31,12,'action started via Admin List Table','2023-11-17 13:54:36','2023-11-17 08:54:36'),(32,12,'action complete via Admin List Table','2023-11-17 13:54:36','2023-11-17 08:54:36'),(33,13,'action started via Admin List Table','2023-11-17 13:54:48','2023-11-17 08:54:48'),(34,13,'action complete via Admin List Table','2023-11-17 13:54:48','2023-11-17 08:54:48'),(35,9,'action started via Admin List Table','2023-11-17 13:57:14','2023-11-17 08:57:14'),(36,9,'action complete via Admin List Table','2023-11-17 13:57:15','2023-11-17 08:57:15'),(37,8,'action started via Admin List Table','2023-11-17 13:57:26','2023-11-17 08:57:26'),(38,8,'action complete via Admin List Table','2023-11-17 13:57:26','2023-11-17 08:57:26'),(39,14,'action started via Admin List Table','2023-11-17 13:57:37','2023-11-17 08:57:37'),(40,14,'action complete via Admin List Table','2023-11-17 13:57:37','2023-11-17 08:57:37'),(41,15,'action canceled','2023-11-17 13:58:07','2023-11-17 08:58:07'),(43,17,'action created','2023-11-17 13:58:44','2023-11-17 08:58:44'),(44,18,'action created','2023-11-17 14:04:59','2023-11-17 09:04:59'); +/*!40000 ALTER TABLE `wp_actionscheduler_logs` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_commentmeta` +-- + +DROP TABLE IF EXISTS `wp_commentmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_commentmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `comment_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `comment_id` (`comment_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_commentmeta` +-- + +LOCK TABLES `wp_commentmeta` WRITE; +/*!40000 ALTER TABLE `wp_commentmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_commentmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_comments` +-- + +DROP TABLE IF EXISTS `wp_comments`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_comments` ( + `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT 0, + `comment_author` tinytext NOT NULL, + `comment_author_email` varchar(100) NOT NULL DEFAULT '', + `comment_author_url` varchar(200) NOT NULL DEFAULT '', + `comment_author_IP` varchar(100) NOT NULL DEFAULT '', + `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `comment_content` text NOT NULL, + `comment_karma` int(11) NOT NULL DEFAULT 0, + `comment_approved` varchar(20) NOT NULL DEFAULT '1', + `comment_agent` varchar(255) NOT NULL DEFAULT '', + `comment_type` varchar(20) NOT NULL DEFAULT 'comment', + `comment_parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + PRIMARY KEY (`comment_ID`), + KEY `comment_post_ID` (`comment_post_ID`), + KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), + KEY `comment_date_gmt` (`comment_date_gmt`), + KEY `comment_parent` (`comment_parent`), + KEY `comment_author_email` (`comment_author_email`(10)), + KEY `woo_idx_comment_type` (`comment_type`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_comments` +-- + +LOCK TABLES `wp_comments` WRITE; +/*!40000 ALTER TABLE `wp_comments` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_comments` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_adjustmentmeta` +-- + +DROP TABLE IF EXISTS `wp_edd_adjustmentmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_adjustmentmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `edd_adjustment_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `edd_adjustment_id` (`edd_adjustment_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_adjustmentmeta` +-- + +LOCK TABLES `wp_edd_adjustmentmeta` WRITE; +/*!40000 ALTER TABLE `wp_edd_adjustmentmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_adjustmentmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_adjustments` +-- + +DROP TABLE IF EXISTS `wp_edd_adjustments`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_adjustments` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `name` varchar(200) NOT NULL DEFAULT '', + `code` varchar(50) NOT NULL DEFAULT '', + `status` varchar(20) NOT NULL DEFAULT '', + `type` varchar(20) NOT NULL DEFAULT '', + `scope` varchar(20) NOT NULL DEFAULT 'all', + `amount_type` varchar(20) NOT NULL DEFAULT '', + `amount` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `description` longtext NOT NULL, + `max_uses` bigint(20) unsigned NOT NULL DEFAULT 0, + `use_count` bigint(20) unsigned NOT NULL DEFAULT 0, + `once_per_customer` int(1) NOT NULL DEFAULT 0, + `min_charge_amount` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `start_date` datetime DEFAULT NULL, + `end_date` datetime DEFAULT NULL, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `type_status` (`type`,`status`), + KEY `code` (`code`), + KEY `date_created` (`date_created`), + KEY `date_start_end` (`start_date`,`end_date`), + KEY `type_status_dates` (`type`,`status`,`start_date`,`end_date`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_adjustments` +-- + +LOCK TABLES `wp_edd_adjustments` WRITE; +/*!40000 ALTER TABLE `wp_edd_adjustments` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_adjustments` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_customer_addresses` +-- + +DROP TABLE IF EXISTS `wp_edd_customer_addresses`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_customer_addresses` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `customer_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `is_primary` tinyint(1) NOT NULL DEFAULT 0, + `type` varchar(20) NOT NULL DEFAULT 'billing', + `status` varchar(20) NOT NULL DEFAULT 'active', + `name` mediumtext NOT NULL, + `address` mediumtext NOT NULL, + `address2` mediumtext NOT NULL, + `city` mediumtext NOT NULL, + `region` mediumtext NOT NULL, + `postal_code` varchar(32) NOT NULL DEFAULT '', + `country` mediumtext NOT NULL, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `customer_is_primary` (`customer_id`,`is_primary`), + KEY `type` (`type`), + KEY `status` (`status`), + KEY `date_created` (`date_created`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_customer_addresses` +-- + +LOCK TABLES `wp_edd_customer_addresses` WRITE; +/*!40000 ALTER TABLE `wp_edd_customer_addresses` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_customer_addresses` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_customer_email_addresses` +-- + +DROP TABLE IF EXISTS `wp_edd_customer_email_addresses`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_customer_email_addresses` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `customer_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `type` varchar(20) NOT NULL DEFAULT 'secondary', + `status` varchar(20) NOT NULL DEFAULT 'active', + `email` varchar(100) NOT NULL DEFAULT '', + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `customer` (`customer_id`), + KEY `email` (`email`), + KEY `type` (`type`), + KEY `status` (`status`), + KEY `date_created` (`date_created`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_customer_email_addresses` +-- + +LOCK TABLES `wp_edd_customer_email_addresses` WRITE; +/*!40000 ALTER TABLE `wp_edd_customer_email_addresses` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_customer_email_addresses` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_customermeta` +-- + +DROP TABLE IF EXISTS `wp_edd_customermeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_customermeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `edd_customer_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `edd_customer_id` (`edd_customer_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_customermeta` +-- + +LOCK TABLES `wp_edd_customermeta` WRITE; +/*!40000 ALTER TABLE `wp_edd_customermeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_customermeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_customers` +-- + +DROP TABLE IF EXISTS `wp_edd_customers`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_customers` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `email` varchar(100) NOT NULL DEFAULT '', + `name` varchar(255) NOT NULL DEFAULT '', + `status` varchar(20) NOT NULL DEFAULT '', + `purchase_value` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `purchase_count` bigint(20) unsigned NOT NULL DEFAULT 0, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + UNIQUE KEY `email` (`email`), + KEY `user` (`user_id`), + KEY `status` (`status`), + KEY `date_created` (`date_created`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_customers` +-- + +LOCK TABLES `wp_edd_customers` WRITE; +/*!40000 ALTER TABLE `wp_edd_customers` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_customers` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_logmeta` +-- + +DROP TABLE IF EXISTS `wp_edd_logmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_logmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `edd_log_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `edd_log_id` (`edd_log_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_logmeta` +-- + +LOCK TABLES `wp_edd_logmeta` WRITE; +/*!40000 ALTER TABLE `wp_edd_logmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_logmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_logs` +-- + +DROP TABLE IF EXISTS `wp_edd_logs`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_logs` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `object_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `object_type` varchar(20) DEFAULT NULL, + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `type` varchar(20) DEFAULT NULL, + `title` varchar(200) DEFAULT NULL, + `content` longtext DEFAULT NULL, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `object_id_type` (`object_id`,`object_type`), + KEY `user_id` (`user_id`), + KEY `type` (`type`), + KEY `date_created` (`date_created`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_logs` +-- + +LOCK TABLES `wp_edd_logs` WRITE; +/*!40000 ALTER TABLE `wp_edd_logs` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_logs` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_logs_api_requestmeta` +-- + +DROP TABLE IF EXISTS `wp_edd_logs_api_requestmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_logs_api_requestmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `edd_logs_api_request_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `edd_logs_api_request_id` (`edd_logs_api_request_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_logs_api_requestmeta` +-- + +LOCK TABLES `wp_edd_logs_api_requestmeta` WRITE; +/*!40000 ALTER TABLE `wp_edd_logs_api_requestmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_logs_api_requestmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_logs_api_requests` +-- + +DROP TABLE IF EXISTS `wp_edd_logs_api_requests`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_logs_api_requests` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `api_key` varchar(32) NOT NULL DEFAULT 'public', + `token` varchar(32) NOT NULL DEFAULT '', + `version` varchar(32) NOT NULL DEFAULT '', + `request` longtext NOT NULL, + `error` longtext NOT NULL, + `ip` varchar(60) NOT NULL DEFAULT '', + `time` varchar(60) NOT NULL DEFAULT '', + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `user_id` (`user_id`), + KEY `date_created` (`date_created`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_logs_api_requests` +-- + +LOCK TABLES `wp_edd_logs_api_requests` WRITE; +/*!40000 ALTER TABLE `wp_edd_logs_api_requests` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_logs_api_requests` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_logs_file_downloadmeta` +-- + +DROP TABLE IF EXISTS `wp_edd_logs_file_downloadmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_logs_file_downloadmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `edd_logs_file_download_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `edd_logs_file_download_id` (`edd_logs_file_download_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_logs_file_downloadmeta` +-- + +LOCK TABLES `wp_edd_logs_file_downloadmeta` WRITE; +/*!40000 ALTER TABLE `wp_edd_logs_file_downloadmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_logs_file_downloadmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_logs_file_downloads` +-- + +DROP TABLE IF EXISTS `wp_edd_logs_file_downloads`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_logs_file_downloads` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `product_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `file_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `order_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `price_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `customer_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `ip` varchar(60) NOT NULL DEFAULT '', + `user_agent` varchar(200) NOT NULL DEFAULT '', + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `customer_id` (`customer_id`), + KEY `product_id` (`product_id`), + KEY `date_created` (`date_created`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_logs_file_downloads` +-- + +LOCK TABLES `wp_edd_logs_file_downloads` WRITE; +/*!40000 ALTER TABLE `wp_edd_logs_file_downloads` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_logs_file_downloads` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_notemeta` +-- + +DROP TABLE IF EXISTS `wp_edd_notemeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_notemeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `edd_note_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `edd_note_id` (`edd_note_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_notemeta` +-- + +LOCK TABLES `wp_edd_notemeta` WRITE; +/*!40000 ALTER TABLE `wp_edd_notemeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_notemeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_notes` +-- + +DROP TABLE IF EXISTS `wp_edd_notes`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_notes` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `object_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `object_type` varchar(20) NOT NULL DEFAULT '', + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `content` longtext NOT NULL, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `object_id_type` (`object_id`,`object_type`), + KEY `user_id` (`user_id`), + KEY `date_created` (`date_created`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_notes` +-- + +LOCK TABLES `wp_edd_notes` WRITE; +/*!40000 ALTER TABLE `wp_edd_notes` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_notes` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_notifications` +-- + +DROP TABLE IF EXISTS `wp_edd_notifications`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_notifications` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `remote_id` varchar(20) DEFAULT NULL, + `source` varchar(20) NOT NULL DEFAULT 'api', + `title` text NOT NULL, + `content` longtext NOT NULL, + `buttons` longtext DEFAULT NULL, + `type` varchar(64) NOT NULL, + `conditions` longtext DEFAULT NULL, + `start` datetime DEFAULT NULL, + `end` datetime DEFAULT NULL, + `dismissed` tinyint(1) unsigned NOT NULL DEFAULT 0, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_updated` datetime NOT NULL DEFAULT current_timestamp(), + PRIMARY KEY (`id`), + KEY `dismissed_start_end` (`dismissed`,`start`,`end`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_notifications` +-- + +LOCK TABLES `wp_edd_notifications` WRITE; +/*!40000 ALTER TABLE `wp_edd_notifications` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_notifications` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_order_addresses` +-- + +DROP TABLE IF EXISTS `wp_edd_order_addresses`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_order_addresses` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `order_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `type` varchar(20) NOT NULL DEFAULT 'billing', + `name` mediumtext NOT NULL, + `address` mediumtext NOT NULL, + `address2` mediumtext NOT NULL, + `city` mediumtext NOT NULL, + `region` mediumtext NOT NULL, + `postal_code` varchar(32) NOT NULL DEFAULT '', + `country` mediumtext NOT NULL, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `order_id` (`order_id`), + KEY `city` (`city`(191)), + KEY `region` (`region`(191)), + KEY `postal_code` (`postal_code`), + KEY `country` (`country`(191)), + KEY `date_created` (`date_created`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_order_addresses` +-- + +LOCK TABLES `wp_edd_order_addresses` WRITE; +/*!40000 ALTER TABLE `wp_edd_order_addresses` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_order_addresses` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_order_adjustmentmeta` +-- + +DROP TABLE IF EXISTS `wp_edd_order_adjustmentmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_order_adjustmentmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `edd_order_adjustment_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `edd_order_adjustment_id` (`edd_order_adjustment_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_order_adjustmentmeta` +-- + +LOCK TABLES `wp_edd_order_adjustmentmeta` WRITE; +/*!40000 ALTER TABLE `wp_edd_order_adjustmentmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_order_adjustmentmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_order_adjustments` +-- + +DROP TABLE IF EXISTS `wp_edd_order_adjustments`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_order_adjustments` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `object_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `object_type` varchar(20) DEFAULT NULL, + `type_id` bigint(20) unsigned DEFAULT NULL, + `type` varchar(20) DEFAULT NULL, + `type_key` varchar(255) DEFAULT NULL, + `description` varchar(100) DEFAULT NULL, + `subtotal` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `tax` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `total` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `rate` decimal(10,5) NOT NULL DEFAULT 1.00000, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `object_id_type` (`object_id`,`object_type`), + KEY `date_created` (`date_created`), + KEY `parent` (`parent`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_order_adjustments` +-- + +LOCK TABLES `wp_edd_order_adjustments` WRITE; +/*!40000 ALTER TABLE `wp_edd_order_adjustments` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_order_adjustments` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_order_itemmeta` +-- + +DROP TABLE IF EXISTS `wp_edd_order_itemmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_order_itemmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `edd_order_item_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `edd_order_item_id` (`edd_order_item_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_order_itemmeta` +-- + +LOCK TABLES `wp_edd_order_itemmeta` WRITE; +/*!40000 ALTER TABLE `wp_edd_order_itemmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_order_itemmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_order_items` +-- + +DROP TABLE IF EXISTS `wp_edd_order_items`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_order_items` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `order_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `product_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `product_name` text NOT NULL, + `price_id` bigint(20) unsigned DEFAULT NULL, + `cart_index` bigint(20) unsigned NOT NULL DEFAULT 0, + `type` varchar(20) NOT NULL DEFAULT 'download', + `status` varchar(20) NOT NULL DEFAULT 'pending', + `quantity` int(11) NOT NULL DEFAULT 0, + `amount` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `subtotal` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `discount` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `tax` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `total` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `rate` decimal(10,5) NOT NULL DEFAULT 1.00000, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `order_product_price_id` (`order_id`,`product_id`,`price_id`), + KEY `type_status` (`type`,`status`), + KEY `parent` (`parent`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_order_items` +-- + +LOCK TABLES `wp_edd_order_items` WRITE; +/*!40000 ALTER TABLE `wp_edd_order_items` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_order_items` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_order_transactions` +-- + +DROP TABLE IF EXISTS `wp_edd_order_transactions`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_order_transactions` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `object_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `object_type` varchar(20) NOT NULL DEFAULT '', + `transaction_id` varchar(256) NOT NULL DEFAULT '', + `gateway` varchar(20) NOT NULL DEFAULT '', + `status` varchar(20) NOT NULL DEFAULT '', + `total` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `rate` decimal(10,5) NOT NULL DEFAULT 1.00000, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `transaction_id` (`transaction_id`(64)), + KEY `gateway` (`gateway`), + KEY `status` (`status`), + KEY `date_created` (`date_created`), + KEY `object_type_object_id` (`object_type`,`object_id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_order_transactions` +-- + +LOCK TABLES `wp_edd_order_transactions` WRITE; +/*!40000 ALTER TABLE `wp_edd_order_transactions` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_order_transactions` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_ordermeta` +-- + +DROP TABLE IF EXISTS `wp_edd_ordermeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_ordermeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `edd_order_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `edd_order_id` (`edd_order_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_ordermeta` +-- + +LOCK TABLES `wp_edd_ordermeta` WRITE; +/*!40000 ALTER TABLE `wp_edd_ordermeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_ordermeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_edd_orders` +-- + +DROP TABLE IF EXISTS `wp_edd_orders`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_edd_orders` ( + `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `order_number` varchar(255) NOT NULL DEFAULT '', + `status` varchar(20) NOT NULL DEFAULT 'pending', + `type` varchar(20) NOT NULL DEFAULT 'sale', + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `customer_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `email` varchar(100) NOT NULL DEFAULT '', + `ip` varchar(60) NOT NULL DEFAULT '', + `gateway` varchar(100) NOT NULL DEFAULT 'manual', + `mode` varchar(20) NOT NULL DEFAULT '', + `currency` varchar(20) NOT NULL DEFAULT '', + `payment_key` varchar(64) NOT NULL DEFAULT '', + `tax_rate_id` bigint(20) DEFAULT NULL, + `subtotal` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `discount` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `tax` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `total` decimal(18,9) NOT NULL DEFAULT 0.000000000, + `rate` decimal(10,5) NOT NULL DEFAULT 1.00000, + `date_created` datetime NOT NULL DEFAULT current_timestamp(), + `date_modified` datetime NOT NULL DEFAULT current_timestamp(), + `date_completed` datetime DEFAULT NULL, + `date_refundable` datetime DEFAULT NULL, + `date_actions_run` datetime DEFAULT NULL, + `uuid` varchar(100) NOT NULL DEFAULT '', + PRIMARY KEY (`id`), + KEY `order_number` (`order_number`(191)), + KEY `status_type` (`status`,`type`), + KEY `user_id` (`user_id`), + KEY `customer_id` (`customer_id`), + KEY `email` (`email`), + KEY `payment_key` (`payment_key`), + KEY `date_created_completed` (`date_created`,`date_completed`), + KEY `currency` (`currency`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_edd_orders` +-- + +LOCK TABLES `wp_edd_orders` WRITE; +/*!40000 ALTER TABLE `wp_edd_orders` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_edd_orders` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_links` +-- + +DROP TABLE IF EXISTS `wp_links`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_links` ( + `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `link_url` varchar(255) NOT NULL DEFAULT '', + `link_name` varchar(255) NOT NULL DEFAULT '', + `link_image` varchar(255) NOT NULL DEFAULT '', + `link_target` varchar(25) NOT NULL DEFAULT '', + `link_description` varchar(255) NOT NULL DEFAULT '', + `link_visible` varchar(20) NOT NULL DEFAULT 'Y', + `link_owner` bigint(20) unsigned NOT NULL DEFAULT 1, + `link_rating` int(11) NOT NULL DEFAULT 0, + `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `link_rel` varchar(255) NOT NULL DEFAULT '', + `link_notes` mediumtext NOT NULL, + `link_rss` varchar(255) NOT NULL DEFAULT '', + PRIMARY KEY (`link_id`), + KEY `link_visible` (`link_visible`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_links` +-- + +LOCK TABLES `wp_links` WRITE; +/*!40000 ALTER TABLE `wp_links` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_links` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_options` +-- + +DROP TABLE IF EXISTS `wp_options`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_options` ( + `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `option_name` varchar(191) NOT NULL DEFAULT '', + `option_value` longtext NOT NULL, + `autoload` varchar(20) NOT NULL DEFAULT 'yes', + PRIMARY KEY (`option_id`), + UNIQUE KEY `option_name` (`option_name`), + KEY `autoload` (`autoload`) +) ENGINE=InnoDB AUTO_INCREMENT=1056 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_options` +-- + +LOCK TABLES `wp_options` WRITE; +/*!40000 ALTER TABLE `wp_options` DISABLE KEYS */; +INSERT INTO `wp_options` VALUES (1,'siteurl','http://wordpress.test','yes'),(2,'home','http://wordpress.test','yes'),(3,'blogname','Wordpress Test','yes'),(4,'blogdescription','','yes'),(5,'users_can_register','0','yes'),(6,'admin_email','admin@wordpress.test','yes'),(7,'start_of_week','1','yes'),(8,'use_balanceTags','0','yes'),(9,'use_smilies','1','yes'),(10,'require_name_email','1','yes'),(11,'comments_notify','1','yes'),(12,'posts_per_rss','10','yes'),(13,'rss_use_excerpt','0','yes'),(14,'mailserver_url','mail.example.com','yes'),(15,'mailserver_login','login@example.com','yes'),(16,'mailserver_pass','password','yes'),(17,'mailserver_port','110','yes'),(18,'default_category','1','yes'),(19,'default_comment_status','open','yes'),(20,'default_ping_status','open','yes'),(21,'default_pingback_flag','1','yes'),(22,'posts_per_page','10','yes'),(23,'date_format','F j, Y','yes'),(24,'time_format','g:i a','yes'),(25,'links_updated_date_format','F j, Y g:i a','yes'),(26,'comment_moderation','0','yes'),(27,'moderation_notify','1','yes'),(28,'permalink_structure','/%year%/%monthnum%/%day%/%postname%/','yes'),(30,'hack_file','0','yes'),(31,'blog_charset','UTF-8','yes'),(32,'moderation_keys','','no'),(33,'active_plugins','a:6:{i:0;s:49:\"easy-digital-downloads/easy-digital-downloads.php\";i:1;s:35:\"event-automator/event-automator.php\";i:2;s:41:\"event-tickets-plus/event-tickets-plus.php\";i:3;s:31:\"event-tickets/event-tickets.php\";i:4;s:43:\"the-events-calendar/the-events-calendar.php\";i:5;s:27:\"woocommerce/woocommerce.php\";}','yes'),(34,'category_base','','yes'),(35,'ping_sites','http://rpc.pingomatic.com/','yes'),(36,'comment_max_links','2','yes'),(37,'gmt_offset','0','yes'),(38,'default_email_category','1','yes'),(39,'recently_edited','','no'),(40,'template','twentyseventeen','yes'),(41,'stylesheet','twentyseventeen','yes'),(44,'comment_registration','0','yes'),(45,'html_type','text/html','yes'),(46,'use_trackback','0','yes'),(47,'default_role','subscriber','yes'),(48,'db_version','56657','yes'),(49,'uploads_use_yearmonth_folders','1','yes'),(50,'upload_path','','yes'),(51,'blog_public','1','yes'),(52,'default_link_category','2','yes'),(53,'show_on_front','posts','yes'),(54,'tag_base','','yes'),(55,'show_avatars','1','yes'),(56,'avatar_rating','G','yes'),(57,'upload_url_path','','yes'),(58,'thumbnail_size_w','150','yes'),(59,'thumbnail_size_h','150','yes'),(60,'thumbnail_crop','1','yes'),(61,'medium_size_w','300','yes'),(62,'medium_size_h','300','yes'),(63,'avatar_default','mystery','yes'),(64,'large_size_w','1024','yes'),(65,'large_size_h','1024','yes'),(66,'image_default_link_type','none','yes'),(67,'image_default_size','','yes'),(68,'image_default_align','','yes'),(69,'close_comments_for_old_posts','0','yes'),(70,'close_comments_days_old','14','yes'),(71,'thread_comments','1','yes'),(72,'thread_comments_depth','5','yes'),(73,'page_comments','0','yes'),(74,'comments_per_page','50','yes'),(75,'default_comments_page','newest','yes'),(76,'comment_order','asc','yes'),(77,'sticky_posts','a:0:{}','yes'),(78,'widget_categories','a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(79,'widget_text','a:0:{}','yes'),(80,'widget_rss','a:0:{}','yes'),(81,'uninstall_plugins','a:3:{s:43:\"the-events-calendar/the-events-calendar.php\";a:2:{i:0;s:8:\"Freemius\";i:1;s:22:\"_uninstall_plugin_hook\";}s:31:\"event-tickets/event-tickets.php\";a:2:{i:0;s:8:\"Freemius\";i:1;s:22:\"_uninstall_plugin_hook\";}s:35:\"event-automator/event-automator.php\";s:23:\"tec_automator_uninstall\";}','no'),(82,'timezone_string','America/New_York','yes'),(83,'page_for_posts','0','yes'),(84,'page_on_front','0','yes'),(85,'default_post_format','0','yes'),(86,'link_manager_enabled','0','yes'),(87,'finished_splitting_shared_terms','1','yes'),(88,'site_icon','0','yes'),(89,'medium_large_size_w','768','yes'),(90,'medium_large_size_h','0','yes'),(91,'initial_db_version','38590','yes'),(92,'wp_user_roles','a:10:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:199:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;s:31:\"read_private_aggregator-records\";b:1;s:23:\"edit_aggregator-records\";b:1;s:30:\"edit_others_aggregator-records\";b:1;s:31:\"edit_private_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:32:\"delete_others_aggregator-records\";b:1;s:33:\"delete_private_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;s:17:\"view_shop_reports\";b:1;s:24:\"view_shop_sensitive_data\";b:1;s:19:\"export_shop_reports\";b:1;s:21:\"manage_shop_discounts\";b:1;s:20:\"manage_shop_settings\";b:1;s:12:\"edit_product\";b:1;s:12:\"read_product\";b:1;s:14:\"delete_product\";b:1;s:13:\"edit_products\";b:1;s:20:\"edit_others_products\";b:1;s:16:\"publish_products\";b:1;s:21:\"read_private_products\";b:1;s:15:\"delete_products\";b:1;s:23:\"delete_private_products\";b:1;s:25:\"delete_published_products\";b:1;s:22:\"delete_others_products\";b:1;s:21:\"edit_private_products\";b:1;s:23:\"edit_published_products\";b:1;s:20:\"manage_product_terms\";b:1;s:18:\"edit_product_terms\";b:1;s:20:\"delete_product_terms\";b:1;s:20:\"assign_product_terms\";b:1;s:18:\"view_product_stats\";b:1;s:15:\"import_products\";b:1;s:17:\"edit_shop_payment\";b:1;s:17:\"read_shop_payment\";b:1;s:19:\"delete_shop_payment\";b:1;s:18:\"edit_shop_payments\";b:1;s:25:\"edit_others_shop_payments\";b:1;s:21:\"publish_shop_payments\";b:1;s:26:\"read_private_shop_payments\";b:1;s:20:\"delete_shop_payments\";b:1;s:28:\"delete_private_shop_payments\";b:1;s:30:\"delete_published_shop_payments\";b:1;s:27:\"delete_others_shop_payments\";b:1;s:26:\"edit_private_shop_payments\";b:1;s:28:\"edit_published_shop_payments\";b:1;s:25:\"manage_shop_payment_terms\";b:1;s:23:\"edit_shop_payment_terms\";b:1;s:25:\"delete_shop_payment_terms\";b:1;s:25:\"assign_shop_payment_terms\";b:1;s:23:\"view_shop_payment_stats\";b:1;s:20:\"import_shop_payments\";b:1;s:18:\"edit_shop_discount\";b:1;s:18:\"read_shop_discount\";b:1;s:20:\"delete_shop_discount\";b:1;s:19:\"edit_shop_discounts\";b:1;s:26:\"edit_others_shop_discounts\";b:1;s:22:\"publish_shop_discounts\";b:1;s:27:\"read_private_shop_discounts\";b:1;s:21:\"delete_shop_discounts\";b:1;s:29:\"delete_private_shop_discounts\";b:1;s:31:\"delete_published_shop_discounts\";b:1;s:28:\"delete_others_shop_discounts\";b:1;s:27:\"edit_private_shop_discounts\";b:1;s:29:\"edit_published_shop_discounts\";b:1;s:26:\"manage_shop_discount_terms\";b:1;s:24:\"edit_shop_discount_terms\";b:1;s:26:\"delete_shop_discount_terms\";b:1;s:26:\"assign_shop_discount_terms\";b:1;s:24:\"view_shop_discount_stats\";b:1;s:21:\"import_shop_discounts\";b:1;s:18:\"manage_woocommerce\";b:1;s:24:\"view_woocommerce_reports\";b:1;s:15:\"edit_shop_order\";b:1;s:15:\"read_shop_order\";b:1;s:17:\"delete_shop_order\";b:1;s:16:\"edit_shop_orders\";b:1;s:23:\"edit_others_shop_orders\";b:1;s:19:\"publish_shop_orders\";b:1;s:24:\"read_private_shop_orders\";b:1;s:18:\"delete_shop_orders\";b:1;s:26:\"delete_private_shop_orders\";b:1;s:28:\"delete_published_shop_orders\";b:1;s:25:\"delete_others_shop_orders\";b:1;s:24:\"edit_private_shop_orders\";b:1;s:26:\"edit_published_shop_orders\";b:1;s:23:\"manage_shop_order_terms\";b:1;s:21:\"edit_shop_order_terms\";b:1;s:23:\"delete_shop_order_terms\";b:1;s:23:\"assign_shop_order_terms\";b:1;s:16:\"edit_shop_coupon\";b:1;s:16:\"read_shop_coupon\";b:1;s:18:\"delete_shop_coupon\";b:1;s:17:\"edit_shop_coupons\";b:1;s:24:\"edit_others_shop_coupons\";b:1;s:20:\"publish_shop_coupons\";b:1;s:25:\"read_private_shop_coupons\";b:1;s:19:\"delete_shop_coupons\";b:1;s:27:\"delete_private_shop_coupons\";b:1;s:29:\"delete_published_shop_coupons\";b:1;s:26:\"delete_others_shop_coupons\";b:1;s:25:\"edit_private_shop_coupons\";b:1;s:27:\"edit_published_shop_coupons\";b:1;s:24:\"manage_shop_coupon_terms\";b:1;s:22:\"edit_shop_coupon_terms\";b:1;s:24:\"delete_shop_coupon_terms\";b:1;s:24:\"assign_shop_coupon_terms\";b:1;s:25:\"read_private_tribe_events\";b:1;s:17:\"edit_tribe_events\";b:1;s:24:\"edit_others_tribe_events\";b:1;s:25:\"edit_private_tribe_events\";b:1;s:27:\"edit_published_tribe_events\";b:1;s:19:\"delete_tribe_events\";b:1;s:26:\"delete_others_tribe_events\";b:1;s:27:\"delete_private_tribe_events\";b:1;s:29:\"delete_published_tribe_events\";b:1;s:20:\"publish_tribe_events\";b:1;s:25:\"read_private_tribe_venues\";b:1;s:17:\"edit_tribe_venues\";b:1;s:24:\"edit_others_tribe_venues\";b:1;s:25:\"edit_private_tribe_venues\";b:1;s:27:\"edit_published_tribe_venues\";b:1;s:19:\"delete_tribe_venues\";b:1;s:26:\"delete_others_tribe_venues\";b:1;s:27:\"delete_private_tribe_venues\";b:1;s:29:\"delete_published_tribe_venues\";b:1;s:20:\"publish_tribe_venues\";b:1;s:29:\"read_private_tribe_organizers\";b:1;s:21:\"edit_tribe_organizers\";b:1;s:28:\"edit_others_tribe_organizers\";b:1;s:29:\"edit_private_tribe_organizers\";b:1;s:31:\"edit_published_tribe_organizers\";b:1;s:23:\"delete_tribe_organizers\";b:1;s:30:\"delete_others_tribe_organizers\";b:1;s:31:\"delete_private_tribe_organizers\";b:1;s:33:\"delete_published_tribe_organizers\";b:1;s:24:\"publish_tribe_organizers\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:74:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:31:\"read_private_aggregator-records\";b:1;s:23:\"edit_aggregator-records\";b:1;s:30:\"edit_others_aggregator-records\";b:1;s:31:\"edit_private_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:32:\"delete_others_aggregator-records\";b:1;s:33:\"delete_private_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;s:25:\"read_private_tribe_events\";b:1;s:17:\"edit_tribe_events\";b:1;s:24:\"edit_others_tribe_events\";b:1;s:25:\"edit_private_tribe_events\";b:1;s:27:\"edit_published_tribe_events\";b:1;s:19:\"delete_tribe_events\";b:1;s:26:\"delete_others_tribe_events\";b:1;s:27:\"delete_private_tribe_events\";b:1;s:29:\"delete_published_tribe_events\";b:1;s:20:\"publish_tribe_events\";b:1;s:25:\"read_private_tribe_venues\";b:1;s:17:\"edit_tribe_venues\";b:1;s:24:\"edit_others_tribe_venues\";b:1;s:25:\"edit_private_tribe_venues\";b:1;s:27:\"edit_published_tribe_venues\";b:1;s:19:\"delete_tribe_venues\";b:1;s:26:\"delete_others_tribe_venues\";b:1;s:27:\"delete_private_tribe_venues\";b:1;s:29:\"delete_published_tribe_venues\";b:1;s:20:\"publish_tribe_venues\";b:1;s:29:\"read_private_tribe_organizers\";b:1;s:21:\"edit_tribe_organizers\";b:1;s:28:\"edit_others_tribe_organizers\";b:1;s:29:\"edit_private_tribe_organizers\";b:1;s:31:\"edit_published_tribe_organizers\";b:1;s:23:\"delete_tribe_organizers\";b:1;s:30:\"delete_others_tribe_organizers\";b:1;s:31:\"delete_private_tribe_organizers\";b:1;s:33:\"delete_published_tribe_organizers\";b:1;s:24:\"publish_tribe_organizers\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:30:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:23:\"edit_aggregator-records\";b:1;s:33:\"edit_published_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:35:\"delete_published_aggregator-records\";b:1;s:26:\"publish_aggregator-records\";b:1;s:17:\"edit_tribe_events\";b:1;s:27:\"edit_published_tribe_events\";b:1;s:19:\"delete_tribe_events\";b:1;s:29:\"delete_published_tribe_events\";b:1;s:20:\"publish_tribe_events\";b:1;s:17:\"edit_tribe_venues\";b:1;s:27:\"edit_published_tribe_venues\";b:1;s:19:\"delete_tribe_venues\";b:1;s:29:\"delete_published_tribe_venues\";b:1;s:20:\"publish_tribe_venues\";b:1;s:21:\"edit_tribe_organizers\";b:1;s:31:\"edit_published_tribe_organizers\";b:1;s:23:\"delete_tribe_organizers\";b:1;s:33:\"delete_published_tribe_organizers\";b:1;s:24:\"publish_tribe_organizers\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:13:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:23:\"edit_aggregator-records\";b:1;s:25:\"delete_aggregator-records\";b:1;s:17:\"edit_tribe_events\";b:1;s:19:\"delete_tribe_events\";b:1;s:17:\"edit_tribe_venues\";b:1;s:19:\"delete_tribe_venues\";b:1;s:21:\"edit_tribe_organizers\";b:1;s:23:\"delete_tribe_organizers\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}s:12:\"shop_manager\";a:2:{s:4:\"name\";s:12:\"Shop Manager\";s:12:\"capabilities\";a:126:{s:4:\"read\";b:1;s:10:\"edit_posts\";b:1;s:12:\"delete_posts\";b:1;s:15:\"unfiltered_html\";b:1;s:12:\"upload_files\";b:1;s:6:\"export\";b:1;s:6:\"import\";b:1;s:19:\"delete_others_pages\";b:1;s:19:\"delete_others_posts\";b:1;s:12:\"delete_pages\";b:1;s:20:\"delete_private_pages\";b:1;s:20:\"delete_private_posts\";b:1;s:22:\"delete_published_pages\";b:1;s:22:\"delete_published_posts\";b:1;s:17:\"edit_others_pages\";b:1;s:17:\"edit_others_posts\";b:1;s:10:\"edit_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"edit_private_posts\";b:1;s:20:\"edit_published_pages\";b:1;s:20:\"edit_published_posts\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:17:\"moderate_comments\";b:1;s:13:\"publish_pages\";b:1;s:13:\"publish_posts\";b:1;s:18:\"read_private_pages\";b:1;s:18:\"read_private_posts\";b:1;s:17:\"view_shop_reports\";b:1;s:24:\"view_shop_sensitive_data\";b:1;s:19:\"export_shop_reports\";b:1;s:20:\"manage_shop_settings\";b:1;s:21:\"manage_shop_discounts\";b:1;s:12:\"edit_product\";b:1;s:12:\"read_product\";b:1;s:14:\"delete_product\";b:1;s:13:\"edit_products\";b:1;s:20:\"edit_others_products\";b:1;s:16:\"publish_products\";b:1;s:21:\"read_private_products\";b:1;s:15:\"delete_products\";b:1;s:23:\"delete_private_products\";b:1;s:25:\"delete_published_products\";b:1;s:22:\"delete_others_products\";b:1;s:21:\"edit_private_products\";b:1;s:23:\"edit_published_products\";b:1;s:20:\"manage_product_terms\";b:1;s:18:\"edit_product_terms\";b:1;s:20:\"delete_product_terms\";b:1;s:20:\"assign_product_terms\";b:1;s:18:\"view_product_stats\";b:1;s:15:\"import_products\";b:1;s:17:\"edit_shop_payment\";b:1;s:17:\"read_shop_payment\";b:1;s:19:\"delete_shop_payment\";b:1;s:18:\"edit_shop_payments\";b:1;s:25:\"edit_others_shop_payments\";b:1;s:21:\"publish_shop_payments\";b:1;s:26:\"read_private_shop_payments\";b:1;s:20:\"delete_shop_payments\";b:1;s:28:\"delete_private_shop_payments\";b:1;s:30:\"delete_published_shop_payments\";b:1;s:27:\"delete_others_shop_payments\";b:1;s:26:\"edit_private_shop_payments\";b:1;s:28:\"edit_published_shop_payments\";b:1;s:25:\"manage_shop_payment_terms\";b:1;s:23:\"edit_shop_payment_terms\";b:1;s:25:\"delete_shop_payment_terms\";b:1;s:25:\"assign_shop_payment_terms\";b:1;s:23:\"view_shop_payment_stats\";b:1;s:20:\"import_shop_payments\";b:1;s:18:\"edit_shop_discount\";b:1;s:18:\"read_shop_discount\";b:1;s:20:\"delete_shop_discount\";b:1;s:19:\"edit_shop_discounts\";b:1;s:26:\"edit_others_shop_discounts\";b:1;s:22:\"publish_shop_discounts\";b:1;s:27:\"read_private_shop_discounts\";b:1;s:21:\"delete_shop_discounts\";b:1;s:29:\"delete_private_shop_discounts\";b:1;s:31:\"delete_published_shop_discounts\";b:1;s:28:\"delete_others_shop_discounts\";b:1;s:27:\"edit_private_shop_discounts\";b:1;s:29:\"edit_published_shop_discounts\";b:1;s:26:\"manage_shop_discount_terms\";b:1;s:24:\"edit_shop_discount_terms\";b:1;s:26:\"delete_shop_discount_terms\";b:1;s:26:\"assign_shop_discount_terms\";b:1;s:24:\"view_shop_discount_stats\";b:1;s:21:\"import_shop_discounts\";b:1;s:18:\"manage_woocommerce\";b:1;s:24:\"view_woocommerce_reports\";b:1;s:15:\"edit_shop_order\";b:1;s:15:\"read_shop_order\";b:1;s:17:\"delete_shop_order\";b:1;s:16:\"edit_shop_orders\";b:1;s:23:\"edit_others_shop_orders\";b:1;s:19:\"publish_shop_orders\";b:1;s:24:\"read_private_shop_orders\";b:1;s:18:\"delete_shop_orders\";b:1;s:26:\"delete_private_shop_orders\";b:1;s:28:\"delete_published_shop_orders\";b:1;s:25:\"delete_others_shop_orders\";b:1;s:24:\"edit_private_shop_orders\";b:1;s:26:\"edit_published_shop_orders\";b:1;s:23:\"manage_shop_order_terms\";b:1;s:21:\"edit_shop_order_terms\";b:1;s:23:\"delete_shop_order_terms\";b:1;s:23:\"assign_shop_order_terms\";b:1;s:16:\"edit_shop_coupon\";b:1;s:16:\"read_shop_coupon\";b:1;s:18:\"delete_shop_coupon\";b:1;s:17:\"edit_shop_coupons\";b:1;s:24:\"edit_others_shop_coupons\";b:1;s:20:\"publish_shop_coupons\";b:1;s:25:\"read_private_shop_coupons\";b:1;s:19:\"delete_shop_coupons\";b:1;s:27:\"delete_private_shop_coupons\";b:1;s:29:\"delete_published_shop_coupons\";b:1;s:26:\"delete_others_shop_coupons\";b:1;s:25:\"edit_private_shop_coupons\";b:1;s:27:\"edit_published_shop_coupons\";b:1;s:24:\"manage_shop_coupon_terms\";b:1;s:22:\"edit_shop_coupon_terms\";b:1;s:24:\"delete_shop_coupon_terms\";b:1;s:24:\"assign_shop_coupon_terms\";b:1;}}s:15:\"shop_accountant\";a:2:{s:4:\"name\";s:15:\"Shop Accountant\";s:12:\"capabilities\";a:8:{s:4:\"read\";b:1;s:10:\"edit_posts\";b:0;s:12:\"delete_posts\";b:0;s:13:\"edit_products\";b:1;s:21:\"read_private_products\";b:1;s:17:\"view_shop_reports\";b:1;s:19:\"export_shop_reports\";b:1;s:18:\"edit_shop_payments\";b:1;}}s:11:\"shop_worker\";a:2:{s:4:\"name\";s:11:\"Shop Worker\";s:12:\"capabilities\";a:61:{s:4:\"read\";b:1;s:10:\"edit_posts\";b:0;s:12:\"upload_files\";b:1;s:12:\"delete_posts\";b:0;s:12:\"edit_product\";b:1;s:12:\"read_product\";b:1;s:14:\"delete_product\";b:1;s:13:\"edit_products\";b:1;s:20:\"edit_others_products\";b:1;s:16:\"publish_products\";b:1;s:21:\"read_private_products\";b:1;s:15:\"delete_products\";b:1;s:23:\"delete_private_products\";b:1;s:25:\"delete_published_products\";b:1;s:22:\"delete_others_products\";b:1;s:21:\"edit_private_products\";b:1;s:23:\"edit_published_products\";b:1;s:20:\"manage_product_terms\";b:1;s:18:\"edit_product_terms\";b:1;s:20:\"delete_product_terms\";b:1;s:20:\"assign_product_terms\";b:1;s:18:\"view_product_stats\";b:1;s:15:\"import_products\";b:1;s:17:\"edit_shop_payment\";b:1;s:17:\"read_shop_payment\";b:1;s:19:\"delete_shop_payment\";b:1;s:18:\"edit_shop_payments\";b:1;s:25:\"edit_others_shop_payments\";b:1;s:21:\"publish_shop_payments\";b:1;s:26:\"read_private_shop_payments\";b:1;s:20:\"delete_shop_payments\";b:1;s:28:\"delete_private_shop_payments\";b:1;s:30:\"delete_published_shop_payments\";b:1;s:27:\"delete_others_shop_payments\";b:1;s:26:\"edit_private_shop_payments\";b:1;s:28:\"edit_published_shop_payments\";b:1;s:25:\"manage_shop_payment_terms\";b:1;s:23:\"edit_shop_payment_terms\";b:1;s:25:\"delete_shop_payment_terms\";b:1;s:25:\"assign_shop_payment_terms\";b:1;s:23:\"view_shop_payment_stats\";b:1;s:20:\"import_shop_payments\";b:1;s:18:\"edit_shop_discount\";b:1;s:18:\"read_shop_discount\";b:1;s:20:\"delete_shop_discount\";b:1;s:19:\"edit_shop_discounts\";b:1;s:26:\"edit_others_shop_discounts\";b:1;s:22:\"publish_shop_discounts\";b:1;s:27:\"read_private_shop_discounts\";b:1;s:21:\"delete_shop_discounts\";b:1;s:29:\"delete_private_shop_discounts\";b:1;s:31:\"delete_published_shop_discounts\";b:1;s:28:\"delete_others_shop_discounts\";b:1;s:27:\"edit_private_shop_discounts\";b:1;s:29:\"edit_published_shop_discounts\";b:1;s:26:\"manage_shop_discount_terms\";b:1;s:24:\"edit_shop_discount_terms\";b:1;s:26:\"delete_shop_discount_terms\";b:1;s:26:\"assign_shop_discount_terms\";b:1;s:24:\"view_shop_discount_stats\";b:1;s:21:\"import_shop_discounts\";b:1;}}s:11:\"shop_vendor\";a:2:{s:4:\"name\";s:11:\"Shop Vendor\";s:12:\"capabilities\";a:11:{s:4:\"read\";b:1;s:10:\"edit_posts\";b:0;s:12:\"upload_files\";b:1;s:12:\"delete_posts\";b:0;s:12:\"edit_product\";b:1;s:13:\"edit_products\";b:1;s:14:\"delete_product\";b:1;s:15:\"delete_products\";b:1;s:16:\"publish_products\";b:1;s:23:\"edit_published_products\";b:1;s:20:\"assign_product_terms\";b:1;}}s:8:\"customer\";a:2:{s:4:\"name\";s:8:\"Customer\";s:12:\"capabilities\";a:1:{s:4:\"read\";b:1;}}}','yes'),(93,'fresh_site','0','yes'),(94,'widget_search','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(95,'widget_recent-posts','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(96,'widget_recent-comments','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(97,'widget_archives','a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(98,'widget_meta','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(99,'sidebars_widgets','a:5:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:9:\"sidebar-2\";a:0:{}s:9:\"sidebar-3\";a:0:{}s:13:\"array_version\";i:3;}','yes'),(100,'widget_pages','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(101,'widget_calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(102,'widget_media_audio','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(103,'widget_media_image','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(104,'widget_media_gallery','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(105,'widget_media_video','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(106,'widget_tag_cloud','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(107,'widget_nav_menu','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(108,'widget_custom_html','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(109,'cron','a:25:{i:1673274618;a:1:{s:26:\"action_scheduler_run_queue\";a:1:{s:32:\"0d04ed39571b55704c122d726248bbac\";a:3:{s:8:\"schedule\";s:12:\"every_minute\";s:4:\"args\";a:1:{i:0;s:7:\"WP Cron\";}s:8:\"interval\";i:60;}}}i:1673275404;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1673277103;a:1:{s:30:\"edds_cleanup_rate_limiting_log\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1673277119;a:1:{s:33:\"wc_admin_process_orders_milestone\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1673277183;a:1:{s:29:\"wc_admin_unsnooze_admin_notes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1673300624;a:1:{s:21:\"wp_update_user_counts\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1673313245;a:3:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1673343804;a:2:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:16:\"tribe_daily_cron\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1673343824;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1673343826;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1673349849;a:1:{s:24:\"tribe_common_log_cleanup\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1673360959;a:1:{s:14:\"wc_admin_daily\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1673516604;a:1:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}i:1700225491;a:2:{s:20:\"jetpack_clean_nonces\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}s:20:\"jetpack_v2_heartbeat\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1700225506;a:5:{s:33:\"woocommerce_cleanup_personal_data\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:30:\"woocommerce_tracker_send_event\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:30:\"generate_category_lookup_table\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:0:{}}}s:27:\"edd_weekly_scheduled_events\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}s:26:\"edd_daily_scheduled_events\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1700225536;a:1:{s:46:\"tec_tickets_update_glance_item_attendee_counts\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:0:{}}}}i:1700225556;a:1:{s:25:\"woocommerce_geoip_updater\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:11:\"fifteendays\";s:4:\"args\";a:0:{}s:8:\"interval\";i:1296000;}}}i:1700227553;a:1:{s:30:\"wp_delete_temp_updater_backups\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}i:1700229096;a:1:{s:32:\"woocommerce_cancel_unpaid_orders\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:0:{}}}}i:1700229898;a:1:{s:30:\"tribe_schedule_transient_purge\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1700236296;a:2:{s:24:\"woocommerce_cleanup_logs\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:31:\"woocommerce_cleanup_rate_limits\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1700247096;a:1:{s:28:\"woocommerce_cleanup_sessions\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1700283600;a:1:{s:27:\"woocommerce_scheduled_sales\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1700485200;a:1:{s:22:\"edd_email_summary_cron\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:0:{}}}}s:7:\"version\";i:2;}','yes'),(110,'theme_mods_twentyseventeen','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(123,'tribe_last_updated_option','1700230867.2217','yes'),(124,'tribe_events_calendar_options','a:37:{s:8:\"did_init\";b:1;s:19:\"tribeEventsTemplate\";s:0:\"\";s:16:\"tribeEnableViews\";a:3:{i:0;s:4:\"list\";i:1;s:5:\"month\";i:2;s:3:\"day\";}s:10:\"viewOption\";s:4:\"list\";s:14:\"schema-version\";s:5:\"6.2.8\";s:21:\"previous_ecp_versions\";a:6:{i:0;s:1:\"0\";i:1;s:5:\"6.0.2\";i:2;s:7:\"6.0.3.1\";i:3;s:5:\"6.0.5\";i:4;s:7:\"6.0.6.2\";i:5;s:5:\"6.2.7\";}s:18:\"latest_ecp_version\";s:5:\"6.2.8\";s:18:\"dateWithYearFormat\";s:6:\"F j, Y\";s:24:\"recurrenceMaxMonthsAfter\";i:60;s:22:\"google_maps_js_api_key\";s:39:\"AIzaSyDNsicAsP6-VuGtAb1O9riI3oc_NOb7IOU\";s:39:\"last-update-message-the-events-calendar\";s:5:\"6.2.8\";s:25:\"ticket-enabled-post-types\";a:2:{i:0;s:12:\"tribe_events\";i:1;s:4:\"page\";}s:28:\"event-tickets-schema-version\";s:5:\"5.7.0\";s:31:\"previous_event_tickets_versions\";a:4:{i:0;s:1:\"0\";i:1;s:5:\"5.5.4\";i:2;s:5:\"5.5.5\";i:3;s:7:\"5.6.8.1\";}s:28:\"latest_event_tickets_version\";s:5:\"5.7.0\";s:29:\"tribe_tickets_migrate_offset_\";s:8:\"complete\";s:33:\"last-update-message-event-tickets\";s:5:\"5.5.4\";s:36:\"previous_event_tickets_plus_versions\";a:3:{i:0;s:1:\"0\";i:1;s:5:\"5.6.4\";i:2;s:5:\"5.7.7\";}s:33:\"latest_event_tickets_plus_version\";s:5:\"5.8.0\";s:33:\"event-tickets-plus-schema-version\";s:5:\"5.8.0\";s:31:\"tickets-plus-qr-options-api-key\";s:8:\"fb89abb8\";s:24:\"tickets_commerce_enabled\";b:1;s:30:\"tickets-commerce-checkout-page\";s:2:\"16\";s:29:\"tickets-commerce-success-page\";s:2:\"17\";s:24:\"tickets-commerce-sandbox\";b:1;s:31:\"tickets-commerce-stock-handling\";s:7:\"pending\";s:30:\"tickets-commerce-currency-code\";s:3:\"USD\";s:34:\"tickets-commerce-currency-position\";s:6:\"prefix\";s:48:\"tickets-commerce-confirmation-email-sender-email\";s:20:\"admin@wordpress.test\";s:47:\"tickets-commerce-confirmation-email-sender-name\";s:5:\"admin\";s:43:\"tickets-commerce-confirmation-email-subject\";s:17:\"You have tickets!\";s:13:\"earliest_date\";s:19:\"2019-01-01 15:00:00\";s:21:\"earliest_date_markers\";a:1:{i:0;i:18;}s:11:\"latest_date\";s:19:\"2019-01-01 18:00:00\";s:19:\"latest_date_markers\";a:1:{i:0;i:18;}s:30:\"event-automator-schema-version\";s:5:\"1.3.1\";s:13:\"opt-in-status\";b:0;}','yes'),(125,'action_scheduler_hybrid_store_demarkation','1','yes'),(126,'schema-ActionScheduler_StoreSchema','7.0.1700225495','yes'),(127,'schema-ActionScheduler_LoggerSchema','3.0.1666777404','yes'),(130,'tribe_last_save_post','1700229964.4526','yes'),(131,'widget_block','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(132,'widget_tribe-widget-events-list','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(135,'tec_ct1_events_table_schema_version','1.0.1','yes'),(136,'tec_ct1_occurrences_table_schema_version','1.0.2','yes'),(137,'tec_ct1_migration_state','a:3:{s:18:\"complete_timestamp\";N;s:5:\"phase\";s:22:\"migration-not-required\";s:19:\"preview_unsupported\";b:0;}','yes'),(140,'tribe_last_generate_rewrite_rules','1700229966.2584','yes'),(142,'action_scheduler_lock_async-request-runner','6557770429f398.87889553|1700230976','yes'),(144,'fs_active_plugins','O:8:\"stdClass\":2:{s:7:\"plugins\";a:0:{}s:7:\"abspath\";s:54:\"/Users/brianjessee/Local Sites/tribe/tests/app/public/\";}','yes'),(145,'fs_debug_mode','','yes'),(146,'fs_accounts','a:6:{s:21:\"id_slug_type_path_map\";a:2:{i:3069;a:3:{s:4:\"slug\";s:19:\"the-events-calendar\";s:4:\"type\";s:6:\"plugin\";s:4:\"path\";s:43:\"the-events-calendar/the-events-calendar.php\";}i:3841;a:3:{s:4:\"slug\";s:13:\"event-tickets\";s:4:\"type\";s:6:\"plugin\";s:4:\"path\";s:31:\"event-tickets/event-tickets.php\";}}s:11:\"plugin_data\";a:2:{s:19:\"the-events-calendar\";a:16:{s:16:\"plugin_main_file\";O:8:\"stdClass\":1:{s:4:\"path\";s:43:\"the-events-calendar/the-events-calendar.php\";}s:20:\"is_network_activated\";b:0;s:17:\"install_timestamp\";i:1666777406;s:17:\"was_plugin_loaded\";b:1;s:21:\"is_plugin_new_install\";b:0;s:16:\"sdk_last_version\";N;s:11:\"sdk_version\";s:5:\"2.4.4\";s:16:\"sdk_upgrade_mode\";b:1;s:18:\"sdk_downgrade_mode\";b:0;s:19:\"plugin_last_version\";s:5:\"6.0.5\";s:14:\"plugin_version\";s:7:\"6.0.6.2\";s:19:\"plugin_upgrade_mode\";b:1;s:21:\"plugin_downgrade_mode\";b:0;s:17:\"connectivity_test\";a:6:{s:12:\"is_connected\";b:1;s:4:\"host\";s:14:\"wordpress.test\";s:9:\"server_ip\";s:3:\"::1\";s:9:\"is_active\";b:1;s:9:\"timestamp\";i:1666777406;s:7:\"version\";s:5:\"6.0.2\";}s:15:\"prev_is_premium\";b:0;s:12:\"is_anonymous\";a:3:{s:2:\"is\";b:1;s:9:\"timestamp\";i:1667820280;s:7:\"version\";s:7:\"6.0.3.1\";}}s:13:\"event-tickets\";a:16:{s:16:\"plugin_main_file\";O:8:\"stdClass\":1:{s:4:\"path\";s:31:\"event-tickets/event-tickets.php\";}s:20:\"is_network_activated\";b:0;s:17:\"install_timestamp\";i:1670232855;s:17:\"was_plugin_loaded\";b:1;s:21:\"is_plugin_new_install\";b:0;s:16:\"sdk_last_version\";N;s:11:\"sdk_version\";s:5:\"2.4.4\";s:16:\"sdk_upgrade_mode\";b:1;s:18:\"sdk_downgrade_mode\";b:0;s:19:\"plugin_last_version\";s:5:\"5.5.4\";s:14:\"plugin_version\";s:5:\"5.5.5\";s:19:\"plugin_upgrade_mode\";b:1;s:21:\"plugin_downgrade_mode\";b:0;s:17:\"connectivity_test\";a:6:{s:12:\"is_connected\";b:1;s:4:\"host\";s:14:\"wordpress.test\";s:9:\"server_ip\";s:9:\"127.0.0.1\";s:9:\"is_active\";b:1;s:9:\"timestamp\";i:1670232855;s:7:\"version\";s:5:\"5.5.4\";}s:15:\"prev_is_premium\";b:0;s:12:\"is_anonymous\";a:3:{s:2:\"is\";b:1;s:9:\"timestamp\";i:1670232858;s:7:\"version\";s:5:\"5.5.4\";}}}s:13:\"file_slug_map\";a:2:{s:43:\"the-events-calendar/the-events-calendar.php\";s:19:\"the-events-calendar\";s:31:\"event-tickets/event-tickets.php\";s:13:\"event-tickets\";}s:7:\"plugins\";a:2:{s:19:\"the-events-calendar\";O:9:\"FS_Plugin\":23:{s:16:\"parent_plugin_id\";N;s:5:\"title\";s:19:\"The Events Calendar\";s:4:\"slug\";s:19:\"the-events-calendar\";s:12:\"premium_slug\";s:27:\"the-events-calendar-premium\";s:4:\"type\";s:6:\"plugin\";s:20:\"affiliate_moderation\";b:0;s:19:\"is_wp_org_compliant\";b:1;s:22:\"premium_releases_count\";N;s:4:\"file\";s:43:\"the-events-calendar/the-events-calendar.php\";s:7:\"version\";s:7:\"6.0.6.2\";s:11:\"auto_update\";N;s:4:\"info\";N;s:10:\"is_premium\";b:0;s:14:\"premium_suffix\";s:9:\"(Premium)\";s:7:\"is_live\";b:1;s:9:\"bundle_id\";N;s:17:\"bundle_public_key\";N;s:10:\"public_key\";s:32:\"pk_e32061abc28cfedf231f3e5c4e626\";s:10:\"secret_key\";N;s:2:\"id\";s:4:\"3069\";s:7:\"updated\";N;s:7:\"created\";N;s:22:\"\0FS_Entity\0_is_updated\";b:1;}s:13:\"event-tickets\";O:9:\"FS_Plugin\":23:{s:16:\"parent_plugin_id\";N;s:5:\"title\";s:13:\"Event Tickets\";s:4:\"slug\";s:13:\"event-tickets\";s:12:\"premium_slug\";s:21:\"event-tickets-premium\";s:4:\"type\";s:6:\"plugin\";s:20:\"affiliate_moderation\";b:0;s:19:\"is_wp_org_compliant\";b:1;s:22:\"premium_releases_count\";N;s:4:\"file\";s:31:\"event-tickets/event-tickets.php\";s:7:\"version\";s:5:\"5.5.5\";s:11:\"auto_update\";N;s:4:\"info\";N;s:10:\"is_premium\";b:0;s:14:\"premium_suffix\";s:9:\"(Premium)\";s:7:\"is_live\";b:1;s:9:\"bundle_id\";N;s:17:\"bundle_public_key\";N;s:10:\"public_key\";s:32:\"pk_6dd9310b57c62871c59e58b8e739e\";s:10:\"secret_key\";N;s:2:\"id\";s:4:\"3841\";s:7:\"updated\";N;s:7:\"created\";N;s:22:\"\0FS_Entity\0_is_updated\";b:1;}}s:9:\"unique_id\";s:32:\"f780b4baade26d5c042675aa17df5c05\";s:13:\"admin_notices\";a:2:{s:19:\"the-events-calendar\";a:0:{}s:13:\"event-tickets\";a:0:{}}}','yes'),(147,'fs_gdpr','a:2:{s:2:\"u0\";a:1:{s:8:\"required\";b:0;}s:2:\"u1\";a:1:{s:8:\"required\";b:0;}}','yes'),(150,'wp_page_for_privacy_policy','0','yes'),(151,'show_comments_cookies_opt_in','1','yes'),(153,'disallowed_keys','','no'),(154,'comment_previously_approved','1','yes'),(155,'auto_plugin_theme_update_emails','a:0:{}','no'),(156,'auto_update_core_dev','enabled','yes'),(157,'auto_update_core_minor','enabled','yes'),(158,'auto_update_core_major','unset','yes'),(159,'wp_force_deactivated_plugins','a:0:{}','yes'),(160,'finished_updating_comment_type','1','yes'),(161,'user_count','1','no'),(162,'db_upgraded','','yes'),(171,'auto_core_update_notified','a:4:{s:4:\"type\";s:7:\"success\";s:5:\"email\";s:20:\"admin@wordpress.test\";s:7:\"version\";s:5:\"6.1.1\";s:9:\"timestamp\";i:1670232824;}','no'),(172,'recovery_keys','a:1:{s:22:\"XtMzHsMEnupZW70KCLjeTw\";a:2:{s:10:\"hashed_key\";s:34:\"$P$B.xHePRjPeG/X2X7GWPTRH5yp7qCdS/\";s:10:\"created_at\";i:1700228528;}}','yes'),(177,'https_detection_errors','a:1:{s:23:\"ssl_verification_failed\";a:1:{i:0;s:24:\"SSL verification failed.\";}}','yes'),(226,'_transient_health-check-site-status-result','{\"good\":14,\"recommended\":3,\"critical\":1}','yes'),(260,'recently_activated','a:0:{}','yes'),(295,'fs_api_cache','a:0:{}','no'),(397,'tec_timed_tribe_supports_async_process','a:3:{s:3:\"key\";s:28:\"tribe_supports_async_process\";s:5:\"value\";N;s:10:\"expiration\";i:1700230932;}','yes'),(430,'edd_settings','a:6:{s:13:\"purchase_page\";i:4;s:12:\"success_page\";i:5;s:12:\"failure_page\";i:6;s:21:\"purchase_history_page\";i:7;s:17:\"confirmation_page\";i:8;s:20:\"stripe_elements_mode\";s:16:\"payment-elements\";}','yes'),(431,'edd_use_php_sessions','1','yes'),(433,'edd_activation_date','1672924302','yes'),(436,'edd_default_api_version','v2','yes'),(437,'edd_completed_upgrades','a:16:{i:0;s:21:\"upgrade_payment_taxes\";i:1;s:37:\"upgrade_customer_payments_association\";i:2;s:21:\"upgrade_user_api_keys\";i:3;s:25:\"remove_refunded_sale_logs\";i:4;s:29:\"update_file_download_log_data\";i:5;s:17:\"migrate_tax_rates\";i:6;s:17:\"migrate_discounts\";i:7;s:14:\"migrate_orders\";i:8;s:26:\"migrate_customer_addresses\";i:9;s:32:\"migrate_customer_email_addresses\";i:10;s:22:\"migrate_customer_notes\";i:11;s:12:\"migrate_logs\";i:12;s:19:\"migrate_order_notes\";i:13;s:23:\"v30_legacy_data_removed\";i:14;s:28:\"stripe_customer_id_migration\";i:15;s:26:\"migrate_order_actions_date\";}','yes'),(438,'edd_version','3.2.5','yes'),(439,'_transient_edd_cache_excluded_uris','a:4:{i:0;s:3:\"p=4\";i:1;s:3:\"p=5\";i:2;s:9:\"/checkout\";i:3;s:8:\"/receipt\";}','yes'),(440,'widget_edd_cart_widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(441,'widget_edd_categories_tags_widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(442,'widget_edd_product_details','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(444,'_transient_edd-sc-receipt-check','86400','yes'),(445,'edds_stripe_version','2.8.13.1','yes'),(446,'wpdb_edd_customers_version','202303220','yes'),(447,'wpdb_edd_customermeta_version','201807111','yes'),(448,'wpdb_edd_customer_addresses_version','202004051','yes'),(449,'wpdb_edd_customer_email_addresses_version','202002141','yes'),(450,'wpdb_edd_adjustments_version','202307311','yes'),(451,'wpdb_edd_adjustmentmeta_version','201806142','yes'),(452,'wpdb_edd_notes_version','202002141','yes'),(454,'wpdb_edd_notemeta_version','201805221','yes'),(455,'wpdb_edd_orders_version','202307111','yes'),(456,'wpdb_edd_ordermeta_version','201805221','yes'),(457,'wpdb_edd_order_items_version','202110141','yes'),(458,'wpdb_edd_order_itemmeta_version','201805221','yes'),(459,'wpdb_edd_order_adjustments_version','202105221','yes'),(460,'wpdb_edd_order_adjustmentmeta_version','201805221','yes'),(461,'wpdb_edd_order_addresses_version','202002141','yes'),(462,'wpdb_edd_order_transactions_version','202205241','yes'),(463,'wpdb_edd_logs_version','202002141','yes'),(464,'wpdb_edd_logmeta_version','201805221','yes'),(465,'wpdb_edd_logs_api_requests_version','202002141','yes'),(466,'wpdb_edd_logs_api_requestmeta_version','201907291','yes'),(467,'wpdb_edd_logs_file_downloads_version','202002141','yes'),(468,'wpdb_edd_logs_file_downloadmeta_version','201907291','yes'),(469,'edd_licensed_extensions','{\"timeout\":1700317321,\"products\":[]}','no'),(470,'edd_tracking_notice','1','yes'),(475,'woocommerce_schema_version','430','yes'),(476,'woocommerce_store_address','101 South Street','yes'),(477,'woocommerce_store_address_2','','yes'),(478,'woocommerce_store_city','New York','yes'),(479,'woocommerce_default_country','US:NY','yes'),(480,'woocommerce_store_postcode','10001','yes'),(481,'woocommerce_allowed_countries','all','yes'),(482,'woocommerce_all_except_countries','a:0:{}','yes'),(483,'woocommerce_specific_allowed_countries','a:0:{}','yes'),(484,'woocommerce_ship_to_countries','','yes'),(485,'woocommerce_specific_ship_to_countries','a:0:{}','yes'),(486,'woocommerce_default_customer_address','base','yes'),(487,'woocommerce_calc_taxes','no','yes'),(488,'woocommerce_enable_coupons','yes','yes'),(489,'woocommerce_calc_discounts_sequentially','no','no'),(490,'woocommerce_currency','USD','yes'),(491,'woocommerce_currency_pos','left','yes'),(492,'woocommerce_price_thousand_sep',',','yes'),(493,'woocommerce_price_decimal_sep','.','yes'),(494,'woocommerce_price_num_decimals','2','yes'),(495,'woocommerce_shop_page_id','10','yes'),(496,'woocommerce_cart_redirect_after_add','no','yes'),(497,'woocommerce_enable_ajax_add_to_cart','yes','yes'),(498,'woocommerce_placeholder_image','9','yes'),(499,'woocommerce_weight_unit','kg','yes'),(500,'woocommerce_dimension_unit','cm','yes'),(501,'woocommerce_enable_reviews','yes','yes'),(502,'woocommerce_review_rating_verification_label','yes','no'),(503,'woocommerce_review_rating_verification_required','no','no'),(504,'woocommerce_enable_review_rating','yes','yes'),(505,'woocommerce_review_rating_required','yes','no'),(506,'woocommerce_manage_stock','yes','yes'),(507,'woocommerce_hold_stock_minutes','60','no'),(508,'woocommerce_notify_low_stock','yes','no'),(509,'woocommerce_notify_no_stock','yes','no'),(510,'woocommerce_stock_email_recipient','admin@wordpress.test','no'),(511,'woocommerce_notify_low_stock_amount','2','no'),(512,'woocommerce_notify_no_stock_amount','0','yes'),(513,'woocommerce_hide_out_of_stock_items','no','yes'),(514,'woocommerce_stock_format','','yes'),(515,'woocommerce_file_download_method','force','no'),(516,'woocommerce_downloads_redirect_fallback_allowed','no','no'),(517,'woocommerce_downloads_require_login','no','no'),(518,'woocommerce_downloads_grant_access_after_payment','yes','no'),(519,'woocommerce_downloads_deliver_inline','','no'),(520,'woocommerce_downloads_add_hash_to_filename','yes','yes'),(522,'woocommerce_attribute_lookup_direct_updates','no','yes'),(523,'woocommerce_prices_include_tax','no','yes'),(524,'woocommerce_tax_based_on','shipping','yes'),(525,'woocommerce_shipping_tax_class','inherit','yes'),(526,'woocommerce_tax_round_at_subtotal','no','yes'),(527,'woocommerce_tax_classes','','yes'),(528,'woocommerce_tax_display_shop','excl','yes'),(529,'woocommerce_tax_display_cart','excl','yes'),(530,'woocommerce_price_display_suffix','','yes'),(531,'woocommerce_tax_total_display','itemized','no'),(532,'woocommerce_enable_shipping_calc','yes','no'),(533,'woocommerce_shipping_cost_requires_address','no','yes'),(534,'woocommerce_ship_to_destination','billing','no'),(535,'woocommerce_shipping_debug_mode','no','yes'),(536,'woocommerce_enable_guest_checkout','yes','no'),(537,'woocommerce_enable_checkout_login_reminder','no','no'),(538,'woocommerce_enable_signup_and_login_from_checkout','no','no'),(539,'woocommerce_enable_myaccount_registration','no','no'),(540,'woocommerce_registration_generate_username','yes','no'),(541,'woocommerce_registration_generate_password','yes','no'),(542,'woocommerce_erasure_request_removes_order_data','no','no'),(543,'woocommerce_erasure_request_removes_download_data','no','no'),(544,'woocommerce_allow_bulk_remove_personal_data','no','no'),(545,'woocommerce_registration_privacy_policy_text','Your personal data will be used to support your experience throughout this website, to manage access to your account, and for other purposes described in our [privacy_policy].','yes'),(546,'woocommerce_checkout_privacy_policy_text','Your personal data will be used to process your order, support your experience throughout this website, and for other purposes described in our [privacy_policy].','yes'),(547,'woocommerce_delete_inactive_accounts','a:2:{s:6:\"number\";s:0:\"\";s:4:\"unit\";s:6:\"months\";}','no'),(548,'woocommerce_trash_pending_orders','','no'),(549,'woocommerce_trash_failed_orders','','no'),(550,'woocommerce_trash_cancelled_orders','','no'),(551,'woocommerce_anonymize_completed_orders','a:2:{s:6:\"number\";s:0:\"\";s:4:\"unit\";s:6:\"months\";}','no'),(552,'woocommerce_email_from_name','Wordpress Test','no'),(553,'woocommerce_email_from_address','admin@wordpress.test','no'),(554,'woocommerce_email_header_image','','no'),(555,'woocommerce_email_footer_text','{site_title} — Built with {WooCommerce}','no'),(556,'woocommerce_email_base_color','#7f54b3','no'),(557,'woocommerce_email_background_color','#f7f7f7','no'),(558,'woocommerce_email_body_background_color','#ffffff','no'),(559,'woocommerce_email_text_color','#3c3c3c','no'),(560,'woocommerce_merchant_email_notifications','no','no'),(561,'woocommerce_cart_page_id','11','no'),(562,'woocommerce_checkout_page_id','12','no'),(563,'woocommerce_myaccount_page_id','13','no'),(564,'woocommerce_terms_page_id','','no'),(565,'woocommerce_force_ssl_checkout','no','yes'),(566,'woocommerce_unforce_ssl_checkout','no','yes'),(567,'woocommerce_checkout_pay_endpoint','order-pay','yes'),(568,'woocommerce_checkout_order_received_endpoint','order-received','yes'),(569,'woocommerce_myaccount_add_payment_method_endpoint','add-payment-method','yes'),(570,'woocommerce_myaccount_delete_payment_method_endpoint','delete-payment-method','yes'),(571,'woocommerce_myaccount_set_default_payment_method_endpoint','set-default-payment-method','yes'),(572,'woocommerce_myaccount_orders_endpoint','orders','yes'),(573,'woocommerce_myaccount_view_order_endpoint','view-order','yes'),(574,'woocommerce_myaccount_downloads_endpoint','downloads','yes'),(575,'woocommerce_myaccount_edit_account_endpoint','edit-account','yes'),(576,'woocommerce_myaccount_edit_address_endpoint','edit-address','yes'),(577,'woocommerce_myaccount_payment_methods_endpoint','payment-methods','yes'),(578,'woocommerce_myaccount_lost_password_endpoint','lost-password','yes'),(579,'woocommerce_logout_endpoint','customer-logout','yes'),(580,'woocommerce_api_enabled','no','yes'),(581,'woocommerce_allow_tracking','no','no'),(582,'woocommerce_show_marketplace_suggestions','yes','no'),(583,'woocommerce_analytics_enabled','yes','yes'),(584,'woocommerce_navigation_enabled','no','yes'),(585,'woocommerce_feature_custom_order_tables_enabled','no','yes'),(586,'woocommerce_single_image_width','600','yes'),(587,'woocommerce_thumbnail_image_width','300','yes'),(588,'woocommerce_checkout_highlight_required_fields','yes','yes'),(589,'woocommerce_demo_store','no','no'),(590,'wc_downloads_approved_directories_mode','enabled','yes'),(591,'woocommerce_permalinks','a:5:{s:12:\"product_base\";s:7:\"product\";s:13:\"category_base\";s:16:\"product-category\";s:8:\"tag_base\";s:11:\"product-tag\";s:14:\"attribute_base\";s:0:\"\";s:22:\"use_verbose_page_rules\";b:0;}','yes'),(592,'current_theme_supports_woocommerce','yes','yes'),(593,'woocommerce_queue_flush_rewrite_rules','no','yes'),(595,'product_cat_children','a:0:{}','yes'),(596,'default_product_cat','15','yes'),(598,'woocommerce_refund_returns_page_id','14','yes'),(601,'woocommerce_paypal_settings','a:23:{s:7:\"enabled\";s:2:\"no\";s:5:\"title\";s:6:\"PayPal\";s:11:\"description\";s:85:\"Pay via PayPal; you can pay with your credit card if you don\'t have a PayPal account.\";s:5:\"email\";s:20:\"admin@wordpress.test\";s:8:\"advanced\";s:0:\"\";s:8:\"testmode\";s:2:\"no\";s:5:\"debug\";s:2:\"no\";s:16:\"ipn_notification\";s:3:\"yes\";s:14:\"receiver_email\";s:20:\"admin@wordpress.test\";s:14:\"identity_token\";s:0:\"\";s:14:\"invoice_prefix\";s:3:\"WC-\";s:13:\"send_shipping\";s:3:\"yes\";s:16:\"address_override\";s:2:\"no\";s:13:\"paymentaction\";s:4:\"sale\";s:9:\"image_url\";s:0:\"\";s:11:\"api_details\";s:0:\"\";s:12:\"api_username\";s:0:\"\";s:12:\"api_password\";s:0:\"\";s:13:\"api_signature\";s:0:\"\";s:20:\"sandbox_api_username\";s:0:\"\";s:20:\"sandbox_api_password\";s:0:\"\";s:21:\"sandbox_api_signature\";s:0:\"\";s:12:\"_should_load\";s:2:\"no\";}','yes'),(602,'woocommerce_version','8.2.2','yes'),(603,'woocommerce_db_version','8.2.2','yes'),(604,'woocommerce_admin_install_timestamp','1672924314','yes'),(605,'woocommerce_inbox_variant_assignment','3','yes'),(609,'_transient_jetpack_autoloader_plugin_paths','a:1:{i:0;s:29:\"{{WP_PLUGIN_DIR}}/woocommerce\";}','yes'),(610,'woocommerce_admin_notices','a:1:{i:1;s:20:\"no_secure_connection\";}','yes'),(611,'woocommerce_maxmind_geolocation_settings','a:1:{s:15:\"database_prefix\";s:32:\"0jxv9z7mXPj1LeMzhbPKfp8fWZJxPthz\";}','yes'),(612,'_transient_woocommerce_webhook_ids_status_active','a:0:{}','yes'),(613,'widget_woocommerce_widget_cart','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(614,'widget_woocommerce_layered_nav_filters','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(615,'widget_woocommerce_layered_nav','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(616,'widget_woocommerce_price_filter','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(617,'widget_woocommerce_product_categories','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(618,'widget_woocommerce_product_search','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(619,'widget_woocommerce_product_tag_cloud','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(620,'widget_woocommerce_products','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(621,'widget_woocommerce_recently_viewed_products','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(622,'widget_woocommerce_top_rated_products','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(623,'widget_woocommerce_recent_reviews','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(624,'widget_woocommerce_rating_filter','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(625,'_transient_wc_count_comments','O:8:\"stdClass\":7:{s:14:\"total_comments\";i:0;s:3:\"all\";i:0;s:9:\"moderated\";i:0;s:8:\"approved\";i:0;s:4:\"spam\";i:0;s:5:\"trash\";i:0;s:12:\"post-trashed\";i:0;}','yes'),(630,'_transient_woocommerce_shipping_task_zone_count_transient','0','yes'),(631,'wc_blocks_db_schema_version','260','yes'),(632,'wc_remote_inbox_notifications_stored_state','O:8:\"stdClass\":2:{s:22:\"there_were_no_products\";b:1;s:22:\"there_are_now_products\";b:0;}','no'),(635,'_transient_woocommerce_reports-transient-version','1672924354','yes'),(643,'woocommerce_task_list_tracked_completed_tasks','a:3:{i:0;s:8:\"purchase\";i:1;s:13:\"store_details\";i:2;s:8:\"products\";}','yes'),(645,'woocommerce_onboarding_profile','a:10:{s:18:\"is_agree_marketing\";b:0;s:11:\"store_email\";s:20:\"admin@wordpress.test\";s:20:\"is_store_country_set\";b:1;s:8:\"industry\";a:1:{i:0;a:1:{s:4:\"slug\";s:5:\"other\";}}s:13:\"product_types\";a:1:{i:0;s:9:\"downloads\";}s:13:\"product_count\";s:1:\"0\";s:14:\"selling_venues\";s:2:\"no\";s:12:\"setup_client\";b:1;s:19:\"business_extensions\";a:0:{}s:9:\"completed\";b:1;}','yes'),(647,'woocommerce_task_list_dismissed_tasks','a:0:{}','yes'),(651,'woocommerce_task_list_prompt_shown','1','yes'),(660,'woocommerce_default_homepage_layout','two_columns','yes'),(661,'woocommerce_task_list_hidden_lists','a:2:{i:0;s:5:\"setup\";i:1;s:8:\"extended\";}','yes'),(744,'external_updates-event-tickets-plus','O:8:\"stdClass\":3:{s:9:\"lastCheck\";i:1700226132;s:14:\"checkedVersion\";N;s:6:\"update\";O:19:\"Tribe__PUE__Utility\":12:{s:2:\"id\";i:0;s:6:\"plugin\";s:41:\"event-tickets-plus/event-tickets-plus.php\";s:4:\"slug\";s:18:\"event-tickets-plus\";s:7:\"version\";s:5:\"5.8.0\";s:8:\"homepage\";s:20:\"https://evnt.is/18wg\";s:12:\"download_url\";s:254:\"https://pue.theeventscalendar.com/api/plugins/v2/download?plugin=event-tickets-plus&version=5.8.0&installed_version=5.7.7&domain=localhost&multisite=0&network_activated=0&active_sites=1&wp_version=6.2.2&key=f0c38a187457a9bb5b1079f4556f467883a223f5&dk&o=o\";s:8:\"sections\";O:8:\"stdClass\":3:{s:11:\"description\";s:154:\"Event Tickets Plus adds features and functionality onto the core Event Tickets plugin, so you can sell tickets with WooCommerce or Easy Digital Downloads.\";s:12:\"installation\";s:348:\"Installing Events Tickets Plus is easy: just back up your site, download/install Event Tickets from the WordPress.org repo, and download/install Events Ticket Plus from theeventscalendar.com. Activate them both and you\'ll be good to go! If you\'re still confused or encounter problems, check out part 1 of our new user primer (http://m.tri.be/18ve).\";s:9:\"changelog\";s:331:\"= [5.8.0] 2023-11-16 =
\r\n\r\n= [1.4.0] 2023-10-19 =
\r\n\r\nWe’re here to announce our exciting new innovation, Wallet Plus. This product creates digital and portable tickets for your event attendees and truly modernizes all of our current offerings, including Event Tickets and Event Tickets Plus. We’ve made this process simpler for your attendees so that they can now save their tickets to digital wallets,…
\nThe post Introducing Wallet Plus appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"Jaime\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4277:\"\nWe’re here to announce our exciting new innovation, Wallet Plus. This product creates digital and portable tickets for your event attendees and truly modernizes all of our current offerings, including Event Tickets and Event Tickets Plus.
\n\n\n\nWe’ve made this process simpler for your attendees so that they can now save their tickets to digital wallets, like Apple Wallet or PassWallet, and download PDF tickets to have them with them at any time.
\n\n\n\nPlus, you can personalize digital tickets by adding your logo, picking your brand colors, and customizing your Apple wallet passes and PDFs.
\n\n\n\nWallet Plus is a game-changer for day-of-event management. Your attendees will have easy access to their tickets, and the QR check-in process will be simpler and faster.
\n\n\n\nBelow, we’ll break down all of the exciting new features
\n\n\n\nAllow users to save their tickets in Apple Wallet.
\n\n\n\nCustomize your PDF tickets and allow your event attendees to download them or receive them by email.
\n\n\n\nInclude digital tickets in ticket confirmation emails and during the checkout process.
\n\n\n\nAllow attendees to save their tickets into their favorite digital platform so they can access their tickets anytime.
\n\n\n\nEasily customize your digital tickets with the look and feel of your brand in a few simple clicks.
\n\n\n\nStart providing digital tickets in a few clicks. Just install the plugin and set up the look and feel of your digital tickets via settings.
\n\n\n\nInclude attendee registration fields into digital tickets when using Event Tickets Plus.
\n\n\n\nInclude QR on digital tickets, and make day-of event management a breeze.
\n\n\n\nWe can’t wait for you to see Wallet Plus in action; we know you’re going to love it! Get started today!
\nThe post Introducing Wallet Plus appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:21:\"Virtual Events 1.15.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:152:\"https://theeventscalendar.com/release-notes/virtual-events/virtual-events-1-15-5/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:33:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:14:\"Virtual Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543276\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:575:\"Summary Maintenance Release The latest version of Virtual Events introduces compatibility features with the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✨ New New tweaks and enhancements in this release: 🗣 Translations Updated language files and strings:
\nThe post Virtual Events 1.15.5 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2617:\"\n\n\n\n\nMaintenance Release
\nThe latest version of Virtual Events introduces compatibility features with the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nNew tweaks and enhancements in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Virtual Events 1.15.5 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:24:\"Event Tickets Plus 5.8.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:159:\"https://theeventscalendar.com/release-notes/event-tickets-plus/event-tickets-plus-5-8-0/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:33:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Event Tickets Plus\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543273\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:595:\"Summary Maintenance Release The latest version of Event Tickets Plus introduces compatibility features with the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing.Event Tickets Plus 5.8.0 is only compatible with Event Tickets 5.7.0 and higher. ✨ New New tweaks and enhancements…
\nThe post Event Tickets Plus 5.8.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2901:\"\n\n\n\n\nMaintenance Release
\nThe latest version of Event Tickets Plus introduces compatibility features with the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
Event Tickets Plus 5.8.0 is only compatible with Event Tickets 5.7.0 and higher.
New tweaks and enhancements in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Event Tickets Plus 5.8.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Event Tickets 5.7.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:149:\"https://theeventscalendar.com/release-notes/event-tickets/event-tickets-5-7-0/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:32:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:13:\"Event Tickets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543271\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:584:\"Summary Maintenance Release The latest version of Event Tickets introduces compatibility features with the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. Event Tickets 5.7.0 is only compatible with The Events Calendar 6.2.7 and higher.Event Tickets 5.7.0 is only compatible with…
\nThe post Event Tickets 5.7.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3089:\"\n\n\n\n\nMaintenance Release
\nThe latest version of Event Tickets introduces compatibility features with the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
Event Tickets 5.7.0 is only compatible with The Events Calendar 6.2.7 and higher.
Event Tickets 5.7.0 is only compatible with Event Tickets Plus 5.8.0 and higher.
New tweaks and enhancements in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Event Tickets 5.7.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"The Events Calendar 6.2.8\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:161:\"https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-2-8/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:31:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:19:\"The Events Calendar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543267\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:615:\"Summary Maintenance Release This new version of The Events Calendar includes compatibility improvements for the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing! The Events Calendar 6.2.8 is only compatible with Event Tickets 5.7.0 and higher. ✨ New New features and tweaks included…
\nThe post The Events Calendar 6.2.8 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2854:\"\n\n\n\n\nMaintenance Release
\nThis new version of The Events Calendar includes compatibility improvements for the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing!
\n\n\n\nThe Events Calendar 6.2.8 is only compatible with Event Tickets 5.7.0 and higher.
\nNew features and tweaks included in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post The Events Calendar 6.2.8 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"The Events Calendar 6.2.7\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:161:\"https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-2-7/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 17:50:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:19:\"The Events Calendar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543207\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:621:\"Summary Maintenance Release The latest update includes fixes for nonce generation and regressions along with various errors and deprecation notices. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✅ Fixed Bugs that were squashed in this release: ✨ Tweaks New tweaks in this release: 🗣 Translations Updated…
\nThe post The Events Calendar 6.2.7 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4757:\"\n\n\n\n\n\n\n\n\nMaintenance Release
\nThe latest update includes fixes for nonce generation and regressions along with various errors and deprecation notices.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nBugs that were squashed in this release:
\n\n\n\nNew tweaks in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post The Events Calendar 6.2.7 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"Events Calendar Pro 6.2.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:161:\"https://theeventscalendar.com/release-notes/events-calendar-pro/events-calendar-pro-6-2-4/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 17:49:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:19:\"Events Calendar Pro\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"Release Notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543209\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:579:\"Summary Maintenance Release The latest update resolves several deprecation notices and WPML permalink query on single posts. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✅ Fixed Bugs that were squashed in this release: 🗣 Translations Updated language files and strings:
\nThe post Events Calendar Pro 6.2.4 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3117:\"\n\n\n\n\nMaintenance Release
\nThe latest update resolves several deprecation notices and WPML permalink query on single posts.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nBugs that were squashed in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Events Calendar Pro 6.2.4 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"Introducing: Event Schedule Manager\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:146:\"https://theeventscalendar.com/blog/news/introducing-event-schedule-manager/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 17:53:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:10:\"What\'s New\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:4:\"blog\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2542727\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:582:\"Are you tired of juggling multiple systems, calendars, and custom coding while planning your events? Do you wish there was a more efficient way to manage your event schedules? Look no further! We are thrilled to introduce you to the all-new Event Schedule Manager – your ultimate event planning companion. Simplify your event planning Event…
\nThe post Introducing: Event Schedule Manager appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"Jaime\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3667:\"\nAre you tired of juggling multiple systems, calendars, and custom coding while planning your events? Do you wish there was a more efficient way to manage your event schedules? Look no further! We are thrilled to introduce you to the all-new Event Schedule Manager – your ultimate event planning companion.
\n\n\n\nEvent planning can be a daunting task, whether you’re organizing a corporate conference, a wedding, a music festival, or any other large-scale event. Event Schedule Manager is designed to simplify this process and make it more efficient than ever before.
\n\n\n\nWith Event Schedule Manager, you can say goodbye to custom coding a schedule with multiple tracks. Our user-friendly plugin provides a centralized hub where you can easily manage all aspects of your event, from scheduling to guest lists and beyond. There’s no need for multiple plugins and services to display your schedule tracks; everything you need is right at your fingertips.
\n\n\n\nLet’s take a closer look at some of the standout features that make Event Schedule Manager the go-to tool for event planners:
\n\n\n\nEvent Schedule Manager is more than just a scheduling tool; it’s a comprehensive event planning solution. Here’s why you should make it an integral part of your event planning process:
\n\n\n\nAre you ready to revolutionize your event schedule planning experience? Event Schedule Manager is here to make your life easier and your events more successful. Say goodbye to the chaos of event creation and hello to streamlined event planning.
\n\n\n\nCheck it out here!
\nThe post Introducing: Event Schedule Manager appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"Events Calendar Pro 6.2.3.1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:163:\"https://theeventscalendar.com/release-notes/events-calendar-pro/events-calendar-pro-6-2-3-1/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 22:16:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:19:\"Events Calendar Pro\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"Release Notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543182\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:569:\"Summary Maintenance Release The latest update includes a fix for saving recurring events correctly on WP v6.4. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✅ Fixed Bugs that were squashed in this release: 🗣 Translations Updated language files and strings:
\nThe post Events Calendar Pro 6.2.3.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2617:\"\n\n\n\n\nMaintenance Release
\nThe latest update includes a fix for saving recurring events correctly on WP v6.4.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nBugs that were squashed in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Events Calendar Pro 6.2.3.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"The Events Calendar 6.2.6.1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:163:\"https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-2-6-1/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 22:16:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:19:\"The Events Calendar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543180\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:617:\"Summary Maintenance Release The latest update includes a preventive fix for possible fatals. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. Event Tickets 5.6.8.1 is only compatible with The Events Calendar 6.2.6.1 and higher. ✅ Fixed Bugs that were squashed in this release: 🗣 Translations Updated language…
\nThe post The Events Calendar 6.2.6.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2703:\"\n\n\n\n\n\n\n\n\nMaintenance Release
\nThe latest update includes a preventive fix for possible fatals.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\n\n\n\nEvent Tickets 5.6.8.1 is only compatible with The Events Calendar 6.2.6.1 and higher.
\nBugs that were squashed in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post The Events Calendar 6.2.6.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:35:\"https://theeventscalendar.com/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:14:{s:4:\"date\";s:29:\"Fri, 17 Nov 2023 12:52:16 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:6:\"cf-ray\";s:20:\"82781c23a8e41ffd-IAD\";s:15:\"cf-cache-status\";s:6:\"BYPASS\";s:4:\"etag\";s:36:\"W/\"28a9d8340e4bf632fa7a8256cb45ab50\"\";s:13:\"last-modified\";s:29:\"Fri, 17 Nov 2023 09:29:19 GMT\";s:4:\"link\";s:117:\"The countdown is on for this year’s State of the Word! If you missed the initial announcement a few weeks ago, you’ll want to mark your calendars for December 11, 2023.
\n\n\n\nState of the Word is the annual keynote in which WordPress co-founder Matt Mullenweg celebrates the progress of the open source project and offers a glimpse into its future.
\n\n\n\nFor the first time, State of the Word ventures beyond North America, bringing the WordPress community to a new and vibrant city that plays a vital role in the WordPress project — Madrid, Spain! The event will be live-streamed to WordPress enthusiasts and newcomers around the globe via the WordPress YouTube channel.
\n\n\n\nPlease visit the event website for more event details and live-streaming information.
\n\n\n\nWhat: State of the Word 2023
When: December 11, 2023, 15:00 UTC (Start of live stream)
Where: Palacio Neptuno, Madrid, Spain
Streaming: Watch the live stream on the WordPress YouTube channel.
Tickets: Request a ticket to attend in person.
Please note that the venue’s capacity is limited; therefore, not all ticket requests will be granted.
Meetups: The community will sponsor several local watch parties globally, both in
person and online. Find one near you or organize one.
State of the Word will include a Q&A session. If you want to participate, you can send your question to ask-matt@wordcamp.org or ask during the event via the Q&A app Slido. A QR code for your submission will be provided during the event live stream.
\n\n\n\nGiven the volume of questions usually submitted, only some will be answered live, while others will be covered in a follow-up post published after the event on make.wordpress.org/project.
\n\n\n\nIs this your first State of the Word? Check out prior events on WordPress.tv for an introduction to the format.
\n\n\n\nSee you in person and online on December 11!
\n\n\n\nThank you to Reyes Martínez and Chloé Bringmann for reviewing this post.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16429\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:68:\"\n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"Introducing Twenty Twenty-Four\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://wordpress.org/news/2023/11/introducing-twenty-twenty-four/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 18:29:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:4:{i:0;a:5:{s:4:\"data\";s:6:\"Design\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:18:\"Twenty Twenty-Four\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16394\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:127:\"Meet Twenty Twenty-Four, the most versatile default theme yet—bundled with WordPress 6.4 and ready to make it uniquely yours.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:2:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:59:\"https://wordpress.org/news/files/2023/11/tt4-i9-small-1.mp4\";s:6:\"length\";s:7:\"6747134\";s:4:\"type\";s:9:\"video/mp4\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:82:\"https://wordpress.org/news/files/2023/11/tt4-howto-replace-template_compressed.mp4\";s:6:\"length\";s:8:\"12815358\";s:4:\"type\";s:9:\"video/mp4\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Maggie Cabrera\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:7209:\"\nWhen it comes to designing a website, one size doesn’t fit all. We understand that every WordPress user has unique needs and goals, whether you’re an aspiring entrepreneur, a passionate photographer, a prolific writer, or a bit of them all. That’s why we are thrilled to introduce Twenty Twenty-Four, the most versatile default theme yet—bundled with WordPress 6.4 and ready to make it uniquely yours.
\n\n\n\n\n\n\n\nUnlike past default themes, Twenty Twenty-Four breaks away from the tradition of focusing on a specific topic or style. Instead, this theme has been thoughtfully crafted to cater to any type of website, regardless of its focus. The theme explores three different use cases: one designed for entrepreneurs and small businesses, another for photographers and artists, and a third tailored for writers and bloggers. Thanks to its multi-faceted nature and adaptability, Twenty Twenty-Four emerges as the perfect fit for any of your projects.
\n\n\n\nAs you dive into its templates and patterns, you will notice how the new Site Editor functionality opens up different pathways for building your site seamlessly.
\n\n\n\nWhether you’re looking to craft an About page, showcase your work, handle RSVPs, or design captivating landing pages, Twenty Twenty-Four has got you covered. Choose from an extensive collection of over 35 beautiful patterns to customize and suit your needs.
\n\n\n\nFor the first time, this theme features full-page patterns for templates like homepage, archive, search, single pages, and posts. Some are exclusively available during the template-switching and creation process, ensuring you have the right options when you need them.
\n\n\n\n\n\n\n\nMoreover, you can take advantage of a variety of patterns for page sections, such as FAQs, testimonials, or pricing, to meet your site’s most specific requirements.
\n\n\n\nWith this diverse pattern library, Twenty Twenty-Four offers a flexible canvas to quickly assemble pages without having to start from scratch—saving you time and energy in the creation process. Just let your creativity flow and explore the possibilities!
\n\n\n\n\n\n\n\nTwenty Twenty-Four ushers in a new era of block themes by bringing together the latest WordPress site editing capabilities. Discover newer design tools such as background image support in Group blocks and vertical text, providing an intuitive and efficient way to create compelling, interactive content.
\n\n\n\nFind image placeholders with predefined aspect ratio settings within patterns, allowing you to drop images that perfectly fill the space. To go one step further, make your visuals interactive by enabling lightboxes. Ideal for showcasing galleries or portfolio images, this feature allows your visitors to expand and engage with them in full-screen mode. Activate it globally for all images throughout your site or for specific ones.
\n\n\n\nFor a smoother browsing experience on your site, you can disable the “Force page reload” setting in the Query Loop block. This allows the necessary content to be loaded dynamically when switching between different pages without needing a full-page refresh.
\n\n\n\nTwenty Twenty-Four goes beyond versatility with a beautiful aesthetic inspired by contemporary design trends, giving your website a sleek and modern look. Key design elements include:
\n\n\n\nAlong with its design, Twenty Twenty-Four has been meticulously optimized for performance. This ensures that your website not only looks great but also delivers a fast and efficient user experience.
\n\n\n\n \n\n\n\nMore information can be found in the following links:
\n\n\n\nThe Twenty Twenty-Four theme was designed by Beatriz Fialho and made possible thanks to the passion and tireless work of more than 120 contributors.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16394\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WP Briefing: Episode 66: Advocating Open Source Solutions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wordpress.org/news/2023/11/episode-66-advocating-open-source-solutions/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16357\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:296:\"WordPress Executive Director, Josepha Haden Chomphosy, speaks to the strategic approach to integrating open source solutions within your company and offers insight into initiating open source advocacy conversations. Tune in for a session that could redefine your company\'s technological approach.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:51:\"https://wordpress.org/news/files/2023/11/WPB066.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:11349:\"\nWordPress Executive Director, Josepha Haden Chomphosy, speaks to the strategic approach to integrating open source solutions within your company and offers insight into initiating open source advocacy conversations. Tune in for a session that could redefine your company’s technological approach.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@WordPress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, we’re talking about something I used to have a lot of experience with in my career before WordPress. I worked at a marketing agency. I wasn’t a developer. I was in data and strategy sorts of things. But part of the work heading into every project was an evaluation of what software was best. There were always a variety being considered, but WordPress was frequently one of them.
\n\n\n\nNow, I don’t know if any of you have had that moment where you’re having to talk open source with a CTO or a CEO, but it can be nerve-wracking, to say the least. And it makes sense, right? Open source has a PR problem, especially when you’re speaking to leadership inside a business. And it doesn’t really matter the size, right?
\n\n\n\nYou’re advocating for something that requires a completely different mental model. It doesn’t fit into accepted concepts of what makes a business thrive or what makes a bet a sure thing. There were three, maybe four, concerns that came up every time I had this conversation. So, I’m going to share those concerns with you and a few possible counterpoints to get you started.
\n\n\n\n[00:01:48] Josepha: First and always is the concern around security. I believe that this particular mismatch is rooted in an idea that controlled equals secure, which isn’t always the case. So the talking point is this. Since open source has a transparent development process, it is often more secure than proprietary software, contrary to what you might hear.
\n\n\n\nThat transparency allows vulnerabilities to be identified by independent researchers and community members and then patched quickly because you aren’t limited by who or what you know personally.
\n\n\n\nAnd if you’re not having a conversation where you’re having to defend the security in open source and you just want to bring it up yourself, here is a conversation opener for that. Security is a top concern for all of us. Surprisingly, open source solutions often have stronger security measures due to the collaborative nature of their development. It’s a proactive approach to minimizing risks.
\n\n\n\n[00:02:43] Josepha: A second thing that frequently came up was questions around innovation and future proofing of open source products. I think this mismatch is fully rooted in the Cathedral and the Bazaar methods of advancement. So the talking point for that one is this. Embracing open source fosters innovation. We can tap into the latest technologies and stay ahead of industry trends that way. It is specifically because we have a diverse set of viewpoints that we can make sure to quickly account for future risks, along with taking advantage of future opportunities. And by our organization being more active, we can potentially get exactly the solutions we need for our clients long term.
\n\n\n\nAnd the conversation opener for this, if you are the one bringing up the topic, is I’ve been thinking about our long-term goals and how to keep our technology stack relevant. Open source not only keeps us current but also positions us as innovators in our field.
\n\n\n\n[00:03:40] Josepha: And finally, the thing that seems to make or break the decision is the concept of independence. Part of any good business decision, especially around software, is determining upfront costs to getting started, long-term effectiveness of the chosen solution, and long-term mobility should circumstances change. Open source can address these from multiple vantage points.
\n\n\n\nSo here’s a good talking point for that one. Open source liberates us from vendor lock-in. We’re not tied to a single vendor’s roadmap or pricing changes, providing us with more options that suit our needs our clients’ needs. Also, given how ubiquitous WordPress is in particular, there will always be a disaster recovery option should a senior developer leave.
\n\n\n\nAnd beyond all of that, clients can own all of the content, audience attention, and clientele that we have all worked so hard to help them earn. And again, if you’re not defending things and instead choosing to bring them up as somebody who is trying to affect change in your own organization, here is a good place to start for that.
\n\n\n\nConsidering the dynamic nature of our industry, having the freedom to choose solutions independent of a specific vendor makes sure that we are always in control of our destiny.
\n\n\n\n[00:04:59] Josepha: So, those are the three most frequent things I encountered when I was having conversations about which software to choose and what software was the best choice long term for both our organization and our client’s organizations.
\n\n\n\nIf you have been in the midst of this type of conversation and have been longing for some counterpoints, I hope this helps. But if you have been feeling in your heart of hearts that your company or organization would be better off using open source software, and of course, in my context, particularly WordPress as that software, but you’ve been worried about bringing it up, I hope this gives you the courage to get out there and be an agent of change in your organization. You can do it, and I know you can.
\n\n\n\n[00:05:44] (Music interlude)
\n\n\n\n[00:05:51] Josepha: All right, my friends, that brings us now to our small list of big things.
\n\n\n\n[00:05:57] Josepha: First on the list, big, big thing. We launched WordPress 6.4 on November 7th, about a week ago. Be sure to download and check out the latest update on this monumental release. And while you’re doing it. Be sure to check out the new default theme that came out with it. It has a lot of patterns in it. I know I’ve talked about it quite a bit over the course of the year, but it’s really beautiful, and I think that it’s worth a good, strong highlight. So WordPress 6.4, you can get it on WordPress.org/download or inside your own host, probably.
\n\n\n\n[00:06:29] Josepha: The second thing that we have is that the training team recently published several new Learn resources to support meetup organizers. So we’ve got over there some lesson plans, tutorials, online workshops. And there are also new materials that help you figure out how to accomplish your goals as a contributor to the WordPress project.
\n\n\n\n[00:06:49] Josepha: And we also have a recently published new diverse speaker training page. It provides incredible resources for new and experienced contributors to bring more diverse speaker lineups and inclusive, diverse WordPress events for official WordPress meetups and WordCamps.
\n\n\n\n[00:07:06] Josepha: And the fourth thing on our small list of big things today is that I would love to get a few voice recordings from you all, from folks who are listening to the WordPress Briefing, or folks that you know, to learn more about how WordPress has impacted you.
\n\n\n\nOne of the things that I miss the most from my days as a WordCamp organizer is that annually, I got to see people who had shown up, once at a meetup, you know, to learn what WordPress was, and then came back year after year to our WordCamp with these new goals and new successes and I got to watch their businesses change over time. And so if you have a story like that where WordPress impacted what you are doing or what people that you know have done, record something and send it to wpbriefing@WordPress.org.
\n\n\n\nSo that, my friends, is your small list of big things.
\n\n\n\n[00:08:04] Josepha: Don’t forget to follow us on your favorite podcasting app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there is a new episode. If you liked what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard, you can share those with me at wpbriefing@WordPress.org. I’m your host, Josepha Haden Chomphosy. Thanks for tuning in today for the WordPress Briefing, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:08:31] (Music outro)
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16357\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"The Month in WordPress – October 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2023/11/the-month-in-wordpress-october-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Nov 2023 23:06:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:18:\"month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16365\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:391:\"September-October 2023 was yet another fun and eventful chapter in WordPress, with more WordCamps hosting exciting discussions, knowledge sharing, and learning. This month also welcomed the release of WordPress 6.4 and the Twenty Twenty-Four theme. Let’s check it out. Meet WordPress 6.4 “Shirley” WordPress 6.4 “Shirley” was released on November 7, 2023, and named after […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Nicholas Garofalo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:11701:\"\nSeptember-October 2023 was yet another fun and eventful chapter in WordPress, with more WordCamps hosting exciting discussions, knowledge sharing, and learning. This month also welcomed the release of WordPress 6.4 and the Twenty Twenty-Four theme. Let’s check it out.
\n\n\n\nWordPress 6.4 “Shirley” was released on November 7, 2023, and named after the iconic jazz artist Shirley Horn. With the release of WordPress 6.4 comes the new Twenty Twenty-Four theme, a multi-faceted, highly flexible default theme pre-loaded with more than 35 templates and patterns.
\n\n\n\nThis release includes more than 100 performance-related updates for a faster and more efficient experience. There’s also a host of new features and enhancements that help improve the content creation process and streamline site editing.
\n\n\n\nWordPress 6.4 was made possible by more than 600 contributors in at least 56 countries. Leading this release has been an underrepresented gender team, emphasizing WordPress’ commitment to fostering diverse voices in the open source project.
\n\n\n\n \n\n\n\n\n\n\n\nMark your calendars for State of the Word! The annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg, will be held on December 11, 2023. For the first time, the event will take place outside North America—this time with the Spanish community in Madrid, Spain.
\n\n\n\nA live stream will be available for WordPress enthusiasts who will not be able to attend in person. Stay tuned for more information, including how to reserve a ticket, soon!
\n\n\n\n \n\n\n\n\n\n\n\nTwo new versions of Gutenberg shipped in October:
\n\n\n\nOctober’s Core Editor Improvement post dives into all the writing enhancements expected in the latest WordPress 6.4 release.
\n\n\n\nhttps://wordpress.org/news/2023/10/episode-64-patterns-in-wordpress/\n\n\n\nHave a story we should include in the next issue of The Month in WordPress? Fill out this quick form to let us know.
\n\n\n\nThank you to Bernard Meyer and Reyes Martínez for their contributions to this edition of The Month in WordPress.
\n\n\n\nJoin over 2 million other subscribers and receive WordPress news directly in your inbox.
\n\n\n\n Subscribe\n
\nThis minor release features four bug fixes. You can review a summary of the maintenance updates in this release by reading the Release Candidate announcement or view the list of tickets on Trac.
\n\n\n\nWordPress 6.4.1 is a short-cycle release. If you have sites that support automatic background updates, the update process will begin automatically. If your site does not update automatically, you can also update from your Dashboard.
\n\n\n\nYou can download WordPress 6.4.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.
\n\n\n\nFor more information on this release, please visit the HelpHub site.
\n\n\n\nThis release was led by Aaron Jorbin and Tonya Mork. Thank you to everyone who tested the RC and 6.4.1, and raised reports.
\n\n\n\nWordPress 6.4.1 would not have been possible without the contributions of the following people. Their quick and concerted coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\n\n@afragen @clorith @desrosj @pbiron @schlessera @azaozz @davidbaumwald @tomsommer @nexflaszlo @howdy_mcgee @baxbridge @earnjam @timothyblynjacobs @johnbillion @flixos90 @joedolson @jeffpaul @zunaid321 @courane01 @audrasjb @tacoverdo @ironprogrammer @webcommsat @otto42 @barry @chanthaboune @rajinsharwar @aaroncampbell @peterwilsoncc @anandau14 @iandunn @matthewjho @coffee2code @boogah @jason_the_adams @joemcgill @johnjamesjacoby @jrf @renehermi @dlh @mukesh27 @sumitbagthariya16 @starbuck @sergeybiryukov @ravipatel
\n\n\n\nTo get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core channel. Need help? Check out the Core Contributor Handbook.
\n\n\n\nThanks to @jeffpaul and @webcommsat for proofreading.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16332\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:66:\"\n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"WordPress 6.4 “Shirley”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://wordpress.org/news/2023/11/shirley/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 07 Nov 2023 19:59:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:4:{i:0;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16299\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:194:\"WordPress 6.4 \"Shirley\" is here! Named in honor of the iconic jazz singer and pianist Shirley Horn, this release was made possible by over 600 contributors. Download WordPress 6.4 Shirley today.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:74789:\"\n\n\n\n\nSay hello to WordPress 6.4 “Shirley,” named after the iconic jazz artist Shirley Horn. Her distinctive voice and extraordinary connection to the piano established her as one of the leading jazz musicians of her generation. Horn’s journey from the Washington D.C. jazz scene to the international stage is a testament to her dedication and perseverance. Her influence reached far beyond the confines of traditional jazz, breaking boundaries and inspiring audiences worldwide.
\n\n\n\nEnjoy the easy pace of Shirley Horn’s music as you take in all that 6.4 offers.
\n\n\n\nThis latest version of WordPress introduces a new, versatile default theme and a suite of upgrades to empower every step of your creative journey. Craft your content seamlessly with further writing improvements. Explore more ways to bring your vision to life and streamline site editing with enhanced tools. Whether you’re new to WordPress or an experienced creator, “Shirley” has something for you. Discover the unmatched flexibility of building with blocks and let your ideas take flight.
\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\nMany of the features and enhancements in WordPress 6.4 fall in the “small but mighty” category. Along with the adaptable beauty of the Twenty Twenty-Four theme, these updates help content creators and site developers alike save time and effort while delivering the high value, low hassle WordPress experience the world has grown to expect.
\nJosepha Haden Chomphosy, Executive Director of WordPress
Experience site editing at its finest with Twenty Twenty-Four. This new multi-faceted default theme has been thoughtfully crafted with three distinct use cases in mind, from writers and artists to entrepreneurs. Save time and effort with its extensive collection of over 35 templates and patterns—and unlock a world of creative possibilities with a few tweaks. Twenty Twenty-Four’s remarkable flexibility ensures an ideal fit for almost any type of site. Check it out in this demo.
\n\n\n\n\n\n\n\nNew enhancements ensure your content creation journey is smooth. Find new keyboard shortcuts in List View, smarter list merging, and enhanced control over link settings. A cohesive toolbar experience for the Navigation, List, and Quote blocks lets you work efficiently with the tooling options you need.
\n\n\n\n\n\n\n\nFirst introduced in WordPress 6.3, the Command Palette is a powerful tool to quickly find what you need, perform tasks efficiently, and speed up your building workflow. Enjoy a refreshed design and new commands to perform block-specific actions in this release.
\n\n\n\n\n\n\n\nPatterns are an excellent way to leverage the potential of blocks and simplify your site-building process. WordPress 6.4 allows you to organize them with custom categories. Plus, new advanced filtering in the Patterns section of the inserter makes finding all your patterns more intuitive.
\n\n\n\n\n\n\n\nBuild beautiful and functional layouts with an expanded set of design tools. Play with background images in Group blocks for unique designs and maintain image dimensions consistent with placeholder aspect ratios. Do you want to add buttons to your Navigation block? Now you can do it conveniently without a line of code.
\n\n\n\n\n\n\n\nEnable lightbox functionality to let your site visitors enjoy full-screen, interactive images on click. Apply it globally or to specific images to customize the viewing experience.
\n\n\n\n\n\n\n\nSet custom names for Group blocks to organize and distinguish areas of your content easily. These names will be visible in List View.
\n\n\n\n\n\n\n\nNew previews for Gallery and Image blocks in List View let you visualize and locate where images on your content are at a glance.
\n\n\n\n\n\n\n\nNeed to use your custom patterns on another site? Import and export them as JSON files from the Site Editor’s patterns view.
\n\n\n\n\n\n\n\nBlock Hooks enables developers to automatically insert dynamic blocks at specific content locations, enriching the extensibility of block themes through plugins. While considered a developer tool, this feature is geared to respect your preferences and gives you complete control to add, dismiss, and customize auto-inserted blocks to your needs.
\n\n\n\n\n\n\n\nThis release includes more than 100 performance-related updates for a faster and more efficient experience. Notable enhancements focus on template loading performance for themes (including Twenty Twenty-Four), usage of the script loading strategies “defer” and “async” in core, blocks, and themes, and optimization of autoloaded options.
\n\n\n\nEvery release is committed to making WordPress accessible to everyone. WordPress 6.4 brings several List View improvements and aria-label support for the Navigation block, among other highlights. The admin user interface includes enhancements to button placements, “Add New” menu items context, and Site Health spoken messages. Learn more about all the updates aimed at improving accessibility.
\n\n\n\nCheck out the new WordPress 6.4 page to learn more about the numerous enhancements and features of this release.
\n\n\n\nExplore Learn WordPress for quick how-to videos, online workshops, and other free resources to level up your WordPress knowledge and skills.
\n\n\n\nIf you are looking for detailed technical notes on new changes, the WordPress 6.4 Field Guide is for you. Don’t forget to subscribe to the Developer Blog to stay on top of the latest development updates, tutorials, and more.
\n\n\n\nFor more information on installation, fixes, and file changes, visit the 6.4 release notes.
\n\n\n\n\n\n\n\nThe WordPress 6.4 release comes to you from an underrepresented gender release squad to welcome and empower diverse voices in the WordPress open source project.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nBeing part of the 6.4 release coordination team has allowed me to closely observe the intricate release process, where every detail, no matter how minor, is meticulously addressed—taking into account various factors like performance and backward compatibility. There’s still much to learn, but I feel fortunate to have had the chance to contribute to WordPress 6.4.
\nAkshaya Rane, 6.4 release coordinator team member
Over several weeks, the 6.4 release squad kept the release on track and moving forward by leading collective work, connecting ideas, and removing roadblocks.
\n\n\n\nWordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a global and diverse community of people working together to strengthen the software.
\n\n\n\nWordPress 6.4 reflects the countless efforts and passion of more than 600 contributors in at least 56 countries. This release also welcomed over 170 first-time contributors!
\n\n\n\nTheir collaboration delivered more than 1150 enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress open source community.
\n\n\n\n6adminit · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · aayusha · Abha Thakor · Abid Omar · Adam Silverstein · Adhun Anand · admcfajn · adrianduffell · aegkr · ahardyjpl · Ahmed Hussein · Ahmed Kabir Chaion · ajakaroth · Aki Hamano · Akihiro Harai · Akira Tachibana · Akshaya Rane · Al-Amin Firdows · Alain Schlesser · Albert Juhé Lluveras · Alex Concha · Alex King · Alex Lende · Alex Stine · Alexandre Buffet · Alisha Bajracharya · Allison Tarr · Alvi Tazwar · amedv · Ana Cirujano · Anand Upadhyay · Anders Norén · André · Andrea Fercia · Andrei Draganescu · Andrew Hayward · Andrew Hutchings · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrew Wilder · Andy Fragen · Andy Peatling · Ankit Gade · Ankit K Gupta · Ankit Panchal · Anna · Anne Katzeff · Anne McCarthy · Anne-Mieke Bovelett · anphira · Anthony Burchell · Anton Plauche · Anton Timmermans · Anton Vlasenko · Anveshika Srivastava · archon810 · arena · Ari Stathopoulos · Arnab Mondal · Artemio Morales · Arthur Chu · asafm7 · Aslam Doctor · Aurooba Ahmed · Austin Ginder · Ayesh Karunaratne · azharckra · Balu B · bangank36 · barbmiller · Barry · Bart · Basilis Kanonidis · Beatriz Fialho · behoney · ben · Ben Dwyer · Ben Greeley · Ben Hansen · Benjamin Intal · Benjamin Zekavica · benjaminknox · Benoit Chantre · Bernhard Reiter · Bernie Reiter · Bhrugesh Bavishi · Bijay Yadav · Binsaifullah · Biplav · Birendra Dhami · Birgit Olzem · Birgit Pauli-Haack · Block Themes Pro · bmalsht · bonger · bookwyrm · Boone Gorges · Boro Sitnikovski · Brad Jorsch · Bradley Jacobs · Brandon Kraft · Brandon Vreeman · Brian Gardner · Brian Haas · Brooke · Brooke. · Bud Kraus · Caleb Burks · Calvin Alkan · Carlo Cannas · Carlos Bravo · Carlos G. P. · Carolina Nymark · Cathi Bosco · ceer · cenkdemir · Chad Chadbourne · chased@si.edu · Chintan hingrajiya · Chip Bennett · Chloé Bringmann · Chris Runnells · chriscct7 · chrisdesrochers · codersantosh · Colin Stewart · Corey Worrell · Courtney Patubo Kranzke · Courtney Robertson · Crisoforo Gaspar · crstauf · Csaba (LittleBigThings) · Cupid Chakma · cybeardjm · Cyberchicken · Daisuke Takahashi · Dajeema Rai · Damon Cook · Damon Sharp · Dan Tovbein · Daniel Bachhuber · Daniel Richards · danieldudzic · Daniele Scasciafratte · Danielle Zarcaro · danieltj · darerodz · Darin Kotter · darkfate · Darren Ethier (nerrad) · Darshit Rajyaguru · Dave Loodts · dave03 · David Baumwald · David Biňovec · David Calhoun · David E. Smith · David Favor · David Herrera · David Ryan · David Smith · Dawid Urbanski · daxelrod · De Belser Arne · Dean Sas · Dee Teal · Deepak Vijayan · Denis Žoljom · Dennis Snell · Derek Blank · Derrick Tennant · Devan Ferguson · Dharmesh Patel · Dhrumil Kumbhani · Dhruvi Shah · Diane Co · Dilip Bheda · Dimitris Mitsis · Dion Hulse · DJ · dj.cowan · Dominik Schilling · doughamlin · Drew Jaynes · Earle Davies · Ebonie Butler · Edi Amin · Edward Caissie · Ehtisham S. · Ella van Durpe · Ellen Bauer · emailjoey · Emerson Maningo · Emily Clarke · Emily Leffler Schulman · emirpprime · enodekciw · Enrico Battocchi · Erik Betshammar · Esrat Sultana Popy · Estela Rueda · Fabian Kägy · Fabian Todt · Fabio Rubioglio · Faisal Alvi · Felipe Elia · Felix Arntz · Femy Praseeth · floydwilde · FolioVision · Francesca Marano · Frank Laszlo · Fredde Battel · fzhantw · Gabriel Koen · Ganesh Dahal · Garrett Hyder · Gary Cao · Gary Pendergast · Gennady Kovshenin · George Hotelling · George Mamadashvili · Gerardo Pacheco · Gio Lodi · Glen Davies · Gnanasekaran Loganathan · Gopal Krishnan · GOZER · gpotter · Grant M. Kinney · Greg Ross · Greg Ziółkowski · gregfuller · Guss77 · Gustavo Bordoni · gvgvgvijayan · Héctor Prieto · H.M. Mushfiqur Rahman · hanneslsm · Hanzala Taifun · Hareesh S · Harsh Gajipara · Hasanuzzaman · Haz · Helen Hou-Sandi · Hemant Tejwani · Hit Bhalodia · hlunter · Howdy_McGee · Huzaifa Al Mesbah · Ian Dunn · Incursa Designs · ironprogrammer · Isabel Brison · itecrs · Ivan Zhuck · jaimieolmstead · Jakaria Istauk · Jake Goldman · Jake Spurlock · James Hunt · James Janco · James Koster · James Roberts · james0r · Jamie McHale · Jamie Perrelet · Jamie VanRaalte · jane · Jarda Snajdr · Jari Vuorenmaa · Jarko Piironen · Jason Adams · Jason Cosper · Jason Crist · jastos · Jean-Baptiste Audras · Jeff Bowen · Jeff Chi · Jeff Everhart · Jeff Ong · jeffikus · Jeffrey Paul · jeflopo · Jeremy Felt · Jeremy Herve · Jeremy Yip · jeryj · Jesin A · Jessica Duarte · Jessica Goddard · Jessica Lyschik · Jick · Jip Moors · jivygraphics · Joe Dolson · Joe Hoyle · Joe McGill · Joen A. · John Blackbourn · John Hooks · John James Jacoby · John Regan · Jon Brown · Jon Cave · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Joona · Joost de Valk · JordanPak · jordesign · Jorge Costa · Joseph G. · Josepha Haden · joshcanhelp · joshuatf · JR Tashjian · Juan Aldasoro · JuanMa Garrido · Juliette Reinders Folmer · Justin Tadlock · Jyolsna J E · K M Ashikur Rahman · K. Adam White · KafleG · Kai Hao · Kalmang · Kalpesh · Kamrul Hasan · Karlijn Bok · Karol Manijak · Karthik Thayyil · Katie Ayres · kawsaralameven · Keanan Koppenhaver · Kelly Choyce-Dwan · Kevin Fodness · Kevin Miller · Kevin Taron · khleomix · Khokan Sardar · Kim Coleman · Kishan Jasani · kkmuffme · Koji Kuno · Konstantin Kovshenin · Konstantin Obenland · Kopila Shrestha · Krupal Panchal · Labun Chemjong · Lance Willett · LarryWEB · lastsplash (a11n) · lau@mindproducts.com.au · launchinteractive · Laura Adamonis · Laura Byrne · laurelfulford · Lauren · Laxmikant Bhumkar · Lee Willis · Lena Morita · Liam Gladdy · Linkon Miyan · Linnea Huxford · Lloyd Budd · Lovekesh Kumar · Luigi · Luis Felipe Zaguini · Luis Herranz · Luke Cavanagh · lunaluna · lyndauwp · Márcio Duarte · maciejmackowiak · madejackson · Madhu Dollu · Madhu Dollu · Maggie Cabrera · Mahbub Hasan Imon · Mahrokh · Mai · Maja Benke · maltfield · Manesh Timilsina · manfcarlo · Manzoor Wani · marcelle42 · Marcelo de Moraes Serpa · Marco Ciampini · Marco Pereirinha · Marcoevich · margolisj · Marin Atanasov · Mario Santos · Marius L. J. · Mark Jaquith · Marko Ivanovic · Marta Torre · Martijn van der Klis · martin.krcho · Mary Baum · Masoud NKH · mathsgrinds · Matias Benedetto · Matias Ventura · Matt Keys · Matt Watson · Matthaus Klute · Matthew Eppelsheimer · Matthew Farlymn · Matthew Haines-Young · matthewjho · maurodf · Maxwell Morgan · maysi · Md HR Shahin · meagan hanes · Mehedi Hassan · Meher Bala · Mel Choyce-Dwan · mer00x · merel1988 · Michael Arestad · Michael Burridge · Michael Showes · Michal Czaplinski · Michalooki · Michelle Blanchette · Michelle Frechette · Michi91 · Miguel Fonseca · Mikael Korpela · Mike Jolley (a11n) · Mike McAlister · Mike Schinkel · Mike Schroder · Mike Straw · Mikin Chauhan · Milen Petrinski - Gonzo · mimi · mitchellaustin · Monir · Mrinal Haque · mrwweb · Muhammad Arslan · Muhibul Haque · mujuonly · Mukesh Panchal · Mumtahina Faguni · Mushrit Shabnam · Myles Taylor · Nalini Thakor · nandhuraj · Nazgul · Nazmul Sabuz · Neil Hainsworth · nendeb · Nick Diego · Nicolas Juen · Nicole Furlan · nicomollet · nidhidhandhukiya · Niels Lange · Nihar Ranjan Das · Nik Tsekouras · Nilambar Sharma · Nilo Velez · niravsherasiya7707 · Nitesh Das · Nithin John · Nithin SreeRaj · Noah Allen · Nyasha · ockham · Ohia · okat · Olga Gleckler · Oliver Campion · OllieJones · Paal Joachim Romdahl · pannelars · Pascal Birchler · Paul Biron · Paul Kevan · pavelevap · Pedro Mendonça · pentatonicfunk · Pete Nelson · Peter Wilson · petitphp · petrosparaskevopoulos · Petter Walbø Johnsgård · Phill · Pieterjan Deneys · piyushdeshmukh · Plugin Devs · Pooja Bhimani · Pooja Derashri · Pooja N Muchandikar · pranavjoshi · Prashant · Presskopp · r-c · Rajin Sharwar · Ramon Ahnert · Ramon Corrales · Ramon James · Rebekah Markowitz · Remy Perona · ren · Renatho (a11n) · Rene Hermenau · Reyes Martínez · Riad Benguella · Rian Rietveld · Rich Tabor · Robert Anderson · Robert O\'Rourke · Robin · robpetrin · Rolf Allard van Hagen · Ryan Duff · Ryan McCue · Ryan Neudorf · Ryan Welcher · Sérgio Gomes · Sagar Tamang · Sajjad Hossain Sagor · Sakib Mohammed · Sal Ferrarello · samba45 · Samir Karmacharya · Sampat Viral · Samuel Wood (Otto) · Sarah Norris · Sarah Williams · Sarath AR · Satish Prajapati · saulirajala · saxonfletcher · Scott Kingsley Clark · Scott Reilly · Scott Taylor · Scout James · scribu · Sergey Biryukov · Sergio Scabuzzo · Seth Rubenstein · Shail Mehta · shawfactor · Shawn Hooper · shilo-ey · Shiva Shanker Bhatta · shresthaaman · Shubham Sedani · Simon Dowdles · Siobhan · Siobhan Bamber · Smit Rathod · sofiashendi · Sonia Gaballa · Soren Wrede · SourceView · Spenser Hale · Stephanie Walters · Stephen Bernhardt · Stephen Edgar · Steve Erdelyi · Steve Jones · Subodh Sunuwar · Subrata Sarkar · Suji K Chandran · Sumi Subedi · Sumit Bagthariya · Sumit Singh · Sunita Rai · suprsam · syamraj24 · Sybre Waaijer · Synchro · Sé Reed · Taco Verdonschot · Tahmid ul Karim · Tahmina Jahan · Takayuki Miyoshi · Tammie Lister · Tanvirul Haque · Teddy Patriarca · tejadev · thinkluke · Thomas Patrick Levy · tibbsa · Tiffany Bridge · Tim Nolte · timdix · Timothy Jacobs · tmatsuur · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tom Cafferkey · Tom H · Tom J Nowell · tomluckies · Tomoki Shimomura · tomsommer · Tony G · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · toscho · Tran Ngoc Tuan Anh · Trinisha · Trisha Salas · tristanleboss · TV productions · Ugyen Dorji · Ulrich · Umesh Balayar · Upadala Vipul · Utsav tilava · valentindu62 · Valerie Blackburn · Vicente Canales · Viktor Szépe · Vipul Ghori · vivekawsm · vortfu · Vraja Das · webashrafians · WebMan Design | Oliver Juhas · Weston Ruter · WHSajid · Will Skora · William Earnhardt · Willington Vega · Winstina · winterstreet · WraithKenny · wyrfel · Yoseph Tamang · Yui · zieladam · Zunaid Amin · Илья
\n\n\n\nOver 60 locales have translated 90 percent or more of WordPress 6.4 into their language. Community translators are working hard to ensure more translations are on their way. Thank you to everyone who helps make WordPress available in 200 languages.
\n\n\n\nLast but not least, thanks to the volunteers who contribute to the support forums by answering questions from WordPress users worldwide.
\n\n\n\nParticipation in WordPress is not limited to coding. If contributing appeals to you, learning more and getting involved is easy. Discover the teams that come together to Make WordPress, and use this interactive tool to help you decide which is right for you.
\n\n\n\n\n\n\n\nOver the past two decades, WordPress has transformed the digital publishing landscape and empowered anyone to create and share, from handcrafted personal stories to world-changing movements.
\n\n\n\nThe present and future of WordPress hold exciting opportunities for everyone, builders and enterprises alike. The foundational work for Phase 3 of the roadmap continues, with efforts focused on fostering real-time collaboration and streamlining publishing flows to improve how creators and teams work together in WordPress.
\n\n\n\nStay on top of the latest news and contributing opportunities by subscribing to WordPress News and the WP Briefing podcast.
\n\n\n\n\n\n\n\nThe smooth feel of jazz
The cutting-edge of the web
Install 6.4
The third release candidate (RC3) for WordPress 6.4 is ready to download!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC3 on a test server and site.
\n\n\n\nWordPress 6.4 is slated for release on November 7, 2023—less than a week away. If you haven’t tried it, now is the time.
\n\n\n\nYou can test WordPress 6.4 RC3 in three ways:
\n\n\n\nwp core update --version=6.4-RC3
Read the RC1 announcement for featured highlights, and check the Make WordPress Core blog for 6.4-related posts. If you are looking for detailed technical notes on new features and improvements, the WordPress 6.4 Field Guide is for you.
\n\n\n\nThe WordPress 6.4 release is brought to you by an underrepresented gender release squad to welcome the participation and partnership of those who identify as gender-underrepresented in the WordPress open source project.
\n\n\n\n\n\n\n\nThanks to everyone who has tested the beta and RC releases. Since RC2 was released on October 24, there have been more than 25 issues resolved. You can browse the technical details for all recent updates using these links:
\n\n\n\nIt’s recommended to use PHP 8.1 or 8.2 with the upcoming 6.4 release. Refer to WordPress 6.4’s PHP compatibility post for more details.
\n\n\n\n\n\n\n\nWordPress is open source software made possible by a community of people collaborating on and contributing to its development. The resources below outline various ways you can help, regardless of your technical expertise.
\n\n\n\nYour feedback and help in testing are vital to developing the WordPress software and ensuring its quality. It’s also a meaningful way for anyone to contribute. Check out this guide for instructions on testing WordPress 6.4 features.
\n\n\n\nThe core Query block requires more testing and feedback to ensure the latest changes to prevent full page reloads work smoothly. Please note that this setting was called “Enhanced pagination” but has recently been renamed, and it’s now referred to as “Force page reload” instead.
\n\n\n\nIf you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
\n\n\n\nCurious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
\n\n\n\nDuring the release candidate phase of WordPress 6.4, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.
\n\n\n\nDo you build themes and plugins? Your products play an integral role in extending the functionality and value of WordPress for users worldwide.
\n\n\n\nHopefully, you have already tested your themes and plugins with WordPress 6.4 betas. With RC3, you will want to continue your testing and update the “Tested up to” version in your plugin’s readme file to 6.4.
\n\n\n\nPlease post detailed information to the support forums if you find compatibility issues.
\n\n\n\nHelp the Docs team put the finishing touches on end-user documentation in time for the 6.4 release. Find out what’s needed and how you can help in this post.
\n\n\n\nDo you speak a language other than English? ¿Español? Français? Português? Русский? 日本? Help translate WordPress into more than 100 languages.
\n\n\n\n\n\n\n\nOne more week of prep
One more week to test the code
One more week til launch
Thank you to the following contributors for collaborating on this post: @meher, @rmartinezduque, @sereedmedia, @jorbin, @luisherranz, @marybaum.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16247\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"WP Briefing: Episode 65: Little Sun Success\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://wordpress.org/news/2023/10/episode-65-little-sun-success/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Oct 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16227\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:340:\"Join WordPress Executive Director, Josepha Haden Chomphosy, as she looks at a recent WordPress success story with Little Sun. To help us, we spoke to two special guests with Little Sun, Romane Guégan, Senior Press and Communications Manager, and Ashley Mrozek, Senior Digital Manager. Don’t miss this opportunity for an insider’s look!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:51:\"https://wordpress.org/news/files/2023/10/WPB065.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:21512:\"\nJoin WordPress Executive Director Josepha Haden Chomphosy as she looks at a recent WordPress success story, the clean energy solution Little Sun, and learns about their WordPress story.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Special Guest: Romane Guégan
Special Guest: Ashley Mrozek
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, I’ve got a special guest with me. I have here a couple of folks from Little Sun, a nonprofit organization that recently moved its entire online presence to WordPress. And we’re talking everything from their mission statement and donations all the way to their blog and shop.
\n\n\n\nWelcome both to the WordPress Briefing.
\n\n\n\n[00:00:59] Ashley: Thank you.
\n\n\n\n[00:01:00] Romane: Thank you.
\n\n\n\n[00:01:01] Josepha: We have with us Little Sun today. Can you start by introducing yourselves and your organization? Just tell us a little bit about what you all do.
\n\n\n\n[00:01:08] Romane: Hi, my name is Romane Guégan. I’m a Senior Press and Communications Manager at Little Sun.
\n\n\n\n[00:01:14] Ashley: And I am Ashley Mrozek. I’m the Senior Digital Manager.
\n\n\n\n[00:01:17] Josepha: So what does Little Sun do for the folks who are listening and maybe don’t know about it yet?
\n\n\n\n[00:01:22] Romane: Little Sun brings full power and light to communities that live off the grid, with the focus on sub-Saharan Africa because most of the people who lack access to electricity and need them. And we also inspire people to take climate action globally.
\n\n\n\n[00:01:39] Ashley: So access to solar energy helps kids who don’t have electricity and study at night. They can complete their homework at night. If their schools are in a more rural area, they will have a light to kind of guide them back home.
\n\n\n\nWe also work on a lot of electric vocation projects and hospitals. So we’re, we’re kind of supporting labors that are, are taking place in the evening, after the sun goes down, among other things.
\n\n\n\n[00:02:07] Josepha: Yeah. It’s, I, I think that that is one of the things that folks, probably most of my listeners, probably take for granted, like the easy access to light. And as we all know, the sun is around a lot. And so that is one of our most readily available resources other than potentially wind power. But I think that that is a great mission. And I really think that that’s wonderful work that y’all are doing.
\n\n\n\nSo, is there a particular reason that you focus on sub-Saharan Africa? Is that where you find a majority of people who don’t have access to that kind of resource are?
\n\n\n\n[00:02:43] Romane: Yeah. 70% of those people actually need in sub-Saharan Africa, where solar is actually a viable source of energy. Actually, it’s only 1% of solar, of the solar capital of the generation when we actually deliver solar energy there because there is so much potential.
\n\n\n\n[00:03:04] Josepha: That’s amazing. So you said that you all were funded in 2012. I imagine that your business has evolved over time. So, obviously, you all are WordPress users. That’s why we have you here with us today. But before we get into the questions about WordPress itself. Why don’t you tell us a bit about how your business needs evolved over time and how you wound up needing a solution that did use WordPress?
\n\n\n\n[00:03:31] Ashley: So I would say our focus and kind of the different initiatives that we’ve taken on since 2012 have shifted a lot based on various reasons, where our donors are, where we’ve kind of found the most need, and where we can be the most impactful.
\n\n\n\nAnd I think as we go into those new geographies, our online presence has become more and more important.
\n\n\n\n[00:03:55] Josepha: So, before you all switched to WordPress, I understand that you had several sites that you had to merge into one. And so I assume that as you evolved the business and your focus has changed, you realized you needed something a bit more streamlined. So, how was that transition, that migration from a lot of different sites to one big site?
\n\n\n\n[00:04:17] Romane: Yeah, because we started as a global project. And then, with the time, we evolved, actually also getting new donations. And in the past, we used to have one website where we have our webshop and our mission, our vision, all of our project descriptions.
\n\n\n\nBut then we had another website only for the foundation. And then you had another foundation in the U.S. So it was the question, okay, how do we put everything together? So we actually switched from littlesun.com to littlesun.org with WordPress, and it was amazing to see how we managed with the team to create an ecosystem approach, including impact, but also sales, and fundraising.
\n\n\n\n[00:05:02] Josepha: That was a big footprint that you all had, and you kind of consolidated it into one. And for all of our folks listening on the podcast, I’m going to include some links, not only to their site but then also to a few other things that we’ve mentioned in here today. So, since you made that change, how has it, how has that impacted the way that you all work with your site or with your online presence?
\n\n\n\n[00:05:27] Ashley: Yeah, I think using WordPress and having access to WordPress has been hugely valuable for us. We’re a small team, we’re a nonprofit, so it is pretty scrappy. Everyone is kind of doing a lot of different things. We don’t have a dedicated development team. And so being able to easily customize our pages and create new landing pages or make adjustments on the site without that development help has been valuable.
\n\n\n\n[00:05:55] Josepha: Yeah, so you don’t have a developer team now. Did you have a developer team when you had all the sites?
\n\n\n\n[00:06:01] Romane: We just still work with freelancers.
\n\n\n\n[00:06:03] Josepha: Okay, yeah. I am also not a developer, for what it’s worth, and have been working with nonprofits for a while. And I understand that problem where you have all these things you need to do and want to do, but there are also things you absolutely have to focus on in order to make your mission possible and your vision come true.
\n\n\n\n[00:06:23] Ashley: Yeah, and I think, I think WordPress has given us a lot more, like a lot more flexibility to kind of produce new content quickly. And because of that, it’s just been a lot more efficient, too, for us, you know.
\n\n\n\n[00:06:38] Josepha: And you all are using Blocks? Are you, like, the best Block builders?
\n\n\n\n[00:06:42] Romane: Yeah, I love Blocks.
\n\n\n\n[00:06:43] Josepha: Blocks are a fairly new innovation for the history of WordPress. WordPress has been around for 20 years, so we’re a nice, mature project. And we’ve really only had blocks as a functional part of the CMS for probably the last five or so. We’ve been working on the project a little bit longer. And it has been fascinating to me, like, in my own work that I have done with WordPress, kind of outside of my work with the project, to see, like, how much autonomy you get to have back as somebody who is not a developer, maybe isn’t a designer, but you do know exactly what you need to have on your site today, right?
\n\n\n\nAnd having to stop and find a freelancer or stop and find some set of developers who can make those changes. For me, when I was specifically working on nonprofit stuff. That was always kind of a moment where I was like, well, I guess I’ll just go to Facebook and put that on there or something because I was faster than trying to find someone to come help you. And so, I’m so glad you love the block.
\n\n\n\n[00:07:48] Ashley: We’ve created many a landing page.
\n\n\n\n[00:07:50] Josepha: Also, your site is adorable, and your brand is adorable, in case no one’s mentioned that lately. Super cute. Super cute.
\n\n\n\n[00:07:58] Josepha: So, we’ve talked about how you kind of took a bunch of stuff and made it into one big thing and how that’s been easier for you all to manage it. But from the standpoint of just, like, somebody who’s running a nonprofit, someone who’s running an organization, how has that transition been for your team? I know you said you don’t have a huge team, but was the move toward WordPress a net benefit over time, or was it immediately beneficial? Like, how has that been for your team?
\n\n\n\n[00:08:27] Romane: So what’s interesting actually is that we have a team that is spread also all over the world. And so we have teams in Berlin and in U.S., and New York. In Zambia, too. What was really interesting was how people identify to the new website because now we have to really think, okay, what is the content we want people to see, but also we want our critics to see. And so it kind of unified all of our content at Little Sun. And it was much more like much easier to understand afterwards.
\n\n\n\n[00:09:03] Josepha: Yeah.
\n\n\n\n[00:09:04] Romane: And it was because we also work at the intersection of creative communications, impacts, fundraising, technology, and to be able to put everything and have it on the front. And then have the stories to tell the stories from sub-Saharan Africa, from universities who got either a Little Sun lamps or solar systems, and then we have the donation page, so basically everything could be integrated in a super easy way, and it could target different audiences easily, either it’s someone who wants to partner with us, or a donor, or just someone who wants to be part of our solar training.
\n\n\n\n[00:09:46] Josepha: Yeah, and I mean, I think that no one will be surprised to hear that if you have multiple things that you have to get everybody to, it really increases the amount of marketing that you have to accomplish, rather than having one place for everyone to go too, and they can see everything that they might want once they arrive. So, that’s wonderful.
\n\n\n\n[00:10:06] Ashley: I think I was just going to say, or kind of echo what Romane said about the fact that we have so many different audiences, we have partners, we have donors, we have people who are just coming to learn about solar energy, or who are interested in purchasing a lamp. I think prior to this, it was a little bit confusing for those different audiences to kind of navigate to where they were intended to go to on the site, and now it’s much more cohesive. And we often hear that from people where it’s like, it’s quite easy to, to kind to find what they need to find on the site.
\n\n\n\n[00:10:39] Josepha: I define the WordPress community as anyone who is using WordPress, regardless of whether they know it or not. And so you all, in my mind, are part of the WordPress Community. And I just wondered if being part of that community has changed your approach to the way that you manage your content online or the way that you have chosen work with your business as like an online entity that also does on-the-ground, in-person thing?
\n\n\n\n[00:11:06] Ashley: I think definitely. I think we’re kind of going back to what I said before. I think we’re much more efficient now. I think in the past, it’s the idea of, like, well, getting this web page live or publishing this is going to be, you know, we have to think about a huge timeline, that’s, is going to require a lot of resourcing, a lot of different types of expertise and people, and everything now feels like something that we can, we can launch pretty immediately, which is really wonderful too.
\n\n\n\nI would also say just like being a part of the WordPress community too. It’s the sort of support that we’ve gotten from your team. It’s always really tailored. And I think as a nonprofit working with a, like, a much bigger business, you can be apprehensive sometimes, feeling like you won’t really get that personalized support.
\n\n\n\nAnd I think that’s something that’s been so nice with WordPress. Is really feeling like the people we’re working with are understanding our business and taking the time to understand our needs. And I think that makes us think differently about our online presence as well because then we feel like we have that additional support, which is great.
\n\n\n\n[00:12:12] Josepha: I’m always a fan of hearing that people who are passionate about WordPress are also passionate about helping others with WordPress. That’s one of my favorite things about us. That’s not true. I have like 25 favorite things about us. And so I need to stop saying that I have one favorite, but I never will.
\n\n\n\nOkay, well, do you all have any last thoughts that you just want to share with me or podcast listeners that we have?
\n\n\n\n[00:12:36] Ashley: Yeah, I think the, the plugins and integrations have been really useful for us. I think it can be really intimidating to bring on, like, a new tech solution or tool and feel like everything that you are already working with or have is going to become outdated or obsolete in some way. And I think it’s just been really nice to work with WordPress and have all of those transitions be really seamless for everything to connect really well. Yeah, I think that’s been. That’s hugely helpful too.
\n\n\n\n[00:13:07] Josepha: So, was that part of the decision-making process? Like, do I know that this software will be around in the future so that you’re making an investment in the site now and know that it’s going to hang around now you can find people help? Like, was that part of the decision-making process?
\n\n\n\n[00:13:21] Ashley: I think so. I mean, I guess I wasn’t completely around during the time, but I would say, like, that’s definitely something that we’re considering in any kind of tech that we’re thinking about is it can require so much work to, to kind of bring something on with such a small team. So we want to ensure that, yeah, it’s going to last, it has longevity, and it’s going to work with the tools that we already have. So I think all of that is really important for sure.
\n\n\n\n[00:13:48] Josepha: Well, thank you both so much for joining me. Like I said, we’ll have a link to littlesun.org in the notes so that you all can learn more about their project and see their beautiful site with their beautiful little solar sunflowers.
\n\n\n\nThank you both for being with me today.
\n\n\n\n[00:14:04] Romane: Thank you so much.
\n\n\n\n[00:14:05] Ashley: Thank you so much for having us.
\n\n\n\n[00:14:07] (Music interlude)
\n\n\n\n[00:14:11] Josepha: What a wonderful organization. I’m so glad that they found WordPress and that it works for them. Let’s continue our tour today with the small list of big things.
\n\n\n\nItem number one, it’s time to save the date: December 11th, 2023, for this year’s State of the Word. State of the Word is the annual keynote address delivered by the WordPress Project co-founder Matt Mullenweg. Every year, the event shares reflections on the project’s progress and aspirations for the future of open source. And so, if that is something that you like to tune into, December 11th is your day.
\n\n\n\nSecond thing on our list is that we are celebrating our 10,000th photo submission. So, on October 11th, the 10,000th photo was approved. The Photo Team is one of the newest ways to contribute to the WordPress open source project, and it feeds all of those photos into Openverse as well.
\n\n\n\nThe third thing on our list today is that I want to tell you about a community team training module that just came out. It’s specifically about the Translate Live tool, and it is ideal for presenting at your local meetups to engage and onboard new translators for your native language. If you’re organizing a WordCamp, consider introducing this tool during your Contributor Day. I will leave a link for this in the show notes so that it is easy to find.
\n\n\n\nAnd item number four, the journey to update WordPress.org, continues with the launch of a new Showcase design. The Showcase is a natural starting point for a lot of visitors who are on WordPress.org. It inspires creativity and also demonstrates what’s possible with WordPress. So, stop on by there, it’s WordPress.org/showcase, and give it a bit of a look.
\n\n\n\n[00:15:58] Josepha: And that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. And don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever a new episode drops. And if you like what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard today, you can share those with me at wprebriefing@WordPress.org.
\n\n\n\nI’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:16:24] (Music outro)
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16227\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 6.4’s PHP Compatibility\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2023/10/wordpress-6-4s-php-compatibility/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 26 Oct 2023 08:40:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"PHP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16235\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:340:\"In an effort to keep the WordPress community up to date, this post provides an update on the PHP compatibility of the upcoming WordPress 6.4 release scheduled for November 7, 2023. Recommended PHP version for WordPress 6.4 It’s recommended to use PHP 8.1 or 8.2 with this upcoming release. Please refer to the Hosting page […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3117:\"\n\n\n\n\nIn an effort to keep the WordPress community up to date, this post provides an update on the PHP compatibility of the upcoming WordPress 6.4 release scheduled for November 7, 2023.
\n\n\n\nIt’s recommended to use PHP 8.1 or 8.2 with this upcoming release. Please refer to the Hosting page for more detailed information, including a few known issues.
\n\n\n\nReach out to your hosting company to explore PHP upgrade options.
\n\n\n\nPHP is a programming language on which the WordPress code is based. This language runs on the server, and it is critical to keep it updated for security and functionality. Various teams within the WordPress open source project work to both test and fix any issues with new PHP versions so you can update with confidence that the WordPress core software is compatible.
\n\n\n\nHappy WordPress-ing!
\n\n\n\nThank you to @annezazu @barry @ironprogrammer @hellofromtonya @chanthaboune @costdev @javiercasares for reviewing and contributing to the effort of this post.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16235\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 6.4 Release Candidate 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 24 Oct 2023 16:45:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:11:\"development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16219\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:163:\"WordPress 6.4 RC2 is ready for download and testing. Reaching this phase of the release cycle is an important milestone. Check out what\'s new and how you can help.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Meher Bala\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:6586:\"\nThe second release candidate (RC2) for WordPress 6.4 is now available!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC2 on a test server and site.
\n\n\n\nWordPress 6.4 is slated for release on November 7, 2023—two weeks from today. If you haven’t tried it, now is the time.
\n\n\n\nYou can test WordPress 6.4 RC2 in three ways:
\n\n\n\nwp core update --version=6.4-RC2
Read the RC1 announcement for featured highlights, and check the Make WordPress Core blog for 6.4-related posts. If you are looking for detailed technical notes on new features and improvements, the WordPress 6.4 Field Guide is for you.
\n\n\n\nThe WordPress 6.4 release is brought to you by an underrepresented gender release squad to welcome the participation and partnership of those who identify as gender-underrepresented in the WordPress open source project.
\n\n\n\nThanks to everyone who has tested the beta and RC releases. Since RC1 was released on October 17, there have been more than 25 issues resolved. You can browse the technical details for all recent updates using these links:
\n\n\n\nWordPress is open source software made possible by a community of people collaborating on and contributing to its development. The resources below outline various ways you can help, regardless of your technical expertise.
\n\n\n\nYour feedback and help in testing are vital to developing the WordPress software and ensuring its quality. It’s also a meaningful way for anyone to contribute. Check out this guide for instructions on testing WordPress 6.4 features.
\n\n\n\nIf you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
\n\n\n\nCurious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
\n\n\n\nDuring the release candidate phase of WordPress 6.4, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.
\n\n\n\nDo you build themes and plugins? Your products play an integral role in extending the functionality and value of WordPress for users worldwide.
\n\n\n\nHopefully, you have already tested your themes and plugins with WordPress 6.4 betas. With RC2, you will want to continue your testing and update the “Tested up to” version in your plugin’s readme file to 6.4.
\n\n\n\nPlease post detailed information to the support forums if you find compatibility issues.
\n\n\n\nDo you speak a language other than English? ¿Español? Français? Português? Русский? 日本? Help translate WordPress into more than 100 languages.
\n\n\n\nYou have been waiting
Download and give it a test
RC2 is here
Thank you to the following contributors for collaborating on this post: @meher, @rmartinezduque, @michelleames, @cbringmann
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16219\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:12:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Fri, 17 Nov 2023 12:52:26 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:25:\"strict-transport-security\";s:12:\"max-age=3600\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Wed, 15 Nov 2023 20:05:33 GMT\";s:4:\"link\";s:63:\"WooCommerce 8.3 was released today, featuring Cart, Checkout, and Order Confirmation blocks as the default checkout flow for new installations. This is a major milestone in moving WooCommerce towards a block-first checkout experience.
\n\n\n\nVersion 8.3 was slightly delayed, as core developers worked to ensure it would be compatible with the latest changes in WordPress 6.4 as well as the upcoming PHP 8.3 release scheduled for November 23, 2023. They also wanted to give time for plugin developers to prepare for the new reality of cart and checkout blocks as the default. An FAQ document outlines the steps for developers who still need to make their extensions compatible.
\n\n\n\nDevelopers with extensions that don’t work with the new default blockified checkout are encouraged to declare their plugins incompatible, so WooCommerce can display a message to users in the settings sidebar. (No action is required for plugins that do not extend the cart and checkout flow).
\n\n\n\n\n\n\n\nimage source: FAQ: Cart and Checkout Blocks by Default\n\n\n\nAlthough existing stores are not impacted by cart and checkout blocks becoming the default, merchants can easily opt into the experience using WooCommerce’s migration tool located at WooCommerce > Status > Tools > Create Pages. This tool will automatically generate the new pages with a block-based checkout flow. The blockified Order Confirmation template is currently only available to stores that are using block themes.
\n\n\n\nOther notable changes in WooCommerce 8.3 include the following:
\n\n\n\nWooCommerce 8.3 includes 682 commits to the core plugin, along with 231 commits rolled in from WooCommerce blocks, thanks to the efforts of 96 contributors. Check out the changelog for a more detailed look at the many fixes, tweaks, and enhancements included in the release.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 17 Nov 2023 03:16:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"Do The Woo Community: De Nederlandse WordPress Community – The Dutch WordPress Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78162\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"https://dothewoo.io/de-nederlandse-wordpress-community-the-dutch-wordpress-community/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:466:\"In ons programma Community Voices, WordPress Around the World zetten we de Nederlandse gemeenschap in de spotlight voor een gesprek in hun moedertaal.
\n>> The post De Nederlandse WordPress Community – The Dutch WordPress Community appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 09:27:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"WPTavern: Elementor Pro Pricing Update Slashes Features in the Essential Plan for New Customers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151354\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"https://wptavern.com/elementor-pro-pricing-update-slashes-features-in-the-essential-plan-for-new-customers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8024:\"Elementor, the most popular website builder plugin for WordPress with more than 5 million active installations, has announced major changes coming to the features included in its Elementor Pro Essential subscription plan.
\n\n\n\nThe plan will still include the Theme Builder along with access to 50+ Pro widgets, basic marketing tools, and the Form widget, but it will shift other more advanced features to the more expensive pricing tiers:
\n\n\n\n“Going forward, when you purchase the new Elementor Pro Essential, you will have all the features you need to create a complete basic website, and also gain access to new features that will be part of the Essential plan,” Elementor Senior Product Marketing Manager Gabriella Laster said. “For more professional capabilities like the Popup Builder, e-commerce features including PayPal button, Stripe button, and the full WooCommerce Builder or collaboration tools like Notes or the Role Manager, you will need to upgrade to the Advanced plan or higher.”
\n\n\n\nThe changes, which are detailed in a comparison chart in the announcement, will be rolled out on December 4, 2023. It will not affect existing subscribers or other subscription plans:
\n\n\n\n\n\n\n\n\nExisting Essential subscribers get to keep all current features.
\n
If you have a valid Elementor Pro Essential subscription, you can keep your subscription with all the features currently available to you, at no additional cost. You’ll also be able to renew your subscription upon expiration, while keeping all the features currently available in your plan. Some new features, released to the higher plans, will not be available as part of your current Pro subscription.
Scott Kingsley Clark, lead developer of the Pods Framework, commented on the news in Post Status’ Slack in regards to how Pods will support Elementor users in the future.
\n\n\n\n“Elementor Pro is removing things like ACF/Pods integration from their lowest tier ‘Essential’ plan in December,” Clark said. “Existing subscribers keep the functionality but anyone getting new licenses after Dec 4th won’t have those.
\n\n\n\n“It’s not super clear since I don’t use the other features whether they’ve removed many other things or if some of those things are actually new features shipping in December to just the other plans.
\n\n\n\n“The impact of this is that I’ve chosen to replace the Elementor Pro integration for Pods that they provide — with a more complete alternative solution within the Page Builder Toolkit add-on. Previously, only new Pods-centric widgets were added. Soon I’ll add dynamic content support for Pods that will be available as a better alternative to what is in Elementor Pro currently.”
\n\n\n\nConcerned Elementor customers reacted to the news on X/Twitter as well as in the comments of the announcement, many looking for reassurance that the features they paid for will still be accessible to them after the change.
\n\n\n\nThe anti-Elementor crowd responded to their concerns in a critical and dismissive way, using the news of the modified plans as an opportunity to express and reinforce their disapproval of the page builder. This prompted those who are reluctantly using the tool to ask for viable alternatives in the comments of the tweet.
\n\n\n\n \n\n\n\nElementor has had a somewhat contentious relationship with the open source project, as it has historically marketed itself against WordPress core. The plugin’s reputation has been saddled with bloat and performance concerns for years, calling its long-term future into question. The writing was on the wall for most page builders when WordPress decided to land full-site editing capabilities in core.
\n\n\n\nElementor has made a pattern of making major changes to pricing and plans while also guaranteeing legacy pricing for current customers. It’s one strategy for getting customers to lock in their auto-renewals to ensure a more predictable financial future for the company.
\n\n\n\nTwo months ago, Human Made engineer Fränk Klein sparked a conversation on X/Twitter contending that “Elementor will disappear as a standalone plugin, along with all other non-block page builders,” as the WordPress ecosystem moves to become block-first by default.
\n\n\n\n“Since 2022, all default themes are block themes,” Klein said. “WordPress.com is all in on blocks. WooCommerce is modernizing with blocks.
\n\n\n\n“For plugin authors the biggest return on investment is to use blocks. So it falls to the page builder developer to ensure that plugins integrate well. And that’s a difficult, tedious, and costly undertaking.”
\n\n\n\n \n\n\n\nWordPress co-founder and Automattic CEO Matt Mullenweg also weighed in on the news, indirectly referencing Elementor’s latest move to slash features in its Essential tier.
\n\n\n\n“As Gutenberg gets more capable, non-Gutenberg site builders will likely need to continue raising their prices, as one is in the news for today, to maintain revenue churn in the face of higher churn and fewer new users,” Mullenweg said. “I don’t [think] this trend will happen for the Gutenberg-based ones.
\n\n\n\n“They’ll also need to spend more to keep up, as they have to duplicate all the engineering that’s going into core. This is why we asked them all to plan on Gutenberg since we started development in 2017. Phases 1 and 2 also could have gone a lot faster with their help. The pace of iteration is pretty relentless.”
\n\n\n\nElementor’s decision to reallocate features across pricing tiers is a response to the shifting dynamics within the page builder landscape and the increasing cost of supporting so many third-party integrations in the entry level plan. WordPress users and developers are slowly reevaluating their relationship with page builders, as every core release puts a greater emphasis on block-based editing for both content and design. This is a fundamental shift in how WordPress websites are built and page builders will continue to be challenged in striking a balance between innovation, user expectations, and business sustainability.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 04:37:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WordPress.org blog: State of the Word 2023 – Madrid, Spain\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16429\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2023/11/state-of-the-word-2023-madrid-spain/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3672:\"\n\n\n\nThe countdown is on for this year’s State of the Word! If you missed the initial announcement a few weeks ago, you’ll want to mark your calendars for December 11, 2023.
\n\n\n\nState of the Word is the annual keynote in which WordPress co-founder Matt Mullenweg celebrates the progress of the open source project and offers a glimpse into its future.
\n\n\n\nFor the first time, State of the Word ventures beyond North America, bringing the WordPress community to a new and vibrant city that plays a vital role in the WordPress project — Madrid, Spain! The event will be live-streamed to WordPress enthusiasts and newcomers around the globe via the WordPress YouTube channel.
\n\n\n\nPlease visit the event website for more event details and live-streaming information.
\n\n\n\nWhat: State of the Word 2023
When: December 11, 2023, 15:00 UTC (Start of live stream)
Where: Palacio Neptuno, Madrid, Spain
Streaming: Watch the live stream on the WordPress YouTube channel.
Tickets: Request a ticket to attend in person.
Please note that the venue’s capacity is limited; therefore, not all ticket requests will be granted.
Meetups: The community will sponsor several local watch parties globally, both in
person and online. Find one near you or organize one.
State of the Word will include a Q&A session. If you want to participate, you can send your question to ask-matt@wordcamp.org or ask during the event via the Q&A app Slido. A QR code for your submission will be provided during the event live stream.
\n\n\n\nGiven the volume of questions usually submitted, only some will be answered live, while others will be covered in a follow-up post published after the event on make.wordpress.org/project.
\n\n\n\nIs this your first State of the Word? Check out prior events on WordPress.tv for an introduction to the format.
\n\n\n\nSee you in person and online on December 11!
\n\n\n\nThank you to Reyes Martínez and Chloé Bringmann for reviewing this post.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Nov 2023 20:03:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"WPTavern: #99 – Matthias Pfefferle on ActivityPub, WordPress and Decentralised Social Networks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=151341\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:109:\"https://wptavern.com/podcast/99-matthias-pfefferle-on-activitypub-wordpress-and-decentralised-social-networks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:54692:\"Transcript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.
\n\n\n\nJukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, how the ActivityPub plugin can make WordPress the center of your social networks.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox and use the form there.
\n\n\n\nSo on the podcast today, we have Matthias Pfefferle. Matthias started using WordPress in its early stages when it was still known as b2. He became passionate about blogging and the web 2.0 era. Over time he dedicated himself to making blogging relevant and developed various tools to compete with social networks, building communities professionally and working for a European hoster. Matthias ultimately joined Automattic to focus on WordPress and the ActivityPub plugin full-time.
\n\n\n\nWe start off talking about the importance of owning your own content, and how it grants us control over what gets published and when it gets deleted or amended, Matthias introduces us to Mastodon, a social network that operates on a non algorithmic, chronological feed. This means that the content is displayed in the order it was created. Breaking free from possibly addictive patterns we see in other platforms.
\n\n\n\nWe learn about the Fediverse, where users can set up their own servers and customize their own rules. Matthias explains how servers communicate with each other through following and federating, creating a truly decentralized network. He shares insights into how relays can be used to generate traffic and activity on new Mastodon servers should you find your feet a little quiet at the start?
\n\n\n\nThere’s definitely some new workflows to learn using the Fediverse and Matthias highlights the differences between Twitter and the Fediverse, with the latter starting off quiet and gradually growing as users find and interact with others.
\n\n\n\nHe introduces us to the ActivityPub plugin for WordPress, which allows users to publish their blogs on Mastodon, and federate the content to different servers. We get an explanation of how it works, what it does, and where it strays from the way you’re used to interacting with a proprietary platform.
\n\n\n\nWe discussed the various waves of migration to Mastodon and the factors that triggered them, including Reddit’s decision to monetize that API. Matthias sheds light on the challenges faced by decentralized networks, and how wordpress.com has implemented his ActivityPub plugin, albeit in a modified form, making it easier for users to migrate their accounts. The adoption of the plugin has been steadily rising and Matthias expresses his confidence in the plugin’s potential, citing the press coverage and impact of Automattic’s takeover.
\n\n\n\nHe also provides insights on how interactions on Mastodon federate, explaining how likes, comments, boosts, updates or deletions to blog posts are reflected across platforms.
\n\n\n\nTowards the end, Matthias shares his thoughts on the future of federated social networks and the potential support from existing platforms like Meta. He emphasizes the profound benefits of using protocols like ActivityPub, allowing users to own their own data and have more control over their content, unlike closed platforms that can delete accounts and cause data loss.
\n\n\n\nIf you want to learn more about the Fediverse, Mastodon, ActivityPub, or just want to know how to make WordPress a first-class citizen in social networks, this podcast is for you.
\n\n\n\nIf you’re interested in finding out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast. Where you’ll find all the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Matthias Pfefferle.
\n\n\n\nI am joined on the podcast by Matthias Pfefferle. Hello, Matthias!
\n\n\n\n[00:05:03] Matthias Pfefferle: Hello, Nathan.
\n\n\n\n[00:05:04] Nathan Wrigley: I’m really, really pleased to have you on the podcast today. This topic is something which is actually quite dear to my heart. Sometimes we stray into these topics. But Matthias is here today to talk about ActivityPub.
\n\n\n\nThis may be something that you’re entirely familiar with. It may be something that you have never heard of before. Perhaps a better way to describe it would be the Fediverse, or maybe even Mastodon, that might get your intuitions going.
\n\n\n\nBefore we get stuck into all of that, Matthias, I wonder if you wouldn’t mind just telling us a little bit about your background with WordPress or technology, whichever way you wish to take it. But little bio just to give us an indication of who you are.
\n\n\n\n[00:05:42] Matthias Pfefferle: Okay. I started with WordPress when it was called b2. So it was really early, and I fell in love with the whole blog thing and the web 2.0 area. I think over the time I tried to keep that momentum and tried to keep blogging relevant. And I think that’s why I built a lot of stuff around WordPress to compete with social networks, and made that in my spare time and liked that and made it my profession.
\n\n\n\nI started on the bad side, professionally building communities, and then I had a quite long time at a European hoster, and finally I joined Automattic to work full time on WordPress and ActivityPub.
\n\n\n\n[00:06:36] Nathan Wrigley: How long ago was it that you joined the Automattic crew?
\n\n\n\n[00:06:40] Matthias Pfefferle: It was this year, it was in April.
\n\n\n\n[00:06:42] Nathan Wrigley: Yeah. I remember the news coming out, and I was so delighted of this news because of everything that we’re going to talk about today. I was delighted because it enables you to concentrate full time I think, I could be wrong about that, but I think you’ve got the opportunity to work full time on a plugin.
\n\n\n\nIt’s a freely available plugin. It’s called ActivityPub, it’s two words combined as one really. And ActivityPub combines the Fediverse really. It’s the architecture that’s going on behind all things in the Fediverse. It’s the protocol, if you like, which binds all of the different social networks and things which sit on top of it.
\n\n\n\nI feel it might be a good idea to actually explain what ActivityPub is, and what it does and how it works. Now I realised we haven’t got any screens on, I realise some of it might be a little bit difficult to explain. But broadly speaking, what is the ActivityPub protocol? Not your plugin just yet, but what is the protocol, and how does it sit behind the Fediverse?
\n\n\n\n[00:07:45] Matthias Pfefferle: I think I would like to start with the Fediverse because that’s even older. The Fediverse is also a word combination between federated and universe, and it’s kind of the idea to have decentralised social networks. It’s not directly equated with ActivityPub, but I think the actual protocol that every social network, every decentralised social network is speaking is ActivityPub. So at least for the time being, you can equate that.
\n\n\n\nBut the idea of the Fediverse is way older than Mastodon and ActivityPub. And ActivityPub is kind of the newest protocol. There were way more over the years. Maybe Diaspora, someone remembers Diaspora back in the days. The Facebook killer.
\n\n\n\nThe actual protocol is ActivityPub. And I think ActivityPub is so famous because of two different things. The one is that it’s fairly easy to implement. And the other thing is that Mastodon made a real good product on top of it. Really nice, usable product. Nice UI, easy to understand.
\n\n\n\n[00:09:04] Nathan Wrigley: So does the ActivityPub protocol, does it govern things like, for example, this is a piece of text, this is an image, this is a poll, this is published on this particular date. What exactly is it in a sort of technical sense?
\n\n\n\n[00:09:20] Matthias Pfefferle: Let’s talk about that. ActivityPub is the email version of a social network. Every server has, or every user has, its outbox and inbox at a server. And they’re floating activities from your outbox to the other inboxes and vice versa. And an activity describes every activity you can do on a social network.
\n\n\n\nIt’s follow, create a post, delete a post, unfollow. And everything is described in a unified json object. And it’s really easy to understand and to model these activities. And it’s really only kind of the same modeled activities floating back and forth between the different servers, describing everything you just did or do.
\n\n\n\n[00:10:15] Nathan Wrigley: Okay, it’s the protocol which sits behind all of the typical things which a social network would need. So in that case, I guess the next question from me would be, who decides what’s in the protocol? Is it an open platform in the same way that WordPress is? And who decides ultimately which ideas get adopted, which ideas don’t get adopted?
\n\n\n\nIs it a fairly glacial experience working with it? In other words, has it settled down over the years and is basically now not that much flux going on? Or yeah, how movable, how changeable is it, and who is in charge of deciding what goes in it?
\n\n\n\n[00:10:52] Matthias Pfefferle: That depends. The protocol was defined by the W3C. So it’s well crafted specification. But it wasn’t updated since it first was published. So the initial version was published by the W3C, and back in the days they worked together with different communities, also the IndieWeb community. There were a bunch of people of the IndieWeb community involved, and there were also the authors of a predecessor of the ActivityPub protocol, OStatus, and later ActivityPump I think.
\n\n\n\nBut the original specification doesn’t change over the time. But specification is based on, ActivityPub is based on JSON-LD, and JSON-LD is defined to be extensible. So you do not have to change the spec to add your own kind of flavor to the activities, or to define your own activities.
\n\n\n\nThe actual version we are currently using is mostly defined by Mastodon, because Mastodon is kind of the big player in that area. So the Mastodon community added lot of extra stuff on top of ActivityPub and made their own extensions to the activities. And because they’re the biggest one, and require a lot of these extensions, I think the current used version is highly customised by, or influenced by, Mastodon.
\n\n\n\n[00:12:40] Nathan Wrigley: Okay, great. Thank you. So that’s really interesting. There’s a lot in there that I didn’t actually know, so thank you for that. How does the use of the ActivityPub protocol, and you described that the Fediverse is older, and it basically means decentralised networks. How does that differ from the networks that we’re all very familiar with?
\n\n\n\nSo I know it’s a very obvious question, but it may very well be that there’s people listening to this who’ve never experienced a decentralised network. So let’s put, say something like Mastodon, let’s just use that as an example, as a social network if you like. Let’s compare it to another incumbent, something like Twitter or Facebook.
\n\n\n\nHow does ActivityPub allow things to be different? What are basically the key differences between an implementation on ActivityPub and some closed system like Facebook or Twitter or something?
\n\n\n\n[00:13:30] Matthias Pfefferle: I think you can compare that also with email perfectly, because it doesn’t matter where you host your email address. It can be the big player, you can host it on your own. The one you want to send an email to always receives the email.
\n\n\n\nAnd that’s kind of the same for Mastodon. It doesn’t matter on which Mastodon server you are, or you registered. You can follow everyone on every other Mastodon server, regardless of the country of the hosting environment. And not even limited to Mastodon, but you can follow everyone that is using, or everyone that is using a platform that uses ActivityPub, if that makes sense.
\n\n\n\n[00:14:14] Nathan Wrigley: That’s perfect. I think the email analogy is really excellent, in the sense that we’re all using different providers for email, but it would be an entirely pointless enterprise if I could only communicate with you, if you were sharing the same email hosting company that I was. That would make the whole thing completely inoperable.
\n\n\n\nAnd I guess at this point, it might be a good idea to explain what you were talking there about Mastodon instances. So we’ve thrown the word instance out there. And if you’ve used social networks before, you’re much more familiar with the notion that you sign up for that network and you’ve got to log in credential for that network. And wherever their computers are stored in the world, it doesn’t matter. You sign in, you go to their homepage, you log in and you are logged in.
\n\n\n\nMastodon and all of these other things built on top of ActivityPub, the Fediverse, for want of a better word. They operate on a completely different model, in that you can set up your own instance of Mastodon. You can set one up, I can set one up. In fact I have set one up. And I’m sure you have set one up. In fact, I’m sure you’ve probably set up dozens in your work that we’re going to talk about.
\n\n\n\nAnd mine will interoperate with yours. So you will be able to communicate with me. The people from yours will be able to see the people from mine. And it’s a social network, but it’s not housed behind one company. It’s made of hundreds, thousands, tens of thousands, millions of smaller entities all talking to each other. Have I described that correctly?
\n\n\n\n[00:15:41] Matthias Pfefferle: Perfect.
\n\n\n\n[00:15:42] Nathan Wrigley: If that’s the case, the way that Mastodon and all these other things are set up, does that cause a bit of friction for people? Because everybody’s so familiar with, you go to the homepage, you create an account, and from that moment on everything’s really straightforward. You log into that service and you start creating your content. Or posting, or communicating, or chatting, whatever it may be.
\n\n\n\nWith Mastodon and other services there’s a little bit of friction there because it’s not that typical workflow. You’ve got to decide on an instance. And I wonder what your intuitions are, as to whether or not that has caused people to be a little bit sceptical of how it works and maybe stopped the growth that we might have had.
\n\n\n\n[00:16:20] Matthias Pfefferle: That’s a really good question. And I think it’s because of, we are at the beginning of this new federated idea of social networks. And I think in that beginning, it’s really complicated to understand that there are different servers that do the same in the end, and how to choose your server, and how the following process is working. Because it’s not simply searching for the username, because he could be on a different server and not well known on the server you are on.
\n\n\n\nBut I think that’s a problem for the time being. But for the future, if you do not really choose the platform anymore, because the normal platforms you are already using will support ActivityPub. I do not think that this will be a friction in the next five years.
\n\n\n\n[00:17:18] Nathan Wrigley: Yeah. So maybe it’s just a consequence of the age of it. You’ve got to select a server right at the outset, and maybe somebody will come up with some amazing UX which just solves that problem, and makes that whole thing go away.
\n\n\n\n[00:17:31] Matthias Pfefferle: Yeah. But not only because of that. But let’s talk a bit about Meta and their new Threads community. They try to build up a microblogging service. And they plan to do that in the open and to support ActivityPub. And if such a big server, and such a big company decides something like that, then a lot of users simply use ActivityPub without knowing.
\n\n\n\nAnd others can follow them, and if you take the ActivityPub thing for WordPress. If you simply enable ActivityPub for WordPress, and you simply use WordPress as you always do, publishing posts, writing comments. And I think it’s not that big of a step if now others can follow you in a different way.
\n\n\n\nAt the moment you really have to decide to go into the Fediverse. You have to decide, I want to have an account on this Mastodon service. But I think in the near future, it’s kind of more ubiquitous. It’s kind of the services will support that and you do not have to actively decide to use it. But you simply have to understand that following is a bit different, if that does make sense.
\n\n\n\n[00:18:52] Nathan Wrigley: Yeah, we can get into all of that in a moment. So you mentioned Meta, Facebook, if you like, and Threads, which is their equivalent platform to something like Twitter or Mastodon or what have you. And the promise that at some point it would in fact interoperate with ActivityPub. Do you know if they followed through with that?
\n\n\n\nIn other words, did it interoperate with ActivityPub from the outset, or are they still in some sort of holding pattern where they’re checking it all worked? Because you’re right, somebody, some giant entity like Meta, Facebook, if they are throwing their weight behind it, it does cause everybody by default to start using ActivityPub without them knowing it.
\n\n\n\n[00:19:29] Matthias Pfefferle: They’re still experimenting with ActivityPub. There’s nothing published yet.
\n\n\n\n[00:19:35] Nathan Wrigley: It’s interesting, isn’t it? A company of size of Meta in these sort of experimental phases. Let’s hope that they honour that.
\n\n\n\n[00:19:42] Matthias Pfefferle: That’s what I meant with, this would be a game changer. Because this would allow my mum or my sister to be part of the Fediverse without knowing it. And they can simply use that without all the technical stuff we are discussing at the moment.
\n\n\n\n[00:19:59] Nathan Wrigley: So just from your perspective, and this question really is about you and what your thoughts are on it. Why do you prefer using ActivityPub, Mastodon, again these terms are sort of somewhat interoperable. But let’s go with Mastodon for the sake of argument.
\n\n\n\nWhy do you prefer using something like that to a quotes, closed platform like Twitter or LinkedIn or whatever it may be? What are some of the benefits that we may not have thought about before? Some of the consequences of using an open protocol as opposed to a closed protocol.
\n\n\n\n[00:20:35] Matthias Pfefferle: I think the biggest thing is owning my data, to not be dependent on a closed platform that can make everything with my data and decide if I can use or cannot use the platform. They can decide what I have to show, how my profile looks, and what are the security settings, what are the visibility settings.
\n\n\n\nI read an interesting article and the title was something like, the privilege of deleting a Facebook account, something like that. You put your whole life into a platform. You have your complete social graph, all your friends there. And if Facebook, for example, decides to ban you because of they decided, then you will lose not only all of your data but connection with your friends.
\n\n\n\nBack in the days, a lot of events only happened on Facebook. You decide who comes with an invite on Facebook. So if you’re not on Facebook, you will not be invited, in the worst case.
\n\n\n\nAnd back in the days I decided that I do not want to depend all of my life on such a closed network, and I want to choose where to publish stuff and if I want to delete it, if I want to share that. Yeah, I want to decide how and what to do with my content. And to be able to migrate platforms, for example, to not depend on a certain hosting environment, for example, or a certain platform.
\n\n\n\n[00:22:15] Nathan Wrigley: I guess it all sounds, unless that’s actually happened to you, the whole deleting of an account. It sounds almost like an implausible thing which would never happen. But I can definitely say from, not personal experience, but a very, very close friend of mine. For no reason whatsoever his Facebook account was deleted.
\n\n\n\nAnd this was fairly catastrophic because a lot of the network of friends that he had established was in Facebook. A lot of the content over the years that he had produced was in Facebook, and it disappeared. And to this day, this was probably about 8 or 9 months ago, to this day it has not come back.
\n\n\n\nAnd so I guess, dear listener, you’re probably a WordPress user if you’re listening to this podcast. The argument of owning your own content is not to be underestimated. Having everything that you’ve created at your disposal, when you like. You get to decide whether you delete your content. You get to decide which things get published, when and how it looks. All of that is absolutely the case.
\n\n\n\nI think for me, just extending what you said there Matthias, some of the things that are important to me on Mastodon as a social network, some of the benefits that I see is the non algorithmic feed. So the protocol in the current implementation at least, who knows what will happen in the future.
\n\n\n\nThe protocol spits out content only based upon the time at which it was created. So it’s a completely chronological feed. So if I don’t log in for six weeks, I will see the thing that was posted five minutes ago, as opposed to the thing which was posted six weeks ago. And it will be my job to scroll back in time.
\n\n\n\nPlus that feed is not being inspected by any kind of AI or sophisticated technology to punctuate it with advertising or sponsorship. And there’s no gamification about which things will arrive in my feed. So something which is proving to be popular gains no more weight in my feed than something which is not popular.
\n\n\n\nAnd so in that way, the whole enterprise is not engineered to keep me addicted to that feed, and keep scrolling, and keep looking, and keep investing more and more time. The purpose is just to serve it up chronologically. And it’s a real breath of fresh air, because you really do suddenly realise, okay, I am not spending a large amount of time on this because I’m not being gamed by the billions of dollars of AI investment that’s gone into making sure that I stay there as long as possible.
\n\n\n\nSo for me, there are a couple of other things there which really were beneficial. Although, maybe on the face of it, they don’t seem like it.
\n\n\n\n[00:24:50] Matthias Pfefferle: Yeah, exactly. And even if you would like to have some kind of AI powered algorithmic feed, then you can search the platform who supports that. That’s the nice thing about the Fediverse, you can choose the platform for your own preferences.
\n\n\n\n[00:25:06] Nathan Wrigley: So let’s just dwell on that a little bit. How do these servers communicate with each other? So, for example, I would imagine that the listeners to this are fairly technical. They’ll understand, you know, installing software on a remote server and things like that.
\n\n\n\nIf I wish to set up my own server, I can do that. I can download the software and if I’m prepared to read through the how to articles, I could set myself up with a server. It’s not without its difficulties, but there are also third party hosting companies, which will abstract away the difficulty in exchange for a few US dollars each month.
\n\n\n\nBut I could set up my server and I can come up with my own set of rules. I can invite people, block people, block other servers, allow everything, disallow everything, whatever I like. But, how do they actually communicate with each other? In other words, if I set up a brand new server, how does it even know what the other servers are doing? How does it begin to communicate with them all?
\n\n\n\n[00:26:01] Matthias Pfefferle: If you simply install a server, there will be no communication at all. So it simply starts with following others on different servers. And then start writing, and then it starts federating. So with the first user or the first follower on a different server, your server starts federating with others.
\n\n\n\nBut if it’s simply you, no followers, or only followers on your server, it will be a very simple and very lonely ecosystem.
\n\n\n\n[00:26:32] Nathan Wrigley: There would be utility in that though. If you wish to have a server, let’s say that you’ve got a company with a thousand employees, you could set up a server, block it looking out into the wider world and just stay in its own boundary. And in a sense you’ve got yourself a little intranet, if you like. You’ve got yourself social network for your own employees and nobody in that can reach out and discover anything elsewhere. So even that use case has its own purpose.
\n\n\n\n[00:26:56] Matthias Pfefferle: Yeah. And there’s also a concept of relays. So if you set up a new Mastodon server, and you want to have some traffic, or you want to see some posts in the global timeline, then you can subscribe to relays. And they will start federating without you following someone. So you can decide. You can decide if you want to start simple and start small, or if you want to have at least some kind of activity on your platform.
\n\n\n\n[00:27:29] Nathan Wrigley: It is quite interesting when you first sign up, because if you sign up for, let’s pick a service, let’s go for Twitter. And you supply them with a username and a password, and you go through the onboarding wizard. The first thing that you see is a full feed. There’s content that they have decided would be appropriate for you, probably based on all sorts of algorithmic ways of keeping it sticky and engaging for you.
\n\n\n\nBut your feed will immediately be full. Whereas the exact opposite is true on the Fediverse. Ignoring all the relays, let’s just imagine that you set up your own instance. You are basically in a vacuum until you start finding people. And then you interact with them and that they are sharing, it’s called a boost. They are boosting other people’s content. And in that way, then you get to see other people.
\n\n\n\nYou can then follow them and this nice organic system of growth, you can imagine it almost like a tree growing out the ground and branches start to appear and further branches and other branches. All of that starts to happen. And it really doesn’t take very long before your feed is, well, as full as you want it to be.
\n\n\n\n[00:28:29] Matthias Pfefferle: Exactly.
\n\n\n\n[00:28:30] Nathan Wrigley: And so that whole system, ultimately though, I feel is a quieter system. That feed, because you’re only following people that you wish to pay attention to. And of course, as with all things, you can decide that you no longer want to follow people, or you can decide to block people, or block whole servers and what have you.
\n\n\n\nOkay, so we’ve spent a little bit of time figuring out what ActivityPub is. Your role at Automattic is working on the ActivityPub plugin. Now am I right in saying, Matthias, this was your brainchild in the beginning? Did you fork this plugin or was this your baby right from the start?
\n\n\n\n[00:29:04] Matthias Pfefferle: That was my baby right from the start. It was not the first experiment with decentralised social networks. But the most famous in the end I think.
\n\n\n\n[00:29:15] Nathan Wrigley: It’s all worked out very well. You know, with the benefit of hindsight, oh, all of the bricks were nicely laid to make the wall. But sounds from the conversation that we had before we hit record as if much of this was by chance and it’s just worked out brilliantly. So what does it do?
\n\n\n\nObviously it’s a plugin. We install it and activate it in WordPress. What is the intention of the plugin? Now I realise that there may be bits of this that are roadmap. It may be that we only want to talk about the things which are in it in October 2023. But what broadly is the intention? What is it trying to do?
\n\n\n\n[00:29:47] Matthias Pfefferle: The first intention I had with it was to simply be part of the Fediverse. Others can follow your blog on Mastodon. So it started with a focus on publishing. Not being a full flavored social network, but simply starting with publishing. That means that users can no longer only follow your RSS feeds or Atom feeds, but also can follow your blog users on the Fediverse. And everything you publish on the blog will be federated to the different servers.
\n\n\n\n[00:30:22] Nathan Wrigley: Can I just interrupt you there? Sorry, just to be clear. You use the word federated as verb, it’s a thing which is being done. But what is being done there? So if I’m on my WordPress website and I go add new post, write a post, click publish. Normally that just publishes the post and people have to find it, you know, through Google or what have you. What’s the additional thing? What’s the federated bit in there? What is happening?
\n\n\n\n[00:30:44] Matthias Pfefferle: That’s kind of the same thing with Mastodon. If someone on Mastodon follows your blog, then he kind of subscribes to your posts. And every time you write a new post, this post will be sent to the inboxes of all your followers. And they will see your post kind of the same way they see a different Mastodon post. So on Mastodon, you could not see any difference between a WordPress blog post, or a post that was directly posted on Mastodon.
\n\n\n\n[00:31:17] Nathan Wrigley: So in effect, is it the same as if I had not used the ActivityPub protocol? I published something on my WordPress site, and then I had gone and meticulously copied and pasted, let’s say, the excerpt, the title, carried across the featured image, or what have you, and gone to the social network and posted it. In effect, are we looking at the same thing? It just automates that process of posting it onto Mastodon.
\n\n\n\n[00:31:41] Matthias Pfefferle: Not directly, because what you mentioned is cross posting. That means what we did in the early days with the WordPress social media things. And that’s copying the post. That means you have to have a profile on Twitter, on Facebook, on Mastodon, you name it. And then this profile was used to publish, to republish your content, or kind of parts of your content.
\n\n\n\nAnd the new thing is that you do not cross post anymore. It’s the natural ActivityPub way you do that. So it’s not you need a Mastodon account and then you copy all your stuff, or you publish all your stuff through that Mastodon account. It’s your blog user is the Mastodon account. Others can follow your account or the whole blog directly, without copying stuff. It’s really, the whole ActivityPub, Fediverse following experience.
\n\n\n\n[00:32:39] Nathan Wrigley: Okay. Let’s explore that a little bit, just to make sure that I’ve understood it. So the first thing to say is, so it’s not cross posting. So if I write something on WordPress, in effect you are just showing the same thing in two different places. You’re showing it on the WordPress blog, for want of a better word. But you’re also showing that on Mastodon, and it’s the same thing. It’s the same entity. So it’s not a cross post, it’s just a post. So first thing, have I got that right?
\n\n\n\n[00:33:08] Matthias Pfefferle: Technically spoken, in the end it’s kind of a copy because that’s how ActivityPub works. The ActivityPub server, the Mastodon server kind of has a cache of your profile, and has a copy of your post. But in the end, it’s more like you described it. It’s not that you have to use something on the other platform to publish it.
\n\n\n\nBut you can compare that with Mastodon. If you are on Mastodon and if you follow someone else, you see his posts in your stream. And you can see the blog posts, your homepage of WordPress, kind of like the stream you have on Mastodon. And others can subscribe to that kind of stream, and then it will be part of their Mastodon timeline. And every time you publish a post, it will be directly federated to that timeline.
\n\n\n\nAnd the thing with cross posting is that, if you post something through a Twitter profile, the whole communication on Twitter will only live on Twitter. To check what others think of your post, or what their ideas to your post are, you have to visit Twitter. The difference between that and Mastodon is that also the interaction on Mastodon or any other platform will federate.
\n\n\n\nSo that means that in the end, comments and boosts and likes will also be part of your WordPress post. So if someone on Mastodon comments your blog article, then it will also show up in the comment section of your blog.
\n\n\n\n[00:34:53] Nathan Wrigley: That really is an amazing, transformational thing, isn’t it? So again, let me be very clear. I post something on my WordPress site. Let’s imagine that’s the first place I want to do things is, you know, the interface that we love and what have you.
\n\n\n\nI post it there, it gets federated. It can now be seen, whatever that complicated process is, it can now be seen on Mastodon, let’s say. But there’s a whole bunch of other services which use the ActivityPub protocol, which we haven’t even gotten into. But there’s whole other social networks, in inverted commas, that are built on top of it, which interoperate.
\n\n\n\nThere’s one called Pixelfed, which is primarily for images but let’s not get into that. So it’s visible on Mastodon, but then if people comment on that, those comments come back, they get federated back to my WordPress site, and they would then be visible to me. Or would they be visible to everybody that visited my website? In other words, do they get consumed and added to the database as a comment?
\n\n\n\n[00:35:49] Matthias Pfefferle: Yeah. In the end we try to reuse every object that’s common in WordPress. So if you write a reply on Mastodon, in the end, it’s simply a comment on your WordPress blog.
\n\n\n\n[00:36:03] Nathan Wrigley: That’s really amazing. What if I update something? So let’s say, I don’t know, a week later in my WordPress post I spot a gigantic error. Spelling error or just factual error or something like that, and I update it. Does that then get re federated? In other words, if somebody were to stumble across that a week ago in their timeline, would they see the newer version or does the cache mean that you get the original version?
\n\n\n\n[00:36:28] Matthias Pfefferle: No, it federates also the updates. That was not always the case, but Mastodon supports that for quite some months, I think. They first implemented that you deleted the original post and repost a new one. But now they fully support updates. So if you update your blog post, the update will be federated. And the same with all other activities like delete, or even if you put it in trash, it will deleted first.
\n\n\n\n[00:37:00] Nathan Wrigley: So this may be a peculiar question, I don’t know. Is it possible to amend things in a different environment that’s not WordPress? Let’s say I’m browsing on the Mastodon interface. Can I edit things over there and they will get re federated back to my WordPress site? Or is this more of an, edit in WordPress, do all the things in WordPress, just make that your first home?
\n\n\n\n[00:37:22] Matthias Pfefferle: It depends to what you’re referring to. If you write a comment on Mastodon, then you can edit that. But you can’t edit, let’s assume you have a Mastodon account and you follow your blog. And you publish a blog post that will be also federated to your Mastodon account. Then you could not use your Mastodon account to edit your blog post, because technically spoken, it’s a different user.
\n\n\n\n[00:37:48] Nathan Wrigley: Okay. Can I bring a pre existing Mastodon user into the ActivityPub protocol for WordPress? In other words, can I use an account that I’ve already got and combine it, and then decide to, you know, go forward with WordPress? Or do I, in the process of setting up the plugin, am I creating a new account at that moment?
\n\n\n\n[00:38:11] Matthias Pfefferle: The first thing you mentioned would be cross posting. So if you register on Mastodon, you will get a Mastodon handle. That means something like mastodon.social/@nathan, something like that. And that’s currently not really portable. At least not that you use the same kind of handle on a different platform.
\n\n\n\nThere are mechanisms where you can kind of move your accounts to a different server. Then all your followers will be pointed to the new server. But technically you have a new handle and using a new server.
\n\n\n\nThat’s currently not possible with the WordPress plugin, because in the end we are not yet a fully comparable social network. So it’s still focusing on the publishing stuff. And you can’t follow others using your WordPress blog. There is no social media stream in the backend, you can consume others posts. So it does not make sense to move your accounts, at least yet.
\n\n\n\nIn the end it’s kind of, with installing the plugin, you will receive new handles. It’s not really a new account, but you have a new handle and others have to follow that new handle to subscribe to your blog posts.
\n\n\n\n[00:39:38] Nathan Wrigley: So if you’ve got a large following that you’ve worked hard to gain on Mastodon, then there’s definitely some thought to be put into this, and the way that you implement it and so on.
\n\n\n\n[00:39:48] Matthias Pfefferle: It’s totally fine to maybe use both, kind of to start with. Still cross post to your carefully crafted Mastodon account with hundreds of thousands of followers. And to start with the new identifier besides of that. Or maybe kind of what I’m currently trying to use is that I boost my blog posts. So that’s kind of the easiest way to gain a bit more traction to my blog posts.
\n\n\n\n[00:40:18] Nathan Wrigley: Got it. Yeah, thank you. I remember over the last, maybe year or so, not to put too fine a point on it. There was a large migration of people over to Mastodon when Elon Musk took on the ownership of Twitter. I think some people had various different concerns about how Twitter would work as a platform.
\n\n\n\nAnd it became a really hot topic in the mainstream press actually, over here on the BBC and various news channels, people were talking about Mastodon. And to me it was great because it was something, you know, it was kind of, oh, I was into that before it was cool, kind of thing.
\n\n\n\nBut then it seemed to die off. I don’t know if you’ve got any intuition on this. But just in the last month or two, especially in the WordPress world, it’s really gained a whole new life again because of WordPress.com. And so I wonder if you could tell me what’s happening over at WordPress.com and, trying to answer it at the same time, whether you’ve got any intuitions as to whether it has been a bit of a trough over the last few months? And, you know, whether or not Mastodon is still maintaining the interest that it once did.
\n\n\n\n[00:41:23] Matthias Pfefferle: I think the movement you mentioned was already the third. So it’s kind of a wave. It’s not a constant movement. There were a lot of different things in the last few months or years that caused a bigger movement. Between these movements, it gets stagnated.
\n\n\n\nJust recently there was another big movement when Reddit decided to monetise their API. And there was also a big movement, not to Mastodon, but to the platforms that are called Lemmy or kbin. That’s kind of the Reddit of the Fediverse.
\n\n\n\nIt’s not only that it’s only about Twitter and Mastodon and maybe Facebook. But it’s kind of a broader thing. It’s not that it’s that loud, as in the early Musk Twitter days, but I think it’s a constant movement of the time. And what I really like about the WordPress plugin, in the end, is that we discussed the ownership of data in social networks.
\n\n\n\nMastodon kind of has the same issues. There were a lot of, in the early days with the big buzz on decentralised networks. There were a lot of admins hosting their own little Mastodon instances. And over the time they had issues with money and payment, and shut down their instances.
\n\n\n\nSo in the end, also with a decentralised social network, you have to choose carefully where you want to host, or where you want to create your account. Because there’s no guarantee that this is even better as in closed networks. There are better mechanisms to move your account. But in the end you’re also depending on the work of others, and that they will keep on hosting the platform.
\n\n\n\nWith WordPress it’s kind of different because you can host your WordPress instance by your own. And even if the hosting provider decides to shut down the hosting, it’s very easy to export or to download your whole WordPress instance and upload it to another hoster.
\n\n\n\nIn the end, if the domain does not change, it doesn’t matter where you host your WordPress instance. And that’s kind of the game changer in my mind. You’re no longer dependent of other’s service in the end.
\n\n\n\n[00:43:57] Nathan Wrigley: The ability to migrate is fairly trivial. You know, you can really just move to another instance. My understanding is that, let’s say for example, that the server that I run, I decide to shut it down. Hopefully I would have the decency, for want of a better word, to inform the people who are on my server with plenty of time, so that they could go through this process.
\n\n\n\nBut I guess that wouldn’t necessarily always be the case. And probably some people have been stung. But it is possible to go into your account, you can export it, and then go to another server and kind of upload it there. There are some caveats, maybe I’m wrong about this. But my understanding is it will bring your followers with you, but for obvious reasons it won’t bring the posts and the replies that were on that previous instance as well. Is that right?
\n\n\n\n[00:44:39] Matthias Pfefferle: Yes. And it’s only working properly if you have only Mastodon followers. This is simply a Mastodon thing. It’s not part of the ActivityPub protocol by definition. So this whole moving profiles to different servers is realised really differently on different kind of protocols. So if you can avoid moving your profile.
\n\n\n\n[00:45:06] Nathan Wrigley: But there is the option there, right? It is at least something, which is nice. It’s interoperable and you can take your social graph elsewhere, if you like.
\n\n\n\nSo .com, WordPress.com probably, I don’t know maybe a month ago, maybe less, I can’t actually remember, decided that they were going to allow this on all of the WordPress.com websites. Is this the plugin that you have created? Is it that, that they’ve implemented? And if so, what has the interest been? Have many people taken WordPress.com up on this, and has it been a smooth experience?
\n\n\n\n[00:45:39] Matthias Pfefferle: Okay, starting with the plugin. Under the hood it’s the same plugin, but it’s a bit modified to work more smoothly together with the WordPress.com experience. I started the free installable plugin to fit my needs. So a lot of the settings are really geeky, and there are a lot of settings.
\n\n\n\nSo we stripped that down to better match with the product WordPress.com. But in the end, it’s technically the same in the background. It’s from the press it was impressive. I had the month of my life. It was stressy but it was the best time ever.
\n\n\n\nThe adoption is rising steadily. We have not done a lot by now to on board our users properly, and to have maybe kind of a special landing page to directly start. I want to have a federated WordPress. So with all of that, it’s a really good adoption. And if you think about that, we only had one blog post for now.
\n\n\n\nWe are fine with that. And we’re working to make it even easier and even better, and have kind of a more social network like experience in the end. But for now, it’s a nice thing because you could use it without changing your publishing behavior, or your commenting behavior. It’s simply activated, and if someone wants to use it, perfect. If not, also fine.
\n\n\n\n[00:47:17] Nathan Wrigley: Right. So it’s a fairly stripped down implementation, with less of the geekiness attached. But it worked, and the last time I looked was probably last Friday. So we’re recording this on a Thursday, so that was six days ago. And thousands, plural thousands of people had taken the opportunity to check that box and implement it.
\n\n\n\nSo I don’t know what’s happened in the last week, but presumably it’s gone up from there. And as you say, if you haven’t gone to any great lengths to promote it, just one blog post and, you know, nothing shouting at you in the UI to tell you you can do this. That’s really amazing. That must give you a, well like you said, it’s been one of the most amazing months of your life. That’s great.
\n\n\n\n[00:47:55] Matthias Pfefferle: And there’s a lot of potential.
\n\n\n\n[00:47:57] Nathan Wrigley: And I know that obviously, the whole position that you’ve been given at Automattic must give you confidence that WordPress as a whole, the .org side, as well as the .com side. There is real interest in this working with websites hosted with WordPress. This is not a flash in the pan. The fact that you’ve been taken on full time to work on this one plugin, I guess illustrates the fact that they are hoping that this is going to be the future of social networking.
\n\n\n\n[00:48:24] Matthias Pfefferle: I hope so too, yeah. But Automattic was a game changer in the end. So now that I can work full time on the plugin, it changed a lot. But simply with Automattic announcing that they would take over the plugin, and me as a developer, the press coverage was insane.
\n\n\n\nAnd in the end nothing changed really, at least from the technical perspective. So I think having Automattic, not only as a backer of the development, but also kind of a evangelist in that topic, is really game changing.
\n\n\n\n[00:49:02] Nathan Wrigley: Well let’s hope that in the future, there’ll be lots on the roadmap, lots of interesting new initiatives. Matthias, if somebody wants to reach out to you, I normally say, do you have a Twitter handle or something like that? I’m going to say something different. Do you have a Fediverse handle that you’d like to share? I mean it might be just as simple as your blog. Let us know where people can find you.
\n\n\n\n[00:49:22] Matthias Pfefferle: Yeah. My blog is German so maybe that’s not the perfect place to follow me. I’m on one of the biggest Mastodon instance, mastodon.social/@pfefferle, my last name.
\n\n\n\n[00:49:36] Nathan Wrigley: I will write everything in the show notes, but the sake of people who don’t read the show notes and just wish to have it spelled out for them, that would be mastodon.social/@ P F E F F E R L E. That will now be in the transcription as well.
\n\n\n\nSo yeah, Matthias, thank you so much for sharing all of your insights about the Fediverse, Mastodon, ActivityPub. And good luck, I hope that the future is bright.
\n\n\n\n[00:50:01] Matthias Pfefferle: Thanks a lot, and thanks for having me.
\nSo on the podcast today, we have Matthias Pfefferle.
\n\n\n\nMatthias started using WordPress in its early stages when it was still known as b2. He became passionate about blogging and the web 2.0 era. Over time he dedicated himself to making blogging relevant and developed various tools to compete with social networks, building communities professionally and working for a European hoster. Matthias ultimately joined Automattic to focus on WordPress and the ActivityPub plugin full-time.
\n\n\n\nWe start off talking about the importance of owning your own content, and how it grants us control over what gets published and when it gets deleted or amended. Matthias introduces us to Mastodon, a social network that operates on a non-algorithmic, chronological feed. This means that the content is displayed in the order it was created, breaking free from possibly addictive patterns we see in other platforms.
\n\n\n\nWe learn about the Fediverse, where users can set up their own servers and customise their own rules. Matthias explains how servers communicate with each other through following and federating, creating a truly decentralised network. He shares insights into how relays can be used to generate traffic and activity on new Mastodon servers should you find your feet a little quiet at the start?
\n\n\n\nThere’s definitely some new workflows to learn using the Fediverse and Matthias highlights the differences between Twitter and the Fediverse, with the latter starting off quiet and gradually growing as users find and interact with others.
\n\n\n\nHe introduces us to the ActivityPub plugin for WordPress, which allows users to publish their blogs on Mastodon, and federate the content to different servers. We get an explanation of how it works, what it does, and where it strays from the way you’re used to interacting with a proprietary platform.
\n\n\n\nWe discussed the various waves of migration to Mastodon and the factors that triggered them, including Reddit’s decision to monetize their API. Matthias sheds light on the challenges faced by decentralised networks, and how wordpress.com has implemented his ActivityPub plugin, albeit in a modified form, making it easier for users to migrate their accounts. The adoption of the plugin has been steadily rising, and Matthias expresses his confidence in the plugin’s potential, citing the press coverage and impact of Automattic’s takeover.
\n\n\n\nHe also provides insights on how interactions on Mastodon federate, explaining how likes, comments, boosts, updates or deletions to blog posts are reflected across platforms.
\n\n\n\nTowards the end Matthias shares his thoughts on the future of federated social networks and the potential support from existing platforms like Meta. He emphasises the profound benefits of using protocols like ActivityPub, allowing users to own their own data and have more control over their content, unlike closed platforms that can delete accounts and cause data loss.
\n\n\n\nIf you want to learn more about the Fediverse, Mastodon, ActivityPub, or just want to know how to make WordPress a first-class citizen in social networks, this podcast is for you.
\n\n\n\nIf you’re reading this, you’re likely not just any marketer. You’re the kind who’s always got a finger on the pulse of what’s going on — the latest tools, the newest lead generation best practices, and the most memorable campaigns of the year.
\n\nAccording to a survey from May 2023, approximately 20.6% of Chief Marketing Officers (CMOs) in the U.S. cited expanding into new markets, segments, or geographies as their top challenge for the next 12 months. Often, the biggest obstacle to making these important moves is having the right tools on hand.
\n\nSo, if you’re on the hunt for marketing apps that can elevate your enterprise marketing strategy from “meh” to “mind‑blowing”, you’re in the right place. We’re diving deep into the world of enterprise marketing tools that are poised to supercharge your efforts in 2023.
\n\n\n\n\n\nBefore we jump into our list, let’s get on the same page about what we mean by “enterprise marketing tools”. These are enterprise marketing software solutions designed to handle the complex, multifaceted needs of large organizations.
\n\n\nThey go beyond the basics, offering features like advanced analytics, automation, and integration capabilities that can scale with your business.
\n\n\n\n\n\n\nWhen you’re running a large WordPress site or ecommerce business, you can’t afford to mess around with tools that are just “good enough”.
\n\n\nYou need robust, reliable solutions that can handle the heavy lifting, so you can focus on what you do best, like creating amazing marketing campaigns that convert.
\n\nBut even small businesses can use and benefit from these tools. Many offer scalable solutions that can grow with you, so there’s something here for everyone.
\n\nBefore you commit to a tool, let’s talk about what you should be looking for. After all, not all marketing tools offer the same features, flexibility, or ease of use. And what works for one business might not be the best for another.
\n\n\nYou don’t want a tool that requires a Ph.D. to operate. The easier a tool is to use, the quicker your team can get up to speed and make the most out of it.
\n\n\nYour business isn’t going to stay the same size forever. So, make sure the tools you choose can grow with you. Scalability is a must, especially for enterprises.
\n\n\nWith all the technology, your firm likely utilizes, you need to have tools that play well with others. Look for solutions that can easily integrate with your existing tech stack. This will make your life a lot easier in the long run.
\n\n\nData is king, so look for tools that offer robust analytics features. This will help you measure the success of your campaigns and make data‑driven decisions.
\n\n\nEvery business is unique, and your tools should be able to accommodate that fact. Customization features can help you tailor the tool to meet your specific needs.
\n\nNow, let’s move on to the best part — the top ten enterprise marketing software tools that can help you ace your marketing game in 2023.
\n\n\n\n\n\n\nAkismet is a must for enterprise-level marketers as it’s your ultimate line of defense against spam. Developed by the same team behind WordPress.com, Akismet uses cutting-edge AI technology to filter out comment, form, and text spam with an unparalleled 99.99% accuracy.
\n\n\nIt’s truly a proven solution that has been trusted by millions of websites globally and can be used by businesses of all sizes.
\n\nAkismet was designed with user‑friendliness in mind. Its seamless integration with WordPress makes it incredibly easy to set up and manage. There’s no need for coding experience or complicated server management — it just works.
\n\nAkismet offers a range of pricing options tailored to different needs:
\n\n\nOracle Eloqua serves as a robust enterprise marketing automation software, specializing in personalized B2B marketing solutions. As a key component of the Oracle Marketing suite, the platform provides an all-encompassing, unified marketing solution that allows cross-channel programs to flourish.
\n\n\nIt focuses on enhancing lead generation, fine‑tuning communications with customers and prospects, and automating marketing tasks through insights derived from real‑time data.
\n\nOracle Eloqua is engineered to empower marketers, allowing them to tap into their creativity and intuition to orchestrate compelling B2B campaigns. Despite its sophisticated feature set, the platform maintains a user‑friendly interface.
\n\nOracle Eloqua does not publicly disclose its pricing structure. However, it’s generally customized to meet the specific needs of an enterprise. Reviews indicate that the basic package for Oracle Marketing Cloud starts at a range of $2,000 to $4,000 per month, with additional costs incurred for add‑ons and higher‑tier plans.
\n\n\n\n\n\n\nMonday.com aims to be the hub for all your work activities, processes, tools, and files. The platform is ideal for a modern work environment, catering to various sectors including creative and design, software development, marketing, and project management.
\n\nIt focuses on streamlining work for optimal productivity and fostering organization‑wide collaboration.
\n\nMonday.com is designed for user‑friendliness, making installation, setup, and restoration a breeze. There’s no need for coding skills or intricate server management. The platform is built to be intuitive and straightforward.
\n\nMonday.com offers various pricing options to cater to different organizational needs. Here’s a breakdown:
\n\n\nMediaMath is a specialized platform for programmatic advertising that allows brands and agencies to manage their marketing campaigns with agility. The platform really excels in delivering effective and efficient omnichannel campaigns, featuring solutions like a Demand Side Platform (DSP) and Connected TV (CTV) advertising.
\n\n\nMediaMath also makes it easier to establish a one‑to‑one relationship with customers across all devices through its audience targeting capabilities.
\n\n\nMediaMath is user‑friendly, offering an intuitive experience for running advertising campaigns across multiple channels. There’s no need for a complicated setup process.
\n\nUnfortunately, MediaMath does not publicly disclose its pricing details. For more specific pricing information, it’s necessary to contact their sales team.
\n\n\n\n\n\n\nKlaviyo is more than just an email marketing tool. It’s a comprehensive platform designed to deliver hyper-personalized experiences through deeper insights. Integrated seamlessly with ecommerce platforms, Klaviyo allows businesses to send targeted emails, SMS, and even push notifications.
\n\n\nThe platform aims to consolidate your tech stack, enhance efficiency, and elevate customer lifetime value.
\n\n\nKlaviyo is designed with user‑friendliness in mind, offering a streamlined customer experience. Whether it’s capturing leads or executing campaigns, navigating the platform is intuitive and straightforward.
\n\nKlaviyo offers both free and premium plans.
\n\n\n\nMailchimp’s expanded its focus beyond email marketing campaigns and is now a comprehensive platform designed to streamline your marketing automation efforts. From A/B testing and customer journey building to content creation, Mailchimp offers a full suite of features that can help you automate campaigns and make data‑driven decisions.
\n\n\nMailchimp is designed to be user‑friendly. Its intuitive interface makes setting up campaigns, managing your audience, and analyzing results a breeze. Plus, they offer 24/7 service and support, so you’re never left in the dark.
\n\nMailchimp offers a free plan with limited features plus various premium plans:
\n\n\nSimpli.fi is a leading advertising success platform that focuses on maximizing relevance and results. It offers a range of media buying and workflow solutions designed to capture your audience and power your best work.
\n\n\nFrom Demand‑Side Platform (DSP) capabilities to Connected TV (CTV) advertising, Simpli.fi aims to deliver highly‑competitive pricing and audience‑targeted solutions.
\n\nSimpli.fi is designed to be user‑friendly, offering an all‑in‑one platform that streamlines every step in your workflow. Whether you’re planning a campaign or analyzing its performance, Simpli.fi makes the process seamless.
\n\nAs we already mentioned, Simpli.fi does not publicly disclose its pricing. For detailed pricing information, you’ll need to get in touch with their sales team.
\n\n\n\n\n\nMarketo Engage, a component of Adobe’s expansive suite, is an enterprise marketing automation tool catering to both B2B and B2C sectors. It’s engineered to bridge the gap between sales and marketing teams.
\n\n\n\nThe platform is of the all-in-one variety, offering everything from lead management and email marketing to multitouch attribution.
\n\n\nMarketo Engage is user‑friendly but comes with a bit of a learning curve due to its extensive feature set. However, once you get the hang of it, it becomes an invaluable enterprise marketing automation solution.
\n\nPricing for Marketo Engage is not publicly disclosed. However, it’s worth noting that the platform offers different plans that scale based on the number of users and the complexity of features. For a more detailed pricing breakdown, you’ll need to contact their sales team directly.
\n\n\n\n\n\n\nInvoca serves as a powerhouse in conversation intelligence, harnessing the prowess of AI to unearth fresh data that can be a game-changer for your business. The platform is designed to help you snag more customers without breaking the bank, offering keen insights into your phone-based customer interactions.
\n\n\nWhether you’re on a mission to ramp up conversions, elevate your agents’ performance, or convert more callers into loyal customers, Invoca is your one‑stop‑shop.
\n\nWhether you’re in the planning phase of a campaign or knee‑deep in performance analytics, Invoca aims to make your life easier. However, getting started will require a time commitment.
\n\nWhen it comes to pricing, Invoca keeps its cards close to its chest. For specifics, you’ll need to have a chat with their sales team.
\n\n\n\n\n\n\n\nStackAdapt is a titan in the realm of programmatic advertising, engineered to help you craft campaigns that catch the eye and engage the mind. The platform is built on planning, execution, and analysis.
\n\n\nWhether you’re an agency hungry for growth or a brand keen on making meaningful connections with your audience, StackAdapt has a toolbox chock‑full of solutions tailored just for you.
\n\nStackAdapt is generally easy to use, but does have a somewhat confusing dashboard. Once you’re familiar with it, however, the workflow becomes intuitive.
\n\nStackAdapt doesn’t offer its pricing upfront, so you’ll need to reach out to their sales team to get a quote for your situation.
\n\nWhen looking for the right enterprise marketing automation tools, there are several factors to consider. Let’s take a look at a few.
\n\nYou have to know what you’re aiming for. What are your specific goals and key performance indicators (KPIs) for your digital marketing programs? Whether it’s boosting lead generation, improving customer engagement, or enhancing ROI, having clear objectives will help you narrow down your options.
\n\n\n\nUnderstanding your target audience is another critical factor. Are you targeting B2B or B2C? What are their pain points, and how do they interact with your brand? Knowing your audience will help you select tools that can effectively engage and convert them.
\n\n\nLet’s be real — budget is always a factor. You need to know how much you can afford to spend on these tools without breaking the bank. Make sure to balance quality and cost‑effectiveness.
\n\n\n\n\n\n\nThings don’t always go as planned. When you hit a snag, you’ll want a responsive customer support team to help you out. Check reviews or ask for references to gauge the quality of a tool’s customer support.
\n\n\nA tool could have all the bells and whistles, but if it’s a nightmare to use, then what’s the point? A good user interface and experience can make all the difference. Look for tools that are intuitive and don’t have a steep learning curve.
\n\nMany tools offer free trials or demos. Take advantage of these to get a feel for the tool’s interface and capabilities. It’s like test‑driving a car. You’ll get to know if it’s the right fit before making a commitment.
\n\nLast but definitely not least, consider the tool’s security features. This is especially important if you’re handling sensitive customer data. Make sure the tool is compliant with regulations like GDPR or HIPAA, depending on your industry.
\n\nThe marketing tools you select will largely depend on your specific business needs, goals, and the scale at which you operate. Start by identifying the gaps in your current marketing strategy and look for tools that can fill them. Also, consider factors like scalability, integration capabilities, and user experience.
\n\nAbsolutely! Many marketing tools offer customizable plans and features. For instance, Akismet offers enterprise‑level plans that can be tailored to meet your specific needs.
\n\n\n\n\n\nLook no further than Akismet for enterprise-level spam protection. It’s a leading tool in the spam protection arena and offers robust features to keep your site free from unwanted spam.
\n\n\nAkismet offers a range of benefits for enterprise companies. It protects your website from spam and saves you time by automatically filtering out malicious content. This allows you to focus on what really matters — e.g. growing your business. Akismet’s enterprise plans also offer dedicated support to meet the unique needs of large‑scale operations.
\n\nAkismet is trusted by a wide range of companies, from small businesses to large enterprises. It’s a versatile tool that can adapt to the unique needs of your business, making it a valuable addition to your marketing toolbox.
\n\n\n\n\n\nAkismet is used by over 100 million sites. And it’s not just small businesses that trust Akismet. Big names like Microsoft, ConvertKit, and Bluehost also rely on Akismet for their spam protection needs.
\n\nAkismet isn’t just a spam protection tool. It’s a must for enterprises looking to increase their lead and contact form conversion rates. By automating spam filtering, Akismet lets you focus on what truly matters — engaging with genuine leads and customers.
\n\nSo, if you’re in the market for a tool that offers robust spam protection while also giving your conversion rates a healthy boost, Akismet is the one for you.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Nov 2023 14:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Rob Pugh\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"HeroPress: Nine Years Of HeroPress, A Retrospective\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=6003\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:152:\"https://heropress.com/essays/nine-years-of-heropress-a-retrospective/#utm_source=rss&utm_medium=rss&utm_campaign=nine-years-of-heropress-a-retrospective\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:232537:\"This week is the anniversary of when I woke up one morning to an email from the owner of the company I worked for (Dave Rosen, XWP) saying he was taking me off the XWP team because he wanted me to do something special for WordPress. I asked him what, and he said “That’s your journey to discover.”
\n\n\n\nAnd what a journey it’s been!
\n\n\n\nI never would have imagined that this kid who grew up in a house without electricity would be part of a project that enabled him to travel through 9 countries, building friendships all over the world and in dozens of cultures. Friendships that have opened my eyes to new ideas, communication models, foods, and so much more. All while elevating the invaluable stories of others and bringing inspiration to those who need it no matter where they are.
\n\n\n\n\n\n\n\n\nHeroPress for me is always a place of empathy and dignity. I return to it often as spending time on it is always rewarding, filled with stories of us- the people of WordPress.
\nAditya Kane
Look with me at what we’ve done so far and what the next phase might have in store.
\n\n\n\nFor many years, HeroPress was a site of community-contributed essays, and HeroPress.com continues to be that today. Since Rarst’s first essay we’ve published just over 260 essays in 28 languages. Broken down, that’s 125 essays by men, 128 by women, and 3 by non-binary folk, with contributors representing 59 different countries.
\n\n\n\n\n\n\n#map_wrapper {\n height: 600px;\n}\n\n#map_canvas {\n width: 100%;\n height: 100%;\n}\n\n.info_content .contributor {\n min-width: 300px;\n clear: left;\n}\n.info_content img {\n margin: 6px 6px 6px 0;\n float: left;\n}\n.info_content h4 {\n margin: 0;\n padding: 0;\n clear: none;\n}\n.info_content h5 {\n text-transform: none;\n letter-spacing: 0;\n margin: 0 0 4px 0;\n clear: none;\n}\n.info_content p {\n margin: 0;\n clear: none;\n}\n \nThe Fuel Of Everything That’s Great In The World – Rotițele care fac lumea să se miște
\' +\n\'New life thanks to WordPress – Una nueva vida gracias a WordPress
\' +\n\'About how WordPress saved my life. – Sobre como WordPress me salvo la vida
\' +\n\'Exploring the Essence of Community – Explorando la esencia de la comunidad
\' +\n\'Becoming A Better Me with Core Contribution – কোর কন্ট্রিবিউশন এবং জীবনের নতুন অধ্যায়
\' +\n\'Finding a second chance in life through WordPress – വേർഡ്പ്രസ്സിലൂടെ ജീവിതവിജയം
\' +\n\'The pleasure of being a part of a community – Щастя бути частиною спільноти
\' +\n\'Connection Makes Credibility, Credibility Makes Opportunity – 連結產生信賴,信賴創造機會
\' +\n\'There is No Shortcut to Success – सफलता का कोई शॉर्टकट नहीं है
\' +\n\'Living Well and Enabling Success For Others Through WordPress
\' +\n\'Tales Of A Serial Contributor – Histórias de um colaborador em série
\' +\n\'Being a freelancer can be the most stable thing in Taco land
\' +\n\'Never give up on your dreams – Moet nooit jou drome laat vaar nie
\' +\n\'WordPress – The Source Of My Satisfaction And Joy – વર્ડપ્રેસ – સંતોષ અને આનંદ નો સાધન
\' +\n\'Life Stacks Up – From A Small Town Boy To A Geek Entrepreneur
\' +\n\'My Journey from being a Dyslexic kid to becoming A Co-organiser For WordCamp Mumbai
\' +\n\'A Journey toward Freedom with WordPress – वर्डप्रेससंगै स्वतन्त्रता तर्फको यात्रामा
\' +\n\'A Life Changing Journey With WordPress – जीवन में मिले रंग वर्डप्रेस के संग
\' +\n\'How To Become A Freelancer – A Few Things I Learned Before I Gave Up
\' +\n\'How the WordPress community contributes to human development
\' +\n\'How the WordPress community contributes to human development
\' +\n\'Second Chances: How A Trip Back Into The WordPress Community Saved My Life
\' +\n\'How the WordPress community contributes to human development
\' +\n\'Building A WordPress Business In Iran – ساختن یک زندگی وردپرسی در ایران
\' +\n\'How The WordPress Community Helped Me Face My Fears And Do It Anyway
\' +\n\'Is WordPress Good for Indian Women? – ભારતીય મહિલાઓ માટે વર્ડપ્રેસ સારું છે?
\' +\n\'My “Hero’s Journey” Through the Dark Underworld of WordPress Hosting
\' +\n\'Building Stability With WordPress – WordPress এবং স্থিতিশীলতা, বাংলা তে পড়ুন
\' +\n\'Sometimes bad things that happen to you are good things in disguise
\' +\n\'The Year I Got Cancer Was The Year My WordPress Business Took Off
\' +\n\'My journey to WordPress taught me that my talents are best used elsewhere.
\' +\n\'16 Little Things That Grew Into Big Things (My Life in a Bunch of Words)
\' +\n\'How I found myself in WordPress – Как я нашел себя в WordPress
\' +\n\'How I tried, applied, got involved. Realizing one of my childhood dreams.
\' +\n\'How WordPress enabled me to take care of my baby without compromising on my career goals
\' +\n\'The London Eye is a giant Ferris wheel situated on the banks of the River Thames. The entire structure is 135 metres (443 ft) tall and the wheel has a diameter of 120 metres (394 ft).
\' + \'The Palace of Westminster is the meeting place of the House of Commons and the House of Lords, the two houses of the Parliament of the United Kingdom. Commonly known as the Houses of Parliament after its tenants.
\' +\n \'\n\n\n\n\nHeroPress has bestowed upon us the most wondrous knowledge of WordPress people from everywhere and anywhere. It’s an absolute treat to read all the stories, perhaps most especially from those less known than others.
\nBarbara Saul
Our Family Of Contributors
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nReading someone’s essay motivates me to venture beyond my comfort zone.
\nTremi Dkhar
2020 saw the transition from I to we. The nudge was there to act on some ideas we’d had over the years. Cate was transitioning into the work force, Liam and Tara were ready to step away from Hallway Chats, and we had to pick a direction. Do we keep things separate and find a connecting point, or do we pull them all into HeroPress itself?
\n\n\n\nAll things feeling fairly equal, we picked Option A: big, but scalable.
\n\n\n\nWe created a network of individual entities that could be nurtured, shelved, sold, or closed down at any point. This resulted in a collection of sites — HeroPress.com, WPPodcasts.com, PressItWP.com, WPPhotos.Info, HallwayChats.com, and WP-Wallpaper.com — being held together through the HeroPress Network hub.
\n\n\n\nHowever, after 3 years of giving this a try, we’re not sure if this is really the future for HeroPress. The Network is fine, but limiting. It’s time to reevaluate where we want to channel our energy as we look ahead to the next phase of HeroPress.
\n\n\n\n\n\n\n\n\nHeroPress has…
\n\n\n\nEnabled me to see the stories that create WordPress. It’s let me discover the people who genuinely power this project, not just the code and pixels. Because open source is people source.
\nTammie Lister
\n\n\n\n\nWhenever I’m down, I find visiting HeroPress and being connected to the many and real ways that WordPress’ stone in the pond of the world leaves ripples, I’m inspired and excited.
\nMatt Mullenweg
Nine years is a long time for a project like this to flourish, and flourish it has. As with any living thing it needs to be tended to and some times that means cutting a little back to make room for new growth.
\n\n\n\nA plan is underway to trim some things out and merge the rest into HeroPress.com. We’re looking at some rebranding and a new purpose statement. The goal has always been to elevate others, but have we really stated that as clearly as we could?
\n\n\n\nWhat ever the future holds, HeroPress will be here, at least for now. And we hope you’ll be alongside us as we head for 10 years of inspiring one another.
\n\n\n\n\n\n\n\n\nThe stories from HeroPress have motivated me and encouraged me to come out of my shell and chase my dreams. Several years back when I was really struggling with my career, reading inspiring stories from people all over the world finding success through WordPress rekindled my hopes and dreams – literally leading me to where I am today. I am eternally thankful for HeroPress!
\nHari Shanker
Many thanks to Tremi, Hari, Matt, Barbara, and Tammie for their words about HeroPress.
\n\n\n\nThe banner at the top is a CC0 licensed photo by Javier Casares from the WordPress Photo Directory.
\nThe post Nine Years Of HeroPress, A Retrospective appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Nov 2023 08:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Topher DeRosia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"Matt: New Yorker on Coding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=105621\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://ma.tt/2023/11/new-yorker-on-coding/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:318:\"I loved this essay from James Somers on coding in the age of AI, A Coder Considers the Waning Days of the Craft. Hat tip: Majd Taby.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Nov 2023 04:37:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: WordCamp Asia Extends Sponsor Application Deadline\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151267\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wptavern.com/wordcamp-asia-extends-sponsor-application-deadline\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1763:\"The WordCamp Asia organizing team has extended its call for sponsors until Thursday, November 30, 2023.
\n\n\n\nIn an update on the official website, organizers explained that they received feedback from multiple potential sponsors regarding why they had been unable to apply before the original deadline.
\n\n\n\nSome of the reasons included the following:
\n\n\n\nWordCamp Asia’s organizers decided to extend the deadline to allow potential sponsors the opportunity to apply.
\n\n\n\nAs one of the three flagship WordCamps, WordCamp Asia is one of the largest gatherings organized by the WordPress community. Its first event in 2023 attracted 1,299 attendees, and it’s expected to exceed that number for 2024.
\n\n\n\nA full list of sponsorship options is available from the sponsorship packages page, many of which are already sold out. Potential sponsors can apply for a sponsorship package using the form at the bottom of that page.
\n\n\n\nSponsors needing more information about travel visas can review the updated visa information page, or reach out directly to the team at asia-sponsors@wordcamp.org with any additional questions.
\n\n\n\nWordCamp Asia 2024 takes place from March 7-9, 2024 at the Taipei International Convention Center in Taipei, Taiwan.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 22:53:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Jonathan Bossenger\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: Brainstorm Force Invests in LatePoint Bookings and Appointment Scheduling Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151318\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"https://wptavern.com/brainstorm-force-invests-in-latepoint-bookings-and-appointment-scheduling-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3240:\"Brainstorm Force, makers of the popular Astra theme, has invested in LatePoint, a commercial booking and appointment scheduling plugin for WordPress. LatePoint is used on 21,000 websites to enable bookings for small businesses, such as salons, therapists, doctors, spas, and fitness studios. It also supports a growing library of add-ons for further customizing the booking experience.
\n\n\n\n“This is a strategic investment, primarily made to begin integrating LatePoint into our products and offer it to our customers,” Brainstorm Force CEO Sujay Pawar said.
\n\n\n\n“Thousands of businesses build their websites with our Astra theme and Starter Templates every day. Many of these businesses could benefit if they were able to get bookings for their services from the websites they built. So, this investment allows us to offer a deeply integrated booking and appointment solution to these customers.”
\n\n\n\nZipWP, the AI WordPress website builder product the company recently launched, will be utilizing LatePoint in the websites that are generated with appointment booking and scheduling features. Brainstorm Force also plans to integrate LatePoint features into its Spectra page builder, which is based on Gutenberg and has more than 600,000 active installs. Spectra will be updated to include blocks for bookings and appointment scheduling.
\n\n\n\nThe company is integrating LatePoint across its entire product suite, including adding it to SureCart, their e-commerce plugin, to enable small businesses to accept subscription payments. Brainstorm Force will be including it with its SureTriggers automation platform to connect LatePoint to other WordPress apps, plugins, and services.
\n\n\n\n“We realized that the service commerce space within WordPress was somewhat underserved,” Pawar said.
\n\n\n\n“Platforms like Squarespace offer Acuity Scheduling and Wix provides Wix Bookings. SaaS solutions like Calendly often come with very limited features and substantially high monthly recurring costs.
\n\n\n\n“Within the WordPress ecosystem, there are a few options, such as WooCommerce Bookings, Amelia, Bookly, etc. We meticulously evaluated all of them.
\n\n\n\n“What impressed us most about LatePoint was its exceptional code quality, modern design flexibility, and robustness.”
\n\n\n\nPawar said the investment is in the six-figures but the exact amount will not be disclosed due to a confidentiality clause.
\n\n\n\n“The idea behind the investment is to initiate this partnership and possibly acquire LatePoint in the future,” Pawar said.
\n\n\n\nBrainstorm Force currently offers more than 70 products that power 7+ million websites. This new investment is aimed at capturing small business customers with a payment and booking solutions fully integrated with the company’s starter templates and other products.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 22:39:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:105:\"Do The Woo Community: Keeping Your Site Secure for the Holidays and Beyond with Rob Cairns and Dan Knauss\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78136\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://dothewoo.io/keep-wordpress-site-secure-for-the-holidays-and-beyond/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:475:\"Rob and Dan discuss the importance of website security, hosting, plugins, backups and two-factor authentication in website security during the holiday season.
\n>> The post Keeping Your Site Secure for the Holidays and Beyond with Rob Cairns and Dan Knauss appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 09:58:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: ElmaStudio Releases Moog: A Free Block Theme for Blogs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151291\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/elmastudio-releases-moog-a-free-block-theme-for-blogs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3554:\"Moog is one of the latest free block themes to be released on WordPress.org. It features a minimal and bold layout with a responsive, masonry style grid on the homepage. Moog is well suited to blogs or even small magazine websites, with options to radically change the style with the click of a button.
\n\n\n\n\n\n\n\n\n\n\n\nMoog’s designers went wild with style variations. The theme packages 25 distinct variations, an exceptionally large number, which quickly transform the site’s design into various moods – everything from a classic style to dark mode to bold colors anchored in different font combinations. Below is a screenshot of the “Enigmatic” style variation and the 404 template, which users can further customize with their own images.
\n\n\n\n\n\n\n\n\n\n\n\nMoog includes seven custom block patterns for creating the two-column gallery, footer, header, masonry column for posts, and patterns for about, team info, and contact pages.
\n\n\n\nUsers can add their own logos (in the header and footer), social media menu, and a newsletter signup. The demo users the MailerLite plugin for the newsletter and WP Forms for the sample contact form on the Contact page.
\n\n\n\nThe single post template is particularly elegant, with the featured image, author avatar, and content centered on the page, creating a distraction-free reading experience.
\n\n\n\n\n\n\n\n\n\n\n\nMoog was created by the team at ElmaStudio, a boutique theme shop that was among the first to create commercial block themes. ElmaStudio released its first block theme, Aino, in 2021 and four commercial block themes during 2022, including one WooCommerce theme. The company has been creating WordPress themes since 2011 and brings a wealth of experience along with meticulous, thoughtful design decisions to the new world of block themes.
\n\n\n\nCo-founder Ellen Bauer created a video with a quick overview of the new Moog theme. She demonstrates how to customize page templates and shows how to add an SVG logo that will automatically adjust with the style variations. The company is not just creating block themes but is also educating users on how to take advantage of all the customization options, as template editing is a capability that was previously out of reach for most users in the classic themes era.
\n\n\n\n \n\n\n\nCheck out the live demo on the ElmaStudio website to see the theme in action, or take it for a test drive using WordPress Playground. Moog is available for free from WordPress.org.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 23:15:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"Matt: Predictive Thermometer\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=105339\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"https://ma.tt/2023/11/predictive-thermometer/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:391:\"There’s a great review of the Combustion Predictive Thermometer in Wired today. If you do any sort of cooking or grilling regularly, this tool from my good friend Chris Young is really essential.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 19:12:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"WordPress.org blog: Introducing Twenty Twenty-Four\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16394\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://wordpress.org/news/2023/11/introducing-twenty-twenty-four/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6194:\"When it comes to designing a website, one size doesn’t fit all. We understand that every WordPress user has unique needs and goals, whether you’re an aspiring entrepreneur, a passionate photographer, a prolific writer, or a bit of them all. That’s why we are thrilled to introduce Twenty Twenty-Four, the most versatile default theme yet—bundled with WordPress 6.4 and ready to make it uniquely yours.
\n\n\n\n\n\n\n\nUnlike past default themes, Twenty Twenty-Four breaks away from the tradition of focusing on a specific topic or style. Instead, this theme has been thoughtfully crafted to cater to any type of website, regardless of its focus. The theme explores three different use cases: one designed for entrepreneurs and small businesses, another for photographers and artists, and a third tailored for writers and bloggers. Thanks to its multi-faceted nature and adaptability, Twenty Twenty-Four emerges as the perfect fit for any of your projects.
\n\n\n\nAs you dive into its templates and patterns, you will notice how the new Site Editor functionality opens up different pathways for building your site seamlessly.
\n\n\n\nWhether you’re looking to craft an About page, showcase your work, handle RSVPs, or design captivating landing pages, Twenty Twenty-Four has got you covered. Choose from an extensive collection of over 35 beautiful patterns to customize and suit your needs.
\n\n\n\nFor the first time, this theme features full-page patterns for templates like homepage, archive, search, single pages, and posts. Some are exclusively available during the template-switching and creation process, ensuring you have the right options when you need them.
\n\n\n\n\n\n\n\nMoreover, you can take advantage of a variety of patterns for page sections, such as FAQs, testimonials, or pricing, to meet your site’s most specific requirements.
\n\n\n\nWith this diverse pattern library, Twenty Twenty-Four offers a flexible canvas to quickly assemble pages without having to start from scratch—saving you time and energy in the creation process. Just let your creativity flow and explore the possibilities!
\n\n\n\n\n\n\n\nTwenty Twenty-Four ushers in a new era of block themes by bringing together the latest WordPress site editing capabilities. Discover newer design tools such as background image support in Group blocks and vertical text, providing an intuitive and efficient way to create compelling, interactive content.
\n\n\n\nFind image placeholders with predefined aspect ratio settings within patterns, allowing you to drop images that perfectly fill the space. To go one step further, make your visuals interactive by enabling lightboxes. Ideal for showcasing galleries or portfolio images, this feature allows your visitors to expand and engage with them in full-screen mode. Activate it globally for all images throughout your site or for specific ones.
\n\n\n\nFor a smoother browsing experience on your site, you can disable the “Force page reload” setting in the Query Loop block. This allows the necessary content to be loaded dynamically when switching between different pages without needing a full-page refresh.
\n\n\n\nTwenty Twenty-Four goes beyond versatility with a beautiful aesthetic inspired by contemporary design trends, giving your website a sleek and modern look. Key design elements include:
\n\n\n\nAlong with its design, Twenty Twenty-Four has been meticulously optimized for performance. This ensures that your website not only looks great but also delivers a fast and efficient user experience.
\n\n\n\n \n\n\n\nMore information can be found in the following links:
\n\n\n\nThe Twenty Twenty-Four theme was designed by Beatriz Fialho and made possible thanks to the passion and tireless work of more than 120 contributors.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 18:29:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Maggie Cabrera\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"WordPress.org blog: WP Briefing: Episode 66: Advocating Open Source Solutions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16357\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wordpress.org/news/2023/11/episode-66-advocating-open-source-solutions/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11355:\"WordPress Executive Director, Josepha Haden Chomphosy, speaks to the strategic approach to integrating open source solutions within your company and offers insight into initiating open source advocacy conversations. Tune in for a session that could redefine your company’s technological approach.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@WordPress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, we’re talking about something I used to have a lot of experience with in my career before WordPress. I worked at a marketing agency. I wasn’t a developer. I was in data and strategy sorts of things. But part of the work heading into every project was an evaluation of what software was best. There were always a variety being considered, but WordPress was frequently one of them.
\n\n\n\nNow, I don’t know if any of you have had that moment where you’re having to talk open source with a CTO or a CEO, but it can be nerve-wracking, to say the least. And it makes sense, right? Open source has a PR problem, especially when you’re speaking to leadership inside a business. And it doesn’t really matter the size, right?
\n\n\n\nYou’re advocating for something that requires a completely different mental model. It doesn’t fit into accepted concepts of what makes a business thrive or what makes a bet a sure thing. There were three, maybe four, concerns that came up every time I had this conversation. So, I’m going to share those concerns with you and a few possible counterpoints to get you started.
\n\n\n\n[00:01:48] Josepha: First and always is the concern around security. I believe that this particular mismatch is rooted in an idea that controlled equals secure, which isn’t always the case. So the talking point is this. Since open source has a transparent development process, it is often more secure than proprietary software, contrary to what you might hear.
\n\n\n\nThat transparency allows vulnerabilities to be identified by independent researchers and community members and then patched quickly because you aren’t limited by who or what you know personally.
\n\n\n\nAnd if you’re not having a conversation where you’re having to defend the security in open source and you just want to bring it up yourself, here is a conversation opener for that. Security is a top concern for all of us. Surprisingly, open source solutions often have stronger security measures due to the collaborative nature of their development. It’s a proactive approach to minimizing risks.
\n\n\n\n[00:02:43] Josepha: A second thing that frequently came up was questions around innovation and future proofing of open source products. I think this mismatch is fully rooted in the Cathedral and the Bazaar methods of advancement. So the talking point for that one is this. Embracing open source fosters innovation. We can tap into the latest technologies and stay ahead of industry trends that way. It is specifically because we have a diverse set of viewpoints that we can make sure to quickly account for future risks, along with taking advantage of future opportunities. And by our organization being more active, we can potentially get exactly the solutions we need for our clients long term.
\n\n\n\nAnd the conversation opener for this, if you are the one bringing up the topic, is I’ve been thinking about our long-term goals and how to keep our technology stack relevant. Open source not only keeps us current but also positions us as innovators in our field.
\n\n\n\n[00:03:40] Josepha: And finally, the thing that seems to make or break the decision is the concept of independence. Part of any good business decision, especially around software, is determining upfront costs to getting started, long-term effectiveness of the chosen solution, and long-term mobility should circumstances change. Open source can address these from multiple vantage points.
\n\n\n\nSo here’s a good talking point for that one. Open source liberates us from vendor lock-in. We’re not tied to a single vendor’s roadmap or pricing changes, providing us with more options that suit our needs our clients’ needs. Also, given how ubiquitous WordPress is in particular, there will always be a disaster recovery option should a senior developer leave.
\n\n\n\nAnd beyond all of that, clients can own all of the content, audience attention, and clientele that we have all worked so hard to help them earn. And again, if you’re not defending things and instead choosing to bring them up as somebody who is trying to affect change in your own organization, here is a good place to start for that.
\n\n\n\nConsidering the dynamic nature of our industry, having the freedom to choose solutions independent of a specific vendor makes sure that we are always in control of our destiny.
\n\n\n\n[00:04:59] Josepha: So, those are the three most frequent things I encountered when I was having conversations about which software to choose and what software was the best choice long term for both our organization and our client’s organizations.
\n\n\n\nIf you have been in the midst of this type of conversation and have been longing for some counterpoints, I hope this helps. But if you have been feeling in your heart of hearts that your company or organization would be better off using open source software, and of course, in my context, particularly WordPress as that software, but you’ve been worried about bringing it up, I hope this gives you the courage to get out there and be an agent of change in your organization. You can do it, and I know you can.
\n\n\n\n[00:05:44] (Music interlude)
\n\n\n\n[00:05:51] Josepha: All right, my friends, that brings us now to our small list of big things.
\n\n\n\n[00:05:57] Josepha: First on the list, big, big thing. We launched WordPress 6.4 on November 7th, about a week ago. Be sure to download and check out the latest update on this monumental release. And while you’re doing it. Be sure to check out the new default theme that came out with it. It has a lot of patterns in it. I know I’ve talked about it quite a bit over the course of the year, but it’s really beautiful, and I think that it’s worth a good, strong highlight. So WordPress 6.4, you can get it on WordPress.org/download or inside your own host, probably.
\n\n\n\n[00:06:29] Josepha: The second thing that we have is that the training team recently published several new Learn resources to support meetup organizers. So we’ve got over there some lesson plans, tutorials, online workshops. And there are also new materials that help you figure out how to accomplish your goals as a contributor to the WordPress project.
\n\n\n\n[00:06:49] Josepha: And we also have a recently published new diverse speaker training page. It provides incredible resources for new and experienced contributors to bring more diverse speaker lineups and inclusive, diverse WordPress events for official WordPress meetups and WordCamps.
\n\n\n\n[00:07:06] Josepha: And the fourth thing on our small list of big things today is that I would love to get a few voice recordings from you all, from folks who are listening to the WordPress Briefing, or folks that you know, to learn more about how WordPress has impacted you.
\n\n\n\nOne of the things that I miss the most from my days as a WordCamp organizer is that annually, I got to see people who had shown up, once at a meetup, you know, to learn what WordPress was, and then came back year after year to our WordCamp with these new goals and new successes and I got to watch their businesses change over time. And so if you have a story like that where WordPress impacted what you are doing or what people that you know have done, record something and send it to wpbriefing@WordPress.org.
\n\n\n\nSo that, my friends, is your small list of big things.
\n\n\n\n[00:08:04] Josepha: Don’t forget to follow us on your favorite podcasting app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there is a new episode. If you liked what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard, you can share those with me at wpbriefing@WordPress.org. I’m your host, Josepha Haden Chomphosy. Thanks for tuning in today for the WordPress Briefing, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:08:31] (Music outro)
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:134:\"Gutenberg Times: Twenty-Twenty-Four, WordPress 6.4, Command Palette Tools, New block themes and documentation – Weekend Edition #273\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=26082\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:137:\"https://gutenbergtimes.com/twenty-twenty-four-wordpress-6-4-comment-palette-tools-new-block-themes-and-documentation-weekend-edition-273/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:26857:\"Howdy,
\n\n\n\nOh wow, catching up on 4 weeks of Gutenberg and WordPress news is an almost impossible task, especially with a major WordPress release happening in between. This edition includes mostly release information and developer notes. Furthermore, I am excited about the new themes that arrived at the Theme directory, plugins and documentation.
\n\n\n\nI hope you are well, and getting ready for the Holidays and the new year.
\n\n\n\nYours, 💕
Birgit
Table of Contents
\n\n\n\n\nNamed after the iconic jazz artist Shirley Horn, released on November 7, 2023, with a quick point release on November 8, 2023, to fix a bug with cURL/Request (WPTavern has the skinny for you)
\n\n\n\nThe release is the culmination of immense effort and passion from over 600 contributors across at least 56 countries, including 170 first-time contributors! Although the Font Library and two new blocks were punted to 6.5, and despite the short release circle, it absolutely features rich. Release lead, Josepha Haden Chomphosy, shared more details in the release post. WordPress 6.4 “Shirley”.
\n\n\n\nRich Tabor posted a Twitter Thread with 19 different features from 6.4. And you can also explore the version via the Microsite.
\n\n\n\n\n\n\n\nSarah Gooding reported on the release: WordPress 6.4 Introduces Twenty Twenty-Four Theme, Adds Lightbox, Block Hooks, and Improvements Across Design Tools.
\n\n\n\nGutenberg YouTube, Jamie Marsland explained WordPress 6.4 in 250 seconds.
\n\n\n\nDeveloper relevant changes that came to WordPress with its latest release can be found in the WordPress 6.4 Field Guide, compiled by Abha Thakor together with the docs release team. Here are the block editor-specific Dev Notes
\n\n\n\nJustin Tadlock was release lead for Gutenberg 16.9 and highlighted in the release post: What’s new in Gutenberg 16.9? (25 October)
\n\n\n\ntheme
attribute provided (55217).getEntityRecords()
calls now return pagination totals in the returned data (55164).Sarah Gooding also reported on the release: Gutenberg 16.9 Lets You Rename (Almost) Any Block, Adds Experimental Form and Input Blocks.
\n\n\n\nHector Prieto managed the release of Gutenberg 17.0. In his release post What’s new in Gutenberg 17.0? (9 November) , he wrote: “This release focuses on maintenance with improvements in performance and accessibility, along with a few new features.” and highlighted:
\n\n\n\n🎙️ Latest episode: Gutenberg Changelog #92 – Twenty-Twenty-Four, WordPress 6.4 and Gutenberg 16.9 and 17.0 with Jessica Lyschik as special guest, hosted by Birgit Pauli-Haack
\nLast Friday, I had the tremendous pleasure of chatting with Jessica Lyschik through all the releases, but mainly the Twenty-Twenty-Four default theme. The episode of the Gutenberg Changelog is already available online.
\n\n\n\n\n\n\n\nJessica Lyschik and Margarita (Maggie) Cabrera were the co-leads for the development of the Twenty-Twenty-Four default theme. Beatrix Fialho created the first designs. From the pops list of the import ticket I counted 83 contributors in total. That’s a massive participation from the community.
\n\n\n\nThe first feedback was overwhelmingly positive. Two quotes from X (former Twitter)
\n\n\n\nProduct Manager, Hashim Warren tweeted: “Played with the new WordPress “Twenty Twenty Four” theme for a few hours. Then quickly switched my site to use it. The first time I’m using the default WordPress theme on a project I care about. Really great work there”.
\n\n\n\nRae Morey, editor of The Repository newsletter tweeted her comments as well: “Holy crap, WordPress 6.4 and Twenty-Twenty Four are a match made in heaven! Props to everyone who contributed. Saying goodbye to my page builder. ” and then “The updated editing experience is a game-changer. Previously, I found it so confusing to know where to start when I enabled a block theme. Yesterday, I redesigned my whole site in a day with Twenty-Twenty Four. Here site is: therepository.email“.
\n\n\n\nYou can download the theme:
\n\n\n\nTopher DeRosia reviewed the theme for Winning WP: WordPress Twenty Twenty Four Default Theme Video Review – How Good Is It? and shows you how to customize the theme.
\n\n\n\nWes Theron introduced the Twenty-Twenty-Four Theme. The idea behind Twenty Twenty-Four was to make a default theme that could be used on any type of site, with any topic.
\n\n\n\nCarlo Daniele shared his view in his post: Twenty Twenty-Four: The New Minimal Multipurpose Default WordPress Theme. “More than a theme, Twenty Twenty-Four is a collection of templates and patterns that, combined, enable you to build a wide variety of websites.” he wrote.
\n\n\n\nNick Diego and Justin Tadlock invited Jessica Lyschick and Maggie Cabrera to this month’s show of Developer Hours. The recording is now online on WordPress TV. Jessica Lyschik led the presentation, which was followed by a Q&A session. The presentation included a demo/walkthrough of Twenty Twenty-Four, showing what the theme is capable of. They also shared some background information and tips and tricks on the new features and how to make it your own.
\n\n\n\nJoen Asmussen again published his bi-weekly sharing of the work from the Design team here and here.
\n\n\n\nThe new design of the WordPress.org Showcase is a wonderful tool to help agencies and freelancers to point to when discussion the use of WordPress with their clients. It’s beautiful and the broad range of types of websites.
\n\n\n\nSarah Gooding has the details in here article: WordPress Relaunches Showcase Powered by Blocks
\n\n\n\n\n\n\n\nKevin Batdorf created the Command Palette Tools plugin, with fun commands for the WordPress Command Palette. The plugin installed allows you to evaluate Math expressions or convert color on the fly and create multicolored confetti.
\n\n\n\nManesh Timilsina submitted a new block theme Taza to the official WordPress theme directory, where it is still in review. A demo is available on. taza.wpmanesh.com. “Taza comes with a two-column layout including a sticky sidebar and a content area.” Timilsina wrote.
\n\n\n\nIn his interview with CodeinWP’ Adelina Tuca he shared the genesis of an earlier Theme: Jadro, also available in the Theme repository.
\n\n\n\n\n\n\n\nEllen Bauer announced their new block theme for the WordPress repository, Moog. “Our new fun, creative free WordPress theme for blogging is released just in time for WordPress 6.4.” Ellen walks you. through it on YouTube: Fun Free New WordPress Block Theme for Bloggers
\n\n\n\nAnders Noren also released a new block theme in the WordPress Repository: Hideo. “It is a clean portfolio and blog theme with bold headings and subdued colors. It comes with 7 different theme styles and over 20 block patterns. Read his Introduction to Hideo blog post and view a demo on Noren’s website
\n\n\n\n\n\n\n\nNew resource for block theme features: The new Features chapter for the Theme handbook includes docs for patterns, block stylesheets, block styles, and block variations. The longer-term plan for the pattern’s doc is to split this into multiple sub-docs, but it was decided to get v1.0 out first than to continue waiting until it was perfect (ship early and iterate).
\n\n\n\nMike McAlister, designer and developer of the Ollie theme, reached out to Anne McCarthy to share some feedback about his recent block theme building experience, and they decided together to turn it into a hallway hangout to have it benefit the wider community and gather more insights. Anne McCarthy shared the recording and summarized the discussion in here post: Hallway Hangout: Let’s chat about the experience of building a block theme.
\n\n\n\nJustin Tadlock published a call for Discussion: How to handle custom settings screens in block themes for the theme review team to tackle the similar topic of settings screens in blocks themes. Your opinion is important. Comment on the post.
\n\n\n\nSarah Gooding reported on the new chapter of the Theme Handbook: The new block-focused Templates chapter is now in the Theme Handbook. “The new chapter on block templating is just one part of a larger effort to overhaul the Theme Handbook for modern-day WordPress. Contributors are transitioning the focus from classic theming to block theming, with just one chapter in the handbook devoted to classic themes.” She wrote.
\n\n\n\n\n “Keeping up with Gutenberg – Index 2022”
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2021 on. Updated by yours truly. The index 2020 is here
Thomas Roberts published the First edition of WooCommerce Blocks Extensibility Snaps – a monthly update to highlight things the WooCommerce developers have been working on. This edition covers the new WooCommerce Components and the custom fields for the Check-out block.
\n\n\n\nWordPress VIP has released a handy block governance plugin on GitHub that adds additional governance capabilities to the block editor (GitHub). The Readme file explains usage as well as customization from the default settings.
\n\n\n\nRyan Welcher continued his Block Development Cookbook series with three more recipes:
\n\n\n\nIn case you missed earlier recipes, browse Welcher’s cookbook play list on YouTube
\n\n\n\nJustin Tadlock collected another edition of the What’s new for developers? (November 2023) round-up post. “Much of this edition of our monthly roundup will include changes that have already landed in WordPress 6.4. Read along if you’re still playing catch-up. You’ll also learn about some features that are still in development, so be sure to install and activate the latest version of the Gutenberg plugin to test them.” he wrote.
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph.
\n\n\n\nFor questions to be answered on the Gutenberg Changelog, send them to changelog@gutenbergtimes.com
\n\n\n\nFeatured Image: “Building Blocks” by Holger Zscheyge is licensed under CC BY 2.0.
\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nBirgit Pauli-Haack and Jessica Lyschik discuss the latest default theme, Twenty-Twenty-Four, the latest WordPress release 6.4 and the last two Gutenberg plugin releases.
\n\n\n\n\n\n\n\nShow Notes
\n\n\n\nDiscussion: How to handle custom settings screens in block themes
\n\n\n\nStay in Touch
\n\n\n\nTranscript
\n\n\n\nBirgit Pauli-Haack: Hello, and welcome to our 92nd episode of the Gutenberg Changelog podcast. In today’s episode, we will talk about WordPress 6.4, the default theme, Gutenberg 16.9, Gutenberg plugin release 17.0. And that’s a lot. So I’m your host Birgit Pauli-Haack, curator at the Gutenberg Times, and a full-time core contributor for the WordPress Open Source Project sponsored by Automattic. And today, I have the pleasure to introduce our listeners to Jessica Lyschik, a core contributor and WordPress 6.4 release team for the default theme together with Maggie Cabrera. So Jessica was also the co-lead organizer of last month’s WordCamp Germany in Gerolstein. Both the building of the default theme and the WordCamp organizing were taking place in the same time space in the last few months. So I’m thrilled that you can make time for the show. Welcome, Jessica. How are you today?
\n\n\n\nJessica Lyschik: Hi, Birgit. Thanks for having me. I’m doing great. A bit tired because this week has been quite exhausting, but I’m very much looking forward to today’s episode.
\n\n\n\nBirgit Pauli-Haack: Yeah. I’m so glad that you’re here and it’s been a while that we said you should come on the podcast, so I’m glad you made it today. Yes, there was a lot of work for the Open Source Project project and…
\n\n\n\nJessica Lyschik: Yes, it was.
\n\n\n\nBirgit Pauli-Haack: … I’m so happy. Congratulations. Welcome to Germany. Have you recovered-
\n\n\n\nJessica Lyschik: Thank you.
\n\n\n\nBirgit Pauli-Haack: … from it all?
\n\n\n\nJessica Lyschik: It took a few more days than expected, but I really had to recover from this. There was a huge push in the last few weeks before WordCamp Germany because some things were about to fall apart, but as they always do. But we managed to create a wonderful event and we’ve got very, very good feedback from attendees, sponsors, speakers, literally everyone was super happy to have been in Gerolstein, and that was fantastic. And yes, of course the default theme also took a lot of hours from me. But yeah, I think we did a great job on this and Maggie was fantastic to work with.
\n\n\n\nBirgit Pauli-Haack: Yeah. And we’re going to talk a lot more about that in just a few moments. But before we head into the releases to listeners, we have a couple of announcements from the project that happened in the last, I don’t know, four weeks since the last episode. So first of all, there’s the State of the Word for those who are new to WordPress, WordPress co-founder Matt Mullenweg shares reflections on the projects’ progress last year, and then what’s in it for next year, and the future.
\n\n\n\nAnd it’s also the time where we celebrate the community activities and the software updates. This year it will take place on December 11th, 2023 at 1500 UTC. That’s for our American friends 9:00 AM Eastern, and it’ll be live-streamed from Madrid. Details on how to reserve a ticket for the in-person event, the link to watch the live stream, and information on how to submit the questions for the Q and A portion will be provided later this month. So watch the news section on the WordPress.org website. Of course we have the save the date post link in the show notes. I’m really excited what’s going to happen there. Do you have any comments on that? What do you expect?
\n\n\n\nJessica Lyschik: It’s interesting to see that it got moved outside the US. I think it’s the first time it’s not happening in the US and I would be curious to hear why Madrid was chosen because… I’ve never been there before, but I know that it’s in a very interesting city, so we’re really looking forward to that.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah, me too. Yeah, you’re right. It’s the first time outside the US. It’s also the first time… Not the first time outside of WordCamp US. The previous two times 2021 in 2022 were also a separate event, was not tied to WordCamp US, which made WordCamp US a little bit more flexible when it’s going to take place. The State of the Word was always in December, but now the WordCamp US was in October, was in September, now in August. So it was moved a little bit earlier into the year. I’m really looking forward again, as always, to reflect on what the last year brought, because right now I’m just like you, what happened last week is all I can think about and what I’m reflecting on. But yeah, so we get a chance for that with it. December 11th, 1500 UTC.
\n\n\n\nJosepha Haden Chomphosy published the proposed release dates for 2024. The proposal is actually on the Make Blog. I’d just say it on… Yeah, it’s a little bit hard if you can’t look at it, but maybe you can retain the 6.5 is scheduled to be released March 26. Well, it’s proposed to be released. The release team still needs to chime in there, which makes beta February 13th, beta one. 6.6 is scheduled for mid-July, July 16th with a beta of June 4th. And then 6.7 similar to 6.4 this year with a January release on November 5th and September 24 in beta one. So I’m always looking just one release ahead of time.
\n\n\n\nAnd Héctor Prieto also chimed in and said, “Well, the last Gutenberg release shipped in 6.5 will be 17.7. That’s seven more complete Gutenberg cycles until we have Beta 1 in February 13th.” Wow. It sounds so far away, but seven releases is not that far away. If we release every two weeks, we have already released the Gutenberg 17.0. So there’s quite a few things that might get in there. We’ll see what the developer team is coming up with a roadmap for 6.5. I’m sure that Fonts Library will be on the list of wanted features like the last five releases. So Interactivity API will be certainly make an appearance again, and maybe we see some new data views or admin redesigns. What do you think?
\n\n\n\nJessica Lyschik: Yeah, that sounds pretty good. I also very looking forward to the font library. Pretty much a bummer. It didn’t get included into 6.4, but it doesn’t make any sense if you push something into the release just to have people complaining about it because it doesn’t work as they expect it to. So if it can be a bit more refined, and I hope this gets to be done by 6.5 because it’s so much of a needed feature to have this management of fonts, especially since we have pushed Google fonts out of the default themes. I was one of the people involved in this for the older themes earlier this year, and of course the last few default themes have already been doing this. It always brings a bit of a problem when you have your own custom fonts or a project requires it, then you have an extra additional work with creating a child theme, making sure it does work there, it gets implemented, and this could solve so many issues and would it make so much easier for every user to just…
\n\n\n\nBirgit Pauli-Haack: Yeah. No, I hear you. And I think because it’s such an important feature, it needed a few more iterations in the Gutenberg plugin base before it gets into core to get more of the kinks out. And if I recall correctly, but there were still quite a few things happening in development in Beta 1 and Beta 2. Fonts Library got pushed punted in beta two, but that it really makes sense to have a few more test cycles for it.
\n\n\n\nJessica Lyschik: Yeah. Maybe some iterations for the replacement of templates that got newly introduced for the default theme because right now it’s very hidden unfortunately, so you have to show people where to go. And if this could be improved over the next version, that would be fantastic because you have such a large sidebar when you open the site editor in browse mode and it would be just perfect if we could implement this replacement feature into the sidebar alongside with all the other settings you can do basically on a template.
\n\n\n\nBirgit Pauli-Haack: Right. And I think there are already some versions of that in the Gutenberg plugin release in 16 point… So 16.1 was the last release that got in… No, 16.7 was the last release that got into 6.4. But in 16.8 and .9, there were additional functionality built that, the bug fixes would be backported, but some of them didn’t make it into the beta because it was so late, but it’s already in Gutenberg, so we can definitely test it there and refine it there. The template part itself, the concept for the user, what is a template and what is a page still seems to be a confusing piece of it. And I can understand that because a WordPress user, an existing or someone who was using WordPress for the last, I don’t know, 10 or 20 years, never had to deal with it because it was always part of the theme and all of a sudden now that added a complexity. We didn’t make a good way to abstract that complexity away to make it easier to realize what they’re doing.
\n\n\n\nBut I think the site editor is now on the way to help with that with a different view and edit modes for templates and page content, but it’s still one additional hurdle for a content creator to make.
\n\n\n\nSo this brings us to the perfect segue to the community contributions item that I selected was… So in September there was actually a big discussion around the theme submission to the WordPress repository that included a few features that didn’t comply with the guidelines that helped a new user to figure out what to do with a theme. And strictly speaking, those features were definitely in the plugin territory and the discussions made clear that there is a need for better onboarding, but it also made clear that you cannot make exceptions for one theme and then have the other themes. So why him or why her and not me? So it’s clear that there needs to be a discussion about standards, about the way to do this for WordPress, and that has been opened now a couple of weeks ago.
\n\n\n\nIt’s a post on the theme Make Blog called, Discussion: How to handle custom settings screens in block themes. And this definitely needs your input if you’re interested in that, if you make themes, and if you want to find a way to have a standardized way on getting an onboarding sequence, for instance, for your theme into the guidelines of the theme repository, that is definitely a discussion where you could be. It wasn’t clear to me what the next steps would be, but the next one is definitely comment on it and if you have time, the themes team meets every other Tuesday at 1500 UTC in the themes review channel on the Make Slack. I think I need to put some links there in the show notes. I think that’s not easy to retain from a radio podcast. But yeah, so that is definitely where the community needs to give some input, where the contributors need some help to figure things out. Do you have any opinion of that now with a default theme? Maybe we can talk about it a little bit there.
\n\n\n\nJessica Lyschik: A lot of opinions to be honest. Yeah, I actually did not know about this post. So just two days before we WordCamp Germany happened, so it totally missed me, but I will definitely go through this later on. But yeah, I can see both sides in this discussion actually. So from a theme author’s perspective, you are limited definitely, and there is, from a user perspective, a huge need for proper onboarding. So there is no standardized system, and every plugin and, in theory, every theme, but every plugin does it on its own.
\n\n\n\nThey often look similar, but everyone does it on its own. And I think we have various APIs in WordPress, and I think an onboarding API would be something for the future that we could consider implementing because then you could say, “Okay. Even if it’s a theme, when you have the standardized API, it would be possible for a theme to like, ‘Hey, just put these settings and here can you change this and upload your logo or whatever that needs to be done for a theme to be set up properly or look good.\'” And yeah, that’s pretty much what I would like to see in the future at some point.
\n\n\n\nBirgit Pauli-Haack: Yeah. The question is does it have to be in the theme or should it be in core? Should it be on the hosting side? I know that there is a product out there by the fine folks at Extendify that has an onboarding sequence that they offer hosting companies to sell their WordPress installations or come with their WordPress installation. I saw some prototypes and those looked really, really well. So the big problem is when you have these features in a plugin or in a theme and the features are plugin territory, what you do is pretty much close down the system that people cannot switch themes without losing content. And that is something that the theme directory really wants to avoid. And so any onboarding sequence or feature would need to make sure that the content that it’s added through that place is in proper places in the database. So when the theme changes that the content is not lost. And that I think is a bigger problem than I think we make it out at the moment.
\n\n\n\nJessica Lyschik: Yeah. But then it’s definitely core territory, so it should land in core this onboarding API, whatever you want to call it. But yeah, that’s the point because otherwise when you just say it’s okay, it’s just for plugins, then themes will always come with a companion plugin. And the question is, is that really needed? Then why it should be in core? And no matter if it’s a plugin or a theme, they all can benefit from this kind of onboarding.
\n\n\n\nBirgit Pauli-Haack: Yeah. And there are these efforts to do a redesign of the WP admin in certain ways. Maybe that brings back that discussion for core contributors to add something like that as well. So I think the discussions are all there. One is again on the Make Theme Block. Yeah, chime in, be part of it, be part of the discussion, and then you may be part of the solution as well. So that’s part of what you might have missed. Jessica and I did while we were celebrating WordPress Germany, I was also on a team retreat for a while and then had four days vacation, and all of a sudden my backlog is insurmountable and I’m going back on it one day at a time.
\n\n\n\nJessica Lyschik: Definitely.
\n\n\n\nBirgit Pauli-Haack: WordPress 6.4, it’s called Shirley after the iconic jazz artist, Shirley Horn, was released on November 7th with a quick point release on November 9th to fix a bug with an older version of cURL, which is a command line request tool. And the request tool we have in the… If you are very interested, it’s very highly technical. And if you’re interested, I’ll share the link to the WPTavern article to it. They have the skinny for you. But this release is a combination of an immense effort and passion from over 600 contributors across at least 56 countries. And it included 170 first-time contributors. This is pretty huge, I think it was… Yeah. So 600 contributors is one of the biggest releases. So we talked on this podcast in episode with Joni Halabi, Nadia Maya Ardiani, Tammie Lister, and Ellen Bauer, already on WordPress 6.4. It was in the making for quite a while, shorter than others. But I also will ask today’s co-host, Jessica, the same question. So what features in 6.4 excited you the most and why?
\n\n\n\nJessica Lyschik: Well, the default theme, obviously.
\n\n\n\nBirgit Pauli-Haack: Apart from that.
\n\n\n\nJessica Lyschik: … we will get into that later. Apart from that, of course renaming group blocks is something I was looking forward to. It has been so needed in the past for me and I’m very glad it’s finally here. And I can’t wait until this comes to all the other blocks as well because it will make editing so much easier, especially if you have larger sites with lots of groups and lots of content grouped together. That’s one of my highlights. And the lightbox feature, the image lightbox is pretty neat one too. And what else was in…
\n\n\n\nBirgit Pauli-Haack: No, it’s not.
\n\n\n\nJessica Lyschik: I’ve forgotten
\n\n\n\nBirgit Pauli-Haack: There’s a highlight. So what I also like is that you now, as a user, can categorize your custom patterns. You can not only have a huge list of patterns that you spread all over your website, but you can also put them in categories. I think that’s a major place to be for patterns.
\n\n\n\nJessica Lyschik: Yeah. And maybe background images in groups. You said last evening, so yesterday evening, I was presenting changes in 6.4 to the local meetup group, and it was pretty exciting to see how easy it was to just add a background image to a group block and put some contents in it and make it look nice.
\n\n\n\nBirgit Pauli-Haack: Yeah. I also like that you can now see the thumbnails in the list views of your pictures or the image blocks or the gallery blocks, so that’s pretty cool too. Yeah, the footnote was new in 6.3, but now you have vertical text support, which is the vertical text support is actually pretty much rolled out as well in 6.3, but it got a lot less fragile in 6.4, so that is definitely a good place to be too. So Rich Tabor posted a Twitter thread with 19 different features or highlights from 6.4, which I will definitely share in the show notes so you can follow along. Here’s a little video on it and how to use some of those. Although the font library didn’t make it and neither did two new blocks that were actually on the list, they were punted to 6.5. It’s still really a feature-rich release.
\n\n\n\nThere is a microsite now available. You can explore the features with. Yeah, I can also share some of the other posts from WPTavern. And Carlo Daniele from Kinsta did a great writeup on the features of WordPress 4. So WordPress 6.4 also comes with a few developer relevant changes and I would highly recommend that you check out the WordPress 6.4 field guide to learn about them, especially the block hooks for dynamic blocks where you can add a block to a block automatically with your code. And we talked about this on the episodes before like a like block or a shopping card block or even an additional lightbox feature if you want to do that.
\n\n\n\nThere’s also new admin notice functions, updates to the HTML API. The removal of the attachment pages for new installations is actually something that Joost van den Bergh was really passionate about and is very happy that it finally made it into WordPress 4 because for a SEO, they’re not useful, but they clutter the whole basis of pages on sites in the Google index. So there’s improved caching, autoloading for plugins, and options. So there’s a lot of few more things there, so the field guide is your friend. Is there any of that that excites you more or that you know that you need to explore because you have a real case application for it or so?
\n\n\n\nJessica Lyschik: Yeah. I think the block hooks is something definitely to explore because it’s very interesting feature to just hook in as we know it from the normal WordPress hooks just but for blocks. And yeah, one thing that’s really cool is also the removal of that attachment pages. I think I have to check again, if you can do it for existing sites somehow. I think there was something possible. I quickly found it somewhere, but I’ve forgotten it already.
\n\n\n\nBirgit Pauli-Haack: Yeah. It’s in the dev notes, how you can make that available to existing pages out of the box. It only works for new installations, but you can go back and update your existing sites to…
\n\n\n\nJessica Lyschik: Yeah. I think it would be very beneficial for already existing sites as well to have that happen.
\n\n\n\nBirgit Pauli-Haack: Yeah, absolutely.
\n\n\n\nJessica Lyschik: But it’s a great way to introduce it without making too much of an issue when you just remove them with the update instead of as it is now, it’s only for new installations and then you can manually update it to also disable them.
\n\n\n\nBirgit Pauli-Haack: Yeah. There’s even a WP Options way to do that in the interface. There’s WP admin/WP options where you see all the options files. You can definitely do it from there, but you can also do it code wise.
\n\n\n\nYeah. So now let’s talk a bit more. We mentioned it multiple times before the new default in Twenty Twenty-Four. So yeah, you, Jessica, and Margarita (Maggie) Cabrera were the co-leads for the development, and Beatrix Fialho created the first designs, congratulations. It seems that the first feedback was overwhelmingly positive. We saw that coming during development. I don’t know if you saw it, but I saw it.
\n\n\n\nJessica Lyschik: Yes, I saw it, and it continued and it still continues. And that is what really makes me happy that Maggie and I did something everyone is excited about. That’s just so cool.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I just want to do two quotes that I found on Twitter. One is from Hashim Warren, he’s a product manager and worked for Gatsby and WP Engine and also for Apollo. And he said, “Played with a new WordPress Twenty Twenty-Four theme for a few hours. Then quickly switched my side to use it. The first time, I’m using the default WordPress theme on a project I care about. Really great work there.” Yay.
\n\n\n\nJessica Lyschik: Yay. That’s cool.
\n\n\n\nBirgit Pauli-Haack: And Rae Morey, she’s the editor of the, The Repository newsletter tweeted her comments as well and says, “Holy crap, WordPress 6.4 and Twenty Twenty-Four are a match made in heaven. Props to everyone who contributed. Saying goodbye to my page builder.” The updated editing experience is a game changer. Previously I found it so confusing to know where to start when I enabled a block theme. Yesterday, I redesigned my whole site in a day with Twenty Twenty-Four, and here’s the site, it’s therepository.email. The repository is an email that’s supported by GoDaddy. And Rae had just announced that they have the four-year anniversary on the newsletter, and I think it was edition 192 that came out on today. That’s Friday, November 10th. So yes, Rae, great comments there for the team.
\n\n\n\nJessica Lyschik: I just opened the site and it looks pretty good.
\n\n\n\nBirgit Pauli-Haack: Yeah. And as everything in reference, it’s created by a team of contributors and from the props list of the import ticket into core. I counted 83 contributors in total. That’s a massive participation. Must’ve been quite exciting to wrangle all the input, feedback, contributions.
\n\n\n\nJessica Lyschik: It was mainly managing actually. So I did a few things on my own, luckily, yay. I could also contribute code. But yeah, I was mainly on the management side on this, but it was so exciting to see that so many people came in and opened issues, open pull requests, and helped out with making this a reality given the very limited time we had actually. And I think that’s not something that a lot of people are aware about, but we had just basically a month, but then we extended it because like, “Okay. It’s just updating patterns so we can do it during better as well.” So hope no one kills me for this, but yeah, otherwise it wouldn’t be in the state that is now. And yeah, it was so great to see.
\n\n\n\nAnd I think also what really helps in contributing to the default theme is that it’s made on GitHub as well, just like the Gutenberg project because I can only speak or I can also speak, especially for myself because I find it so hard with Trek and SVN to make fixes or do new stuff in it and in GitHub it’s just so much easier for me even to have this entire process done. And we just set up very few rules and it really went up very well, had great discussion sales too. And again, I’m so happy that so many people contributed, and we also did our best to include everyone in these contributions file because everyone deserves to be in there, even if it’s just opening an issue and saying, “Hey, I got a problem with this,” or, “Is this something we should think about?” Because every discussion is worth it.
\n\n\n\nBirgit Pauli-Haack: Oh, yeah. Especially bug reports. It’s half the work is already done, somebody found it and nobody else needs to go if you find a fix in time to go through it. So yeah, it’s really valuable time to spend to contribute to that. Yes. And so the theme itself has an outlook for three different use cases. Can you talk a little bit more about that?
\n\n\n\nJessica Lyschik: Yeah, sure. So the original idea was… I shared it first time with Maggie when we met at work in Europe just a few days earlier it got announced, the release squad got announced. So I met her there the first time and I shared this idea with her, let’s make a default theme that does not only showcase that you can make a block with WordPress, but you can do any type of website basically. Of course, we could not include any type of website. That would be pretty huge and we would still be developing that. But what are the main very often used cases where WordPress is used as the platform for this website. So of course blogging is one, but business is also a very important one. And I think many websites today getting set up on WordPress are business focused in some way.
\n\n\n\nAnd portfolio was also another one to showcase your work, either if you’re a graphic designer or make products of your own physical products, you can also showcase them with these. And it became pretty clear that this was the way to go and I’m glad that it did not get questioned it too much, but that people also saw that it’s an interesting idea to showcase what’s possible with WordPress in these three specific use cases. And once we knew that Bayer was doing the designs for it, we also briefed her with this entire brain child of us, how we would like to see this and how we’d like to see the default theme coming together. And I must say again, she did a fantastic job on this as well, bringing this to life and also the style variations, giving a bit of variety in what could colors of fonts basically look like in a setup of the patterns that we already have.
\n\n\n\nBirgit Pauli-Haack: So one of the big features that I think made people very successful at the first round of trying to customize their website is that it uses full-page patterns. So when you create a service page, you get your services in there, you get a header graphic, you get a footer graphic, and all that. So I think that particular feature was something that was available before but not long before, maybe 6.2, but it wasn’t showcased by anyone that much. So having that in the default theme definitely makes it really good available for everybody.
\n\n\n\nJessica Lyschik: Yeah. It just lowers the bar for the average user to like, “Oh, hey, I can just switch out this template with the other one I prefer or I need for my website on this.” And I think that’s something… Because previously you would have to delete all the blocks that you had on the site and recreate them on their own and you have to find the patterns that you would use and how could you arrange them. And with Twenty Twenty-Four, you get pre-built templates you can already use or just use and adjust to your own needs. And I think this is what’s helping people a lot compared to Twenty Twenty-Three, which was pretty stripped down basically.
\n\n\n\nBirgit Pauli-Haack: Yeah. So for our listeners, I have a few links for you. One is the blogger demo, and the artist/photography demo, and of course the main site, demo site. And then also a link to the patterns and of course the download link if you don’t have that yet. Yeah, so try them out, I think it’s a great move forward. I think the Gutenberg Times will always also will migrate to a block theme, probably the default theme. I have started the process and then backed away again because I need to have a few quiet moments, haven’t had that yet to think through some of the features that we need because we need the podcast template and we need the podcast archive template and the plugins don’t provide that yet, so we figure that one out and a lot of other things, mainly having the time.
\n\n\n\nJessica Lyschik: That would be a cool project to do it in public and have people following around maybe.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah, I’m trying. I’m probably teaming up with Justin Tadlock who’s a theme wiz to help me out with that. So I actually finished that project because most of the time, some of the project I just start see what I can do and then, okay. Yeah. Now I know how this works and then I lose interest. But this one I would need to have to finish and it will be the first redesign since, I think, 2020. So three years or four years then. All right. So is there anything else that you want people to know about the defaulting?
\n\n\n\nJessica Lyschik: Go test it out, have a look at it, play with it. I would be super interested in any feedback, positive or constructive. Negative, maybe not, but constructive. That’s why I said it because we can always learn for future themes. What does work well or what does not work not so well because I’ve already seen a bit of feedback on people implementing it. For example, Matt for Matt Report had already done a video on this. I only saw the first bit of it so far and it was very interesting to see what he struggled with actually that I wasn’t so much aware that was would be a problem. And that’s definitely something you can always…
\n\n\n\nBirgit Pauli-Haack: Do you have an example?
\n\n\n\nJessica Lyschik: … look back at his feedback. Sorry?
\n\n\n\nBirgit Pauli-Haack: Do you have an example of what he struggled with?
\n\n\n\nJessica Lyschik: Actually it’s when he updated on this mattreport.com website and he had a static site configured as his front page, so the homepage, and then had this lock subsite as on the slash block. And when you have this set up, what happens is Twenty Twenty-Four brings the template you have you see on the front page when you have not set up that it brings the entire template in, which can be confusing for people because there’s all this content they never edit before but it’s in the template. So that’s something I wasn’t aware of that even in this case I thought it would be overwritten already, but of course now that I saw it’s definitely clear what happens.
\n\n\n\nBirgit Pauli-Haack: Do you think it’s a bug?
\n\n\n\nJessica Lyschik: That’s a good question. If it’s a bug or a feature, depending from which side you’re looking at it. But he had to remove all the contents to just simply show query block with the latest posts on the website. But this is not something particularly the default theme can fix. Of course you could remove all that extra patterns from there, but it’s also something we have to send upstream to the Gutenberg repository to say, “Folks, please look at this. It’s okay, it works somehow, but we need a way to fix it.” Or a very common thing is people edit their templates, switch the theme, and then their content is gone. It’s not gone but it’s in the template so it’s not there in the next template. And these custom user changes are also something that needs to be considered for the future because the more we work with block themes, the more we see where we still have some issues we need to fix.
\n\n\n\nBirgit Pauli-Haack: Those issues were there before, but they were abstracted away because it was the theme developers thing, but the user never was confronted with it because the theme took care of it with an if statement and all that, and it tapping into the settings and then because you don’t have these if statements in the template somehow all of a sudden it’s a little bit disjointed there. Yeah, I can see that. Yeah. All right. Okay, good. Yeah, I had the same problem when I switched my… I have a personal technology blog where I just keep track of things that I learned, that I need to look up three months from now, and I probably will have forgotten how I did this. And that was one thing that I had a blog front page, but I needed to remove the stuff from the default theme. Yeah, that’s true. Didn’t remember that, but now that you mentioned it.
\n\n\n\nAll right. So we are done with 6.4 for now and the default theme. Thank you so much about letting us look behind the scenes there.
\n\n\n\nWe are coming now to the last two Gutenberg releases. Let’s start with Gutenberg 16.9 that was released on October 25th and Justin Tadlock was the release candidate and he shared all the information. Of course in his release post it entailed 168 PRs from 60 contributors and one of them was new. So as a new feature or what came in, and I wanted to highlight, is that you mentioned it for 6.4 was to enable the renaming of group blocks in 6.4. With 16.9 in Gutenberg you can rename almost all the blocks. So the custom names are stored in metadata in the block markup and meaning they can also be used for panon and templates, and that makes it so much more, I don’t know, less ambiguous for users when they look at the blocks that are in the templates or on their site. So that’s a great feature.
\n\n\n\nJessica Lyschik: I mean, my workaround right now is to use the anchor feature for this. It works but it creates anchors. Yeah, it’s not the best way, but if it’s coming to 6.5, that’s so great.
\n\n\n\nBirgit Pauli-Haack: Yeah. And because it’s in 6.9 it will be in 6.5 unless somebody has additional bugs that they find there during the beta version.
\n\n\n\nJessica Lyschik: Then we have to fix it before beta one.
\n\n\n\nBirgit Pauli-Haack: Then we have to fix. Yeah, absolutely. Absolutely. The next item is block specific commands as contextual suggestions. So 6.2 came with a command palette… Or 6.3, I forgot. 6.3 I think came with a new command palette where you do control K and then you get a search bar and then you can ask for certain things like add a post or open the patterns. And now there are block specific commands that are suggested contextually. So when you’re in a block it shows do you want to transform it or something like that.
\n\n\n\nSo it gets more like, I like that this software now becomes a little bit more contextual and you don’t have to know which menu item on which screen in which level you find something to switch on or off or you have to do three clicks to switch on the top toolbar and now you can just have the command bar, switch on top toolbar and it doesn’t. I don’t know if that command already exists, but I will find out. It’s almost like a shortcut. So these little things are a little bit on the edge of value, a palette command or just “Why don’t you just get a keyboard shortcut?” It’s the other thing.
\n\n\n\nJessica Lyschik: It makes it more keyboard friendly. So if you’re used to or if you prefer to work with the keyboard, it makes things so much easier because otherwise you have to always use the mouse to get to that contextual menu to select to copy or duplicate something or add before and after. And if you have these commands in the palette, you can just hit command K or control K and just use your hands on the keyboard instead of using your hand on the mouse. And I think that can be definitely beneficial for people who prefer to work on the keyboard only or prefer to work on the keyboard.
\n\n\n\nBirgit Pauli-Haack: And it also speeds up your publishing process when you only have, I don’t know, six sets of commands that you punch in into the command palette instead of clicking around with a mouse. Yeah, absolutely. I wonder if that’s on the roadmap for ISO 7.0 WordPress like having a programming, I as a user can Daisy Chain commands into a workflow? I don’t know if that’s going to be possible or it’s even thought about it.
\n\n\n\nJessica Lyschik: Oh, like Apple shortcuts.
\n\n\n\nBirgit Pauli-Haack: Yeah. Kind of Apple shortcuts. Or what was the other one? Alfred on Mac. There are quite a few. Even GitHub has workflows where you can just Daisy Chain some of the commands, but yeah, maybe we get a plugin for that. How about that? That’s definitely plugin territory I think. All right. The next feature is for developers, there is a new component and it adds the tabs. That’s a composable tab panel which was before, but it’s a tab panel version two. So you can build out interfaces that use tab labels and tab content better with components that are… It’s now available, you can test them out.
\n\n\n\nThe documentation seems to be already in there on the story book, not the style book, the story book for the developers to figure out how these tabs work. And there’s also a type button for the Vanilla button element is now available so you don’t have to make it up. What else? Oh, yes. Patterns got some new management features and it’s a nice addition with duplicate pattern command. They’re all for the command palette, rename the command, rename the pattern, rename delete options for pattern categories in the site editor. There are new media related categories for the patterns. So there’s quite a few changes in there to make this all a little bit more comprehensive as a management tool to create patterns and to make them available to certain content production people. Any comment, any ideas, any thoughts?
\n\n\n\nJessica Lyschik: Sounds pretty good. I have to test this out. I haven’t seen this. So again this is… But that’s pretty interesting to have these renaming features also now via the command palette because that’s something also I appreciate to have these pattern categories now that you can also create on your own and make it your own basically. That’s pretty cool.
\n\n\n\nBirgit Pauli-Haack: Yeah. And also add them to the theme and help the user to find things better. For developers, definitely something that they have been asking for quite a bit regarding extensibility of the block editor. There is now a new slot to put information or interfaces into the plugin post excerpt slot, and that means that in the post excerpt place where not only there’s the excerpt but there’s also other things in there. You now can, per plugin, add additional sections there. So that’s specific for the plugin for the post excerpt space there. That’s in the sidebar when you want to… The document settings, for the post itself, we also see featured image.
\n\n\n\nThere’s also one for the published slot for the pre-published slot, and there are quite a few other slot fills that you can use as a plugin developer, but we need more, I guess. And this one is definitely one that a lot of people ask for. In this design tools there are two changes. One is that the measurement 16.10 and 10.16 options were removed from the aspect ratio drop down and they figure that it wouldn’t take too much harm to do that because it’s too close to the 6.9. And I think that’s pretty much the justification for it.
\n\n\n\nJessica Lyschik: Yeah. To have less options and it’s not too overwhelming because the change from 16 to 10 to 16 to 9 is not that huge. For example, when you have four to three or three to two, that’s a big of a bigger difference than if you would have just a little bit of more on one side.
\n\n\n\nBirgit Pauli-Haack: Yeah. And then the other one is that you can now add CSS level 4 viewpoint relative units in the theme.json setting spacing units. And that brings us closer to bridge the gap between the big philosophies, intrinsic design, but I want my 15 media viewpoints crowd to… And intrinsic design does not solve all the viewport problems or mobile problems. So this definitely brings us closer to having giving theme developers and designers a little bit more options.
\n\n\n\nJessica Lyschik: I haven’t seen them yet, but they look very interesting. So much to catch up.
\n\n\n\nBirgit Pauli-Haack: Yeah. Come as a guest to the Gutenberg Changelog and you know what you missed.
\n\n\n\nJessica Lyschik: Yeah. You learn more than you think what you have missed in the past four weeks and beyond probably.
\n\n\n\nBirgit Pauli-Haack: Yeah. And there is a new API with 16.9 is that you can retrieve the pagination totals with the get entity records call. So get entity records function is a call to a query call to get the entities, be it pages, posts, post types metas, all that kind of thing. And now it also comes with a total so you can build pagination or use it some other way. That’s certainly for the developers quite interesting, which you are. So I hope it interests you.
\n\n\n\nJessica Lyschik: Definitely. That’s very much things I can look into. As I said, I have to catch up.
\n\n\n\nBirgit Pauli-Haack: Yeah. And the team was really… Although there was a slump in October kind of, and we talk about it a little bit in the 17, but there’s definitely a lot’s happening, there’s some momentum going with a lot of different directions. We are skipping over all the bug fixes that we saw in that change log and some other minor enhancements and drop right into the experiments because when you take a look at the new experiments page of the Gutenberg plugin, you see quite a few listed.
\n\n\n\nAnd the most interesting for me and probably other people in WordPress are the new data views. Those are prototypes for the admin redesign project on how to display the lists of posts, the list of pages, post types, and whatever plugin would need things to be listed. And in this Gutenberg version, you now can see the grid layout of those pages and how it looks when list contains a featured image or controls for the actions to switch the layoffs and also to have some additional actions in there. So it’s quite an interesting study to go in and look at the experiments. Of course everything is experimental, meaning, nothing lasts, nothing is final.
\n\n\n\nJessica Lyschik: Things will break.
\n\n\n\nBirgit Pauli-Haack: … things will break. And if you have ideas or want to comment on some of the features, GitHub is definitely your friend there. Comment on the current PRs or the PRs that are not merged yet or create new issues to discuss additional things, what you might need, what you think is missing because this is one of the few pages in admin that almost every plugin extends or needs and getting into the discussion. As soon as possible, make sure that voices are heard and listened to because sometimes there is this complaint that, well, we weren’t asked or we weren’t listened to or we didn’t know that was going on. And the discussions were designed, decisions were made were actually three years ago, like the block theme in 2022 or even in 2019. In 2019 we were already seeing prototypes of block themes and there were some, Gutenberg live Q and As where we talked about block themes, but only now in 6.2, .3 they came and went to WordPress 5.8, and then we’re always iterated on until now 6.4.
\n\n\n\nBut the other three years of it were missed by a lot of people that might have at least follow up on the discussion and see why decisions were made. So this is the place to get in on the new redesign. Another experimental feature there is basic form input blocks and to build out basic forms. Also very, very experimental and just a prototype. But if you enable those experiments you can see it in action and try it out and see how that works out, and if you can get to that. So that is the idea to bring a form building to core, at least the basic part. So you don’t need yet another plugin to do that, but it also helps standardized, it also aims for a standardized blocks that you can then enhance in plugins that plugins developers can enhance for their products, but can always be built on a standardized way of forming the input, doing the processing, and then what comes after processing to have that a unified API for that.
\n\n\n\nJessica Lyschik: Yeah. And I think this can only be beneficial for the future. So if everyone speaks the same language, you can make adjustments… you get the basics and you do not have to reinvent the wheel. You get the basics and then, from that point on, you can iterate what to your specific needs or to that project specific needs for example. And I think that’s a pretty cool feature.
\n\n\n\nBirgit Pauli-Haack: It is, especially for an Open Source Project. When you find that all of a sudden hundreds of people are maintaining the basis of your code and you only need to really handle the things that you, as a plugin developer, care about, that makes it a value added feature for you base your business on, but your basis is actually covered, and it’s good for all the whole ecosystem to have some then standardized way of doing things. That’s also why pretty much the block editor needed to be in core right away to have other people build on top of it to see if the other page builders can re-ramp their system to build on top of something because page builders closed the system down, didn’t they?
\n\n\n\nJessica Lyschik: Yeah. They did.
\n\n\n\nBirgit Pauli-Haack: You couldn’t change your site over to a different theme that wouldn’t support that page builder. So you were pretty much locked in into that particular way of doing things. And that’s never a good system for an Open Source Project that says open source in the name. Just to go back to that history of why wasn’t it a plugin?
\n\n\n\nThere’s a few documentation things that I wanted to point out. There’s also initial documentation for the AWs, so if you want to experiment with them, you can definitely follow the documentation on that. But there’s also a way, the documentation was updated for the appearance tools in the theme.json to include using background images for blocks that you can find now. And so when you have a theme, especially classic themes that enable appearance tools to have a set of design tools available to the block editor, you can switch it on and off for the background image as well. So I think that was Gutenberg 16.9. Is there anything that stood out for you apart from what we talked about?
\n\n\n\nJessica Lyschik: No. I think you pretty much picked the really cool ones. I mean, of course there’s so much going on. Just have a look at these blog posts. Everything is listed there and I think they’re super helpful to have an overview. And even if you do not get everything right away, when you come to a specific issue in developing for a theme or for a plugin, it is super helpful to have these handy so you can look up that version and you have a focused bird’s eye view. I know that sounds weird, but it is like that. And you can just see if anything in that version actually breaks whatever you’re working on or if there was a breaking change that makes things appear different than it was before. So they’re super helpful.
\n\n\n\nBirgit Pauli-Haack: It reminds me also to make a pitch for a series that will come out this week in its 9th or 10th edition. That’s the what’s new for developers’ monthly post on the WordPress developer blog where Justin Tadlock and I, we put together a list of things that are just new for theme developers for plugin developers and then some highlight things where even if they’re interface, user interface, or end user capabilities, sometimes a developer needs to know that that’s there so they can include it into their features and products. And then there is also a section on what’s new unlearn and the links to the developer hours. You mentioned that you were last week at the developer hours with Justin Tadlock, and Nick Diego, and with Maggie, and talking about the default theme. Those links are in that what’s new for developers once monthly post as well.
\n\n\n\nAnd the developer blog is available on developer.wordpress.org/news. So keep that in mind. It’s a good blog to subscribe to and has a wonderful RSS feed. And that was the pitch for the developer blog.
\n\n\n\nThough next up, very short, relatively short, the Gutenberg 17.0 release, Héctor Prieto was a release lead and it supports many small fixes and developers also made progress on the data views experiment that we just talked about. So with the two plugin releases, there’s definitely some headwind there.
\n\n\n\nSo the link control for the menu, there were new icons added to it, the blog icon for the block homepage and the home icon for the front page for the link control in the navigation block as much as I see it. And then the block theme preview, you also can see the loading state. So I don’t know if nobody really made a big deal out of it, but WordPress 6.3 came with a block theme preview in the admin.
\n\n\n\nSo you were looking for a new theme and if there’s a block theme, you could actually grade in the site editor, you can see a preview of the theme, you can see your content in the themes’ makeup. And I really enjoyed doing that with quite a lot of themes that were in the repository. Now this feature has gotten a new embellishment was that you now could actually activate the theme from the preview and now you see how the loading state works when it’s activated. So it goes from preview to actually, “Oh, this is now my theme and I can stay in the editor and make all the changes that I need to do in my templates or in my content and all that.” So it’s pretty neat, the block theme or preview.
\n\n\n\nJessica Lyschik: Yeah. Sounds pretty nice.
\n\n\n\nBirgit Pauli-Haack: I don’t think a lot of people have used it yet. I don’t see people talking about it. I don’t know.
\n\n\n\nJessica Lyschik: I mean, it’s a hidden feature, I guess, maybe then that’s why people are not aware of it. It’s like so often you come across something and you did not know that this thing existed.
\n\n\n\nBirgit Pauli-Haack: Look at that. Yeah, and I think, I guess, people don’t… I don’t know if that feature… There was before in the customizer where you could preview a classic theme, and I don’t know how many people used it before that we’re looking for it and we’re disappointed that they couldn’t do this with a block theme because it didn’t have that feature and now do it. I guess we need more adaptation of block themes to actually for people to use it more. The 7.0 also brings in the components, a new ariakit-based dropdown menu component that can be used in plugins and in your blocks if you need to. And it’s more accessible. And our kit is a small footprint, really built out kit for area labels and accessibility support for developers to make it less. You don’t, as a developer, have to know a lot about accessibility to still be accessible with that tool. So quite a few components will use that ariakit as well. And the developers are in the progress to migrate some of the components over to actually use it as well.
\n\n\n\nBut this is a completely new build component, the dropdown menu. There were new suggested commands for editing with a pattern similar to 16.9 as we dotted. And then there is one thing, ensure that term description block is registered in core that I think, actually, was that back ported to the version yet? I think it’s for 16.4. It was found in beta and yes, it made it actually into 6.4 that you can use the term description block that was available in Gutenberg also in your templates in 6.4 for your theme. That was an interesting addition. Either it was forgotten or nobody thought about it, but it definitely made it and it’s helping so much more. So what does it do? If you have a category page, archive page, you can actually add the description that you put into your interface for the category into the template and design it and have all the design tools for it. Am I right with that?
\n\n\n\nJessica Lyschik: Yeah, I think so. I guess, probably just got forgotten or, anyone who worked on this, never had a use case for this and someone just popped up saying, “Hey, why is this not available?” And it finally made its way. I wasn’t aware that it was put into 6.4 already. But yeah, good to hear.
\n\n\n\nBirgit Pauli-Haack: The 6.4 just came out, so it made it into the release candidate three I think. Cool, cool, cool. I guess we weren’t done with 6.4.
\n\n\n\nJessica Lyschik: You were never done with developing software, unfortunately.
\n\n\n\nBirgit Pauli-Haack: No. Yeah. That’s a Japanese beauty philosophy or design philosophy. It’s never done. It’s nothing permanent and it’s not perfect. Those are the three… that pretty much tells me, “Yeah, that’s the web.” You are always fiddling with something, and sometimes the websites go away, and you’re never done with things, and it’s never perfect.
\n\n\n\nJessica Lyschik: No, that’s pretty much true.
\n\n\n\nBirgit Pauli-Haack: Yeah. It’s my approach to web development now. I don’t have a lot of expectations. I take it like the weather.
\n\n\n\nSo I think that was it for the show. I think we talked quite a bit about things. Thank you so much for being on the show and talking with me through 6.4, the default theme and the plugin. Is there anything that you want people to know or how can people get in contact with you that you didn’t get to talk about before?
\n\n\n\nJessica Lyschik: Yeah. How to get in touch with me is relatively easy. I’m on Twitter or X as it is now under my name Jessica Lyschik. If you have Jessica Lys, then you can find me definitely. I am Jessica on the Mac Slack, WordPress Slack, you can find me too. And yeah, pretty much on every social network. I will probably not check them all, but Twitter and Slack is the best way to get in touch with me, definitely. And, yeah.
\n\n\n\nBirgit Pauli-Haack: Awesome.
\n\n\n\nJessica Lyschik: Maybe one thing I probably didn’t say in the beginning is I just started a new job last week, so I’m now with a team of Greg.
\n\n\n\nBirgit Pauli-Haack: Oh, congratulations.
\n\n\n\nJessica Lyschik: Yeah. Thank you. And yeah, that has been on top of everything else, so that’s why I am a bit out of date on so many things, but I’m catching up and got a ton of new information, like what’s going on there, what they’re going to do with the product. And it’s really interesting and super fantastic team, really great people and I’m very looking forward to bring in my knowledge to their knowledge and let’s make some fancy things.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I saw there were also a big sponsor for WordCamp Germany. And Sandra Kurze, she was also a speaker. So they’re all quite active in the WordPress community. Yeah, I met a few of them at WordCamp in Porto actually 2022. And since then they have been be more and more active in the community. So I’m glad that they hired you. Yeah, congratulations.
\n\n\n\nJessica Lyschik: Yeah. Thanks.
\n\n\n\nBirgit Pauli-Haack: … have some input from you and some contributions there. Yeah. All right. Well, we’re coming to an end and before I end the show, I want to remind everyone, as always, the show notes will be published on gutenbergtimes.com/podcast, and this is episode 92. And if you have questions or suggestions or news you want to include, send them to changelog@gutenbergtimes.com. That’s changelog@gutenbergtimes.com. Thank you everyone, and I’m glad we are back in talking to you. And thank you for listening, and goodbye.
\n\n\n\nJessica Lyschik: Bye.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 12 Nov 2023 15:03:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Gutenberg Changelog\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"WordPress.org blog: The Month in WordPress – October 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16365\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2023/11/the-month-in-wordpress-october-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9742:\"September-October 2023 was yet another fun and eventful chapter in WordPress, with more WordCamps hosting exciting discussions, knowledge sharing, and learning. This month also welcomed the release of WordPress 6.4 and the Twenty Twenty-Four theme. Let’s check it out.
\n\n\n\nWordPress 6.4 “Shirley” was released on November 7, 2023, and named after the iconic jazz artist Shirley Horn. With the release of WordPress 6.4 comes the new Twenty Twenty-Four theme, a multi-faceted, highly flexible default theme pre-loaded with more than 35 templates and patterns.
\n\n\n\nThis release includes more than 100 performance-related updates for a faster and more efficient experience. There’s also a host of new features and enhancements that help improve the content creation process and streamline site editing.
\n\n\n\nWordPress 6.4 was made possible by more than 600 contributors in at least 56 countries. Leading this release has been an underrepresented gender team, emphasizing WordPress’ commitment to fostering diverse voices in the open source project.
\n\n\n\n \n\n\n\n\n\n\n\nMark your calendars for State of the Word! The annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg, will be held on December 11, 2023. For the first time, the event will take place outside North America—this time with the Spanish community in Madrid, Spain.
\n\n\n\nA live stream will be available for WordPress enthusiasts who will not be able to attend in person. Stay tuned for more information, including how to reserve a ticket, soon!
\n\n\n\n \n\n\n\n\n\n\n\nTwo new versions of Gutenberg shipped in October:
\n\n\n\nOctober’s Core Editor Improvement post dives into all the writing enhancements expected in the latest WordPress 6.4 release.
\n\n\n\nhttps://wordpress.org/news/2023/10/episode-64-patterns-in-wordpress/\n\n\n\nHave a story we should include in the next issue of The Month in WordPress? Fill out this quick form to let us know.
\n\n\n\nThank you to Bernard Meyer and Reyes Martínez for their contributions to this edition of The Month in WordPress.
\n\n\n\nJoin over 2 million other subscribers and receive WordPress news directly in your inbox.
\n\n\n\n Subscribe\n
\nWordPress Executive Director Josepha Haden Chomphosy has published a proposed schedule for 2024 that includes three major core releases. The dates have not yet been set in stone but have been planned to avoid major holidays and WordPress events.
\n\n\n\nThe first release of the year, WordPress 6.5, is scheduled for March 26, followed by 6.6 in July and 6.7 in early November.
\n\n\n\nAlthough WordPress had officially concluded Phase 2 of the Gutenberg project (focused on Site Customiziation), 6.4 was focused primarily on extending existing features in the block and site editors alongside initial explorations of Phase 3 (Collaboration). Releases in 2024 will go full force into collaboration features.
\n\n\n\n“Given that 2024 will hold a bulk of the work for Phase 3, I expect that 6.5 and 6.7 will be focused on those Collaborative features,” Chomphosy said. “I would like to propose that 6.6 be held specifically for maintenance and general polish of the software (as was wished for earlier this year).”
\n\n\n\nChomphosy asked for feedback on the timing and focus of the planned releases. WordPress core committer Pascal Birchler suggested swapping the focuses for 6.5 and 6.6, as it’s not clear how much of of Phase 3 work will be ready in time for 6.5. The suggestion also makes sense in light of the features that didn’t make the cut for the previous release.
\n\n\n\nWordPress 6.4’s release squad had to punt the planned typography management flagship features and these are anticipated to land in 6.5. This includes a Font Library and server-side @font-face CSS generation and printing, which will allow users to browse a library of fonts in the admin, similar to managing media. It will not be dependent on the theme that is activated but will be a library that is extensible for plugin developers.
\n\n\n\nThe discussion regarding 2024 releases is still ongoing in the comments of the post. WordPress users may also hear more about what’s coming in the next year during Matt Mullenwg’s State of the Word address, which will be delivered live from Madrid on December 11, 2023.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Nov 2023 19:14:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"Do The Woo Community: WP 6.4, Black Friday, Tumblr, Free Plugins and Woo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77953\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://dothewoo.io/wp-6-4-black-friday-tumblr-free-plugins-and-woo/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:391:\"BobWP mentioning WordPress 6.4, Black Friday deals, Tumblr in the red, free vs. premium plugins and the Woo brand.
\n>> The post WP 6.4, Black Friday, Tumblr, Free Plugins and Woo appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Nov 2023 13:06:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"WPTavern: Wordfence Launches Bug Bounty Program\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151186\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com/wordfence-launches-bug-bounty-program\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8389:\"Wordfence launched a bug bounty program today to provide financial incentive for security researchers reporting high risk vulnerabilities to the company’s program.
\n\n\n\nAfter researchers disclose vulnerabilities to Wordfence, the company triages them and confidentially discloses them to the vendors to fix. When the fix is released, the vulnerability will be included in Wordfence’s public database, which is free to access, following a responsible disclosure policy.
\n\n\n\n“There is no cap on the rewards an individual researcher can earn, and every single in-scope vulnerability received via our submissions process earns a reward bounty,” Wordfence security analyst Chloe Chamberland said.
\n\n\n\nWordfence will reward researchers who discover vulnerabilities in plugins and themes with 50,000+ active installations. A few examples of the payouts include the following:
\n\n\n\n“Our Bug Bounty Program has been designed to have the greatest positive impact on the security of the WordPress ecosystem,” Chamberland said. “Rewards are not earned by bulk hunting for vulnerabilities with minimal impact and earning a place on a leaderboard, but rather, they are based on active install counts, the criticality of the vulnerability, the ease of exploitation, and the prevalence of the vulnerability type.”
\n\n\n\nWordfence’s bug bounty program launch was clearly vying for competitive positioning by indirectly calling out Patchstack, which operates its program on a leaderboard system where only the top researchers get paid. There are a few notable differences, where some bounties are awarded by discretion but most individual bounties are for the highest score in various categories:
\n\n\n\n\n\n\n\n\nPatchstack guarantees a monthly prize pool of at least $2425 (the lowest possible prize pool). Patchstack Alliance member who will collect the most points for a particular month from their submitted reports will get the $650 bounty, the second place will get $350 and the third will get $250.
\n\n\n\nWe have extra bounties (single bounties) for reporting the vulnerability with the highest CVSS ver. 3.1 base score; the highest active install count; and for reporting a group of components affected by the same vulnerability.
\n\n\n\nPatchstack can reward individual Patchstack Alliance members at their discretion based on the overall impact of the vulnerabilities they discover.
\n
Wordfence is taking a different approach in paying for every vulnerability reported within the scope identified by the program.
\n\n\n\nResearchers in the WordPress ecosystem should familiarize themselves with the various bug bounty programs and determine the best avenue for their disclosures. Some plugins and companies, such as Elementor, Brainstorm Force, Automattic, Castos, and WP Engine, have their own bug bounty programs, with a range of different payouts.
\n\n\n\n“We pay more per vulnerability and we pay for every valid vulnerability submitted,” Wordfence CEO Mark Maunder said. “We feel this is the only fair way to do it because gamification of a vulnerability program is like having employees who all work, but only those at the top of the leaderboard get paid. If you submit a valid vulnerability, you should get paid for your work.”
\n\n\n\nMaunder contends that the wrong incentives are driving down the quality of the research submitted.
\n\n\n\n“There are an extremely high number of low risk and low quality vulnerabilities being submitted to databases like Patchstack,” he said. “Vulnerabilities that involve a Cross-Site Request Forgery are an example of this. The incentives we are seeing out there encourage researchers to generate a a high volume of low risk vulnerabilities to get rewarded. These high numbers are then used to market security products.”
\n\n\n\nMaunder said Wordfence has structured its program around shifting the incentives to reward research into high risk vulnerabilities, instead of ramping up the marketing metrics for a particular vulnerability database.
\n\n\n\n“A high volume of low risk vulnerabilities in any particular database harms the industry because it creates work for other organizations who have to integrate this data, but for the most part it is useless noise that we are forced to sift through, rather than representing any real-world risk to the user community,” Maunder said.
\n\n\n\nPatchstack CEO Oliver Sild responded to these claims with data he says demonstrates that Wordfence is also responsible for producing a high volume of low risk vulnerability CVE’s.
\n\n\n\n“WordFence as a CNA actually produces lower risk vulnerability CVE’s in average compared to all 3 CNA’s in the WordPress space,” Sild said.
\n\n\n\nCVE’s with CVSS equal or higher than 5 (2023)
\n\n\n\nCVE’s with CVSS equal or higher than 7 (2023)
\n\n\n\nCVE’s with CVSS equal or higher than 8 (2023)
\n\n\n\nCVE’s with CVSS equal or higher than 9 (2023)
\n\n\n\n“WordFence does indeed on average assign highest % of CVSS 9+ CVE’s (though, they are also the smallest CNA of all three), but the high CVSS alone doesn’t determine wether the vulnerability will become exploited and the reality is that vulnerabilities that are being actively exploited in the WordPress ecosystem often have lower CVSS scores,” Sild said.
\n\n\n\n“Also, keep in mind that we at Patchstack have almost 2x higher volume of new vulnerability reports coming in (more than WPscan and WordFence combined), so obviously this also lowers the average for us on the edge scores.”
\n\n\n\nAs the newcomer to the group of WordPress companies offering bug bounties, Wordfence is entering the market with the intention of attracting more reports through additional bonuses (10% for the first 6 months) and a bonus structure that rewards chaining multiple vulnerabilities together, thorough documentation, and other extra efforts.
\n\n\n\nNot every author of a popular plugin or theme can afford to offer their own bug bounty program, and this is where security companies are stepping in to fill in the gaps. More competition across companies for high quality research can only be good for WordPress users, as it provides more incentive for securing the ecosystem and will potentially attract more skilled researchers. The bug bounty programs will likely evolve over time as companies refine them to provide the best value for original research.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Nov 2023 02:48:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:21;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"Do The Woo Community: The Challenges of Hosting Difficult Woo Sites Tom Fanelli and Ben Gabler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77947\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"https://dothewoo.io/the-challenges-of-hosting-difficult-woo-sites-tom-fanelli-and-ben-gabler/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:460:\"Guests Ben Gabler from Rocket.net and Tom Fanelli from Convesio talk scaling, plugins and coding standards when it comes to performance.
\n>> The post The Challenges of Hosting Difficult Woo Sites Tom Fanelli and Ben Gabler appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 13:15:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: WordPress 6.4.1 Fixes a Critical cURL/Requests Bug\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151163\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wptavern.com/wordpress-6-4-1-fixes-a-critical-curl-requests-bug\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4466:\"WordPress contributors have worked quickly over the past 24 hours to prepare a 6.4.1 maintenance release after a critical bug emerged from a change in the Requests library, causing problems with updates on servers running older versions of cURL.
\n\n\n\nHosting companies began reporting widespread impact of the bug. Tom Sommer, from one of Denmark’s largest hosting companies, filed a GitHub issue outlining how the cURL timeouts were affecting sites:
\n\n\n\nError: RuntimeException: Failed to get url \'https://api.wordpress.org/core/version-check/1.7/?locale=en_US\': cURL error 28: Operation timed out after 10000 milliseconds with 807 out of -1 bytes received.
REST API response: (http_request_failed) cURL error 28: Operation timed out after 10005 milliseconds with XXX out of XXX bytes received”
The issue became a top priority as it wasn’t clear how it would be possible for users to receive an update.
\n\n\n\n“Even if you fix this now the issue prevents any future auto-upgrade to a 6.4.1, since it breaks Curl requests, so the only way for people to update would be manually,” Sommer said. “The longer you wait, the bigger the problem will become.”
\n\n\n\nNexcess reported tens of thousands of sites being affected by the bug. The issue was beyond what most users would be able to manually patch on their own, relegating hosts to figure out how to update their customers.
\n\n\n\n“All my websites locked after updating to WordPress 6.4,” Javier Martín González reported. “The ones without updates are working normally.”
\n\n\n\nThe bug was also reported to be causing causing potential Stripe API, WP-Admin, and performance issues.
\n\n\n\nLiquid Web/Nexcess product manager Tiffany Bridge summarized how this problem emerged:
\n\n\n\n\n\n\n\n\nIt looks like:
\n\n\n\n\n
\n- Someone reported a bug having to do with an interaction between his Intrusion Protection System and WordPress
\n\n\n\n- They then submitted their own patch to WordPress
\n\n\n\n- The project lead for that area asked the submitter to write tests, which he did not do
\n\n\n\n- Then they merged the PR anyway, despite the lack of tests
\n\n\n\n- Meanwhile hosts are all going to have to revert that change ourselves on our own fleets so that our customers can still have little things like core and plugin updates if we are running an affected cURL version. (7.29 confirmed, there may be others)
\n
WordPress core contributors will have to get to the bottom of how this bug was allowed through, via a postmortem or other discussion to prevent this from happening on such a large scale in the future.
\n\n\n\nWordPress 6.4.1 updates the Requests library from version 2.0.8
to 2.0.9
. as a hotfix release to mitigate the issue. It reverts the problematic change. Version 6.4.1 also includes fixes for three other separate issues. Automatic updates shipped out this evening for anyone with sites that support automatic background updates.
WordPress’ Performance team is proposing merging Performant Translations into core in time for the upcoming WordPress 6.5 release. After an in-depth performance analysis earlier this year revealed that translations can significantly impact server response times, the team discussed various solutions and landed on one that requires no configuration from users. More than 2,000 WordPress sites have tested it through the Performant Translations feature plugin, after it was released in August.
\n\n\n\nPerformance Team contributor Pascal Birchler, who penned the proposal to merge the plugin into core, explained how it speeds up sites using translations:
\n\n\n\n\n\n\n\n\nPerformant Translations is powered by a new, lightweight i18n library that is faster at loading binary MO files and uses less memory. It even supports loading multiple locales at the same time, which makes locale switching faster. In addition to that, it supports translations contained in PHP files, avoiding a binary file format and leveraging OPCache if available. If an MO translation file has a corresponding PHP file, the latter will be loaded instead, making things even faster and use even less memory.
\n
Birchler also published some compelling benchmarks demonstrating the plugin’s ability to reduce memory usage and decrease load time:
\n\n\n\n\n\n\n\nLocale | Scenario | Memory Usage | Load Time |
---|---|---|---|
en_US | Default | 15 MB | 159 ms |
de_DE | Default | 29 MB | 217 ms |
de_DE | Performant Translations | 17 MB | 166 ms |
The Performance team has opened a ticket for merging the plugin into WordPress 6.5. Core committer Felix Arntz marked it as a high priority for the next release “due to the significant estimated impact this will have for localized sites’ performance.” The improvements stand to have a positive impact on the majority of WordPress sites (more than 50%) that are using translations.
\n\n\n\nWordPress 6.5 is expected in late March 2024. Getting merged this early in the release cycle would give Performant Translations the time it needs to be more widely tested and ready to go. Users who don’t want to wait until next year to get these reported performance improvements can install the plugin in the meantime.
\n\n\n\n“The Performant Translations plugin will continue to be maintained even after a core merge to build on top of the core solution with a distinct additional feature,” Birchler said. “As is already the case today, the plugin will automatically convert any MO files to PHP files if a PHP file does not currently exist. This is useful for sites where translations are not coming from translate.wordpress.org or only exist locally on that server.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 02:34:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"WordPress.org blog: WordPress 6.4.1 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16332\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2023/11/wordpress-6-4-1-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5868:\"This minor release features four bug fixes. You can review a summary of the maintenance updates in this release by reading the Release Candidate announcement or view the list of tickets on Trac.
\n\n\n\nWordPress 6.4.1 is a short-cycle release. If you have sites that support automatic background updates, the update process will begin automatically. If your site does not update automatically, you can also update from your Dashboard.
\n\n\n\nYou can download WordPress 6.4.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.
\n\n\n\nFor more information on this release, please visit the HelpHub site.
\n\n\n\nThis release was led by Aaron Jorbin and Tonya Mork. Thank you to everyone who tested the RC and 6.4.1, and raised reports.
\n\n\n\nWordPress 6.4.1 would not have been possible without the contributions of the following people. Their quick and concerted coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\n\n@afragen @clorith @desrosj @pbiron @schlessera @azaozz @davidbaumwald @tomsommer @nexflaszlo @howdy_mcgee @baxbridge @earnjam @timothyblynjacobs @johnbillion @flixos90 @joedolson @jeffpaul @zunaid321 @courane01 @audrasjb @tacoverdo @ironprogrammer @webcommsat @otto42 @barry @chanthaboune @rajinsharwar @aaroncampbell @peterwilsoncc @anandau14 @iandunn @matthewjho @coffee2code @boogah @jason_the_adams @joemcgill @johnjamesjacoby @jrf @renehermi @dlh @mukesh27 @sumitbagthariya16 @starbuck @sergeybiryukov @ravipatel
\n\n\n\nTo get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core channel. Need help? Check out the Core Contributor Handbook.
\n\n\n\nThanks to @jeffpaul and @webcommsat for proofreading.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 01:45:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:25;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"BuddyPress: BuddyPress 12.0.0-beta4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=331850\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"https://buddypress.org/2023/11/buddypress-12-0-0-beta4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3631:\"Hello BuddyPress contributors!
\n\n\n\nIf you haven’t tested our 3 previous beta releases, here’s a fresh opportunity to join the 28 contributors who helped build 12.0.0 so far. Whether you’re a new, regular or advanced user, a theme designer or a plugin author: we really need you to beta test our next major release, please contribute!
\n\n\n\n \n\n\n\n\n\n\n\n12.0.0 will introduce the BP Rewrites API overhauling the way that BuddyPress builds and parses URLs as well as a new community visibility feature. Learn more about these changes by reading the beta1 announcement post.
\n\n\n\n\n\n\n\nWe’ve fixed a dozen bugs and added new developer documentation pages explaining important changes introduced in 12.0.0:
\n\n\n\nWe also updated the 12.0.0 release schedule and delayed it a bit to make it as great as possible. It’s now slated to be released December 6. Please, help us meet this new deadline by testing 12.0.0 as thoroughly as possible .
\n\n\n\nYou can test BuddyPress 12.0.0-beta4 in 4 ways :
\n\n\n\nsvn co https://buddypress.svn.wordpress.org/trunk/
git clone git://buddypress.git.wordpress.org/
If you find something weird, please report it on BuddyPress Trac, post a reply to this support topic or get in touch with us on our WordPress.org Slack channel.
\n\n\n\nThanks in advance for your contributions
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 18:44:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"WPTavern: #98 – Marieke van de Rakt on Uniting the WordPress Community for a Stronger Future\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=151132\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wptavern.com/podcast/98-marieke-van-de-rakt-on-uniting-the-wordpress-community-for-a-stronger-future\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:47833:\"Transcript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.
\n\n\n\nJukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case, how the WordPress community can stay United.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast, player of choice. Or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you, and hopefully get you, or your idea, featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox and use the form there.
\n\n\n\nSo on the podcast today, we have Marieke van de Rakt. Marieke was one of the co-founders of Yoast. She left Yoast entirely in May 2023, and is now focusing her energy on her investment company, Emilia Capital, together with Joost de Valk. This is investing in various WordPress brands and ventures.
\n\n\n\nMarieke shares her insights on the current state of the WordPress community and the challenges it faces. She highlights the growing divide between those who prioritize community orientated contributions, and those purely driven by commercial interests. She expresses her concerns about the potential consequences if this division continues to widen, including the potential growth of other content management systems.
\n\n\n\nThis issue is certainly worthy of attention, and whilst it might seem that the two sides of this debate irreconcilable, Marieke offers potential solutions to these challenges. She emphasizes the need for the WordPress community to unite and compete against other proprietary platforms. She suggests a more cohesive marketing strategy and collaboration to strengthen the community. She advocates for an official recognition system to celebrate and promote companies actively contributing to WordPress. Although what this might look like is very much up for debate.
\n\n\n\nWe also hear about Marieke’s experiences at Yoast, and how they contributed to WordPress over the years, particularly during the development of Gutenberg. She discusses the importance of open source collaboration and the need for companies to align with the project’s direction, for the benefit of the wider community.
\n\n\n\nWe also discussed the potential negative outcomes if WordPress becomes more commercialized, leading to a divide in the community, a divide which might be difficult to undo.
\n\n\n\nWe end by chatting about the importance of WordPress in democratizing publishing, it’s benefits for the internet and the planet, and how, from Marieke’s point of view, WordPress is too important to fail.
\n\n\n\nIf you’re keen to see the WordPress community grow, and have an interest in how internal divisions can be avoided and resolved, this episode is for you.
\n\n\n\nIf you’re interested in finding out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast, where you’ll find all the other episodes.
\n\n\n\nAnd so without further delay, I bring you Marieke van de Rakt.
\n\n\n\nI am joined on the podcast today by Marieke van de Rakt. Hello.
\n\n\n\n[00:04:06] Marieke van de Rakt: Hello! Very nice to be here.
\n\n\n\n[00:04:08] Nathan Wrigley: Did I get your name vaguely right?
\n\n\n\n[00:04:11] Marieke van de Rakt: I think you did a really good job. It sounded a bit like I’m a Viking, so a bit more Scandinavian but it was correct. Yeah.
\n\n\n\n[00:04:20] Nathan Wrigley: I will take that. If you don’t know Marieke, honestly where have you been for the last couple of decades? Marieke was the driving force, along with her husband, of a very, very famous WordPress company, Yoast. Things have changed in the last year or so. So I wonder, for the purposes of this podcast, which is obviously a WordPress based podcast. I know it’s a bit of an uninteresting question perhaps, but for those people who don’t know who you are, could you just give us your potted history, your biography, if you like?
\n\n\n\n[00:04:47] Marieke van de Rakt: My biography, yes of course. So I am Marieke, Marieke van de Rakt. I am, I don’t know what I am, I am an entrepreneur and an investor now. So we’ve been running Yoast since, I’ve been with the company I think since 2013, so about 10 years. And then in 2021 we sold to Newfold Digital. And then like you just said, I left Yoast I think in May of this year.
\n\n\n\nBut before leaving, we already started investing in a number of WordPress brands, so Atarim, Equalize Digital, a Dutch company called wildcloud, really, really good. Also, outside the WordPress space, we have some investments and we’re now helping those investments grow. And we’re also having some new ideas of products and things we can do in the WordPress world. So we’ll stay in the community forever.
\n\n\n\n[00:05:37] Nathan Wrigley: Oh nice. That’s great. Do you feel like your foot has come off the pedal since May, or has your foot gone on the pedal since May? Are you busier than ever or, do you have a little bit more free time for the things that you enjoy outside of work?
\n\n\n\n[00:05:50] Marieke van de Rakt: I do think that I have a little bit more time, but I’m also full with ideas. I have to be very careful because I wanted to work for four days a week, but I’m already working five again. But that’s all things that I like. So I think it’s better and it’s less stressful than it used to be, because I don’t have to lead a team. We do have a small team now, but it’s only three or four people, and I know them very well so they’re not difficult people. It’s easier than it used to be.
\n\n\n\n[00:06:18] Nathan Wrigley: Well that’s good to hear. The reason that we’ve got you on the podcast today is not to talk about any of those things, but I think it was important to paint the picture of who you are and how long been in the WordPress space. Because what we’re talking about, I guess requires a fairly large telescope, staring into the history of WordPress. Because without that backstory, without that familiarity with the community over decades basically, then you wouldn’t really have the authority to write this.
\n\n\n\nBut I’m going to point listeners to this podcast to a poststatus.com post which Marieke wrote. It was on the 28th of September, so Google could be a friend here. And it was called Two Worlds of WordPress. Now just to paraphrase it, you could obviously do that, but I’ll just give it a go. Essentially, in that piece you were talking about the fact that, over the years, WordPress has grown in two seemingly contradictory directions.
\n\n\n\nOn the one hand, well you’ve called them different sides, different faces. On the one hand, you’ve got the community side. So the people who are in, as you describe it, enthusiastic about open source, contributing to the project and the events and all of that.
\n\n\n\nAnd then on the other side, you’ve got the people who are business orientated, and in the back of their minds is using WordPress as a commercial vehicle, a way to generate revenue.
\n\n\n\nNow over the course of WordPress’s history, the relationship of those two things has changed. And I feel that decades ago it was really clear that WordPress was much more community and much less business. But over the last decade or so it’s grown more and more business orientated. And your fear is that these two camps, these two faces, different sides, they’re growing apart to the point where they can’t even see what the other side is doing. There’s no point of communication between them. And in a way it’s tearing the community apart. Is that a fair summation of it?
\n\n\n\n[00:08:08] Marieke van de Rakt: Yeah I think so. That’s what I’m afraid of. Because I think both worlds have a necessity to exist. So because the business side of WordPress grew so quickly, it also meant that there was a lot of opportunity for people to make money out of WordPress.
\n\n\n\nSo we did that all together. But it’s an open source project. So we need people to contribute to it, otherwise we’ll lose our momentum and we’ll lose the fact that we are the biggest CMS out there. So what we ideally want is that all of those businesses that make money out of WordPress also pay something back to the community. And that’s not always happening. And I know that a lot of businesses are struggling because they don’t know how and then that is hard, but that’s what I’m worried about, yeah.
\n\n\n\n[00:08:53] Nathan Wrigley: Do you have some sort of intuition? Is there some sort of feeling that you get when you are dealing with these different sides? So as an example, when you turn up to a WordPress event and you meet somebody who is just purely in it for the contributing value of it. Do you have a different relationship with those people than you do with the people who have a only a commercial side to it? I just wonder if you’ve got any intuitions as to, do any alarm bells go off, or is there anything different about the way you deal with those different sides?
\n\n\n\n[00:09:22] Marieke van de Rakt: Yes. I think if you meet that kind of contributor that’s only in there for the open source, that’s a hero. That’s nothing short of a hero, because he’s there for something bigger than himself. He’s there to contribute to something that is bigger. And the business side, if you’re only in it for the business side, I’m always a little bit on edge. So I think that you shouldn’t do that.
\n\n\n\nBut I also think that we should reward businesses that are giving back more. And it’s very hard to be a business that gives back and gives back and gives back, and doesn’t really get anything in return. So I know this Dutch company, we can name them, Level Level. But it’s not, especially in the Netherlands, it’s not for them immediately, that doesn’t pay them anything else except for we’re the experts.
\n\n\n\nBut perhaps if we, as the WordPress world, also shout about, but they’re the experts, they’re on every WordCamp in the Netherlands, they’re on WordCamp Europe, they come there with their entire people, all the people that work there, their team.
\n\n\n\nMaybe those companies need a bigger shout out because they’re the ones that do contribute and, I don’t know, that could be some sort of solution. That we celebrate those people and companies that dedicate a lot of their time towards WordPress.
\n\n\n\n[00:10:39] Nathan Wrigley: The fact that you’ve written this article, at least the implication of it is that you fear that in the future, if the current trajectory carries on, there’s going to be a moment where things break irrevocably. So the two sides grow so far apart that they genuinely have no point of reference to each other anymore.
\n\n\n\nAnd really the philanthropic effort of WordPress would be lost somewhere in that. The whole project would fail. I can imagine a scenario where people, contributors who are just in it for pushing the WordPress project forward, they might have a chip on their shoulder saying, well you know, there’s all those people over there making millions of dollars for their company. I’m not making anything out of it, so I’m not going bother.
\n\n\n\nAnd then the other side, well we make millions of dollars out of this project. Why would we want to waste our time contributing to it? And you just get this echo chamber. One side chatting and confirming their own confirmation bias over here, and the other side doing the exact same but in their little echo chamber.
\n\n\n\nSo is that a fear? That you think that it literally will get to the point where the project itself is broken, because there is no, in air quotes, community anymore.
\n\n\n\n[00:11:44] Marieke van de Rakt: I think then other CMSs will grow, because of our division between those two worlds, will make a smaller and other CMSs will grow. Because, well, we care about open source, a lot of people don’t, and they don’t choose WordPress just because it’s open source. They choose WordPress because it used to be the best. I don’t know if it’s the best anymore but it used to be the best. So if we look at marketing, all these big companies, so the big hosts, all market their own brand. So GoDaddy markets for GoDaddy. Bluehost markets for Bluehost. SiteGround markets for SiteGround.
\n\n\n\nBut they all do WordPress. So perhaps we should also market WordPress as a system more, we don’t do that. They’re competing with each other, and they’re competing with companies like Wix and Shopify. But I think as a whole of the WordPress community we should be competing with each other against Shopify and Wix. And we don’t do that enough. We should join forces more. Also on the business side of things.
\n\n\n\n[00:12:45] Nathan Wrigley: I think that’s really interesting because, I think only people who are deeply into WordPress in the same way that you and I both are, you know, we probably think about WordPress more than is healthy for us.
\n\n\n\nBut we’re really obsessed by it, so we go out searching for the news and we look for the companies that are, in air quotes, doing the right thing. Until we read the posts that come out on an annual basis saying who has contributed, which companies have contributed and so on. But most people using WordPress probably won’t have any idea about that because it’s not really applauded publicly, is it?
\n\n\n\nI think we should probably call out Yoast at the moment and discuss what you decided to do, because that was a really good example. So we’re recording this in October 2023, obviously caveat emptor, I don’t know what will happen in the future in terms of WordPress’s contribution. But what was your stated goal? How did you want to commit time within the company, resources within the company? Because obviously that would be a model that you think worked quite well.
\n\n\n\n[00:13:44] Marieke van de Rakt: We have the Five for the Future working quite well. At Yoast we did that before that even was a thing. But I remember, and this was WordCamp Europe, the first one in 2013, yes it was in 2013 in Leiden. And Yoast did a talk and I prepared that talk. It was about open source and about how it’s okay to make money out of it.
\n\n\n\nAnd that was this huge thing. People were, no you’re not allowed to make money out of. We were allowed to make money out of themes, because they were all unique and you wanted to be unique. But on plugins, everybody needed a plugin, it was frowned upon. But we, or Yoast back then, had I think 2,000,000 installs, and you get so many questions off people. You can’t maintain a plugin and make sure it’s secure, and come up with new features and test that, that’s impossible to do without making money.
\n\n\n\nSo we started out, I think we were the first to start out with a freemium model thing, and that was frowned upon for a few years. And then everybody started doing that, and they went much further than we did. So we first were very reluctant to go to that you buy something and that’s an immediately you buy it for a couple of years, unless you actively say no I don’t want it anymore, you have to call out. We just gave you for one year and then you have to manually renew because we didn’t want anybody to feel like, oh no I’m stuck to it.
\n\n\n\nThis all changed but we were reluctant in that kind of way. And we saw that we were just. So we weren’t perhaps the first most commercial, but then so many companies came in, mostly outside of the WordPress world who did it differently.
\n\n\n\nAnd at the end when we sold Yoast I felt really naive because I got a little peek of what it’s like to be on the really business side after we sold Yoast. We didn’t know, we didn’t know that there were all kinds of meetings and people making deals about who installs what, and we didn’t do that at Yoast, we just built the best product and contributed a lot to WordPress. Part because we believed in it, but also part because it just makes sense.
\n\n\n\nWhen Gutenberg was announced, that was a major implication for the Yoast plugin. We had to be involved otherwise it would have been really bad for our product. So that’s something. Even if you’re not like a WordPress enthusiastic like we are, just because it will allow you to see where the project is going, that’s a good reason to contribute, that alone. So it also makes business sense to do that.
\n\n\n\n[00:16:19] Nathan Wrigley: Yeah so, what specifically was the sort of, the things that you did in Yoast? What were the boots that you put on the ground, the hours that you allocated? Now it may be that it was a movable feast and that each year was different, but broadly speaking, typically, what was the kind of commitment that you were prepared to make? That could be in terms of hours, finance, whatever, however you want to take it.
\n\n\n\n[00:16:41] Marieke van de Rakt: So I think Joost personally did a day a week for ages. And we had entire teams, community teams that did nothing else than sponsoring WordCamps, organising WordCamps, those kinds of stuff. And then we had a few during Gutenberg, we had, I think two full time developers on it.
\n\n\n\nAnd afterwards we, Yoast still has, a core contributor team. So there were like four or five contributors that worked solely on the project. I think Yoast did a little over 5% in terms of hours and money, but not even that much. In the beginning it was, I think in the beginning we did 20% but when we grew bigger, I think 5% to 10%, you can do a lot with 5% to 10% of a bigger company.
\n\n\n\n[00:17:24] Nathan Wrigley: First of all, the reason you’re doing all of this, my guess is it wasn’t to be recognised publicly. That would be nice, but that wasn’t the primary motive. It was to foster a good relationship with the community to promote the whole project itself.
\n\n\n\nBut there must be some side of that equation where you’re thinking, we’re putting all this time in, there seems to be a lot of companies out in the space who are probably more profitable than us, who are not putting an equal amount of time in, and we don’t seem to be getting much in the way of recognition.
\n\n\n\nSo really what I’m asking is, did you feel that the recognition piece was something that was lacking? Maybe something that ought to be considered in the future, some sort of an an official badge, some way of displaying, look this company did this categorically, we’re very proud of them. Let’s just talk about recognition.
\n\n\n\n[00:18:17] Marieke van de Rakt: Within the core of the WordPress community we were recognised, people saw that. So that’s good. But outside of that first bubble people have no idea. And then a WordPress stamp of approval, and I don’t know how you should come up with some things. Oh also a company like Level Level who does a lot, if they get a WordPress stamp of approval that would help them so much with selling websites because they build websites.
\n\n\n\nIf we would have a WordPress stamp of approval, not even this is the best SEO plugin for Yoast, but this is they contribute to WordPress, they have their things in order, that would help a lot.
\n\n\n\nBut we don’t have something like that, and I don’t know how to set something like that up. But I do think that would help. Because we really believed in the open source thought. So not even I like WordPress, but the fact that you can build something together, and you don’t have to come up with an, event the wheel over and over again, that just makes sense for whole world.
\n\n\n\nSo I’m a strong believer in open source and in working together without having all these, I don’t know, without talking about, this is mine and you shouldn’t have this. That’s just a bad way of running the world. So I think that’s something we strongly believe in.
\n\n\n\n[00:19:34] Nathan Wrigley: I think having some sort of accreditation system, the merits of that would be good, but I can equally see how the actual organisation of that would be fraught with problems. Because no doubt there’d be companies who, I don’t know, just didn’t quite get out of that accreditation what they were hoping for, and yet they’d clearly put in some time. And so you’d have to have bodies on the ground making sure that accreditation was fair and meritorious and everybody got what they deserved.
\n\n\n\nSo that does seem like a bit of a minefield to go down. But then the project prioritizes all sorts of things that don’t have a profit motive, and maybe something like that, an accreditation system could be something worthwhile.
\n\n\n\nIt just occurs to me that if I go around WordPress company websites, you don’t see that, do you? You don’t see them shouting on the hero section of their web page, we have contributed such and such an amount of hours. It’s all about the product that they’ve got because they’re selling directly to end, you know, end users.
\n\n\n\n[00:20:33] Marieke van de Rakt: And they don’t understand that. But I think as a community, we should make people more aware. It’s like buying or working with open source software is like being a vegetarian, you’re just doing the right thing. So we should talk about that more, because it’s the only way I think we can move forward, and come up with new knowledge, everybody should do open source.
\n\n\n\nSo every government website should be made out of open source software. It can be really, get mad if they spend money on proprietary systems. They should spend money on, I don’t know, health and education and don’t spend it on a very expensive software, because there’s software that’s really good and we should use that. But I think as a community, perhaps we should talk more about why open source is so awesome.
\n\n\n\n[00:21:18] Nathan Wrigley: Yeah it really is tricky, but I have this intuition that something like this would be a good idea, despite the fact that it would be almost impossible I think to manage, and it would be very difficult to decide who got what.
\n\n\n\nBut in your conversations over the years working at Yoast, okay let’s imagine that there’s somebody listening to this podcast who desperately wants to contribute, but feels that they don’t have the bandwidth to do that. They’re not profitable enough, they don’t have enough hours to make that possible. So this question is directed to you but talking to them, if you know what I mean.
\n\n\n\nSo when you were working at Yoast, did you get an impression that your contributions to the project led to you being profitable? Were there certain customers of yours who came to you because you were working so hard for the project as a whole, and not just because you had a superior product?
\n\n\n\n[00:22:12] Marieke van de Rakt: Not directly, but I’m convinced that indirectly, yes. So being on all those events, having Taco, having Taco just being everywhere and organising, and talking to people helps with getting those core community people talking about you. And when they talk about you to all the other people, it just, it’s like a pyramid that goes down.
\n\n\n\nSo we never did any influencer marketing, we did WordPress contribution. And I think it’s about the same thing, because you just show up at contributor days or at events and you talk to people. And when you do those kinds of things, you also talk about your product and people think you are nice because you’re helping. Not everybody thinks you’re nice, so you always have that.
\n\n\n\nBut I think that’s just WordPress influencer marketing. I even say that to people we invest in. I said, you should do WordPress influencer marketing. That means contributing to the project and doing your best. And that’s the way the people in the community will get to know you and see you, and they’ll also talk about your product then.
\n\n\n\n[00:23:20] Nathan Wrigley: Yeah, there’s no direct correlation between the amount that you put in and the success, if you like, of the commercial side at least of the plugin. But there is some sort of fuzzy appreciation on your behalf, that there is a connection even though you can’t quite grab hold of what that is.
\n\n\n\nBut the more that you put in, the more recognition you’ve got, the more the brand became known and probably the by product of that is that there would be sales from that. I should point out that Marieke isn’t just doing this one piece, we’ve talked about this two worlds of WordPress piece. It’s going to be a regular feature on Post Status.
\n\n\n\n[00:23:54] Marieke van de Rakt: Yeah. So I’m just telling stories from both worlds and sometimes, well no, there’s always one side, sometimes two, that I think, I hope, that’ll help to get those worlds to understand each other. That’s the only thing I hope.
\n\n\n\n[00:24:10] Nathan Wrigley: The broad overarching idea behind all of the posts that you’re going to be putting on Post Status is about getting the commercial side and the non commercial side, to get them talking a bit more. And to get, because obviously, Post Status has this enormous reach and that would be a really superb place to do it.
\n\n\n\nOne of the pieces that you wrote was called, On people breaking up with WordPress. And I’m sure I don’t need to explain to everybody what that means, but you can guess. It was all about how people decide that they want to move away from the project.
\n\n\n\nBut one of the things that you wrote in there, I’m curious as to how this fits with everything that you’ve just been talking about. You wrote, and I’m going to quote, I strongly believe that all contributors, so developers, marketers, organisers, et cetera, to the WordPress project, need to be financially compensated. Next to that, I think it would help if they feel valued and important, and that they’ll be able to be productive.
\n\n\n\nLet’s talk about the first bit, the financial compensation, because I don’t think anybody would disagree with that, would they? Everybody would love to think that, you know, you contribute something to WordPress, you’ve got something, you get return, you put an hour in, you get some finance back.
\n\n\n\nHow do you see that working in reality? Especially if you’re, I don’t know, you’re working for a plugin company, let’s say, and there’s not a lot of money sloshing around, you’ve got very little reserves. How would you like to see this happen? Are you talking about like a pool that big companies who are successful put money into, and then if you like that can be dipped into by people from around the community. What were you thinking there?
\n\n\n\n[00:25:44] Marieke van de Rakt: That would be best. I think the most money in the WordPress world is made by hosting companies. So they have large margins. If they don’t want to hire people themselves then they should invest in people that want to contribute their time. And I think in the beginning of WordPress it was led by volunteers, but I do think that nowadays there is so much money being made that we should be able, together with all of us, to at least compensate for those hours that put in.
\n\n\n\nAnd that’s probably not the highest salary but people should be compensated a little. And I know still that there are main organisers for WordCamps that do that entirely in their free time. And I think that’s just wrong. There’s too much money being made by big companies, and they should pitch in together to make sure that the events are led by people that are also paid for their contributions.
\n\n\n\n[00:26:43] Nathan Wrigley: That seems like a really credible way of short circuiting the accreditation thing that we were talking about earlier. We can prove categorically that we committed 5 percent of something. Whether that’s 5 percent of time across our employee distribution. Or whether that’s 5 percent of the finance that we had available to us in this year.
\n\n\n\nAnd we’re talking about this 5 percent because, I don’t know if you know dear listener, there is this concept of Five for the Future where exactly this would happen. But there’s no way of demonstrating to the world that you did it.
\n\n\n\nSo just that simple metric of, we did and we’ve certified that we did Five for the Future, maybe that alone would be a fairly, it’s a fairly blunt instrument, but at least it would be some way of the company’s getting that recognition back. The badge could go on the website, so that people who are into the community could fully understand, okay, there it is. They did their 5 percent contribution for whatever it was. That might be a fairly swift and easy way, well not easy, but a fairly quick way of doing it.
\n\n\n\n[00:27:44] Marieke van de Rakt: It could also be a way of getting those worlds together. I think that’s the start. I just think there’s too much money being made by big companies to have people volunteer and have a hard time. If you’re an organiser of a big WordCamp, which is like WordCamp Europe is extremely important that it exists for businesses. Those businesses should also be like, I have to make sure that this continues.
\n\n\n\nAnd that means that those people need to be compensated because they are usually working for themselves. But if you build websites and you organise an event, you probably build less websites if you’re like busy organising WordCamp Europe. I think the WordPress world has been, we used to do it with all volunteers and I don’t think that we can do this anymore.
\n\n\n\n[00:28:30] Nathan Wrigley: When an event like WordCamp Europe is put on, the level of commitment from some, again it could be any WordCamp, but I just pluck WordCamp Europe out of thin air. Because, well it’s so big and because of that there’s so many technicalities. And having interviewed quite a few of the people who were really involved in those projects, they are genuinely giving up weeks and weeks of their year. And they’re doing it out of the goodness of their heart.
\n\n\n\nNow in some cases it may be that they’ve got some kind of sponsorship somewhere, maybe their company has allowed them to have that time. But I have a strong intuition that many of them are literally taking it almost like annual leave.
\n\n\n\nAnd so it’s exactly what you said. It’s not just that they’re committing time, but they are committing time which they can’t get back in their own business. So it’s a double whammy. They’re not getting paid for that contribution, but also they’re losing money so it’s going wrong in both directions.
\n\n\n\nI don’t know how that would work, but it does strike me that badge, that 5 percent commitment being pulled somewhere, some independent organisation which could then give that out seems like a good idea.
\n\n\n\nIf we’re going to accredit people, now this could be controversial, if we’re going to credit people, do we go the other way? Do we go in the direction of calling out companies that don’t do it? Is that something which the community should ever be involved in? My intuition says no, but that’s just my intuition, what do you think?
\n\n\n\n[00:29:54] Marieke van de Rakt: My intuition also says no, because it’s a very negative thing to do. And it’s hard as well because, especially like in the plugin businesses you know, but in the website builder businesses, a lot of websites builders will not even know about Five for the Future or anything like that. I wouldn’t call people out on not contributing but perhaps other people will.
\n\n\n\n[00:30:17] Nathan Wrigley: I’m sure they will, because people who are not bound to any particular company, they might have stronger feelings about that and they can do that in their own way, can’t they? So really we’re painting a picture of, if you do the right thing there should be a mechanism for you to be able to certify that you have done the right thing, and have some sort of badge of honor to be able to display that and explain.
\n\n\n\nWhat are your feelings about how you feel this conversation is going to be received? Because we’re having this, we’ve had a little bit of a chat beforehand, and we exchanged a few messages and so on and so we knew what we were talking about. But somebody listening to this for the first time, it may be difficult to hear this conversation because it’s a, you know, it’s the trusted community, it’s the thing that we love and here we are suggesting that potentially money has to be involved. What would you say to those people who don’t want money to have anything to do with their WordPress experience?
\n\n\n\n[00:31:08] Marieke van de Rakt: I love those people just because I think their heart is in the right place. But I also feel like it’s not fair to those people because there’s so much money being made by those big companies, so everybody should be compensated or should grow from that.
\n\n\n\nI just think, I know I’ve had conversations in the past in which people said it should be true volunteers, and not even compensated by the company you work for, it should only be volunteers. I think it’s just not fair to those people, that they’re doing the big chunk of work. Especially if it’s organising, like a day volunteering is different to me than organising an event out of your free time.
\n\n\n\nYou’re organising something that’s of massive importance to those big companies, because they see each other there and they set up deals together, business deals. So they really need that event. They need the organisers to be in space. Those people just deserve to be compensated.
\n\n\n\nI love everybody who says that they want to do it for free, but I also think that’s not fair to them, and to their work. It’s not playing around anymore, these are like really big events. The first WordCamp Europe was 650 people, but we’re now talking about 3,000, I don’t know, 4,000 people. That’s a different league. We’re playing in a different league now.
\n\n\n\n[00:32:28] Nathan Wrigley: Yeah. I guess the rules of engagement change, don’t they? If you’ve ever been to a non WordPress event, so a more commercial event, you might have sympathy from what I’m about to say. They really do feel different, just the whole purpose of standing in that space is the economics of it. You are there to pitch your product, and that is the bottom line.
\n\n\n\nAnd if you haven’t been to a WordPress event, firstly, can I encourage you to go because you’ll probably make some great friends as much as anything else. But you don’t get that feeling, you get the feeling that it still has that community vibe to it. There are still oodles of people milling about who aren’t on the commercial side.
\n\n\n\nBut I wonder, with the people who are just in it for the commercial side, have they already gone too far? What is the road back, if you like, I’m going to say it that way. What’s the road back for these people? Where would you encourage them to go? Who would you encourage them to talk to? Which projects would you point them in the direction of?
\n\n\n\nIf somebody listening to this, their spidey sense has gone, oh hang on a minute what Marieke is saying makes sense. We’re on the commercial side, we don’t really have much in the way of the community side. How can we begin that journey? Where would you go? Where would you point them?
\n\n\n\n[00:33:43] Marieke van de Rakt: That’s hard, because I know there are companies that want to do something and don’t know. So perhaps that’s something we should be setting up, that people who are now contributing but are not being compensated for the hours, that they can somewhere say, hello. And then companies that want to compensate somebody, or sponsor somebody, can find each other. I don’t know if there’s something like that. Michelle Frechette should put up a website about that.
\n\n\n\n[00:34:07] Nathan Wrigley: We do have something called the WPCC, which might cover a little bit of this ground. It’s the WP Community Collective, and I will put that in the show notes. They have the opportunity for you to contribute financially to projects that have been decided upon already.
\n\n\n\nAs an example, I can’t remember what they call them, bursaries or something like that. You contribute to that and then if the goal is reached then that particular bit, it might be accessibility or it might be something else, that bit will happen.
\n\n\n\nBut it’s not quite the, it’s not really the place, essentially what you’re doing there is contributing your finance, which is great but it’s not really getting you inside of the community, is it? So I don’t know if such a thing exists.
\n\n\n\n[00:34:48] Marieke van de Rakt: Come to a WordCamp, come to a contributor day, that’ll help. I think then you’ll at least see, I didn’t understand anything on my first contributer day, but I know now the onboarding is better than when I started. And talk to people and see what you can do.
\n\n\n\nAnd I think if you’re profitable. Financial, there’s a lot to help. So that’s a very good first start, and perhaps then you work with someone and can see what you could do too yourself.
\n\n\n\nI’m always reluctant to be an organiser because I’m afraid that I’ll get in fights with everybody. It’s just true. I just want certain things a certain way, so I’m not going to do that. But I now know that my colleague, which works with our new company, she said, I would like to do that. So now I’m like, oh that’s great, we’ll sponsor your time and you can do that. And nobody ever gets mad at her because she’s really sweet.
\n\n\n\n[00:35:41] Nathan Wrigley: There is an option that none of this happens, and the whole thing goes pear shaped. That the enterprise of WordPress becomes more and more commercial, we just sort of put up with it, and eventually the community does just reach this point where the two sides can’t talk to each other, and so therefore, really the whole enterprise has fizzled out and gone away.
\n\n\n\nThat feels like a real shame. It does feel like the promise of something like WordPress, to democratise publishing. I know it’s easy to say those words, but the fact that you and I both have, no matter how much money is in our pocket, we have the capacity to go somewhere, and so long as we’ve got access to the internet, we can download that software and we can publish whatever we like, whenever we like, to whomever we like.
\n\n\n\nIt’s too precious of a thing to allow to just disappear, because we can’t be bothered to figure out solutions like this. That would such a shame if that happened.
\n\n\n\n[00:36:37] Marieke van de Rakt: Yeah I think we agree here. I also think that would be bad for the planet. So it would be bad for the community. But I also believe that the world is better if WordPress is bigger, because of the fact that a lot of people are in there to make the best software, and to build accessible software and to make sure that it’s, I don’t know, it’s really democratising publishing. So it would be a bad thing for the internet if WordPress would not flourish.
\n\n\n\n[00:37:04] Nathan Wrigley: Yeah, I think we can see all over the internet examples where proprietary, privately owned platforms, the incentives for those platforms to exist, it doesn’t take too many years for all sorts of bad incentives to creep in, and all of a sudden you notice that you’re being advertised all sorts of things, and your feed is being filled up with all sorts of things that potentially are good for the company behind that, but not necessarily great for you.
\n\n\n\nThat really isn’t the internet that probably anybody realistically wants. It might be free and it might be on a gigantic global scale, but maybe it’s not in everybody’s best interest. So let’s hope that we don’t have the calamity that we have just described. I have this feeling that in some way we will figure out these wrinkles, but I share your concern that now is probably the time to tackle them and not let this problem get too far.
\n\n\n\nBefore we hit record, we talked about this and we said that, really, we’re not in the game today of offering up any answers. We were just in the business of airing it, and stirring up this debate and seeing what came out.
\n\n\n\n[00:38:11] Marieke van de Rakt: Other people can come up with the answers.
\n\n\n\n[00:38:14] Nathan Wrigley: But that’s important. It’s true, isn’t it? Neither you nor I have the perfect solution. We’ve come up with a few things on the fly here today. But it would be good if anybody who had any intuitions around this, who had some novel idea that maybe nobody else has had before. Maybe you’ve tried something out in your company that you thought worked and would spread more globally. If somebody wanted to contact you, Marieke, where these days is the best place to keep this conversation going?
\n\n\n\n[00:38:42] Marieke van de Rakt: I’m on Twitter but it’s not called, no it’s called X now. I think that’s the best way get in touch. I’m not very active on Twitter but I do read it. So if you send me something there i’ll read it.
\n\n\n\n[00:38:54] Nathan Wrigley: And the fact you’re writing these posts every week, this is something which is dear to your heart. This isn’t a flash in the pan thing for you. You’re going to keep banging this drum in the days, weeks and months to come, right?
\n\n\n\n[00:39:04] Marieke van de Rakt: Yeah, I’m going to be talking about these kinds of issues and I hope that that’ll get the conversation started. People thinking about it, that would be good. And then we have a lot of new events coming up, I think, and then we’ll figure it out. I know there are a lot of people working on the same things, trying to solve the same problems.
\n\n\n\nI also think WordPress is too big to fall apart all of a sudden. So we’ll figure it out. I’m also hopeful, I’m an optimist.
\n\n\n\n[00:39:34] Nathan Wrigley: Marieke van de Rakt, thank you so much for chatting to me on the podcast today. I appreciate it.
\n\n\n\n[00:39:40] Marieke van de Rakt: Thank you. I had a good time.
\nOn the podcast today we have Marieke van de Rakt.
\n\n\n\nMarieke was one of the co-founders of Yoast. She left Yoast entirely in May 2023 and is now focussing her energy on her investment company Emilia Capital (together with Joost de Valk). This is investing in various WordPress brands and ventures.
\n\n\n\nMarieke shares her insights on the current state of the WordPress community and the challenges it faces. She highlights the growing divide between those who prioritise community-oriented contributions and those driven purely by commercial interests. She expresses her concerns about the potential consequences if this division continues to widen, including the potential growth of other content management systems.
\n\n\n\nThis issue is certainly worthy of attention, and whilst it might seem that the two sides of this debate are irreconcilable, Marieke offers potential solutions to these challenges. She emphasises the need for the WordPress community to unite and compete against other proprietary platforms. She suggests a more cohesive marketing strategy and collaboration to strengthen the community. She advocates for an official recognition system to celebrate and promote companies actively contributing to WordPress, although what that might look like is very much up for debate.
\n\n\n\nWe also hear about Marieke’s experiences at Yoast and how they contributed to WordPress over the years, particularly during the development of Gutenberg. She discusses the importance of open-source collaboration and the need for companies to align with the project’s direction for the benefit of the wider community.
\n\n\n\nWe also discuss the potential negative outcomes if WordPress becomes more commercialised, leading to a divide in the community, a divide which might be difficult to undo.
\n\n\n\nWe end by chatting about the importance of WordPress in democratising publishing, its benefits for the internet and the planet, and how, from Marieke’s point of view, WordPress is too important to fail.
\n\n\n\nIf you’re keen to see the WordPress community grow, and have an interest in how internal divisions can be avoided and resolved, this episode is for you.
\n\n\n\nOn people breaking up with WordPress
\n\n\n\nWordPress Community Collective
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 15:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:27;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"Do The Woo Community: New Woo BizChat Hosts Emma and Adam Dive into Black Friday\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77931\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://dothewoo.io/woocommerce-wordpress-sales-black-friday-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:399:\"Join our new hosts Emma Young and Adam Weeks for a great conversation and insights into doing sales on Black Friday.
\n>> The post New Woo BizChat Hosts Emma and Adam Dive into Black Friday appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 10:38:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:28;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:125:\"WPTavern: WordPress 6.4 Introduces Twenty Twenty-Four Theme, Adds Lightbox, Block Hooks, and Improvements Across Design Tools\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151068\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:133:\"https://wptavern.com/wordpress-6-4-introduces-twenty-twenty-four-theme-adds-lightbox-block-hooks-and-improvements-across-design-tools\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5852:\"WordPress 6.4 “Shirley” was released today, named for famed American jazz pianist and singer Shirley Horn. This release introduces a new batch of writing and design tools that give users more powerful customization capabilities inside the editor. We covered most of the changes as they were released in the Gutenberg plugin and added to core, but here are a few of the highlights.
\n\n\n\nWordPress now has core support for loading images in a lightbox. It’s a simple, yet elegant “expand on click” feature that allows visitors to expand images to be full-screen without leaving the page. The lightbox can be enabled on a per-image basis or site-wide under Styles » Blocks » Images.
\n\n\n\n\n\n\n\n\n\n\n\nThe Command Palette has gotten a design refresh in 6.4 in order to accommodate a growing catalog of commands available to help users perform tasks more efficiently. Users can access the tool inside the Site Editor and the Post Editor alike, with specific contextual command options for saving time across both editing experiences.
\n\n\n\n\n\n\n\n\n\n\n\nimage credit: WordPress 6.4 release page\n\n\n\nThe List View continues to get improvements to make it more useful for getting a condensed overview of the content at a glance. WordPress 6.4 adds media previews for the Gallery and Image blocks in the List View. It also allows users to assign custom names for Group blocks, which are visible in the List View so they can be easily organized.
\n\n\n\n\n\n\n\nimage credit: WordPress 6.4 release post\n\n\n\nBlock Hooks are a new developer feature, originally introduced in Gutenberg 16.4 for auto-inserting blocks. Developers can specify a location where a block will be inserted, such as before or after a template. Users can then reposition the blocks after insertion using the editor tools.
\n\n\n\nWordPress 6.4 ships with a brand new default theme, Twenty Twenty-Four. It was designed to be a multi-purpose theme, suitable for building a wide range of websites, including blogs, businesses, and portfolios. The theme comes with more than 35 templates and patterns. Check out a live demo to see all the full-page patterns, section patterns, and style variations available in Twenty Twenty-Four. It includes three different fully-built site demos for blogger, photographer, and entrepreneur use cases.
\n\n\n\nimage credit: WordPress 6.4 About Page\n\n\n\nOther notable improvements in 6.4 include the following:
\n\n\n\nCheck out the beautiful 6.4 release page to see all the major features highlighted. Under the hood there are also more than 100 performance-related updates and a range of accessibility improvements that create a more consistent experience in the site and post editors.
\n\n\n\nThis is the last major release planned for 2023. It includes contributions from more than 600 people across 56 countries, with 170 first-time contributors.
\n\n\n\nWordPress 6.4 was led by an underrepresented gender release squad, which Release Lead Josepha Haden Chomphosy organized “to welcome and empower diverse voices in the WordPress open source project.” Together they shipped 1,150 enhancements and fixes available now in 6.4.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 03:40:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Matt: Shirley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=103777\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://ma.tt/2023/11/shirley/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:464:\"The new WordPress 6.4 is named in honor of Shirley Horn, who NPR described as the queen of silence and interpretation. If you’re in San Francisco and love jazz vocalists, this Friday Clairdee will be at Keys.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 00:44:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"WPTavern: Jetpack 12.8 Launches Jetpack Creator for Monetizing Content and Subscribers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150970\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"https://wptavern.com/jetpack-12-8-launches-jetpack-creator-for-monetizing-content-and-subscribers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6417:\"Jetpack 12.8 was released this week, introducing Jetpack Creator, a new product under the Growth category that sits alongside the recently launched Newsletter product. Jetpack Creator is aimed at users who want to monetize their content and subscribers. It supports e-books, courses, paid newsletters, advertising, paywalled access, and other content monetization options.
\n\n\n\nThe market size of the creator economy is growing and established social networking apps are updating their offerings to better serve creators who are marketing themselves independently. According to Goldman Sachs Research, the creator economy could approach half-a-trillion dollars by 2027:
\n\n\n\n\n\n\n\n\nAs the ecosystem grows, the total addressable market of the creator economy could roughly double in size over the next five years to $480 billion by 2027 from $250 billion today.
\n\n\n\nGoldman Sachs Research expects the 50 million global creators to grow at a 10-20% compound annual growth rate during the next five years.
\n
Jetpack Creator bundles monetization features aimed at this market. It enables access to 40+ blocks that allow creators to paywall content, add subscriber forms, accept donations, start a newsletter, and receive payment via Stripe or PayPal. Jetpack Creator also extends existing products, like adding the ability to import unlimited subscribers. The free Newsletter product caps subscriber imports at 100.
\n\n\n\n\n\n\n\n\n\n\n\nUsers on the Creator plan are also added to Jetpack’s “creator network,” which appears to be similar to ConvertKit’s creator network with a few differences. The network is designed to amplify creator’s content to help them reach a broader audience across WordPress.com and self-hosted sites using Jetpack. Jetpack’s creator network aims to get sites exposure to new readers through distribution to more areas of WordPress.com’s Reader.
\n\n\n\n\n\n\n\n\n\n\n\nIt also includes author recommendations, powered by the Blogroll block, which was introduced in Jetpack 12.7. Site admins can recommend other sites their readers might enjoy and have their site included in others’ recommendations as well.
\n\n\n\n\n\n\n\n\n\n\n\nThe Suggested follows modal is currently driven by an algorithm and suggests additional publications to follow based on what other people follow and other publications recommend. Jetpack representatives said there are plans to make it more Blogroll driven in the future.
\n\n\n\n\n\n\n\n\n\n\n\nCreators can track their engagement through a number of different ways in Jetpack, including general traffic stats, email open stats, WordAds revenue, and subscriber stats, with a new growth chart using records going forwards since October 24. Jetpack also includes an Earn screen for those selling paid content.
\n\n\n\n\n\n\n\n\nEmail opens\n\n\n\nSubscriber growth\n\n\n\n\nThe Jetpack Free plan gives users access to all the monetization tools for free but takes 10% of all revenue, similar to Substack and Gumroad. This allows users to try out the tools to see if they can make money through their web presence. The new Creator plan reduces the fees to 2% (plus Stripe fees), a significant savings for those who are successfully earning money as an online creator.
\n\n\n\nThe fees apply to the following features:
\n\n\n\nJetpack product manager Mike Stott said his team is keen on receiving feedback on this initial offering and will continue developing the roadmap based on users’ input.
\n\n\n\n“There’s a lot happening in Newsletter – last month we launched Paid Newsletter tiers and we’ll be bringing subscriber modal and categories settings into the Jetpack UI in future too,” Stott said.
\n\n\n\n“We’ll also be making it easier for content creators to gain more subscribers through the creator network (a start to this is the Author recommendations) as well as make it easier to get started.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 07 Nov 2023 20:56:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"WordPress.org blog: WordPress 6.4 “Shirley”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16299\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://wordpress.org/news/2023/11/shirley/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:67291:\"\n\n\n\nSay hello to WordPress 6.4 “Shirley,” named after the iconic jazz artist Shirley Horn. Her distinctive voice and extraordinary connection to the piano established her as one of the leading jazz musicians of her generation. Horn’s journey from the Washington D.C. jazz scene to the international stage is a testament to her dedication and perseverance. Her influence reached far beyond the confines of traditional jazz, breaking boundaries and inspiring audiences worldwide.
\n\n\n\nEnjoy the easy pace of Shirley Horn’s music as you take in all that 6.4 offers.
\n\n\n\nThis latest version of WordPress introduces a new, versatile default theme and a suite of upgrades to empower every step of your creative journey. Craft your content seamlessly with further writing improvements. Explore more ways to bring your vision to life and streamline site editing with enhanced tools. Whether you’re new to WordPress or an experienced creator, “Shirley” has something for you. Discover the unmatched flexibility of building with blocks and let your ideas take flight.
\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\nMany of the features and enhancements in WordPress 6.4 fall in the “small but mighty” category. Along with the adaptable beauty of the Twenty Twenty-Four theme, these updates help content creators and site developers alike save time and effort while delivering the high value, low hassle WordPress experience the world has grown to expect.
\nJosepha Haden Chomphosy, Executive Director of WordPress
Experience site editing at its finest with Twenty Twenty-Four. This new multi-faceted default theme has been thoughtfully crafted with three distinct use cases in mind, from writers and artists to entrepreneurs. Save time and effort with its extensive collection of over 35 templates and patterns—and unlock a world of creative possibilities with a few tweaks. Twenty Twenty-Four’s remarkable flexibility ensures an ideal fit for almost any type of site. Check it out in this demo.
\n\n\n\n\n\n\n\nNew enhancements ensure your content creation journey is smooth. Find new keyboard shortcuts in List View, smarter list merging, and enhanced control over link settings. A cohesive toolbar experience for the Navigation, List, and Quote blocks lets you work efficiently with the tooling options you need.
\n\n\n\n\n\n\n\nFirst introduced in WordPress 6.3, the Command Palette is a powerful tool to quickly find what you need, perform tasks efficiently, and speed up your building workflow. Enjoy a refreshed design and new commands to perform block-specific actions in this release.
\n\n\n\n\n\n\n\nPatterns are an excellent way to leverage the potential of blocks and simplify your site-building process. WordPress 6.4 allows you to organize them with custom categories. Plus, new advanced filtering in the Patterns section of the inserter makes finding all your patterns more intuitive.
\n\n\n\n\n\n\n\nBuild beautiful and functional layouts with an expanded set of design tools. Play with background images in Group blocks for unique designs and maintain image dimensions consistent with placeholder aspect ratios. Do you want to add buttons to your Navigation block? Now you can do it conveniently without a line of code.
\n\n\n\n\n\n\n\nEnable lightbox functionality to let your site visitors enjoy full-screen, interactive images on click. Apply it globally or to specific images to customize the viewing experience.
\n\n\n\n\n\n\n\nSet custom names for Group blocks to organize and distinguish areas of your content easily. These names will be visible in List View.
\n\n\n\n\n\n\n\nNew previews for Gallery and Image blocks in List View let you visualize and locate where images on your content are at a glance.
\n\n\n\n\n\n\n\nNeed to use your custom patterns on another site? Import and export them as JSON files from the Site Editor’s patterns view.
\n\n\n\n\n\n\n\nBlock Hooks enables developers to automatically insert dynamic blocks at specific content locations, enriching the extensibility of block themes through plugins. While considered a developer tool, this feature is geared to respect your preferences and gives you complete control to add, dismiss, and customize auto-inserted blocks to your needs.
\n\n\n\n\n\n\n\nThis release includes more than 100 performance-related updates for a faster and more efficient experience. Notable enhancements focus on template loading performance for themes (including Twenty Twenty-Four), usage of the script loading strategies “defer” and “async” in core, blocks, and themes, and optimization of autoloaded options.
\n\n\n\nEvery release is committed to making WordPress accessible to everyone. WordPress 6.4 brings several List View improvements and aria-label support for the Navigation block, among other highlights. The admin user interface includes enhancements to button placements, “Add New” menu items context, and Site Health spoken messages. Learn more about all the updates aimed at improving accessibility.
\n\n\n\nCheck out the new WordPress 6.4 page to learn more about the numerous enhancements and features of this release.
\n\n\n\nExplore Learn WordPress for quick how-to videos, online workshops, and other free resources to level up your WordPress knowledge and skills.
\n\n\n\nIf you are looking for detailed technical notes on new changes, the WordPress 6.4 Field Guide is for you. Don’t forget to subscribe to the Developer Blog to stay on top of the latest development updates, tutorials, and more.
\n\n\n\nFor more information on installation, fixes, and file changes, visit the 6.4 release notes.
\n\n\n\n\n\n\n\nThe WordPress 6.4 release comes to you from an underrepresented gender release squad to welcome and empower diverse voices in the WordPress open source project.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nBeing part of the 6.4 release coordination team has allowed me to closely observe the intricate release process, where every detail, no matter how minor, is meticulously addressed—taking into account various factors like performance and backward compatibility. There’s still much to learn, but I feel fortunate to have had the chance to contribute to WordPress 6.4.
\nAkshaya Rane, 6.4 release coordinator team member
Over several weeks, the 6.4 release squad kept the release on track and moving forward by leading collective work, connecting ideas, and removing roadblocks.
\n\n\n\nWordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a global and diverse community of people working together to strengthen the software.
\n\n\n\nWordPress 6.4 reflects the countless efforts and passion of more than 600 contributors in at least 56 countries. This release also welcomed over 170 first-time contributors!
\n\n\n\nTheir collaboration delivered more than 1150 enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress open source community.
\n\n\n\n6adminit · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · aayusha · Abha Thakor · Abid Omar · Adam Silverstein · Adhun Anand · admcfajn · adrianduffell · aegkr · ahardyjpl · Ahmed Hussein · Ahmed Kabir Chaion · ajakaroth · Aki Hamano · Akihiro Harai · Akira Tachibana · Akshaya Rane · Al-Amin Firdows · Alain Schlesser · Albert Juhé Lluveras · Alex Concha · Alex King · Alex Lende · Alex Stine · Alexandre Buffet · Alisha Bajracharya · Allison Tarr · Alvi Tazwar · amedv · Ana Cirujano · Anand Upadhyay · Anders Norén · André · Andrea Fercia · Andrei Draganescu · Andrew Hayward · Andrew Hutchings · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrew Wilder · Andy Fragen · Andy Peatling · Ankit Gade · Ankit K Gupta · Ankit Panchal · Anna · Anne Katzeff · Anne McCarthy · Anne-Mieke Bovelett · anphira · Anthony Burchell · Anton Plauche · Anton Timmermans · Anton Vlasenko · Anveshika Srivastava · archon810 · arena · Ari Stathopoulos · Arnab Mondal · Artemio Morales · Arthur Chu · asafm7 · Aslam Doctor · Aurooba Ahmed · Austin Ginder · Ayesh Karunaratne · azharckra · Balu B · bangank36 · barbmiller · Barry · Bart · Basilis Kanonidis · Beatriz Fialho · behoney · ben · Ben Dwyer · Ben Greeley · Ben Hansen · Benjamin Intal · Benjamin Zekavica · benjaminknox · Benoit Chantre · Bernhard Reiter · Bernie Reiter · Bhrugesh Bavishi · Bijay Yadav · Binsaifullah · Biplav · Birendra Dhami · Birgit Olzem · Birgit Pauli-Haack · Block Themes Pro · bmalsht · bonger · bookwyrm · Boone Gorges · Boro Sitnikovski · Brad Jorsch · Bradley Jacobs · Brandon Kraft · Brandon Vreeman · Brian Gardner · Brian Haas · Brooke · Brooke. · Bud Kraus · Caleb Burks · Calvin Alkan · Carlo Cannas · Carlos Bravo · Carlos G. P. · Carolina Nymark · Cathi Bosco · ceer · cenkdemir · Chad Chadbourne · chased@si.edu · Chintan hingrajiya · Chip Bennett · Chloé Bringmann · Chris Runnells · chriscct7 · chrisdesrochers · codersantosh · Colin Stewart · Corey Worrell · Courtney Patubo Kranzke · Courtney Robertson · Crisoforo Gaspar · crstauf · Csaba (LittleBigThings) · Cupid Chakma · cybeardjm · Cyberchicken · Daisuke Takahashi · Dajeema Rai · Damon Cook · Damon Sharp · Dan Tovbein · Daniel Bachhuber · Daniel Richards · danieldudzic · Daniele Scasciafratte · Danielle Zarcaro · danieltj · darerodz · Darin Kotter · darkfate · Darren Ethier (nerrad) · Darshit Rajyaguru · Dave Loodts · dave03 · David Baumwald · David Biňovec · David Calhoun · David E. Smith · David Favor · David Herrera · David Ryan · David Smith · Dawid Urbanski · daxelrod · De Belser Arne · Dean Sas · Dee Teal · Deepak Vijayan · Denis Žoljom · Dennis Snell · Derek Blank · Derrick Tennant · Devan Ferguson · Dharmesh Patel · Dhrumil Kumbhani · Dhruvi Shah · Diane Co · Dilip Bheda · Dimitris Mitsis · Dion Hulse · DJ · dj.cowan · Dominik Schilling · doughamlin · Drew Jaynes · Earle Davies · Ebonie Butler · Edi Amin · Edward Caissie · Ehtisham S. · Ella van Durpe · Ellen Bauer · emailjoey · Emerson Maningo · Emily Clarke · Emily Leffler Schulman · emirpprime · enodekciw · Enrico Battocchi · Erik Betshammar · Esrat Sultana Popy · Estela Rueda · Fabian Kägy · Fabian Todt · Fabio Rubioglio · Faisal Alvi · Felipe Elia · Felix Arntz · Femy Praseeth · floydwilde · FolioVision · Francesca Marano · Frank Laszlo · Fredde Battel · fzhantw · Gabriel Koen · Ganesh Dahal · Garrett Hyder · Gary Cao · Gary Pendergast · Gennady Kovshenin · George Hotelling · George Mamadashvili · Gerardo Pacheco · Gio Lodi · Glen Davies · Gnanasekaran Loganathan · Gopal Krishnan · GOZER · gpotter · Grant M. Kinney · Greg Ross · Greg Ziółkowski · gregfuller · Guss77 · Gustavo Bordoni · gvgvgvijayan · Héctor Prieto · H.M. Mushfiqur Rahman · hanneslsm · Hanzala Taifun · Hareesh S · Harsh Gajipara · Hasanuzzaman · Haz · Helen Hou-Sandi · Hemant Tejwani · Hit Bhalodia · hlunter · Howdy_McGee · Huzaifa Al Mesbah · Ian Dunn · Incursa Designs · ironprogrammer · Isabel Brison · itecrs · Ivan Zhuck · jaimieolmstead · Jakaria Istauk · Jake Goldman · Jake Spurlock · James Hunt · James Janco · James Koster · James Roberts · james0r · Jamie McHale · Jamie Perrelet · Jamie VanRaalte · jane · Jarda Snajdr · Jari Vuorenmaa · Jarko Piironen · Jason Adams · Jason Cosper · Jason Crist · jastos · Jean-Baptiste Audras · Jeff Bowen · Jeff Chi · Jeff Everhart · Jeff Ong · jeffikus · Jeffrey Paul · jeflopo · Jeremy Felt · Jeremy Herve · Jeremy Yip · jeryj · Jesin A · Jessica Duarte · Jessica Goddard · Jessica Lyschik · Jick · Jip Moors · jivygraphics · Joe Dolson · Joe Hoyle · Joe McGill · Joen A. · John Blackbourn · John Hooks · John James Jacoby · John Regan · Jon Brown · Jon Cave · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Joona · Joost de Valk · JordanPak · jordesign · Jorge Costa · Joseph G. · Josepha Haden · joshcanhelp · joshuatf · JR Tashjian · Juan Aldasoro · JuanMa Garrido · Juliette Reinders Folmer · Justin Tadlock · Jyolsna J E · K M Ashikur Rahman · K. Adam White · KafleG · Kai Hao · Kalmang · Kalpesh · Kamrul Hasan · Karlijn Bok · Karol Manijak · Karthik Thayyil · Katie Ayres · kawsaralameven · Keanan Koppenhaver · Kelly Choyce-Dwan · Kevin Fodness · Kevin Miller · Kevin Taron · khleomix · Khokan Sardar · Kim Coleman · Kishan Jasani · kkmuffme · Koji Kuno · Konstantin Kovshenin · Konstantin Obenland · Kopila Shrestha · Krupal Panchal · Labun Chemjong · Lance Willett · LarryWEB · lastsplash (a11n) · lau@mindproducts.com.au · launchinteractive · Laura Adamonis · Laura Byrne · laurelfulford · Lauren · Laxmikant Bhumkar · Lee Willis · Lena Morita · Liam Gladdy · Linkon Miyan · Linnea Huxford · Lloyd Budd · Lovekesh Kumar · Luigi · Luis Felipe Zaguini · Luis Herranz · Luke Cavanagh · lunaluna · lyndauwp · Márcio Duarte · maciejmackowiak · madejackson · Madhu Dollu · Madhu Dollu · Maggie Cabrera · Mahbub Hasan Imon · Mahrokh · Mai · Maja Benke · maltfield · Manesh Timilsina · manfcarlo · Manzoor Wani · marcelle42 · Marcelo de Moraes Serpa · Marco Ciampini · Marco Pereirinha · Marcoevich · margolisj · Marin Atanasov · Mario Santos · Marius L. J. · Mark Jaquith · Marko Ivanovic · Marta Torre · Martijn van der Klis · martin.krcho · Mary Baum · Masoud NKH · mathsgrinds · Matias Benedetto · Matias Ventura · Matt Keys · Matt Watson · Matthaus Klute · Matthew Eppelsheimer · Matthew Farlymn · Matthew Haines-Young · matthewjho · maurodf · Maxwell Morgan · maysi · Md HR Shahin · meagan hanes · Mehedi Hassan · Meher Bala · Mel Choyce-Dwan · mer00x · merel1988 · Michael Arestad · Michael Burridge · Michael Showes · Michal Czaplinski · Michalooki · Michelle Blanchette · Michelle Frechette · Michi91 · Miguel Fonseca · Mikael Korpela · Mike Jolley (a11n) · Mike McAlister · Mike Schinkel · Mike Schroder · Mike Straw · Mikin Chauhan · Milen Petrinski - Gonzo · mimi · mitchellaustin · Monir · Mrinal Haque · mrwweb · Muhammad Arslan · Muhibul Haque · mujuonly · Mukesh Panchal · Mumtahina Faguni · Mushrit Shabnam · Myles Taylor · Nalini Thakor · nandhuraj · Nazgul · Nazmul Sabuz · Neil Hainsworth · nendeb · Nick Diego · Nicolas Juen · Nicole Furlan · nicomollet · nidhidhandhukiya · Niels Lange · Nihar Ranjan Das · Nik Tsekouras · Nilambar Sharma · Nilo Velez · niravsherasiya7707 · Nitesh Das · Nithin John · Nithin SreeRaj · Noah Allen · Nyasha · ockham · Ohia · okat · Olga Gleckler · Oliver Campion · OllieJones · Paal Joachim Romdahl · pannelars · Pascal Birchler · Paul Biron · Paul Kevan · pavelevap · Pedro Mendonça · pentatonicfunk · Pete Nelson · Peter Wilson · petitphp · petrosparaskevopoulos · Petter Walbø Johnsgård · Phill · Pieterjan Deneys · piyushdeshmukh · Plugin Devs · Pooja Bhimani · Pooja Derashri · Pooja N Muchandikar · pranavjoshi · Prashant · Presskopp · r-c · Rajin Sharwar · Ramon Ahnert · Ramon Corrales · Ramon James · Rebekah Markowitz · Remy Perona · ren · Renatho (a11n) · Rene Hermenau · Reyes Martínez · Riad Benguella · Rian Rietveld · Rich Tabor · Robert Anderson · Robert O\'Rourke · Robin · robpetrin · Rolf Allard van Hagen · Ryan Duff · Ryan McCue · Ryan Neudorf · Ryan Welcher · Sérgio Gomes · Sagar Tamang · Sajjad Hossain Sagor · Sakib Mohammed · Sal Ferrarello · samba45 · Samir Karmacharya · Sampat Viral · Samuel Wood (Otto) · Sarah Norris · Sarah Williams · Sarath AR · Satish Prajapati · saulirajala · saxonfletcher · Scott Kingsley Clark · Scott Reilly · Scott Taylor · Scout James · scribu · Sergey Biryukov · Sergio Scabuzzo · Seth Rubenstein · Shail Mehta · shawfactor · Shawn Hooper · shilo-ey · Shiva Shanker Bhatta · shresthaaman · Shubham Sedani · Simon Dowdles · Siobhan · Siobhan Bamber · Smit Rathod · sofiashendi · Sonia Gaballa · Soren Wrede · SourceView · Spenser Hale · Stephanie Walters · Stephen Bernhardt · Stephen Edgar · Steve Erdelyi · Steve Jones · Subodh Sunuwar · Subrata Sarkar · Suji K Chandran · Sumi Subedi · Sumit Bagthariya · Sumit Singh · Sunita Rai · suprsam · syamraj24 · Sybre Waaijer · Synchro · Sé Reed · Taco Verdonschot · Tahmid ul Karim · Tahmina Jahan · Takayuki Miyoshi · Tammie Lister · Tanvirul Haque · Teddy Patriarca · tejadev · thinkluke · Thomas Patrick Levy · tibbsa · Tiffany Bridge · Tim Nolte · timdix · Timothy Jacobs · tmatsuur · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tom Cafferkey · Tom H · Tom J Nowell · tomluckies · Tomoki Shimomura · tomsommer · Tony G · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · toscho · Tran Ngoc Tuan Anh · Trinisha · Trisha Salas · tristanleboss · TV productions · Ugyen Dorji · Ulrich · Umesh Balayar · Upadala Vipul · Utsav tilava · valentindu62 · Valerie Blackburn · Vicente Canales · Viktor Szépe · Vipul Ghori · vivekawsm · vortfu · Vraja Das · webashrafians · WebMan Design | Oliver Juhas · Weston Ruter · WHSajid · Will Skora · William Earnhardt · Willington Vega · Winstina · winterstreet · WraithKenny · wyrfel · Yoseph Tamang · Yui · zieladam · Zunaid Amin · Илья
\n\n\n\nOver 60 locales have translated 90 percent or more of WordPress 6.4 into their language. Community translators are working hard to ensure more translations are on their way. Thank you to everyone who helps make WordPress available in 200 languages.
\n\n\n\nLast but not least, thanks to the volunteers who contribute to the support forums by answering questions from WordPress users worldwide.
\n\n\n\nParticipation in WordPress is not limited to coding. If contributing appeals to you, learning more and getting involved is easy. Discover the teams that come together to Make WordPress, and use this interactive tool to help you decide which is right for you.
\n\n\n\n\n\n\n\nOver the past two decades, WordPress has transformed the digital publishing landscape and empowered anyone to create and share, from handcrafted personal stories to world-changing movements.
\n\n\n\nThe present and future of WordPress hold exciting opportunities for everyone, builders and enterprises alike. The foundational work for Phase 3 of the roadmap continues, with efforts focused on fostering real-time collaboration and streamlining publishing flows to improve how creators and teams work together in WordPress.
\n\n\n\nStay on top of the latest news and contributing opportunities by subscribing to WordPress News and the WP Briefing podcast.
\n\n\n\n\n\n\n\nThe smooth feel of jazz
The cutting-edge of the web
Install 6.4
In this show we talk with Topher about explaining what WordPress pros do for a living, the demographics of WordPress and teaching with video.
\n>> The post How to Tell Friends and Family What You Do in WordPress with Topher DeRosia appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 07 Nov 2023 10:48:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"WPTavern: Newspack Plugin Update Checker Lets Users Update from GitHub\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150972\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/newspack-plugin-update-checker-lets-users-update-from-github\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4125:\"Adam Schweigert, an independent media and technology consultant, has released a plugin called Newspack Plugin Update Checker that enables self-hosted Newspack users to keep their plugins up-to-date. The Newspack project was launched in 2019 by WordPress.com, with support from the Google News Initiative, the Knight Foundation, and The Lenfest Institute. It provides local news organizations a powerful, yet cost effective publishing platform that promotes financial sustainability.
\n\n\n\nMore than 200 news sites are on the hosted version of Newspack, which uses WordPress.com’s cloud platform. Organizations can also host their own Newspack installations independently, which includes a theme, collection of plugins, and blocks. KinshiPress, which publishes news and updates for WordPress publishers, has a guide to self-hosting Newspack that walks through the process of getting set up. It also mentions the drawback of the plugins being hosted on GitHub.
\n\n\n\nSchweigert’s Newspack Plugin Update Checker solves this problem by using a plugin updater library that checks for updates and lets users know when a new version is available. The notice appears in the dashboard in a similar way to how WordPress.org displays updates.
\n\n\n\n\n\n\n\n\n\n\n\nThe plugin checks for updates for nine of the most commonly-used Newspack plugins, including the following:
\n\n\n\nSchweigert noted that the plugin requires the Newspack plugins be in folders named using their respective slugs. Although the plugin allows users to enable auto-updates, he recommends keeping an eye on the Newspack release notes to be prepared for any potentially breaking changes.
\n\n\n\nKinshiPress author Steve Burge recently published an article on the Newspack ecosystem, contending that Newspack has the potential to do for publishers what WooCommerce has done for e-commerce.
\n\n\n\n“There’s a big audience out for a publishing platform that is open source, highly extendable, and has the backing of a successful company and a strong community,” Burge said.” Where else can newspapers, magazines and radio stations go? They mostly go to WordPress already, but the platform we provide them could be much more targeted and helpful.”
\n\n\n\nAlthough Schweigert’s plugin is a good stop gap measure, Burge said he thinks putting the Newspack plugins on WordPress.org and improving the documentation would go a long way towards expanding its impact.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 04 Nov 2023 03:30:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:34;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"WPTavern: WordPress Theme Handbook Updates Chapter on Block Templating\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150958\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/wordpress-theme-handbook-updates-chapter-on-block-templating\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2584:\"WordPress contributors have updated the Theme Handbook to include a new chapter on block templating. The chapter covers how the WordPress block template system works, how to build custom templates and parts and include them in a theme. This is critical documentation designed to provide a learning path for those who are building their first block themes.
\n\n\n\nAutomattic-sponsored developer advocate Justin Tadlock announced the update on Twitter, noting that it also includes a couple of new docs in the Global Settings and Styles chapter for registering template-related features in theme.json, and the same for template parts.
\n\n\n\nThe new chapter on block templating is just one part of a larger effort to overhaul the Theme Handbook for modern day WordPress. Contributors are transitioning the focus from classic theming to block theming, with just one chapter in the handbook devoted to classic themes.
\n\n\n\n“It was created during a time when classic themes were the only method of front-end design for WordPress,” Tadlock said in the proposal to overhaul the handbook. “Much of its content now exists in a transitory state between classic and modern block theming. This has created a scenario where the handbook sometimes reads more like patchwork than if it were built with a single vision. That is often a natural result of adding new documentation over years.”
\n\n\n\nThe proposal does not recommend scrapping all of the existing content but rather carrying some of it forward to be updated and reorganized. A good portion of the existing content is still relevant to be migrated to the Classic Themes chapter.
\n\n\n\nOverhauling the Theme Handbook is a colossal effort that’s still ongoing. It’s being managed under a tracking ticket on GitHub. The new chapter better supports developers who are just figuring out how the WordPress block template system works, but there are many more chapters that need attention. Anyone who would like to get involved in the project can select any issue on the ticket to get started.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 03 Nov 2023 19:36:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:35;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"WPTavern: Add Icons to WordPress’ Core Button Block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150927\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://wptavern.com/add-icons-to-wordpress-core-button-block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5605:\"Nick Diego, a developer advocate at Automattic and core contributor, is the author of the popular Icon Block plugin that enables users to add custom SVG icons and graphics to the WordPress block editor. He is often asked if the plugin can add icons to the core Button block, but that is outside the scope of what it does. Last week he wrote a plugin that fulfills this feature request in a separate plugin without building a custom block.
\n\n\n\n \n\n\n\n\n\n\n\nThe Enable Button Icons plugin is available on GitHub as an example that demonstrates how developers can lightly extend core blocks for features like this. Diego said he was inspired by WordPress developer Aki Hamano’s Enable Responsive Image plugin that adds settings to the Image block to elegantly display different images depending on the width of the screen.
\n\n\n\n \n\n\n\n“I wanted to use the WordPress image block to switch images on mobile, but I wanted something that would simply extend the core block without having to create a custom block, so I tried making one,” Hamano said. “For now, you can only add one image, and only the breakpoint and resolution can be switched.”
\n\n\n\nDiego said he doesn’t plan to add his Enable Button Icons plugin to the official WordPress directory.
\n\n\n\n“It works great, but it is not designed to support an entire library of icons, and I know that will be the first thing people ask for,” he said. “So, I’m thinking of keeping it as an example and encouraging people to take it and modify it as they want.”
\n\n\n\nI tested the plugin and it works perfectly but is certainly ripe for being extended to support a larger selection of icons. Alternatively, it may be useful for a brand that has a set number of custom designed icons they want to be easily accessible for use in Button blocks.
\n\n\n\n\n\n\n\n\n\n\n\nDiego will be running an event at the end of the month about how to extend core WordPress blocks, and the Enable Button Icons plugin will be part of that. It will be another segment in the “Developer Hours” series run through the Learn WordPress Online Workshops group on Meetup. Diego and a team of contributors just wrapped up a Developer Hours event today featuring a demo/walkthrough of the upcoming Twenty Twenty-Four default theme. Watch for the next event to be added to the schedule sometime this week.
\n\n\n\nDevelopers have been asking for more extensibility, hooks, and filters for the block editor, and an upcoming Hallway Hangout event will focus on triaging issues related to extending Gutenberg. Contributors will discuss the 110 outstanding issues labeled “Extensibility,” and 20 issues labeled “Blocks Adoption,” used for issues that directly impact the ability to adopt features of Gutenberg. Anyone who wants to share their opinions about block editor extensibility issues is invited to join.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 03 Nov 2023 02:03:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"Do The Woo Community: Do the Woo Day 3 Recap, WooSesh 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77702\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://dothewoo.io/do-the-woo-day-3-recap-woosesh-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:367:\"Day 3 recap included a deep look at producing WooSesh, the Seshies awards and conversation around the days sessions.
\n>> The post Do the Woo Day 3 Recap, WooSesh 2023 appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 02 Nov 2023 11:05:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"WPTavern: Wordfence CLI 2.0.1 Update Adds Free Vulnerability Scanning\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150866\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wptavern.com/wordfence-cli-2-0-1-update-adds-free-vulnerability-scanning\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3294:\"Wordfence CLI 2.0.1 introduced free vulnerability scanning this week. The new CLI product was launched at WordCamp US two months ago with malware detection capabilities, but the latest update brings in the most highly requested feature – vulnerability scanning at scale.
\n\n\n\nWordfence is most well-known for its Web Application Firewall, malware scanner, and login security product, which is packaged as a free plugin and installed on more than 4 million websites. The CLI is the first-ever command line malware and vulnerability scanner for WordPress servers. It is targeted at developers, site cleaners who scan large numbers of files for remediation, agencies, and hosting companies that want to scan across entire networks of millions of customers.
\n\n\n\n“Vulnerability scanning in Wordfence CLI 2.0.1 uses our own open vulnerability database,” Wordfence CEO Mark Maunder said. “The database itself is completely free for anyone to use, and includes APIs that are open, along with web hooks so that developers can build real-time alerting into their applications. Our mission is to secure the Web, and we think that having an open vulnerability database, with an open source, robust and high performance vulnerability scanner for servers furthers that mission.”
\n\n\n\nThe vulnerability database includes responsible disclosures published by researchers for the benefit of the wider community.
“Because most vulnerabilities come from the research community, we believe they are public property,” Maunder said. “While some companies do charge for their collection of vulnerabilities, we don’t think it is appropriate to resell public property, which is why we created an open and completely free vulnerability database.”
The CLI vulnerability scans use the Wordfence Intelligence Vulnerability API feed, which is free for both personal and commercial use. It contains more than 12,250 unique vulnerability records affecting 7,600 plugins and themes. The Wordfence team adds an average of 82 new vulnerabilities per week.
\n\n\n\nVersion 2.0.1, code named “Voodoo Child” simplifies installation so users no longer have to go to the Wordfence site to get an API key. The tool fetches the API key in the background to make it easier to get started.
\n\n\n\nWordfence CLI is licensed under the GPLv3 and available on GitHub, along with documentation for installing, configuring, and running the application.
\n\n\n\n“Wordfence CLI is one of those projects where the product roadmap writes itself because there is such an obvious need for a powerful tool like this in the WordPress server administration space,” Wordfence lead developer Matt Barry said. “We’re in this for the long haul and will continue to invest heavily in Wordfence CLI, with your guidance.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 20:48:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"WordPress.org blog: WordPress 6.4 Release Candidate 3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16247\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2023/11/wordpress-6-4-release-candidate-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8050:\"The third release candidate (RC3) for WordPress 6.4 is ready to download!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC3 on a test server and site.
\n\n\n\nWordPress 6.4 is slated for release on November 7, 2023—less than a week away. If you haven’t tried it, now is the time.
\n\n\n\nYou can test WordPress 6.4 RC3 in three ways:
\n\n\n\nwp core update --version=6.4-RC3
Read the RC1 announcement for featured highlights, and check the Make WordPress Core blog for 6.4-related posts. If you are looking for detailed technical notes on new features and improvements, the WordPress 6.4 Field Guide is for you.
\n\n\n\nThe WordPress 6.4 release is brought to you by an underrepresented gender release squad to welcome the participation and partnership of those who identify as gender-underrepresented in the WordPress open source project.
\n\n\n\n\n\n\n\nThanks to everyone who has tested the beta and RC releases. Since RC2 was released on October 24, there have been more than 25 issues resolved. You can browse the technical details for all recent updates using these links:
\n\n\n\nIt’s recommended to use PHP 8.1 or 8.2 with the upcoming 6.4 release. Refer to WordPress 6.4’s PHP compatibility post for more details.
\n\n\n\n\n\n\n\nWordPress is open source software made possible by a community of people collaborating on and contributing to its development. The resources below outline various ways you can help, regardless of your technical expertise.
\n\n\n\nYour feedback and help in testing are vital to developing the WordPress software and ensuring its quality. It’s also a meaningful way for anyone to contribute. Check out this guide for instructions on testing WordPress 6.4 features.
\n\n\n\nThe core Query block requires more testing and feedback to ensure the latest changes to prevent full page reloads work smoothly. Please note that this setting was called “Enhanced pagination” but has recently been renamed, and it’s now referred to as “Force page reload” instead.
\n\n\n\nIf you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
\n\n\n\nCurious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
\n\n\n\nDuring the release candidate phase of WordPress 6.4, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.
\n\n\n\nDo you build themes and plugins? Your products play an integral role in extending the functionality and value of WordPress for users worldwide.
\n\n\n\nHopefully, you have already tested your themes and plugins with WordPress 6.4 betas. With RC3, you will want to continue your testing and update the “Tested up to” version in your plugin’s readme file to 6.4.
\n\n\n\nPlease post detailed information to the support forums if you find compatibility issues.
\n\n\n\nHelp the Docs team put the finishing touches on end-user documentation in time for the 6.4 release. Find out what’s needed and how you can help in this post.
\n\n\n\nDo you speak a language other than English? ¿Español? Français? Português? Русский? 日本? Help translate WordPress into more than 100 languages.
\n\n\n\n\n\n\n\nOne more week of prep
One more week to test the code
One more week til launch
Thank you to the following contributors for collaborating on this post: @meher, @rmartinezduque, @sereedmedia, @jorbin, @luisherranz, @marybaum.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 19:21:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Reyes Martínez\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"WPTavern: #97 – Estela Rueda, Courtney Robertson and Javier Casares on the Future of Translating WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=150878\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://wptavern.com/podcast/97-estela-rueda-courtney-robertson-and-javier-casares-on-the-future-of-translating-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:56373:\"Transcript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast, which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case how translations of the WordPress project are created now and in the future.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you all your idea featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox, and use the form there.
\n\n\n\nSo on the podcast today, we have Estela Rueda, Courtney Robertson and Javier Casares.
\n\n\n\nCourtney is a former teacher who now focuses on contributing to WordPress. With a background in education, she understands the challenges faced by English second language learners in the American education system. She’s passionate about providing access to WordPress in multiple languages, as she believes it’s unfair to expect non-English speakers to simultaneously translate content and understand it.
\n\n\n\nEstela is a language enthusiast who has spent years navigating the challenges of website localization. As a member of the WordPress community, Estela has come across the intricacies of language differences, and the need for accurate translation in various Spanish locales. With 14 Spanish locales to handle Estela’s expertise in understanding the subtle nuances, and localizations of each language variation has been indispensable.
\n\n\n\nJavier is a dedicated member of the WordPress community, with expertise in creating documentation. Javier has been instrumental in developing handbooks for various sites. However, there have been some technical challenges. Despite these obstacles Javier, as you will hear, remains committed to addressing and solving the documentation issues at hand.
\n\n\n\nThis episode covers the important topic of translations, and making WordPress documentation more accessible to people worldwide. Our guests bring a wealth of knowledge and experience to the table, as they discuss the complexities and challenges of language translation in the WordPress ecosystem.
\n\n\n\nWe start by highlighting challenges posed in translating WordPress, such as the tangled processes currently in place, as well as more language focused topics. We talk about the extensive collaborative effort involved in translating WordPress, and the plans to expand translation efforts to documentation with the help of dedicated teams.
\n\n\n\nWe get into how contributors might need to rethink how many of the current translation processes are structured. We discuss the different approaches needed for translating plugins and themes versus documentation. We touch upon how technical aspects of these processes such as content creation and updates also pose significant challenges.
\n\n\n\nAll three guests stress the importance of global involvement in translation efforts, including translators, reviewers, and project managers. They advocate for the development of standardized style guides for each language to maintain consistency. And they explore the possibility of creating software, or tools, to manage translation tasks.
\n\n\n\nCourtney, Estela and Javier all acknowledge the challenges ahead, but express optimism that their ideas will help make WordPress accessible for all. Communicating how WordPress is built and how it works is an endeavor tightly aligned with the projects overall mission of democratizing publishing.
\n\n\n\nIf you’re interested in finding out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast, where you’ll find all the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Estela Rueda, Courtney Robertson and Javier Casares.
\n\n\n\nI am joined on the podcast today by three fine people. I’m joined by Courtney Robertson, Estela Rueda and Javier Casares. Hello all three of you.
\n\n\n\n[00:04:48] Javier Casares: Hello.
\n\n\n\n[00:04:49] Estela Rueda: Hi Nathan.
\n\n\n\n[00:04:50] Courtney Robertson: Hello.
\n\n\n\n[00:04:51] Nathan Wrigley: Very nice to have you on the podcast today. We’re going to be talking about WordPress translations, and the way that we can make it easier for people from around the globe to get access to WordPress documentation. It’s a very important subject and there’s been a lot of work, albeit that you may not know about it. There’s been an awful lot of work going on over, well more or less a decade, and we’ll find out more about that in a moment.
\n\n\n\nBut first of all I think it’s important that everybody gets a little window to introduce themselves, do a quick bio. So if I take you one at a time and lets start with Courtney. Just tell us who you are. And I know that I’m going to say can we be brief but I know time is short, so let’s keep it fairly brief if that’s all right.
\n\n\n\n[00:05:33] Courtney Robertson: Sure thing. I’ve been contributing to WordPress since 2009. A big part of the training team for many years. These days you can also find me over in Meta, Sustainability, and generally around the project on behalf of GoDaddy these days, and I’ve been there for about two and a half years. Long time contributor. Big fan.
\n\n\n\n[00:05:50] Nathan Wrigley: Thank you so much. I’m sure that people have come across Courtney in the past, as would be the case for the next two people. Let’s go for Estela next. Hello Estela, would you mind giving us your intro?
\n\n\n\n[00:06:01] Estela Rueda: Hi Nathan. Yes. I’ve been contributing for about five years already and I am mostly in the design and the documentation teams. But you can find me everywhere. I do mess around everywhere, I ask questions. And my goal has been to rearrange, recategorise the end user documentation. And that’s been the big project that we finished, it took us three years. And now we want to bring it up to the whole world in every single language we can manage.
\n\n\n\n[00:06:33] Nathan Wrigley: Okay thank you. And finally Javier, if you want to just give us your short bio.
\n\n\n\n[00:06:37] Javier Casares: Yeah. Hello everybody. I’m Javier Casares, I’m from Spain. I’ve been involved with WordPress since 2006, so more or less 17 years. I mainly focus on hosting, on the hosting team, and I’m helping the documentation team mainly with the Advanced Administration Handbook. So that’s more or less what I do. I do a lot of things but those are the main things.
\n\n\n\n[00:07:04] Nathan Wrigley: Those are the things which are pertinent to today’s discussion. Yeah, thank you so much.
\n\n\n\nSo if, like me, you are a native English speaker, English is your first language. It may very well be that some of the things that we’re going to talk about today have either never occurred to you, or you’ve never bumped up against this problem.
\n\n\n\nBecause broadly speaking, if you are a native English speaker, you can find the documentation, you can find tutorials. You can find almost anything you wish to find out about WordPress, how to use it, how to implement things and so on, by going and doing a Google search. And you’re off to the races because essentially everything has historically been done in the English language.
\n\n\n\nSo I guess that, in my case, makes me an incredibly fortunate person. But that’s not the case throughout the world. And as obviously WordPress has grown, we’re now 40 plus percent of the internet, it would be not really serving the user base of WordPress if everything was simply in English. It would be a laudable goal to get everything translated.
\n\n\n\nNow I guess we should probably outline where all of the things are at the moment. So it’s not the case that you can go to one website and there it all is, open a Pandora’s box, open it all and there it all is.
\n\n\n\nSo let’s outline that problem first. I don’t really mind who wishes to tackle this one. Yeah if somebody wants to just outline the problem that we face, where are all the documents stored at the moment?
\n\n\n\n[00:08:23] Estela Rueda: I can’t give it a go. There are many, many limitations within WordPress. There are the sites that are called the Rosetta sites, or locales and those are the ones that are written in other languages for local teams.
\n\n\n\nBut then we have issues, different issues. For instance, in Spanish, we have 14 locales in Spanish. So we have Spanish from Spain, we have Spanish from Mexico, Spanish from Colombia, Spanish from Costa Rica, et cetera. And everybody will think, well don’t you understand each other? Yeah we do, we understand each other, but there are so many differences in our languages. And there is the localisation of the words, and a lot of little things that we need to figure out. That’s one thing.
\n\n\n\nThen the other thing is that there are never enough contributors to do translations. And then there are all the technical issues that we have, and Javier can talk to you about those, because he’s more aware than all of the technical issues that we have.
\n\n\n\n[00:09:25] Nathan Wrigley: Okay, in that case, we’ll hopefully segue over to Javier. Are you able to take it from there?
\n\n\n\n[00:09:29] Javier Casares: Yeah. So the main thing is, we have the Rosetta sites. It’s local team can create their own documentation in a way, because some of the sites have their own handbooks. But there is some technical things there because, for example, the Spanish from Spain is one of the older sites in the WordPress network.
\n\n\n\nSo it’s database is in LATIN1, it’s not in UTF, it’s a technical thing. But it doesn’t allow, for example, emojis in the database. That’s so simple but it’s something that happens. So we have some problems having documentation there. That’s one of the things.
\n\n\n\nBut the other one is we have the documentation right now in wordpress.org/documentation. Also we have the developer.wordpress.org. We have the Learn corpus also in with a lot of documentation. In a lot of ways, WordPress TV should, maybe it’s another place with documentation, in video in this case. And everything usually is focused on English.
\n\n\n\nSo the main idea on this project we started like a year ago is, how can we translate everything into, more or less, at least eight languages? Because eight languages cover more or less eighty percent of the WordPress users. And also, where are we going to put that documentation? Because, for example, we can do ses.wordpress.org/documentation, that’s the easy one. But, for example, the developer documentation is in a subdomain so, where are we going to put all this documentation?
\n\n\n\nSo that’s one of the things we are trying to solve. That’s one technical problem we have to face. And the other one is, where are we going to put all the documentation to be translated? Because we know that WordPress will be multilingual in a way in some years. I hope soon, as soon as possible.
\n\n\n\nWe have now the phase three, the collaboration part. But we have the problem that we cannot give access in this case. This is something concrete for WordPress, not for a translation or a documentation problem. But we cannot give access to thousands of people to the WordPress network, because it won’t be able to control the security and everything.
\n\n\n\nWe decided to start migrating or having the English documentation in GitHub. That’s one place. Also GitHub has natively, the Markdown editor, so with some commands and some things we can put everything there in a way that everybody can take the English document and translate it into their language.
\n\n\n\nFor example I’m doing that, I’m starting to do that in a beta project for the advanced documentation. That’s something we’ve been working on for more or less 8 months. It was a very difficult thing to arrive because it’s been a big problem. A lot of people have been involved, a lot of languages, people from different countries involved, a lot of teams involved. So it has been a very technical challenge in a way.
\n\n\n\n[00:13:00] Nathan Wrigley: Thank you so much. I don’t know if Courtney wants to add anything to that before we move on.
\n\n\n\n[00:13:05] Courtney Robertson: Yeah. So my background, before going full time contributing to WordPress, was that of a teacher. And in the education space within America we have a lot of ESL, English Second Language. So we have a lot of people that don’t primarily speak English, and it’s a disservice to them in the education system to expect them to understand the content on top of having to simultaneously translate a language. That’s a really big learning difficulty.
\n\n\n\nSo I very much wholeheartedly believe in providing access for people to learn WordPress in their own languages. Down to reading the captions on videos. If you’re an English speaker I would encourage you to go over to wordpress.tv, try to find a video that is not in your language, not in your first language, and subject yourselves to reading the captions and think about how fair is that for the rest of the world.
\n\n\n\nSo with that in mind, in Learn WordPress we have a different workflow perhaps than the Docs team. So Docs again think of as the dictionary and the reference manuals, and Learn as the teacher’s spot to be, or the direct learner’s spot to go, if they don’t find reading the manual version to meet their learning style.
\n\n\n\nAnd that’s something that we very much want to consider. Some people need a little more instruction to be able to get the concepts. And so Learn WordPress exists for that, both direct learners and educators. And over there we do not get access to Rosetta sites and instead we rely upon one instance of Learn WordPress.
\n\n\n\nWhereas in the Rosetta sites and what we’ve heard from recent episodes with Vagelis and Piermario, just a few episodes back. We could hear that from what they’ve shared in other parts of the WordPress project there are tools to basically make a whole separate locale instance going on. So if you were in Spain and you wanted to read the same type of content, you would have an entire version of the site that is just for you.
\n\n\n\nWhereas with Learn WordPress, what we have going on is all the languages all smooshed into one site. And what becomes difficult is we don’t have good workflows yet established around if the English language version gets an update, how do I assess what content? I speak only a tiny bit of Spanish and a tiny bit of Latin, of all the things. Good conversation starters.
\n\n\n\nSo you won’t find an easy way to identify even what the other topics are with the same title. Let alone somebody that can’t assess what that content looks like. So we have some locale ambassadors, Piermario is doing a great job with the folks based out of Italy on rounding up some efforts there. Margarita especially, is someone that’s participating with Piermario on identifying the content to be translated into the Italian locale.
\n\n\n\nSo we’re basically duplicating the content, but just in other languages all under the same site. So that’s not the most efficient way and we’re using GitHub as well to do some of this work. We have GitHub issues that have a template. So think of GitHub issues as logging something on the WordPress forums, right? It’s about on par with that. But we prefill what the text of that issue is, and have a workflow to publish that.
\n\n\n\nBut that’s not necessarily in conjunction with what the English version, last update, is or plans of how do we maintain those updates? And then, how do we also look and see if the Docs team did a certain bit of update? And how do we find the polyglots that really like these specific areas? You can see this becomes quite a challenge as we’re looking ahead to Gutenberg phase four with multilingual support natively. We’re still a ways out from that, but you can see where this is something to start untangling and working on internally before we roll it all into Core.
\n\n\n\n[00:16:59] Nathan Wrigley: So it sounds like that this is a spaghetti of things just loosely held together simply by people actually understanding what the processes of the different teams are. But we don’t have this one workflow, which presumably is some kind of goal. But we do have a moment in time, which would be the release of Gutenberg phase four, where hopefully a large proportion of this would be either in progress or completed, because at that point WordPress itself becomes translatable. And I suppose at that point it would be incredibly useful to have this work done.
\n\n\n\nI just want to touch on a couple of things that may have confused the listeners because we’re all speaking, probably in a bit of an echo chamber here. And so there were a couple of things which were mentioned. The first of which was Rosetta, that got dropped a couple of times, and it may be useful for people to actually know what that means. So if anybody’s willing to just very briefly explain what Rosetta is. I mean we know what the stone is and so we get the connection there but, what is that thing in WordPress?
\n\n\n\n[00:17:57] Javier Casares: The Rosetta sites are the locale sites in WordPress. So we have wordpress.org, everything is in English, it’s the main site. Most of everything is there. But, for example, for Spain we have es.wordpress.org, or for Catalan we have ca.wordpress.org or I don’t know for French we have fr.wordpress.org.
\n\n\n\nThose are translation sites from the main site, but not everything is in there. There are the main contents, for example, the download page, everything is in your language. When you download the WordPress from that site, it’s in your language. It includes the translation files. But each site can be managed by different people.
\n\n\n\nFor example, in Spain we usually publish one post every week talking about things. It can be translation from general post, or it can be local things about WordCamps in Spain or whatever. So that’s more or less the thing inside the Rosetta. It’s the technical name, the project, the Rosetta project is the name or the locale site. So that’s more or less the thing.
\n\n\n\n[00:19:12] Nathan Wrigley: Yeah thank you, that’s perfect. That explains it beautifully.
\n\n\n\nThe other thing that was mentioned was eight languages have been put forward as the language is to get us to 80%. So I guess it would be quite nice for the listeners to know what those languages are. I don’t know if a quick Google search needs to be done there, or if anybody’s got that information to hand. But it would be nice to know eight languages initially are.
\n\n\n\nAnd also to know that isn’t the entire scope of the project. That’s more a, let’s get something over the line with these eight languages, as opposed to that’s what we’re doing and that’s all that we’ll ever do.
\n\n\n\n[00:19:44] Javier Casares: Yeah. I have some information from the hosting team, and it was like, okay, I’m going to analyse where and what language are the most downloaded in WordPress. So these languages are not the eight most top languages in the world, they are are the most used in the WordPress ecosystem.
\n\n\n\nSo that’s the main idea behind having those languages as the main ones. German, more or less the 6% in the WordPress scope. English, the 48%, Spanish 7%, French 5%, Italian 4%, Japanese 6%, Portuguese 5%, and Russian 3%. More or less that covers the 80% of the documentation or languages that WordPress has installations.
\n\n\n\n[00:20:34] Nathan Wrigley: Okay thank you, that’s great. That clears that one up.
\n\n\n\nSo I guess we’ve highlighted a problematic past, well not really problematic, it’s just the way the project evolved where everything is done in a unique way depending on the team, or which part of WordPress you’re touching. And maybe this one is for Estela. The enterprise of this podcast really is to highlight some future where we improve things and we take things forward, and you have outlined, I guess a project is the best way to describe it.
\n\n\n\nWhat is your idea? What is it that you want to happen in the future? We don’t have to create timelines or anything, but let’s just imagine that we’re a decade out from now and it’s all been achieved, what would be your north star for all of this?
\n\n\n\n[00:21:16] Estela Rueda: This is where we are, you know where we are working at right now, where we are starting. I started with this Spanish team. They are my trial team. And the only reason why I started with them is because I speak Spanish and it’s easier for me to guide them. We had to start the project in, you know, baby steps, go little by little. The idea is to create a process or a model that we can replicate into other languages.
\n\n\n\nI started with the style guide and how to write documentation in Spanish, because we have many grammar issues with the language. First of all, you know, we have the way we address each other, like formal, informal or we have the language is genderised, completely genderised. Everything is either female or male, there is no neutral gender in Spanish.
\n\n\n\nThere are so many issues that we need to address. And I’m pretty sure other languages have the same or similar problems in their grammar, you know, grammatically speaking. And we need to address those and, how are we going to use them in documentation, in order to make it as neutral as possible and as easy to understand? They’re going to be like, you know, writing rules.
\n\n\n\nThen we have the translation of the sitemap. Now, what I did with the Spanish team, we spent during a WordC amp, a whole contributor day, translating the site map for end user documentation. But I sat the marketing, the polyglots, and the documentation teams together. And I told them, okay, we’re going to translate but I don’t want you to translate literally. I asked marketing, give us words that are searched for, that will help with the SEO of the site. So that way we can localise also, and we can increase the use of the translation of WordPress.
\n\n\n\nAfter that, I guess we’re going to start working into translating documentation. We’re going to create teams, and we’re going to start working on it. My idea is to start some sort of triage hours with teams. And let’s say twice a month, to review what we have written and to continue writing and just that sort of thing.
\n\n\n\nBecause I know that if I leave it to every contributor day for every WordCamp it’s just never going to happen. And this is something that we need. If we want to progress we need to work, you know, a little bit every day, a little bit every day.
\n\n\n\nSo if we don’t put set goals then this is not going to happen. But that’s where I am right now. And I will reach out to the Brazilian team who approached me and may be the second team that I start working with.
\n\n\n\n[00:23:56] Nathan Wrigley: So Estela, just to be clear the intention here is to delve into, in your case, the Spanish language and come up with a rule set, like a workflow. Where, okay, if we receive things in English, these are the set of constraints that we’ve got when we translate into Spanish. So somebody who is new to the team would be able to look at those guidelines, the workflow document, whatever it may be and have a very strong idea of, okay, this is the way to do it. When you’re going from English to Spanish, this is how you do it. Have I understood that correctly?
\n\n\n\n[00:24:29] Estela Rueda: Yes. But those writing rules, or the style guide, I call them the writing rules because that’s what they are. But I want to apply that for every language, just not for the Spanish team. And that style guide has to be according to the language grammar, not to what we like.
\n\n\n\n[00:24:45] Nathan Wrigley: In my head I’m seeing a website when you say that, but of course, you’re talking about the style of the language, in your case the sort of gender that you’ve got to go to and things like that. That’s interesting. And, can you give us some sort of insight into how that’s going? Has it proven to be fairly straightforward to put that workflow together or is it a really thorny thing to unpick?
\n\n\n\n[00:25:03] Estela Rueda: We are just at the beginning of it. I just pitched this idea at the WordCamp in Pontevedra, which was last month, two months ago. And I realised that I need to sit down and start writing. So I gave them some sort of topics that might affect the language, and gave it to the team, to the Spanish team actually.
\n\n\n\nThey are going to start writing the style guide. And I said listen, I write something, ideas that I have and if they are not okay, feel free to go ahead and edit and change them. And let’s see what affects us where. Is it easy? No it’s not easy. It’s going to be difficult because like I said, we have 14 locales, or 14 Rosetta sites, for 14 different versions of Spanish. And we need to come together to a point where, what is the most common use for everybody?
\n\n\n\n[00:26:03] Nathan Wrigley: So this question is going to sound a bit meta, meta in the real sense of the word. You are creating a document which then you will be able to share to other teams in order that they can run their own process. So a silly example, the Latin version of WordPress would need to look at what your team have put together, how to go through the process? Which they can then implement with their own locale.
\n\n\n\n[00:26:28] Estela Rueda: Yes. I will be documenting. Actually this week I’m going to publish a post in the Polyglots team regarding about this step one, step two. So what is the writing style guide and why are we writing it? And what happened to the sitemap and how we came up to what we have.
\n\n\n\n[00:26:44] Nathan Wrigley: So just talking about it on this podcast, it seems like a fairly solvable problem, but of course when you actually apply thought to it, this really is a gigantic plate of spaghetti. There’s an awful lot to be unpicked. There’s an awful lot of work to be done. And I’m just wondering how you feel about this, whether you’re sanguine.
\n\n\n\nAnd it’s not necessarily for Estela, it’s for everybody on the call. How you feel about whether this project is going to be able to ship its aspiration in the, well let’s say, it’s probably a matter of years not months certainly, but probably under a decade, before Gutenberg four comes out.
\n\n\n\nBecause it does sound, on the face of it, it sounds like you’ve got an awful lot of work to be done. If you complete the Spanish, then you’ve got to move on to another one. You’ve got to get people’s buy in, you’ve got to re educate those people who are contributing their time, as translators. They’ve got to be re educated to do it in a different way. How positive, sanguine do you feel that this is achievable?
\n\n\n\n[00:27:41] Courtney Robertson: Nathan, I’ll jump in here. One of the ideas that a coach in my life has shared with me, the motto of this company is, a world that works for everyone with no one left out. And I think about that a lot in the context of open source, and how we make WordPress possible for the whole globe, right?
\n\n\n\nWe are trying to make this tool that we have available, be available for as many people as would have used it, and make the best of that situation. And if we take that backwards to a place where we might need a mindset shift to go on, let’s think about a couple of features in the WordPress project that have rolled out within the last few versions of releases, and the naming that goes into it.
\n\n\n\nI know the community would like to improve how we name things from this outset, so that we don’t have to rename them later. So one example that I thought went really, really well is what became the Command Palette. The initial proposal was to call it something along the lines of Wayfinder. And one of the great insights, because we were able to identify and put this kind of call out across social media and other places, it was not something that was just buried and obscure over in GitHub.
\n\n\n\nIt was raised throughout the community and a lot of folks said, that doesn’t make sense in my language. If you do a direct translation this does not make sense. So it’s not just about translating after the fact, but it’s also about how we name things really even before it gets widely publicly released.
\n\n\n\nAnd so that’s a mindset shift that I think, I’ll say as an English speaker, I really think that we need to experience more of being the second language to truly appreciate and understand the depth of why naming things matters so greatly. The depth of why we need to consider how this will work with other languages. Consider the workflow process. To the point where we’re not just, yes, it will probably remain English forward first.
\n\n\n\nBut to always tuck in mind the processes that go on downstream after we get the thing out in English or what have you. What are we asking our translation folks to do, and how does this impact somebody in a different language? I learned that when Learn was added the navigation menu across all WordPress sites, that the way it had been translated, particularly into Russian, Olga caught this one, it didn’t make sense in the way that it was translated. And so we have to think about these things before we just ship sometimes.
\n\n\n\n[00:30:22] Nathan Wrigley: I have this intuition that if the Command Palette had been called something, even adjacent to the Command Palette, it would have stayed like that. It the controversy of it being so poorly named that led the community to sort of say, well that’s really not the right idea.
\n\n\n\nAnd so sometimes I wonder if backing yourself into a corner is the best way to get attention, if you know what I mean. It’s probably not the desirable outcome but it is possibly a way that, you know, people get enraged by something and so they go out on social media and change happens more quickly.
\n\n\n\nFrom what I’m hearing there Courtney, you’re basically making a moral argument for this. It’s the right thing to do. It doesn’t matter what the goal is, whether we achieve this in a matter of 2 years, 6 years, 10 years, whatever it may be. The journey is the important thing, making the steps now to make this possible is the important point, not the end goal.
\n\n\n\n[00:31:11] Courtney Robertson: Absolutely true. Yes.
\n\n\n\n[00:31:13] Nathan Wrigley: Okay, thank you.
\n\n\n\nSo I guess in order for this to happen, as with many things in WordPress, bodies need to be on the ground. We need people actually doing this work. There’s probably a whole lot of people listening to this who are already committing their time to translations, but there’s probably a lot of people who haven’t. So I guess we need to speak to them.
\n\n\n\nFirstly, I suppose we need to reassure people that if in the future, if this project has wings and takes off and it all goes in this direction, that they will be educated in the new ways of doing things. But also a call out to people who haven’t yet committed their time and feel that they could commit their time. How do they go about doing it?
\n\n\n\nSo let’s tackle it in two parts. The first one, to people who are already translating, will there be education materials? Will there be instruction as to whatever comes out of this whole process?
\n\n\n\n[00:32:04] Javier Casares: Okay. So for me, we will need two different teams. This is not a polyglots project in a way. Obviously everybody will be invited to participate on everything, but I don’t think that the same people translating WordPress plugins, themes or whatever, needs to be the same people translating documentation.
\n\n\n\nSo in a way, at least for me, because I think those are two very different things. As Courtney was saying, translating a plugin for example, or WordPress per se, maybe you need to be a little more literal in the translation. But documentation is different because people need to learn about what you are explaining. So you need to relate with that person.
\n\n\n\nSo in this case that’s the work Estela is doing. You need to know how to communicate to these people, and that’s very different than translating a thing. So for me, it’s not like translating documentation is adapting or doing your own documentation based on one in another language.
\n\n\n\nSo we don’t need to have the same documentation because, cultural things or whatever. Because not everybody in all the countries, in all the languages, use the same tools, the same things. So that’s one thing we need to have in mind. For example, as I was saying at the beginning, I just started leading the advanced administration handbook like one year or two years ago. That’s something Milana gave me as a gift in a way.
\n\n\n\nSo one thing I started, for me this is the pilot in the technical part, not in the documentation part. But now the only thing, or main thing we have in GitHub, in English, everything synchronised with WordPress, is the advanced admin handbook. So for me the next step is to do the technical part for this translation.
\n\n\n\nWe need to check also the technical part because writing right is one thing, but doing the thing is another step we need to check. And that creates a lot of new problems in a way. Because we have new content, we have updates, and we have changes in the documentation. Because it’s not the same changing or creating a new feature, because I don’t know the command palette and everything. It’s a new thing from one, two versions ago.
\n\n\n\nSo we need to create all the documentation. We need to notify everybody in all the languages that we have this new. So we need to translate everything and we need to check with the Polyglots team, how are you going to name the palette in your language and everything? Everybody should be involved in a way, because documenting in all the languages should be a global thing, not a local thing.
\n\n\n\nAnd also, the notifications. We need to have like three levels in the translation part, because we need the translators. We need people doing the translation per se. And we need something like the GTEs. So people can check that the translation is doing fine, the translation is right. And we need project managers because each documentation is not the same. The advanced admin handbook, the end user documentation, the Learn WordPress whatever, the plugins handbook, the themes handbook, developers handbook. Each documentation needs one or two or a team that can control the publication that everything is right.
\n\n\n\nFor example, one thing we talk in WordCamp US was how we are going to relate it’s language? Because we don’t have that now. So if we publish the documentation in Spanish and somebody wants to go from this page to another language, how are we going to do that? Because that’s not something we have now.
\n\n\n\nSo we are trying to solve phase four before we have phase four. So we have a lot of challenge in the organisation and in the technical part. Also with the translation or the organisation about how we are going to talk to people. Because, for example, the Spanish for me is one of the best examples, because in Spain we have a more direct, we talk to people and in Latin American they talk in another way.
\n\n\n\nSo we need to find like a common ground because we cannot maintain the Spanish documentation in 12 or 15 different ways. So we need to create a standard or international Spanish. That’s something that more or less exists, but we cannot create a lot of different documentation. So we need to have that in the translation part. We need to have that documentation, that style guide. We need to have one international Spanish because we cannot maintain, we don’t have a lot of people maintaining some little languages or whatever, because it’s not possible right now in the WordPress ecosystem.
\n\n\n\n[00:37:35] Nathan Wrigley: Thank you. That was really insightful. I got an awful lot out of that. I just have a little question off the back of that. So, is the intention then to build I guess more or less software to take care of this notification problem? And obviously there’s a lot more than notifications. There’s, you know, the work that needs to be done, and perhaps the order that it needs to be done, and who it’s going to be assigned to.
\n\n\n\nIs the intention to have that as, if you like, paper based web pages or is the intention to have a piece of software that people can log into and assign themselves tasks, and offload tasks, and check things out, and then finally hit publish if something meets all of the different criteria? And it sounded like it was partially done but I don’t know if that’s falling on your shoulders Javier. Just a little guidance around that.
\n\n\n\n[00:38:18] Javier Casares: Yeah. that was one of the main things we have pending. We started talking about this in WordCamp US, in the contributor day. Right now, for example, for the advanced admin handbook I’m going to lead everything in the Spanish part because I think we need to test everything, and I’m going to test this development part or whatever we are doing. I know Milana is doing it for the end user. She’s creating like teams in GitHub and doing actions and everything.
\n\n\n\nShe’s starting to automatising more or less the notifications and everything. So the main idea is we will have translation teams. So for example, the Spanish translation team, or the German translation team. And you will apply in those teams. And when something changed, in the English part, you will get a notification.
\n\n\n\nFor example, there is a new page. This document has changed because of whatever. So we need to inform people that we need a new version, or to update something, or to add something to the documentation. And then we need another step that when somebody translates something, it needs some checking or review or whatever. So we need like the GTEs in Polyglots more or less, the general translation editor. So people that know imperfection, the style guide or whatever. And they will check that this document is ready to be published.
\n\n\n\nThis is something we start talking and I think it will be something good for the project, is to create versions for the documentation. When we have 6.4 or 6.5 or whatever version, we can create a new batch of documentation, and we can create the 1.2 version of the end user documentation. So we can have a history of everything that changed, and we don’t need to put the documentation every day.
\n\n\n\nSo we can have a weekly or a monthly updating. So it’s control, it’s more like the WordPress. So everybody will know where the new version is going to be published. If you need to add this document, priorities or whatever. So that’s something we are working on now, but there are a lot of people involved testing different things.
\n\n\n\nSo for example, Estela is doing the documentation for Spanish. I’m testing the technical part. Milana is testing this notification system. So we need to check everything because we don’t really know if this project is going to be real, but we think it will be. But we need to check everything, and we need to do this in parallel because we cannot wait to have all the work from one person to do the next step.
\n\n\n\nI think that’s something we are going to work on in the next contributor days in some places. At least in Spain I’m going to try to do this. And for example, that’s my next step in the documentation part, is going to test this technical part. How are we going to organise everything?
\n\n\n\nSo everybody is invited to participate. So if anybody wants to check things, we can talk. Probably in the Polyglots or the documentation channel in Slack. So I think a lot of people are doing the right steps right now, and before 2024 we have some pilot or something finished.
\n\n\n\n[00:42:02] Nathan Wrigley: If you’ve ever been involved in creating software, you’ll know that the devil is in the detail. And although it’s easy to say what you’ve just said, I suspect that it will be fiendishly challenging.
\n\n\n\nFirstly, good luck, I hope that your endeavors pay off. And it does sound like you would desperately want some people to cast their eyes over this.
\n\n\n\nAnd we’ll get onto that in a moment. We’ll figure out a way where people can get in touch if they wish to. But you’re clearly all good people. You have the, what I’m going to describe as the right moral intentions here. You are giving up lots of your time for this worthy cause. Nobody could deny that this is a fabulous endeavor.
\n\n\n\nBut for people who are listening to this and sitting on the fence, thinking to themselves, what would I get out of translating? It’s a bit of an ephemeral question really, but I’m wondering if you could portray or explain to us, what do you get out of this? Apart from the fact that you’ve translated a software project, that much is obvious. But, do you get like a warm, fuzzy feeling out of this? Does it make you feel good? Is there a good community? Are there nice people sitting behind translation that you’ve become friends with? I’m trying to offer a path for people who kind of want to commit but haven’t committed, because they just see it as there’s more things to do on my plate each week.
\n\n\n\n[00:43:13] Estela Rueda: I think that friendships, they just come. They are just like part of it. But that’s not the reason why I do it. For me it’s more about empowering people. I think that, you know, if I can translate more of the documentation in another language then there will be more plugin developers, or theme developers, or agencies in that country. And then you will empower people. You will empower more people because they will be able to start their own businesses, you know, create their own little plugins and start small like we all did at some point, and then become bigger and bigger.
\n\n\n\nI don’t know, I kind of took into that Matt’s dream about a hundred years. I think that if we open everything up for more countries, more cultures to join, then WordPress will be bigger and bigger and more people will use it.
\n\n\n\n[00:44:10] Nathan Wrigley: Thank you so much, Courtney. I think maybe you want to chip in there.
\n\n\n\n[00:44:13] Courtney Robertson: I really love solving complex puzzles. And so if we look, devils in the details. Relaying communications between docs and training becomes pretty important. So not only do we want to leverage Milana’s system about the GitHub actions, some of that automation work that can notify people in other languages. But also the communication between the teams about the same topics or the areas in which our topics overlap. It’s a fun thing for me to do that.
\n\n\n\nBut then in addition, as I kind of look more broadly like Estela, I firmly believe in empowering others. And that’s really what open source and the four freedoms give us. You are free to do what you would like with this thing.
\n\n\n\nSo to make that possible my method is to solve big problems, I guess. To work on these interesting challenges so that more people can leverage what’s going on and get involved along the way, and have mentors and others to connect with. Because for every time that I felt personally like I didn’t know what was going on, or I didn’t understand the value that I brought, or understand how I could start contributing with something small, I want to remove those barriers for other people. I want to make their lives a lot better from that process.
\n\n\n\n[00:45:34] Nathan Wrigley: What a fabulous set of answers. Thank you so much.
\n\n\n\nWe’re running short of time. I guess the only thing that we should say before we wrap up is to give out a shout to people who are sitting on the fence, who haven’t contributed so far. What is the best way, the quickest route to finding out more? Is there a particular page that you would highlight more than any others? Is there a particular venue to go to? Is this a contributor day kind of thing? What would you recommend? We could take that one at a time. So let’s start with, well let’s go back to Courtney.
\n\n\n\n[00:46:05] Courtney Robertson: Sure. Since our process looks a little bit different than what you see in Docs, for instance, I would encourage folks to swing by the training team. You can find our main site at make. wordpress. org slash training. There is a handbook in our top navigation area and inside of that has some information on how to get started with content localization. I’ll make sure that we have all those show notes. As well as a GitHub issue to log if you want to take part in that translation effort.
\n\n\n\nAnd for those inside the WordPress project that are really skilled with amazing things like GitHub Actions, if you understand how to make GitHub automate some stuff, there is a channel if you search for GitHub inside of the channels area, you’ll find a channel where we share tips and tools about GitHub activity.
\n\n\n\n[00:46:51] Nathan Wrigley: Thank you so much, Courtney. Estela, anything that you wanted to add?
\n\n\n\n[00:46:55] Estela Rueda: You can go into documentation Slack channels. We meet on Tuesdays, 2 PM UTC, and just join us. And then we can talk about it. We are trying to look now for Documentation writers, but they are also bilingual. So they do need to dominate at least one word so that they can help us in the future once we move into their own language.
\n\n\n\nWe have, actually the documentation team is, most of us are non English speakers. English is not our first language, so we have a lot of people that speak other languages, and they do help when it’s necessary. Now, we have several posts. I’m posting, like I said, I’m documenting what I’m doing, and we’ll be documenting it both in Documentation and polyglots, and just pick it up from there. Join the polyglots team. They are open to every language, or every Rosetta side, locale team. They all need contributors. They all need translators. So that’s the best way.
\n\n\n\n[00:48:01] Nathan Wrigley: Thank you so much. And Javier, if you’ve got anything to add there.
\n\n\n\n[00:48:05] Javier Casares: Yeah. In my case if anybody wants to check the most technical part or be involved in the testing, they can ask me directly in Slack. Because right now it’s like I’m doing the test alone. I probably when I do the main testing, I will explain everything because we did the proposal in the make.wordpress.org slash project. You can look for a proposal, documentation, translation, localization.
\n\n\n\nThat’s the main document explaining everything. It explains why we are doing this. How we are going to do that. I think, right now, Estela, Courtney, Milana, and I are the ones involved. So another way is to, at least for this project, is to contact us, and we will try to put you in the right place to contribute.
\n\n\n\nYeah, we are always open to help people. So another way is to contact directly to us.
\n\n\n\n[00:49:09] Nathan Wrigley: Well, Thank you so much, the three of you, for joining us today. Thank you Courtney, Estela, and Javier. I really appreciate it. Obviously, a very complicated set of challenges to come, but hopefully with your and other people’s contributions, WordPress will be readable by all the world. Thank you so much for your contributions today.
\nOn the podcast today we have Estela Rueda, Courtney Robertson and Javier Casares.
\n\n\n\nCourtney is a former teacher who now focuses on contributing to WordPress. With a background in education, she understands the challenges faced by English Second Language (ESL) learners in the American education system. She’s passionate about providing access to WordPress in multiple languages, as she believes it is unfair to expect non-English speakers to simultaneously translate content and understand it.
\n\n\n\nEstela is a language enthusiast who has spent years navigating the challenges of website localization. As a member of the WordPress community, Estela has come across the intricacies of language differences and the need for accurate translation in various Spanish locales. With 14 different Spanish locales to handle, Estela’s expertise in understanding the subtle nuances and localizations of each language variation has been indispensable.
\n\n\n\nJavier Casares is a dedicated member of the WordPress community. With expertise in creating documentation, Javier has been instrumental in developing handbooks for various sites. However, there have been some technical challenges. Despite these obstacles, Javier, as you will hear, remains committed to addressing and solving the documentation issues at hand.
\n\n\n\nThis episode covers the important topic of translations and making WordPress documentation more accessible to people worldwide. Our guests bring a wealth of knowledge and experience to the table as they discuss the complexities and challenges of language translation in the WordPress ecosystem.
\n\n\n\nWe start by highlighting challenges posed in translating WordPress, such as the tangled processes currently in place, as well as more language focussed topics. We talk about the extensive collaborative effort involved in translating WordPress and the plans to expand translation efforts to documentation with the help of dedicated teams.
\n\n\n\nWe get into how contributors might need to rethink the way that many of the current translation processes are structured. We discuss the different approaches needed for translating plugins and themes versus documentation. We touch upon how technical aspects of these processes, such as content creation and updates, also pose significant challenges.
\n\n\n\nAll three guests stress the importance of global involvement in translation efforts, including translators, reviewers, and project managers. They advocate for the development of standardised style guides for each language to maintain consistency, and they explore the possibility of creating software or tools to manage translation tasks.
\n\n\n\nCourtney, Estela, and Javier all acknowledge the challenges ahead, but express optimism that their ideas will help make WordPress accessible for all. Communicating how WordPress is built and how it works is an endeavour tightly aligned with the project’s overall mission of democratising publishing.
\n\n\n\nWe want to offer non-English speaking people the possibility to access all the WordPress documentation in their language. To accomplish that we need to translate all the actual documentation at HelpHub, DevHub, Learn WordPress and some Handbooks.
\n\n\n\nBut, the problems are not to do the translations per sé, but where to put that in each language, how to get the updates from the English primary documentation, and then how to maintain everything in place.
\n\n\n\nFirst, we need to know where are we putting the documentation, because this project cannot wait until Gutenberg Phase 4. This means that Local Communities should be involved here (for example, where are we putting the documentation in Spanish? es.wordpress.org/documentation, developer.es.wordpress.org?)
\n\n\n\nAfter having the right place… how are we going to know if something changes? The best way is probably using the same way we are translating right now: translate.wordpress.org, (GlotPress). If we can use this platform, each page can be translated and, when arrived to the 90% threshold, it will be shown in the local language page.
\n\n\n\nDiscussion for a proposal for WP.org content translation and localization
\n\n\n\nNew look, new site, new HelpHub
\n\n\n\n\n\n\n\n\n\n\n\nGitHub… Issue: Content Translation Template
\n\n\n\nProposal: Documentation translation / localization
\n\n\n\nWordPress Advanced Administration Handbook
\n\n\n\n\n\n\n\nPrevious podcast episodes with Piermario and Vagelis
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 15:15:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"Do The Woo Community: Do the Woo Day 2 Recap, WooSesh 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77699\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://dothewoo.io/do-the-woo-day-2-recap-woosesh-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:370:\"Conversations around AI and customer support, Amazon Pay, personalization and privacy in ecommerce and shipping trends.
\n>> The post Do the Woo Day 2 Recap, WooSesh 2023 appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 12:23:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"HeroPress: From Sci-fi Dreams to Software Reality\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=5985\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:150:\"https://heropress.com/essays/from-sci-fi-dreams-to-software-reality/#utm_source=rss&utm_medium=rss&utm_campaign=from-sci-fi-dreams-to-software-reality\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7038:\"Growing up, my family didn’t have much. Yet, a quote always resonated with me: “If you’re born poor, it’s not your fault. But if you die poor, it’s your fault.” My humble beginnings never deterred my aspirations.
\n\n\n\nAs a child, my exposure to technology was limited. In our village, neither schools nor homes had computers or mobile phones. My fascination with technology was sparked by sci-fi movies I watched on television, where characters operated these machines called “computers.”. That first moment when I laid my eyes on a computer, I knew my life was about to change. The real encounter with a computer came in 2006 when a neighbor purchased one.
\n\n\n\nIn 2008, My family moved to the town and it opened up a world of opportunities. Later that year a friend introduced me to a Cyber Café, where for just 20 Indian Rupees (24 cents US), I could play games for an hour. After saving the money for two weeks, I visited the café for the first time. Over time, my interest shifted from playing games to exploring the computer itself. It was a Windows XP machine, and I recall being intrigued by its features. This exploration continued almost every month for the next two to three years.
\n\n\n\nBy 2011, I had become proficient with the internet and was familiar with operating systems like Windows, Linux, and Mac. That year, my father bought me my first phone, a Nokia 7210 Supernova. While it wasn’t a smartphone, it sparked my curiosity about the creation of software and websites.
\n\n\n\n\n\n\n\n\nI researched “how to make a website” and encountered HTML and CSS.
\n
Initially overwhelmed by the complexity, I decided to push forward, and by the end of the year, I had launched my first website using an online builder and my Nokia phone.
\n\n\n\nMy passion for technology only grew from there. I self-taught programming languages like JavaScript, PHP, Python, Java, C, and C++. I also learned computer hardware maintenance and served as a go-to tech helper in my community. Impressively, I became a full-time Teacher and SysAdmin for a local school, managing five servers and around a hundred computers. All of this knowledge came from internet tutorials.
\n\n\n\nI truly developed a passion for web technologies.
\n\n\n\n\n\n\n\n\nMy first encounter with WordPress.com in 2012 was underwhelming, as I perceived it to be just another blogging platform like blogger.com.
\n
Yet, a few months later, my discovery of WordPress.org profoundly shifted my perspective. By 2014, I had set up my own WordPress blog. Despite juggling a demanding college schedule and coursework, I consistently set aside time each night to keep up with the latest developments in WordPress and other web technologies. Much of what I’ve learned comes from the generosity of online communities. In gratitude, I’m eager to share my own experiences, hoping to guide others on similar paths.
\n\n\n\nBeing a teacher was a fulfilling and enjoyable experience. One of the highlights for me was the opportunity to share my knowledge with the children and witness their growth and development. Teaching stands out as one of the most rewarding endeavors of my life.
\n\n\n\nDriven by a strong desire to delve deeper into web technology, I realized I had become too comfortable in my current role, working as a Teacher. In October 2020, I made the difficult decision to leave my teaching position and venture into the realm of Web Technologies. This decision did not come easily, as I had no alternate source of income and my savings were limited, only sufficient to last a few months. For the next three months, I found myself unemployed, but I utilized this time to extensively explore web technology, with a particular focus on WordPress.
\n\n\n\nDespite grappling with imposter syndrome at the time, I was completely unaware of its impact on me.
\n\n\n\n\n\n\n\n\nI found myself reluctant to apply for job positions at various companies, filled with doubt about my abilities, and questioning whether I had acquired sufficient knowledge or was proficient enough to undertake the work.
\n
What I failed to realize then was that all I needed was a little push—a smidgen of encouragement—to help me advance with the skills and knowledge I possessed. I am immensely grateful to Topher DeRosia for providing me with that much-needed push. His encouragement was priceless, and it spurred me to send my resume to three different WordPress-related companies. To my delight and relief, I received a response from one of them.
\n\n\n\nFrom those early days in the cyber café to securing a position at rtCamp, my journey has been anything but ordinary. In light of my experiences and the passion I developed from my early encounters with technology, I secured a position as a WordPress developer at rtCamp in February 2021. This was a significant milestone for me, especially recalling my days without a computer in my village and the hours spent in cyber cafes learning the complexities of the digital world. The journey to this point was challenging, especially since I navigated it largely on my own, without a mentor or assistance from anyone./
\n\n\n\nNow, working full-time with WordPress, not only am I able to comfortably cover my bills, but I can also provide for my family.
\n\n\n\n\n\n\n\n\nMost crucially, it has enabled me to fund my brother’s necessary neurological treatments.
\n
I’m delighted to share that he has successfully recuperated and no longer requires medication.
\n\n\n\nThroughout this path, I’ve faced countless challenges, sleepless nights, and stress. Yet, one truth remains clear: moving forward, no matter the obstacle. Failures are just milestones, not endpoints. With perseverance, success is not just a destination but a beautiful journey. If you’re facing doubts about your abilities, remember, we all start somewhere. It’s the perseverance that counts.
\nThe post From Sci-fi Dreams to Software Reality appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 00:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Tremi Dkhar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"WPTavern: WooCommerce Rebrands as Woo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150841\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/woocommerce-rebrands-as-woo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2569:\"WooCommerce is rebranding to “Woo,” a shorter, more playful version of the company name that many customers are already using. Automattic acquired WooCommerce in 2015, along with WooThemes. The open source commerce platform now powers more than 4.4 million live websites, including 33% of the top 1 million online stores.
\n\n\n\nThe rebranding extends to the Woo Marketplace, WooExperts program, and all other aspects of the Woo experience. It also includes a migration of WooCommerce.com to the woo.com domain.
\n\n\n\n“‘Woo’ is how many loyal customers have referred to us for years. And now we’re leaning into that name for our company and brand,” Woo VP of Creative and Communications David Callaway said. “It’s a fun, punchy name that shows how excited we are to empower success for merchants and developers. Switching to Woo.com is part of this larger strategy.
\n\n\n\n“The move to Woo also allows us to standardize and streamline the names of our products and services. For example, we recently renamed WooCommerce Payments to WooPayments, and we’re gradually changing other product names to support this simplified naming system and better connect our core software, extensions, and programs.”
\n\n\n\nCallaway also noted that while Woo is how they refer to the brand and company, WooCommerce is the open-source e-commerce platform for WordPress, Woo’s core product.
\n\n\n\nWoo Express is another recently launched product that already bears the shorter name. During the 2023 State of the Woo, delivered at WooSesh, the team highlighted a few milestones for Woo Express, the company’s all-in-one Woo plan hosted on WordPress.com’s infrastructure. It launched in 2023 as what the team described as “Woo’s biggest bet ever.” Free trials began in April 2023 and by July 2023, Woo Express had more than 1,000 customers. It features a new onboarding flow and store personlization experience for merchants, with a setup guide and recommendation engine powered by an AI-driven assistant.
\n\n\n\nWoo customers will not be affected by the name change, although merchants may see a note about it in their dashboard or emails. No action is required from store owners.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 31 Oct 2023 12:51:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:43;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"Do The Woo Community: Do the … Woo dot Com\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77718\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://dothewoo.io/do-the-woo-dot-com/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:335:\"Inside Woo. Today the WooCommerce site becomes Woo.com as a strategic part of their branding and product line.
\n>> The post Do the … Woo dot Com appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 31 Oct 2023 12:12:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:44;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"Do The Woo Community: Do the Woo Day 1 Recap, WooSesh 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77694\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://dothewoo.io/do-the-woo-day-1-recap-woosesh-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:372:\"Day one started with State of the Woo, conversations on open source and hosting, scalable ecommerce and website security.
\n>> The post Do the Woo Day 1 Recap, WooSesh 2023 appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 31 Oct 2023 10:54:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"BuddyPress: BuddyPress 11.4.0 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=331729\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://buddypress.org/2023/10/buddypress-11-4-0-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1054:\"Immediately available is BuddyPress 11.4.0. This maintenance release fixes 1 bug and adds a new Admin Notifications feature to prepare the next BuddyPress major version (12.0.0). For details on the changes, please read the 11.4.0 release notes.
\n\n\n\nUpdate to BuddyPress 11.4.0 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.
\n\n\n\n\n\n\n\nvapvarun, martenw, dcavins & imath.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Oct 2023 20:58:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WPTavern: WP Data Dashboard Tracks WordPress.org Themes Ecosystem\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150809\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://wptavern.com/wp-data-dashboard-tracks-wordpress-org-themes-ecosystem\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7244:\"Munich-based digital agency owner Hendrik Luehrsen has been tracking the usage of themes with the FSE tag (block themes) using a spreadsheet that pulls in data from the WordPress.org API. Wrangling the data in a spreadsheet became too cumbersome, so Luehrsen launched WP Data Dashboard over the weekend as a “centralized hub for exploring, analyzing, and visualizing data across the WordPress landscape.”
\n\n\n\nThe new website is currently tracking 6,017 themes hosted on WordPress.org with 250 snapshots. It offers stats and data-based insights for those interested in getting a bird’s-eye view on themes hosted in the official directory.
\n\n\n\n\n\n\n\n\n\n\n\n“Right now, the WP Data Dashboard has one main function: It crawls the WordPress Theme Repo (API) and crunches the numbers to identify trends,” Luehrsen said. “With the data stored in my own database, I can analyze and combine it in exciting new ways.”
\n\n\n\nWP Data Dashboard has two unique stats that are interpretations of the data available. The first is a “Usage Score,” which is calculated based on a theme’s active installs vs. total downloads:
\n\n\n\n\n\n\n\n\nA high score indicates a theme that not only has been downloaded frequently but also remains actively installed on many sites. The score undergoes a significant decay if the proportion of active installs to downloads is low, indicating that while the theme might be frequently downloaded, it’s not retained by users. This metric provides insight into both the initial appeal of a theme and its lasting utility to users.
\n
The second unique stat is a “Diversity Score,” which compares the downloads of a single theme author to the overall theme directory (or a tag) and scales that value from 0 to 100:
\n\n\n\n\n\n\n\n\nA high score indicates that downloads are spread across many authors, suggesting a diverse and competitive marketplace. On the other hand, a low score suggests that a few authors dominate the downloads, indicating less diversity. This metric provides insight into the variety of theme offerings and the balance of power in the theme marketplace.
\n
The Usage Scores can be seen on the List page, which is an index of all the themes, as well as on the Tag pages.
\n\n\n\n\n\n\n\nThe Diversity Score is only displayed on the Stats page as a percentage representing the entire WordPress.org ecosystem. The Diversity score goes up when the stats are calculated without the default themes, which get a large number of downloads from the same “WordPress.org” author every year.
\n\n\n\n\n\n\n\nIn a thread on X, Luehrsen highlighted a few data points he has extracted so far from the dashboard.
\n\n\n\n“Fun fact: Did you know that the most downloaded themes ever are Twenty Seventeen, Twenty Fifteen, and Astra?” he said. “Each has crossed over 10 million downloads! But only Astra managed to retain its users and remains today as one of the most widely used themes.
\n\n\n\n“What’s somewhat surprising is the decline in downloads for the newer default themes. While Twenty-Twenty garnered over 8 million downloads, Twenty Twenty-One managed only 6 million, and Twenty Twenty-Two a mere 3 million.”
\n\n\n\nThis may be related to the slow adoption of block themes, which still appears to be stagnating at the end of October. The number of block theme active installs declined from August to September, but is now inching its way back up to previous numbers.
\n\n\n\n\n\n\n\n\n\n\n\n“Did you know that only 2% of overall theme downloads come from themes tagged as ‘Full Site Editing‘?” Luehrsen said. “Given that they’re relatively new, it’s not too surprising!”
\n\n\n\nWhen asked if he has considered trying to include numbers for themes like Elementor and Divi, which make up a large segment of the commercial theme market, Luehrsen said he would like to include external data but the compatibility of that data would be very limited, which in turn limits comparability with WordPress.org-hosted themes.
\n\n\n\n \n\n\n\nThe WP Data Dashboard is a useful way to track trends in WordPress.org themes over time, and the site appears primed to add data for plugins at a future date. It would be even more helpful if Luehrsen could make some of the calculated data available for visitors at a glance, such as 2% of overall theme downloads coming from Full Site Editing tagged themes. There are a lot of ways this data could be visualized with graphs and charts in the future, as the database adds more information over time.
\n\n\n\nThe project is hosted on GitHub under a GPL license, so anyone can dig deeper into the code to see how it works or submit contributions to extend its capabilities.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Oct 2023 20:30:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"WordPress.org blog: WP Briefing: Episode 65: Little Sun Success\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16227\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://wordpress.org/news/2023/10/episode-65-little-sun-success/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:21522:\"Join WordPress Executive Director Josepha Haden Chomphosy as she looks at a recent WordPress success story, the clean energy solution Little Sun, and learns about their WordPress story.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Special Guest: Romane Guégan
Special Guest: Ashley Mrozek
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, I’ve got a special guest with me. I have here a couple of folks from Little Sun, a nonprofit organization that recently moved its entire online presence to WordPress. And we’re talking everything from their mission statement and donations all the way to their blog and shop.
\n\n\n\nWelcome both to the WordPress Briefing.
\n\n\n\n[00:00:59] Ashley: Thank you.
\n\n\n\n[00:01:00] Romane: Thank you.
\n\n\n\n[00:01:01] Josepha: We have with us Little Sun today. Can you start by introducing yourselves and your organization? Just tell us a little bit about what you all do.
\n\n\n\n[00:01:08] Romane: Hi, my name is Romane Guégan. I’m a Senior Press and Communications Manager at Little Sun.
\n\n\n\n[00:01:14] Ashley: And I am Ashley Mrozek. I’m the Senior Digital Manager.
\n\n\n\n[00:01:17] Josepha: So what does Little Sun do for the folks who are listening and maybe don’t know about it yet?
\n\n\n\n[00:01:22] Romane: Little Sun brings full power and light to communities that live off the grid, with the focus on sub-Saharan Africa because most of the people who lack access to electricity and need them. And we also inspire people to take climate action globally.
\n\n\n\n[00:01:39] Ashley: So access to solar energy helps kids who don’t have electricity and study at night. They can complete their homework at night. If their schools are in a more rural area, they will have a light to kind of guide them back home.
\n\n\n\nWe also work on a lot of electric vocation projects and hospitals. So we’re, we’re kind of supporting labors that are, are taking place in the evening, after the sun goes down, among other things.
\n\n\n\n[00:02:07] Josepha: Yeah. It’s, I, I think that that is one of the things that folks, probably most of my listeners, probably take for granted, like the easy access to light. And as we all know, the sun is around a lot. And so that is one of our most readily available resources other than potentially wind power. But I think that that is a great mission. And I really think that that’s wonderful work that y’all are doing.
\n\n\n\nSo, is there a particular reason that you focus on sub-Saharan Africa? Is that where you find a majority of people who don’t have access to that kind of resource are?
\n\n\n\n[00:02:43] Romane: Yeah. 70% of those people actually need in sub-Saharan Africa, where solar is actually a viable source of energy. Actually, it’s only 1% of solar, of the solar capital of the generation when we actually deliver solar energy there because there is so much potential.
\n\n\n\n[00:03:04] Josepha: That’s amazing. So you said that you all were funded in 2012. I imagine that your business has evolved over time. So, obviously, you all are WordPress users. That’s why we have you here with us today. But before we get into the questions about WordPress itself. Why don’t you tell us a bit about how your business needs evolved over time and how you wound up needing a solution that did use WordPress?
\n\n\n\n[00:03:31] Ashley: So I would say our focus and kind of the different initiatives that we’ve taken on since 2012 have shifted a lot based on various reasons, where our donors are, where we’ve kind of found the most need, and where we can be the most impactful.
\n\n\n\nAnd I think as we go into those new geographies, our online presence has become more and more important.
\n\n\n\n[00:03:55] Josepha: So, before you all switched to WordPress, I understand that you had several sites that you had to merge into one. And so I assume that as you evolved the business and your focus has changed, you realized you needed something a bit more streamlined. So, how was that transition, that migration from a lot of different sites to one big site?
\n\n\n\n[00:04:17] Romane: Yeah, because we started as a global project. And then, with the time, we evolved, actually also getting new donations. And in the past, we used to have one website where we have our webshop and our mission, our vision, all of our project descriptions.
\n\n\n\nBut then we had another website only for the foundation. And then you had another foundation in the U.S. So it was the question, okay, how do we put everything together? So we actually switched from littlesun.com to littlesun.org with WordPress, and it was amazing to see how we managed with the team to create an ecosystem approach, including impact, but also sales, and fundraising.
\n\n\n\n[00:05:02] Josepha: That was a big footprint that you all had, and you kind of consolidated it into one. And for all of our folks listening on the podcast, I’m going to include some links, not only to their site but then also to a few other things that we’ve mentioned in here today. So, since you made that change, how has it, how has that impacted the way that you all work with your site or with your online presence?
\n\n\n\n[00:05:27] Ashley: Yeah, I think using WordPress and having access to WordPress has been hugely valuable for us. We’re a small team, we’re a nonprofit, so it is pretty scrappy. Everyone is kind of doing a lot of different things. We don’t have a dedicated development team. And so being able to easily customize our pages and create new landing pages or make adjustments on the site without that development help has been valuable.
\n\n\n\n[00:05:55] Josepha: Yeah, so you don’t have a developer team now. Did you have a developer team when you had all the sites?
\n\n\n\n[00:06:01] Romane: We just still work with freelancers.
\n\n\n\n[00:06:03] Josepha: Okay, yeah. I am also not a developer, for what it’s worth, and have been working with nonprofits for a while. And I understand that problem where you have all these things you need to do and want to do, but there are also things you absolutely have to focus on in order to make your mission possible and your vision come true.
\n\n\n\n[00:06:23] Ashley: Yeah, and I think, I think WordPress has given us a lot more, like a lot more flexibility to kind of produce new content quickly. And because of that, it’s just been a lot more efficient, too, for us, you know.
\n\n\n\n[00:06:38] Josepha: And you all are using Blocks? Are you, like, the best Block builders?
\n\n\n\n[00:06:42] Romane: Yeah, I love Blocks.
\n\n\n\n[00:06:43] Josepha: Blocks are a fairly new innovation for the history of WordPress. WordPress has been around for 20 years, so we’re a nice, mature project. And we’ve really only had blocks as a functional part of the CMS for probably the last five or so. We’ve been working on the project a little bit longer. And it has been fascinating to me, like, in my own work that I have done with WordPress, kind of outside of my work with the project, to see, like, how much autonomy you get to have back as somebody who is not a developer, maybe isn’t a designer, but you do know exactly what you need to have on your site today, right?
\n\n\n\nAnd having to stop and find a freelancer or stop and find some set of developers who can make those changes. For me, when I was specifically working on nonprofit stuff. That was always kind of a moment where I was like, well, I guess I’ll just go to Facebook and put that on there or something because I was faster than trying to find someone to come help you. And so, I’m so glad you love the block.
\n\n\n\n[00:07:48] Ashley: We’ve created many a landing page.
\n\n\n\n[00:07:50] Josepha: Also, your site is adorable, and your brand is adorable, in case no one’s mentioned that lately. Super cute. Super cute.
\n\n\n\n[00:07:58] Josepha: So, we’ve talked about how you kind of took a bunch of stuff and made it into one big thing and how that’s been easier for you all to manage it. But from the standpoint of just, like, somebody who’s running a nonprofit, someone who’s running an organization, how has that transition been for your team? I know you said you don’t have a huge team, but was the move toward WordPress a net benefit over time, or was it immediately beneficial? Like, how has that been for your team?
\n\n\n\n[00:08:27] Romane: So what’s interesting actually is that we have a team that is spread also all over the world. And so we have teams in Berlin and in U.S., and New York. In Zambia, too. What was really interesting was how people identify to the new website because now we have to really think, okay, what is the content we want people to see, but also we want our critics to see. And so it kind of unified all of our content at Little Sun. And it was much more like much easier to understand afterwards.
\n\n\n\n[00:09:03] Josepha: Yeah.
\n\n\n\n[00:09:04] Romane: And it was because we also work at the intersection of creative communications, impacts, fundraising, technology, and to be able to put everything and have it on the front. And then have the stories to tell the stories from sub-Saharan Africa, from universities who got either a Little Sun lamps or solar systems, and then we have the donation page, so basically everything could be integrated in a super easy way, and it could target different audiences easily, either it’s someone who wants to partner with us, or a donor, or just someone who wants to be part of our solar training.
\n\n\n\n[00:09:46] Josepha: Yeah, and I mean, I think that no one will be surprised to hear that if you have multiple things that you have to get everybody to, it really increases the amount of marketing that you have to accomplish, rather than having one place for everyone to go too, and they can see everything that they might want once they arrive. So, that’s wonderful.
\n\n\n\n[00:10:06] Ashley: I think I was just going to say, or kind of echo what Romane said about the fact that we have so many different audiences, we have partners, we have donors, we have people who are just coming to learn about solar energy, or who are interested in purchasing a lamp. I think prior to this, it was a little bit confusing for those different audiences to kind of navigate to where they were intended to go to on the site, and now it’s much more cohesive. And we often hear that from people where it’s like, it’s quite easy to, to kind to find what they need to find on the site.
\n\n\n\n[00:10:39] Josepha: I define the WordPress community as anyone who is using WordPress, regardless of whether they know it or not. And so you all, in my mind, are part of the WordPress Community. And I just wondered if being part of that community has changed your approach to the way that you manage your content online or the way that you have chosen work with your business as like an online entity that also does on-the-ground, in-person thing?
\n\n\n\n[00:11:06] Ashley: I think definitely. I think we’re kind of going back to what I said before. I think we’re much more efficient now. I think in the past, it’s the idea of, like, well, getting this web page live or publishing this is going to be, you know, we have to think about a huge timeline, that’s, is going to require a lot of resourcing, a lot of different types of expertise and people, and everything now feels like something that we can, we can launch pretty immediately, which is really wonderful too.
\n\n\n\nI would also say just like being a part of the WordPress community too. It’s the sort of support that we’ve gotten from your team. It’s always really tailored. And I think as a nonprofit working with a, like, a much bigger business, you can be apprehensive sometimes, feeling like you won’t really get that personalized support.
\n\n\n\nAnd I think that’s something that’s been so nice with WordPress. Is really feeling like the people we’re working with are understanding our business and taking the time to understand our needs. And I think that makes us think differently about our online presence as well because then we feel like we have that additional support, which is great.
\n\n\n\n[00:12:12] Josepha: I’m always a fan of hearing that people who are passionate about WordPress are also passionate about helping others with WordPress. That’s one of my favorite things about us. That’s not true. I have like 25 favorite things about us. And so I need to stop saying that I have one favorite, but I never will.
\n\n\n\nOkay, well, do you all have any last thoughts that you just want to share with me or podcast listeners that we have?
\n\n\n\n[00:12:36] Ashley: Yeah, I think the, the plugins and integrations have been really useful for us. I think it can be really intimidating to bring on, like, a new tech solution or tool and feel like everything that you are already working with or have is going to become outdated or obsolete in some way. And I think it’s just been really nice to work with WordPress and have all of those transitions be really seamless for everything to connect really well. Yeah, I think that’s been. That’s hugely helpful too.
\n\n\n\n[00:13:07] Josepha: So, was that part of the decision-making process? Like, do I know that this software will be around in the future so that you’re making an investment in the site now and know that it’s going to hang around now you can find people help? Like, was that part of the decision-making process?
\n\n\n\n[00:13:21] Ashley: I think so. I mean, I guess I wasn’t completely around during the time, but I would say, like, that’s definitely something that we’re considering in any kind of tech that we’re thinking about is it can require so much work to, to kind of bring something on with such a small team. So we want to ensure that, yeah, it’s going to last, it has longevity, and it’s going to work with the tools that we already have. So I think all of that is really important for sure.
\n\n\n\n[00:13:48] Josepha: Well, thank you both so much for joining me. Like I said, we’ll have a link to littlesun.org in the notes so that you all can learn more about their project and see their beautiful site with their beautiful little solar sunflowers.
\n\n\n\nThank you both for being with me today.
\n\n\n\n[00:14:04] Romane: Thank you so much.
\n\n\n\n[00:14:05] Ashley: Thank you so much for having us.
\n\n\n\n[00:14:07] (Music interlude)
\n\n\n\n[00:14:11] Josepha: What a wonderful organization. I’m so glad that they found WordPress and that it works for them. Let’s continue our tour today with the small list of big things.
\n\n\n\nItem number one, it’s time to save the date: December 11th, 2023, for this year’s State of the Word. State of the Word is the annual keynote address delivered by the WordPress Project co-founder Matt Mullenweg. Every year, the event shares reflections on the project’s progress and aspirations for the future of open source. And so, if that is something that you like to tune into, December 11th is your day.
\n\n\n\nSecond thing on our list is that we are celebrating our 10,000th photo submission. So, on October 11th, the 10,000th photo was approved. The Photo Team is one of the newest ways to contribute to the WordPress open source project, and it feeds all of those photos into Openverse as well.
\n\n\n\nThe third thing on our list today is that I want to tell you about a community team training module that just came out. It’s specifically about the Translate Live tool, and it is ideal for presenting at your local meetups to engage and onboard new translators for your native language. If you’re organizing a WordCamp, consider introducing this tool during your Contributor Day. I will leave a link for this in the show notes so that it is easy to find.
\n\n\n\nAnd item number four, the journey to update WordPress.org, continues with the launch of a new Showcase design. The Showcase is a natural starting point for a lot of visitors who are on WordPress.org. It inspires creativity and also demonstrates what’s possible with WordPress. So, stop on by there, it’s WordPress.org/showcase, and give it a bit of a look.
\n\n\n\n[00:15:58] Josepha: And that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. And don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever a new episode drops. And if you like what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard today, you can share those with me at wprebriefing@WordPress.org.
\n\n\n\nI’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:16:24] (Music outro)
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Oct 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"WPTavern: Gutenberg 16.9 Lets You Rename (Almost) Any Block, Adds Experimental Form and Input Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150720\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wptavern.com/gutenberg-16-9-lets-you-rename-almost-any-block-adds-experimental-form-and-input-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4201:\"Delivering on an highly-requested feature, Gutenberg contributors have made it possible to rename almost any block in the List View. Version 16.9 was released this week with the new feature, which builds on Gutenberg 16.7‘s introduction of the ability to rename Group blocks.
\n\n\n\nIt works in a similar way to naming Photoshop layers. Users can now open the list view, click on the ellipsis menu, select “Rename,” and enter a custom name.
\n\n\n\n\n\n\n\nvideo credit: Gutenberg PR #54426\n\n\n\n“Allowing users to distinguish between blocks in the List View is becoming increasingly important as the scope of the Site Editor grows,” Automattic-sponsored contributor Dave Smith said in the original ticket proposing the feature for the Group block. “Given that all blocks are currently labelled by the block name (e.g. Group
) it can be difficult to distinguish between them. This is especially important if your Groups represent distinct ‘sections’ of a given page/template.”
Every block can be renamed with the exception of these four:
\n\n\n\ncore/block
core/template-part
core/pattern
core/navigation
More renaming capabilities have been added in 16.9, including the ability to duplicate and rename patterns, as well as pattern categories.
\n\n\n\nThis release introduces new experimental form and inputs blocks to allow building basic forms. It’s a feature that has taken many by surprise, as few would have predicted WordPress core would be adding form building. A very early version is available under Gutenberg > Experiments, under the “Form and input blocks” experiment setting.
\n\n\n\n“Why has there been no proactive outreach to the many developers of longstanding WordPress form solutions currently used by millions and millions of WordPress sites?” Gravity Forms co-founder Carl Hancock commented on the PR.
\n\n\n\n“It seems like proactive outreach to people who are experts in this space and who could do the most to help drive adoption (beyond comments/search/etc.) would have been a good thing. On many levels. Trying to get them on board with contributing, learning from their shared historical knowledge, and even more important of all… building on top of it and adopting it instead of introducing a point of more fragmentation.”
\n\n\n\nThe forms feature is still in the very early stages of experimentation, and more information may be published to the November edition of “What’s New For Developers?“
\n\n\n\nA few other notable highlights from this release include the following:
\n\n\n\nCheck out the release post for Gutenberg 16.9 to see the full changelog and more details on bug fixes and enhancements to performance, tooling, documentation, code quality, and accessibility.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 Oct 2023 22:00:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"WPTavern: WordPress 6.4 Disables Attachment Pages for New Installations\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150736\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/wordpress-6-4-disables-attachment-pages-for-new-installations\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4090:\"The upcoming 6.4 release, expected on November 7, will disable attachment pages for new installations. Up until now, WordPress automatically created attachment pages when users upload a file through the media upload system. It has been treated as a special post type that holds information about the file and each attachment is accessible under its own URL. SEO plugins have been redirecting attachment pages for years, as they rarely have any significant purpose.
\n\n\n\n“Until WordPress 6.4 was released, WordPress created attachment pages by default for every attachment uploaded,” WordPress contributor Joost de Valk said in the dev note for this change. “On the vast majority of sites, these attachment pages don’t add any meaningful information. They do, however, exist, get indexed by search engines, and sometimes even rank in search results, leading to bad results for users and site owners.”
\n\n\n\nThere will be no changes to existing sites. They will continue to work as they always have, but new sites will have their attachment pages redirected to the attachment URL. Site admins who want to enable or disable attachment pages can use the new wp_attachment_pages_enabled
database option to control attachment pages’ behavior.
There is no interface for changing whether a site disables attachment pages, which was somewhat controversial in the comments on the Trac ticket and the dev note.
\n\n\n\n“In light of the WordPress mantra ‘decisions, not options,’ we’ve decided against making a setting for this,” de Valk said.
\n\n\n\nWordPress plugin developer Sybre Waaijer mades a case for giving users an option with an interface for toggling it on or off:
\n\n\n\n\n\n\n\n\nThe problem with filtering options is that when another plugin provides the option toggle, the option filter will go against user expectations.
\n\n\n\nThis is where “decisions, not options” becomes paradoxical because we’re now deciding to set an option while also not giving the option.
\n\n\n\nSo, as plugins fill in this gap, then A) where will plugins put the option (likely on their custom page instead of options-media.php), and B) of the dozens of types of plugins that are in the market to juggle this, who will ultimately be in control of the option?
\n\n\n\nIf it’s a filter, each plugin promises to set a toggle via a simple condition. But since it’s an option, plugins can add an option to filter an option and add an option to toggle the option. It’ll become a source of bugs because of the logical biconditionals (XNOR).
\n
While an interface isn’t in the cards for WordPress 6.4, and may never be back on the table for consideration, contributors are discussing the possibility of putting this in a core plugin.
\n\n\n\n“Should we not have a core plugin for re-enabling attachment pages on new sites?” Automattic-sponsored contributor Justin Tadlock said. “If there’s not going to be a UI for this, then a plugin that’s not buried in a Trac ticket would be ideal.”
\n\n\n\nde Valk agreed this would be a good idea to have a plugin that simply adds a setting to the Options -> Media page. Users likely will not understand the purpose of attachment pages unless they are looking to enable them for a specific, niche use case. A plugin like this would be useful for those who are not able to write the code to change attachment pages’ behavior, as described in the dev note.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 Oct 2023 17:42:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Fri, 17 Nov 2023 12:52:26 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:13:\"last-modified\";s:29:\"Fri, 17 Nov 2023 12:45:30 GMT\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:16:\"content-encoding\";s:2:\"br\";s:7:\"alt-svc\";s:19:\"h3=\":443\"; ma=86400\";s:4:\"x-nc\";s:9:\"HIT ord 1\";}}s:5:\"build\";s:14:\"20211221003300\";}','no'),(936,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1700268746','no'),(937,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1700225546','no'),(938,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1700268746','no'),(939,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b',' ','no'),(940,'_site_transient_timeout_community-events-6718ef04d3f46d7f6ff6aabe77f33591','1700268755','no'),(941,'_site_transient_community-events-6718ef04d3f46d7f6ff6aabe77f33591','a:4:{s:9:\"sandboxed\";b:0;s:5:\"error\";N;s:8:\"location\";a:1:{s:2:\"ip\";s:10:\"172.18.0.0\";}s:6:\"events\";a:2:{i:0;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:43:\"Frederick Tech Open Workshop - 3rd Saturday\";s:3:\"url\";s:59:\"https://www.meetup.com/wordpress-frederick/events/296877413\";s:6:\"meetup\";s:19:\"WordPress Frederick\";s:10:\"meetup_url\";s:43:\"https://www.meetup.com/wordpress-frederick/\";s:4:\"date\";s:19:\"2023-11-18 10:00:00\";s:8:\"end_date\";s:19:\"2023-11-18 12:00:00\";s:20:\"start_unix_timestamp\";i:1700319600;s:18:\"end_unix_timestamp\";i:1700326800;s:8:\"location\";a:4:{s:8:\"location\";s:18:\"Frederick, MD, USA\";s:7:\"country\";s:2:\"us\";s:8:\"latitude\";d:39.415829;s:9:\"longitude\";d:-77.410446;}}i:1;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:42:\"Core Web Vitals - Speeding Up Your Website\";s:3:\"url\";s:69:\"https://www.meetup.com/the-baltimore-wordpress-group/events/297095111\";s:6:\"meetup\";s:29:\"The Baltimore WordPress Group\";s:10:\"meetup_url\";s:53:\"https://www.meetup.com/The-Baltimore-WordPress-Group/\";s:4:\"date\";s:19:\"2023-12-14 18:00:00\";s:8:\"end_date\";s:19:\"2023-12-14 19:00:00\";s:20:\"start_unix_timestamp\";i:1702594800;s:18:\"end_unix_timestamp\";i:1702598400;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"US\";s:8:\"latitude\";d:39.31;s:9:\"longitude\";d:-76.58;}}}}','no'),(942,'_transient_timeout_tribe_plugin_upgrade_notice-bb3d480e','1700311965','no'),(943,'_transient_tribe_plugin_upgrade_notice-bb3d480e','','no'),(952,'_transient_timeout__tribe_admin_notices','1702822895','no'),(953,'_transient__tribe_admin_notices','a:0:{}','no'),(955,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1700229801;s:8:\"response\";a:1:{s:27:\"woocommerce/woocommerce.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:25:\"w.org/plugins/woocommerce\";s:4:\"slug\";s:11:\"woocommerce\";s:6:\"plugin\";s:27:\"woocommerce/woocommerce.php\";s:11:\"new_version\";s:5:\"8.3.0\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/woocommerce/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/woocommerce.8.3.0.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/woocommerce/assets/icon-256x256.gif?rev=2869506\";s:2:\"1x\";s:64:\"https://ps.w.org/woocommerce/assets/icon-128x128.gif?rev=2869506\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/woocommerce/assets/banner-1544x500.png?rev=2366418\";s:2:\"1x\";s:66:\"https://ps.w.org/woocommerce/assets/banner-772x250.png?rev=2366418\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"6.3\";s:6:\"tested\";s:5:\"6.4.1\";s:12:\"requires_php\";s:3:\"7.4\";}}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:5:{s:33:\"coupon-creator/coupon_creator.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:28:\"w.org/plugins/coupon-creator\";s:4:\"slug\";s:14:\"coupon-creator\";s:6:\"plugin\";s:33:\"coupon-creator/coupon_creator.php\";s:11:\"new_version\";s:5:\"3.3.0\";s:3:\"url\";s:45:\"https://wordpress.org/plugins/coupon-creator/\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/plugin/coupon-creator.3.3.0.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:59:\"https://ps.w.org/coupon-creator/assets/icon.svg?rev=2688941\";s:3:\"svg\";s:59:\"https://ps.w.org/coupon-creator/assets/icon.svg?rev=2688941\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:70:\"https://ps.w.org/coupon-creator/assets/banner-1544x500.png?rev=2688941\";s:2:\"1x\";s:69:\"https://ps.w.org/coupon-creator/assets/banner-772x250.png?rev=2688941\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.9\";}s:49:\"easy-digital-downloads/easy-digital-downloads.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:36:\"w.org/plugins/easy-digital-downloads\";s:4:\"slug\";s:22:\"easy-digital-downloads\";s:6:\"plugin\";s:49:\"easy-digital-downloads/easy-digital-downloads.php\";s:11:\"new_version\";s:5:\"3.2.5\";s:3:\"url\";s:53:\"https://wordpress.org/plugins/easy-digital-downloads/\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/plugin/easy-digital-downloads.3.2.5.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:66:\"https://ps.w.org/easy-digital-downloads/assets/icon.svg?rev=971968\";s:3:\"svg\";s:66:\"https://ps.w.org/easy-digital-downloads/assets/icon.svg?rev=971968\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:78:\"https://ps.w.org/easy-digital-downloads/assets/banner-1544x500.png?rev=2636140\";s:2:\"1x\";s:77:\"https://ps.w.org/easy-digital-downloads/assets/banner-772x250.png?rev=2636140\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.8\";}s:31:\"event-tickets/event-tickets.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:27:\"w.org/plugins/event-tickets\";s:4:\"slug\";s:13:\"event-tickets\";s:6:\"plugin\";s:31:\"event-tickets/event-tickets.php\";s:11:\"new_version\";s:5:\"5.7.0\";s:3:\"url\";s:44:\"https://wordpress.org/plugins/event-tickets/\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/plugin/event-tickets.5.7.0.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:58:\"https://ps.w.org/event-tickets/assets/icon.svg?rev=2259340\";s:3:\"svg\";s:58:\"https://ps.w.org/event-tickets/assets/icon.svg?rev=2259340\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:69:\"https://ps.w.org/event-tickets/assets/banner-1544x500.png?rev=2257626\";s:2:\"1x\";s:68:\"https://ps.w.org/event-tickets/assets/banner-772x250.png?rev=2257626\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"6.2\";}s:27:\"redis-cache/redis-cache.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:25:\"w.org/plugins/redis-cache\";s:4:\"slug\";s:11:\"redis-cache\";s:6:\"plugin\";s:27:\"redis-cache/redis-cache.php\";s:11:\"new_version\";s:5:\"2.5.0\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/redis-cache/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/redis-cache.2.5.0.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/redis-cache/assets/icon-256x256.gif?rev=2568513\";s:2:\"1x\";s:64:\"https://ps.w.org/redis-cache/assets/icon-128x128.gif?rev=2568513\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/redis-cache/assets/banner-1544x500.png?rev=2315420\";s:2:\"1x\";s:66:\"https://ps.w.org/redis-cache/assets/banner-772x250.png?rev=2315420\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.6\";}s:43:\"the-events-calendar/the-events-calendar.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:33:\"w.org/plugins/the-events-calendar\";s:4:\"slug\";s:19:\"the-events-calendar\";s:6:\"plugin\";s:43:\"the-events-calendar/the-events-calendar.php\";s:11:\"new_version\";s:5:\"6.2.8\";s:3:\"url\";s:50:\"https://wordpress.org/plugins/the-events-calendar/\";s:7:\"package\";s:68:\"https://downloads.wordpress.org/plugin/the-events-calendar.6.2.8.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-256x256.gif?rev=2516440\";s:2:\"1x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-128x128.gif?rev=2516440\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:75:\"https://ps.w.org/the-events-calendar/assets/banner-1544x500.png?rev=2257622\";s:2:\"1x\";s:74:\"https://ps.w.org/the-events-calendar/assets/banner-772x250.png?rev=2257622\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:5:\"6.2.0\";}}s:7:\"checked\";a:15:{s:33:\"ai-development/ai-development.php\";s:5:\"0.1.0\";s:33:\"coupon-creator/coupon_creator.php\";s:5:\"3.3.0\";s:49:\"coupon-creator-add-ons/coupon-creator-add-ons.php\";s:5:\"3.3.0\";s:41:\"coupon-creator-pro/coupon-creator-pro.php\";s:5:\"3.3.0\";s:49:\"easy-digital-downloads/easy-digital-downloads.php\";s:5:\"3.2.5\";s:31:\"event-tickets/event-tickets.php\";s:5:\"5.7.0\";s:41:\"event-tickets-plus/event-tickets-plus.php\";s:5:\"5.8.0\";s:27:\"redis-cache/redis-cache.php\";s:5:\"2.5.0\";s:43:\"the-events-calendar/the-events-calendar.php\";s:5:\"6.2.8\";s:35:\"event-automator/event-automator.php\";s:5:\"1.3.1\";s:33:\"events-virtual/events-virtual.php\";s:6:\"1.15.5\";s:34:\"events-pro/events-calendar-pro.php\";s:5:\"6.2.4\";s:29:\"volt-vectors/volt-vectors.php\";s:5:\"0.1.0\";s:37:\"volt-vectors-pro/volt-vectors-pro.php\";s:5:\"0.1.0\";s:27:\"woocommerce/woocommerce.php\";s:5:\"8.2.2\";}}','no'),(962,'_transient_timeout_orders-all-statuses','1700831425','no'),(963,'_transient_orders-all-statuses','a:2:{s:7:\"version\";s:10:\"1672924354\";s:5:\"value\";a:0:{}}','no'),(964,'_transient_timeout_woocommerce_admin_payment_method_promotion_specs','1700831425','no'),(965,'_transient_woocommerce_admin_payment_method_promotion_specs','a:1:{s:5:\"en_US\";a:2:{s:27:\"woocommerce_payments:woopay\";O:8:\"stdClass\":8:{s:2:\"id\";s:27:\"woocommerce_payments:woopay\";s:5:\"title\";s:20:\"WooCommerce Payments\";s:7:\"content\";s:393:\"Payments made simple — including WooPay, a new express checkout feature.Your transaction failed; please try again or contact site support.
','Transaction Failed','','publish','closed','closed','','transaction-failed','','','2023-01-05 13:11:42','2023-01-05 13:11:42','',4,'http://wordpress.test/checkout/transaction-failed/',0,'page','',0),(7,1,'2023-01-05 13:11:42','2023-01-05 13:11:42','','Order History','','publish','closed','closed','','order-history','','','2023-01-05 13:11:42','2023-01-05 13:11:42','',4,'http://wordpress.test/checkout/order-history/',0,'page','',0),(8,1,'2023-01-05 13:11:42','2023-01-05 13:11:42','Thank you for your purchase!
','Confirmation','','publish','closed','closed','','confirmation','','','2023-01-05 13:11:42','2023-01-05 13:11:42','',4,'http://wordpress.test/checkout/confirmation/',0,'page','',0),(9,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','','woocommerce-placeholder','','inherit','open','closed','','woocommerce-placeholder','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/wp-content/uploads/2023/01/woocommerce-placeholder.png',0,'attachment','image/png',0),(10,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','','Shop','','publish','closed','closed','','shop','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/shop/',0,'page','',0),(11,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','[woocommerce_cart]','Cart','','publish','closed','closed','','cart','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/cart/',0,'page','',0),(12,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','[woocommerce_checkout]','Checkout','','publish','closed','closed','','checkout-2','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/checkout-2/',0,'page','',0),(13,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','[woocommerce_my_account]','My account','','publish','closed','closed','','my-account','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/my-account/',0,'page','',0),(14,1,'2023-01-05 13:11:54','0000-00-00 00:00:00','\nThis is a sample page.
\n\n\n\nOur refund and returns policy lasts 30 days. If 30 days have passed since your purchase, we can’t offer you a full refund or exchange.
\n\n\n\nTo be eligible for a return, your item must be unused and in the same condition that you received it. It must also be in the original packaging.
\n\n\n\nSeveral types of goods are exempt from being returned. Perishable goods such as food, flowers, newspapers or magazines cannot be returned. We also do not accept products that are intimate or sanitary goods, hazardous materials, or flammable liquids or gases.
\n\n\n\nAdditional non-returnable items:
\n\n\n\nTo complete your return, we require a receipt or proof of purchase.
\n\n\n\nPlease do not send your purchase back to the manufacturer.
\n\n\n\nThere are certain situations where only partial refunds are granted:
\n\n\n\nOnce your return is received and inspected, we will send you an email to notify you that we have received your returned item. We will also notify you of the approval or rejection of your refund.
\n\n\n\nIf you are approved, then your refund will be processed, and a credit will automatically be applied to your credit card or original method of payment, within a certain amount of days.
\n\n\n\nLate or missing refunds\n\n\n\nIf you haven’t received a refund yet, first check your bank account again.
\n\n\n\nThen contact your credit card company, it may take some time before your refund is officially posted.
\n\n\n\nNext contact your bank. There is often some processing time before a refund is posted.
\n\n\n\nIf you’ve done all of this and you still have not received your refund yet, please contact us at {email address}.
\n\n\n\nSale items\n\n\n\nOnly regular priced items may be refunded. Sale items cannot be refunded.
\n\n\n\nWe only replace items if they are defective or damaged. If you need to exchange it for the same item, send us an email at {email address} and send your item to: {physical address}.
\n\n\n\nIf the item was marked as a gift when purchased and shipped directly to you, you’ll receive a gift credit for the value of your return. Once the returned item is received, a gift certificate will be mailed to you.
\n\n\n\nIf the item wasn’t marked as a gift when purchased, or the gift giver had the order shipped to themselves to give to you later, we will send a refund to the gift giver and they will find out about your return.
\n\n\n\nTo return your product, you should mail your product to: {physical address}.
\n\n\n\nYou will be responsible for paying for your own shipping costs for returning your item. Shipping costs are non-refundable. If you receive a refund, the cost of return shipping will be deducted from your refund.
\n\n\n\nDepending on where you live, the time it may take for your exchanged product to reach you may vary.
\n\n\n\nIf you are returning more expensive items, you may consider using a trackable shipping service or purchasing shipping insurance. We don’t guarantee that we will receive your returned item.
\n\n\n\nContact us at {email} for questions related to refunds and returns.
\n','Refund and Returns Policy','','draft','closed','closed','','refund_returns','','','2023-01-05 13:11:54','0000-00-00 00:00:00','',0,'http://wordpress.test/?page_id=14',0,'page','',0),(15,1,'2023-01-06 12:37:03','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2023-01-06 12:37:03','0000-00-00 00:00:00','',0,'http://wordpress.test/?p=15',0,'post','',0),(16,1,'2023-01-06 12:37:19','2023-01-06 12:37:19','[tec_tickets_checkout]','Tickets Checkout','','publish','closed','closed','','tickets-checkout','','','2023-01-06 12:37:19','2023-01-06 12:37:19','',0,'http://wordpress.test/tickets-checkout/',0,'page','',0),(17,1,'2023-01-06 12:37:19','2023-01-06 12:37:19','[tec_tickets_success]','Order Completed','','publish','closed','closed','','tickets-order','','','2023-01-06 12:37:19','2023-01-06 12:37:19','',0,'http://wordpress.test/tickets-order/',0,'page','',0),(18,0,'2023-11-17 07:24:17','2023-11-17 12:24:17','','Test Event','','publish','open','closed','','test-event','','','2023-11-17 07:24:17','2023-11-17 12:24:17','',0,'http://wordpress.test/event/test-event/',0,'tribe_events','',0),(19,0,'2023-11-17 07:24:18','2023-11-17 12:24:18','','Test WooCommerce ticket for 18','Test WooCommerce ticket description for 18','publish','open','closed','','test-woocommerce-ticket-for-18','','','2023-11-17 07:24:18','2023-11-17 12:24:18','',0,'http://wordpress.test/product/test-woocommerce-ticket-for-18/',-1,'product','',0); +/*!40000 ALTER TABLE `wp_posts` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_tec_events` +-- + +DROP TABLE IF EXISTS `wp_tec_events`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_tec_events` ( + `event_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `post_id` bigint(20) unsigned NOT NULL, + `start_date` varchar(19) NOT NULL, + `end_date` varchar(19) DEFAULT NULL, + `timezone` varchar(30) NOT NULL DEFAULT 'UTC', + `start_date_utc` varchar(19) NOT NULL, + `end_date_utc` varchar(19) DEFAULT NULL, + `duration` mediumint(30) DEFAULT 7200, + `updated_at` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), + `hash` varchar(40) NOT NULL, + PRIMARY KEY (`event_id`), + UNIQUE KEY `post_id` (`post_id`) +) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_tec_events` +-- + +LOCK TABLES `wp_tec_events` WRITE; +/*!40000 ALTER TABLE `wp_tec_events` DISABLE KEYS */; +INSERT INTO `wp_tec_events` VALUES (1,18,'2019-01-01 10:00:00','2019-01-01 13:00:00','America/New_York','2019-01-01 15:00:00','2019-01-01 18:00:00',10800,'2023-11-17 12:24:17',''); +/*!40000 ALTER TABLE `wp_tec_events` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_tec_occurrences` +-- + +DROP TABLE IF EXISTS `wp_tec_occurrences`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_tec_occurrences` ( + `occurrence_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `event_id` bigint(20) unsigned NOT NULL, + `post_id` bigint(20) unsigned NOT NULL, + `start_date` varchar(19) NOT NULL, + `start_date_utc` varchar(19) NOT NULL, + `end_date` varchar(19) NOT NULL, + `end_date_utc` varchar(19) NOT NULL, + `duration` mediumint(30) DEFAULT 7200, + `hash` varchar(40) NOT NULL, + `updated_at` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), + PRIMARY KEY (`occurrence_id`), + UNIQUE KEY `hash` (`hash`), + KEY `event_id` (`event_id`) +) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_tec_occurrences` +-- + +LOCK TABLES `wp_tec_occurrences` WRITE; +/*!40000 ALTER TABLE `wp_tec_occurrences` DISABLE KEYS */; +INSERT INTO `wp_tec_occurrences` VALUES (1,1,18,'2019-01-01 10:00:00','2019-01-01 15:00:00','2019-01-01 13:00:00','2019-01-01 18:00:00',10800,'4488dda4f18421f2229725fcd75413eb811f1538','2023-11-17 12:24:19'); +/*!40000 ALTER TABLE `wp_tec_occurrences` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_term_relationships` +-- + +DROP TABLE IF EXISTS `wp_term_relationships`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_term_relationships` ( + `object_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `term_order` int(11) NOT NULL DEFAULT 0, + PRIMARY KEY (`object_id`,`term_taxonomy_id`), + KEY `term_taxonomy_id` (`term_taxonomy_id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_term_relationships` +-- + +LOCK TABLES `wp_term_relationships` WRITE; +/*!40000 ALTER TABLE `wp_term_relationships` DISABLE KEYS */; +INSERT INTO `wp_term_relationships` VALUES (19,2,0),(19,6,0),(19,7,0); +/*!40000 ALTER TABLE `wp_term_relationships` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_term_taxonomy` +-- + +DROP TABLE IF EXISTS `wp_term_taxonomy`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_term_taxonomy` ( + `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `taxonomy` varchar(32) NOT NULL DEFAULT '', + `description` longtext NOT NULL, + `parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `count` bigint(20) NOT NULL DEFAULT 0, + PRIMARY KEY (`term_taxonomy_id`), + UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), + KEY `taxonomy` (`taxonomy`) +) ENGINE=InnoDB AUTO_INCREMENT=16 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_term_taxonomy` +-- + +LOCK TABLES `wp_term_taxonomy` WRITE; +/*!40000 ALTER TABLE `wp_term_taxonomy` DISABLE KEYS */; +INSERT INTO `wp_term_taxonomy` VALUES (1,1,'category','',0,1),(2,2,'product_type','',0,1),(3,3,'product_type','',0,0),(4,4,'product_type','',0,0),(5,5,'product_type','',0,0),(6,6,'product_visibility','',0,1),(7,7,'product_visibility','',0,1),(8,8,'product_visibility','',0,0),(9,9,'product_visibility','',0,0),(10,10,'product_visibility','',0,0),(11,11,'product_visibility','',0,0),(12,12,'product_visibility','',0,0),(13,13,'product_visibility','',0,0),(14,14,'product_visibility','',0,0),(15,15,'product_cat','',0,0); +/*!40000 ALTER TABLE `wp_term_taxonomy` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_termmeta` +-- + +DROP TABLE IF EXISTS `wp_termmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_termmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `term_id` (`term_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_termmeta` +-- + +LOCK TABLES `wp_termmeta` WRITE; +/*!40000 ALTER TABLE `wp_termmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_termmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_terms` +-- + +DROP TABLE IF EXISTS `wp_terms`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_terms` ( + `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `name` varchar(200) NOT NULL DEFAULT '', + `slug` varchar(200) NOT NULL DEFAULT '', + `term_group` bigint(10) NOT NULL DEFAULT 0, + PRIMARY KEY (`term_id`), + KEY `slug` (`slug`(191)), + KEY `name` (`name`(191)) +) ENGINE=InnoDB AUTO_INCREMENT=16 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_terms` +-- + +LOCK TABLES `wp_terms` WRITE; +/*!40000 ALTER TABLE `wp_terms` DISABLE KEYS */; +INSERT INTO `wp_terms` VALUES (1,'Uncategorized','uncategorized',0),(2,'simple','simple',0),(3,'grouped','grouped',0),(4,'variable','variable',0),(5,'external','external',0),(6,'exclude-from-search','exclude-from-search',0),(7,'exclude-from-catalog','exclude-from-catalog',0),(8,'featured','featured',0),(9,'outofstock','outofstock',0),(10,'rated-1','rated-1',0),(11,'rated-2','rated-2',0),(12,'rated-3','rated-3',0),(13,'rated-4','rated-4',0),(14,'rated-5','rated-5',0),(15,'Uncategorized','uncategorized',0); +/*!40000 ALTER TABLE `wp_terms` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_usermeta` +-- + +DROP TABLE IF EXISTS `wp_usermeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_usermeta` ( + `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`umeta_id`), + KEY `user_id` (`user_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB AUTO_INCREMENT=32 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_usermeta` +-- + +LOCK TABLES `wp_usermeta` WRITE; +/*!40000 ALTER TABLE `wp_usermeta` DISABLE KEYS */; +INSERT INTO `wp_usermeta` VALUES (1,1,'nickname','admin'),(2,1,'first_name',''),(3,1,'last_name',''),(4,1,'description',''),(5,1,'rich_editing','true'),(6,1,'syntax_highlighting','true'),(7,1,'comment_shortcuts','false'),(8,1,'admin_color','fresh'),(9,1,'use_ssl','0'),(10,1,'show_admin_bar_front','true'),(11,1,'locale',''),(12,1,'wp_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wp_user_level','10'),(14,1,'dismissed_wp_pointers',''),(15,1,'show_welcome_panel','0'),(16,1,'session_tokens','a:1:{s:64:\"f87edbb427e6c886863d67ca01bbe24209c88c0fed4152790d5a3c5b458b6abe\";a:4:{s:10:\"expiration\";i:1700398319;s:2:\"ip\";s:10:\"172.18.0.1\";s:2:\"ua\";s:84:\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/119.0\";s:5:\"login\";i:1700225519;}}'),(17,1,'wp_user-settings','mfold=o'),(18,1,'wp_user-settings-time','1666777420'),(19,1,'wp_dashboard_quick_press_last_post_id','15'),(20,1,'community-events-location','a:1:{s:2:\"ip\";s:10:\"172.18.0.0\";}'),(21,1,'wc_last_active','1700179200'),(23,1,'_woocommerce_tracks_anon_id','woo:5wYlp+5sdH3mKeoMABLSOktJ'),(24,1,'_woocommerce_persistent_cart_1','a:1:{s:4:\"cart\";a:0:{}}'),(25,1,'dismissed_no_secure_connection_notice','1'),(27,1,'tribe-dismiss-notice-time-event-tickets-plus-missing-easydigitaldownloads-support','1700226647'),(28,1,'tribe-dismiss-notice','event-tickets-plus-missing-easydigitaldownloads-support'),(29,1,'tribe-dismiss-notice-time-event-tickets-plus-missing-woocommerce-support','1700226652'),(30,1,'tribe-dismiss-notice','event-tickets-plus-missing-woocommerce-support'),(31,1,'dismissed_update_notice','1'); +/*!40000 ALTER TABLE `wp_usermeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_users` +-- + +DROP TABLE IF EXISTS `wp_users`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_users` ( + `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_login` varchar(60) NOT NULL DEFAULT '', + `user_pass` varchar(255) NOT NULL DEFAULT '', + `user_nicename` varchar(50) NOT NULL DEFAULT '', + `user_email` varchar(100) NOT NULL DEFAULT '', + `user_url` varchar(100) NOT NULL DEFAULT '', + `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `user_activation_key` varchar(255) NOT NULL DEFAULT '', + `user_status` int(11) NOT NULL DEFAULT 0, + `display_name` varchar(250) NOT NULL DEFAULT '', + PRIMARY KEY (`ID`), + KEY `user_login_key` (`user_login`), + KEY `user_nicename` (`user_nicename`), + KEY `user_email` (`user_email`) +) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_users` +-- + +LOCK TABLES `wp_users` WRITE; +/*!40000 ALTER TABLE `wp_users` DISABLE KEYS */; +INSERT INTO `wp_users` VALUES (1,'admin','$P$BXTnf5Ms8OdVvNu2ToTsQvL1LsiHRC.','admin','admin@wordpress.test','','2018-04-03 13:14:05','',0,'admin'); +/*!40000 ALTER TABLE `wp_users` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_wc_admin_note_actions` +-- + +DROP TABLE IF EXISTS `wp_wc_admin_note_actions`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_wc_admin_note_actions` ( + `action_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `note_id` bigint(20) unsigned NOT NULL, + `name` varchar(255) NOT NULL, + `label` varchar(255) NOT NULL, + `query` longtext NOT NULL, + `status` varchar(255) NOT NULL, + `actioned_text` varchar(255) NOT NULL, + `nonce_action` varchar(255) DEFAULT NULL, + `nonce_name` varchar(255) DEFAULT NULL, + PRIMARY KEY (`action_id`), + KEY `note_id` (`note_id`) +) ENGINE=InnoDB AUTO_INCREMENT=605 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_wc_admin_note_actions` +-- + +LOCK TABLES `wp_wc_admin_note_actions` WRITE; +/*!40000 ALTER TABLE `wp_wc_admin_note_actions` DISABLE KEYS */; +INSERT INTO `wp_wc_admin_note_actions` VALUES (1,1,'notify-refund-returns-page','Edit page','http://wordpress.test/wp-admin/post.php?post=14&action=edit','actioned','',NULL,NULL),(2,2,'connect','Connect','?page=wc-addons§ion=helper','unactioned','',NULL,NULL),(25,23,'share-navigation-survey-feedback','Share feedback','https://automattic.survey.fm/feedback-on-woocommerce-navigation','actioned','',NULL,NULL),(45,37,'add-first-product','Add a product','http://wordpress.test/wp-admin/admin.php?page=wc-admin&task=products','actioned','',NULL,NULL),(46,38,'visit-the-theme-marketplace','Visit the theme marketplace','https://woocommerce.com/product-category/themes/?utm_source=inbox&utm_medium=product','actioned','',NULL,NULL),(47,39,'learn-more','Learn more','https://woocommerce.com/mobile/?utm_medium=product','actioned','',NULL,NULL),(48,3,'browse_extensions','Browse extensions','http://wordpress.test/wp-admin/admin.php?page=wc-addons','unactioned','',NULL,NULL),(76,28,'wc-admin-wisepad3','Grow my business offline','https://woocommerce.com/products/wisepad3-card-reader/?utm_source=inbox_note&utm_medium=product&utm_campaign=wc-admin-wisepad3','actioned','',NULL,NULL),(81,31,'woocommerce_admin_deprecation_q4_2022','Deactivate WooCommerce Admin','http://wordpress.test/wp-admin/plugins.php','actioned','',NULL,NULL),(82,32,'paypal_paylater_g3_q4_22','Install PayPal Payments','https://woocommerce.com/products/woocommerce-paypal-payments/?utm_source=inbox_note&utm_medium=product&utm_campaign=paypal_paylater_g3_q4_22','unactioned','',NULL,NULL),(83,33,'paypal_paylater_g2_q4_22','Install PayPal Payments','https://woocommerce.com/products/woocommerce-paypal-payments/?utm_source=inbox_note&utm_medium=product&utm_campaign=paypal_paylater_g2_q4_22','unactioned','',NULL,NULL),(84,34,'google_listings_ads_custom_attribute_mapping_q4_2022','Learn more','https://woocommerce.com/document/google-listings-and-ads/?utm_source=inbox_note&utm_medium=product&utm_campaign=google_listings_ads_custom_attribute_mapping_q4_2022#attribute-mapping','actioned','',NULL,NULL),(424,40,'update-db_done','Thanks!','http://localhost:8888/wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s&wc-hide-notice=update','actioned','woocommerce_hide_notices_nonce','woocommerce_hide_notices_nonce','_wc_notice_nonce'),(515,4,'wayflyer_bnpl_q4_2021','Level up with funding','https://woo.com/products/wayflyer/?utm_source=inbox_note&utm_medium=product&utm_campaign=wayflyer_bnpl_q4_2021','actioned','',NULL,NULL),(516,5,'wc_shipping_mobile_app_usps_q4_2021','Get WooCommerce Shipping','https://woo.com/woocommerce-shipping/?utm_source=inbox_note&utm_medium=product&utm_campaign=wc_shipping_mobile_app_usps_q4_2021','actioned','',NULL,NULL),(517,6,'learn-more','Learn more','https://docs.woocommerce.com/document/woocommerce-shipping-and-tax/?utm_source=inbox','unactioned','',NULL,NULL),(518,7,'learn-more','Learn more','https://woo.com/posts/ecommerce-shipping-solutions-guide/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','actioned','',NULL,NULL),(519,8,'optimizing-the-checkout-flow','Learn more','https://woo.com/posts/optimizing-woocommerce-checkout?utm_source=inbox_note&utm_medium=product&utm_campaign=optimizing-the-checkout-flow','actioned','',NULL,NULL),(520,9,'qualitative-feedback-from-new-users','Share feedback','https://automattic.survey.fm/wc-pay-new','actioned','',NULL,NULL),(521,10,'share-feedback','Share feedback','http://automattic.survey.fm/paypal-feedback','unactioned','',NULL,NULL),(522,11,'get-started','Get started','https://woo.com/products/google-listings-and-ads?utm_source=inbox_note&utm_medium=product&utm_campaign=get-started','actioned','',NULL,NULL),(523,12,'update-wc-subscriptions-3-0-15','View latest version','http://localhost:8888/wp-admin/&page=wc-addons§ion=helper','actioned','',NULL,NULL),(524,13,'update-wc-core-5-4-0','How to update WooCommerce','https://docs.woocommerce.com/document/how-to-update-woocommerce/','actioned','',NULL,NULL),(525,16,'ppxo-pps-install-paypal-payments-1','View upgrade guide','https://docs.woocommerce.com/document/woocommerce-paypal-payments/paypal-payments-upgrade-guide/','actioned','',NULL,NULL),(526,17,'ppxo-pps-install-paypal-payments-2','View upgrade guide','https://docs.woocommerce.com/document/woocommerce-paypal-payments/paypal-payments-upgrade-guide/','actioned','',NULL,NULL),(527,18,'learn-more','Learn more','https://woo.com/posts/critical-vulnerability-detected-july-2021/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','unactioned','',NULL,NULL),(528,18,'dismiss','Dismiss','','actioned','',NULL,NULL),(529,19,'learn-more','Learn more','https://woo.com/posts/critical-vulnerability-detected-july-2021/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','unactioned','',NULL,NULL),(530,19,'dismiss','Dismiss','','actioned','',NULL,NULL),(531,20,'learn-more','Learn more','https://woo.com/posts/critical-vulnerability-detected-july-2021/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','unactioned','',NULL,NULL),(532,20,'dismiss','Dismiss','','actioned','',NULL,NULL),(533,21,'learn-more','Learn more','https://woo.com/posts/critical-vulnerability-detected-july-2021/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','unactioned','',NULL,NULL),(534,21,'dismiss','Dismiss','','actioned','',NULL,NULL),(535,22,'share-feedback','Share feedback','https://automattic.survey.fm/store-management','unactioned','',NULL,NULL),(536,24,'learn-more','Learn more','https://developer.woocommerce.com/2022/03/10/woocommerce-3-5-10-6-3-1-security-releases/','unactioned','',NULL,NULL),(537,24,'woocommerce-core-paypal-march-2022-dismiss','Dismiss','','actioned','',NULL,NULL),(538,25,'learn-more','Learn more','https://developer.woocommerce.com/2022/03/10/woocommerce-3-5-10-6-3-1-security-releases/','unactioned','',NULL,NULL),(539,25,'dismiss','Dismiss','','actioned','',NULL,NULL),(540,26,'pinterest_03_2022_update','Update Instructions','https://woo.com/document/pinterest-for-woocommerce/?utm_source=inbox_note&utm_medium=product&utm_campaign=pinterest_03_2022_update#section-3','actioned','',NULL,NULL),(541,27,'store_setup_survey_survey_q2_2022_share_your_thoughts','Tell us how it’s going','https://automattic.survey.fm/store-setup-survey-2022','actioned','',NULL,NULL),(542,29,'learn-more','Find out more','https://developer.woocommerce.com/2022/08/09/woocommerce-payments-3-9-4-4-5-1-security-releases/','unactioned','',NULL,NULL),(543,29,'dismiss','Dismiss','','actioned','',NULL,NULL),(544,30,'learn-more','Find out more','https://developer.woocommerce.com/2022/08/09/woocommerce-payments-3-9-4-4-5-1-security-releases/','unactioned','',NULL,NULL),(545,30,'dismiss','Dismiss','','actioned','',NULL,NULL),(546,35,'needs-update-eway-payment-gateway-rin-action-button-2022-12-20','See available updates','http://localhost:8888/wp-admin/update-core.php','unactioned','',NULL,NULL),(547,35,'needs-update-eway-payment-gateway-rin-dismiss-button-2022-12-20','Dismiss','#','actioned','',NULL,NULL),(548,36,'updated-eway-payment-gateway-rin-action-button-2022-12-20','See all updates','http://localhost:8888/wp-admin/update-core.php','unactioned','',NULL,NULL),(549,36,'updated-eway-payment-gateway-rin-dismiss-button-2022-12-20','Dismiss','#','actioned','',NULL,NULL),(550,41,'share-navigation-survey-feedback','Share feedback','https://automattic.survey.fm/new-ecommerce-plan-navigation','actioned','',NULL,NULL),(551,42,'woopay-beta-merchantrecruitment-activate-04MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','actioned','',NULL,NULL),(552,42,'woopay-beta-merchantrecruitment-activate-learnmore-04MAY23','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-activate-learnmore-04MAY23','unactioned','',NULL,NULL),(553,43,'woocommerce-wcpay-march-2023-update-needed-button','See Blog Post','https://developer.woocommerce.com/2023/03/23/critical-vulnerability-detected-in-woocommerce-payments-what-you-need-to-know','unactioned','',NULL,NULL),(554,43,'woocommerce-wcpay-march-2023-update-needed-dismiss-button','Dismiss','#','actioned','',NULL,NULL),(555,44,'tap_to_pay_iphone_q2_2023_no_wcpay','Simplify my payments','https://woo.com/products/woocommerce-payments/?utm_source=inbox_note&utm_medium=product&utm_campaign=tap_to_pay_iphone_q2_2023_no_wcpay','actioned','',NULL,NULL),(556,45,'extension-settings','See available updates','http://localhost:8888/wp-admin/update-core.php','unactioned','',NULL,NULL),(557,45,'dismiss','Dismiss','#','actioned','',NULL,NULL),(558,46,'woopay-beta-merchantrecruitment-update-WCPay-04MAY23','Update WooCommerce Payments','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(559,46,'woopay-beta-merchantrecruitment-update-activate-04MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','actioned','',NULL,NULL),(560,47,'woopay-beta-existingmerchants-noaction-documentation-27APR23','Documentation','https://woo.com/document/woopay-merchant-documentation/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-existingmerchants-noaction-documentation-27APR23','actioned','',NULL,NULL),(561,48,'woopay-beta-existingmerchants-update-WCPay-27APR23','Update WooCommerce Payments','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','actioned','',NULL,NULL),(562,49,'woopay-beta-merchantrecruitment-short-activate-04MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','actioned','',NULL,NULL),(563,49,'woopay-beta-merchantrecruitment-short-activate-learnmore-04MAY23','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-04MAY23','actioned','',NULL,NULL),(564,50,'woopay-beta-merchantrecruitment-short-update-WCPay-04MAY23','Update WooCommerce Payments','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(565,50,'woopay-beta-merchantrecruitment-short-update-activate-04MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','actioned','',NULL,NULL),(566,51,'woopay-beta-merchantrecruitment-short-activate-06MAY23-TESTA','Activate WooPay Test A','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(567,51,'woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTA','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTA','unactioned','',NULL,NULL),(568,52,'woopay-beta-merchantrecruitment-short-activate-06MAY23-TESTB','Activate WooPay Test B','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(569,52,'woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTA','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTA','unactioned','',NULL,NULL),(570,53,'woopay-beta-merchantrecruitment-short-activate-06MAY23-TESTC','Activate WooPay Test C','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(571,53,'woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTC','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTC','unactioned','',NULL,NULL),(572,54,'woopay-beta-merchantrecruitment-short-activate-06MAY23-TESTD','Activate WooPay Test D','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(573,54,'woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTD','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTD','unactioned','',NULL,NULL),(574,55,'woopay-beta-merchantrecruitment-short-activate-button-09MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(575,55,'woopay-beta-merchantrecruitment-short-activate-learnmore-button2-09MAY23','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-button2-09MAY23','unactioned','',NULL,NULL),(576,56,'woopay-beta-merchantrecruitment-short-update-WCPay-09MAY23','Update WooCommerce Payments','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(577,56,'woopay-beta-merchantrecruitment-short-update-activate-09MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(578,57,'woocommerce-WCStripe-May-2023-updated-needed-Plugin-Settings','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(579,57,'woocommerce-WCStripe-May-2023-updated-needed-Plugin-Settings-dismiss','Dismiss','#','actioned','',NULL,NULL),(580,58,'woocommerce-WCPayments-June-2023-updated-needed-Plugin-Settings','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(581,58,'woocommerce-WCPayments-June-2023-updated-needed-Dismiss','Dismiss','#','actioned','',NULL,NULL),(582,59,'woocommerce-WCSubscriptions-June-2023-updated-needed-Plugin-Settings','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(583,59,'woocommerce-WCSubscriptions-June-2023-updated-needed-dismiss','Dismiss','#','actioned','',NULL,NULL),(584,60,'woocommerce-WCReturnsWarranty-June-2023-updated-needed','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(585,60,'woocommerce-WCReturnsWarranty-June-2023-updated-needed','Dismiss','#','actioned','',NULL,NULL),(586,61,'woocommerce-WCOPC-June-2023-updated-needed','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','actioned','',NULL,NULL),(587,61,'woocommerce-WCOPC-June-2023-updated-needed','Dismiss','http://localhost:8888/wp-admin/#','actioned','',NULL,NULL),(588,62,'woocommerce-WCGC-July-2023-update-needed','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(589,62,'woocommerce-WCGC-July-2023-update-needed','Dismiss','#','actioned','',NULL,NULL),(590,63,'learn-more','Learn more','https://woo.com/document/fedex/?utm_medium=product&utm_source=inbox_note&utm_campaign=learn-more#july-2023-api-outage','unactioned','',NULL,NULL),(591,64,'plugin-list','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(592,64,'dismiss','Dismiss','http://localhost:8888/wp-admin/admin.php?page=wc-admin','actioned','',NULL,NULL),(593,65,'woocommerce-WCStripe-Aug-2023-update-needed','See available updates','http://localhost:8888/wp-admin/update-core.php?','unactioned','',NULL,NULL),(594,65,'dismiss','Dismiss','#','actioned','',NULL,NULL),(595,66,'dismiss','Dismiss','#','actioned','',NULL,NULL),(596,67,'woocommerce-WooPayments-Aug-2023-update-needed','See available updates','http://localhost:8888/wp-admin/update-core.php?','unactioned','',NULL,NULL),(597,67,'dismiss','Dismiss','#','actioned','',NULL,NULL),(598,68,'dismiss','Dismiss','#','actioned','',NULL,NULL),(599,69,'avalara_q3-2023_noAvaTax','Automate my sales tax','https://woo.com/products/woocommerce-avatax/?utm_source=inbox_note&utm_medium=product&utm_campaign=avalara_q3-2023_noAvaTax','unactioned','',NULL,NULL),(600,70,'woo-activation-survey-blockers-survey-button-22AUG23','Take our short survey','https://woocommerce.survey.fm/getting-started-with-woo','unactioned','',NULL,NULL),(601,71,'woocommerce-usermeta-Sept2023-productvendors','See available updates','http://localhost:8888/wp-admin/plugins.php','unactioned','',NULL,NULL),(602,71,'dismiss','Dismiss','http://localhost:8888/wp-admin/#','actioned','',NULL,NULL),(603,72,'woocommerce-STRIPE-Oct-2023-update-needed','See available updates','http://localhost:8888/wp-admin/update-core.php','unactioned','',NULL,NULL),(604,72,'dismiss','Dismiss','#','actioned','',NULL,NULL); +/*!40000 ALTER TABLE `wp_wc_admin_note_actions` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_wc_admin_notes` +-- + +DROP TABLE IF EXISTS `wp_wc_admin_notes`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_wc_admin_notes` ( + `note_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `name` varchar(255) NOT NULL, + `type` varchar(20) NOT NULL, + `locale` varchar(20) NOT NULL, + `title` longtext NOT NULL, + `content` longtext NOT NULL, + `content_data` longtext DEFAULT NULL, + `status` varchar(200) NOT NULL, + `source` varchar(200) NOT NULL, + `date_created` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `date_reminder` datetime DEFAULT NULL, + `is_snoozable` tinyint(1) NOT NULL DEFAULT 0, + `layout` varchar(20) NOT NULL DEFAULT '', + `image` varchar(200) DEFAULT NULL, + `is_deleted` tinyint(1) NOT NULL DEFAULT 0, + `is_read` tinyint(1) NOT NULL DEFAULT 0, + `icon` varchar(200) NOT NULL DEFAULT 'info', + PRIMARY KEY (`note_id`) +) ENGINE=InnoDB AUTO_INCREMENT=73 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_wc_admin_notes` +-- + +LOCK TABLES `wp_wc_admin_notes` WRITE; +/*!40000 ALTER TABLE `wp_wc_admin_notes` DISABLE KEYS */; +INSERT INTO `wp_wc_admin_notes` VALUES (1,'wc-refund-returns-page','info','en_US','Setup a Refund and Returns Policy page to boost your store\'s credibility.','We have created a sample draft Refund and Returns Policy page for you. Please have a look and update it to fit your store.','{}','unactioned','woocommerce-core','2023-01-05 13:11:55',NULL,0,'plain','',1,0,'info'),(2,'wc-admin-wc-helper-connection','info','en_US','Connect to WooCommerce.com','Connect to get important product notifications and updates.','{}','unactioned','woocommerce-admin','2023-01-05 13:11:56',NULL,0,'plain','',1,0,'info'),(3,'new_in_app_marketplace_2021','info','en_US','Customize your store with extensions','Check out our NEW Extensions tab to see our favorite extensions for customizing your store, and discover the most popular extensions in the WooCommerce Marketplace.','{}','unactioned','woocommerce.com','2023-01-05 13:13:22',NULL,0,'plain','',1,0,'info'),(4,'wayflyer_bnpl_q4_2021','marketing','en_US','Grow your business with funding through Wayflyer','Fast, flexible financing to boost cash flow and help your business grow – one fee, no interest rates, penalties, equity, or personal guarantees. Based on your store’s performance, Wayflyer provides funding and analytical insights to invest in your business.','{}','pending','woocommerce.com','2023-01-05 13:13:22',NULL,0,'plain','',0,0,'info'),(5,'wc_shipping_mobile_app_usps_q4_2021','marketing','en_US','Print and manage your shipping labels with WooCommerce Shipping and the WooCommerce Mobile App','Save time by printing, purchasing, refunding, and tracking shipping labels generated by WooCommerce Shipping – all directly from your mobile device!','{}','pending','woocommerce.com','2023-01-05 13:13:22',NULL,0,'plain','',0,0,'info'),(6,'woocommerce-services','info','en_US','WooCommerce Shipping & Tax','WooCommerce Shipping & Tax helps get your store \"ready to sell\" as quickly as possible. You create your products. We take care of tax calculation, payment processing, and shipping label printing! Learn more about the extension that you just installed.','{}','pending','woocommerce.com','2023-01-05 13:13:22',NULL,0,'plain','',0,0,'info'),(7,'your-first-product','info','en_US','Your first product','That’s huge! You’re well on your way to building a successful online store — now it’s time to think about how you’ll fulfill your orders.= [5.8.0] 2023-11-16 =
\r\n\r\n= [1.4.0] 2023-10-19 =
\r\n\r\nWe’re here to announce our exciting new innovation, Wallet Plus. This product creates digital and portable tickets for your event attendees and truly modernizes all of our current offerings, including Event Tickets and Event Tickets Plus. We’ve made this process simpler for your attendees so that they can now save their tickets to digital wallets,…
\nThe post Introducing Wallet Plus appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"Jaime\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4277:\"\nWe’re here to announce our exciting new innovation, Wallet Plus. This product creates digital and portable tickets for your event attendees and truly modernizes all of our current offerings, including Event Tickets and Event Tickets Plus.
\n\n\n\nWe’ve made this process simpler for your attendees so that they can now save their tickets to digital wallets, like Apple Wallet or PassWallet, and download PDF tickets to have them with them at any time.
\n\n\n\nPlus, you can personalize digital tickets by adding your logo, picking your brand colors, and customizing your Apple wallet passes and PDFs.
\n\n\n\nWallet Plus is a game-changer for day-of-event management. Your attendees will have easy access to their tickets, and the QR check-in process will be simpler and faster.
\n\n\n\nBelow, we’ll break down all of the exciting new features
\n\n\n\nAllow users to save their tickets in Apple Wallet.
\n\n\n\nCustomize your PDF tickets and allow your event attendees to download them or receive them by email.
\n\n\n\nInclude digital tickets in ticket confirmation emails and during the checkout process.
\n\n\n\nAllow attendees to save their tickets into their favorite digital platform so they can access their tickets anytime.
\n\n\n\nEasily customize your digital tickets with the look and feel of your brand in a few simple clicks.
\n\n\n\nStart providing digital tickets in a few clicks. Just install the plugin and set up the look and feel of your digital tickets via settings.
\n\n\n\nInclude attendee registration fields into digital tickets when using Event Tickets Plus.
\n\n\n\nInclude QR on digital tickets, and make day-of event management a breeze.
\n\n\n\nWe can’t wait for you to see Wallet Plus in action; we know you’re going to love it! Get started today!
\nThe post Introducing Wallet Plus appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:21:\"Virtual Events 1.15.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:152:\"https://theeventscalendar.com/release-notes/virtual-events/virtual-events-1-15-5/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:33:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:14:\"Virtual Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543276\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:575:\"Summary Maintenance Release The latest version of Virtual Events introduces compatibility features with the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✨ New New tweaks and enhancements in this release: 🗣 Translations Updated language files and strings:
\nThe post Virtual Events 1.15.5 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2617:\"\n\n\n\n\nMaintenance Release
\nThe latest version of Virtual Events introduces compatibility features with the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nNew tweaks and enhancements in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Virtual Events 1.15.5 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:24:\"Event Tickets Plus 5.8.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:159:\"https://theeventscalendar.com/release-notes/event-tickets-plus/event-tickets-plus-5-8-0/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:33:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Event Tickets Plus\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543273\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:595:\"Summary Maintenance Release The latest version of Event Tickets Plus introduces compatibility features with the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing.Event Tickets Plus 5.8.0 is only compatible with Event Tickets 5.7.0 and higher. ✨ New New tweaks and enhancements…
\nThe post Event Tickets Plus 5.8.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2901:\"\n\n\n\n\nMaintenance Release
\nThe latest version of Event Tickets Plus introduces compatibility features with the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
Event Tickets Plus 5.8.0 is only compatible with Event Tickets 5.7.0 and higher.
New tweaks and enhancements in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Event Tickets Plus 5.8.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Event Tickets 5.7.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:149:\"https://theeventscalendar.com/release-notes/event-tickets/event-tickets-5-7-0/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:32:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:13:\"Event Tickets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543271\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:584:\"Summary Maintenance Release The latest version of Event Tickets introduces compatibility features with the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. Event Tickets 5.7.0 is only compatible with The Events Calendar 6.2.7 and higher.Event Tickets 5.7.0 is only compatible with…
\nThe post Event Tickets 5.7.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3089:\"\n\n\n\n\nMaintenance Release
\nThe latest version of Event Tickets introduces compatibility features with the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
Event Tickets 5.7.0 is only compatible with The Events Calendar 6.2.7 and higher.
Event Tickets 5.7.0 is only compatible with Event Tickets Plus 5.8.0 and higher.
New tweaks and enhancements in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Event Tickets 5.7.0 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"The Events Calendar 6.2.8\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:161:\"https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-2-8/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 15:31:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:19:\"The Events Calendar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543267\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:615:\"Summary Maintenance Release This new version of The Events Calendar includes compatibility improvements for the new Wallet Plus plugin. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing! The Events Calendar 6.2.8 is only compatible with Event Tickets 5.7.0 and higher. ✨ New New features and tweaks included…
\nThe post The Events Calendar 6.2.8 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Leopoldo Scanavino\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2854:\"\n\n\n\n\nMaintenance Release
\nThis new version of The Events Calendar includes compatibility improvements for the new Wallet Plus plugin.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing!
\n\n\n\nThe Events Calendar 6.2.8 is only compatible with Event Tickets 5.7.0 and higher.
\nNew features and tweaks included in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post The Events Calendar 6.2.8 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"The Events Calendar 6.2.7\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:161:\"https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-2-7/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 17:50:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:19:\"The Events Calendar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543207\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:621:\"Summary Maintenance Release The latest update includes fixes for nonce generation and regressions along with various errors and deprecation notices. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✅ Fixed Bugs that were squashed in this release: ✨ Tweaks New tweaks in this release: 🗣 Translations Updated…
\nThe post The Events Calendar 6.2.7 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4757:\"\n\n\n\n\n\n\n\n\nMaintenance Release
\nThe latest update includes fixes for nonce generation and regressions along with various errors and deprecation notices.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nBugs that were squashed in this release:
\n\n\n\nNew tweaks in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post The Events Calendar 6.2.7 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"Events Calendar Pro 6.2.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:161:\"https://theeventscalendar.com/release-notes/events-calendar-pro/events-calendar-pro-6-2-4/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 17:49:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:19:\"Events Calendar Pro\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"Release Notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543209\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:579:\"Summary Maintenance Release The latest update resolves several deprecation notices and WPML permalink query on single posts. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✅ Fixed Bugs that were squashed in this release: 🗣 Translations Updated language files and strings:
\nThe post Events Calendar Pro 6.2.4 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3117:\"\n\n\n\n\nMaintenance Release
\nThe latest update resolves several deprecation notices and WPML permalink query on single posts.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nBugs that were squashed in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Events Calendar Pro 6.2.4 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"Introducing: Event Schedule Manager\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:146:\"https://theeventscalendar.com/blog/news/introducing-event-schedule-manager/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 17:53:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:10:\"What\'s New\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:4:\"blog\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2542727\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:582:\"Are you tired of juggling multiple systems, calendars, and custom coding while planning your events? Do you wish there was a more efficient way to manage your event schedules? Look no further! We are thrilled to introduce you to the all-new Event Schedule Manager – your ultimate event planning companion. Simplify your event planning Event…
\nThe post Introducing: Event Schedule Manager appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"Jaime\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3667:\"\nAre you tired of juggling multiple systems, calendars, and custom coding while planning your events? Do you wish there was a more efficient way to manage your event schedules? Look no further! We are thrilled to introduce you to the all-new Event Schedule Manager – your ultimate event planning companion.
\n\n\n\nEvent planning can be a daunting task, whether you’re organizing a corporate conference, a wedding, a music festival, or any other large-scale event. Event Schedule Manager is designed to simplify this process and make it more efficient than ever before.
\n\n\n\nWith Event Schedule Manager, you can say goodbye to custom coding a schedule with multiple tracks. Our user-friendly plugin provides a centralized hub where you can easily manage all aspects of your event, from scheduling to guest lists and beyond. There’s no need for multiple plugins and services to display your schedule tracks; everything you need is right at your fingertips.
\n\n\n\nLet’s take a closer look at some of the standout features that make Event Schedule Manager the go-to tool for event planners:
\n\n\n\nEvent Schedule Manager is more than just a scheduling tool; it’s a comprehensive event planning solution. Here’s why you should make it an integral part of your event planning process:
\n\n\n\nAre you ready to revolutionize your event schedule planning experience? Event Schedule Manager is here to make your life easier and your events more successful. Say goodbye to the chaos of event creation and hello to streamlined event planning.
\n\n\n\nCheck it out here!
\nThe post Introducing: Event Schedule Manager appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"Events Calendar Pro 6.2.3.1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:163:\"https://theeventscalendar.com/release-notes/events-calendar-pro/events-calendar-pro-6-2-3-1/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 22:16:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:19:\"Events Calendar Pro\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"Release Notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543182\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:569:\"Summary Maintenance Release The latest update includes a fix for saving recurring events correctly on WP v6.4. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. ✅ Fixed Bugs that were squashed in this release: 🗣 Translations Updated language files and strings:
\nThe post Events Calendar Pro 6.2.3.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2617:\"\n\n\n\n\nMaintenance Release
\nThe latest update includes a fix for saving recurring events correctly on WP v6.4.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\nBugs that were squashed in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post Events Calendar Pro 6.2.3.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"The Events Calendar 6.2.6.1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:163:\"https://theeventscalendar.com/release-notes/the-events-calendar/the-events-calendar-6-2-6-1/?utm_source=theeventscalendar&utm_medium=referral&utm_campaign=rss-feed\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 22:16:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:19:\"The Events Calendar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"release notes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://theeventscalendar.com/?p=2543180\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:617:\"Summary Maintenance Release The latest update includes a preventive fix for possible fatals. As always, we recommend testing updates on a staging site first, but it should all be smooth sailing. Event Tickets 5.6.8.1 is only compatible with The Events Calendar 6.2.6.1 and higher. ✅ Fixed Bugs that were squashed in this release: 🗣 Translations Updated language…
\nThe post The Events Calendar 6.2.6.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Emily Negroni\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2703:\"\n\n\n\n\n\n\n\n\nMaintenance Release
\nThe latest update includes a preventive fix for possible fatals.
\n\n\n\nAs always, we recommend testing updates on a staging site first, but it should all be smooth sailing.
\n\n\n\nEvent Tickets 5.6.8.1 is only compatible with The Events Calendar 6.2.6.1 and higher.
\nBugs that were squashed in this release:
\n\n\n\nUpdated language files and strings:
\n\n\n\nThe post The Events Calendar 6.2.6.1 appeared first on The Events Calendar.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:35:\"https://theeventscalendar.com/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:14:{s:4:\"date\";s:29:\"Fri, 17 Nov 2023 12:52:16 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:6:\"cf-ray\";s:20:\"82781c23a8e41ffd-IAD\";s:15:\"cf-cache-status\";s:6:\"BYPASS\";s:4:\"etag\";s:36:\"W/\"28a9d8340e4bf632fa7a8256cb45ab50\"\";s:13:\"last-modified\";s:29:\"Fri, 17 Nov 2023 09:29:19 GMT\";s:4:\"link\";s:117:\"The countdown is on for this year’s State of the Word! If you missed the initial announcement a few weeks ago, you’ll want to mark your calendars for December 11, 2023.
\n\n\n\nState of the Word is the annual keynote in which WordPress co-founder Matt Mullenweg celebrates the progress of the open source project and offers a glimpse into its future.
\n\n\n\nFor the first time, State of the Word ventures beyond North America, bringing the WordPress community to a new and vibrant city that plays a vital role in the WordPress project — Madrid, Spain! The event will be live-streamed to WordPress enthusiasts and newcomers around the globe via the WordPress YouTube channel.
\n\n\n\nPlease visit the event website for more event details and live-streaming information.
\n\n\n\nWhat: State of the Word 2023
When: December 11, 2023, 15:00 UTC (Start of live stream)
Where: Palacio Neptuno, Madrid, Spain
Streaming: Watch the live stream on the WordPress YouTube channel.
Tickets: Request a ticket to attend in person.
Please note that the venue’s capacity is limited; therefore, not all ticket requests will be granted.
Meetups: The community will sponsor several local watch parties globally, both in
person and online. Find one near you or organize one.
State of the Word will include a Q&A session. If you want to participate, you can send your question to ask-matt@wordcamp.org or ask during the event via the Q&A app Slido. A QR code for your submission will be provided during the event live stream.
\n\n\n\nGiven the volume of questions usually submitted, only some will be answered live, while others will be covered in a follow-up post published after the event on make.wordpress.org/project.
\n\n\n\nIs this your first State of the Word? Check out prior events on WordPress.tv for an introduction to the format.
\n\n\n\nSee you in person and online on December 11!
\n\n\n\nThank you to Reyes Martínez and Chloé Bringmann for reviewing this post.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16429\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:68:\"\n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"Introducing Twenty Twenty-Four\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://wordpress.org/news/2023/11/introducing-twenty-twenty-four/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 18:29:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:4:{i:0;a:5:{s:4:\"data\";s:6:\"Design\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:18:\"Twenty Twenty-Four\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16394\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:127:\"Meet Twenty Twenty-Four, the most versatile default theme yet—bundled with WordPress 6.4 and ready to make it uniquely yours.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:2:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:59:\"https://wordpress.org/news/files/2023/11/tt4-i9-small-1.mp4\";s:6:\"length\";s:7:\"6747134\";s:4:\"type\";s:9:\"video/mp4\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:82:\"https://wordpress.org/news/files/2023/11/tt4-howto-replace-template_compressed.mp4\";s:6:\"length\";s:8:\"12815358\";s:4:\"type\";s:9:\"video/mp4\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Maggie Cabrera\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:7209:\"\nWhen it comes to designing a website, one size doesn’t fit all. We understand that every WordPress user has unique needs and goals, whether you’re an aspiring entrepreneur, a passionate photographer, a prolific writer, or a bit of them all. That’s why we are thrilled to introduce Twenty Twenty-Four, the most versatile default theme yet—bundled with WordPress 6.4 and ready to make it uniquely yours.
\n\n\n\n\n\n\n\nUnlike past default themes, Twenty Twenty-Four breaks away from the tradition of focusing on a specific topic or style. Instead, this theme has been thoughtfully crafted to cater to any type of website, regardless of its focus. The theme explores three different use cases: one designed for entrepreneurs and small businesses, another for photographers and artists, and a third tailored for writers and bloggers. Thanks to its multi-faceted nature and adaptability, Twenty Twenty-Four emerges as the perfect fit for any of your projects.
\n\n\n\nAs you dive into its templates and patterns, you will notice how the new Site Editor functionality opens up different pathways for building your site seamlessly.
\n\n\n\nWhether you’re looking to craft an About page, showcase your work, handle RSVPs, or design captivating landing pages, Twenty Twenty-Four has got you covered. Choose from an extensive collection of over 35 beautiful patterns to customize and suit your needs.
\n\n\n\nFor the first time, this theme features full-page patterns for templates like homepage, archive, search, single pages, and posts. Some are exclusively available during the template-switching and creation process, ensuring you have the right options when you need them.
\n\n\n\n\n\n\n\nMoreover, you can take advantage of a variety of patterns for page sections, such as FAQs, testimonials, or pricing, to meet your site’s most specific requirements.
\n\n\n\nWith this diverse pattern library, Twenty Twenty-Four offers a flexible canvas to quickly assemble pages without having to start from scratch—saving you time and energy in the creation process. Just let your creativity flow and explore the possibilities!
\n\n\n\n\n\n\n\nTwenty Twenty-Four ushers in a new era of block themes by bringing together the latest WordPress site editing capabilities. Discover newer design tools such as background image support in Group blocks and vertical text, providing an intuitive and efficient way to create compelling, interactive content.
\n\n\n\nFind image placeholders with predefined aspect ratio settings within patterns, allowing you to drop images that perfectly fill the space. To go one step further, make your visuals interactive by enabling lightboxes. Ideal for showcasing galleries or portfolio images, this feature allows your visitors to expand and engage with them in full-screen mode. Activate it globally for all images throughout your site or for specific ones.
\n\n\n\nFor a smoother browsing experience on your site, you can disable the “Force page reload” setting in the Query Loop block. This allows the necessary content to be loaded dynamically when switching between different pages without needing a full-page refresh.
\n\n\n\nTwenty Twenty-Four goes beyond versatility with a beautiful aesthetic inspired by contemporary design trends, giving your website a sleek and modern look. Key design elements include:
\n\n\n\nAlong with its design, Twenty Twenty-Four has been meticulously optimized for performance. This ensures that your website not only looks great but also delivers a fast and efficient user experience.
\n\n\n\n \n\n\n\nMore information can be found in the following links:
\n\n\n\nThe Twenty Twenty-Four theme was designed by Beatriz Fialho and made possible thanks to the passion and tireless work of more than 120 contributors.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16394\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WP Briefing: Episode 66: Advocating Open Source Solutions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wordpress.org/news/2023/11/episode-66-advocating-open-source-solutions/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16357\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:296:\"WordPress Executive Director, Josepha Haden Chomphosy, speaks to the strategic approach to integrating open source solutions within your company and offers insight into initiating open source advocacy conversations. Tune in for a session that could redefine your company\'s technological approach.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:51:\"https://wordpress.org/news/files/2023/11/WPB066.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:11349:\"\nWordPress Executive Director, Josepha Haden Chomphosy, speaks to the strategic approach to integrating open source solutions within your company and offers insight into initiating open source advocacy conversations. Tune in for a session that could redefine your company’s technological approach.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@WordPress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, we’re talking about something I used to have a lot of experience with in my career before WordPress. I worked at a marketing agency. I wasn’t a developer. I was in data and strategy sorts of things. But part of the work heading into every project was an evaluation of what software was best. There were always a variety being considered, but WordPress was frequently one of them.
\n\n\n\nNow, I don’t know if any of you have had that moment where you’re having to talk open source with a CTO or a CEO, but it can be nerve-wracking, to say the least. And it makes sense, right? Open source has a PR problem, especially when you’re speaking to leadership inside a business. And it doesn’t really matter the size, right?
\n\n\n\nYou’re advocating for something that requires a completely different mental model. It doesn’t fit into accepted concepts of what makes a business thrive or what makes a bet a sure thing. There were three, maybe four, concerns that came up every time I had this conversation. So, I’m going to share those concerns with you and a few possible counterpoints to get you started.
\n\n\n\n[00:01:48] Josepha: First and always is the concern around security. I believe that this particular mismatch is rooted in an idea that controlled equals secure, which isn’t always the case. So the talking point is this. Since open source has a transparent development process, it is often more secure than proprietary software, contrary to what you might hear.
\n\n\n\nThat transparency allows vulnerabilities to be identified by independent researchers and community members and then patched quickly because you aren’t limited by who or what you know personally.
\n\n\n\nAnd if you’re not having a conversation where you’re having to defend the security in open source and you just want to bring it up yourself, here is a conversation opener for that. Security is a top concern for all of us. Surprisingly, open source solutions often have stronger security measures due to the collaborative nature of their development. It’s a proactive approach to minimizing risks.
\n\n\n\n[00:02:43] Josepha: A second thing that frequently came up was questions around innovation and future proofing of open source products. I think this mismatch is fully rooted in the Cathedral and the Bazaar methods of advancement. So the talking point for that one is this. Embracing open source fosters innovation. We can tap into the latest technologies and stay ahead of industry trends that way. It is specifically because we have a diverse set of viewpoints that we can make sure to quickly account for future risks, along with taking advantage of future opportunities. And by our organization being more active, we can potentially get exactly the solutions we need for our clients long term.
\n\n\n\nAnd the conversation opener for this, if you are the one bringing up the topic, is I’ve been thinking about our long-term goals and how to keep our technology stack relevant. Open source not only keeps us current but also positions us as innovators in our field.
\n\n\n\n[00:03:40] Josepha: And finally, the thing that seems to make or break the decision is the concept of independence. Part of any good business decision, especially around software, is determining upfront costs to getting started, long-term effectiveness of the chosen solution, and long-term mobility should circumstances change. Open source can address these from multiple vantage points.
\n\n\n\nSo here’s a good talking point for that one. Open source liberates us from vendor lock-in. We’re not tied to a single vendor’s roadmap or pricing changes, providing us with more options that suit our needs our clients’ needs. Also, given how ubiquitous WordPress is in particular, there will always be a disaster recovery option should a senior developer leave.
\n\n\n\nAnd beyond all of that, clients can own all of the content, audience attention, and clientele that we have all worked so hard to help them earn. And again, if you’re not defending things and instead choosing to bring them up as somebody who is trying to affect change in your own organization, here is a good place to start for that.
\n\n\n\nConsidering the dynamic nature of our industry, having the freedom to choose solutions independent of a specific vendor makes sure that we are always in control of our destiny.
\n\n\n\n[00:04:59] Josepha: So, those are the three most frequent things I encountered when I was having conversations about which software to choose and what software was the best choice long term for both our organization and our client’s organizations.
\n\n\n\nIf you have been in the midst of this type of conversation and have been longing for some counterpoints, I hope this helps. But if you have been feeling in your heart of hearts that your company or organization would be better off using open source software, and of course, in my context, particularly WordPress as that software, but you’ve been worried about bringing it up, I hope this gives you the courage to get out there and be an agent of change in your organization. You can do it, and I know you can.
\n\n\n\n[00:05:44] (Music interlude)
\n\n\n\n[00:05:51] Josepha: All right, my friends, that brings us now to our small list of big things.
\n\n\n\n[00:05:57] Josepha: First on the list, big, big thing. We launched WordPress 6.4 on November 7th, about a week ago. Be sure to download and check out the latest update on this monumental release. And while you’re doing it. Be sure to check out the new default theme that came out with it. It has a lot of patterns in it. I know I’ve talked about it quite a bit over the course of the year, but it’s really beautiful, and I think that it’s worth a good, strong highlight. So WordPress 6.4, you can get it on WordPress.org/download or inside your own host, probably.
\n\n\n\n[00:06:29] Josepha: The second thing that we have is that the training team recently published several new Learn resources to support meetup organizers. So we’ve got over there some lesson plans, tutorials, online workshops. And there are also new materials that help you figure out how to accomplish your goals as a contributor to the WordPress project.
\n\n\n\n[00:06:49] Josepha: And we also have a recently published new diverse speaker training page. It provides incredible resources for new and experienced contributors to bring more diverse speaker lineups and inclusive, diverse WordPress events for official WordPress meetups and WordCamps.
\n\n\n\n[00:07:06] Josepha: And the fourth thing on our small list of big things today is that I would love to get a few voice recordings from you all, from folks who are listening to the WordPress Briefing, or folks that you know, to learn more about how WordPress has impacted you.
\n\n\n\nOne of the things that I miss the most from my days as a WordCamp organizer is that annually, I got to see people who had shown up, once at a meetup, you know, to learn what WordPress was, and then came back year after year to our WordCamp with these new goals and new successes and I got to watch their businesses change over time. And so if you have a story like that where WordPress impacted what you are doing or what people that you know have done, record something and send it to wpbriefing@WordPress.org.
\n\n\n\nSo that, my friends, is your small list of big things.
\n\n\n\n[00:08:04] Josepha: Don’t forget to follow us on your favorite podcasting app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there is a new episode. If you liked what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard, you can share those with me at wpbriefing@WordPress.org. I’m your host, Josepha Haden Chomphosy. Thanks for tuning in today for the WordPress Briefing, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:08:31] (Music outro)
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16357\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"The Month in WordPress – October 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2023/11/the-month-in-wordpress-october-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Nov 2023 23:06:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:18:\"month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16365\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:391:\"September-October 2023 was yet another fun and eventful chapter in WordPress, with more WordCamps hosting exciting discussions, knowledge sharing, and learning. This month also welcomed the release of WordPress 6.4 and the Twenty Twenty-Four theme. Let’s check it out. Meet WordPress 6.4 “Shirley” WordPress 6.4 “Shirley” was released on November 7, 2023, and named after […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Nicholas Garofalo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:11701:\"\nSeptember-October 2023 was yet another fun and eventful chapter in WordPress, with more WordCamps hosting exciting discussions, knowledge sharing, and learning. This month also welcomed the release of WordPress 6.4 and the Twenty Twenty-Four theme. Let’s check it out.
\n\n\n\nWordPress 6.4 “Shirley” was released on November 7, 2023, and named after the iconic jazz artist Shirley Horn. With the release of WordPress 6.4 comes the new Twenty Twenty-Four theme, a multi-faceted, highly flexible default theme pre-loaded with more than 35 templates and patterns.
\n\n\n\nThis release includes more than 100 performance-related updates for a faster and more efficient experience. There’s also a host of new features and enhancements that help improve the content creation process and streamline site editing.
\n\n\n\nWordPress 6.4 was made possible by more than 600 contributors in at least 56 countries. Leading this release has been an underrepresented gender team, emphasizing WordPress’ commitment to fostering diverse voices in the open source project.
\n\n\n\n \n\n\n\n\n\n\n\nMark your calendars for State of the Word! The annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg, will be held on December 11, 2023. For the first time, the event will take place outside North America—this time with the Spanish community in Madrid, Spain.
\n\n\n\nA live stream will be available for WordPress enthusiasts who will not be able to attend in person. Stay tuned for more information, including how to reserve a ticket, soon!
\n\n\n\n \n\n\n\n\n\n\n\nTwo new versions of Gutenberg shipped in October:
\n\n\n\nOctober’s Core Editor Improvement post dives into all the writing enhancements expected in the latest WordPress 6.4 release.
\n\n\n\nhttps://wordpress.org/news/2023/10/episode-64-patterns-in-wordpress/\n\n\n\nHave a story we should include in the next issue of The Month in WordPress? Fill out this quick form to let us know.
\n\n\n\nThank you to Bernard Meyer and Reyes Martínez for their contributions to this edition of The Month in WordPress.
\n\n\n\nJoin over 2 million other subscribers and receive WordPress news directly in your inbox.
\n\n\n\n Subscribe\n
\nThis minor release features four bug fixes. You can review a summary of the maintenance updates in this release by reading the Release Candidate announcement or view the list of tickets on Trac.
\n\n\n\nWordPress 6.4.1 is a short-cycle release. If you have sites that support automatic background updates, the update process will begin automatically. If your site does not update automatically, you can also update from your Dashboard.
\n\n\n\nYou can download WordPress 6.4.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.
\n\n\n\nFor more information on this release, please visit the HelpHub site.
\n\n\n\nThis release was led by Aaron Jorbin and Tonya Mork. Thank you to everyone who tested the RC and 6.4.1, and raised reports.
\n\n\n\nWordPress 6.4.1 would not have been possible without the contributions of the following people. Their quick and concerted coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\n\n@afragen @clorith @desrosj @pbiron @schlessera @azaozz @davidbaumwald @tomsommer @nexflaszlo @howdy_mcgee @baxbridge @earnjam @timothyblynjacobs @johnbillion @flixos90 @joedolson @jeffpaul @zunaid321 @courane01 @audrasjb @tacoverdo @ironprogrammer @webcommsat @otto42 @barry @chanthaboune @rajinsharwar @aaroncampbell @peterwilsoncc @anandau14 @iandunn @matthewjho @coffee2code @boogah @jason_the_adams @joemcgill @johnjamesjacoby @jrf @renehermi @dlh @mukesh27 @sumitbagthariya16 @starbuck @sergeybiryukov @ravipatel
\n\n\n\nTo get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core channel. Need help? Check out the Core Contributor Handbook.
\n\n\n\nThanks to @jeffpaul and @webcommsat for proofreading.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16332\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:66:\"\n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"WordPress 6.4 “Shirley”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://wordpress.org/news/2023/11/shirley/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 07 Nov 2023 19:59:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:4:{i:0;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16299\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:194:\"WordPress 6.4 \"Shirley\" is here! Named in honor of the iconic jazz singer and pianist Shirley Horn, this release was made possible by over 600 contributors. Download WordPress 6.4 Shirley today.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:74789:\"\n\n\n\n\nSay hello to WordPress 6.4 “Shirley,” named after the iconic jazz artist Shirley Horn. Her distinctive voice and extraordinary connection to the piano established her as one of the leading jazz musicians of her generation. Horn’s journey from the Washington D.C. jazz scene to the international stage is a testament to her dedication and perseverance. Her influence reached far beyond the confines of traditional jazz, breaking boundaries and inspiring audiences worldwide.
\n\n\n\nEnjoy the easy pace of Shirley Horn’s music as you take in all that 6.4 offers.
\n\n\n\nThis latest version of WordPress introduces a new, versatile default theme and a suite of upgrades to empower every step of your creative journey. Craft your content seamlessly with further writing improvements. Explore more ways to bring your vision to life and streamline site editing with enhanced tools. Whether you’re new to WordPress or an experienced creator, “Shirley” has something for you. Discover the unmatched flexibility of building with blocks and let your ideas take flight.
\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\nMany of the features and enhancements in WordPress 6.4 fall in the “small but mighty” category. Along with the adaptable beauty of the Twenty Twenty-Four theme, these updates help content creators and site developers alike save time and effort while delivering the high value, low hassle WordPress experience the world has grown to expect.
\nJosepha Haden Chomphosy, Executive Director of WordPress
Experience site editing at its finest with Twenty Twenty-Four. This new multi-faceted default theme has been thoughtfully crafted with three distinct use cases in mind, from writers and artists to entrepreneurs. Save time and effort with its extensive collection of over 35 templates and patterns—and unlock a world of creative possibilities with a few tweaks. Twenty Twenty-Four’s remarkable flexibility ensures an ideal fit for almost any type of site. Check it out in this demo.
\n\n\n\n\n\n\n\nNew enhancements ensure your content creation journey is smooth. Find new keyboard shortcuts in List View, smarter list merging, and enhanced control over link settings. A cohesive toolbar experience for the Navigation, List, and Quote blocks lets you work efficiently with the tooling options you need.
\n\n\n\n\n\n\n\nFirst introduced in WordPress 6.3, the Command Palette is a powerful tool to quickly find what you need, perform tasks efficiently, and speed up your building workflow. Enjoy a refreshed design and new commands to perform block-specific actions in this release.
\n\n\n\n\n\n\n\nPatterns are an excellent way to leverage the potential of blocks and simplify your site-building process. WordPress 6.4 allows you to organize them with custom categories. Plus, new advanced filtering in the Patterns section of the inserter makes finding all your patterns more intuitive.
\n\n\n\n\n\n\n\nBuild beautiful and functional layouts with an expanded set of design tools. Play with background images in Group blocks for unique designs and maintain image dimensions consistent with placeholder aspect ratios. Do you want to add buttons to your Navigation block? Now you can do it conveniently without a line of code.
\n\n\n\n\n\n\n\nEnable lightbox functionality to let your site visitors enjoy full-screen, interactive images on click. Apply it globally or to specific images to customize the viewing experience.
\n\n\n\n\n\n\n\nSet custom names for Group blocks to organize and distinguish areas of your content easily. These names will be visible in List View.
\n\n\n\n\n\n\n\nNew previews for Gallery and Image blocks in List View let you visualize and locate where images on your content are at a glance.
\n\n\n\n\n\n\n\nNeed to use your custom patterns on another site? Import and export them as JSON files from the Site Editor’s patterns view.
\n\n\n\n\n\n\n\nBlock Hooks enables developers to automatically insert dynamic blocks at specific content locations, enriching the extensibility of block themes through plugins. While considered a developer tool, this feature is geared to respect your preferences and gives you complete control to add, dismiss, and customize auto-inserted blocks to your needs.
\n\n\n\n\n\n\n\nThis release includes more than 100 performance-related updates for a faster and more efficient experience. Notable enhancements focus on template loading performance for themes (including Twenty Twenty-Four), usage of the script loading strategies “defer” and “async” in core, blocks, and themes, and optimization of autoloaded options.
\n\n\n\nEvery release is committed to making WordPress accessible to everyone. WordPress 6.4 brings several List View improvements and aria-label support for the Navigation block, among other highlights. The admin user interface includes enhancements to button placements, “Add New” menu items context, and Site Health spoken messages. Learn more about all the updates aimed at improving accessibility.
\n\n\n\nCheck out the new WordPress 6.4 page to learn more about the numerous enhancements and features of this release.
\n\n\n\nExplore Learn WordPress for quick how-to videos, online workshops, and other free resources to level up your WordPress knowledge and skills.
\n\n\n\nIf you are looking for detailed technical notes on new changes, the WordPress 6.4 Field Guide is for you. Don’t forget to subscribe to the Developer Blog to stay on top of the latest development updates, tutorials, and more.
\n\n\n\nFor more information on installation, fixes, and file changes, visit the 6.4 release notes.
\n\n\n\n\n\n\n\nThe WordPress 6.4 release comes to you from an underrepresented gender release squad to welcome and empower diverse voices in the WordPress open source project.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nBeing part of the 6.4 release coordination team has allowed me to closely observe the intricate release process, where every detail, no matter how minor, is meticulously addressed—taking into account various factors like performance and backward compatibility. There’s still much to learn, but I feel fortunate to have had the chance to contribute to WordPress 6.4.
\nAkshaya Rane, 6.4 release coordinator team member
Over several weeks, the 6.4 release squad kept the release on track and moving forward by leading collective work, connecting ideas, and removing roadblocks.
\n\n\n\nWordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a global and diverse community of people working together to strengthen the software.
\n\n\n\nWordPress 6.4 reflects the countless efforts and passion of more than 600 contributors in at least 56 countries. This release also welcomed over 170 first-time contributors!
\n\n\n\nTheir collaboration delivered more than 1150 enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress open source community.
\n\n\n\n6adminit · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · aayusha · Abha Thakor · Abid Omar · Adam Silverstein · Adhun Anand · admcfajn · adrianduffell · aegkr · ahardyjpl · Ahmed Hussein · Ahmed Kabir Chaion · ajakaroth · Aki Hamano · Akihiro Harai · Akira Tachibana · Akshaya Rane · Al-Amin Firdows · Alain Schlesser · Albert Juhé Lluveras · Alex Concha · Alex King · Alex Lende · Alex Stine · Alexandre Buffet · Alisha Bajracharya · Allison Tarr · Alvi Tazwar · amedv · Ana Cirujano · Anand Upadhyay · Anders Norén · André · Andrea Fercia · Andrei Draganescu · Andrew Hayward · Andrew Hutchings · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrew Wilder · Andy Fragen · Andy Peatling · Ankit Gade · Ankit K Gupta · Ankit Panchal · Anna · Anne Katzeff · Anne McCarthy · Anne-Mieke Bovelett · anphira · Anthony Burchell · Anton Plauche · Anton Timmermans · Anton Vlasenko · Anveshika Srivastava · archon810 · arena · Ari Stathopoulos · Arnab Mondal · Artemio Morales · Arthur Chu · asafm7 · Aslam Doctor · Aurooba Ahmed · Austin Ginder · Ayesh Karunaratne · azharckra · Balu B · bangank36 · barbmiller · Barry · Bart · Basilis Kanonidis · Beatriz Fialho · behoney · ben · Ben Dwyer · Ben Greeley · Ben Hansen · Benjamin Intal · Benjamin Zekavica · benjaminknox · Benoit Chantre · Bernhard Reiter · Bernie Reiter · Bhrugesh Bavishi · Bijay Yadav · Binsaifullah · Biplav · Birendra Dhami · Birgit Olzem · Birgit Pauli-Haack · Block Themes Pro · bmalsht · bonger · bookwyrm · Boone Gorges · Boro Sitnikovski · Brad Jorsch · Bradley Jacobs · Brandon Kraft · Brandon Vreeman · Brian Gardner · Brian Haas · Brooke · Brooke. · Bud Kraus · Caleb Burks · Calvin Alkan · Carlo Cannas · Carlos Bravo · Carlos G. P. · Carolina Nymark · Cathi Bosco · ceer · cenkdemir · Chad Chadbourne · chased@si.edu · Chintan hingrajiya · Chip Bennett · Chloé Bringmann · Chris Runnells · chriscct7 · chrisdesrochers · codersantosh · Colin Stewart · Corey Worrell · Courtney Patubo Kranzke · Courtney Robertson · Crisoforo Gaspar · crstauf · Csaba (LittleBigThings) · Cupid Chakma · cybeardjm · Cyberchicken · Daisuke Takahashi · Dajeema Rai · Damon Cook · Damon Sharp · Dan Tovbein · Daniel Bachhuber · Daniel Richards · danieldudzic · Daniele Scasciafratte · Danielle Zarcaro · danieltj · darerodz · Darin Kotter · darkfate · Darren Ethier (nerrad) · Darshit Rajyaguru · Dave Loodts · dave03 · David Baumwald · David Biňovec · David Calhoun · David E. Smith · David Favor · David Herrera · David Ryan · David Smith · Dawid Urbanski · daxelrod · De Belser Arne · Dean Sas · Dee Teal · Deepak Vijayan · Denis Žoljom · Dennis Snell · Derek Blank · Derrick Tennant · Devan Ferguson · Dharmesh Patel · Dhrumil Kumbhani · Dhruvi Shah · Diane Co · Dilip Bheda · Dimitris Mitsis · Dion Hulse · DJ · dj.cowan · Dominik Schilling · doughamlin · Drew Jaynes · Earle Davies · Ebonie Butler · Edi Amin · Edward Caissie · Ehtisham S. · Ella van Durpe · Ellen Bauer · emailjoey · Emerson Maningo · Emily Clarke · Emily Leffler Schulman · emirpprime · enodekciw · Enrico Battocchi · Erik Betshammar · Esrat Sultana Popy · Estela Rueda · Fabian Kägy · Fabian Todt · Fabio Rubioglio · Faisal Alvi · Felipe Elia · Felix Arntz · Femy Praseeth · floydwilde · FolioVision · Francesca Marano · Frank Laszlo · Fredde Battel · fzhantw · Gabriel Koen · Ganesh Dahal · Garrett Hyder · Gary Cao · Gary Pendergast · Gennady Kovshenin · George Hotelling · George Mamadashvili · Gerardo Pacheco · Gio Lodi · Glen Davies · Gnanasekaran Loganathan · Gopal Krishnan · GOZER · gpotter · Grant M. Kinney · Greg Ross · Greg Ziółkowski · gregfuller · Guss77 · Gustavo Bordoni · gvgvgvijayan · Héctor Prieto · H.M. Mushfiqur Rahman · hanneslsm · Hanzala Taifun · Hareesh S · Harsh Gajipara · Hasanuzzaman · Haz · Helen Hou-Sandi · Hemant Tejwani · Hit Bhalodia · hlunter · Howdy_McGee · Huzaifa Al Mesbah · Ian Dunn · Incursa Designs · ironprogrammer · Isabel Brison · itecrs · Ivan Zhuck · jaimieolmstead · Jakaria Istauk · Jake Goldman · Jake Spurlock · James Hunt · James Janco · James Koster · James Roberts · james0r · Jamie McHale · Jamie Perrelet · Jamie VanRaalte · jane · Jarda Snajdr · Jari Vuorenmaa · Jarko Piironen · Jason Adams · Jason Cosper · Jason Crist · jastos · Jean-Baptiste Audras · Jeff Bowen · Jeff Chi · Jeff Everhart · Jeff Ong · jeffikus · Jeffrey Paul · jeflopo · Jeremy Felt · Jeremy Herve · Jeremy Yip · jeryj · Jesin A · Jessica Duarte · Jessica Goddard · Jessica Lyschik · Jick · Jip Moors · jivygraphics · Joe Dolson · Joe Hoyle · Joe McGill · Joen A. · John Blackbourn · John Hooks · John James Jacoby · John Regan · Jon Brown · Jon Cave · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Joona · Joost de Valk · JordanPak · jordesign · Jorge Costa · Joseph G. · Josepha Haden · joshcanhelp · joshuatf · JR Tashjian · Juan Aldasoro · JuanMa Garrido · Juliette Reinders Folmer · Justin Tadlock · Jyolsna J E · K M Ashikur Rahman · K. Adam White · KafleG · Kai Hao · Kalmang · Kalpesh · Kamrul Hasan · Karlijn Bok · Karol Manijak · Karthik Thayyil · Katie Ayres · kawsaralameven · Keanan Koppenhaver · Kelly Choyce-Dwan · Kevin Fodness · Kevin Miller · Kevin Taron · khleomix · Khokan Sardar · Kim Coleman · Kishan Jasani · kkmuffme · Koji Kuno · Konstantin Kovshenin · Konstantin Obenland · Kopila Shrestha · Krupal Panchal · Labun Chemjong · Lance Willett · LarryWEB · lastsplash (a11n) · lau@mindproducts.com.au · launchinteractive · Laura Adamonis · Laura Byrne · laurelfulford · Lauren · Laxmikant Bhumkar · Lee Willis · Lena Morita · Liam Gladdy · Linkon Miyan · Linnea Huxford · Lloyd Budd · Lovekesh Kumar · Luigi · Luis Felipe Zaguini · Luis Herranz · Luke Cavanagh · lunaluna · lyndauwp · Márcio Duarte · maciejmackowiak · madejackson · Madhu Dollu · Madhu Dollu · Maggie Cabrera · Mahbub Hasan Imon · Mahrokh · Mai · Maja Benke · maltfield · Manesh Timilsina · manfcarlo · Manzoor Wani · marcelle42 · Marcelo de Moraes Serpa · Marco Ciampini · Marco Pereirinha · Marcoevich · margolisj · Marin Atanasov · Mario Santos · Marius L. J. · Mark Jaquith · Marko Ivanovic · Marta Torre · Martijn van der Klis · martin.krcho · Mary Baum · Masoud NKH · mathsgrinds · Matias Benedetto · Matias Ventura · Matt Keys · Matt Watson · Matthaus Klute · Matthew Eppelsheimer · Matthew Farlymn · Matthew Haines-Young · matthewjho · maurodf · Maxwell Morgan · maysi · Md HR Shahin · meagan hanes · Mehedi Hassan · Meher Bala · Mel Choyce-Dwan · mer00x · merel1988 · Michael Arestad · Michael Burridge · Michael Showes · Michal Czaplinski · Michalooki · Michelle Blanchette · Michelle Frechette · Michi91 · Miguel Fonseca · Mikael Korpela · Mike Jolley (a11n) · Mike McAlister · Mike Schinkel · Mike Schroder · Mike Straw · Mikin Chauhan · Milen Petrinski - Gonzo · mimi · mitchellaustin · Monir · Mrinal Haque · mrwweb · Muhammad Arslan · Muhibul Haque · mujuonly · Mukesh Panchal · Mumtahina Faguni · Mushrit Shabnam · Myles Taylor · Nalini Thakor · nandhuraj · Nazgul · Nazmul Sabuz · Neil Hainsworth · nendeb · Nick Diego · Nicolas Juen · Nicole Furlan · nicomollet · nidhidhandhukiya · Niels Lange · Nihar Ranjan Das · Nik Tsekouras · Nilambar Sharma · Nilo Velez · niravsherasiya7707 · Nitesh Das · Nithin John · Nithin SreeRaj · Noah Allen · Nyasha · ockham · Ohia · okat · Olga Gleckler · Oliver Campion · OllieJones · Paal Joachim Romdahl · pannelars · Pascal Birchler · Paul Biron · Paul Kevan · pavelevap · Pedro Mendonça · pentatonicfunk · Pete Nelson · Peter Wilson · petitphp · petrosparaskevopoulos · Petter Walbø Johnsgård · Phill · Pieterjan Deneys · piyushdeshmukh · Plugin Devs · Pooja Bhimani · Pooja Derashri · Pooja N Muchandikar · pranavjoshi · Prashant · Presskopp · r-c · Rajin Sharwar · Ramon Ahnert · Ramon Corrales · Ramon James · Rebekah Markowitz · Remy Perona · ren · Renatho (a11n) · Rene Hermenau · Reyes Martínez · Riad Benguella · Rian Rietveld · Rich Tabor · Robert Anderson · Robert O\'Rourke · Robin · robpetrin · Rolf Allard van Hagen · Ryan Duff · Ryan McCue · Ryan Neudorf · Ryan Welcher · Sérgio Gomes · Sagar Tamang · Sajjad Hossain Sagor · Sakib Mohammed · Sal Ferrarello · samba45 · Samir Karmacharya · Sampat Viral · Samuel Wood (Otto) · Sarah Norris · Sarah Williams · Sarath AR · Satish Prajapati · saulirajala · saxonfletcher · Scott Kingsley Clark · Scott Reilly · Scott Taylor · Scout James · scribu · Sergey Biryukov · Sergio Scabuzzo · Seth Rubenstein · Shail Mehta · shawfactor · Shawn Hooper · shilo-ey · Shiva Shanker Bhatta · shresthaaman · Shubham Sedani · Simon Dowdles · Siobhan · Siobhan Bamber · Smit Rathod · sofiashendi · Sonia Gaballa · Soren Wrede · SourceView · Spenser Hale · Stephanie Walters · Stephen Bernhardt · Stephen Edgar · Steve Erdelyi · Steve Jones · Subodh Sunuwar · Subrata Sarkar · Suji K Chandran · Sumi Subedi · Sumit Bagthariya · Sumit Singh · Sunita Rai · suprsam · syamraj24 · Sybre Waaijer · Synchro · Sé Reed · Taco Verdonschot · Tahmid ul Karim · Tahmina Jahan · Takayuki Miyoshi · Tammie Lister · Tanvirul Haque · Teddy Patriarca · tejadev · thinkluke · Thomas Patrick Levy · tibbsa · Tiffany Bridge · Tim Nolte · timdix · Timothy Jacobs · tmatsuur · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tom Cafferkey · Tom H · Tom J Nowell · tomluckies · Tomoki Shimomura · tomsommer · Tony G · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · toscho · Tran Ngoc Tuan Anh · Trinisha · Trisha Salas · tristanleboss · TV productions · Ugyen Dorji · Ulrich · Umesh Balayar · Upadala Vipul · Utsav tilava · valentindu62 · Valerie Blackburn · Vicente Canales · Viktor Szépe · Vipul Ghori · vivekawsm · vortfu · Vraja Das · webashrafians · WebMan Design | Oliver Juhas · Weston Ruter · WHSajid · Will Skora · William Earnhardt · Willington Vega · Winstina · winterstreet · WraithKenny · wyrfel · Yoseph Tamang · Yui · zieladam · Zunaid Amin · Илья
\n\n\n\nOver 60 locales have translated 90 percent or more of WordPress 6.4 into their language. Community translators are working hard to ensure more translations are on their way. Thank you to everyone who helps make WordPress available in 200 languages.
\n\n\n\nLast but not least, thanks to the volunteers who contribute to the support forums by answering questions from WordPress users worldwide.
\n\n\n\nParticipation in WordPress is not limited to coding. If contributing appeals to you, learning more and getting involved is easy. Discover the teams that come together to Make WordPress, and use this interactive tool to help you decide which is right for you.
\n\n\n\n\n\n\n\nOver the past two decades, WordPress has transformed the digital publishing landscape and empowered anyone to create and share, from handcrafted personal stories to world-changing movements.
\n\n\n\nThe present and future of WordPress hold exciting opportunities for everyone, builders and enterprises alike. The foundational work for Phase 3 of the roadmap continues, with efforts focused on fostering real-time collaboration and streamlining publishing flows to improve how creators and teams work together in WordPress.
\n\n\n\nStay on top of the latest news and contributing opportunities by subscribing to WordPress News and the WP Briefing podcast.
\n\n\n\n\n\n\n\nThe smooth feel of jazz
The cutting-edge of the web
Install 6.4
The third release candidate (RC3) for WordPress 6.4 is ready to download!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC3 on a test server and site.
\n\n\n\nWordPress 6.4 is slated for release on November 7, 2023—less than a week away. If you haven’t tried it, now is the time.
\n\n\n\nYou can test WordPress 6.4 RC3 in three ways:
\n\n\n\nwp core update --version=6.4-RC3
Read the RC1 announcement for featured highlights, and check the Make WordPress Core blog for 6.4-related posts. If you are looking for detailed technical notes on new features and improvements, the WordPress 6.4 Field Guide is for you.
\n\n\n\nThe WordPress 6.4 release is brought to you by an underrepresented gender release squad to welcome the participation and partnership of those who identify as gender-underrepresented in the WordPress open source project.
\n\n\n\n\n\n\n\nThanks to everyone who has tested the beta and RC releases. Since RC2 was released on October 24, there have been more than 25 issues resolved. You can browse the technical details for all recent updates using these links:
\n\n\n\nIt’s recommended to use PHP 8.1 or 8.2 with the upcoming 6.4 release. Refer to WordPress 6.4’s PHP compatibility post for more details.
\n\n\n\n\n\n\n\nWordPress is open source software made possible by a community of people collaborating on and contributing to its development. The resources below outline various ways you can help, regardless of your technical expertise.
\n\n\n\nYour feedback and help in testing are vital to developing the WordPress software and ensuring its quality. It’s also a meaningful way for anyone to contribute. Check out this guide for instructions on testing WordPress 6.4 features.
\n\n\n\nThe core Query block requires more testing and feedback to ensure the latest changes to prevent full page reloads work smoothly. Please note that this setting was called “Enhanced pagination” but has recently been renamed, and it’s now referred to as “Force page reload” instead.
\n\n\n\nIf you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
\n\n\n\nCurious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
\n\n\n\nDuring the release candidate phase of WordPress 6.4, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.
\n\n\n\nDo you build themes and plugins? Your products play an integral role in extending the functionality and value of WordPress for users worldwide.
\n\n\n\nHopefully, you have already tested your themes and plugins with WordPress 6.4 betas. With RC3, you will want to continue your testing and update the “Tested up to” version in your plugin’s readme file to 6.4.
\n\n\n\nPlease post detailed information to the support forums if you find compatibility issues.
\n\n\n\nHelp the Docs team put the finishing touches on end-user documentation in time for the 6.4 release. Find out what’s needed and how you can help in this post.
\n\n\n\nDo you speak a language other than English? ¿Español? Français? Português? Русский? 日本? Help translate WordPress into more than 100 languages.
\n\n\n\n\n\n\n\nOne more week of prep
One more week to test the code
One more week til launch
Thank you to the following contributors for collaborating on this post: @meher, @rmartinezduque, @sereedmedia, @jorbin, @luisherranz, @marybaum.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16247\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"WP Briefing: Episode 65: Little Sun Success\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://wordpress.org/news/2023/10/episode-65-little-sun-success/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Oct 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16227\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:340:\"Join WordPress Executive Director, Josepha Haden Chomphosy, as she looks at a recent WordPress success story with Little Sun. To help us, we spoke to two special guests with Little Sun, Romane Guégan, Senior Press and Communications Manager, and Ashley Mrozek, Senior Digital Manager. Don’t miss this opportunity for an insider’s look!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:51:\"https://wordpress.org/news/files/2023/10/WPB065.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:21512:\"\nJoin WordPress Executive Director Josepha Haden Chomphosy as she looks at a recent WordPress success story, the clean energy solution Little Sun, and learns about their WordPress story.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Special Guest: Romane Guégan
Special Guest: Ashley Mrozek
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, I’ve got a special guest with me. I have here a couple of folks from Little Sun, a nonprofit organization that recently moved its entire online presence to WordPress. And we’re talking everything from their mission statement and donations all the way to their blog and shop.
\n\n\n\nWelcome both to the WordPress Briefing.
\n\n\n\n[00:00:59] Ashley: Thank you.
\n\n\n\n[00:01:00] Romane: Thank you.
\n\n\n\n[00:01:01] Josepha: We have with us Little Sun today. Can you start by introducing yourselves and your organization? Just tell us a little bit about what you all do.
\n\n\n\n[00:01:08] Romane: Hi, my name is Romane Guégan. I’m a Senior Press and Communications Manager at Little Sun.
\n\n\n\n[00:01:14] Ashley: And I am Ashley Mrozek. I’m the Senior Digital Manager.
\n\n\n\n[00:01:17] Josepha: So what does Little Sun do for the folks who are listening and maybe don’t know about it yet?
\n\n\n\n[00:01:22] Romane: Little Sun brings full power and light to communities that live off the grid, with the focus on sub-Saharan Africa because most of the people who lack access to electricity and need them. And we also inspire people to take climate action globally.
\n\n\n\n[00:01:39] Ashley: So access to solar energy helps kids who don’t have electricity and study at night. They can complete their homework at night. If their schools are in a more rural area, they will have a light to kind of guide them back home.
\n\n\n\nWe also work on a lot of electric vocation projects and hospitals. So we’re, we’re kind of supporting labors that are, are taking place in the evening, after the sun goes down, among other things.
\n\n\n\n[00:02:07] Josepha: Yeah. It’s, I, I think that that is one of the things that folks, probably most of my listeners, probably take for granted, like the easy access to light. And as we all know, the sun is around a lot. And so that is one of our most readily available resources other than potentially wind power. But I think that that is a great mission. And I really think that that’s wonderful work that y’all are doing.
\n\n\n\nSo, is there a particular reason that you focus on sub-Saharan Africa? Is that where you find a majority of people who don’t have access to that kind of resource are?
\n\n\n\n[00:02:43] Romane: Yeah. 70% of those people actually need in sub-Saharan Africa, where solar is actually a viable source of energy. Actually, it’s only 1% of solar, of the solar capital of the generation when we actually deliver solar energy there because there is so much potential.
\n\n\n\n[00:03:04] Josepha: That’s amazing. So you said that you all were funded in 2012. I imagine that your business has evolved over time. So, obviously, you all are WordPress users. That’s why we have you here with us today. But before we get into the questions about WordPress itself. Why don’t you tell us a bit about how your business needs evolved over time and how you wound up needing a solution that did use WordPress?
\n\n\n\n[00:03:31] Ashley: So I would say our focus and kind of the different initiatives that we’ve taken on since 2012 have shifted a lot based on various reasons, where our donors are, where we’ve kind of found the most need, and where we can be the most impactful.
\n\n\n\nAnd I think as we go into those new geographies, our online presence has become more and more important.
\n\n\n\n[00:03:55] Josepha: So, before you all switched to WordPress, I understand that you had several sites that you had to merge into one. And so I assume that as you evolved the business and your focus has changed, you realized you needed something a bit more streamlined. So, how was that transition, that migration from a lot of different sites to one big site?
\n\n\n\n[00:04:17] Romane: Yeah, because we started as a global project. And then, with the time, we evolved, actually also getting new donations. And in the past, we used to have one website where we have our webshop and our mission, our vision, all of our project descriptions.
\n\n\n\nBut then we had another website only for the foundation. And then you had another foundation in the U.S. So it was the question, okay, how do we put everything together? So we actually switched from littlesun.com to littlesun.org with WordPress, and it was amazing to see how we managed with the team to create an ecosystem approach, including impact, but also sales, and fundraising.
\n\n\n\n[00:05:02] Josepha: That was a big footprint that you all had, and you kind of consolidated it into one. And for all of our folks listening on the podcast, I’m going to include some links, not only to their site but then also to a few other things that we’ve mentioned in here today. So, since you made that change, how has it, how has that impacted the way that you all work with your site or with your online presence?
\n\n\n\n[00:05:27] Ashley: Yeah, I think using WordPress and having access to WordPress has been hugely valuable for us. We’re a small team, we’re a nonprofit, so it is pretty scrappy. Everyone is kind of doing a lot of different things. We don’t have a dedicated development team. And so being able to easily customize our pages and create new landing pages or make adjustments on the site without that development help has been valuable.
\n\n\n\n[00:05:55] Josepha: Yeah, so you don’t have a developer team now. Did you have a developer team when you had all the sites?
\n\n\n\n[00:06:01] Romane: We just still work with freelancers.
\n\n\n\n[00:06:03] Josepha: Okay, yeah. I am also not a developer, for what it’s worth, and have been working with nonprofits for a while. And I understand that problem where you have all these things you need to do and want to do, but there are also things you absolutely have to focus on in order to make your mission possible and your vision come true.
\n\n\n\n[00:06:23] Ashley: Yeah, and I think, I think WordPress has given us a lot more, like a lot more flexibility to kind of produce new content quickly. And because of that, it’s just been a lot more efficient, too, for us, you know.
\n\n\n\n[00:06:38] Josepha: And you all are using Blocks? Are you, like, the best Block builders?
\n\n\n\n[00:06:42] Romane: Yeah, I love Blocks.
\n\n\n\n[00:06:43] Josepha: Blocks are a fairly new innovation for the history of WordPress. WordPress has been around for 20 years, so we’re a nice, mature project. And we’ve really only had blocks as a functional part of the CMS for probably the last five or so. We’ve been working on the project a little bit longer. And it has been fascinating to me, like, in my own work that I have done with WordPress, kind of outside of my work with the project, to see, like, how much autonomy you get to have back as somebody who is not a developer, maybe isn’t a designer, but you do know exactly what you need to have on your site today, right?
\n\n\n\nAnd having to stop and find a freelancer or stop and find some set of developers who can make those changes. For me, when I was specifically working on nonprofit stuff. That was always kind of a moment where I was like, well, I guess I’ll just go to Facebook and put that on there or something because I was faster than trying to find someone to come help you. And so, I’m so glad you love the block.
\n\n\n\n[00:07:48] Ashley: We’ve created many a landing page.
\n\n\n\n[00:07:50] Josepha: Also, your site is adorable, and your brand is adorable, in case no one’s mentioned that lately. Super cute. Super cute.
\n\n\n\n[00:07:58] Josepha: So, we’ve talked about how you kind of took a bunch of stuff and made it into one big thing and how that’s been easier for you all to manage it. But from the standpoint of just, like, somebody who’s running a nonprofit, someone who’s running an organization, how has that transition been for your team? I know you said you don’t have a huge team, but was the move toward WordPress a net benefit over time, or was it immediately beneficial? Like, how has that been for your team?
\n\n\n\n[00:08:27] Romane: So what’s interesting actually is that we have a team that is spread also all over the world. And so we have teams in Berlin and in U.S., and New York. In Zambia, too. What was really interesting was how people identify to the new website because now we have to really think, okay, what is the content we want people to see, but also we want our critics to see. And so it kind of unified all of our content at Little Sun. And it was much more like much easier to understand afterwards.
\n\n\n\n[00:09:03] Josepha: Yeah.
\n\n\n\n[00:09:04] Romane: And it was because we also work at the intersection of creative communications, impacts, fundraising, technology, and to be able to put everything and have it on the front. And then have the stories to tell the stories from sub-Saharan Africa, from universities who got either a Little Sun lamps or solar systems, and then we have the donation page, so basically everything could be integrated in a super easy way, and it could target different audiences easily, either it’s someone who wants to partner with us, or a donor, or just someone who wants to be part of our solar training.
\n\n\n\n[00:09:46] Josepha: Yeah, and I mean, I think that no one will be surprised to hear that if you have multiple things that you have to get everybody to, it really increases the amount of marketing that you have to accomplish, rather than having one place for everyone to go too, and they can see everything that they might want once they arrive. So, that’s wonderful.
\n\n\n\n[00:10:06] Ashley: I think I was just going to say, or kind of echo what Romane said about the fact that we have so many different audiences, we have partners, we have donors, we have people who are just coming to learn about solar energy, or who are interested in purchasing a lamp. I think prior to this, it was a little bit confusing for those different audiences to kind of navigate to where they were intended to go to on the site, and now it’s much more cohesive. And we often hear that from people where it’s like, it’s quite easy to, to kind to find what they need to find on the site.
\n\n\n\n[00:10:39] Josepha: I define the WordPress community as anyone who is using WordPress, regardless of whether they know it or not. And so you all, in my mind, are part of the WordPress Community. And I just wondered if being part of that community has changed your approach to the way that you manage your content online or the way that you have chosen work with your business as like an online entity that also does on-the-ground, in-person thing?
\n\n\n\n[00:11:06] Ashley: I think definitely. I think we’re kind of going back to what I said before. I think we’re much more efficient now. I think in the past, it’s the idea of, like, well, getting this web page live or publishing this is going to be, you know, we have to think about a huge timeline, that’s, is going to require a lot of resourcing, a lot of different types of expertise and people, and everything now feels like something that we can, we can launch pretty immediately, which is really wonderful too.
\n\n\n\nI would also say just like being a part of the WordPress community too. It’s the sort of support that we’ve gotten from your team. It’s always really tailored. And I think as a nonprofit working with a, like, a much bigger business, you can be apprehensive sometimes, feeling like you won’t really get that personalized support.
\n\n\n\nAnd I think that’s something that’s been so nice with WordPress. Is really feeling like the people we’re working with are understanding our business and taking the time to understand our needs. And I think that makes us think differently about our online presence as well because then we feel like we have that additional support, which is great.
\n\n\n\n[00:12:12] Josepha: I’m always a fan of hearing that people who are passionate about WordPress are also passionate about helping others with WordPress. That’s one of my favorite things about us. That’s not true. I have like 25 favorite things about us. And so I need to stop saying that I have one favorite, but I never will.
\n\n\n\nOkay, well, do you all have any last thoughts that you just want to share with me or podcast listeners that we have?
\n\n\n\n[00:12:36] Ashley: Yeah, I think the, the plugins and integrations have been really useful for us. I think it can be really intimidating to bring on, like, a new tech solution or tool and feel like everything that you are already working with or have is going to become outdated or obsolete in some way. And I think it’s just been really nice to work with WordPress and have all of those transitions be really seamless for everything to connect really well. Yeah, I think that’s been. That’s hugely helpful too.
\n\n\n\n[00:13:07] Josepha: So, was that part of the decision-making process? Like, do I know that this software will be around in the future so that you’re making an investment in the site now and know that it’s going to hang around now you can find people help? Like, was that part of the decision-making process?
\n\n\n\n[00:13:21] Ashley: I think so. I mean, I guess I wasn’t completely around during the time, but I would say, like, that’s definitely something that we’re considering in any kind of tech that we’re thinking about is it can require so much work to, to kind of bring something on with such a small team. So we want to ensure that, yeah, it’s going to last, it has longevity, and it’s going to work with the tools that we already have. So I think all of that is really important for sure.
\n\n\n\n[00:13:48] Josepha: Well, thank you both so much for joining me. Like I said, we’ll have a link to littlesun.org in the notes so that you all can learn more about their project and see their beautiful site with their beautiful little solar sunflowers.
\n\n\n\nThank you both for being with me today.
\n\n\n\n[00:14:04] Romane: Thank you so much.
\n\n\n\n[00:14:05] Ashley: Thank you so much for having us.
\n\n\n\n[00:14:07] (Music interlude)
\n\n\n\n[00:14:11] Josepha: What a wonderful organization. I’m so glad that they found WordPress and that it works for them. Let’s continue our tour today with the small list of big things.
\n\n\n\nItem number one, it’s time to save the date: December 11th, 2023, for this year’s State of the Word. State of the Word is the annual keynote address delivered by the WordPress Project co-founder Matt Mullenweg. Every year, the event shares reflections on the project’s progress and aspirations for the future of open source. And so, if that is something that you like to tune into, December 11th is your day.
\n\n\n\nSecond thing on our list is that we are celebrating our 10,000th photo submission. So, on October 11th, the 10,000th photo was approved. The Photo Team is one of the newest ways to contribute to the WordPress open source project, and it feeds all of those photos into Openverse as well.
\n\n\n\nThe third thing on our list today is that I want to tell you about a community team training module that just came out. It’s specifically about the Translate Live tool, and it is ideal for presenting at your local meetups to engage and onboard new translators for your native language. If you’re organizing a WordCamp, consider introducing this tool during your Contributor Day. I will leave a link for this in the show notes so that it is easy to find.
\n\n\n\nAnd item number four, the journey to update WordPress.org, continues with the launch of a new Showcase design. The Showcase is a natural starting point for a lot of visitors who are on WordPress.org. It inspires creativity and also demonstrates what’s possible with WordPress. So, stop on by there, it’s WordPress.org/showcase, and give it a bit of a look.
\n\n\n\n[00:15:58] Josepha: And that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. And don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever a new episode drops. And if you like what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard today, you can share those with me at wprebriefing@WordPress.org.
\n\n\n\nI’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:16:24] (Music outro)
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16227\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 6.4’s PHP Compatibility\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2023/10/wordpress-6-4s-php-compatibility/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 26 Oct 2023 08:40:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"PHP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16235\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:340:\"In an effort to keep the WordPress community up to date, this post provides an update on the PHP compatibility of the upcoming WordPress 6.4 release scheduled for November 7, 2023. Recommended PHP version for WordPress 6.4 It’s recommended to use PHP 8.1 or 8.2 with this upcoming release. Please refer to the Hosting page […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3117:\"\n\n\n\n\nIn an effort to keep the WordPress community up to date, this post provides an update on the PHP compatibility of the upcoming WordPress 6.4 release scheduled for November 7, 2023.
\n\n\n\nIt’s recommended to use PHP 8.1 or 8.2 with this upcoming release. Please refer to the Hosting page for more detailed information, including a few known issues.
\n\n\n\nReach out to your hosting company to explore PHP upgrade options.
\n\n\n\nPHP is a programming language on which the WordPress code is based. This language runs on the server, and it is critical to keep it updated for security and functionality. Various teams within the WordPress open source project work to both test and fix any issues with new PHP versions so you can update with confidence that the WordPress core software is compatible.
\n\n\n\nHappy WordPress-ing!
\n\n\n\nThank you to @annezazu @barry @ironprogrammer @hellofromtonya @chanthaboune @costdev @javiercasares for reviewing and contributing to the effort of this post.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16235\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 6.4 Release Candidate 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 24 Oct 2023 16:45:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:11:\"development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16219\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:163:\"WordPress 6.4 RC2 is ready for download and testing. Reaching this phase of the release cycle is an important milestone. Check out what\'s new and how you can help.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Meher Bala\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:6586:\"\nThe second release candidate (RC2) for WordPress 6.4 is now available!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC2 on a test server and site.
\n\n\n\nWordPress 6.4 is slated for release on November 7, 2023—two weeks from today. If you haven’t tried it, now is the time.
\n\n\n\nYou can test WordPress 6.4 RC2 in three ways:
\n\n\n\nwp core update --version=6.4-RC2
Read the RC1 announcement for featured highlights, and check the Make WordPress Core blog for 6.4-related posts. If you are looking for detailed technical notes on new features and improvements, the WordPress 6.4 Field Guide is for you.
\n\n\n\nThe WordPress 6.4 release is brought to you by an underrepresented gender release squad to welcome the participation and partnership of those who identify as gender-underrepresented in the WordPress open source project.
\n\n\n\nThanks to everyone who has tested the beta and RC releases. Since RC1 was released on October 17, there have been more than 25 issues resolved. You can browse the technical details for all recent updates using these links:
\n\n\n\nWordPress is open source software made possible by a community of people collaborating on and contributing to its development. The resources below outline various ways you can help, regardless of your technical expertise.
\n\n\n\nYour feedback and help in testing are vital to developing the WordPress software and ensuring its quality. It’s also a meaningful way for anyone to contribute. Check out this guide for instructions on testing WordPress 6.4 features.
\n\n\n\nIf you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
\n\n\n\nCurious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
\n\n\n\nDuring the release candidate phase of WordPress 6.4, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.
\n\n\n\nDo you build themes and plugins? Your products play an integral role in extending the functionality and value of WordPress for users worldwide.
\n\n\n\nHopefully, you have already tested your themes and plugins with WordPress 6.4 betas. With RC2, you will want to continue your testing and update the “Tested up to” version in your plugin’s readme file to 6.4.
\n\n\n\nPlease post detailed information to the support forums if you find compatibility issues.
\n\n\n\nDo you speak a language other than English? ¿Español? Français? Português? Русский? 日本? Help translate WordPress into more than 100 languages.
\n\n\n\nYou have been waiting
Download and give it a test
RC2 is here
Thank you to the following contributors for collaborating on this post: @meher, @rmartinezduque, @michelleames, @cbringmann
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"16219\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:12:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Fri, 17 Nov 2023 12:52:26 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:25:\"strict-transport-security\";s:12:\"max-age=3600\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Wed, 15 Nov 2023 20:05:33 GMT\";s:4:\"link\";s:63:\"WooCommerce 8.3 was released today, featuring Cart, Checkout, and Order Confirmation blocks as the default checkout flow for new installations. This is a major milestone in moving WooCommerce towards a block-first checkout experience.
\n\n\n\nVersion 8.3 was slightly delayed, as core developers worked to ensure it would be compatible with the latest changes in WordPress 6.4 as well as the upcoming PHP 8.3 release scheduled for November 23, 2023. They also wanted to give time for plugin developers to prepare for the new reality of cart and checkout blocks as the default. An FAQ document outlines the steps for developers who still need to make their extensions compatible.
\n\n\n\nDevelopers with extensions that don’t work with the new default blockified checkout are encouraged to declare their plugins incompatible, so WooCommerce can display a message to users in the settings sidebar. (No action is required for plugins that do not extend the cart and checkout flow).
\n\n\n\n\n\n\n\nimage source: FAQ: Cart and Checkout Blocks by Default\n\n\n\nAlthough existing stores are not impacted by cart and checkout blocks becoming the default, merchants can easily opt into the experience using WooCommerce’s migration tool located at WooCommerce > Status > Tools > Create Pages. This tool will automatically generate the new pages with a block-based checkout flow. The blockified Order Confirmation template is currently only available to stores that are using block themes.
\n\n\n\nOther notable changes in WooCommerce 8.3 include the following:
\n\n\n\nWooCommerce 8.3 includes 682 commits to the core plugin, along with 231 commits rolled in from WooCommerce blocks, thanks to the efforts of 96 contributors. Check out the changelog for a more detailed look at the many fixes, tweaks, and enhancements included in the release.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 17 Nov 2023 03:16:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"Do The Woo Community: De Nederlandse WordPress Community – The Dutch WordPress Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78162\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"https://dothewoo.io/de-nederlandse-wordpress-community-the-dutch-wordpress-community/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:466:\"In ons programma Community Voices, WordPress Around the World zetten we de Nederlandse gemeenschap in de spotlight voor een gesprek in hun moedertaal.
\n>> The post De Nederlandse WordPress Community – The Dutch WordPress Community appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 09:27:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"WPTavern: Elementor Pro Pricing Update Slashes Features in the Essential Plan for New Customers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151354\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"https://wptavern.com/elementor-pro-pricing-update-slashes-features-in-the-essential-plan-for-new-customers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8024:\"Elementor, the most popular website builder plugin for WordPress with more than 5 million active installations, has announced major changes coming to the features included in its Elementor Pro Essential subscription plan.
\n\n\n\nThe plan will still include the Theme Builder along with access to 50+ Pro widgets, basic marketing tools, and the Form widget, but it will shift other more advanced features to the more expensive pricing tiers:
\n\n\n\n“Going forward, when you purchase the new Elementor Pro Essential, you will have all the features you need to create a complete basic website, and also gain access to new features that will be part of the Essential plan,” Elementor Senior Product Marketing Manager Gabriella Laster said. “For more professional capabilities like the Popup Builder, e-commerce features including PayPal button, Stripe button, and the full WooCommerce Builder or collaboration tools like Notes or the Role Manager, you will need to upgrade to the Advanced plan or higher.”
\n\n\n\nThe changes, which are detailed in a comparison chart in the announcement, will be rolled out on December 4, 2023. It will not affect existing subscribers or other subscription plans:
\n\n\n\n\n\n\n\n\nExisting Essential subscribers get to keep all current features.
\n
If you have a valid Elementor Pro Essential subscription, you can keep your subscription with all the features currently available to you, at no additional cost. You’ll also be able to renew your subscription upon expiration, while keeping all the features currently available in your plan. Some new features, released to the higher plans, will not be available as part of your current Pro subscription.
Scott Kingsley Clark, lead developer of the Pods Framework, commented on the news in Post Status’ Slack in regards to how Pods will support Elementor users in the future.
\n\n\n\n“Elementor Pro is removing things like ACF/Pods integration from their lowest tier ‘Essential’ plan in December,” Clark said. “Existing subscribers keep the functionality but anyone getting new licenses after Dec 4th won’t have those.
\n\n\n\n“It’s not super clear since I don’t use the other features whether they’ve removed many other things or if some of those things are actually new features shipping in December to just the other plans.
\n\n\n\n“The impact of this is that I’ve chosen to replace the Elementor Pro integration for Pods that they provide — with a more complete alternative solution within the Page Builder Toolkit add-on. Previously, only new Pods-centric widgets were added. Soon I’ll add dynamic content support for Pods that will be available as a better alternative to what is in Elementor Pro currently.”
\n\n\n\nConcerned Elementor customers reacted to the news on X/Twitter as well as in the comments of the announcement, many looking for reassurance that the features they paid for will still be accessible to them after the change.
\n\n\n\nThe anti-Elementor crowd responded to their concerns in a critical and dismissive way, using the news of the modified plans as an opportunity to express and reinforce their disapproval of the page builder. This prompted those who are reluctantly using the tool to ask for viable alternatives in the comments of the tweet.
\n\n\n\n \n\n\n\nElementor has had a somewhat contentious relationship with the open source project, as it has historically marketed itself against WordPress core. The plugin’s reputation has been saddled with bloat and performance concerns for years, calling its long-term future into question. The writing was on the wall for most page builders when WordPress decided to land full-site editing capabilities in core.
\n\n\n\nElementor has made a pattern of making major changes to pricing and plans while also guaranteeing legacy pricing for current customers. It’s one strategy for getting customers to lock in their auto-renewals to ensure a more predictable financial future for the company.
\n\n\n\nTwo months ago, Human Made engineer Fränk Klein sparked a conversation on X/Twitter contending that “Elementor will disappear as a standalone plugin, along with all other non-block page builders,” as the WordPress ecosystem moves to become block-first by default.
\n\n\n\n“Since 2022, all default themes are block themes,” Klein said. “WordPress.com is all in on blocks. WooCommerce is modernizing with blocks.
\n\n\n\n“For plugin authors the biggest return on investment is to use blocks. So it falls to the page builder developer to ensure that plugins integrate well. And that’s a difficult, tedious, and costly undertaking.”
\n\n\n\n \n\n\n\nWordPress co-founder and Automattic CEO Matt Mullenweg also weighed in on the news, indirectly referencing Elementor’s latest move to slash features in its Essential tier.
\n\n\n\n“As Gutenberg gets more capable, non-Gutenberg site builders will likely need to continue raising their prices, as one is in the news for today, to maintain revenue churn in the face of higher churn and fewer new users,” Mullenweg said. “I don’t [think] this trend will happen for the Gutenberg-based ones.
\n\n\n\n“They’ll also need to spend more to keep up, as they have to duplicate all the engineering that’s going into core. This is why we asked them all to plan on Gutenberg since we started development in 2017. Phases 1 and 2 also could have gone a lot faster with their help. The pace of iteration is pretty relentless.”
\n\n\n\nElementor’s decision to reallocate features across pricing tiers is a response to the shifting dynamics within the page builder landscape and the increasing cost of supporting so many third-party integrations in the entry level plan. WordPress users and developers are slowly reevaluating their relationship with page builders, as every core release puts a greater emphasis on block-based editing for both content and design. This is a fundamental shift in how WordPress websites are built and page builders will continue to be challenged in striking a balance between innovation, user expectations, and business sustainability.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Nov 2023 04:37:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WordPress.org blog: State of the Word 2023 – Madrid, Spain\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16429\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2023/11/state-of-the-word-2023-madrid-spain/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3672:\"\n\n\n\nThe countdown is on for this year’s State of the Word! If you missed the initial announcement a few weeks ago, you’ll want to mark your calendars for December 11, 2023.
\n\n\n\nState of the Word is the annual keynote in which WordPress co-founder Matt Mullenweg celebrates the progress of the open source project and offers a glimpse into its future.
\n\n\n\nFor the first time, State of the Word ventures beyond North America, bringing the WordPress community to a new and vibrant city that plays a vital role in the WordPress project — Madrid, Spain! The event will be live-streamed to WordPress enthusiasts and newcomers around the globe via the WordPress YouTube channel.
\n\n\n\nPlease visit the event website for more event details and live-streaming information.
\n\n\n\nWhat: State of the Word 2023
When: December 11, 2023, 15:00 UTC (Start of live stream)
Where: Palacio Neptuno, Madrid, Spain
Streaming: Watch the live stream on the WordPress YouTube channel.
Tickets: Request a ticket to attend in person.
Please note that the venue’s capacity is limited; therefore, not all ticket requests will be granted.
Meetups: The community will sponsor several local watch parties globally, both in
person and online. Find one near you or organize one.
State of the Word will include a Q&A session. If you want to participate, you can send your question to ask-matt@wordcamp.org or ask during the event via the Q&A app Slido. A QR code for your submission will be provided during the event live stream.
\n\n\n\nGiven the volume of questions usually submitted, only some will be answered live, while others will be covered in a follow-up post published after the event on make.wordpress.org/project.
\n\n\n\nIs this your first State of the Word? Check out prior events on WordPress.tv for an introduction to the format.
\n\n\n\nSee you in person and online on December 11!
\n\n\n\nThank you to Reyes Martínez and Chloé Bringmann for reviewing this post.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Nov 2023 20:03:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"WPTavern: #99 – Matthias Pfefferle on ActivityPub, WordPress and Decentralised Social Networks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=151341\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:109:\"https://wptavern.com/podcast/99-matthias-pfefferle-on-activitypub-wordpress-and-decentralised-social-networks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:54692:\"Transcript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.
\n\n\n\nJukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, how the ActivityPub plugin can make WordPress the center of your social networks.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox and use the form there.
\n\n\n\nSo on the podcast today, we have Matthias Pfefferle. Matthias started using WordPress in its early stages when it was still known as b2. He became passionate about blogging and the web 2.0 era. Over time he dedicated himself to making blogging relevant and developed various tools to compete with social networks, building communities professionally and working for a European hoster. Matthias ultimately joined Automattic to focus on WordPress and the ActivityPub plugin full-time.
\n\n\n\nWe start off talking about the importance of owning your own content, and how it grants us control over what gets published and when it gets deleted or amended, Matthias introduces us to Mastodon, a social network that operates on a non algorithmic, chronological feed. This means that the content is displayed in the order it was created. Breaking free from possibly addictive patterns we see in other platforms.
\n\n\n\nWe learn about the Fediverse, where users can set up their own servers and customize their own rules. Matthias explains how servers communicate with each other through following and federating, creating a truly decentralized network. He shares insights into how relays can be used to generate traffic and activity on new Mastodon servers should you find your feet a little quiet at the start?
\n\n\n\nThere’s definitely some new workflows to learn using the Fediverse and Matthias highlights the differences between Twitter and the Fediverse, with the latter starting off quiet and gradually growing as users find and interact with others.
\n\n\n\nHe introduces us to the ActivityPub plugin for WordPress, which allows users to publish their blogs on Mastodon, and federate the content to different servers. We get an explanation of how it works, what it does, and where it strays from the way you’re used to interacting with a proprietary platform.
\n\n\n\nWe discussed the various waves of migration to Mastodon and the factors that triggered them, including Reddit’s decision to monetize that API. Matthias sheds light on the challenges faced by decentralized networks, and how wordpress.com has implemented his ActivityPub plugin, albeit in a modified form, making it easier for users to migrate their accounts. The adoption of the plugin has been steadily rising and Matthias expresses his confidence in the plugin’s potential, citing the press coverage and impact of Automattic’s takeover.
\n\n\n\nHe also provides insights on how interactions on Mastodon federate, explaining how likes, comments, boosts, updates or deletions to blog posts are reflected across platforms.
\n\n\n\nTowards the end, Matthias shares his thoughts on the future of federated social networks and the potential support from existing platforms like Meta. He emphasizes the profound benefits of using protocols like ActivityPub, allowing users to own their own data and have more control over their content, unlike closed platforms that can delete accounts and cause data loss.
\n\n\n\nIf you want to learn more about the Fediverse, Mastodon, ActivityPub, or just want to know how to make WordPress a first-class citizen in social networks, this podcast is for you.
\n\n\n\nIf you’re interested in finding out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast. Where you’ll find all the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Matthias Pfefferle.
\n\n\n\nI am joined on the podcast by Matthias Pfefferle. Hello, Matthias!
\n\n\n\n[00:05:03] Matthias Pfefferle: Hello, Nathan.
\n\n\n\n[00:05:04] Nathan Wrigley: I’m really, really pleased to have you on the podcast today. This topic is something which is actually quite dear to my heart. Sometimes we stray into these topics. But Matthias is here today to talk about ActivityPub.
\n\n\n\nThis may be something that you’re entirely familiar with. It may be something that you have never heard of before. Perhaps a better way to describe it would be the Fediverse, or maybe even Mastodon, that might get your intuitions going.
\n\n\n\nBefore we get stuck into all of that, Matthias, I wonder if you wouldn’t mind just telling us a little bit about your background with WordPress or technology, whichever way you wish to take it. But little bio just to give us an indication of who you are.
\n\n\n\n[00:05:42] Matthias Pfefferle: Okay. I started with WordPress when it was called b2. So it was really early, and I fell in love with the whole blog thing and the web 2.0 area. I think over the time I tried to keep that momentum and tried to keep blogging relevant. And I think that’s why I built a lot of stuff around WordPress to compete with social networks, and made that in my spare time and liked that and made it my profession.
\n\n\n\nI started on the bad side, professionally building communities, and then I had a quite long time at a European hoster, and finally I joined Automattic to work full time on WordPress and ActivityPub.
\n\n\n\n[00:06:36] Nathan Wrigley: How long ago was it that you joined the Automattic crew?
\n\n\n\n[00:06:40] Matthias Pfefferle: It was this year, it was in April.
\n\n\n\n[00:06:42] Nathan Wrigley: Yeah. I remember the news coming out, and I was so delighted of this news because of everything that we’re going to talk about today. I was delighted because it enables you to concentrate full time I think, I could be wrong about that, but I think you’ve got the opportunity to work full time on a plugin.
\n\n\n\nIt’s a freely available plugin. It’s called ActivityPub, it’s two words combined as one really. And ActivityPub combines the Fediverse really. It’s the architecture that’s going on behind all things in the Fediverse. It’s the protocol, if you like, which binds all of the different social networks and things which sit on top of it.
\n\n\n\nI feel it might be a good idea to actually explain what ActivityPub is, and what it does and how it works. Now I realised we haven’t got any screens on, I realise some of it might be a little bit difficult to explain. But broadly speaking, what is the ActivityPub protocol? Not your plugin just yet, but what is the protocol, and how does it sit behind the Fediverse?
\n\n\n\n[00:07:45] Matthias Pfefferle: I think I would like to start with the Fediverse because that’s even older. The Fediverse is also a word combination between federated and universe, and it’s kind of the idea to have decentralised social networks. It’s not directly equated with ActivityPub, but I think the actual protocol that every social network, every decentralised social network is speaking is ActivityPub. So at least for the time being, you can equate that.
\n\n\n\nBut the idea of the Fediverse is way older than Mastodon and ActivityPub. And ActivityPub is kind of the newest protocol. There were way more over the years. Maybe Diaspora, someone remembers Diaspora back in the days. The Facebook killer.
\n\n\n\nThe actual protocol is ActivityPub. And I think ActivityPub is so famous because of two different things. The one is that it’s fairly easy to implement. And the other thing is that Mastodon made a real good product on top of it. Really nice, usable product. Nice UI, easy to understand.
\n\n\n\n[00:09:04] Nathan Wrigley: So does the ActivityPub protocol, does it govern things like, for example, this is a piece of text, this is an image, this is a poll, this is published on this particular date. What exactly is it in a sort of technical sense?
\n\n\n\n[00:09:20] Matthias Pfefferle: Let’s talk about that. ActivityPub is the email version of a social network. Every server has, or every user has, its outbox and inbox at a server. And they’re floating activities from your outbox to the other inboxes and vice versa. And an activity describes every activity you can do on a social network.
\n\n\n\nIt’s follow, create a post, delete a post, unfollow. And everything is described in a unified json object. And it’s really easy to understand and to model these activities. And it’s really only kind of the same modeled activities floating back and forth between the different servers, describing everything you just did or do.
\n\n\n\n[00:10:15] Nathan Wrigley: Okay, it’s the protocol which sits behind all of the typical things which a social network would need. So in that case, I guess the next question from me would be, who decides what’s in the protocol? Is it an open platform in the same way that WordPress is? And who decides ultimately which ideas get adopted, which ideas don’t get adopted?
\n\n\n\nIs it a fairly glacial experience working with it? In other words, has it settled down over the years and is basically now not that much flux going on? Or yeah, how movable, how changeable is it, and who is in charge of deciding what goes in it?
\n\n\n\n[00:10:52] Matthias Pfefferle: That depends. The protocol was defined by the W3C. So it’s well crafted specification. But it wasn’t updated since it first was published. So the initial version was published by the W3C, and back in the days they worked together with different communities, also the IndieWeb community. There were a bunch of people of the IndieWeb community involved, and there were also the authors of a predecessor of the ActivityPub protocol, OStatus, and later ActivityPump I think.
\n\n\n\nBut the original specification doesn’t change over the time. But specification is based on, ActivityPub is based on JSON-LD, and JSON-LD is defined to be extensible. So you do not have to change the spec to add your own kind of flavor to the activities, or to define your own activities.
\n\n\n\nThe actual version we are currently using is mostly defined by Mastodon, because Mastodon is kind of the big player in that area. So the Mastodon community added lot of extra stuff on top of ActivityPub and made their own extensions to the activities. And because they’re the biggest one, and require a lot of these extensions, I think the current used version is highly customised by, or influenced by, Mastodon.
\n\n\n\n[00:12:40] Nathan Wrigley: Okay, great. Thank you. So that’s really interesting. There’s a lot in there that I didn’t actually know, so thank you for that. How does the use of the ActivityPub protocol, and you described that the Fediverse is older, and it basically means decentralised networks. How does that differ from the networks that we’re all very familiar with?
\n\n\n\nSo I know it’s a very obvious question, but it may very well be that there’s people listening to this who’ve never experienced a decentralised network. So let’s put, say something like Mastodon, let’s just use that as an example, as a social network if you like. Let’s compare it to another incumbent, something like Twitter or Facebook.
\n\n\n\nHow does ActivityPub allow things to be different? What are basically the key differences between an implementation on ActivityPub and some closed system like Facebook or Twitter or something?
\n\n\n\n[00:13:30] Matthias Pfefferle: I think you can compare that also with email perfectly, because it doesn’t matter where you host your email address. It can be the big player, you can host it on your own. The one you want to send an email to always receives the email.
\n\n\n\nAnd that’s kind of the same for Mastodon. It doesn’t matter on which Mastodon server you are, or you registered. You can follow everyone on every other Mastodon server, regardless of the country of the hosting environment. And not even limited to Mastodon, but you can follow everyone that is using, or everyone that is using a platform that uses ActivityPub, if that makes sense.
\n\n\n\n[00:14:14] Nathan Wrigley: That’s perfect. I think the email analogy is really excellent, in the sense that we’re all using different providers for email, but it would be an entirely pointless enterprise if I could only communicate with you, if you were sharing the same email hosting company that I was. That would make the whole thing completely inoperable.
\n\n\n\nAnd I guess at this point, it might be a good idea to explain what you were talking there about Mastodon instances. So we’ve thrown the word instance out there. And if you’ve used social networks before, you’re much more familiar with the notion that you sign up for that network and you’ve got to log in credential for that network. And wherever their computers are stored in the world, it doesn’t matter. You sign in, you go to their homepage, you log in and you are logged in.
\n\n\n\nMastodon and all of these other things built on top of ActivityPub, the Fediverse, for want of a better word. They operate on a completely different model, in that you can set up your own instance of Mastodon. You can set one up, I can set one up. In fact I have set one up. And I’m sure you have set one up. In fact, I’m sure you’ve probably set up dozens in your work that we’re going to talk about.
\n\n\n\nAnd mine will interoperate with yours. So you will be able to communicate with me. The people from yours will be able to see the people from mine. And it’s a social network, but it’s not housed behind one company. It’s made of hundreds, thousands, tens of thousands, millions of smaller entities all talking to each other. Have I described that correctly?
\n\n\n\n[00:15:41] Matthias Pfefferle: Perfect.
\n\n\n\n[00:15:42] Nathan Wrigley: If that’s the case, the way that Mastodon and all these other things are set up, does that cause a bit of friction for people? Because everybody’s so familiar with, you go to the homepage, you create an account, and from that moment on everything’s really straightforward. You log into that service and you start creating your content. Or posting, or communicating, or chatting, whatever it may be.
\n\n\n\nWith Mastodon and other services there’s a little bit of friction there because it’s not that typical workflow. You’ve got to decide on an instance. And I wonder what your intuitions are, as to whether or not that has caused people to be a little bit sceptical of how it works and maybe stopped the growth that we might have had.
\n\n\n\n[00:16:20] Matthias Pfefferle: That’s a really good question. And I think it’s because of, we are at the beginning of this new federated idea of social networks. And I think in that beginning, it’s really complicated to understand that there are different servers that do the same in the end, and how to choose your server, and how the following process is working. Because it’s not simply searching for the username, because he could be on a different server and not well known on the server you are on.
\n\n\n\nBut I think that’s a problem for the time being. But for the future, if you do not really choose the platform anymore, because the normal platforms you are already using will support ActivityPub. I do not think that this will be a friction in the next five years.
\n\n\n\n[00:17:18] Nathan Wrigley: Yeah. So maybe it’s just a consequence of the age of it. You’ve got to select a server right at the outset, and maybe somebody will come up with some amazing UX which just solves that problem, and makes that whole thing go away.
\n\n\n\n[00:17:31] Matthias Pfefferle: Yeah. But not only because of that. But let’s talk a bit about Meta and their new Threads community. They try to build up a microblogging service. And they plan to do that in the open and to support ActivityPub. And if such a big server, and such a big company decides something like that, then a lot of users simply use ActivityPub without knowing.
\n\n\n\nAnd others can follow them, and if you take the ActivityPub thing for WordPress. If you simply enable ActivityPub for WordPress, and you simply use WordPress as you always do, publishing posts, writing comments. And I think it’s not that big of a step if now others can follow you in a different way.
\n\n\n\nAt the moment you really have to decide to go into the Fediverse. You have to decide, I want to have an account on this Mastodon service. But I think in the near future, it’s kind of more ubiquitous. It’s kind of the services will support that and you do not have to actively decide to use it. But you simply have to understand that following is a bit different, if that does make sense.
\n\n\n\n[00:18:52] Nathan Wrigley: Yeah, we can get into all of that in a moment. So you mentioned Meta, Facebook, if you like, and Threads, which is their equivalent platform to something like Twitter or Mastodon or what have you. And the promise that at some point it would in fact interoperate with ActivityPub. Do you know if they followed through with that?
\n\n\n\nIn other words, did it interoperate with ActivityPub from the outset, or are they still in some sort of holding pattern where they’re checking it all worked? Because you’re right, somebody, some giant entity like Meta, Facebook, if they are throwing their weight behind it, it does cause everybody by default to start using ActivityPub without them knowing it.
\n\n\n\n[00:19:29] Matthias Pfefferle: They’re still experimenting with ActivityPub. There’s nothing published yet.
\n\n\n\n[00:19:35] Nathan Wrigley: It’s interesting, isn’t it? A company of size of Meta in these sort of experimental phases. Let’s hope that they honour that.
\n\n\n\n[00:19:42] Matthias Pfefferle: That’s what I meant with, this would be a game changer. Because this would allow my mum or my sister to be part of the Fediverse without knowing it. And they can simply use that without all the technical stuff we are discussing at the moment.
\n\n\n\n[00:19:59] Nathan Wrigley: So just from your perspective, and this question really is about you and what your thoughts are on it. Why do you prefer using ActivityPub, Mastodon, again these terms are sort of somewhat interoperable. But let’s go with Mastodon for the sake of argument.
\n\n\n\nWhy do you prefer using something like that to a quotes, closed platform like Twitter or LinkedIn or whatever it may be? What are some of the benefits that we may not have thought about before? Some of the consequences of using an open protocol as opposed to a closed protocol.
\n\n\n\n[00:20:35] Matthias Pfefferle: I think the biggest thing is owning my data, to not be dependent on a closed platform that can make everything with my data and decide if I can use or cannot use the platform. They can decide what I have to show, how my profile looks, and what are the security settings, what are the visibility settings.
\n\n\n\nI read an interesting article and the title was something like, the privilege of deleting a Facebook account, something like that. You put your whole life into a platform. You have your complete social graph, all your friends there. And if Facebook, for example, decides to ban you because of they decided, then you will lose not only all of your data but connection with your friends.
\n\n\n\nBack in the days, a lot of events only happened on Facebook. You decide who comes with an invite on Facebook. So if you’re not on Facebook, you will not be invited, in the worst case.
\n\n\n\nAnd back in the days I decided that I do not want to depend all of my life on such a closed network, and I want to choose where to publish stuff and if I want to delete it, if I want to share that. Yeah, I want to decide how and what to do with my content. And to be able to migrate platforms, for example, to not depend on a certain hosting environment, for example, or a certain platform.
\n\n\n\n[00:22:15] Nathan Wrigley: I guess it all sounds, unless that’s actually happened to you, the whole deleting of an account. It sounds almost like an implausible thing which would never happen. But I can definitely say from, not personal experience, but a very, very close friend of mine. For no reason whatsoever his Facebook account was deleted.
\n\n\n\nAnd this was fairly catastrophic because a lot of the network of friends that he had established was in Facebook. A lot of the content over the years that he had produced was in Facebook, and it disappeared. And to this day, this was probably about 8 or 9 months ago, to this day it has not come back.
\n\n\n\nAnd so I guess, dear listener, you’re probably a WordPress user if you’re listening to this podcast. The argument of owning your own content is not to be underestimated. Having everything that you’ve created at your disposal, when you like. You get to decide whether you delete your content. You get to decide which things get published, when and how it looks. All of that is absolutely the case.
\n\n\n\nI think for me, just extending what you said there Matthias, some of the things that are important to me on Mastodon as a social network, some of the benefits that I see is the non algorithmic feed. So the protocol in the current implementation at least, who knows what will happen in the future.
\n\n\n\nThe protocol spits out content only based upon the time at which it was created. So it’s a completely chronological feed. So if I don’t log in for six weeks, I will see the thing that was posted five minutes ago, as opposed to the thing which was posted six weeks ago. And it will be my job to scroll back in time.
\n\n\n\nPlus that feed is not being inspected by any kind of AI or sophisticated technology to punctuate it with advertising or sponsorship. And there’s no gamification about which things will arrive in my feed. So something which is proving to be popular gains no more weight in my feed than something which is not popular.
\n\n\n\nAnd so in that way, the whole enterprise is not engineered to keep me addicted to that feed, and keep scrolling, and keep looking, and keep investing more and more time. The purpose is just to serve it up chronologically. And it’s a real breath of fresh air, because you really do suddenly realise, okay, I am not spending a large amount of time on this because I’m not being gamed by the billions of dollars of AI investment that’s gone into making sure that I stay there as long as possible.
\n\n\n\nSo for me, there are a couple of other things there which really were beneficial. Although, maybe on the face of it, they don’t seem like it.
\n\n\n\n[00:24:50] Matthias Pfefferle: Yeah, exactly. And even if you would like to have some kind of AI powered algorithmic feed, then you can search the platform who supports that. That’s the nice thing about the Fediverse, you can choose the platform for your own preferences.
\n\n\n\n[00:25:06] Nathan Wrigley: So let’s just dwell on that a little bit. How do these servers communicate with each other? So, for example, I would imagine that the listeners to this are fairly technical. They’ll understand, you know, installing software on a remote server and things like that.
\n\n\n\nIf I wish to set up my own server, I can do that. I can download the software and if I’m prepared to read through the how to articles, I could set myself up with a server. It’s not without its difficulties, but there are also third party hosting companies, which will abstract away the difficulty in exchange for a few US dollars each month.
\n\n\n\nBut I could set up my server and I can come up with my own set of rules. I can invite people, block people, block other servers, allow everything, disallow everything, whatever I like. But, how do they actually communicate with each other? In other words, if I set up a brand new server, how does it even know what the other servers are doing? How does it begin to communicate with them all?
\n\n\n\n[00:26:01] Matthias Pfefferle: If you simply install a server, there will be no communication at all. So it simply starts with following others on different servers. And then start writing, and then it starts federating. So with the first user or the first follower on a different server, your server starts federating with others.
\n\n\n\nBut if it’s simply you, no followers, or only followers on your server, it will be a very simple and very lonely ecosystem.
\n\n\n\n[00:26:32] Nathan Wrigley: There would be utility in that though. If you wish to have a server, let’s say that you’ve got a company with a thousand employees, you could set up a server, block it looking out into the wider world and just stay in its own boundary. And in a sense you’ve got yourself a little intranet, if you like. You’ve got yourself social network for your own employees and nobody in that can reach out and discover anything elsewhere. So even that use case has its own purpose.
\n\n\n\n[00:26:56] Matthias Pfefferle: Yeah. And there’s also a concept of relays. So if you set up a new Mastodon server, and you want to have some traffic, or you want to see some posts in the global timeline, then you can subscribe to relays. And they will start federating without you following someone. So you can decide. You can decide if you want to start simple and start small, or if you want to have at least some kind of activity on your platform.
\n\n\n\n[00:27:29] Nathan Wrigley: It is quite interesting when you first sign up, because if you sign up for, let’s pick a service, let’s go for Twitter. And you supply them with a username and a password, and you go through the onboarding wizard. The first thing that you see is a full feed. There’s content that they have decided would be appropriate for you, probably based on all sorts of algorithmic ways of keeping it sticky and engaging for you.
\n\n\n\nBut your feed will immediately be full. Whereas the exact opposite is true on the Fediverse. Ignoring all the relays, let’s just imagine that you set up your own instance. You are basically in a vacuum until you start finding people. And then you interact with them and that they are sharing, it’s called a boost. They are boosting other people’s content. And in that way, then you get to see other people.
\n\n\n\nYou can then follow them and this nice organic system of growth, you can imagine it almost like a tree growing out the ground and branches start to appear and further branches and other branches. All of that starts to happen. And it really doesn’t take very long before your feed is, well, as full as you want it to be.
\n\n\n\n[00:28:29] Matthias Pfefferle: Exactly.
\n\n\n\n[00:28:30] Nathan Wrigley: And so that whole system, ultimately though, I feel is a quieter system. That feed, because you’re only following people that you wish to pay attention to. And of course, as with all things, you can decide that you no longer want to follow people, or you can decide to block people, or block whole servers and what have you.
\n\n\n\nOkay, so we’ve spent a little bit of time figuring out what ActivityPub is. Your role at Automattic is working on the ActivityPub plugin. Now am I right in saying, Matthias, this was your brainchild in the beginning? Did you fork this plugin or was this your baby right from the start?
\n\n\n\n[00:29:04] Matthias Pfefferle: That was my baby right from the start. It was not the first experiment with decentralised social networks. But the most famous in the end I think.
\n\n\n\n[00:29:15] Nathan Wrigley: It’s all worked out very well. You know, with the benefit of hindsight, oh, all of the bricks were nicely laid to make the wall. But sounds from the conversation that we had before we hit record as if much of this was by chance and it’s just worked out brilliantly. So what does it do?
\n\n\n\nObviously it’s a plugin. We install it and activate it in WordPress. What is the intention of the plugin? Now I realise that there may be bits of this that are roadmap. It may be that we only want to talk about the things which are in it in October 2023. But what broadly is the intention? What is it trying to do?
\n\n\n\n[00:29:47] Matthias Pfefferle: The first intention I had with it was to simply be part of the Fediverse. Others can follow your blog on Mastodon. So it started with a focus on publishing. Not being a full flavored social network, but simply starting with publishing. That means that users can no longer only follow your RSS feeds or Atom feeds, but also can follow your blog users on the Fediverse. And everything you publish on the blog will be federated to the different servers.
\n\n\n\n[00:30:22] Nathan Wrigley: Can I just interrupt you there? Sorry, just to be clear. You use the word federated as verb, it’s a thing which is being done. But what is being done there? So if I’m on my WordPress website and I go add new post, write a post, click publish. Normally that just publishes the post and people have to find it, you know, through Google or what have you. What’s the additional thing? What’s the federated bit in there? What is happening?
\n\n\n\n[00:30:44] Matthias Pfefferle: That’s kind of the same thing with Mastodon. If someone on Mastodon follows your blog, then he kind of subscribes to your posts. And every time you write a new post, this post will be sent to the inboxes of all your followers. And they will see your post kind of the same way they see a different Mastodon post. So on Mastodon, you could not see any difference between a WordPress blog post, or a post that was directly posted on Mastodon.
\n\n\n\n[00:31:17] Nathan Wrigley: So in effect, is it the same as if I had not used the ActivityPub protocol? I published something on my WordPress site, and then I had gone and meticulously copied and pasted, let’s say, the excerpt, the title, carried across the featured image, or what have you, and gone to the social network and posted it. In effect, are we looking at the same thing? It just automates that process of posting it onto Mastodon.
\n\n\n\n[00:31:41] Matthias Pfefferle: Not directly, because what you mentioned is cross posting. That means what we did in the early days with the WordPress social media things. And that’s copying the post. That means you have to have a profile on Twitter, on Facebook, on Mastodon, you name it. And then this profile was used to publish, to republish your content, or kind of parts of your content.
\n\n\n\nAnd the new thing is that you do not cross post anymore. It’s the natural ActivityPub way you do that. So it’s not you need a Mastodon account and then you copy all your stuff, or you publish all your stuff through that Mastodon account. It’s your blog user is the Mastodon account. Others can follow your account or the whole blog directly, without copying stuff. It’s really, the whole ActivityPub, Fediverse following experience.
\n\n\n\n[00:32:39] Nathan Wrigley: Okay. Let’s explore that a little bit, just to make sure that I’ve understood it. So the first thing to say is, so it’s not cross posting. So if I write something on WordPress, in effect you are just showing the same thing in two different places. You’re showing it on the WordPress blog, for want of a better word. But you’re also showing that on Mastodon, and it’s the same thing. It’s the same entity. So it’s not a cross post, it’s just a post. So first thing, have I got that right?
\n\n\n\n[00:33:08] Matthias Pfefferle: Technically spoken, in the end it’s kind of a copy because that’s how ActivityPub works. The ActivityPub server, the Mastodon server kind of has a cache of your profile, and has a copy of your post. But in the end, it’s more like you described it. It’s not that you have to use something on the other platform to publish it.
\n\n\n\nBut you can compare that with Mastodon. If you are on Mastodon and if you follow someone else, you see his posts in your stream. And you can see the blog posts, your homepage of WordPress, kind of like the stream you have on Mastodon. And others can subscribe to that kind of stream, and then it will be part of their Mastodon timeline. And every time you publish a post, it will be directly federated to that timeline.
\n\n\n\nAnd the thing with cross posting is that, if you post something through a Twitter profile, the whole communication on Twitter will only live on Twitter. To check what others think of your post, or what their ideas to your post are, you have to visit Twitter. The difference between that and Mastodon is that also the interaction on Mastodon or any other platform will federate.
\n\n\n\nSo that means that in the end, comments and boosts and likes will also be part of your WordPress post. So if someone on Mastodon comments your blog article, then it will also show up in the comment section of your blog.
\n\n\n\n[00:34:53] Nathan Wrigley: That really is an amazing, transformational thing, isn’t it? So again, let me be very clear. I post something on my WordPress site. Let’s imagine that’s the first place I want to do things is, you know, the interface that we love and what have you.
\n\n\n\nI post it there, it gets federated. It can now be seen, whatever that complicated process is, it can now be seen on Mastodon, let’s say. But there’s a whole bunch of other services which use the ActivityPub protocol, which we haven’t even gotten into. But there’s whole other social networks, in inverted commas, that are built on top of it, which interoperate.
\n\n\n\nThere’s one called Pixelfed, which is primarily for images but let’s not get into that. So it’s visible on Mastodon, but then if people comment on that, those comments come back, they get federated back to my WordPress site, and they would then be visible to me. Or would they be visible to everybody that visited my website? In other words, do they get consumed and added to the database as a comment?
\n\n\n\n[00:35:49] Matthias Pfefferle: Yeah. In the end we try to reuse every object that’s common in WordPress. So if you write a reply on Mastodon, in the end, it’s simply a comment on your WordPress blog.
\n\n\n\n[00:36:03] Nathan Wrigley: That’s really amazing. What if I update something? So let’s say, I don’t know, a week later in my WordPress post I spot a gigantic error. Spelling error or just factual error or something like that, and I update it. Does that then get re federated? In other words, if somebody were to stumble across that a week ago in their timeline, would they see the newer version or does the cache mean that you get the original version?
\n\n\n\n[00:36:28] Matthias Pfefferle: No, it federates also the updates. That was not always the case, but Mastodon supports that for quite some months, I think. They first implemented that you deleted the original post and repost a new one. But now they fully support updates. So if you update your blog post, the update will be federated. And the same with all other activities like delete, or even if you put it in trash, it will deleted first.
\n\n\n\n[00:37:00] Nathan Wrigley: So this may be a peculiar question, I don’t know. Is it possible to amend things in a different environment that’s not WordPress? Let’s say I’m browsing on the Mastodon interface. Can I edit things over there and they will get re federated back to my WordPress site? Or is this more of an, edit in WordPress, do all the things in WordPress, just make that your first home?
\n\n\n\n[00:37:22] Matthias Pfefferle: It depends to what you’re referring to. If you write a comment on Mastodon, then you can edit that. But you can’t edit, let’s assume you have a Mastodon account and you follow your blog. And you publish a blog post that will be also federated to your Mastodon account. Then you could not use your Mastodon account to edit your blog post, because technically spoken, it’s a different user.
\n\n\n\n[00:37:48] Nathan Wrigley: Okay. Can I bring a pre existing Mastodon user into the ActivityPub protocol for WordPress? In other words, can I use an account that I’ve already got and combine it, and then decide to, you know, go forward with WordPress? Or do I, in the process of setting up the plugin, am I creating a new account at that moment?
\n\n\n\n[00:38:11] Matthias Pfefferle: The first thing you mentioned would be cross posting. So if you register on Mastodon, you will get a Mastodon handle. That means something like mastodon.social/@nathan, something like that. And that’s currently not really portable. At least not that you use the same kind of handle on a different platform.
\n\n\n\nThere are mechanisms where you can kind of move your accounts to a different server. Then all your followers will be pointed to the new server. But technically you have a new handle and using a new server.
\n\n\n\nThat’s currently not possible with the WordPress plugin, because in the end we are not yet a fully comparable social network. So it’s still focusing on the publishing stuff. And you can’t follow others using your WordPress blog. There is no social media stream in the backend, you can consume others posts. So it does not make sense to move your accounts, at least yet.
\n\n\n\nIn the end it’s kind of, with installing the plugin, you will receive new handles. It’s not really a new account, but you have a new handle and others have to follow that new handle to subscribe to your blog posts.
\n\n\n\n[00:39:38] Nathan Wrigley: So if you’ve got a large following that you’ve worked hard to gain on Mastodon, then there’s definitely some thought to be put into this, and the way that you implement it and so on.
\n\n\n\n[00:39:48] Matthias Pfefferle: It’s totally fine to maybe use both, kind of to start with. Still cross post to your carefully crafted Mastodon account with hundreds of thousands of followers. And to start with the new identifier besides of that. Or maybe kind of what I’m currently trying to use is that I boost my blog posts. So that’s kind of the easiest way to gain a bit more traction to my blog posts.
\n\n\n\n[00:40:18] Nathan Wrigley: Got it. Yeah, thank you. I remember over the last, maybe year or so, not to put too fine a point on it. There was a large migration of people over to Mastodon when Elon Musk took on the ownership of Twitter. I think some people had various different concerns about how Twitter would work as a platform.
\n\n\n\nAnd it became a really hot topic in the mainstream press actually, over here on the BBC and various news channels, people were talking about Mastodon. And to me it was great because it was something, you know, it was kind of, oh, I was into that before it was cool, kind of thing.
\n\n\n\nBut then it seemed to die off. I don’t know if you’ve got any intuition on this. But just in the last month or two, especially in the WordPress world, it’s really gained a whole new life again because of WordPress.com. And so I wonder if you could tell me what’s happening over at WordPress.com and, trying to answer it at the same time, whether you’ve got any intuitions as to whether it has been a bit of a trough over the last few months? And, you know, whether or not Mastodon is still maintaining the interest that it once did.
\n\n\n\n[00:41:23] Matthias Pfefferle: I think the movement you mentioned was already the third. So it’s kind of a wave. It’s not a constant movement. There were a lot of different things in the last few months or years that caused a bigger movement. Between these movements, it gets stagnated.
\n\n\n\nJust recently there was another big movement when Reddit decided to monetise their API. And there was also a big movement, not to Mastodon, but to the platforms that are called Lemmy or kbin. That’s kind of the Reddit of the Fediverse.
\n\n\n\nIt’s not only that it’s only about Twitter and Mastodon and maybe Facebook. But it’s kind of a broader thing. It’s not that it’s that loud, as in the early Musk Twitter days, but I think it’s a constant movement of the time. And what I really like about the WordPress plugin, in the end, is that we discussed the ownership of data in social networks.
\n\n\n\nMastodon kind of has the same issues. There were a lot of, in the early days with the big buzz on decentralised networks. There were a lot of admins hosting their own little Mastodon instances. And over the time they had issues with money and payment, and shut down their instances.
\n\n\n\nSo in the end, also with a decentralised social network, you have to choose carefully where you want to host, or where you want to create your account. Because there’s no guarantee that this is even better as in closed networks. There are better mechanisms to move your account. But in the end you’re also depending on the work of others, and that they will keep on hosting the platform.
\n\n\n\nWith WordPress it’s kind of different because you can host your WordPress instance by your own. And even if the hosting provider decides to shut down the hosting, it’s very easy to export or to download your whole WordPress instance and upload it to another hoster.
\n\n\n\nIn the end, if the domain does not change, it doesn’t matter where you host your WordPress instance. And that’s kind of the game changer in my mind. You’re no longer dependent of other’s service in the end.
\n\n\n\n[00:43:57] Nathan Wrigley: The ability to migrate is fairly trivial. You know, you can really just move to another instance. My understanding is that, let’s say for example, that the server that I run, I decide to shut it down. Hopefully I would have the decency, for want of a better word, to inform the people who are on my server with plenty of time, so that they could go through this process.
\n\n\n\nBut I guess that wouldn’t necessarily always be the case. And probably some people have been stung. But it is possible to go into your account, you can export it, and then go to another server and kind of upload it there. There are some caveats, maybe I’m wrong about this. But my understanding is it will bring your followers with you, but for obvious reasons it won’t bring the posts and the replies that were on that previous instance as well. Is that right?
\n\n\n\n[00:44:39] Matthias Pfefferle: Yes. And it’s only working properly if you have only Mastodon followers. This is simply a Mastodon thing. It’s not part of the ActivityPub protocol by definition. So this whole moving profiles to different servers is realised really differently on different kind of protocols. So if you can avoid moving your profile.
\n\n\n\n[00:45:06] Nathan Wrigley: But there is the option there, right? It is at least something, which is nice. It’s interoperable and you can take your social graph elsewhere, if you like.
\n\n\n\nSo .com, WordPress.com probably, I don’t know maybe a month ago, maybe less, I can’t actually remember, decided that they were going to allow this on all of the WordPress.com websites. Is this the plugin that you have created? Is it that, that they’ve implemented? And if so, what has the interest been? Have many people taken WordPress.com up on this, and has it been a smooth experience?
\n\n\n\n[00:45:39] Matthias Pfefferle: Okay, starting with the plugin. Under the hood it’s the same plugin, but it’s a bit modified to work more smoothly together with the WordPress.com experience. I started the free installable plugin to fit my needs. So a lot of the settings are really geeky, and there are a lot of settings.
\n\n\n\nSo we stripped that down to better match with the product WordPress.com. But in the end, it’s technically the same in the background. It’s from the press it was impressive. I had the month of my life. It was stressy but it was the best time ever.
\n\n\n\nThe adoption is rising steadily. We have not done a lot by now to on board our users properly, and to have maybe kind of a special landing page to directly start. I want to have a federated WordPress. So with all of that, it’s a really good adoption. And if you think about that, we only had one blog post for now.
\n\n\n\nWe are fine with that. And we’re working to make it even easier and even better, and have kind of a more social network like experience in the end. But for now, it’s a nice thing because you could use it without changing your publishing behavior, or your commenting behavior. It’s simply activated, and if someone wants to use it, perfect. If not, also fine.
\n\n\n\n[00:47:17] Nathan Wrigley: Right. So it’s a fairly stripped down implementation, with less of the geekiness attached. But it worked, and the last time I looked was probably last Friday. So we’re recording this on a Thursday, so that was six days ago. And thousands, plural thousands of people had taken the opportunity to check that box and implement it.
\n\n\n\nSo I don’t know what’s happened in the last week, but presumably it’s gone up from there. And as you say, if you haven’t gone to any great lengths to promote it, just one blog post and, you know, nothing shouting at you in the UI to tell you you can do this. That’s really amazing. That must give you a, well like you said, it’s been one of the most amazing months of your life. That’s great.
\n\n\n\n[00:47:55] Matthias Pfefferle: And there’s a lot of potential.
\n\n\n\n[00:47:57] Nathan Wrigley: And I know that obviously, the whole position that you’ve been given at Automattic must give you confidence that WordPress as a whole, the .org side, as well as the .com side. There is real interest in this working with websites hosted with WordPress. This is not a flash in the pan. The fact that you’ve been taken on full time to work on this one plugin, I guess illustrates the fact that they are hoping that this is going to be the future of social networking.
\n\n\n\n[00:48:24] Matthias Pfefferle: I hope so too, yeah. But Automattic was a game changer in the end. So now that I can work full time on the plugin, it changed a lot. But simply with Automattic announcing that they would take over the plugin, and me as a developer, the press coverage was insane.
\n\n\n\nAnd in the end nothing changed really, at least from the technical perspective. So I think having Automattic, not only as a backer of the development, but also kind of a evangelist in that topic, is really game changing.
\n\n\n\n[00:49:02] Nathan Wrigley: Well let’s hope that in the future, there’ll be lots on the roadmap, lots of interesting new initiatives. Matthias, if somebody wants to reach out to you, I normally say, do you have a Twitter handle or something like that? I’m going to say something different. Do you have a Fediverse handle that you’d like to share? I mean it might be just as simple as your blog. Let us know where people can find you.
\n\n\n\n[00:49:22] Matthias Pfefferle: Yeah. My blog is German so maybe that’s not the perfect place to follow me. I’m on one of the biggest Mastodon instance, mastodon.social/@pfefferle, my last name.
\n\n\n\n[00:49:36] Nathan Wrigley: I will write everything in the show notes, but the sake of people who don’t read the show notes and just wish to have it spelled out for them, that would be mastodon.social/@ P F E F F E R L E. That will now be in the transcription as well.
\n\n\n\nSo yeah, Matthias, thank you so much for sharing all of your insights about the Fediverse, Mastodon, ActivityPub. And good luck, I hope that the future is bright.
\n\n\n\n[00:50:01] Matthias Pfefferle: Thanks a lot, and thanks for having me.
\nSo on the podcast today, we have Matthias Pfefferle.
\n\n\n\nMatthias started using WordPress in its early stages when it was still known as b2. He became passionate about blogging and the web 2.0 era. Over time he dedicated himself to making blogging relevant and developed various tools to compete with social networks, building communities professionally and working for a European hoster. Matthias ultimately joined Automattic to focus on WordPress and the ActivityPub plugin full-time.
\n\n\n\nWe start off talking about the importance of owning your own content, and how it grants us control over what gets published and when it gets deleted or amended. Matthias introduces us to Mastodon, a social network that operates on a non-algorithmic, chronological feed. This means that the content is displayed in the order it was created, breaking free from possibly addictive patterns we see in other platforms.
\n\n\n\nWe learn about the Fediverse, where users can set up their own servers and customise their own rules. Matthias explains how servers communicate with each other through following and federating, creating a truly decentralised network. He shares insights into how relays can be used to generate traffic and activity on new Mastodon servers should you find your feet a little quiet at the start?
\n\n\n\nThere’s definitely some new workflows to learn using the Fediverse and Matthias highlights the differences between Twitter and the Fediverse, with the latter starting off quiet and gradually growing as users find and interact with others.
\n\n\n\nHe introduces us to the ActivityPub plugin for WordPress, which allows users to publish their blogs on Mastodon, and federate the content to different servers. We get an explanation of how it works, what it does, and where it strays from the way you’re used to interacting with a proprietary platform.
\n\n\n\nWe discussed the various waves of migration to Mastodon and the factors that triggered them, including Reddit’s decision to monetize their API. Matthias sheds light on the challenges faced by decentralised networks, and how wordpress.com has implemented his ActivityPub plugin, albeit in a modified form, making it easier for users to migrate their accounts. The adoption of the plugin has been steadily rising, and Matthias expresses his confidence in the plugin’s potential, citing the press coverage and impact of Automattic’s takeover.
\n\n\n\nHe also provides insights on how interactions on Mastodon federate, explaining how likes, comments, boosts, updates or deletions to blog posts are reflected across platforms.
\n\n\n\nTowards the end Matthias shares his thoughts on the future of federated social networks and the potential support from existing platforms like Meta. He emphasises the profound benefits of using protocols like ActivityPub, allowing users to own their own data and have more control over their content, unlike closed platforms that can delete accounts and cause data loss.
\n\n\n\nIf you want to learn more about the Fediverse, Mastodon, ActivityPub, or just want to know how to make WordPress a first-class citizen in social networks, this podcast is for you.
\n\n\n\nIf you’re reading this, you’re likely not just any marketer. You’re the kind who’s always got a finger on the pulse of what’s going on — the latest tools, the newest lead generation best practices, and the most memorable campaigns of the year.
\n\nAccording to a survey from May 2023, approximately 20.6% of Chief Marketing Officers (CMOs) in the U.S. cited expanding into new markets, segments, or geographies as their top challenge for the next 12 months. Often, the biggest obstacle to making these important moves is having the right tools on hand.
\n\nSo, if you’re on the hunt for marketing apps that can elevate your enterprise marketing strategy from “meh” to “mind‑blowing”, you’re in the right place. We’re diving deep into the world of enterprise marketing tools that are poised to supercharge your efforts in 2023.
\n\n\n\n\n\nBefore we jump into our list, let’s get on the same page about what we mean by “enterprise marketing tools”. These are enterprise marketing software solutions designed to handle the complex, multifaceted needs of large organizations.
\n\n\nThey go beyond the basics, offering features like advanced analytics, automation, and integration capabilities that can scale with your business.
\n\n\n\n\n\n\nWhen you’re running a large WordPress site or ecommerce business, you can’t afford to mess around with tools that are just “good enough”.
\n\n\nYou need robust, reliable solutions that can handle the heavy lifting, so you can focus on what you do best, like creating amazing marketing campaigns that convert.
\n\nBut even small businesses can use and benefit from these tools. Many offer scalable solutions that can grow with you, so there’s something here for everyone.
\n\nBefore you commit to a tool, let’s talk about what you should be looking for. After all, not all marketing tools offer the same features, flexibility, or ease of use. And what works for one business might not be the best for another.
\n\n\nYou don’t want a tool that requires a Ph.D. to operate. The easier a tool is to use, the quicker your team can get up to speed and make the most out of it.
\n\n\nYour business isn’t going to stay the same size forever. So, make sure the tools you choose can grow with you. Scalability is a must, especially for enterprises.
\n\n\nWith all the technology, your firm likely utilizes, you need to have tools that play well with others. Look for solutions that can easily integrate with your existing tech stack. This will make your life a lot easier in the long run.
\n\n\nData is king, so look for tools that offer robust analytics features. This will help you measure the success of your campaigns and make data‑driven decisions.
\n\n\nEvery business is unique, and your tools should be able to accommodate that fact. Customization features can help you tailor the tool to meet your specific needs.
\n\nNow, let’s move on to the best part — the top ten enterprise marketing software tools that can help you ace your marketing game in 2023.
\n\n\n\n\n\n\nAkismet is a must for enterprise-level marketers as it’s your ultimate line of defense against spam. Developed by the same team behind WordPress.com, Akismet uses cutting-edge AI technology to filter out comment, form, and text spam with an unparalleled 99.99% accuracy.
\n\n\nIt’s truly a proven solution that has been trusted by millions of websites globally and can be used by businesses of all sizes.
\n\nAkismet was designed with user‑friendliness in mind. Its seamless integration with WordPress makes it incredibly easy to set up and manage. There’s no need for coding experience or complicated server management — it just works.
\n\nAkismet offers a range of pricing options tailored to different needs:
\n\n\nOracle Eloqua serves as a robust enterprise marketing automation software, specializing in personalized B2B marketing solutions. As a key component of the Oracle Marketing suite, the platform provides an all-encompassing, unified marketing solution that allows cross-channel programs to flourish.
\n\n\nIt focuses on enhancing lead generation, fine‑tuning communications with customers and prospects, and automating marketing tasks through insights derived from real‑time data.
\n\nOracle Eloqua is engineered to empower marketers, allowing them to tap into their creativity and intuition to orchestrate compelling B2B campaigns. Despite its sophisticated feature set, the platform maintains a user‑friendly interface.
\n\nOracle Eloqua does not publicly disclose its pricing structure. However, it’s generally customized to meet the specific needs of an enterprise. Reviews indicate that the basic package for Oracle Marketing Cloud starts at a range of $2,000 to $4,000 per month, with additional costs incurred for add‑ons and higher‑tier plans.
\n\n\n\n\n\n\nMonday.com aims to be the hub for all your work activities, processes, tools, and files. The platform is ideal for a modern work environment, catering to various sectors including creative and design, software development, marketing, and project management.
\n\nIt focuses on streamlining work for optimal productivity and fostering organization‑wide collaboration.
\n\nMonday.com is designed for user‑friendliness, making installation, setup, and restoration a breeze. There’s no need for coding skills or intricate server management. The platform is built to be intuitive and straightforward.
\n\nMonday.com offers various pricing options to cater to different organizational needs. Here’s a breakdown:
\n\n\nMediaMath is a specialized platform for programmatic advertising that allows brands and agencies to manage their marketing campaigns with agility. The platform really excels in delivering effective and efficient omnichannel campaigns, featuring solutions like a Demand Side Platform (DSP) and Connected TV (CTV) advertising.
\n\n\nMediaMath also makes it easier to establish a one‑to‑one relationship with customers across all devices through its audience targeting capabilities.
\n\n\nMediaMath is user‑friendly, offering an intuitive experience for running advertising campaigns across multiple channels. There’s no need for a complicated setup process.
\n\nUnfortunately, MediaMath does not publicly disclose its pricing details. For more specific pricing information, it’s necessary to contact their sales team.
\n\n\n\n\n\n\nKlaviyo is more than just an email marketing tool. It’s a comprehensive platform designed to deliver hyper-personalized experiences through deeper insights. Integrated seamlessly with ecommerce platforms, Klaviyo allows businesses to send targeted emails, SMS, and even push notifications.
\n\n\nThe platform aims to consolidate your tech stack, enhance efficiency, and elevate customer lifetime value.
\n\n\nKlaviyo is designed with user‑friendliness in mind, offering a streamlined customer experience. Whether it’s capturing leads or executing campaigns, navigating the platform is intuitive and straightforward.
\n\nKlaviyo offers both free and premium plans.
\n\n\n\nMailchimp’s expanded its focus beyond email marketing campaigns and is now a comprehensive platform designed to streamline your marketing automation efforts. From A/B testing and customer journey building to content creation, Mailchimp offers a full suite of features that can help you automate campaigns and make data‑driven decisions.
\n\n\nMailchimp is designed to be user‑friendly. Its intuitive interface makes setting up campaigns, managing your audience, and analyzing results a breeze. Plus, they offer 24/7 service and support, so you’re never left in the dark.
\n\nMailchimp offers a free plan with limited features plus various premium plans:
\n\n\nSimpli.fi is a leading advertising success platform that focuses on maximizing relevance and results. It offers a range of media buying and workflow solutions designed to capture your audience and power your best work.
\n\n\nFrom Demand‑Side Platform (DSP) capabilities to Connected TV (CTV) advertising, Simpli.fi aims to deliver highly‑competitive pricing and audience‑targeted solutions.
\n\nSimpli.fi is designed to be user‑friendly, offering an all‑in‑one platform that streamlines every step in your workflow. Whether you’re planning a campaign or analyzing its performance, Simpli.fi makes the process seamless.
\n\nAs we already mentioned, Simpli.fi does not publicly disclose its pricing. For detailed pricing information, you’ll need to get in touch with their sales team.
\n\n\n\n\n\nMarketo Engage, a component of Adobe’s expansive suite, is an enterprise marketing automation tool catering to both B2B and B2C sectors. It’s engineered to bridge the gap between sales and marketing teams.
\n\n\n\nThe platform is of the all-in-one variety, offering everything from lead management and email marketing to multitouch attribution.
\n\n\nMarketo Engage is user‑friendly but comes with a bit of a learning curve due to its extensive feature set. However, once you get the hang of it, it becomes an invaluable enterprise marketing automation solution.
\n\nPricing for Marketo Engage is not publicly disclosed. However, it’s worth noting that the platform offers different plans that scale based on the number of users and the complexity of features. For a more detailed pricing breakdown, you’ll need to contact their sales team directly.
\n\n\n\n\n\n\nInvoca serves as a powerhouse in conversation intelligence, harnessing the prowess of AI to unearth fresh data that can be a game-changer for your business. The platform is designed to help you snag more customers without breaking the bank, offering keen insights into your phone-based customer interactions.
\n\n\nWhether you’re on a mission to ramp up conversions, elevate your agents’ performance, or convert more callers into loyal customers, Invoca is your one‑stop‑shop.
\n\nWhether you’re in the planning phase of a campaign or knee‑deep in performance analytics, Invoca aims to make your life easier. However, getting started will require a time commitment.
\n\nWhen it comes to pricing, Invoca keeps its cards close to its chest. For specifics, you’ll need to have a chat with their sales team.
\n\n\n\n\n\n\n\nStackAdapt is a titan in the realm of programmatic advertising, engineered to help you craft campaigns that catch the eye and engage the mind. The platform is built on planning, execution, and analysis.
\n\n\nWhether you’re an agency hungry for growth or a brand keen on making meaningful connections with your audience, StackAdapt has a toolbox chock‑full of solutions tailored just for you.
\n\nStackAdapt is generally easy to use, but does have a somewhat confusing dashboard. Once you’re familiar with it, however, the workflow becomes intuitive.
\n\nStackAdapt doesn’t offer its pricing upfront, so you’ll need to reach out to their sales team to get a quote for your situation.
\n\nWhen looking for the right enterprise marketing automation tools, there are several factors to consider. Let’s take a look at a few.
\n\nYou have to know what you’re aiming for. What are your specific goals and key performance indicators (KPIs) for your digital marketing programs? Whether it’s boosting lead generation, improving customer engagement, or enhancing ROI, having clear objectives will help you narrow down your options.
\n\n\n\nUnderstanding your target audience is another critical factor. Are you targeting B2B or B2C? What are their pain points, and how do they interact with your brand? Knowing your audience will help you select tools that can effectively engage and convert them.
\n\n\nLet’s be real — budget is always a factor. You need to know how much you can afford to spend on these tools without breaking the bank. Make sure to balance quality and cost‑effectiveness.
\n\n\n\n\n\n\nThings don’t always go as planned. When you hit a snag, you’ll want a responsive customer support team to help you out. Check reviews or ask for references to gauge the quality of a tool’s customer support.
\n\n\nA tool could have all the bells and whistles, but if it’s a nightmare to use, then what’s the point? A good user interface and experience can make all the difference. Look for tools that are intuitive and don’t have a steep learning curve.
\n\nMany tools offer free trials or demos. Take advantage of these to get a feel for the tool’s interface and capabilities. It’s like test‑driving a car. You’ll get to know if it’s the right fit before making a commitment.
\n\nLast but definitely not least, consider the tool’s security features. This is especially important if you’re handling sensitive customer data. Make sure the tool is compliant with regulations like GDPR or HIPAA, depending on your industry.
\n\nThe marketing tools you select will largely depend on your specific business needs, goals, and the scale at which you operate. Start by identifying the gaps in your current marketing strategy and look for tools that can fill them. Also, consider factors like scalability, integration capabilities, and user experience.
\n\nAbsolutely! Many marketing tools offer customizable plans and features. For instance, Akismet offers enterprise‑level plans that can be tailored to meet your specific needs.
\n\n\n\n\n\nLook no further than Akismet for enterprise-level spam protection. It’s a leading tool in the spam protection arena and offers robust features to keep your site free from unwanted spam.
\n\n\nAkismet offers a range of benefits for enterprise companies. It protects your website from spam and saves you time by automatically filtering out malicious content. This allows you to focus on what really matters — e.g. growing your business. Akismet’s enterprise plans also offer dedicated support to meet the unique needs of large‑scale operations.
\n\nAkismet is trusted by a wide range of companies, from small businesses to large enterprises. It’s a versatile tool that can adapt to the unique needs of your business, making it a valuable addition to your marketing toolbox.
\n\n\n\n\n\nAkismet is used by over 100 million sites. And it’s not just small businesses that trust Akismet. Big names like Microsoft, ConvertKit, and Bluehost also rely on Akismet for their spam protection needs.
\n\nAkismet isn’t just a spam protection tool. It’s a must for enterprises looking to increase their lead and contact form conversion rates. By automating spam filtering, Akismet lets you focus on what truly matters — engaging with genuine leads and customers.
\n\nSo, if you’re in the market for a tool that offers robust spam protection while also giving your conversion rates a healthy boost, Akismet is the one for you.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Nov 2023 14:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Rob Pugh\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"HeroPress: Nine Years Of HeroPress, A Retrospective\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=6003\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:152:\"https://heropress.com/essays/nine-years-of-heropress-a-retrospective/#utm_source=rss&utm_medium=rss&utm_campaign=nine-years-of-heropress-a-retrospective\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:232537:\"This week is the anniversary of when I woke up one morning to an email from the owner of the company I worked for (Dave Rosen, XWP) saying he was taking me off the XWP team because he wanted me to do something special for WordPress. I asked him what, and he said “That’s your journey to discover.”
\n\n\n\nAnd what a journey it’s been!
\n\n\n\nI never would have imagined that this kid who grew up in a house without electricity would be part of a project that enabled him to travel through 9 countries, building friendships all over the world and in dozens of cultures. Friendships that have opened my eyes to new ideas, communication models, foods, and so much more. All while elevating the invaluable stories of others and bringing inspiration to those who need it no matter where they are.
\n\n\n\n\n\n\n\n\nHeroPress for me is always a place of empathy and dignity. I return to it often as spending time on it is always rewarding, filled with stories of us- the people of WordPress.
\nAditya Kane
Look with me at what we’ve done so far and what the next phase might have in store.
\n\n\n\nFor many years, HeroPress was a site of community-contributed essays, and HeroPress.com continues to be that today. Since Rarst’s first essay we’ve published just over 260 essays in 28 languages. Broken down, that’s 125 essays by men, 128 by women, and 3 by non-binary folk, with contributors representing 59 different countries.
\n\n\n\n\n\n\n#map_wrapper {\n height: 600px;\n}\n\n#map_canvas {\n width: 100%;\n height: 100%;\n}\n\n.info_content .contributor {\n min-width: 300px;\n clear: left;\n}\n.info_content img {\n margin: 6px 6px 6px 0;\n float: left;\n}\n.info_content h4 {\n margin: 0;\n padding: 0;\n clear: none;\n}\n.info_content h5 {\n text-transform: none;\n letter-spacing: 0;\n margin: 0 0 4px 0;\n clear: none;\n}\n.info_content p {\n margin: 0;\n clear: none;\n}\n \nThe Fuel Of Everything That’s Great In The World – Rotițele care fac lumea să se miște
\' +\n\'New life thanks to WordPress – Una nueva vida gracias a WordPress
\' +\n\'About how WordPress saved my life. – Sobre como WordPress me salvo la vida
\' +\n\'Exploring the Essence of Community – Explorando la esencia de la comunidad
\' +\n\'Becoming A Better Me with Core Contribution – কোর কন্ট্রিবিউশন এবং জীবনের নতুন অধ্যায়
\' +\n\'Finding a second chance in life through WordPress – വേർഡ്പ്രസ്സിലൂടെ ജീവിതവിജയം
\' +\n\'The pleasure of being a part of a community – Щастя бути частиною спільноти
\' +\n\'Connection Makes Credibility, Credibility Makes Opportunity – 連結產生信賴,信賴創造機會
\' +\n\'There is No Shortcut to Success – सफलता का कोई शॉर्टकट नहीं है
\' +\n\'Living Well and Enabling Success For Others Through WordPress
\' +\n\'Tales Of A Serial Contributor – Histórias de um colaborador em série
\' +\n\'Being a freelancer can be the most stable thing in Taco land
\' +\n\'Never give up on your dreams – Moet nooit jou drome laat vaar nie
\' +\n\'WordPress – The Source Of My Satisfaction And Joy – વર્ડપ્રેસ – સંતોષ અને આનંદ નો સાધન
\' +\n\'Life Stacks Up – From A Small Town Boy To A Geek Entrepreneur
\' +\n\'My Journey from being a Dyslexic kid to becoming A Co-organiser For WordCamp Mumbai
\' +\n\'A Journey toward Freedom with WordPress – वर्डप्रेससंगै स्वतन्त्रता तर्फको यात्रामा
\' +\n\'A Life Changing Journey With WordPress – जीवन में मिले रंग वर्डप्रेस के संग
\' +\n\'How To Become A Freelancer – A Few Things I Learned Before I Gave Up
\' +\n\'How the WordPress community contributes to human development
\' +\n\'How the WordPress community contributes to human development
\' +\n\'Second Chances: How A Trip Back Into The WordPress Community Saved My Life
\' +\n\'How the WordPress community contributes to human development
\' +\n\'Building A WordPress Business In Iran – ساختن یک زندگی وردپرسی در ایران
\' +\n\'How The WordPress Community Helped Me Face My Fears And Do It Anyway
\' +\n\'Is WordPress Good for Indian Women? – ભારતીય મહિલાઓ માટે વર્ડપ્રેસ સારું છે?
\' +\n\'My “Hero’s Journey” Through the Dark Underworld of WordPress Hosting
\' +\n\'Building Stability With WordPress – WordPress এবং স্থিতিশীলতা, বাংলা তে পড়ুন
\' +\n\'Sometimes bad things that happen to you are good things in disguise
\' +\n\'The Year I Got Cancer Was The Year My WordPress Business Took Off
\' +\n\'My journey to WordPress taught me that my talents are best used elsewhere.
\' +\n\'16 Little Things That Grew Into Big Things (My Life in a Bunch of Words)
\' +\n\'How I found myself in WordPress – Как я нашел себя в WordPress
\' +\n\'How I tried, applied, got involved. Realizing one of my childhood dreams.
\' +\n\'How WordPress enabled me to take care of my baby without compromising on my career goals
\' +\n\'The London Eye is a giant Ferris wheel situated on the banks of the River Thames. The entire structure is 135 metres (443 ft) tall and the wheel has a diameter of 120 metres (394 ft).
\' + \'The Palace of Westminster is the meeting place of the House of Commons and the House of Lords, the two houses of the Parliament of the United Kingdom. Commonly known as the Houses of Parliament after its tenants.
\' +\n \'\n\n\n\n\nHeroPress has bestowed upon us the most wondrous knowledge of WordPress people from everywhere and anywhere. It’s an absolute treat to read all the stories, perhaps most especially from those less known than others.
\nBarbara Saul
Our Family Of Contributors
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nReading someone’s essay motivates me to venture beyond my comfort zone.
\nTremi Dkhar
2020 saw the transition from I to we. The nudge was there to act on some ideas we’d had over the years. Cate was transitioning into the work force, Liam and Tara were ready to step away from Hallway Chats, and we had to pick a direction. Do we keep things separate and find a connecting point, or do we pull them all into HeroPress itself?
\n\n\n\nAll things feeling fairly equal, we picked Option A: big, but scalable.
\n\n\n\nWe created a network of individual entities that could be nurtured, shelved, sold, or closed down at any point. This resulted in a collection of sites — HeroPress.com, WPPodcasts.com, PressItWP.com, WPPhotos.Info, HallwayChats.com, and WP-Wallpaper.com — being held together through the HeroPress Network hub.
\n\n\n\nHowever, after 3 years of giving this a try, we’re not sure if this is really the future for HeroPress. The Network is fine, but limiting. It’s time to reevaluate where we want to channel our energy as we look ahead to the next phase of HeroPress.
\n\n\n\n\n\n\n\n\nHeroPress has…
\n\n\n\nEnabled me to see the stories that create WordPress. It’s let me discover the people who genuinely power this project, not just the code and pixels. Because open source is people source.
\nTammie Lister
\n\n\n\n\nWhenever I’m down, I find visiting HeroPress and being connected to the many and real ways that WordPress’ stone in the pond of the world leaves ripples, I’m inspired and excited.
\nMatt Mullenweg
Nine years is a long time for a project like this to flourish, and flourish it has. As with any living thing it needs to be tended to and some times that means cutting a little back to make room for new growth.
\n\n\n\nA plan is underway to trim some things out and merge the rest into HeroPress.com. We’re looking at some rebranding and a new purpose statement. The goal has always been to elevate others, but have we really stated that as clearly as we could?
\n\n\n\nWhat ever the future holds, HeroPress will be here, at least for now. And we hope you’ll be alongside us as we head for 10 years of inspiring one another.
\n\n\n\n\n\n\n\n\nThe stories from HeroPress have motivated me and encouraged me to come out of my shell and chase my dreams. Several years back when I was really struggling with my career, reading inspiring stories from people all over the world finding success through WordPress rekindled my hopes and dreams – literally leading me to where I am today. I am eternally thankful for HeroPress!
\nHari Shanker
Many thanks to Tremi, Hari, Matt, Barbara, and Tammie for their words about HeroPress.
\n\n\n\nThe banner at the top is a CC0 licensed photo by Javier Casares from the WordPress Photo Directory.
\nThe post Nine Years Of HeroPress, A Retrospective appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Nov 2023 08:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Topher DeRosia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"Matt: New Yorker on Coding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=105621\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://ma.tt/2023/11/new-yorker-on-coding/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:318:\"I loved this essay from James Somers on coding in the age of AI, A Coder Considers the Waning Days of the Craft. Hat tip: Majd Taby.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Nov 2023 04:37:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: WordCamp Asia Extends Sponsor Application Deadline\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151267\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wptavern.com/wordcamp-asia-extends-sponsor-application-deadline\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1763:\"The WordCamp Asia organizing team has extended its call for sponsors until Thursday, November 30, 2023.
\n\n\n\nIn an update on the official website, organizers explained that they received feedback from multiple potential sponsors regarding why they had been unable to apply before the original deadline.
\n\n\n\nSome of the reasons included the following:
\n\n\n\nWordCamp Asia’s organizers decided to extend the deadline to allow potential sponsors the opportunity to apply.
\n\n\n\nAs one of the three flagship WordCamps, WordCamp Asia is one of the largest gatherings organized by the WordPress community. Its first event in 2023 attracted 1,299 attendees, and it’s expected to exceed that number for 2024.
\n\n\n\nA full list of sponsorship options is available from the sponsorship packages page, many of which are already sold out. Potential sponsors can apply for a sponsorship package using the form at the bottom of that page.
\n\n\n\nSponsors needing more information about travel visas can review the updated visa information page, or reach out directly to the team at asia-sponsors@wordcamp.org with any additional questions.
\n\n\n\nWordCamp Asia 2024 takes place from March 7-9, 2024 at the Taipei International Convention Center in Taipei, Taiwan.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 22:53:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Jonathan Bossenger\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: Brainstorm Force Invests in LatePoint Bookings and Appointment Scheduling Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151318\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"https://wptavern.com/brainstorm-force-invests-in-latepoint-bookings-and-appointment-scheduling-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3240:\"Brainstorm Force, makers of the popular Astra theme, has invested in LatePoint, a commercial booking and appointment scheduling plugin for WordPress. LatePoint is used on 21,000 websites to enable bookings for small businesses, such as salons, therapists, doctors, spas, and fitness studios. It also supports a growing library of add-ons for further customizing the booking experience.
\n\n\n\n“This is a strategic investment, primarily made to begin integrating LatePoint into our products and offer it to our customers,” Brainstorm Force CEO Sujay Pawar said.
\n\n\n\n“Thousands of businesses build their websites with our Astra theme and Starter Templates every day. Many of these businesses could benefit if they were able to get bookings for their services from the websites they built. So, this investment allows us to offer a deeply integrated booking and appointment solution to these customers.”
\n\n\n\nZipWP, the AI WordPress website builder product the company recently launched, will be utilizing LatePoint in the websites that are generated with appointment booking and scheduling features. Brainstorm Force also plans to integrate LatePoint features into its Spectra page builder, which is based on Gutenberg and has more than 600,000 active installs. Spectra will be updated to include blocks for bookings and appointment scheduling.
\n\n\n\nThe company is integrating LatePoint across its entire product suite, including adding it to SureCart, their e-commerce plugin, to enable small businesses to accept subscription payments. Brainstorm Force will be including it with its SureTriggers automation platform to connect LatePoint to other WordPress apps, plugins, and services.
\n\n\n\n“We realized that the service commerce space within WordPress was somewhat underserved,” Pawar said.
\n\n\n\n“Platforms like Squarespace offer Acuity Scheduling and Wix provides Wix Bookings. SaaS solutions like Calendly often come with very limited features and substantially high monthly recurring costs.
\n\n\n\n“Within the WordPress ecosystem, there are a few options, such as WooCommerce Bookings, Amelia, Bookly, etc. We meticulously evaluated all of them.
\n\n\n\n“What impressed us most about LatePoint was its exceptional code quality, modern design flexibility, and robustness.”
\n\n\n\nPawar said the investment is in the six-figures but the exact amount will not be disclosed due to a confidentiality clause.
\n\n\n\n“The idea behind the investment is to initiate this partnership and possibly acquire LatePoint in the future,” Pawar said.
\n\n\n\nBrainstorm Force currently offers more than 70 products that power 7+ million websites. This new investment is aimed at capturing small business customers with a payment and booking solutions fully integrated with the company’s starter templates and other products.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 22:39:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:105:\"Do The Woo Community: Keeping Your Site Secure for the Holidays and Beyond with Rob Cairns and Dan Knauss\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78136\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://dothewoo.io/keep-wordpress-site-secure-for-the-holidays-and-beyond/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:475:\"Rob and Dan discuss the importance of website security, hosting, plugins, backups and two-factor authentication in website security during the holiday season.
\n>> The post Keeping Your Site Secure for the Holidays and Beyond with Rob Cairns and Dan Knauss appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Nov 2023 09:58:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: ElmaStudio Releases Moog: A Free Block Theme for Blogs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151291\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/elmastudio-releases-moog-a-free-block-theme-for-blogs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3554:\"Moog is one of the latest free block themes to be released on WordPress.org. It features a minimal and bold layout with a responsive, masonry style grid on the homepage. Moog is well suited to blogs or even small magazine websites, with options to radically change the style with the click of a button.
\n\n\n\n\n\n\n\n\n\n\n\nMoog’s designers went wild with style variations. The theme packages 25 distinct variations, an exceptionally large number, which quickly transform the site’s design into various moods – everything from a classic style to dark mode to bold colors anchored in different font combinations. Below is a screenshot of the “Enigmatic” style variation and the 404 template, which users can further customize with their own images.
\n\n\n\n\n\n\n\n\n\n\n\nMoog includes seven custom block patterns for creating the two-column gallery, footer, header, masonry column for posts, and patterns for about, team info, and contact pages.
\n\n\n\nUsers can add their own logos (in the header and footer), social media menu, and a newsletter signup. The demo users the MailerLite plugin for the newsletter and WP Forms for the sample contact form on the Contact page.
\n\n\n\nThe single post template is particularly elegant, with the featured image, author avatar, and content centered on the page, creating a distraction-free reading experience.
\n\n\n\n\n\n\n\n\n\n\n\nMoog was created by the team at ElmaStudio, a boutique theme shop that was among the first to create commercial block themes. ElmaStudio released its first block theme, Aino, in 2021 and four commercial block themes during 2022, including one WooCommerce theme. The company has been creating WordPress themes since 2011 and brings a wealth of experience along with meticulous, thoughtful design decisions to the new world of block themes.
\n\n\n\nCo-founder Ellen Bauer created a video with a quick overview of the new Moog theme. She demonstrates how to customize page templates and shows how to add an SVG logo that will automatically adjust with the style variations. The company is not just creating block themes but is also educating users on how to take advantage of all the customization options, as template editing is a capability that was previously out of reach for most users in the classic themes era.
\n\n\n\n \n\n\n\nCheck out the live demo on the ElmaStudio website to see the theme in action, or take it for a test drive using WordPress Playground. Moog is available for free from WordPress.org.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 23:15:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"Matt: Predictive Thermometer\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=105339\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"https://ma.tt/2023/11/predictive-thermometer/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:391:\"There’s a great review of the Combustion Predictive Thermometer in Wired today. If you do any sort of cooking or grilling regularly, this tool from my good friend Chris Young is really essential.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 19:12:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"WordPress.org blog: Introducing Twenty Twenty-Four\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16394\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://wordpress.org/news/2023/11/introducing-twenty-twenty-four/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6194:\"When it comes to designing a website, one size doesn’t fit all. We understand that every WordPress user has unique needs and goals, whether you’re an aspiring entrepreneur, a passionate photographer, a prolific writer, or a bit of them all. That’s why we are thrilled to introduce Twenty Twenty-Four, the most versatile default theme yet—bundled with WordPress 6.4 and ready to make it uniquely yours.
\n\n\n\n\n\n\n\nUnlike past default themes, Twenty Twenty-Four breaks away from the tradition of focusing on a specific topic or style. Instead, this theme has been thoughtfully crafted to cater to any type of website, regardless of its focus. The theme explores three different use cases: one designed for entrepreneurs and small businesses, another for photographers and artists, and a third tailored for writers and bloggers. Thanks to its multi-faceted nature and adaptability, Twenty Twenty-Four emerges as the perfect fit for any of your projects.
\n\n\n\nAs you dive into its templates and patterns, you will notice how the new Site Editor functionality opens up different pathways for building your site seamlessly.
\n\n\n\nWhether you’re looking to craft an About page, showcase your work, handle RSVPs, or design captivating landing pages, Twenty Twenty-Four has got you covered. Choose from an extensive collection of over 35 beautiful patterns to customize and suit your needs.
\n\n\n\nFor the first time, this theme features full-page patterns for templates like homepage, archive, search, single pages, and posts. Some are exclusively available during the template-switching and creation process, ensuring you have the right options when you need them.
\n\n\n\n\n\n\n\nMoreover, you can take advantage of a variety of patterns for page sections, such as FAQs, testimonials, or pricing, to meet your site’s most specific requirements.
\n\n\n\nWith this diverse pattern library, Twenty Twenty-Four offers a flexible canvas to quickly assemble pages without having to start from scratch—saving you time and energy in the creation process. Just let your creativity flow and explore the possibilities!
\n\n\n\n\n\n\n\nTwenty Twenty-Four ushers in a new era of block themes by bringing together the latest WordPress site editing capabilities. Discover newer design tools such as background image support in Group blocks and vertical text, providing an intuitive and efficient way to create compelling, interactive content.
\n\n\n\nFind image placeholders with predefined aspect ratio settings within patterns, allowing you to drop images that perfectly fill the space. To go one step further, make your visuals interactive by enabling lightboxes. Ideal for showcasing galleries or portfolio images, this feature allows your visitors to expand and engage with them in full-screen mode. Activate it globally for all images throughout your site or for specific ones.
\n\n\n\nFor a smoother browsing experience on your site, you can disable the “Force page reload” setting in the Query Loop block. This allows the necessary content to be loaded dynamically when switching between different pages without needing a full-page refresh.
\n\n\n\nTwenty Twenty-Four goes beyond versatility with a beautiful aesthetic inspired by contemporary design trends, giving your website a sleek and modern look. Key design elements include:
\n\n\n\nAlong with its design, Twenty Twenty-Four has been meticulously optimized for performance. This ensures that your website not only looks great but also delivers a fast and efficient user experience.
\n\n\n\n \n\n\n\nMore information can be found in the following links:
\n\n\n\nThe Twenty Twenty-Four theme was designed by Beatriz Fialho and made possible thanks to the passion and tireless work of more than 120 contributors.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 18:29:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Maggie Cabrera\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"WordPress.org blog: WP Briefing: Episode 66: Advocating Open Source Solutions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16357\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wordpress.org/news/2023/11/episode-66-advocating-open-source-solutions/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11355:\"WordPress Executive Director, Josepha Haden Chomphosy, speaks to the strategic approach to integrating open source solutions within your company and offers insight into initiating open source advocacy conversations. Tune in for a session that could redefine your company’s technological approach.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@WordPress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, we’re talking about something I used to have a lot of experience with in my career before WordPress. I worked at a marketing agency. I wasn’t a developer. I was in data and strategy sorts of things. But part of the work heading into every project was an evaluation of what software was best. There were always a variety being considered, but WordPress was frequently one of them.
\n\n\n\nNow, I don’t know if any of you have had that moment where you’re having to talk open source with a CTO or a CEO, but it can be nerve-wracking, to say the least. And it makes sense, right? Open source has a PR problem, especially when you’re speaking to leadership inside a business. And it doesn’t really matter the size, right?
\n\n\n\nYou’re advocating for something that requires a completely different mental model. It doesn’t fit into accepted concepts of what makes a business thrive or what makes a bet a sure thing. There were three, maybe four, concerns that came up every time I had this conversation. So, I’m going to share those concerns with you and a few possible counterpoints to get you started.
\n\n\n\n[00:01:48] Josepha: First and always is the concern around security. I believe that this particular mismatch is rooted in an idea that controlled equals secure, which isn’t always the case. So the talking point is this. Since open source has a transparent development process, it is often more secure than proprietary software, contrary to what you might hear.
\n\n\n\nThat transparency allows vulnerabilities to be identified by independent researchers and community members and then patched quickly because you aren’t limited by who or what you know personally.
\n\n\n\nAnd if you’re not having a conversation where you’re having to defend the security in open source and you just want to bring it up yourself, here is a conversation opener for that. Security is a top concern for all of us. Surprisingly, open source solutions often have stronger security measures due to the collaborative nature of their development. It’s a proactive approach to minimizing risks.
\n\n\n\n[00:02:43] Josepha: A second thing that frequently came up was questions around innovation and future proofing of open source products. I think this mismatch is fully rooted in the Cathedral and the Bazaar methods of advancement. So the talking point for that one is this. Embracing open source fosters innovation. We can tap into the latest technologies and stay ahead of industry trends that way. It is specifically because we have a diverse set of viewpoints that we can make sure to quickly account for future risks, along with taking advantage of future opportunities. And by our organization being more active, we can potentially get exactly the solutions we need for our clients long term.
\n\n\n\nAnd the conversation opener for this, if you are the one bringing up the topic, is I’ve been thinking about our long-term goals and how to keep our technology stack relevant. Open source not only keeps us current but also positions us as innovators in our field.
\n\n\n\n[00:03:40] Josepha: And finally, the thing that seems to make or break the decision is the concept of independence. Part of any good business decision, especially around software, is determining upfront costs to getting started, long-term effectiveness of the chosen solution, and long-term mobility should circumstances change. Open source can address these from multiple vantage points.
\n\n\n\nSo here’s a good talking point for that one. Open source liberates us from vendor lock-in. We’re not tied to a single vendor’s roadmap or pricing changes, providing us with more options that suit our needs our clients’ needs. Also, given how ubiquitous WordPress is in particular, there will always be a disaster recovery option should a senior developer leave.
\n\n\n\nAnd beyond all of that, clients can own all of the content, audience attention, and clientele that we have all worked so hard to help them earn. And again, if you’re not defending things and instead choosing to bring them up as somebody who is trying to affect change in your own organization, here is a good place to start for that.
\n\n\n\nConsidering the dynamic nature of our industry, having the freedom to choose solutions independent of a specific vendor makes sure that we are always in control of our destiny.
\n\n\n\n[00:04:59] Josepha: So, those are the three most frequent things I encountered when I was having conversations about which software to choose and what software was the best choice long term for both our organization and our client’s organizations.
\n\n\n\nIf you have been in the midst of this type of conversation and have been longing for some counterpoints, I hope this helps. But if you have been feeling in your heart of hearts that your company or organization would be better off using open source software, and of course, in my context, particularly WordPress as that software, but you’ve been worried about bringing it up, I hope this gives you the courage to get out there and be an agent of change in your organization. You can do it, and I know you can.
\n\n\n\n[00:05:44] (Music interlude)
\n\n\n\n[00:05:51] Josepha: All right, my friends, that brings us now to our small list of big things.
\n\n\n\n[00:05:57] Josepha: First on the list, big, big thing. We launched WordPress 6.4 on November 7th, about a week ago. Be sure to download and check out the latest update on this monumental release. And while you’re doing it. Be sure to check out the new default theme that came out with it. It has a lot of patterns in it. I know I’ve talked about it quite a bit over the course of the year, but it’s really beautiful, and I think that it’s worth a good, strong highlight. So WordPress 6.4, you can get it on WordPress.org/download or inside your own host, probably.
\n\n\n\n[00:06:29] Josepha: The second thing that we have is that the training team recently published several new Learn resources to support meetup organizers. So we’ve got over there some lesson plans, tutorials, online workshops. And there are also new materials that help you figure out how to accomplish your goals as a contributor to the WordPress project.
\n\n\n\n[00:06:49] Josepha: And we also have a recently published new diverse speaker training page. It provides incredible resources for new and experienced contributors to bring more diverse speaker lineups and inclusive, diverse WordPress events for official WordPress meetups and WordCamps.
\n\n\n\n[00:07:06] Josepha: And the fourth thing on our small list of big things today is that I would love to get a few voice recordings from you all, from folks who are listening to the WordPress Briefing, or folks that you know, to learn more about how WordPress has impacted you.
\n\n\n\nOne of the things that I miss the most from my days as a WordCamp organizer is that annually, I got to see people who had shown up, once at a meetup, you know, to learn what WordPress was, and then came back year after year to our WordCamp with these new goals and new successes and I got to watch their businesses change over time. And so if you have a story like that where WordPress impacted what you are doing or what people that you know have done, record something and send it to wpbriefing@WordPress.org.
\n\n\n\nSo that, my friends, is your small list of big things.
\n\n\n\n[00:08:04] Josepha: Don’t forget to follow us on your favorite podcasting app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there is a new episode. If you liked what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard, you can share those with me at wpbriefing@WordPress.org. I’m your host, Josepha Haden Chomphosy. Thanks for tuning in today for the WordPress Briefing, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:08:31] (Music outro)
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Nov 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:134:\"Gutenberg Times: Twenty-Twenty-Four, WordPress 6.4, Command Palette Tools, New block themes and documentation – Weekend Edition #273\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=26082\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:137:\"https://gutenbergtimes.com/twenty-twenty-four-wordpress-6-4-comment-palette-tools-new-block-themes-and-documentation-weekend-edition-273/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:26857:\"Howdy,
\n\n\n\nOh wow, catching up on 4 weeks of Gutenberg and WordPress news is an almost impossible task, especially with a major WordPress release happening in between. This edition includes mostly release information and developer notes. Furthermore, I am excited about the new themes that arrived at the Theme directory, plugins and documentation.
\n\n\n\nI hope you are well, and getting ready for the Holidays and the new year.
\n\n\n\nYours, 💕
Birgit
Table of Contents
\n\n\n\n\nNamed after the iconic jazz artist Shirley Horn, released on November 7, 2023, with a quick point release on November 8, 2023, to fix a bug with cURL/Request (WPTavern has the skinny for you)
\n\n\n\nThe release is the culmination of immense effort and passion from over 600 contributors across at least 56 countries, including 170 first-time contributors! Although the Font Library and two new blocks were punted to 6.5, and despite the short release circle, it absolutely features rich. Release lead, Josepha Haden Chomphosy, shared more details in the release post. WordPress 6.4 “Shirley”.
\n\n\n\nRich Tabor posted a Twitter Thread with 19 different features from 6.4. And you can also explore the version via the Microsite.
\n\n\n\n\n\n\n\nSarah Gooding reported on the release: WordPress 6.4 Introduces Twenty Twenty-Four Theme, Adds Lightbox, Block Hooks, and Improvements Across Design Tools.
\n\n\n\nGutenberg YouTube, Jamie Marsland explained WordPress 6.4 in 250 seconds.
\n\n\n\nDeveloper relevant changes that came to WordPress with its latest release can be found in the WordPress 6.4 Field Guide, compiled by Abha Thakor together with the docs release team. Here are the block editor-specific Dev Notes
\n\n\n\nJustin Tadlock was release lead for Gutenberg 16.9 and highlighted in the release post: What’s new in Gutenberg 16.9? (25 October)
\n\n\n\ntheme
attribute provided (55217).getEntityRecords()
calls now return pagination totals in the returned data (55164).Sarah Gooding also reported on the release: Gutenberg 16.9 Lets You Rename (Almost) Any Block, Adds Experimental Form and Input Blocks.
\n\n\n\nHector Prieto managed the release of Gutenberg 17.0. In his release post What’s new in Gutenberg 17.0? (9 November) , he wrote: “This release focuses on maintenance with improvements in performance and accessibility, along with a few new features.” and highlighted:
\n\n\n\n🎙️ Latest episode: Gutenberg Changelog #92 – Twenty-Twenty-Four, WordPress 6.4 and Gutenberg 16.9 and 17.0 with Jessica Lyschik as special guest, hosted by Birgit Pauli-Haack
\nLast Friday, I had the tremendous pleasure of chatting with Jessica Lyschik through all the releases, but mainly the Twenty-Twenty-Four default theme. The episode of the Gutenberg Changelog is already available online.
\n\n\n\n\n\n\n\nJessica Lyschik and Margarita (Maggie) Cabrera were the co-leads for the development of the Twenty-Twenty-Four default theme. Beatrix Fialho created the first designs. From the pops list of the import ticket I counted 83 contributors in total. That’s a massive participation from the community.
\n\n\n\nThe first feedback was overwhelmingly positive. Two quotes from X (former Twitter)
\n\n\n\nProduct Manager, Hashim Warren tweeted: “Played with the new WordPress “Twenty Twenty Four” theme for a few hours. Then quickly switched my site to use it. The first time I’m using the default WordPress theme on a project I care about. Really great work there”.
\n\n\n\nRae Morey, editor of The Repository newsletter tweeted her comments as well: “Holy crap, WordPress 6.4 and Twenty-Twenty Four are a match made in heaven! Props to everyone who contributed. Saying goodbye to my page builder. ” and then “The updated editing experience is a game-changer. Previously, I found it so confusing to know where to start when I enabled a block theme. Yesterday, I redesigned my whole site in a day with Twenty-Twenty Four. Here site is: therepository.email“.
\n\n\n\nYou can download the theme:
\n\n\n\nTopher DeRosia reviewed the theme for Winning WP: WordPress Twenty Twenty Four Default Theme Video Review – How Good Is It? and shows you how to customize the theme.
\n\n\n\nWes Theron introduced the Twenty-Twenty-Four Theme. The idea behind Twenty Twenty-Four was to make a default theme that could be used on any type of site, with any topic.
\n\n\n\nCarlo Daniele shared his view in his post: Twenty Twenty-Four: The New Minimal Multipurpose Default WordPress Theme. “More than a theme, Twenty Twenty-Four is a collection of templates and patterns that, combined, enable you to build a wide variety of websites.” he wrote.
\n\n\n\nNick Diego and Justin Tadlock invited Jessica Lyschick and Maggie Cabrera to this month’s show of Developer Hours. The recording is now online on WordPress TV. Jessica Lyschik led the presentation, which was followed by a Q&A session. The presentation included a demo/walkthrough of Twenty Twenty-Four, showing what the theme is capable of. They also shared some background information and tips and tricks on the new features and how to make it your own.
\n\n\n\nJoen Asmussen again published his bi-weekly sharing of the work from the Design team here and here.
\n\n\n\nThe new design of the WordPress.org Showcase is a wonderful tool to help agencies and freelancers to point to when discussion the use of WordPress with their clients. It’s beautiful and the broad range of types of websites.
\n\n\n\nSarah Gooding has the details in here article: WordPress Relaunches Showcase Powered by Blocks
\n\n\n\n\n\n\n\nKevin Batdorf created the Command Palette Tools plugin, with fun commands for the WordPress Command Palette. The plugin installed allows you to evaluate Math expressions or convert color on the fly and create multicolored confetti.
\n\n\n\nManesh Timilsina submitted a new block theme Taza to the official WordPress theme directory, where it is still in review. A demo is available on. taza.wpmanesh.com. “Taza comes with a two-column layout including a sticky sidebar and a content area.” Timilsina wrote.
\n\n\n\nIn his interview with CodeinWP’ Adelina Tuca he shared the genesis of an earlier Theme: Jadro, also available in the Theme repository.
\n\n\n\n\n\n\n\nEllen Bauer announced their new block theme for the WordPress repository, Moog. “Our new fun, creative free WordPress theme for blogging is released just in time for WordPress 6.4.” Ellen walks you. through it on YouTube: Fun Free New WordPress Block Theme for Bloggers
\n\n\n\nAnders Noren also released a new block theme in the WordPress Repository: Hideo. “It is a clean portfolio and blog theme with bold headings and subdued colors. It comes with 7 different theme styles and over 20 block patterns. Read his Introduction to Hideo blog post and view a demo on Noren’s website
\n\n\n\n\n\n\n\nNew resource for block theme features: The new Features chapter for the Theme handbook includes docs for patterns, block stylesheets, block styles, and block variations. The longer-term plan for the pattern’s doc is to split this into multiple sub-docs, but it was decided to get v1.0 out first than to continue waiting until it was perfect (ship early and iterate).
\n\n\n\nMike McAlister, designer and developer of the Ollie theme, reached out to Anne McCarthy to share some feedback about his recent block theme building experience, and they decided together to turn it into a hallway hangout to have it benefit the wider community and gather more insights. Anne McCarthy shared the recording and summarized the discussion in here post: Hallway Hangout: Let’s chat about the experience of building a block theme.
\n\n\n\nJustin Tadlock published a call for Discussion: How to handle custom settings screens in block themes for the theme review team to tackle the similar topic of settings screens in blocks themes. Your opinion is important. Comment on the post.
\n\n\n\nSarah Gooding reported on the new chapter of the Theme Handbook: The new block-focused Templates chapter is now in the Theme Handbook. “The new chapter on block templating is just one part of a larger effort to overhaul the Theme Handbook for modern-day WordPress. Contributors are transitioning the focus from classic theming to block theming, with just one chapter in the handbook devoted to classic themes.” She wrote.
\n\n\n\n\n “Keeping up with Gutenberg – Index 2022”
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2021 on. Updated by yours truly. The index 2020 is here
Thomas Roberts published the First edition of WooCommerce Blocks Extensibility Snaps – a monthly update to highlight things the WooCommerce developers have been working on. This edition covers the new WooCommerce Components and the custom fields for the Check-out block.
\n\n\n\nWordPress VIP has released a handy block governance plugin on GitHub that adds additional governance capabilities to the block editor (GitHub). The Readme file explains usage as well as customization from the default settings.
\n\n\n\nRyan Welcher continued his Block Development Cookbook series with three more recipes:
\n\n\n\nIn case you missed earlier recipes, browse Welcher’s cookbook play list on YouTube
\n\n\n\nJustin Tadlock collected another edition of the What’s new for developers? (November 2023) round-up post. “Much of this edition of our monthly roundup will include changes that have already landed in WordPress 6.4. Read along if you’re still playing catch-up. You’ll also learn about some features that are still in development, so be sure to install and activate the latest version of the Gutenberg plugin to test them.” he wrote.
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph.
\n\n\n\nFor questions to be answered on the Gutenberg Changelog, send them to changelog@gutenbergtimes.com
\n\n\n\nFeatured Image: “Building Blocks” by Holger Zscheyge is licensed under CC BY 2.0.
\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nBirgit Pauli-Haack and Jessica Lyschik discuss the latest default theme, Twenty-Twenty-Four, the latest WordPress release 6.4 and the last two Gutenberg plugin releases.
\n\n\n\n\n\n\n\nShow Notes
\n\n\n\nDiscussion: How to handle custom settings screens in block themes
\n\n\n\nStay in Touch
\n\n\n\nTranscript
\n\n\n\nBirgit Pauli-Haack: Hello, and welcome to our 92nd episode of the Gutenberg Changelog podcast. In today’s episode, we will talk about WordPress 6.4, the default theme, Gutenberg 16.9, Gutenberg plugin release 17.0. And that’s a lot. So I’m your host Birgit Pauli-Haack, curator at the Gutenberg Times, and a full-time core contributor for the WordPress Open Source Project sponsored by Automattic. And today, I have the pleasure to introduce our listeners to Jessica Lyschik, a core contributor and WordPress 6.4 release team for the default theme together with Maggie Cabrera. So Jessica was also the co-lead organizer of last month’s WordCamp Germany in Gerolstein. Both the building of the default theme and the WordCamp organizing were taking place in the same time space in the last few months. So I’m thrilled that you can make time for the show. Welcome, Jessica. How are you today?
\n\n\n\nJessica Lyschik: Hi, Birgit. Thanks for having me. I’m doing great. A bit tired because this week has been quite exhausting, but I’m very much looking forward to today’s episode.
\n\n\n\nBirgit Pauli-Haack: Yeah. I’m so glad that you’re here and it’s been a while that we said you should come on the podcast, so I’m glad you made it today. Yes, there was a lot of work for the Open Source Project project and…
\n\n\n\nJessica Lyschik: Yes, it was.
\n\n\n\nBirgit Pauli-Haack: … I’m so happy. Congratulations. Welcome to Germany. Have you recovered-
\n\n\n\nJessica Lyschik: Thank you.
\n\n\n\nBirgit Pauli-Haack: … from it all?
\n\n\n\nJessica Lyschik: It took a few more days than expected, but I really had to recover from this. There was a huge push in the last few weeks before WordCamp Germany because some things were about to fall apart, but as they always do. But we managed to create a wonderful event and we’ve got very, very good feedback from attendees, sponsors, speakers, literally everyone was super happy to have been in Gerolstein, and that was fantastic. And yes, of course the default theme also took a lot of hours from me. But yeah, I think we did a great job on this and Maggie was fantastic to work with.
\n\n\n\nBirgit Pauli-Haack: Yeah. And we’re going to talk a lot more about that in just a few moments. But before we head into the releases to listeners, we have a couple of announcements from the project that happened in the last, I don’t know, four weeks since the last episode. So first of all, there’s the State of the Word for those who are new to WordPress, WordPress co-founder Matt Mullenweg shares reflections on the projects’ progress last year, and then what’s in it for next year, and the future.
\n\n\n\nAnd it’s also the time where we celebrate the community activities and the software updates. This year it will take place on December 11th, 2023 at 1500 UTC. That’s for our American friends 9:00 AM Eastern, and it’ll be live-streamed from Madrid. Details on how to reserve a ticket for the in-person event, the link to watch the live stream, and information on how to submit the questions for the Q and A portion will be provided later this month. So watch the news section on the WordPress.org website. Of course we have the save the date post link in the show notes. I’m really excited what’s going to happen there. Do you have any comments on that? What do you expect?
\n\n\n\nJessica Lyschik: It’s interesting to see that it got moved outside the US. I think it’s the first time it’s not happening in the US and I would be curious to hear why Madrid was chosen because… I’ve never been there before, but I know that it’s in a very interesting city, so we’re really looking forward to that.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah, me too. Yeah, you’re right. It’s the first time outside the US. It’s also the first time… Not the first time outside of WordCamp US. The previous two times 2021 in 2022 were also a separate event, was not tied to WordCamp US, which made WordCamp US a little bit more flexible when it’s going to take place. The State of the Word was always in December, but now the WordCamp US was in October, was in September, now in August. So it was moved a little bit earlier into the year. I’m really looking forward again, as always, to reflect on what the last year brought, because right now I’m just like you, what happened last week is all I can think about and what I’m reflecting on. But yeah, so we get a chance for that with it. December 11th, 1500 UTC.
\n\n\n\nJosepha Haden Chomphosy published the proposed release dates for 2024. The proposal is actually on the Make Blog. I’d just say it on… Yeah, it’s a little bit hard if you can’t look at it, but maybe you can retain the 6.5 is scheduled to be released March 26. Well, it’s proposed to be released. The release team still needs to chime in there, which makes beta February 13th, beta one. 6.6 is scheduled for mid-July, July 16th with a beta of June 4th. And then 6.7 similar to 6.4 this year with a January release on November 5th and September 24 in beta one. So I’m always looking just one release ahead of time.
\n\n\n\nAnd Héctor Prieto also chimed in and said, “Well, the last Gutenberg release shipped in 6.5 will be 17.7. That’s seven more complete Gutenberg cycles until we have Beta 1 in February 13th.” Wow. It sounds so far away, but seven releases is not that far away. If we release every two weeks, we have already released the Gutenberg 17.0. So there’s quite a few things that might get in there. We’ll see what the developer team is coming up with a roadmap for 6.5. I’m sure that Fonts Library will be on the list of wanted features like the last five releases. So Interactivity API will be certainly make an appearance again, and maybe we see some new data views or admin redesigns. What do you think?
\n\n\n\nJessica Lyschik: Yeah, that sounds pretty good. I also very looking forward to the font library. Pretty much a bummer. It didn’t get included into 6.4, but it doesn’t make any sense if you push something into the release just to have people complaining about it because it doesn’t work as they expect it to. So if it can be a bit more refined, and I hope this gets to be done by 6.5 because it’s so much of a needed feature to have this management of fonts, especially since we have pushed Google fonts out of the default themes. I was one of the people involved in this for the older themes earlier this year, and of course the last few default themes have already been doing this. It always brings a bit of a problem when you have your own custom fonts or a project requires it, then you have an extra additional work with creating a child theme, making sure it does work there, it gets implemented, and this could solve so many issues and would it make so much easier for every user to just…
\n\n\n\nBirgit Pauli-Haack: Yeah. No, I hear you. And I think because it’s such an important feature, it needed a few more iterations in the Gutenberg plugin base before it gets into core to get more of the kinks out. And if I recall correctly, but there were still quite a few things happening in development in Beta 1 and Beta 2. Fonts Library got pushed punted in beta two, but that it really makes sense to have a few more test cycles for it.
\n\n\n\nJessica Lyschik: Yeah. Maybe some iterations for the replacement of templates that got newly introduced for the default theme because right now it’s very hidden unfortunately, so you have to show people where to go. And if this could be improved over the next version, that would be fantastic because you have such a large sidebar when you open the site editor in browse mode and it would be just perfect if we could implement this replacement feature into the sidebar alongside with all the other settings you can do basically on a template.
\n\n\n\nBirgit Pauli-Haack: Right. And I think there are already some versions of that in the Gutenberg plugin release in 16 point… So 16.1 was the last release that got in… No, 16.7 was the last release that got into 6.4. But in 16.8 and .9, there were additional functionality built that, the bug fixes would be backported, but some of them didn’t make it into the beta because it was so late, but it’s already in Gutenberg, so we can definitely test it there and refine it there. The template part itself, the concept for the user, what is a template and what is a page still seems to be a confusing piece of it. And I can understand that because a WordPress user, an existing or someone who was using WordPress for the last, I don’t know, 10 or 20 years, never had to deal with it because it was always part of the theme and all of a sudden now that added a complexity. We didn’t make a good way to abstract that complexity away to make it easier to realize what they’re doing.
\n\n\n\nBut I think the site editor is now on the way to help with that with a different view and edit modes for templates and page content, but it’s still one additional hurdle for a content creator to make.
\n\n\n\nSo this brings us to the perfect segue to the community contributions item that I selected was… So in September there was actually a big discussion around the theme submission to the WordPress repository that included a few features that didn’t comply with the guidelines that helped a new user to figure out what to do with a theme. And strictly speaking, those features were definitely in the plugin territory and the discussions made clear that there is a need for better onboarding, but it also made clear that you cannot make exceptions for one theme and then have the other themes. So why him or why her and not me? So it’s clear that there needs to be a discussion about standards, about the way to do this for WordPress, and that has been opened now a couple of weeks ago.
\n\n\n\nIt’s a post on the theme Make Blog called, Discussion: How to handle custom settings screens in block themes. And this definitely needs your input if you’re interested in that, if you make themes, and if you want to find a way to have a standardized way on getting an onboarding sequence, for instance, for your theme into the guidelines of the theme repository, that is definitely a discussion where you could be. It wasn’t clear to me what the next steps would be, but the next one is definitely comment on it and if you have time, the themes team meets every other Tuesday at 1500 UTC in the themes review channel on the Make Slack. I think I need to put some links there in the show notes. I think that’s not easy to retain from a radio podcast. But yeah, so that is definitely where the community needs to give some input, where the contributors need some help to figure things out. Do you have any opinion of that now with a default theme? Maybe we can talk about it a little bit there.
\n\n\n\nJessica Lyschik: A lot of opinions to be honest. Yeah, I actually did not know about this post. So just two days before we WordCamp Germany happened, so it totally missed me, but I will definitely go through this later on. But yeah, I can see both sides in this discussion actually. So from a theme author’s perspective, you are limited definitely, and there is, from a user perspective, a huge need for proper onboarding. So there is no standardized system, and every plugin and, in theory, every theme, but every plugin does it on its own.
\n\n\n\nThey often look similar, but everyone does it on its own. And I think we have various APIs in WordPress, and I think an onboarding API would be something for the future that we could consider implementing because then you could say, “Okay. Even if it’s a theme, when you have the standardized API, it would be possible for a theme to like, ‘Hey, just put these settings and here can you change this and upload your logo or whatever that needs to be done for a theme to be set up properly or look good.\'” And yeah, that’s pretty much what I would like to see in the future at some point.
\n\n\n\nBirgit Pauli-Haack: Yeah. The question is does it have to be in the theme or should it be in core? Should it be on the hosting side? I know that there is a product out there by the fine folks at Extendify that has an onboarding sequence that they offer hosting companies to sell their WordPress installations or come with their WordPress installation. I saw some prototypes and those looked really, really well. So the big problem is when you have these features in a plugin or in a theme and the features are plugin territory, what you do is pretty much close down the system that people cannot switch themes without losing content. And that is something that the theme directory really wants to avoid. And so any onboarding sequence or feature would need to make sure that the content that it’s added through that place is in proper places in the database. So when the theme changes that the content is not lost. And that I think is a bigger problem than I think we make it out at the moment.
\n\n\n\nJessica Lyschik: Yeah. But then it’s definitely core territory, so it should land in core this onboarding API, whatever you want to call it. But yeah, that’s the point because otherwise when you just say it’s okay, it’s just for plugins, then themes will always come with a companion plugin. And the question is, is that really needed? Then why it should be in core? And no matter if it’s a plugin or a theme, they all can benefit from this kind of onboarding.
\n\n\n\nBirgit Pauli-Haack: Yeah. And there are these efforts to do a redesign of the WP admin in certain ways. Maybe that brings back that discussion for core contributors to add something like that as well. So I think the discussions are all there. One is again on the Make Theme Block. Yeah, chime in, be part of it, be part of the discussion, and then you may be part of the solution as well. So that’s part of what you might have missed. Jessica and I did while we were celebrating WordPress Germany, I was also on a team retreat for a while and then had four days vacation, and all of a sudden my backlog is insurmountable and I’m going back on it one day at a time.
\n\n\n\nJessica Lyschik: Definitely.
\n\n\n\nBirgit Pauli-Haack: WordPress 6.4, it’s called Shirley after the iconic jazz artist, Shirley Horn, was released on November 7th with a quick point release on November 9th to fix a bug with an older version of cURL, which is a command line request tool. And the request tool we have in the… If you are very interested, it’s very highly technical. And if you’re interested, I’ll share the link to the WPTavern article to it. They have the skinny for you. But this release is a combination of an immense effort and passion from over 600 contributors across at least 56 countries. And it included 170 first-time contributors. This is pretty huge, I think it was… Yeah. So 600 contributors is one of the biggest releases. So we talked on this podcast in episode with Joni Halabi, Nadia Maya Ardiani, Tammie Lister, and Ellen Bauer, already on WordPress 6.4. It was in the making for quite a while, shorter than others. But I also will ask today’s co-host, Jessica, the same question. So what features in 6.4 excited you the most and why?
\n\n\n\nJessica Lyschik: Well, the default theme, obviously.
\n\n\n\nBirgit Pauli-Haack: Apart from that.
\n\n\n\nJessica Lyschik: … we will get into that later. Apart from that, of course renaming group blocks is something I was looking forward to. It has been so needed in the past for me and I’m very glad it’s finally here. And I can’t wait until this comes to all the other blocks as well because it will make editing so much easier, especially if you have larger sites with lots of groups and lots of content grouped together. That’s one of my highlights. And the lightbox feature, the image lightbox is pretty neat one too. And what else was in…
\n\n\n\nBirgit Pauli-Haack: No, it’s not.
\n\n\n\nJessica Lyschik: I’ve forgotten
\n\n\n\nBirgit Pauli-Haack: There’s a highlight. So what I also like is that you now, as a user, can categorize your custom patterns. You can not only have a huge list of patterns that you spread all over your website, but you can also put them in categories. I think that’s a major place to be for patterns.
\n\n\n\nJessica Lyschik: Yeah. And maybe background images in groups. You said last evening, so yesterday evening, I was presenting changes in 6.4 to the local meetup group, and it was pretty exciting to see how easy it was to just add a background image to a group block and put some contents in it and make it look nice.
\n\n\n\nBirgit Pauli-Haack: Yeah. I also like that you can now see the thumbnails in the list views of your pictures or the image blocks or the gallery blocks, so that’s pretty cool too. Yeah, the footnote was new in 6.3, but now you have vertical text support, which is the vertical text support is actually pretty much rolled out as well in 6.3, but it got a lot less fragile in 6.4, so that is definitely a good place to be too. So Rich Tabor posted a Twitter thread with 19 different features or highlights from 6.4, which I will definitely share in the show notes so you can follow along. Here’s a little video on it and how to use some of those. Although the font library didn’t make it and neither did two new blocks that were actually on the list, they were punted to 6.5. It’s still really a feature-rich release.
\n\n\n\nThere is a microsite now available. You can explore the features with. Yeah, I can also share some of the other posts from WPTavern. And Carlo Daniele from Kinsta did a great writeup on the features of WordPress 4. So WordPress 6.4 also comes with a few developer relevant changes and I would highly recommend that you check out the WordPress 6.4 field guide to learn about them, especially the block hooks for dynamic blocks where you can add a block to a block automatically with your code. And we talked about this on the episodes before like a like block or a shopping card block or even an additional lightbox feature if you want to do that.
\n\n\n\nThere’s also new admin notice functions, updates to the HTML API. The removal of the attachment pages for new installations is actually something that Joost van den Bergh was really passionate about and is very happy that it finally made it into WordPress 4 because for a SEO, they’re not useful, but they clutter the whole basis of pages on sites in the Google index. So there’s improved caching, autoloading for plugins, and options. So there’s a lot of few more things there, so the field guide is your friend. Is there any of that that excites you more or that you know that you need to explore because you have a real case application for it or so?
\n\n\n\nJessica Lyschik: Yeah. I think the block hooks is something definitely to explore because it’s very interesting feature to just hook in as we know it from the normal WordPress hooks just but for blocks. And yeah, one thing that’s really cool is also the removal of that attachment pages. I think I have to check again, if you can do it for existing sites somehow. I think there was something possible. I quickly found it somewhere, but I’ve forgotten it already.
\n\n\n\nBirgit Pauli-Haack: Yeah. It’s in the dev notes, how you can make that available to existing pages out of the box. It only works for new installations, but you can go back and update your existing sites to…
\n\n\n\nJessica Lyschik: Yeah. I think it would be very beneficial for already existing sites as well to have that happen.
\n\n\n\nBirgit Pauli-Haack: Yeah, absolutely.
\n\n\n\nJessica Lyschik: But it’s a great way to introduce it without making too much of an issue when you just remove them with the update instead of as it is now, it’s only for new installations and then you can manually update it to also disable them.
\n\n\n\nBirgit Pauli-Haack: Yeah. There’s even a WP Options way to do that in the interface. There’s WP admin/WP options where you see all the options files. You can definitely do it from there, but you can also do it code wise.
\n\n\n\nYeah. So now let’s talk a bit more. We mentioned it multiple times before the new default in Twenty Twenty-Four. So yeah, you, Jessica, and Margarita (Maggie) Cabrera were the co-leads for the development, and Beatrix Fialho created the first designs, congratulations. It seems that the first feedback was overwhelmingly positive. We saw that coming during development. I don’t know if you saw it, but I saw it.
\n\n\n\nJessica Lyschik: Yes, I saw it, and it continued and it still continues. And that is what really makes me happy that Maggie and I did something everyone is excited about. That’s just so cool.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I just want to do two quotes that I found on Twitter. One is from Hashim Warren, he’s a product manager and worked for Gatsby and WP Engine and also for Apollo. And he said, “Played with a new WordPress Twenty Twenty-Four theme for a few hours. Then quickly switched my side to use it. The first time, I’m using the default WordPress theme on a project I care about. Really great work there.” Yay.
\n\n\n\nJessica Lyschik: Yay. That’s cool.
\n\n\n\nBirgit Pauli-Haack: And Rae Morey, she’s the editor of the, The Repository newsletter tweeted her comments as well and says, “Holy crap, WordPress 6.4 and Twenty Twenty-Four are a match made in heaven. Props to everyone who contributed. Saying goodbye to my page builder.” The updated editing experience is a game changer. Previously I found it so confusing to know where to start when I enabled a block theme. Yesterday, I redesigned my whole site in a day with Twenty Twenty-Four, and here’s the site, it’s therepository.email. The repository is an email that’s supported by GoDaddy. And Rae had just announced that they have the four-year anniversary on the newsletter, and I think it was edition 192 that came out on today. That’s Friday, November 10th. So yes, Rae, great comments there for the team.
\n\n\n\nJessica Lyschik: I just opened the site and it looks pretty good.
\n\n\n\nBirgit Pauli-Haack: Yeah. And as everything in reference, it’s created by a team of contributors and from the props list of the import ticket into core. I counted 83 contributors in total. That’s a massive participation. Must’ve been quite exciting to wrangle all the input, feedback, contributions.
\n\n\n\nJessica Lyschik: It was mainly managing actually. So I did a few things on my own, luckily, yay. I could also contribute code. But yeah, I was mainly on the management side on this, but it was so exciting to see that so many people came in and opened issues, open pull requests, and helped out with making this a reality given the very limited time we had actually. And I think that’s not something that a lot of people are aware about, but we had just basically a month, but then we extended it because like, “Okay. It’s just updating patterns so we can do it during better as well.” So hope no one kills me for this, but yeah, otherwise it wouldn’t be in the state that is now. And yeah, it was so great to see.
\n\n\n\nAnd I think also what really helps in contributing to the default theme is that it’s made on GitHub as well, just like the Gutenberg project because I can only speak or I can also speak, especially for myself because I find it so hard with Trek and SVN to make fixes or do new stuff in it and in GitHub it’s just so much easier for me even to have this entire process done. And we just set up very few rules and it really went up very well, had great discussion sales too. And again, I’m so happy that so many people contributed, and we also did our best to include everyone in these contributions file because everyone deserves to be in there, even if it’s just opening an issue and saying, “Hey, I got a problem with this,” or, “Is this something we should think about?” Because every discussion is worth it.
\n\n\n\nBirgit Pauli-Haack: Oh, yeah. Especially bug reports. It’s half the work is already done, somebody found it and nobody else needs to go if you find a fix in time to go through it. So yeah, it’s really valuable time to spend to contribute to that. Yes. And so the theme itself has an outlook for three different use cases. Can you talk a little bit more about that?
\n\n\n\nJessica Lyschik: Yeah, sure. So the original idea was… I shared it first time with Maggie when we met at work in Europe just a few days earlier it got announced, the release squad got announced. So I met her there the first time and I shared this idea with her, let’s make a default theme that does not only showcase that you can make a block with WordPress, but you can do any type of website basically. Of course, we could not include any type of website. That would be pretty huge and we would still be developing that. But what are the main very often used cases where WordPress is used as the platform for this website. So of course blogging is one, but business is also a very important one. And I think many websites today getting set up on WordPress are business focused in some way.
\n\n\n\nAnd portfolio was also another one to showcase your work, either if you’re a graphic designer or make products of your own physical products, you can also showcase them with these. And it became pretty clear that this was the way to go and I’m glad that it did not get questioned it too much, but that people also saw that it’s an interesting idea to showcase what’s possible with WordPress in these three specific use cases. And once we knew that Bayer was doing the designs for it, we also briefed her with this entire brain child of us, how we would like to see this and how we’d like to see the default theme coming together. And I must say again, she did a fantastic job on this as well, bringing this to life and also the style variations, giving a bit of variety in what could colors of fonts basically look like in a setup of the patterns that we already have.
\n\n\n\nBirgit Pauli-Haack: So one of the big features that I think made people very successful at the first round of trying to customize their website is that it uses full-page patterns. So when you create a service page, you get your services in there, you get a header graphic, you get a footer graphic, and all that. So I think that particular feature was something that was available before but not long before, maybe 6.2, but it wasn’t showcased by anyone that much. So having that in the default theme definitely makes it really good available for everybody.
\n\n\n\nJessica Lyschik: Yeah. It just lowers the bar for the average user to like, “Oh, hey, I can just switch out this template with the other one I prefer or I need for my website on this.” And I think that’s something… Because previously you would have to delete all the blocks that you had on the site and recreate them on their own and you have to find the patterns that you would use and how could you arrange them. And with Twenty Twenty-Four, you get pre-built templates you can already use or just use and adjust to your own needs. And I think this is what’s helping people a lot compared to Twenty Twenty-Three, which was pretty stripped down basically.
\n\n\n\nBirgit Pauli-Haack: Yeah. So for our listeners, I have a few links for you. One is the blogger demo, and the artist/photography demo, and of course the main site, demo site. And then also a link to the patterns and of course the download link if you don’t have that yet. Yeah, so try them out, I think it’s a great move forward. I think the Gutenberg Times will always also will migrate to a block theme, probably the default theme. I have started the process and then backed away again because I need to have a few quiet moments, haven’t had that yet to think through some of the features that we need because we need the podcast template and we need the podcast archive template and the plugins don’t provide that yet, so we figure that one out and a lot of other things, mainly having the time.
\n\n\n\nJessica Lyschik: That would be a cool project to do it in public and have people following around maybe.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah, I’m trying. I’m probably teaming up with Justin Tadlock who’s a theme wiz to help me out with that. So I actually finished that project because most of the time, some of the project I just start see what I can do and then, okay. Yeah. Now I know how this works and then I lose interest. But this one I would need to have to finish and it will be the first redesign since, I think, 2020. So three years or four years then. All right. So is there anything else that you want people to know about the defaulting?
\n\n\n\nJessica Lyschik: Go test it out, have a look at it, play with it. I would be super interested in any feedback, positive or constructive. Negative, maybe not, but constructive. That’s why I said it because we can always learn for future themes. What does work well or what does not work not so well because I’ve already seen a bit of feedback on people implementing it. For example, Matt for Matt Report had already done a video on this. I only saw the first bit of it so far and it was very interesting to see what he struggled with actually that I wasn’t so much aware that was would be a problem. And that’s definitely something you can always…
\n\n\n\nBirgit Pauli-Haack: Do you have an example?
\n\n\n\nJessica Lyschik: … look back at his feedback. Sorry?
\n\n\n\nBirgit Pauli-Haack: Do you have an example of what he struggled with?
\n\n\n\nJessica Lyschik: Actually it’s when he updated on this mattreport.com website and he had a static site configured as his front page, so the homepage, and then had this lock subsite as on the slash block. And when you have this set up, what happens is Twenty Twenty-Four brings the template you have you see on the front page when you have not set up that it brings the entire template in, which can be confusing for people because there’s all this content they never edit before but it’s in the template. So that’s something I wasn’t aware of that even in this case I thought it would be overwritten already, but of course now that I saw it’s definitely clear what happens.
\n\n\n\nBirgit Pauli-Haack: Do you think it’s a bug?
\n\n\n\nJessica Lyschik: That’s a good question. If it’s a bug or a feature, depending from which side you’re looking at it. But he had to remove all the contents to just simply show query block with the latest posts on the website. But this is not something particularly the default theme can fix. Of course you could remove all that extra patterns from there, but it’s also something we have to send upstream to the Gutenberg repository to say, “Folks, please look at this. It’s okay, it works somehow, but we need a way to fix it.” Or a very common thing is people edit their templates, switch the theme, and then their content is gone. It’s not gone but it’s in the template so it’s not there in the next template. And these custom user changes are also something that needs to be considered for the future because the more we work with block themes, the more we see where we still have some issues we need to fix.
\n\n\n\nBirgit Pauli-Haack: Those issues were there before, but they were abstracted away because it was the theme developers thing, but the user never was confronted with it because the theme took care of it with an if statement and all that, and it tapping into the settings and then because you don’t have these if statements in the template somehow all of a sudden it’s a little bit disjointed there. Yeah, I can see that. Yeah. All right. Okay, good. Yeah, I had the same problem when I switched my… I have a personal technology blog where I just keep track of things that I learned, that I need to look up three months from now, and I probably will have forgotten how I did this. And that was one thing that I had a blog front page, but I needed to remove the stuff from the default theme. Yeah, that’s true. Didn’t remember that, but now that you mentioned it.
\n\n\n\nAll right. So we are done with 6.4 for now and the default theme. Thank you so much about letting us look behind the scenes there.
\n\n\n\nWe are coming now to the last two Gutenberg releases. Let’s start with Gutenberg 16.9 that was released on October 25th and Justin Tadlock was the release candidate and he shared all the information. Of course in his release post it entailed 168 PRs from 60 contributors and one of them was new. So as a new feature or what came in, and I wanted to highlight, is that you mentioned it for 6.4 was to enable the renaming of group blocks in 6.4. With 16.9 in Gutenberg you can rename almost all the blocks. So the custom names are stored in metadata in the block markup and meaning they can also be used for panon and templates, and that makes it so much more, I don’t know, less ambiguous for users when they look at the blocks that are in the templates or on their site. So that’s a great feature.
\n\n\n\nJessica Lyschik: I mean, my workaround right now is to use the anchor feature for this. It works but it creates anchors. Yeah, it’s not the best way, but if it’s coming to 6.5, that’s so great.
\n\n\n\nBirgit Pauli-Haack: Yeah. And because it’s in 6.9 it will be in 6.5 unless somebody has additional bugs that they find there during the beta version.
\n\n\n\nJessica Lyschik: Then we have to fix it before beta one.
\n\n\n\nBirgit Pauli-Haack: Then we have to fix. Yeah, absolutely. Absolutely. The next item is block specific commands as contextual suggestions. So 6.2 came with a command palette… Or 6.3, I forgot. 6.3 I think came with a new command palette where you do control K and then you get a search bar and then you can ask for certain things like add a post or open the patterns. And now there are block specific commands that are suggested contextually. So when you’re in a block it shows do you want to transform it or something like that.
\n\n\n\nSo it gets more like, I like that this software now becomes a little bit more contextual and you don’t have to know which menu item on which screen in which level you find something to switch on or off or you have to do three clicks to switch on the top toolbar and now you can just have the command bar, switch on top toolbar and it doesn’t. I don’t know if that command already exists, but I will find out. It’s almost like a shortcut. So these little things are a little bit on the edge of value, a palette command or just “Why don’t you just get a keyboard shortcut?” It’s the other thing.
\n\n\n\nJessica Lyschik: It makes it more keyboard friendly. So if you’re used to or if you prefer to work with the keyboard, it makes things so much easier because otherwise you have to always use the mouse to get to that contextual menu to select to copy or duplicate something or add before and after. And if you have these commands in the palette, you can just hit command K or control K and just use your hands on the keyboard instead of using your hand on the mouse. And I think that can be definitely beneficial for people who prefer to work on the keyboard only or prefer to work on the keyboard.
\n\n\n\nBirgit Pauli-Haack: And it also speeds up your publishing process when you only have, I don’t know, six sets of commands that you punch in into the command palette instead of clicking around with a mouse. Yeah, absolutely. I wonder if that’s on the roadmap for ISO 7.0 WordPress like having a programming, I as a user can Daisy Chain commands into a workflow? I don’t know if that’s going to be possible or it’s even thought about it.
\n\n\n\nJessica Lyschik: Oh, like Apple shortcuts.
\n\n\n\nBirgit Pauli-Haack: Yeah. Kind of Apple shortcuts. Or what was the other one? Alfred on Mac. There are quite a few. Even GitHub has workflows where you can just Daisy Chain some of the commands, but yeah, maybe we get a plugin for that. How about that? That’s definitely plugin territory I think. All right. The next feature is for developers, there is a new component and it adds the tabs. That’s a composable tab panel which was before, but it’s a tab panel version two. So you can build out interfaces that use tab labels and tab content better with components that are… It’s now available, you can test them out.
\n\n\n\nThe documentation seems to be already in there on the story book, not the style book, the story book for the developers to figure out how these tabs work. And there’s also a type button for the Vanilla button element is now available so you don’t have to make it up. What else? Oh, yes. Patterns got some new management features and it’s a nice addition with duplicate pattern command. They’re all for the command palette, rename the command, rename the pattern, rename delete options for pattern categories in the site editor. There are new media related categories for the patterns. So there’s quite a few changes in there to make this all a little bit more comprehensive as a management tool to create patterns and to make them available to certain content production people. Any comment, any ideas, any thoughts?
\n\n\n\nJessica Lyschik: Sounds pretty good. I have to test this out. I haven’t seen this. So again this is… But that’s pretty interesting to have these renaming features also now via the command palette because that’s something also I appreciate to have these pattern categories now that you can also create on your own and make it your own basically. That’s pretty cool.
\n\n\n\nBirgit Pauli-Haack: Yeah. And also add them to the theme and help the user to find things better. For developers, definitely something that they have been asking for quite a bit regarding extensibility of the block editor. There is now a new slot to put information or interfaces into the plugin post excerpt slot, and that means that in the post excerpt place where not only there’s the excerpt but there’s also other things in there. You now can, per plugin, add additional sections there. So that’s specific for the plugin for the post excerpt space there. That’s in the sidebar when you want to… The document settings, for the post itself, we also see featured image.
\n\n\n\nThere’s also one for the published slot for the pre-published slot, and there are quite a few other slot fills that you can use as a plugin developer, but we need more, I guess. And this one is definitely one that a lot of people ask for. In this design tools there are two changes. One is that the measurement 16.10 and 10.16 options were removed from the aspect ratio drop down and they figure that it wouldn’t take too much harm to do that because it’s too close to the 6.9. And I think that’s pretty much the justification for it.
\n\n\n\nJessica Lyschik: Yeah. To have less options and it’s not too overwhelming because the change from 16 to 10 to 16 to 9 is not that huge. For example, when you have four to three or three to two, that’s a big of a bigger difference than if you would have just a little bit of more on one side.
\n\n\n\nBirgit Pauli-Haack: Yeah. And then the other one is that you can now add CSS level 4 viewpoint relative units in the theme.json setting spacing units. And that brings us closer to bridge the gap between the big philosophies, intrinsic design, but I want my 15 media viewpoints crowd to… And intrinsic design does not solve all the viewport problems or mobile problems. So this definitely brings us closer to having giving theme developers and designers a little bit more options.
\n\n\n\nJessica Lyschik: I haven’t seen them yet, but they look very interesting. So much to catch up.
\n\n\n\nBirgit Pauli-Haack: Yeah. Come as a guest to the Gutenberg Changelog and you know what you missed.
\n\n\n\nJessica Lyschik: Yeah. You learn more than you think what you have missed in the past four weeks and beyond probably.
\n\n\n\nBirgit Pauli-Haack: Yeah. And there is a new API with 16.9 is that you can retrieve the pagination totals with the get entity records call. So get entity records function is a call to a query call to get the entities, be it pages, posts, post types metas, all that kind of thing. And now it also comes with a total so you can build pagination or use it some other way. That’s certainly for the developers quite interesting, which you are. So I hope it interests you.
\n\n\n\nJessica Lyschik: Definitely. That’s very much things I can look into. As I said, I have to catch up.
\n\n\n\nBirgit Pauli-Haack: Yeah. And the team was really… Although there was a slump in October kind of, and we talk about it a little bit in the 17, but there’s definitely a lot’s happening, there’s some momentum going with a lot of different directions. We are skipping over all the bug fixes that we saw in that change log and some other minor enhancements and drop right into the experiments because when you take a look at the new experiments page of the Gutenberg plugin, you see quite a few listed.
\n\n\n\nAnd the most interesting for me and probably other people in WordPress are the new data views. Those are prototypes for the admin redesign project on how to display the lists of posts, the list of pages, post types, and whatever plugin would need things to be listed. And in this Gutenberg version, you now can see the grid layout of those pages and how it looks when list contains a featured image or controls for the actions to switch the layoffs and also to have some additional actions in there. So it’s quite an interesting study to go in and look at the experiments. Of course everything is experimental, meaning, nothing lasts, nothing is final.
\n\n\n\nJessica Lyschik: Things will break.
\n\n\n\nBirgit Pauli-Haack: … things will break. And if you have ideas or want to comment on some of the features, GitHub is definitely your friend there. Comment on the current PRs or the PRs that are not merged yet or create new issues to discuss additional things, what you might need, what you think is missing because this is one of the few pages in admin that almost every plugin extends or needs and getting into the discussion. As soon as possible, make sure that voices are heard and listened to because sometimes there is this complaint that, well, we weren’t asked or we weren’t listened to or we didn’t know that was going on. And the discussions were designed, decisions were made were actually three years ago, like the block theme in 2022 or even in 2019. In 2019 we were already seeing prototypes of block themes and there were some, Gutenberg live Q and As where we talked about block themes, but only now in 6.2, .3 they came and went to WordPress 5.8, and then we’re always iterated on until now 6.4.
\n\n\n\nBut the other three years of it were missed by a lot of people that might have at least follow up on the discussion and see why decisions were made. So this is the place to get in on the new redesign. Another experimental feature there is basic form input blocks and to build out basic forms. Also very, very experimental and just a prototype. But if you enable those experiments you can see it in action and try it out and see how that works out, and if you can get to that. So that is the idea to bring a form building to core, at least the basic part. So you don’t need yet another plugin to do that, but it also helps standardized, it also aims for a standardized blocks that you can then enhance in plugins that plugins developers can enhance for their products, but can always be built on a standardized way of forming the input, doing the processing, and then what comes after processing to have that a unified API for that.
\n\n\n\nJessica Lyschik: Yeah. And I think this can only be beneficial for the future. So if everyone speaks the same language, you can make adjustments… you get the basics and you do not have to reinvent the wheel. You get the basics and then, from that point on, you can iterate what to your specific needs or to that project specific needs for example. And I think that’s a pretty cool feature.
\n\n\n\nBirgit Pauli-Haack: It is, especially for an Open Source Project. When you find that all of a sudden hundreds of people are maintaining the basis of your code and you only need to really handle the things that you, as a plugin developer, care about, that makes it a value added feature for you base your business on, but your basis is actually covered, and it’s good for all the whole ecosystem to have some then standardized way of doing things. That’s also why pretty much the block editor needed to be in core right away to have other people build on top of it to see if the other page builders can re-ramp their system to build on top of something because page builders closed the system down, didn’t they?
\n\n\n\nJessica Lyschik: Yeah. They did.
\n\n\n\nBirgit Pauli-Haack: You couldn’t change your site over to a different theme that wouldn’t support that page builder. So you were pretty much locked in into that particular way of doing things. And that’s never a good system for an Open Source Project that says open source in the name. Just to go back to that history of why wasn’t it a plugin?
\n\n\n\nThere’s a few documentation things that I wanted to point out. There’s also initial documentation for the AWs, so if you want to experiment with them, you can definitely follow the documentation on that. But there’s also a way, the documentation was updated for the appearance tools in the theme.json to include using background images for blocks that you can find now. And so when you have a theme, especially classic themes that enable appearance tools to have a set of design tools available to the block editor, you can switch it on and off for the background image as well. So I think that was Gutenberg 16.9. Is there anything that stood out for you apart from what we talked about?
\n\n\n\nJessica Lyschik: No. I think you pretty much picked the really cool ones. I mean, of course there’s so much going on. Just have a look at these blog posts. Everything is listed there and I think they’re super helpful to have an overview. And even if you do not get everything right away, when you come to a specific issue in developing for a theme or for a plugin, it is super helpful to have these handy so you can look up that version and you have a focused bird’s eye view. I know that sounds weird, but it is like that. And you can just see if anything in that version actually breaks whatever you’re working on or if there was a breaking change that makes things appear different than it was before. So they’re super helpful.
\n\n\n\nBirgit Pauli-Haack: It reminds me also to make a pitch for a series that will come out this week in its 9th or 10th edition. That’s the what’s new for developers’ monthly post on the WordPress developer blog where Justin Tadlock and I, we put together a list of things that are just new for theme developers for plugin developers and then some highlight things where even if they’re interface, user interface, or end user capabilities, sometimes a developer needs to know that that’s there so they can include it into their features and products. And then there is also a section on what’s new unlearn and the links to the developer hours. You mentioned that you were last week at the developer hours with Justin Tadlock, and Nick Diego, and with Maggie, and talking about the default theme. Those links are in that what’s new for developers once monthly post as well.
\n\n\n\nAnd the developer blog is available on developer.wordpress.org/news. So keep that in mind. It’s a good blog to subscribe to and has a wonderful RSS feed. And that was the pitch for the developer blog.
\n\n\n\nThough next up, very short, relatively short, the Gutenberg 17.0 release, Héctor Prieto was a release lead and it supports many small fixes and developers also made progress on the data views experiment that we just talked about. So with the two plugin releases, there’s definitely some headwind there.
\n\n\n\nSo the link control for the menu, there were new icons added to it, the blog icon for the block homepage and the home icon for the front page for the link control in the navigation block as much as I see it. And then the block theme preview, you also can see the loading state. So I don’t know if nobody really made a big deal out of it, but WordPress 6.3 came with a block theme preview in the admin.
\n\n\n\nSo you were looking for a new theme and if there’s a block theme, you could actually grade in the site editor, you can see a preview of the theme, you can see your content in the themes’ makeup. And I really enjoyed doing that with quite a lot of themes that were in the repository. Now this feature has gotten a new embellishment was that you now could actually activate the theme from the preview and now you see how the loading state works when it’s activated. So it goes from preview to actually, “Oh, this is now my theme and I can stay in the editor and make all the changes that I need to do in my templates or in my content and all that.” So it’s pretty neat, the block theme or preview.
\n\n\n\nJessica Lyschik: Yeah. Sounds pretty nice.
\n\n\n\nBirgit Pauli-Haack: I don’t think a lot of people have used it yet. I don’t see people talking about it. I don’t know.
\n\n\n\nJessica Lyschik: I mean, it’s a hidden feature, I guess, maybe then that’s why people are not aware of it. It’s like so often you come across something and you did not know that this thing existed.
\n\n\n\nBirgit Pauli-Haack: Look at that. Yeah, and I think, I guess, people don’t… I don’t know if that feature… There was before in the customizer where you could preview a classic theme, and I don’t know how many people used it before that we’re looking for it and we’re disappointed that they couldn’t do this with a block theme because it didn’t have that feature and now do it. I guess we need more adaptation of block themes to actually for people to use it more. The 7.0 also brings in the components, a new ariakit-based dropdown menu component that can be used in plugins and in your blocks if you need to. And it’s more accessible. And our kit is a small footprint, really built out kit for area labels and accessibility support for developers to make it less. You don’t, as a developer, have to know a lot about accessibility to still be accessible with that tool. So quite a few components will use that ariakit as well. And the developers are in the progress to migrate some of the components over to actually use it as well.
\n\n\n\nBut this is a completely new build component, the dropdown menu. There were new suggested commands for editing with a pattern similar to 16.9 as we dotted. And then there is one thing, ensure that term description block is registered in core that I think, actually, was that back ported to the version yet? I think it’s for 16.4. It was found in beta and yes, it made it actually into 6.4 that you can use the term description block that was available in Gutenberg also in your templates in 6.4 for your theme. That was an interesting addition. Either it was forgotten or nobody thought about it, but it definitely made it and it’s helping so much more. So what does it do? If you have a category page, archive page, you can actually add the description that you put into your interface for the category into the template and design it and have all the design tools for it. Am I right with that?
\n\n\n\nJessica Lyschik: Yeah, I think so. I guess, probably just got forgotten or, anyone who worked on this, never had a use case for this and someone just popped up saying, “Hey, why is this not available?” And it finally made its way. I wasn’t aware that it was put into 6.4 already. But yeah, good to hear.
\n\n\n\nBirgit Pauli-Haack: The 6.4 just came out, so it made it into the release candidate three I think. Cool, cool, cool. I guess we weren’t done with 6.4.
\n\n\n\nJessica Lyschik: You were never done with developing software, unfortunately.
\n\n\n\nBirgit Pauli-Haack: No. Yeah. That’s a Japanese beauty philosophy or design philosophy. It’s never done. It’s nothing permanent and it’s not perfect. Those are the three… that pretty much tells me, “Yeah, that’s the web.” You are always fiddling with something, and sometimes the websites go away, and you’re never done with things, and it’s never perfect.
\n\n\n\nJessica Lyschik: No, that’s pretty much true.
\n\n\n\nBirgit Pauli-Haack: Yeah. It’s my approach to web development now. I don’t have a lot of expectations. I take it like the weather.
\n\n\n\nSo I think that was it for the show. I think we talked quite a bit about things. Thank you so much for being on the show and talking with me through 6.4, the default theme and the plugin. Is there anything that you want people to know or how can people get in contact with you that you didn’t get to talk about before?
\n\n\n\nJessica Lyschik: Yeah. How to get in touch with me is relatively easy. I’m on Twitter or X as it is now under my name Jessica Lyschik. If you have Jessica Lys, then you can find me definitely. I am Jessica on the Mac Slack, WordPress Slack, you can find me too. And yeah, pretty much on every social network. I will probably not check them all, but Twitter and Slack is the best way to get in touch with me, definitely. And, yeah.
\n\n\n\nBirgit Pauli-Haack: Awesome.
\n\n\n\nJessica Lyschik: Maybe one thing I probably didn’t say in the beginning is I just started a new job last week, so I’m now with a team of Greg.
\n\n\n\nBirgit Pauli-Haack: Oh, congratulations.
\n\n\n\nJessica Lyschik: Yeah. Thank you. And yeah, that has been on top of everything else, so that’s why I am a bit out of date on so many things, but I’m catching up and got a ton of new information, like what’s going on there, what they’re going to do with the product. And it’s really interesting and super fantastic team, really great people and I’m very looking forward to bring in my knowledge to their knowledge and let’s make some fancy things.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I saw there were also a big sponsor for WordCamp Germany. And Sandra Kurze, she was also a speaker. So they’re all quite active in the WordPress community. Yeah, I met a few of them at WordCamp in Porto actually 2022. And since then they have been be more and more active in the community. So I’m glad that they hired you. Yeah, congratulations.
\n\n\n\nJessica Lyschik: Yeah. Thanks.
\n\n\n\nBirgit Pauli-Haack: … have some input from you and some contributions there. Yeah. All right. Well, we’re coming to an end and before I end the show, I want to remind everyone, as always, the show notes will be published on gutenbergtimes.com/podcast, and this is episode 92. And if you have questions or suggestions or news you want to include, send them to changelog@gutenbergtimes.com. That’s changelog@gutenbergtimes.com. Thank you everyone, and I’m glad we are back in talking to you. And thank you for listening, and goodbye.
\n\n\n\nJessica Lyschik: Bye.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 12 Nov 2023 15:03:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Gutenberg Changelog\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"WordPress.org blog: The Month in WordPress – October 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16365\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2023/11/the-month-in-wordpress-october-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9742:\"September-October 2023 was yet another fun and eventful chapter in WordPress, with more WordCamps hosting exciting discussions, knowledge sharing, and learning. This month also welcomed the release of WordPress 6.4 and the Twenty Twenty-Four theme. Let’s check it out.
\n\n\n\nWordPress 6.4 “Shirley” was released on November 7, 2023, and named after the iconic jazz artist Shirley Horn. With the release of WordPress 6.4 comes the new Twenty Twenty-Four theme, a multi-faceted, highly flexible default theme pre-loaded with more than 35 templates and patterns.
\n\n\n\nThis release includes more than 100 performance-related updates for a faster and more efficient experience. There’s also a host of new features and enhancements that help improve the content creation process and streamline site editing.
\n\n\n\nWordPress 6.4 was made possible by more than 600 contributors in at least 56 countries. Leading this release has been an underrepresented gender team, emphasizing WordPress’ commitment to fostering diverse voices in the open source project.
\n\n\n\n \n\n\n\n\n\n\n\nMark your calendars for State of the Word! The annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg, will be held on December 11, 2023. For the first time, the event will take place outside North America—this time with the Spanish community in Madrid, Spain.
\n\n\n\nA live stream will be available for WordPress enthusiasts who will not be able to attend in person. Stay tuned for more information, including how to reserve a ticket, soon!
\n\n\n\n \n\n\n\n\n\n\n\nTwo new versions of Gutenberg shipped in October:
\n\n\n\nOctober’s Core Editor Improvement post dives into all the writing enhancements expected in the latest WordPress 6.4 release.
\n\n\n\nhttps://wordpress.org/news/2023/10/episode-64-patterns-in-wordpress/\n\n\n\nHave a story we should include in the next issue of The Month in WordPress? Fill out this quick form to let us know.
\n\n\n\nThank you to Bernard Meyer and Reyes Martínez for their contributions to this edition of The Month in WordPress.
\n\n\n\nJoin over 2 million other subscribers and receive WordPress news directly in your inbox.
\n\n\n\n Subscribe\n
\nWordPress Executive Director Josepha Haden Chomphosy has published a proposed schedule for 2024 that includes three major core releases. The dates have not yet been set in stone but have been planned to avoid major holidays and WordPress events.
\n\n\n\nThe first release of the year, WordPress 6.5, is scheduled for March 26, followed by 6.6 in July and 6.7 in early November.
\n\n\n\nAlthough WordPress had officially concluded Phase 2 of the Gutenberg project (focused on Site Customiziation), 6.4 was focused primarily on extending existing features in the block and site editors alongside initial explorations of Phase 3 (Collaboration). Releases in 2024 will go full force into collaboration features.
\n\n\n\n“Given that 2024 will hold a bulk of the work for Phase 3, I expect that 6.5 and 6.7 will be focused on those Collaborative features,” Chomphosy said. “I would like to propose that 6.6 be held specifically for maintenance and general polish of the software (as was wished for earlier this year).”
\n\n\n\nChomphosy asked for feedback on the timing and focus of the planned releases. WordPress core committer Pascal Birchler suggested swapping the focuses for 6.5 and 6.6, as it’s not clear how much of of Phase 3 work will be ready in time for 6.5. The suggestion also makes sense in light of the features that didn’t make the cut for the previous release.
\n\n\n\nWordPress 6.4’s release squad had to punt the planned typography management flagship features and these are anticipated to land in 6.5. This includes a Font Library and server-side @font-face CSS generation and printing, which will allow users to browse a library of fonts in the admin, similar to managing media. It will not be dependent on the theme that is activated but will be a library that is extensible for plugin developers.
\n\n\n\nThe discussion regarding 2024 releases is still ongoing in the comments of the post. WordPress users may also hear more about what’s coming in the next year during Matt Mullenwg’s State of the Word address, which will be delivered live from Madrid on December 11, 2023.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Nov 2023 19:14:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"Do The Woo Community: WP 6.4, Black Friday, Tumblr, Free Plugins and Woo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77953\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://dothewoo.io/wp-6-4-black-friday-tumblr-free-plugins-and-woo/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:391:\"BobWP mentioning WordPress 6.4, Black Friday deals, Tumblr in the red, free vs. premium plugins and the Woo brand.
\n>> The post WP 6.4, Black Friday, Tumblr, Free Plugins and Woo appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Nov 2023 13:06:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"WPTavern: Wordfence Launches Bug Bounty Program\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151186\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com/wordfence-launches-bug-bounty-program\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8389:\"Wordfence launched a bug bounty program today to provide financial incentive for security researchers reporting high risk vulnerabilities to the company’s program.
\n\n\n\nAfter researchers disclose vulnerabilities to Wordfence, the company triages them and confidentially discloses them to the vendors to fix. When the fix is released, the vulnerability will be included in Wordfence’s public database, which is free to access, following a responsible disclosure policy.
\n\n\n\n“There is no cap on the rewards an individual researcher can earn, and every single in-scope vulnerability received via our submissions process earns a reward bounty,” Wordfence security analyst Chloe Chamberland said.
\n\n\n\nWordfence will reward researchers who discover vulnerabilities in plugins and themes with 50,000+ active installations. A few examples of the payouts include the following:
\n\n\n\n“Our Bug Bounty Program has been designed to have the greatest positive impact on the security of the WordPress ecosystem,” Chamberland said. “Rewards are not earned by bulk hunting for vulnerabilities with minimal impact and earning a place on a leaderboard, but rather, they are based on active install counts, the criticality of the vulnerability, the ease of exploitation, and the prevalence of the vulnerability type.”
\n\n\n\nWordfence’s bug bounty program launch was clearly vying for competitive positioning by indirectly calling out Patchstack, which operates its program on a leaderboard system where only the top researchers get paid. There are a few notable differences, where some bounties are awarded by discretion but most individual bounties are for the highest score in various categories:
\n\n\n\n\n\n\n\n\nPatchstack guarantees a monthly prize pool of at least $2425 (the lowest possible prize pool). Patchstack Alliance member who will collect the most points for a particular month from their submitted reports will get the $650 bounty, the second place will get $350 and the third will get $250.
\n\n\n\nWe have extra bounties (single bounties) for reporting the vulnerability with the highest CVSS ver. 3.1 base score; the highest active install count; and for reporting a group of components affected by the same vulnerability.
\n\n\n\nPatchstack can reward individual Patchstack Alliance members at their discretion based on the overall impact of the vulnerabilities they discover.
\n
Wordfence is taking a different approach in paying for every vulnerability reported within the scope identified by the program.
\n\n\n\nResearchers in the WordPress ecosystem should familiarize themselves with the various bug bounty programs and determine the best avenue for their disclosures. Some plugins and companies, such as Elementor, Brainstorm Force, Automattic, Castos, and WP Engine, have their own bug bounty programs, with a range of different payouts.
\n\n\n\n“We pay more per vulnerability and we pay for every valid vulnerability submitted,” Wordfence CEO Mark Maunder said. “We feel this is the only fair way to do it because gamification of a vulnerability program is like having employees who all work, but only those at the top of the leaderboard get paid. If you submit a valid vulnerability, you should get paid for your work.”
\n\n\n\nMaunder contends that the wrong incentives are driving down the quality of the research submitted.
\n\n\n\n“There are an extremely high number of low risk and low quality vulnerabilities being submitted to databases like Patchstack,” he said. “Vulnerabilities that involve a Cross-Site Request Forgery are an example of this. The incentives we are seeing out there encourage researchers to generate a a high volume of low risk vulnerabilities to get rewarded. These high numbers are then used to market security products.”
\n\n\n\nMaunder said Wordfence has structured its program around shifting the incentives to reward research into high risk vulnerabilities, instead of ramping up the marketing metrics for a particular vulnerability database.
\n\n\n\n“A high volume of low risk vulnerabilities in any particular database harms the industry because it creates work for other organizations who have to integrate this data, but for the most part it is useless noise that we are forced to sift through, rather than representing any real-world risk to the user community,” Maunder said.
\n\n\n\nPatchstack CEO Oliver Sild responded to these claims with data he says demonstrates that Wordfence is also responsible for producing a high volume of low risk vulnerability CVE’s.
\n\n\n\n“WordFence as a CNA actually produces lower risk vulnerability CVE’s in average compared to all 3 CNA’s in the WordPress space,” Sild said.
\n\n\n\nCVE’s with CVSS equal or higher than 5 (2023)
\n\n\n\nCVE’s with CVSS equal or higher than 7 (2023)
\n\n\n\nCVE’s with CVSS equal or higher than 8 (2023)
\n\n\n\nCVE’s with CVSS equal or higher than 9 (2023)
\n\n\n\n“WordFence does indeed on average assign highest % of CVSS 9+ CVE’s (though, they are also the smallest CNA of all three), but the high CVSS alone doesn’t determine wether the vulnerability will become exploited and the reality is that vulnerabilities that are being actively exploited in the WordPress ecosystem often have lower CVSS scores,” Sild said.
\n\n\n\n“Also, keep in mind that we at Patchstack have almost 2x higher volume of new vulnerability reports coming in (more than WPscan and WordFence combined), so obviously this also lowers the average for us on the edge scores.”
\n\n\n\nAs the newcomer to the group of WordPress companies offering bug bounties, Wordfence is entering the market with the intention of attracting more reports through additional bonuses (10% for the first 6 months) and a bonus structure that rewards chaining multiple vulnerabilities together, thorough documentation, and other extra efforts.
\n\n\n\nNot every author of a popular plugin or theme can afford to offer their own bug bounty program, and this is where security companies are stepping in to fill in the gaps. More competition across companies for high quality research can only be good for WordPress users, as it provides more incentive for securing the ecosystem and will potentially attract more skilled researchers. The bug bounty programs will likely evolve over time as companies refine them to provide the best value for original research.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Nov 2023 02:48:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:21;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"Do The Woo Community: The Challenges of Hosting Difficult Woo Sites Tom Fanelli and Ben Gabler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77947\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"https://dothewoo.io/the-challenges-of-hosting-difficult-woo-sites-tom-fanelli-and-ben-gabler/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:460:\"Guests Ben Gabler from Rocket.net and Tom Fanelli from Convesio talk scaling, plugins and coding standards when it comes to performance.
\n>> The post The Challenges of Hosting Difficult Woo Sites Tom Fanelli and Ben Gabler appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 13:15:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: WordPress 6.4.1 Fixes a Critical cURL/Requests Bug\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151163\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wptavern.com/wordpress-6-4-1-fixes-a-critical-curl-requests-bug\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4466:\"WordPress contributors have worked quickly over the past 24 hours to prepare a 6.4.1 maintenance release after a critical bug emerged from a change in the Requests library, causing problems with updates on servers running older versions of cURL.
\n\n\n\nHosting companies began reporting widespread impact of the bug. Tom Sommer, from one of Denmark’s largest hosting companies, filed a GitHub issue outlining how the cURL timeouts were affecting sites:
\n\n\n\nError: RuntimeException: Failed to get url \'https://api.wordpress.org/core/version-check/1.7/?locale=en_US\': cURL error 28: Operation timed out after 10000 milliseconds with 807 out of -1 bytes received.
REST API response: (http_request_failed) cURL error 28: Operation timed out after 10005 milliseconds with XXX out of XXX bytes received”
The issue became a top priority as it wasn’t clear how it would be possible for users to receive an update.
\n\n\n\n“Even if you fix this now the issue prevents any future auto-upgrade to a 6.4.1, since it breaks Curl requests, so the only way for people to update would be manually,” Sommer said. “The longer you wait, the bigger the problem will become.”
\n\n\n\nNexcess reported tens of thousands of sites being affected by the bug. The issue was beyond what most users would be able to manually patch on their own, relegating hosts to figure out how to update their customers.
\n\n\n\n“All my websites locked after updating to WordPress 6.4,” Javier Martín González reported. “The ones without updates are working normally.”
\n\n\n\nThe bug was also reported to be causing causing potential Stripe API, WP-Admin, and performance issues.
\n\n\n\nLiquid Web/Nexcess product manager Tiffany Bridge summarized how this problem emerged:
\n\n\n\n\n\n\n\n\nIt looks like:
\n\n\n\n\n
\n- Someone reported a bug having to do with an interaction between his Intrusion Protection System and WordPress
\n\n\n\n- They then submitted their own patch to WordPress
\n\n\n\n- The project lead for that area asked the submitter to write tests, which he did not do
\n\n\n\n- Then they merged the PR anyway, despite the lack of tests
\n\n\n\n- Meanwhile hosts are all going to have to revert that change ourselves on our own fleets so that our customers can still have little things like core and plugin updates if we are running an affected cURL version. (7.29 confirmed, there may be others)
\n
WordPress core contributors will have to get to the bottom of how this bug was allowed through, via a postmortem or other discussion to prevent this from happening on such a large scale in the future.
\n\n\n\nWordPress 6.4.1 updates the Requests library from version 2.0.8
to 2.0.9
. as a hotfix release to mitigate the issue. It reverts the problematic change. Version 6.4.1 also includes fixes for three other separate issues. Automatic updates shipped out this evening for anyone with sites that support automatic background updates.
WordPress’ Performance team is proposing merging Performant Translations into core in time for the upcoming WordPress 6.5 release. After an in-depth performance analysis earlier this year revealed that translations can significantly impact server response times, the team discussed various solutions and landed on one that requires no configuration from users. More than 2,000 WordPress sites have tested it through the Performant Translations feature plugin, after it was released in August.
\n\n\n\nPerformance Team contributor Pascal Birchler, who penned the proposal to merge the plugin into core, explained how it speeds up sites using translations:
\n\n\n\n\n\n\n\n\nPerformant Translations is powered by a new, lightweight i18n library that is faster at loading binary MO files and uses less memory. It even supports loading multiple locales at the same time, which makes locale switching faster. In addition to that, it supports translations contained in PHP files, avoiding a binary file format and leveraging OPCache if available. If an MO translation file has a corresponding PHP file, the latter will be loaded instead, making things even faster and use even less memory.
\n
Birchler also published some compelling benchmarks demonstrating the plugin’s ability to reduce memory usage and decrease load time:
\n\n\n\n\n\n\n\nLocale | Scenario | Memory Usage | Load Time |
---|---|---|---|
en_US | Default | 15 MB | 159 ms |
de_DE | Default | 29 MB | 217 ms |
de_DE | Performant Translations | 17 MB | 166 ms |
The Performance team has opened a ticket for merging the plugin into WordPress 6.5. Core committer Felix Arntz marked it as a high priority for the next release “due to the significant estimated impact this will have for localized sites’ performance.” The improvements stand to have a positive impact on the majority of WordPress sites (more than 50%) that are using translations.
\n\n\n\nWordPress 6.5 is expected in late March 2024. Getting merged this early in the release cycle would give Performant Translations the time it needs to be more widely tested and ready to go. Users who don’t want to wait until next year to get these reported performance improvements can install the plugin in the meantime.
\n\n\n\n“The Performant Translations plugin will continue to be maintained even after a core merge to build on top of the core solution with a distinct additional feature,” Birchler said. “As is already the case today, the plugin will automatically convert any MO files to PHP files if a PHP file does not currently exist. This is useful for sites where translations are not coming from translate.wordpress.org or only exist locally on that server.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 02:34:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"WordPress.org blog: WordPress 6.4.1 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16332\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2023/11/wordpress-6-4-1-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5868:\"This minor release features four bug fixes. You can review a summary of the maintenance updates in this release by reading the Release Candidate announcement or view the list of tickets on Trac.
\n\n\n\nWordPress 6.4.1 is a short-cycle release. If you have sites that support automatic background updates, the update process will begin automatically. If your site does not update automatically, you can also update from your Dashboard.
\n\n\n\nYou can download WordPress 6.4.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.
\n\n\n\nFor more information on this release, please visit the HelpHub site.
\n\n\n\nThis release was led by Aaron Jorbin and Tonya Mork. Thank you to everyone who tested the RC and 6.4.1, and raised reports.
\n\n\n\nWordPress 6.4.1 would not have been possible without the contributions of the following people. Their quick and concerted coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\n\n@afragen @clorith @desrosj @pbiron @schlessera @azaozz @davidbaumwald @tomsommer @nexflaszlo @howdy_mcgee @baxbridge @earnjam @timothyblynjacobs @johnbillion @flixos90 @joedolson @jeffpaul @zunaid321 @courane01 @audrasjb @tacoverdo @ironprogrammer @webcommsat @otto42 @barry @chanthaboune @rajinsharwar @aaroncampbell @peterwilsoncc @anandau14 @iandunn @matthewjho @coffee2code @boogah @jason_the_adams @joemcgill @johnjamesjacoby @jrf @renehermi @dlh @mukesh27 @sumitbagthariya16 @starbuck @sergeybiryukov @ravipatel
\n\n\n\nTo get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core channel. Need help? Check out the Core Contributor Handbook.
\n\n\n\nThanks to @jeffpaul and @webcommsat for proofreading.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 01:45:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:25;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"BuddyPress: BuddyPress 12.0.0-beta4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=331850\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"https://buddypress.org/2023/11/buddypress-12-0-0-beta4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3631:\"Hello BuddyPress contributors!
\n\n\n\nIf you haven’t tested our 3 previous beta releases, here’s a fresh opportunity to join the 28 contributors who helped build 12.0.0 so far. Whether you’re a new, regular or advanced user, a theme designer or a plugin author: we really need you to beta test our next major release, please contribute!
\n\n\n\n \n\n\n\n\n\n\n\n12.0.0 will introduce the BP Rewrites API overhauling the way that BuddyPress builds and parses URLs as well as a new community visibility feature. Learn more about these changes by reading the beta1 announcement post.
\n\n\n\n\n\n\n\nWe’ve fixed a dozen bugs and added new developer documentation pages explaining important changes introduced in 12.0.0:
\n\n\n\nWe also updated the 12.0.0 release schedule and delayed it a bit to make it as great as possible. It’s now slated to be released December 6. Please, help us meet this new deadline by testing 12.0.0 as thoroughly as possible .
\n\n\n\nYou can test BuddyPress 12.0.0-beta4 in 4 ways :
\n\n\n\nsvn co https://buddypress.svn.wordpress.org/trunk/
git clone git://buddypress.git.wordpress.org/
If you find something weird, please report it on BuddyPress Trac, post a reply to this support topic or get in touch with us on our WordPress.org Slack channel.
\n\n\n\nThanks in advance for your contributions
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 18:44:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"WPTavern: #98 – Marieke van de Rakt on Uniting the WordPress Community for a Stronger Future\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=151132\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wptavern.com/podcast/98-marieke-van-de-rakt-on-uniting-the-wordpress-community-for-a-stronger-future\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:47833:\"Transcript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.
\n\n\n\nJukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case, how the WordPress community can stay United.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast, player of choice. Or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you, and hopefully get you, or your idea, featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox and use the form there.
\n\n\n\nSo on the podcast today, we have Marieke van de Rakt. Marieke was one of the co-founders of Yoast. She left Yoast entirely in May 2023, and is now focusing her energy on her investment company, Emilia Capital, together with Joost de Valk. This is investing in various WordPress brands and ventures.
\n\n\n\nMarieke shares her insights on the current state of the WordPress community and the challenges it faces. She highlights the growing divide between those who prioritize community orientated contributions, and those purely driven by commercial interests. She expresses her concerns about the potential consequences if this division continues to widen, including the potential growth of other content management systems.
\n\n\n\nThis issue is certainly worthy of attention, and whilst it might seem that the two sides of this debate irreconcilable, Marieke offers potential solutions to these challenges. She emphasizes the need for the WordPress community to unite and compete against other proprietary platforms. She suggests a more cohesive marketing strategy and collaboration to strengthen the community. She advocates for an official recognition system to celebrate and promote companies actively contributing to WordPress. Although what this might look like is very much up for debate.
\n\n\n\nWe also hear about Marieke’s experiences at Yoast, and how they contributed to WordPress over the years, particularly during the development of Gutenberg. She discusses the importance of open source collaboration and the need for companies to align with the project’s direction, for the benefit of the wider community.
\n\n\n\nWe also discussed the potential negative outcomes if WordPress becomes more commercialized, leading to a divide in the community, a divide which might be difficult to undo.
\n\n\n\nWe end by chatting about the importance of WordPress in democratizing publishing, it’s benefits for the internet and the planet, and how, from Marieke’s point of view, WordPress is too important to fail.
\n\n\n\nIf you’re keen to see the WordPress community grow, and have an interest in how internal divisions can be avoided and resolved, this episode is for you.
\n\n\n\nIf you’re interested in finding out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast, where you’ll find all the other episodes.
\n\n\n\nAnd so without further delay, I bring you Marieke van de Rakt.
\n\n\n\nI am joined on the podcast today by Marieke van de Rakt. Hello.
\n\n\n\n[00:04:06] Marieke van de Rakt: Hello! Very nice to be here.
\n\n\n\n[00:04:08] Nathan Wrigley: Did I get your name vaguely right?
\n\n\n\n[00:04:11] Marieke van de Rakt: I think you did a really good job. It sounded a bit like I’m a Viking, so a bit more Scandinavian but it was correct. Yeah.
\n\n\n\n[00:04:20] Nathan Wrigley: I will take that. If you don’t know Marieke, honestly where have you been for the last couple of decades? Marieke was the driving force, along with her husband, of a very, very famous WordPress company, Yoast. Things have changed in the last year or so. So I wonder, for the purposes of this podcast, which is obviously a WordPress based podcast. I know it’s a bit of an uninteresting question perhaps, but for those people who don’t know who you are, could you just give us your potted history, your biography, if you like?
\n\n\n\n[00:04:47] Marieke van de Rakt: My biography, yes of course. So I am Marieke, Marieke van de Rakt. I am, I don’t know what I am, I am an entrepreneur and an investor now. So we’ve been running Yoast since, I’ve been with the company I think since 2013, so about 10 years. And then in 2021 we sold to Newfold Digital. And then like you just said, I left Yoast I think in May of this year.
\n\n\n\nBut before leaving, we already started investing in a number of WordPress brands, so Atarim, Equalize Digital, a Dutch company called wildcloud, really, really good. Also, outside the WordPress space, we have some investments and we’re now helping those investments grow. And we’re also having some new ideas of products and things we can do in the WordPress world. So we’ll stay in the community forever.
\n\n\n\n[00:05:37] Nathan Wrigley: Oh nice. That’s great. Do you feel like your foot has come off the pedal since May, or has your foot gone on the pedal since May? Are you busier than ever or, do you have a little bit more free time for the things that you enjoy outside of work?
\n\n\n\n[00:05:50] Marieke van de Rakt: I do think that I have a little bit more time, but I’m also full with ideas. I have to be very careful because I wanted to work for four days a week, but I’m already working five again. But that’s all things that I like. So I think it’s better and it’s less stressful than it used to be, because I don’t have to lead a team. We do have a small team now, but it’s only three or four people, and I know them very well so they’re not difficult people. It’s easier than it used to be.
\n\n\n\n[00:06:18] Nathan Wrigley: Well that’s good to hear. The reason that we’ve got you on the podcast today is not to talk about any of those things, but I think it was important to paint the picture of who you are and how long been in the WordPress space. Because what we’re talking about, I guess requires a fairly large telescope, staring into the history of WordPress. Because without that backstory, without that familiarity with the community over decades basically, then you wouldn’t really have the authority to write this.
\n\n\n\nBut I’m going to point listeners to this podcast to a poststatus.com post which Marieke wrote. It was on the 28th of September, so Google could be a friend here. And it was called Two Worlds of WordPress. Now just to paraphrase it, you could obviously do that, but I’ll just give it a go. Essentially, in that piece you were talking about the fact that, over the years, WordPress has grown in two seemingly contradictory directions.
\n\n\n\nOn the one hand, well you’ve called them different sides, different faces. On the one hand, you’ve got the community side. So the people who are in, as you describe it, enthusiastic about open source, contributing to the project and the events and all of that.
\n\n\n\nAnd then on the other side, you’ve got the people who are business orientated, and in the back of their minds is using WordPress as a commercial vehicle, a way to generate revenue.
\n\n\n\nNow over the course of WordPress’s history, the relationship of those two things has changed. And I feel that decades ago it was really clear that WordPress was much more community and much less business. But over the last decade or so it’s grown more and more business orientated. And your fear is that these two camps, these two faces, different sides, they’re growing apart to the point where they can’t even see what the other side is doing. There’s no point of communication between them. And in a way it’s tearing the community apart. Is that a fair summation of it?
\n\n\n\n[00:08:08] Marieke van de Rakt: Yeah I think so. That’s what I’m afraid of. Because I think both worlds have a necessity to exist. So because the business side of WordPress grew so quickly, it also meant that there was a lot of opportunity for people to make money out of WordPress.
\n\n\n\nSo we did that all together. But it’s an open source project. So we need people to contribute to it, otherwise we’ll lose our momentum and we’ll lose the fact that we are the biggest CMS out there. So what we ideally want is that all of those businesses that make money out of WordPress also pay something back to the community. And that’s not always happening. And I know that a lot of businesses are struggling because they don’t know how and then that is hard, but that’s what I’m worried about, yeah.
\n\n\n\n[00:08:53] Nathan Wrigley: Do you have some sort of intuition? Is there some sort of feeling that you get when you are dealing with these different sides? So as an example, when you turn up to a WordPress event and you meet somebody who is just purely in it for the contributing value of it. Do you have a different relationship with those people than you do with the people who have a only a commercial side to it? I just wonder if you’ve got any intuitions as to, do any alarm bells go off, or is there anything different about the way you deal with those different sides?
\n\n\n\n[00:09:22] Marieke van de Rakt: Yes. I think if you meet that kind of contributor that’s only in there for the open source, that’s a hero. That’s nothing short of a hero, because he’s there for something bigger than himself. He’s there to contribute to something that is bigger. And the business side, if you’re only in it for the business side, I’m always a little bit on edge. So I think that you shouldn’t do that.
\n\n\n\nBut I also think that we should reward businesses that are giving back more. And it’s very hard to be a business that gives back and gives back and gives back, and doesn’t really get anything in return. So I know this Dutch company, we can name them, Level Level. But it’s not, especially in the Netherlands, it’s not for them immediately, that doesn’t pay them anything else except for we’re the experts.
\n\n\n\nBut perhaps if we, as the WordPress world, also shout about, but they’re the experts, they’re on every WordCamp in the Netherlands, they’re on WordCamp Europe, they come there with their entire people, all the people that work there, their team.
\n\n\n\nMaybe those companies need a bigger shout out because they’re the ones that do contribute and, I don’t know, that could be some sort of solution. That we celebrate those people and companies that dedicate a lot of their time towards WordPress.
\n\n\n\n[00:10:39] Nathan Wrigley: The fact that you’ve written this article, at least the implication of it is that you fear that in the future, if the current trajectory carries on, there’s going to be a moment where things break irrevocably. So the two sides grow so far apart that they genuinely have no point of reference to each other anymore.
\n\n\n\nAnd really the philanthropic effort of WordPress would be lost somewhere in that. The whole project would fail. I can imagine a scenario where people, contributors who are just in it for pushing the WordPress project forward, they might have a chip on their shoulder saying, well you know, there’s all those people over there making millions of dollars for their company. I’m not making anything out of it, so I’m not going bother.
\n\n\n\nAnd then the other side, well we make millions of dollars out of this project. Why would we want to waste our time contributing to it? And you just get this echo chamber. One side chatting and confirming their own confirmation bias over here, and the other side doing the exact same but in their little echo chamber.
\n\n\n\nSo is that a fear? That you think that it literally will get to the point where the project itself is broken, because there is no, in air quotes, community anymore.
\n\n\n\n[00:11:44] Marieke van de Rakt: I think then other CMSs will grow, because of our division between those two worlds, will make a smaller and other CMSs will grow. Because, well, we care about open source, a lot of people don’t, and they don’t choose WordPress just because it’s open source. They choose WordPress because it used to be the best. I don’t know if it’s the best anymore but it used to be the best. So if we look at marketing, all these big companies, so the big hosts, all market their own brand. So GoDaddy markets for GoDaddy. Bluehost markets for Bluehost. SiteGround markets for SiteGround.
\n\n\n\nBut they all do WordPress. So perhaps we should also market WordPress as a system more, we don’t do that. They’re competing with each other, and they’re competing with companies like Wix and Shopify. But I think as a whole of the WordPress community we should be competing with each other against Shopify and Wix. And we don’t do that enough. We should join forces more. Also on the business side of things.
\n\n\n\n[00:12:45] Nathan Wrigley: I think that’s really interesting because, I think only people who are deeply into WordPress in the same way that you and I both are, you know, we probably think about WordPress more than is healthy for us.
\n\n\n\nBut we’re really obsessed by it, so we go out searching for the news and we look for the companies that are, in air quotes, doing the right thing. Until we read the posts that come out on an annual basis saying who has contributed, which companies have contributed and so on. But most people using WordPress probably won’t have any idea about that because it’s not really applauded publicly, is it?
\n\n\n\nI think we should probably call out Yoast at the moment and discuss what you decided to do, because that was a really good example. So we’re recording this in October 2023, obviously caveat emptor, I don’t know what will happen in the future in terms of WordPress’s contribution. But what was your stated goal? How did you want to commit time within the company, resources within the company? Because obviously that would be a model that you think worked quite well.
\n\n\n\n[00:13:44] Marieke van de Rakt: We have the Five for the Future working quite well. At Yoast we did that before that even was a thing. But I remember, and this was WordCamp Europe, the first one in 2013, yes it was in 2013 in Leiden. And Yoast did a talk and I prepared that talk. It was about open source and about how it’s okay to make money out of it.
\n\n\n\nAnd that was this huge thing. People were, no you’re not allowed to make money out of. We were allowed to make money out of themes, because they were all unique and you wanted to be unique. But on plugins, everybody needed a plugin, it was frowned upon. But we, or Yoast back then, had I think 2,000,000 installs, and you get so many questions off people. You can’t maintain a plugin and make sure it’s secure, and come up with new features and test that, that’s impossible to do without making money.
\n\n\n\nSo we started out, I think we were the first to start out with a freemium model thing, and that was frowned upon for a few years. And then everybody started doing that, and they went much further than we did. So we first were very reluctant to go to that you buy something and that’s an immediately you buy it for a couple of years, unless you actively say no I don’t want it anymore, you have to call out. We just gave you for one year and then you have to manually renew because we didn’t want anybody to feel like, oh no I’m stuck to it.
\n\n\n\nThis all changed but we were reluctant in that kind of way. And we saw that we were just. So we weren’t perhaps the first most commercial, but then so many companies came in, mostly outside of the WordPress world who did it differently.
\n\n\n\nAnd at the end when we sold Yoast I felt really naive because I got a little peek of what it’s like to be on the really business side after we sold Yoast. We didn’t know, we didn’t know that there were all kinds of meetings and people making deals about who installs what, and we didn’t do that at Yoast, we just built the best product and contributed a lot to WordPress. Part because we believed in it, but also part because it just makes sense.
\n\n\n\nWhen Gutenberg was announced, that was a major implication for the Yoast plugin. We had to be involved otherwise it would have been really bad for our product. So that’s something. Even if you’re not like a WordPress enthusiastic like we are, just because it will allow you to see where the project is going, that’s a good reason to contribute, that alone. So it also makes business sense to do that.
\n\n\n\n[00:16:19] Nathan Wrigley: Yeah so, what specifically was the sort of, the things that you did in Yoast? What were the boots that you put on the ground, the hours that you allocated? Now it may be that it was a movable feast and that each year was different, but broadly speaking, typically, what was the kind of commitment that you were prepared to make? That could be in terms of hours, finance, whatever, however you want to take it.
\n\n\n\n[00:16:41] Marieke van de Rakt: So I think Joost personally did a day a week for ages. And we had entire teams, community teams that did nothing else than sponsoring WordCamps, organising WordCamps, those kinds of stuff. And then we had a few during Gutenberg, we had, I think two full time developers on it.
\n\n\n\nAnd afterwards we, Yoast still has, a core contributor team. So there were like four or five contributors that worked solely on the project. I think Yoast did a little over 5% in terms of hours and money, but not even that much. In the beginning it was, I think in the beginning we did 20% but when we grew bigger, I think 5% to 10%, you can do a lot with 5% to 10% of a bigger company.
\n\n\n\n[00:17:24] Nathan Wrigley: First of all, the reason you’re doing all of this, my guess is it wasn’t to be recognised publicly. That would be nice, but that wasn’t the primary motive. It was to foster a good relationship with the community to promote the whole project itself.
\n\n\n\nBut there must be some side of that equation where you’re thinking, we’re putting all this time in, there seems to be a lot of companies out in the space who are probably more profitable than us, who are not putting an equal amount of time in, and we don’t seem to be getting much in the way of recognition.
\n\n\n\nSo really what I’m asking is, did you feel that the recognition piece was something that was lacking? Maybe something that ought to be considered in the future, some sort of an an official badge, some way of displaying, look this company did this categorically, we’re very proud of them. Let’s just talk about recognition.
\n\n\n\n[00:18:17] Marieke van de Rakt: Within the core of the WordPress community we were recognised, people saw that. So that’s good. But outside of that first bubble people have no idea. And then a WordPress stamp of approval, and I don’t know how you should come up with some things. Oh also a company like Level Level who does a lot, if they get a WordPress stamp of approval that would help them so much with selling websites because they build websites.
\n\n\n\nIf we would have a WordPress stamp of approval, not even this is the best SEO plugin for Yoast, but this is they contribute to WordPress, they have their things in order, that would help a lot.
\n\n\n\nBut we don’t have something like that, and I don’t know how to set something like that up. But I do think that would help. Because we really believed in the open source thought. So not even I like WordPress, but the fact that you can build something together, and you don’t have to come up with an, event the wheel over and over again, that just makes sense for whole world.
\n\n\n\nSo I’m a strong believer in open source and in working together without having all these, I don’t know, without talking about, this is mine and you shouldn’t have this. That’s just a bad way of running the world. So I think that’s something we strongly believe in.
\n\n\n\n[00:19:34] Nathan Wrigley: I think having some sort of accreditation system, the merits of that would be good, but I can equally see how the actual organisation of that would be fraught with problems. Because no doubt there’d be companies who, I don’t know, just didn’t quite get out of that accreditation what they were hoping for, and yet they’d clearly put in some time. And so you’d have to have bodies on the ground making sure that accreditation was fair and meritorious and everybody got what they deserved.
\n\n\n\nSo that does seem like a bit of a minefield to go down. But then the project prioritizes all sorts of things that don’t have a profit motive, and maybe something like that, an accreditation system could be something worthwhile.
\n\n\n\nIt just occurs to me that if I go around WordPress company websites, you don’t see that, do you? You don’t see them shouting on the hero section of their web page, we have contributed such and such an amount of hours. It’s all about the product that they’ve got because they’re selling directly to end, you know, end users.
\n\n\n\n[00:20:33] Marieke van de Rakt: And they don’t understand that. But I think as a community, we should make people more aware. It’s like buying or working with open source software is like being a vegetarian, you’re just doing the right thing. So we should talk about that more, because it’s the only way I think we can move forward, and come up with new knowledge, everybody should do open source.
\n\n\n\nSo every government website should be made out of open source software. It can be really, get mad if they spend money on proprietary systems. They should spend money on, I don’t know, health and education and don’t spend it on a very expensive software, because there’s software that’s really good and we should use that. But I think as a community, perhaps we should talk more about why open source is so awesome.
\n\n\n\n[00:21:18] Nathan Wrigley: Yeah it really is tricky, but I have this intuition that something like this would be a good idea, despite the fact that it would be almost impossible I think to manage, and it would be very difficult to decide who got what.
\n\n\n\nBut in your conversations over the years working at Yoast, okay let’s imagine that there’s somebody listening to this podcast who desperately wants to contribute, but feels that they don’t have the bandwidth to do that. They’re not profitable enough, they don’t have enough hours to make that possible. So this question is directed to you but talking to them, if you know what I mean.
\n\n\n\nSo when you were working at Yoast, did you get an impression that your contributions to the project led to you being profitable? Were there certain customers of yours who came to you because you were working so hard for the project as a whole, and not just because you had a superior product?
\n\n\n\n[00:22:12] Marieke van de Rakt: Not directly, but I’m convinced that indirectly, yes. So being on all those events, having Taco, having Taco just being everywhere and organising, and talking to people helps with getting those core community people talking about you. And when they talk about you to all the other people, it just, it’s like a pyramid that goes down.
\n\n\n\nSo we never did any influencer marketing, we did WordPress contribution. And I think it’s about the same thing, because you just show up at contributor days or at events and you talk to people. And when you do those kinds of things, you also talk about your product and people think you are nice because you’re helping. Not everybody thinks you’re nice, so you always have that.
\n\n\n\nBut I think that’s just WordPress influencer marketing. I even say that to people we invest in. I said, you should do WordPress influencer marketing. That means contributing to the project and doing your best. And that’s the way the people in the community will get to know you and see you, and they’ll also talk about your product then.
\n\n\n\n[00:23:20] Nathan Wrigley: Yeah, there’s no direct correlation between the amount that you put in and the success, if you like, of the commercial side at least of the plugin. But there is some sort of fuzzy appreciation on your behalf, that there is a connection even though you can’t quite grab hold of what that is.
\n\n\n\nBut the more that you put in, the more recognition you’ve got, the more the brand became known and probably the by product of that is that there would be sales from that. I should point out that Marieke isn’t just doing this one piece, we’ve talked about this two worlds of WordPress piece. It’s going to be a regular feature on Post Status.
\n\n\n\n[00:23:54] Marieke van de Rakt: Yeah. So I’m just telling stories from both worlds and sometimes, well no, there’s always one side, sometimes two, that I think, I hope, that’ll help to get those worlds to understand each other. That’s the only thing I hope.
\n\n\n\n[00:24:10] Nathan Wrigley: The broad overarching idea behind all of the posts that you’re going to be putting on Post Status is about getting the commercial side and the non commercial side, to get them talking a bit more. And to get, because obviously, Post Status has this enormous reach and that would be a really superb place to do it.
\n\n\n\nOne of the pieces that you wrote was called, On people breaking up with WordPress. And I’m sure I don’t need to explain to everybody what that means, but you can guess. It was all about how people decide that they want to move away from the project.
\n\n\n\nBut one of the things that you wrote in there, I’m curious as to how this fits with everything that you’ve just been talking about. You wrote, and I’m going to quote, I strongly believe that all contributors, so developers, marketers, organisers, et cetera, to the WordPress project, need to be financially compensated. Next to that, I think it would help if they feel valued and important, and that they’ll be able to be productive.
\n\n\n\nLet’s talk about the first bit, the financial compensation, because I don’t think anybody would disagree with that, would they? Everybody would love to think that, you know, you contribute something to WordPress, you’ve got something, you get return, you put an hour in, you get some finance back.
\n\n\n\nHow do you see that working in reality? Especially if you’re, I don’t know, you’re working for a plugin company, let’s say, and there’s not a lot of money sloshing around, you’ve got very little reserves. How would you like to see this happen? Are you talking about like a pool that big companies who are successful put money into, and then if you like that can be dipped into by people from around the community. What were you thinking there?
\n\n\n\n[00:25:44] Marieke van de Rakt: That would be best. I think the most money in the WordPress world is made by hosting companies. So they have large margins. If they don’t want to hire people themselves then they should invest in people that want to contribute their time. And I think in the beginning of WordPress it was led by volunteers, but I do think that nowadays there is so much money being made that we should be able, together with all of us, to at least compensate for those hours that put in.
\n\n\n\nAnd that’s probably not the highest salary but people should be compensated a little. And I know still that there are main organisers for WordCamps that do that entirely in their free time. And I think that’s just wrong. There’s too much money being made by big companies, and they should pitch in together to make sure that the events are led by people that are also paid for their contributions.
\n\n\n\n[00:26:43] Nathan Wrigley: That seems like a really credible way of short circuiting the accreditation thing that we were talking about earlier. We can prove categorically that we committed 5 percent of something. Whether that’s 5 percent of time across our employee distribution. Or whether that’s 5 percent of the finance that we had available to us in this year.
\n\n\n\nAnd we’re talking about this 5 percent because, I don’t know if you know dear listener, there is this concept of Five for the Future where exactly this would happen. But there’s no way of demonstrating to the world that you did it.
\n\n\n\nSo just that simple metric of, we did and we’ve certified that we did Five for the Future, maybe that alone would be a fairly, it’s a fairly blunt instrument, but at least it would be some way of the company’s getting that recognition back. The badge could go on the website, so that people who are into the community could fully understand, okay, there it is. They did their 5 percent contribution for whatever it was. That might be a fairly swift and easy way, well not easy, but a fairly quick way of doing it.
\n\n\n\n[00:27:44] Marieke van de Rakt: It could also be a way of getting those worlds together. I think that’s the start. I just think there’s too much money being made by big companies to have people volunteer and have a hard time. If you’re an organiser of a big WordCamp, which is like WordCamp Europe is extremely important that it exists for businesses. Those businesses should also be like, I have to make sure that this continues.
\n\n\n\nAnd that means that those people need to be compensated because they are usually working for themselves. But if you build websites and you organise an event, you probably build less websites if you’re like busy organising WordCamp Europe. I think the WordPress world has been, we used to do it with all volunteers and I don’t think that we can do this anymore.
\n\n\n\n[00:28:30] Nathan Wrigley: When an event like WordCamp Europe is put on, the level of commitment from some, again it could be any WordCamp, but I just pluck WordCamp Europe out of thin air. Because, well it’s so big and because of that there’s so many technicalities. And having interviewed quite a few of the people who were really involved in those projects, they are genuinely giving up weeks and weeks of their year. And they’re doing it out of the goodness of their heart.
\n\n\n\nNow in some cases it may be that they’ve got some kind of sponsorship somewhere, maybe their company has allowed them to have that time. But I have a strong intuition that many of them are literally taking it almost like annual leave.
\n\n\n\nAnd so it’s exactly what you said. It’s not just that they’re committing time, but they are committing time which they can’t get back in their own business. So it’s a double whammy. They’re not getting paid for that contribution, but also they’re losing money so it’s going wrong in both directions.
\n\n\n\nI don’t know how that would work, but it does strike me that badge, that 5 percent commitment being pulled somewhere, some independent organisation which could then give that out seems like a good idea.
\n\n\n\nIf we’re going to accredit people, now this could be controversial, if we’re going to credit people, do we go the other way? Do we go in the direction of calling out companies that don’t do it? Is that something which the community should ever be involved in? My intuition says no, but that’s just my intuition, what do you think?
\n\n\n\n[00:29:54] Marieke van de Rakt: My intuition also says no, because it’s a very negative thing to do. And it’s hard as well because, especially like in the plugin businesses you know, but in the website builder businesses, a lot of websites builders will not even know about Five for the Future or anything like that. I wouldn’t call people out on not contributing but perhaps other people will.
\n\n\n\n[00:30:17] Nathan Wrigley: I’m sure they will, because people who are not bound to any particular company, they might have stronger feelings about that and they can do that in their own way, can’t they? So really we’re painting a picture of, if you do the right thing there should be a mechanism for you to be able to certify that you have done the right thing, and have some sort of badge of honor to be able to display that and explain.
\n\n\n\nWhat are your feelings about how you feel this conversation is going to be received? Because we’re having this, we’ve had a little bit of a chat beforehand, and we exchanged a few messages and so on and so we knew what we were talking about. But somebody listening to this for the first time, it may be difficult to hear this conversation because it’s a, you know, it’s the trusted community, it’s the thing that we love and here we are suggesting that potentially money has to be involved. What would you say to those people who don’t want money to have anything to do with their WordPress experience?
\n\n\n\n[00:31:08] Marieke van de Rakt: I love those people just because I think their heart is in the right place. But I also feel like it’s not fair to those people because there’s so much money being made by those big companies, so everybody should be compensated or should grow from that.
\n\n\n\nI just think, I know I’ve had conversations in the past in which people said it should be true volunteers, and not even compensated by the company you work for, it should only be volunteers. I think it’s just not fair to those people, that they’re doing the big chunk of work. Especially if it’s organising, like a day volunteering is different to me than organising an event out of your free time.
\n\n\n\nYou’re organising something that’s of massive importance to those big companies, because they see each other there and they set up deals together, business deals. So they really need that event. They need the organisers to be in space. Those people just deserve to be compensated.
\n\n\n\nI love everybody who says that they want to do it for free, but I also think that’s not fair to them, and to their work. It’s not playing around anymore, these are like really big events. The first WordCamp Europe was 650 people, but we’re now talking about 3,000, I don’t know, 4,000 people. That’s a different league. We’re playing in a different league now.
\n\n\n\n[00:32:28] Nathan Wrigley: Yeah. I guess the rules of engagement change, don’t they? If you’ve ever been to a non WordPress event, so a more commercial event, you might have sympathy from what I’m about to say. They really do feel different, just the whole purpose of standing in that space is the economics of it. You are there to pitch your product, and that is the bottom line.
\n\n\n\nAnd if you haven’t been to a WordPress event, firstly, can I encourage you to go because you’ll probably make some great friends as much as anything else. But you don’t get that feeling, you get the feeling that it still has that community vibe to it. There are still oodles of people milling about who aren’t on the commercial side.
\n\n\n\nBut I wonder, with the people who are just in it for the commercial side, have they already gone too far? What is the road back, if you like, I’m going to say it that way. What’s the road back for these people? Where would you encourage them to go? Who would you encourage them to talk to? Which projects would you point them in the direction of?
\n\n\n\nIf somebody listening to this, their spidey sense has gone, oh hang on a minute what Marieke is saying makes sense. We’re on the commercial side, we don’t really have much in the way of the community side. How can we begin that journey? Where would you go? Where would you point them?
\n\n\n\n[00:33:43] Marieke van de Rakt: That’s hard, because I know there are companies that want to do something and don’t know. So perhaps that’s something we should be setting up, that people who are now contributing but are not being compensated for the hours, that they can somewhere say, hello. And then companies that want to compensate somebody, or sponsor somebody, can find each other. I don’t know if there’s something like that. Michelle Frechette should put up a website about that.
\n\n\n\n[00:34:07] Nathan Wrigley: We do have something called the WPCC, which might cover a little bit of this ground. It’s the WP Community Collective, and I will put that in the show notes. They have the opportunity for you to contribute financially to projects that have been decided upon already.
\n\n\n\nAs an example, I can’t remember what they call them, bursaries or something like that. You contribute to that and then if the goal is reached then that particular bit, it might be accessibility or it might be something else, that bit will happen.
\n\n\n\nBut it’s not quite the, it’s not really the place, essentially what you’re doing there is contributing your finance, which is great but it’s not really getting you inside of the community, is it? So I don’t know if such a thing exists.
\n\n\n\n[00:34:48] Marieke van de Rakt: Come to a WordCamp, come to a contributor day, that’ll help. I think then you’ll at least see, I didn’t understand anything on my first contributer day, but I know now the onboarding is better than when I started. And talk to people and see what you can do.
\n\n\n\nAnd I think if you’re profitable. Financial, there’s a lot to help. So that’s a very good first start, and perhaps then you work with someone and can see what you could do too yourself.
\n\n\n\nI’m always reluctant to be an organiser because I’m afraid that I’ll get in fights with everybody. It’s just true. I just want certain things a certain way, so I’m not going to do that. But I now know that my colleague, which works with our new company, she said, I would like to do that. So now I’m like, oh that’s great, we’ll sponsor your time and you can do that. And nobody ever gets mad at her because she’s really sweet.
\n\n\n\n[00:35:41] Nathan Wrigley: There is an option that none of this happens, and the whole thing goes pear shaped. That the enterprise of WordPress becomes more and more commercial, we just sort of put up with it, and eventually the community does just reach this point where the two sides can’t talk to each other, and so therefore, really the whole enterprise has fizzled out and gone away.
\n\n\n\nThat feels like a real shame. It does feel like the promise of something like WordPress, to democratise publishing. I know it’s easy to say those words, but the fact that you and I both have, no matter how much money is in our pocket, we have the capacity to go somewhere, and so long as we’ve got access to the internet, we can download that software and we can publish whatever we like, whenever we like, to whomever we like.
\n\n\n\nIt’s too precious of a thing to allow to just disappear, because we can’t be bothered to figure out solutions like this. That would such a shame if that happened.
\n\n\n\n[00:36:37] Marieke van de Rakt: Yeah I think we agree here. I also think that would be bad for the planet. So it would be bad for the community. But I also believe that the world is better if WordPress is bigger, because of the fact that a lot of people are in there to make the best software, and to build accessible software and to make sure that it’s, I don’t know, it’s really democratising publishing. So it would be a bad thing for the internet if WordPress would not flourish.
\n\n\n\n[00:37:04] Nathan Wrigley: Yeah, I think we can see all over the internet examples where proprietary, privately owned platforms, the incentives for those platforms to exist, it doesn’t take too many years for all sorts of bad incentives to creep in, and all of a sudden you notice that you’re being advertised all sorts of things, and your feed is being filled up with all sorts of things that potentially are good for the company behind that, but not necessarily great for you.
\n\n\n\nThat really isn’t the internet that probably anybody realistically wants. It might be free and it might be on a gigantic global scale, but maybe it’s not in everybody’s best interest. So let’s hope that we don’t have the calamity that we have just described. I have this feeling that in some way we will figure out these wrinkles, but I share your concern that now is probably the time to tackle them and not let this problem get too far.
\n\n\n\nBefore we hit record, we talked about this and we said that, really, we’re not in the game today of offering up any answers. We were just in the business of airing it, and stirring up this debate and seeing what came out.
\n\n\n\n[00:38:11] Marieke van de Rakt: Other people can come up with the answers.
\n\n\n\n[00:38:14] Nathan Wrigley: But that’s important. It’s true, isn’t it? Neither you nor I have the perfect solution. We’ve come up with a few things on the fly here today. But it would be good if anybody who had any intuitions around this, who had some novel idea that maybe nobody else has had before. Maybe you’ve tried something out in your company that you thought worked and would spread more globally. If somebody wanted to contact you, Marieke, where these days is the best place to keep this conversation going?
\n\n\n\n[00:38:42] Marieke van de Rakt: I’m on Twitter but it’s not called, no it’s called X now. I think that’s the best way get in touch. I’m not very active on Twitter but I do read it. So if you send me something there i’ll read it.
\n\n\n\n[00:38:54] Nathan Wrigley: And the fact you’re writing these posts every week, this is something which is dear to your heart. This isn’t a flash in the pan thing for you. You’re going to keep banging this drum in the days, weeks and months to come, right?
\n\n\n\n[00:39:04] Marieke van de Rakt: Yeah, I’m going to be talking about these kinds of issues and I hope that that’ll get the conversation started. People thinking about it, that would be good. And then we have a lot of new events coming up, I think, and then we’ll figure it out. I know there are a lot of people working on the same things, trying to solve the same problems.
\n\n\n\nI also think WordPress is too big to fall apart all of a sudden. So we’ll figure it out. I’m also hopeful, I’m an optimist.
\n\n\n\n[00:39:34] Nathan Wrigley: Marieke van de Rakt, thank you so much for chatting to me on the podcast today. I appreciate it.
\n\n\n\n[00:39:40] Marieke van de Rakt: Thank you. I had a good time.
\nOn the podcast today we have Marieke van de Rakt.
\n\n\n\nMarieke was one of the co-founders of Yoast. She left Yoast entirely in May 2023 and is now focussing her energy on her investment company Emilia Capital (together with Joost de Valk). This is investing in various WordPress brands and ventures.
\n\n\n\nMarieke shares her insights on the current state of the WordPress community and the challenges it faces. She highlights the growing divide between those who prioritise community-oriented contributions and those driven purely by commercial interests. She expresses her concerns about the potential consequences if this division continues to widen, including the potential growth of other content management systems.
\n\n\n\nThis issue is certainly worthy of attention, and whilst it might seem that the two sides of this debate are irreconcilable, Marieke offers potential solutions to these challenges. She emphasises the need for the WordPress community to unite and compete against other proprietary platforms. She suggests a more cohesive marketing strategy and collaboration to strengthen the community. She advocates for an official recognition system to celebrate and promote companies actively contributing to WordPress, although what that might look like is very much up for debate.
\n\n\n\nWe also hear about Marieke’s experiences at Yoast and how they contributed to WordPress over the years, particularly during the development of Gutenberg. She discusses the importance of open-source collaboration and the need for companies to align with the project’s direction for the benefit of the wider community.
\n\n\n\nWe also discuss the potential negative outcomes if WordPress becomes more commercialised, leading to a divide in the community, a divide which might be difficult to undo.
\n\n\n\nWe end by chatting about the importance of WordPress in democratising publishing, its benefits for the internet and the planet, and how, from Marieke’s point of view, WordPress is too important to fail.
\n\n\n\nIf you’re keen to see the WordPress community grow, and have an interest in how internal divisions can be avoided and resolved, this episode is for you.
\n\n\n\nOn people breaking up with WordPress
\n\n\n\nWordPress Community Collective
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 15:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:27;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"Do The Woo Community: New Woo BizChat Hosts Emma and Adam Dive into Black Friday\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77931\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://dothewoo.io/woocommerce-wordpress-sales-black-friday-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:399:\"Join our new hosts Emma Young and Adam Weeks for a great conversation and insights into doing sales on Black Friday.
\n>> The post New Woo BizChat Hosts Emma and Adam Dive into Black Friday appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 10:38:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:28;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:125:\"WPTavern: WordPress 6.4 Introduces Twenty Twenty-Four Theme, Adds Lightbox, Block Hooks, and Improvements Across Design Tools\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=151068\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:133:\"https://wptavern.com/wordpress-6-4-introduces-twenty-twenty-four-theme-adds-lightbox-block-hooks-and-improvements-across-design-tools\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5852:\"WordPress 6.4 “Shirley” was released today, named for famed American jazz pianist and singer Shirley Horn. This release introduces a new batch of writing and design tools that give users more powerful customization capabilities inside the editor. We covered most of the changes as they were released in the Gutenberg plugin and added to core, but here are a few of the highlights.
\n\n\n\nWordPress now has core support for loading images in a lightbox. It’s a simple, yet elegant “expand on click” feature that allows visitors to expand images to be full-screen without leaving the page. The lightbox can be enabled on a per-image basis or site-wide under Styles » Blocks » Images.
\n\n\n\n\n\n\n\n\n\n\n\nThe Command Palette has gotten a design refresh in 6.4 in order to accommodate a growing catalog of commands available to help users perform tasks more efficiently. Users can access the tool inside the Site Editor and the Post Editor alike, with specific contextual command options for saving time across both editing experiences.
\n\n\n\n\n\n\n\n\n\n\n\nimage credit: WordPress 6.4 release page\n\n\n\nThe List View continues to get improvements to make it more useful for getting a condensed overview of the content at a glance. WordPress 6.4 adds media previews for the Gallery and Image blocks in the List View. It also allows users to assign custom names for Group blocks, which are visible in the List View so they can be easily organized.
\n\n\n\n\n\n\n\nimage credit: WordPress 6.4 release post\n\n\n\nBlock Hooks are a new developer feature, originally introduced in Gutenberg 16.4 for auto-inserting blocks. Developers can specify a location where a block will be inserted, such as before or after a template. Users can then reposition the blocks after insertion using the editor tools.
\n\n\n\nWordPress 6.4 ships with a brand new default theme, Twenty Twenty-Four. It was designed to be a multi-purpose theme, suitable for building a wide range of websites, including blogs, businesses, and portfolios. The theme comes with more than 35 templates and patterns. Check out a live demo to see all the full-page patterns, section patterns, and style variations available in Twenty Twenty-Four. It includes three different fully-built site demos for blogger, photographer, and entrepreneur use cases.
\n\n\n\nimage credit: WordPress 6.4 About Page\n\n\n\nOther notable improvements in 6.4 include the following:
\n\n\n\nCheck out the beautiful 6.4 release page to see all the major features highlighted. Under the hood there are also more than 100 performance-related updates and a range of accessibility improvements that create a more consistent experience in the site and post editors.
\n\n\n\nThis is the last major release planned for 2023. It includes contributions from more than 600 people across 56 countries, with 170 first-time contributors.
\n\n\n\nWordPress 6.4 was led by an underrepresented gender release squad, which Release Lead Josepha Haden Chomphosy organized “to welcome and empower diverse voices in the WordPress open source project.” Together they shipped 1,150 enhancements and fixes available now in 6.4.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 03:40:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Matt: Shirley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=103777\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://ma.tt/2023/11/shirley/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:464:\"The new WordPress 6.4 is named in honor of Shirley Horn, who NPR described as the queen of silence and interpretation. If you’re in San Francisco and love jazz vocalists, this Friday Clairdee will be at Keys.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Nov 2023 00:44:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"WPTavern: Jetpack 12.8 Launches Jetpack Creator for Monetizing Content and Subscribers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150970\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"https://wptavern.com/jetpack-12-8-launches-jetpack-creator-for-monetizing-content-and-subscribers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6417:\"Jetpack 12.8 was released this week, introducing Jetpack Creator, a new product under the Growth category that sits alongside the recently launched Newsletter product. Jetpack Creator is aimed at users who want to monetize their content and subscribers. It supports e-books, courses, paid newsletters, advertising, paywalled access, and other content monetization options.
\n\n\n\nThe market size of the creator economy is growing and established social networking apps are updating their offerings to better serve creators who are marketing themselves independently. According to Goldman Sachs Research, the creator economy could approach half-a-trillion dollars by 2027:
\n\n\n\n\n\n\n\n\nAs the ecosystem grows, the total addressable market of the creator economy could roughly double in size over the next five years to $480 billion by 2027 from $250 billion today.
\n\n\n\nGoldman Sachs Research expects the 50 million global creators to grow at a 10-20% compound annual growth rate during the next five years.
\n
Jetpack Creator bundles monetization features aimed at this market. It enables access to 40+ blocks that allow creators to paywall content, add subscriber forms, accept donations, start a newsletter, and receive payment via Stripe or PayPal. Jetpack Creator also extends existing products, like adding the ability to import unlimited subscribers. The free Newsletter product caps subscriber imports at 100.
\n\n\n\n\n\n\n\n\n\n\n\nUsers on the Creator plan are also added to Jetpack’s “creator network,” which appears to be similar to ConvertKit’s creator network with a few differences. The network is designed to amplify creator’s content to help them reach a broader audience across WordPress.com and self-hosted sites using Jetpack. Jetpack’s creator network aims to get sites exposure to new readers through distribution to more areas of WordPress.com’s Reader.
\n\n\n\n\n\n\n\n\n\n\n\nIt also includes author recommendations, powered by the Blogroll block, which was introduced in Jetpack 12.7. Site admins can recommend other sites their readers might enjoy and have their site included in others’ recommendations as well.
\n\n\n\n\n\n\n\n\n\n\n\nThe Suggested follows modal is currently driven by an algorithm and suggests additional publications to follow based on what other people follow and other publications recommend. Jetpack representatives said there are plans to make it more Blogroll driven in the future.
\n\n\n\n\n\n\n\n\n\n\n\nCreators can track their engagement through a number of different ways in Jetpack, including general traffic stats, email open stats, WordAds revenue, and subscriber stats, with a new growth chart using records going forwards since October 24. Jetpack also includes an Earn screen for those selling paid content.
\n\n\n\n\n\n\n\n\nEmail opens\n\n\n\nSubscriber growth\n\n\n\n\nThe Jetpack Free plan gives users access to all the monetization tools for free but takes 10% of all revenue, similar to Substack and Gumroad. This allows users to try out the tools to see if they can make money through their web presence. The new Creator plan reduces the fees to 2% (plus Stripe fees), a significant savings for those who are successfully earning money as an online creator.
\n\n\n\nThe fees apply to the following features:
\n\n\n\nJetpack product manager Mike Stott said his team is keen on receiving feedback on this initial offering and will continue developing the roadmap based on users’ input.
\n\n\n\n“There’s a lot happening in Newsletter – last month we launched Paid Newsletter tiers and we’ll be bringing subscriber modal and categories settings into the Jetpack UI in future too,” Stott said.
\n\n\n\n“We’ll also be making it easier for content creators to gain more subscribers through the creator network (a start to this is the Author recommendations) as well as make it easier to get started.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 07 Nov 2023 20:56:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"WordPress.org blog: WordPress 6.4 “Shirley”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16299\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://wordpress.org/news/2023/11/shirley/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:67291:\"\n\n\n\nSay hello to WordPress 6.4 “Shirley,” named after the iconic jazz artist Shirley Horn. Her distinctive voice and extraordinary connection to the piano established her as one of the leading jazz musicians of her generation. Horn’s journey from the Washington D.C. jazz scene to the international stage is a testament to her dedication and perseverance. Her influence reached far beyond the confines of traditional jazz, breaking boundaries and inspiring audiences worldwide.
\n\n\n\nEnjoy the easy pace of Shirley Horn’s music as you take in all that 6.4 offers.
\n\n\n\nThis latest version of WordPress introduces a new, versatile default theme and a suite of upgrades to empower every step of your creative journey. Craft your content seamlessly with further writing improvements. Explore more ways to bring your vision to life and streamline site editing with enhanced tools. Whether you’re new to WordPress or an experienced creator, “Shirley” has something for you. Discover the unmatched flexibility of building with blocks and let your ideas take flight.
\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\nMany of the features and enhancements in WordPress 6.4 fall in the “small but mighty” category. Along with the adaptable beauty of the Twenty Twenty-Four theme, these updates help content creators and site developers alike save time and effort while delivering the high value, low hassle WordPress experience the world has grown to expect.
\nJosepha Haden Chomphosy, Executive Director of WordPress
Experience site editing at its finest with Twenty Twenty-Four. This new multi-faceted default theme has been thoughtfully crafted with three distinct use cases in mind, from writers and artists to entrepreneurs. Save time and effort with its extensive collection of over 35 templates and patterns—and unlock a world of creative possibilities with a few tweaks. Twenty Twenty-Four’s remarkable flexibility ensures an ideal fit for almost any type of site. Check it out in this demo.
\n\n\n\n\n\n\n\nNew enhancements ensure your content creation journey is smooth. Find new keyboard shortcuts in List View, smarter list merging, and enhanced control over link settings. A cohesive toolbar experience for the Navigation, List, and Quote blocks lets you work efficiently with the tooling options you need.
\n\n\n\n\n\n\n\nFirst introduced in WordPress 6.3, the Command Palette is a powerful tool to quickly find what you need, perform tasks efficiently, and speed up your building workflow. Enjoy a refreshed design and new commands to perform block-specific actions in this release.
\n\n\n\n\n\n\n\nPatterns are an excellent way to leverage the potential of blocks and simplify your site-building process. WordPress 6.4 allows you to organize them with custom categories. Plus, new advanced filtering in the Patterns section of the inserter makes finding all your patterns more intuitive.
\n\n\n\n\n\n\n\nBuild beautiful and functional layouts with an expanded set of design tools. Play with background images in Group blocks for unique designs and maintain image dimensions consistent with placeholder aspect ratios. Do you want to add buttons to your Navigation block? Now you can do it conveniently without a line of code.
\n\n\n\n\n\n\n\nEnable lightbox functionality to let your site visitors enjoy full-screen, interactive images on click. Apply it globally or to specific images to customize the viewing experience.
\n\n\n\n\n\n\n\nSet custom names for Group blocks to organize and distinguish areas of your content easily. These names will be visible in List View.
\n\n\n\n\n\n\n\nNew previews for Gallery and Image blocks in List View let you visualize and locate where images on your content are at a glance.
\n\n\n\n\n\n\n\nNeed to use your custom patterns on another site? Import and export them as JSON files from the Site Editor’s patterns view.
\n\n\n\n\n\n\n\nBlock Hooks enables developers to automatically insert dynamic blocks at specific content locations, enriching the extensibility of block themes through plugins. While considered a developer tool, this feature is geared to respect your preferences and gives you complete control to add, dismiss, and customize auto-inserted blocks to your needs.
\n\n\n\n\n\n\n\nThis release includes more than 100 performance-related updates for a faster and more efficient experience. Notable enhancements focus on template loading performance for themes (including Twenty Twenty-Four), usage of the script loading strategies “defer” and “async” in core, blocks, and themes, and optimization of autoloaded options.
\n\n\n\nEvery release is committed to making WordPress accessible to everyone. WordPress 6.4 brings several List View improvements and aria-label support for the Navigation block, among other highlights. The admin user interface includes enhancements to button placements, “Add New” menu items context, and Site Health spoken messages. Learn more about all the updates aimed at improving accessibility.
\n\n\n\nCheck out the new WordPress 6.4 page to learn more about the numerous enhancements and features of this release.
\n\n\n\nExplore Learn WordPress for quick how-to videos, online workshops, and other free resources to level up your WordPress knowledge and skills.
\n\n\n\nIf you are looking for detailed technical notes on new changes, the WordPress 6.4 Field Guide is for you. Don’t forget to subscribe to the Developer Blog to stay on top of the latest development updates, tutorials, and more.
\n\n\n\nFor more information on installation, fixes, and file changes, visit the 6.4 release notes.
\n\n\n\n\n\n\n\nThe WordPress 6.4 release comes to you from an underrepresented gender release squad to welcome and empower diverse voices in the WordPress open source project.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nBeing part of the 6.4 release coordination team has allowed me to closely observe the intricate release process, where every detail, no matter how minor, is meticulously addressed—taking into account various factors like performance and backward compatibility. There’s still much to learn, but I feel fortunate to have had the chance to contribute to WordPress 6.4.
\nAkshaya Rane, 6.4 release coordinator team member
Over several weeks, the 6.4 release squad kept the release on track and moving forward by leading collective work, connecting ideas, and removing roadblocks.
\n\n\n\nWordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a global and diverse community of people working together to strengthen the software.
\n\n\n\nWordPress 6.4 reflects the countless efforts and passion of more than 600 contributors in at least 56 countries. This release also welcomed over 170 first-time contributors!
\n\n\n\nTheir collaboration delivered more than 1150 enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress open source community.
\n\n\n\n6adminit · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · aayusha · Abha Thakor · Abid Omar · Adam Silverstein · Adhun Anand · admcfajn · adrianduffell · aegkr · ahardyjpl · Ahmed Hussein · Ahmed Kabir Chaion · ajakaroth · Aki Hamano · Akihiro Harai · Akira Tachibana · Akshaya Rane · Al-Amin Firdows · Alain Schlesser · Albert Juhé Lluveras · Alex Concha · Alex King · Alex Lende · Alex Stine · Alexandre Buffet · Alisha Bajracharya · Allison Tarr · Alvi Tazwar · amedv · Ana Cirujano · Anand Upadhyay · Anders Norén · André · Andrea Fercia · Andrei Draganescu · Andrew Hayward · Andrew Hutchings · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrew Wilder · Andy Fragen · Andy Peatling · Ankit Gade · Ankit K Gupta · Ankit Panchal · Anna · Anne Katzeff · Anne McCarthy · Anne-Mieke Bovelett · anphira · Anthony Burchell · Anton Plauche · Anton Timmermans · Anton Vlasenko · Anveshika Srivastava · archon810 · arena · Ari Stathopoulos · Arnab Mondal · Artemio Morales · Arthur Chu · asafm7 · Aslam Doctor · Aurooba Ahmed · Austin Ginder · Ayesh Karunaratne · azharckra · Balu B · bangank36 · barbmiller · Barry · Bart · Basilis Kanonidis · Beatriz Fialho · behoney · ben · Ben Dwyer · Ben Greeley · Ben Hansen · Benjamin Intal · Benjamin Zekavica · benjaminknox · Benoit Chantre · Bernhard Reiter · Bernie Reiter · Bhrugesh Bavishi · Bijay Yadav · Binsaifullah · Biplav · Birendra Dhami · Birgit Olzem · Birgit Pauli-Haack · Block Themes Pro · bmalsht · bonger · bookwyrm · Boone Gorges · Boro Sitnikovski · Brad Jorsch · Bradley Jacobs · Brandon Kraft · Brandon Vreeman · Brian Gardner · Brian Haas · Brooke · Brooke. · Bud Kraus · Caleb Burks · Calvin Alkan · Carlo Cannas · Carlos Bravo · Carlos G. P. · Carolina Nymark · Cathi Bosco · ceer · cenkdemir · Chad Chadbourne · chased@si.edu · Chintan hingrajiya · Chip Bennett · Chloé Bringmann · Chris Runnells · chriscct7 · chrisdesrochers · codersantosh · Colin Stewart · Corey Worrell · Courtney Patubo Kranzke · Courtney Robertson · Crisoforo Gaspar · crstauf · Csaba (LittleBigThings) · Cupid Chakma · cybeardjm · Cyberchicken · Daisuke Takahashi · Dajeema Rai · Damon Cook · Damon Sharp · Dan Tovbein · Daniel Bachhuber · Daniel Richards · danieldudzic · Daniele Scasciafratte · Danielle Zarcaro · danieltj · darerodz · Darin Kotter · darkfate · Darren Ethier (nerrad) · Darshit Rajyaguru · Dave Loodts · dave03 · David Baumwald · David Biňovec · David Calhoun · David E. Smith · David Favor · David Herrera · David Ryan · David Smith · Dawid Urbanski · daxelrod · De Belser Arne · Dean Sas · Dee Teal · Deepak Vijayan · Denis Žoljom · Dennis Snell · Derek Blank · Derrick Tennant · Devan Ferguson · Dharmesh Patel · Dhrumil Kumbhani · Dhruvi Shah · Diane Co · Dilip Bheda · Dimitris Mitsis · Dion Hulse · DJ · dj.cowan · Dominik Schilling · doughamlin · Drew Jaynes · Earle Davies · Ebonie Butler · Edi Amin · Edward Caissie · Ehtisham S. · Ella van Durpe · Ellen Bauer · emailjoey · Emerson Maningo · Emily Clarke · Emily Leffler Schulman · emirpprime · enodekciw · Enrico Battocchi · Erik Betshammar · Esrat Sultana Popy · Estela Rueda · Fabian Kägy · Fabian Todt · Fabio Rubioglio · Faisal Alvi · Felipe Elia · Felix Arntz · Femy Praseeth · floydwilde · FolioVision · Francesca Marano · Frank Laszlo · Fredde Battel · fzhantw · Gabriel Koen · Ganesh Dahal · Garrett Hyder · Gary Cao · Gary Pendergast · Gennady Kovshenin · George Hotelling · George Mamadashvili · Gerardo Pacheco · Gio Lodi · Glen Davies · Gnanasekaran Loganathan · Gopal Krishnan · GOZER · gpotter · Grant M. Kinney · Greg Ross · Greg Ziółkowski · gregfuller · Guss77 · Gustavo Bordoni · gvgvgvijayan · Héctor Prieto · H.M. Mushfiqur Rahman · hanneslsm · Hanzala Taifun · Hareesh S · Harsh Gajipara · Hasanuzzaman · Haz · Helen Hou-Sandi · Hemant Tejwani · Hit Bhalodia · hlunter · Howdy_McGee · Huzaifa Al Mesbah · Ian Dunn · Incursa Designs · ironprogrammer · Isabel Brison · itecrs · Ivan Zhuck · jaimieolmstead · Jakaria Istauk · Jake Goldman · Jake Spurlock · James Hunt · James Janco · James Koster · James Roberts · james0r · Jamie McHale · Jamie Perrelet · Jamie VanRaalte · jane · Jarda Snajdr · Jari Vuorenmaa · Jarko Piironen · Jason Adams · Jason Cosper · Jason Crist · jastos · Jean-Baptiste Audras · Jeff Bowen · Jeff Chi · Jeff Everhart · Jeff Ong · jeffikus · Jeffrey Paul · jeflopo · Jeremy Felt · Jeremy Herve · Jeremy Yip · jeryj · Jesin A · Jessica Duarte · Jessica Goddard · Jessica Lyschik · Jick · Jip Moors · jivygraphics · Joe Dolson · Joe Hoyle · Joe McGill · Joen A. · John Blackbourn · John Hooks · John James Jacoby · John Regan · Jon Brown · Jon Cave · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Joona · Joost de Valk · JordanPak · jordesign · Jorge Costa · Joseph G. · Josepha Haden · joshcanhelp · joshuatf · JR Tashjian · Juan Aldasoro · JuanMa Garrido · Juliette Reinders Folmer · Justin Tadlock · Jyolsna J E · K M Ashikur Rahman · K. Adam White · KafleG · Kai Hao · Kalmang · Kalpesh · Kamrul Hasan · Karlijn Bok · Karol Manijak · Karthik Thayyil · Katie Ayres · kawsaralameven · Keanan Koppenhaver · Kelly Choyce-Dwan · Kevin Fodness · Kevin Miller · Kevin Taron · khleomix · Khokan Sardar · Kim Coleman · Kishan Jasani · kkmuffme · Koji Kuno · Konstantin Kovshenin · Konstantin Obenland · Kopila Shrestha · Krupal Panchal · Labun Chemjong · Lance Willett · LarryWEB · lastsplash (a11n) · lau@mindproducts.com.au · launchinteractive · Laura Adamonis · Laura Byrne · laurelfulford · Lauren · Laxmikant Bhumkar · Lee Willis · Lena Morita · Liam Gladdy · Linkon Miyan · Linnea Huxford · Lloyd Budd · Lovekesh Kumar · Luigi · Luis Felipe Zaguini · Luis Herranz · Luke Cavanagh · lunaluna · lyndauwp · Márcio Duarte · maciejmackowiak · madejackson · Madhu Dollu · Madhu Dollu · Maggie Cabrera · Mahbub Hasan Imon · Mahrokh · Mai · Maja Benke · maltfield · Manesh Timilsina · manfcarlo · Manzoor Wani · marcelle42 · Marcelo de Moraes Serpa · Marco Ciampini · Marco Pereirinha · Marcoevich · margolisj · Marin Atanasov · Mario Santos · Marius L. J. · Mark Jaquith · Marko Ivanovic · Marta Torre · Martijn van der Klis · martin.krcho · Mary Baum · Masoud NKH · mathsgrinds · Matias Benedetto · Matias Ventura · Matt Keys · Matt Watson · Matthaus Klute · Matthew Eppelsheimer · Matthew Farlymn · Matthew Haines-Young · matthewjho · maurodf · Maxwell Morgan · maysi · Md HR Shahin · meagan hanes · Mehedi Hassan · Meher Bala · Mel Choyce-Dwan · mer00x · merel1988 · Michael Arestad · Michael Burridge · Michael Showes · Michal Czaplinski · Michalooki · Michelle Blanchette · Michelle Frechette · Michi91 · Miguel Fonseca · Mikael Korpela · Mike Jolley (a11n) · Mike McAlister · Mike Schinkel · Mike Schroder · Mike Straw · Mikin Chauhan · Milen Petrinski - Gonzo · mimi · mitchellaustin · Monir · Mrinal Haque · mrwweb · Muhammad Arslan · Muhibul Haque · mujuonly · Mukesh Panchal · Mumtahina Faguni · Mushrit Shabnam · Myles Taylor · Nalini Thakor · nandhuraj · Nazgul · Nazmul Sabuz · Neil Hainsworth · nendeb · Nick Diego · Nicolas Juen · Nicole Furlan · nicomollet · nidhidhandhukiya · Niels Lange · Nihar Ranjan Das · Nik Tsekouras · Nilambar Sharma · Nilo Velez · niravsherasiya7707 · Nitesh Das · Nithin John · Nithin SreeRaj · Noah Allen · Nyasha · ockham · Ohia · okat · Olga Gleckler · Oliver Campion · OllieJones · Paal Joachim Romdahl · pannelars · Pascal Birchler · Paul Biron · Paul Kevan · pavelevap · Pedro Mendonça · pentatonicfunk · Pete Nelson · Peter Wilson · petitphp · petrosparaskevopoulos · Petter Walbø Johnsgård · Phill · Pieterjan Deneys · piyushdeshmukh · Plugin Devs · Pooja Bhimani · Pooja Derashri · Pooja N Muchandikar · pranavjoshi · Prashant · Presskopp · r-c · Rajin Sharwar · Ramon Ahnert · Ramon Corrales · Ramon James · Rebekah Markowitz · Remy Perona · ren · Renatho (a11n) · Rene Hermenau · Reyes Martínez · Riad Benguella · Rian Rietveld · Rich Tabor · Robert Anderson · Robert O\'Rourke · Robin · robpetrin · Rolf Allard van Hagen · Ryan Duff · Ryan McCue · Ryan Neudorf · Ryan Welcher · Sérgio Gomes · Sagar Tamang · Sajjad Hossain Sagor · Sakib Mohammed · Sal Ferrarello · samba45 · Samir Karmacharya · Sampat Viral · Samuel Wood (Otto) · Sarah Norris · Sarah Williams · Sarath AR · Satish Prajapati · saulirajala · saxonfletcher · Scott Kingsley Clark · Scott Reilly · Scott Taylor · Scout James · scribu · Sergey Biryukov · Sergio Scabuzzo · Seth Rubenstein · Shail Mehta · shawfactor · Shawn Hooper · shilo-ey · Shiva Shanker Bhatta · shresthaaman · Shubham Sedani · Simon Dowdles · Siobhan · Siobhan Bamber · Smit Rathod · sofiashendi · Sonia Gaballa · Soren Wrede · SourceView · Spenser Hale · Stephanie Walters · Stephen Bernhardt · Stephen Edgar · Steve Erdelyi · Steve Jones · Subodh Sunuwar · Subrata Sarkar · Suji K Chandran · Sumi Subedi · Sumit Bagthariya · Sumit Singh · Sunita Rai · suprsam · syamraj24 · Sybre Waaijer · Synchro · Sé Reed · Taco Verdonschot · Tahmid ul Karim · Tahmina Jahan · Takayuki Miyoshi · Tammie Lister · Tanvirul Haque · Teddy Patriarca · tejadev · thinkluke · Thomas Patrick Levy · tibbsa · Tiffany Bridge · Tim Nolte · timdix · Timothy Jacobs · tmatsuur · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tom Cafferkey · Tom H · Tom J Nowell · tomluckies · Tomoki Shimomura · tomsommer · Tony G · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · toscho · Tran Ngoc Tuan Anh · Trinisha · Trisha Salas · tristanleboss · TV productions · Ugyen Dorji · Ulrich · Umesh Balayar · Upadala Vipul · Utsav tilava · valentindu62 · Valerie Blackburn · Vicente Canales · Viktor Szépe · Vipul Ghori · vivekawsm · vortfu · Vraja Das · webashrafians · WebMan Design | Oliver Juhas · Weston Ruter · WHSajid · Will Skora · William Earnhardt · Willington Vega · Winstina · winterstreet · WraithKenny · wyrfel · Yoseph Tamang · Yui · zieladam · Zunaid Amin · Илья
\n\n\n\nOver 60 locales have translated 90 percent or more of WordPress 6.4 into their language. Community translators are working hard to ensure more translations are on their way. Thank you to everyone who helps make WordPress available in 200 languages.
\n\n\n\nLast but not least, thanks to the volunteers who contribute to the support forums by answering questions from WordPress users worldwide.
\n\n\n\nParticipation in WordPress is not limited to coding. If contributing appeals to you, learning more and getting involved is easy. Discover the teams that come together to Make WordPress, and use this interactive tool to help you decide which is right for you.
\n\n\n\n\n\n\n\nOver the past two decades, WordPress has transformed the digital publishing landscape and empowered anyone to create and share, from handcrafted personal stories to world-changing movements.
\n\n\n\nThe present and future of WordPress hold exciting opportunities for everyone, builders and enterprises alike. The foundational work for Phase 3 of the roadmap continues, with efforts focused on fostering real-time collaboration and streamlining publishing flows to improve how creators and teams work together in WordPress.
\n\n\n\nStay on top of the latest news and contributing opportunities by subscribing to WordPress News and the WP Briefing podcast.
\n\n\n\n\n\n\n\nThe smooth feel of jazz
The cutting-edge of the web
Install 6.4
In this show we talk with Topher about explaining what WordPress pros do for a living, the demographics of WordPress and teaching with video.
\n>> The post How to Tell Friends and Family What You Do in WordPress with Topher DeRosia appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 07 Nov 2023 10:48:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"WPTavern: Newspack Plugin Update Checker Lets Users Update from GitHub\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150972\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/newspack-plugin-update-checker-lets-users-update-from-github\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4125:\"Adam Schweigert, an independent media and technology consultant, has released a plugin called Newspack Plugin Update Checker that enables self-hosted Newspack users to keep their plugins up-to-date. The Newspack project was launched in 2019 by WordPress.com, with support from the Google News Initiative, the Knight Foundation, and The Lenfest Institute. It provides local news organizations a powerful, yet cost effective publishing platform that promotes financial sustainability.
\n\n\n\nMore than 200 news sites are on the hosted version of Newspack, which uses WordPress.com’s cloud platform. Organizations can also host their own Newspack installations independently, which includes a theme, collection of plugins, and blocks. KinshiPress, which publishes news and updates for WordPress publishers, has a guide to self-hosting Newspack that walks through the process of getting set up. It also mentions the drawback of the plugins being hosted on GitHub.
\n\n\n\nSchweigert’s Newspack Plugin Update Checker solves this problem by using a plugin updater library that checks for updates and lets users know when a new version is available. The notice appears in the dashboard in a similar way to how WordPress.org displays updates.
\n\n\n\n\n\n\n\n\n\n\n\nThe plugin checks for updates for nine of the most commonly-used Newspack plugins, including the following:
\n\n\n\nSchweigert noted that the plugin requires the Newspack plugins be in folders named using their respective slugs. Although the plugin allows users to enable auto-updates, he recommends keeping an eye on the Newspack release notes to be prepared for any potentially breaking changes.
\n\n\n\nKinshiPress author Steve Burge recently published an article on the Newspack ecosystem, contending that Newspack has the potential to do for publishers what WooCommerce has done for e-commerce.
\n\n\n\n“There’s a big audience out for a publishing platform that is open source, highly extendable, and has the backing of a successful company and a strong community,” Burge said.” Where else can newspapers, magazines and radio stations go? They mostly go to WordPress already, but the platform we provide them could be much more targeted and helpful.”
\n\n\n\nAlthough Schweigert’s plugin is a good stop gap measure, Burge said he thinks putting the Newspack plugins on WordPress.org and improving the documentation would go a long way towards expanding its impact.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 04 Nov 2023 03:30:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:34;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"WPTavern: WordPress Theme Handbook Updates Chapter on Block Templating\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150958\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/wordpress-theme-handbook-updates-chapter-on-block-templating\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2584:\"WordPress contributors have updated the Theme Handbook to include a new chapter on block templating. The chapter covers how the WordPress block template system works, how to build custom templates and parts and include them in a theme. This is critical documentation designed to provide a learning path for those who are building their first block themes.
\n\n\n\nAutomattic-sponsored developer advocate Justin Tadlock announced the update on Twitter, noting that it also includes a couple of new docs in the Global Settings and Styles chapter for registering template-related features in theme.json, and the same for template parts.
\n\n\n\nThe new chapter on block templating is just one part of a larger effort to overhaul the Theme Handbook for modern day WordPress. Contributors are transitioning the focus from classic theming to block theming, with just one chapter in the handbook devoted to classic themes.
\n\n\n\n“It was created during a time when classic themes were the only method of front-end design for WordPress,” Tadlock said in the proposal to overhaul the handbook. “Much of its content now exists in a transitory state between classic and modern block theming. This has created a scenario where the handbook sometimes reads more like patchwork than if it were built with a single vision. That is often a natural result of adding new documentation over years.”
\n\n\n\nThe proposal does not recommend scrapping all of the existing content but rather carrying some of it forward to be updated and reorganized. A good portion of the existing content is still relevant to be migrated to the Classic Themes chapter.
\n\n\n\nOverhauling the Theme Handbook is a colossal effort that’s still ongoing. It’s being managed under a tracking ticket on GitHub. The new chapter better supports developers who are just figuring out how the WordPress block template system works, but there are many more chapters that need attention. Anyone who would like to get involved in the project can select any issue on the ticket to get started.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 03 Nov 2023 19:36:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:35;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"WPTavern: Add Icons to WordPress’ Core Button Block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150927\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://wptavern.com/add-icons-to-wordpress-core-button-block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5605:\"Nick Diego, a developer advocate at Automattic and core contributor, is the author of the popular Icon Block plugin that enables users to add custom SVG icons and graphics to the WordPress block editor. He is often asked if the plugin can add icons to the core Button block, but that is outside the scope of what it does. Last week he wrote a plugin that fulfills this feature request in a separate plugin without building a custom block.
\n\n\n\n \n\n\n\n\n\n\n\nThe Enable Button Icons plugin is available on GitHub as an example that demonstrates how developers can lightly extend core blocks for features like this. Diego said he was inspired by WordPress developer Aki Hamano’s Enable Responsive Image plugin that adds settings to the Image block to elegantly display different images depending on the width of the screen.
\n\n\n\n \n\n\n\n“I wanted to use the WordPress image block to switch images on mobile, but I wanted something that would simply extend the core block without having to create a custom block, so I tried making one,” Hamano said. “For now, you can only add one image, and only the breakpoint and resolution can be switched.”
\n\n\n\nDiego said he doesn’t plan to add his Enable Button Icons plugin to the official WordPress directory.
\n\n\n\n“It works great, but it is not designed to support an entire library of icons, and I know that will be the first thing people ask for,” he said. “So, I’m thinking of keeping it as an example and encouraging people to take it and modify it as they want.”
\n\n\n\nI tested the plugin and it works perfectly but is certainly ripe for being extended to support a larger selection of icons. Alternatively, it may be useful for a brand that has a set number of custom designed icons they want to be easily accessible for use in Button blocks.
\n\n\n\n\n\n\n\n\n\n\n\nDiego will be running an event at the end of the month about how to extend core WordPress blocks, and the Enable Button Icons plugin will be part of that. It will be another segment in the “Developer Hours” series run through the Learn WordPress Online Workshops group on Meetup. Diego and a team of contributors just wrapped up a Developer Hours event today featuring a demo/walkthrough of the upcoming Twenty Twenty-Four default theme. Watch for the next event to be added to the schedule sometime this week.
\n\n\n\nDevelopers have been asking for more extensibility, hooks, and filters for the block editor, and an upcoming Hallway Hangout event will focus on triaging issues related to extending Gutenberg. Contributors will discuss the 110 outstanding issues labeled “Extensibility,” and 20 issues labeled “Blocks Adoption,” used for issues that directly impact the ability to adopt features of Gutenberg. Anyone who wants to share their opinions about block editor extensibility issues is invited to join.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 03 Nov 2023 02:03:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"Do The Woo Community: Do the Woo Day 3 Recap, WooSesh 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77702\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://dothewoo.io/do-the-woo-day-3-recap-woosesh-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:367:\"Day 3 recap included a deep look at producing WooSesh, the Seshies awards and conversation around the days sessions.
\n>> The post Do the Woo Day 3 Recap, WooSesh 2023 appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 02 Nov 2023 11:05:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"WPTavern: Wordfence CLI 2.0.1 Update Adds Free Vulnerability Scanning\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150866\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wptavern.com/wordfence-cli-2-0-1-update-adds-free-vulnerability-scanning\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3294:\"Wordfence CLI 2.0.1 introduced free vulnerability scanning this week. The new CLI product was launched at WordCamp US two months ago with malware detection capabilities, but the latest update brings in the most highly requested feature – vulnerability scanning at scale.
\n\n\n\nWordfence is most well-known for its Web Application Firewall, malware scanner, and login security product, which is packaged as a free plugin and installed on more than 4 million websites. The CLI is the first-ever command line malware and vulnerability scanner for WordPress servers. It is targeted at developers, site cleaners who scan large numbers of files for remediation, agencies, and hosting companies that want to scan across entire networks of millions of customers.
\n\n\n\n“Vulnerability scanning in Wordfence CLI 2.0.1 uses our own open vulnerability database,” Wordfence CEO Mark Maunder said. “The database itself is completely free for anyone to use, and includes APIs that are open, along with web hooks so that developers can build real-time alerting into their applications. Our mission is to secure the Web, and we think that having an open vulnerability database, with an open source, robust and high performance vulnerability scanner for servers furthers that mission.”
\n\n\n\nThe vulnerability database includes responsible disclosures published by researchers for the benefit of the wider community.
“Because most vulnerabilities come from the research community, we believe they are public property,” Maunder said. “While some companies do charge for their collection of vulnerabilities, we don’t think it is appropriate to resell public property, which is why we created an open and completely free vulnerability database.”
The CLI vulnerability scans use the Wordfence Intelligence Vulnerability API feed, which is free for both personal and commercial use. It contains more than 12,250 unique vulnerability records affecting 7,600 plugins and themes. The Wordfence team adds an average of 82 new vulnerabilities per week.
\n\n\n\nVersion 2.0.1, code named “Voodoo Child” simplifies installation so users no longer have to go to the Wordfence site to get an API key. The tool fetches the API key in the background to make it easier to get started.
\n\n\n\nWordfence CLI is licensed under the GPLv3 and available on GitHub, along with documentation for installing, configuring, and running the application.
\n\n\n\n“Wordfence CLI is one of those projects where the product roadmap writes itself because there is such an obvious need for a powerful tool like this in the WordPress server administration space,” Wordfence lead developer Matt Barry said. “We’re in this for the long haul and will continue to invest heavily in Wordfence CLI, with your guidance.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 20:48:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"WordPress.org blog: WordPress 6.4 Release Candidate 3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=16247\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2023/11/wordpress-6-4-release-candidate-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8050:\"The third release candidate (RC3) for WordPress 6.4 is ready to download!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC3 on a test server and site.
\n\n\n\nWordPress 6.4 is slated for release on November 7, 2023—less than a week away. If you haven’t tried it, now is the time.
\n\n\n\nYou can test WordPress 6.4 RC3 in three ways:
\n\n\n\nwp core update --version=6.4-RC3
Read the RC1 announcement for featured highlights, and check the Make WordPress Core blog for 6.4-related posts. If you are looking for detailed technical notes on new features and improvements, the WordPress 6.4 Field Guide is for you.
\n\n\n\nThe WordPress 6.4 release is brought to you by an underrepresented gender release squad to welcome the participation and partnership of those who identify as gender-underrepresented in the WordPress open source project.
\n\n\n\n\n\n\n\nThanks to everyone who has tested the beta and RC releases. Since RC2 was released on October 24, there have been more than 25 issues resolved. You can browse the technical details for all recent updates using these links:
\n\n\n\nIt’s recommended to use PHP 8.1 or 8.2 with the upcoming 6.4 release. Refer to WordPress 6.4’s PHP compatibility post for more details.
\n\n\n\n\n\n\n\nWordPress is open source software made possible by a community of people collaborating on and contributing to its development. The resources below outline various ways you can help, regardless of your technical expertise.
\n\n\n\nYour feedback and help in testing are vital to developing the WordPress software and ensuring its quality. It’s also a meaningful way for anyone to contribute. Check out this guide for instructions on testing WordPress 6.4 features.
\n\n\n\nThe core Query block requires more testing and feedback to ensure the latest changes to prevent full page reloads work smoothly. Please note that this setting was called “Enhanced pagination” but has recently been renamed, and it’s now referred to as “Force page reload” instead.
\n\n\n\nIf you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.
\n\n\n\nCurious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
\n\n\n\nDuring the release candidate phase of WordPress 6.4, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.
\n\n\n\nDo you build themes and plugins? Your products play an integral role in extending the functionality and value of WordPress for users worldwide.
\n\n\n\nHopefully, you have already tested your themes and plugins with WordPress 6.4 betas. With RC3, you will want to continue your testing and update the “Tested up to” version in your plugin’s readme file to 6.4.
\n\n\n\nPlease post detailed information to the support forums if you find compatibility issues.
\n\n\n\nHelp the Docs team put the finishing touches on end-user documentation in time for the 6.4 release. Find out what’s needed and how you can help in this post.
\n\n\n\nDo you speak a language other than English? ¿Español? Français? Português? Русский? 日本? Help translate WordPress into more than 100 languages.
\n\n\n\n\n\n\n\nOne more week of prep
One more week to test the code
One more week til launch
Thank you to the following contributors for collaborating on this post: @meher, @rmartinezduque, @sereedmedia, @jorbin, @luisherranz, @marybaum.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 19:21:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Reyes Martínez\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"WPTavern: #97 – Estela Rueda, Courtney Robertson and Javier Casares on the Future of Translating WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=150878\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://wptavern.com/podcast/97-estela-rueda-courtney-robertson-and-javier-casares-on-the-future-of-translating-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:56373:\"Transcript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast, which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case how translations of the WordPress project are created now and in the future.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you all your idea featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox, and use the form there.
\n\n\n\nSo on the podcast today, we have Estela Rueda, Courtney Robertson and Javier Casares.
\n\n\n\nCourtney is a former teacher who now focuses on contributing to WordPress. With a background in education, she understands the challenges faced by English second language learners in the American education system. She’s passionate about providing access to WordPress in multiple languages, as she believes it’s unfair to expect non-English speakers to simultaneously translate content and understand it.
\n\n\n\nEstela is a language enthusiast who has spent years navigating the challenges of website localization. As a member of the WordPress community, Estela has come across the intricacies of language differences, and the need for accurate translation in various Spanish locales. With 14 Spanish locales to handle Estela’s expertise in understanding the subtle nuances, and localizations of each language variation has been indispensable.
\n\n\n\nJavier is a dedicated member of the WordPress community, with expertise in creating documentation. Javier has been instrumental in developing handbooks for various sites. However, there have been some technical challenges. Despite these obstacles Javier, as you will hear, remains committed to addressing and solving the documentation issues at hand.
\n\n\n\nThis episode covers the important topic of translations, and making WordPress documentation more accessible to people worldwide. Our guests bring a wealth of knowledge and experience to the table, as they discuss the complexities and challenges of language translation in the WordPress ecosystem.
\n\n\n\nWe start by highlighting challenges posed in translating WordPress, such as the tangled processes currently in place, as well as more language focused topics. We talk about the extensive collaborative effort involved in translating WordPress, and the plans to expand translation efforts to documentation with the help of dedicated teams.
\n\n\n\nWe get into how contributors might need to rethink how many of the current translation processes are structured. We discuss the different approaches needed for translating plugins and themes versus documentation. We touch upon how technical aspects of these processes such as content creation and updates also pose significant challenges.
\n\n\n\nAll three guests stress the importance of global involvement in translation efforts, including translators, reviewers, and project managers. They advocate for the development of standardized style guides for each language to maintain consistency. And they explore the possibility of creating software, or tools, to manage translation tasks.
\n\n\n\nCourtney, Estela and Javier all acknowledge the challenges ahead, but express optimism that their ideas will help make WordPress accessible for all. Communicating how WordPress is built and how it works is an endeavor tightly aligned with the projects overall mission of democratizing publishing.
\n\n\n\nIf you’re interested in finding out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast, where you’ll find all the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Estela Rueda, Courtney Robertson and Javier Casares.
\n\n\n\nI am joined on the podcast today by three fine people. I’m joined by Courtney Robertson, Estela Rueda and Javier Casares. Hello all three of you.
\n\n\n\n[00:04:48] Javier Casares: Hello.
\n\n\n\n[00:04:49] Estela Rueda: Hi Nathan.
\n\n\n\n[00:04:50] Courtney Robertson: Hello.
\n\n\n\n[00:04:51] Nathan Wrigley: Very nice to have you on the podcast today. We’re going to be talking about WordPress translations, and the way that we can make it easier for people from around the globe to get access to WordPress documentation. It’s a very important subject and there’s been a lot of work, albeit that you may not know about it. There’s been an awful lot of work going on over, well more or less a decade, and we’ll find out more about that in a moment.
\n\n\n\nBut first of all I think it’s important that everybody gets a little window to introduce themselves, do a quick bio. So if I take you one at a time and lets start with Courtney. Just tell us who you are. And I know that I’m going to say can we be brief but I know time is short, so let’s keep it fairly brief if that’s all right.
\n\n\n\n[00:05:33] Courtney Robertson: Sure thing. I’ve been contributing to WordPress since 2009. A big part of the training team for many years. These days you can also find me over in Meta, Sustainability, and generally around the project on behalf of GoDaddy these days, and I’ve been there for about two and a half years. Long time contributor. Big fan.
\n\n\n\n[00:05:50] Nathan Wrigley: Thank you so much. I’m sure that people have come across Courtney in the past, as would be the case for the next two people. Let’s go for Estela next. Hello Estela, would you mind giving us your intro?
\n\n\n\n[00:06:01] Estela Rueda: Hi Nathan. Yes. I’ve been contributing for about five years already and I am mostly in the design and the documentation teams. But you can find me everywhere. I do mess around everywhere, I ask questions. And my goal has been to rearrange, recategorise the end user documentation. And that’s been the big project that we finished, it took us three years. And now we want to bring it up to the whole world in every single language we can manage.
\n\n\n\n[00:06:33] Nathan Wrigley: Okay thank you. And finally Javier, if you want to just give us your short bio.
\n\n\n\n[00:06:37] Javier Casares: Yeah. Hello everybody. I’m Javier Casares, I’m from Spain. I’ve been involved with WordPress since 2006, so more or less 17 years. I mainly focus on hosting, on the hosting team, and I’m helping the documentation team mainly with the Advanced Administration Handbook. So that’s more or less what I do. I do a lot of things but those are the main things.
\n\n\n\n[00:07:04] Nathan Wrigley: Those are the things which are pertinent to today’s discussion. Yeah, thank you so much.
\n\n\n\nSo if, like me, you are a native English speaker, English is your first language. It may very well be that some of the things that we’re going to talk about today have either never occurred to you, or you’ve never bumped up against this problem.
\n\n\n\nBecause broadly speaking, if you are a native English speaker, you can find the documentation, you can find tutorials. You can find almost anything you wish to find out about WordPress, how to use it, how to implement things and so on, by going and doing a Google search. And you’re off to the races because essentially everything has historically been done in the English language.
\n\n\n\nSo I guess that, in my case, makes me an incredibly fortunate person. But that’s not the case throughout the world. And as obviously WordPress has grown, we’re now 40 plus percent of the internet, it would be not really serving the user base of WordPress if everything was simply in English. It would be a laudable goal to get everything translated.
\n\n\n\nNow I guess we should probably outline where all of the things are at the moment. So it’s not the case that you can go to one website and there it all is, open a Pandora’s box, open it all and there it all is.
\n\n\n\nSo let’s outline that problem first. I don’t really mind who wishes to tackle this one. Yeah if somebody wants to just outline the problem that we face, where are all the documents stored at the moment?
\n\n\n\n[00:08:23] Estela Rueda: I can’t give it a go. There are many, many limitations within WordPress. There are the sites that are called the Rosetta sites, or locales and those are the ones that are written in other languages for local teams.
\n\n\n\nBut then we have issues, different issues. For instance, in Spanish, we have 14 locales in Spanish. So we have Spanish from Spain, we have Spanish from Mexico, Spanish from Colombia, Spanish from Costa Rica, et cetera. And everybody will think, well don’t you understand each other? Yeah we do, we understand each other, but there are so many differences in our languages. And there is the localisation of the words, and a lot of little things that we need to figure out. That’s one thing.
\n\n\n\nThen the other thing is that there are never enough contributors to do translations. And then there are all the technical issues that we have, and Javier can talk to you about those, because he’s more aware than all of the technical issues that we have.
\n\n\n\n[00:09:25] Nathan Wrigley: Okay, in that case, we’ll hopefully segue over to Javier. Are you able to take it from there?
\n\n\n\n[00:09:29] Javier Casares: Yeah. So the main thing is, we have the Rosetta sites. It’s local team can create their own documentation in a way, because some of the sites have their own handbooks. But there is some technical things there because, for example, the Spanish from Spain is one of the older sites in the WordPress network.
\n\n\n\nSo it’s database is in LATIN1, it’s not in UTF, it’s a technical thing. But it doesn’t allow, for example, emojis in the database. That’s so simple but it’s something that happens. So we have some problems having documentation there. That’s one of the things.
\n\n\n\nBut the other one is we have the documentation right now in wordpress.org/documentation. Also we have the developer.wordpress.org. We have the Learn corpus also in with a lot of documentation. In a lot of ways, WordPress TV should, maybe it’s another place with documentation, in video in this case. And everything usually is focused on English.
\n\n\n\nSo the main idea on this project we started like a year ago is, how can we translate everything into, more or less, at least eight languages? Because eight languages cover more or less eighty percent of the WordPress users. And also, where are we going to put that documentation? Because, for example, we can do ses.wordpress.org/documentation, that’s the easy one. But, for example, the developer documentation is in a subdomain so, where are we going to put all this documentation?
\n\n\n\nSo that’s one of the things we are trying to solve. That’s one technical problem we have to face. And the other one is, where are we going to put all the documentation to be translated? Because we know that WordPress will be multilingual in a way in some years. I hope soon, as soon as possible.
\n\n\n\nWe have now the phase three, the collaboration part. But we have the problem that we cannot give access in this case. This is something concrete for WordPress, not for a translation or a documentation problem. But we cannot give access to thousands of people to the WordPress network, because it won’t be able to control the security and everything.
\n\n\n\nWe decided to start migrating or having the English documentation in GitHub. That’s one place. Also GitHub has natively, the Markdown editor, so with some commands and some things we can put everything there in a way that everybody can take the English document and translate it into their language.
\n\n\n\nFor example I’m doing that, I’m starting to do that in a beta project for the advanced documentation. That’s something we’ve been working on for more or less 8 months. It was a very difficult thing to arrive because it’s been a big problem. A lot of people have been involved, a lot of languages, people from different countries involved, a lot of teams involved. So it has been a very technical challenge in a way.
\n\n\n\n[00:13:00] Nathan Wrigley: Thank you so much. I don’t know if Courtney wants to add anything to that before we move on.
\n\n\n\n[00:13:05] Courtney Robertson: Yeah. So my background, before going full time contributing to WordPress, was that of a teacher. And in the education space within America we have a lot of ESL, English Second Language. So we have a lot of people that don’t primarily speak English, and it’s a disservice to them in the education system to expect them to understand the content on top of having to simultaneously translate a language. That’s a really big learning difficulty.
\n\n\n\nSo I very much wholeheartedly believe in providing access for people to learn WordPress in their own languages. Down to reading the captions on videos. If you’re an English speaker I would encourage you to go over to wordpress.tv, try to find a video that is not in your language, not in your first language, and subject yourselves to reading the captions and think about how fair is that for the rest of the world.
\n\n\n\nSo with that in mind, in Learn WordPress we have a different workflow perhaps than the Docs team. So Docs again think of as the dictionary and the reference manuals, and Learn as the teacher’s spot to be, or the direct learner’s spot to go, if they don’t find reading the manual version to meet their learning style.
\n\n\n\nAnd that’s something that we very much want to consider. Some people need a little more instruction to be able to get the concepts. And so Learn WordPress exists for that, both direct learners and educators. And over there we do not get access to Rosetta sites and instead we rely upon one instance of Learn WordPress.
\n\n\n\nWhereas in the Rosetta sites and what we’ve heard from recent episodes with Vagelis and Piermario, just a few episodes back. We could hear that from what they’ve shared in other parts of the WordPress project there are tools to basically make a whole separate locale instance going on. So if you were in Spain and you wanted to read the same type of content, you would have an entire version of the site that is just for you.
\n\n\n\nWhereas with Learn WordPress, what we have going on is all the languages all smooshed into one site. And what becomes difficult is we don’t have good workflows yet established around if the English language version gets an update, how do I assess what content? I speak only a tiny bit of Spanish and a tiny bit of Latin, of all the things. Good conversation starters.
\n\n\n\nSo you won’t find an easy way to identify even what the other topics are with the same title. Let alone somebody that can’t assess what that content looks like. So we have some locale ambassadors, Piermario is doing a great job with the folks based out of Italy on rounding up some efforts there. Margarita especially, is someone that’s participating with Piermario on identifying the content to be translated into the Italian locale.
\n\n\n\nSo we’re basically duplicating the content, but just in other languages all under the same site. So that’s not the most efficient way and we’re using GitHub as well to do some of this work. We have GitHub issues that have a template. So think of GitHub issues as logging something on the WordPress forums, right? It’s about on par with that. But we prefill what the text of that issue is, and have a workflow to publish that.
\n\n\n\nBut that’s not necessarily in conjunction with what the English version, last update, is or plans of how do we maintain those updates? And then, how do we also look and see if the Docs team did a certain bit of update? And how do we find the polyglots that really like these specific areas? You can see this becomes quite a challenge as we’re looking ahead to Gutenberg phase four with multilingual support natively. We’re still a ways out from that, but you can see where this is something to start untangling and working on internally before we roll it all into Core.
\n\n\n\n[00:16:59] Nathan Wrigley: So it sounds like that this is a spaghetti of things just loosely held together simply by people actually understanding what the processes of the different teams are. But we don’t have this one workflow, which presumably is some kind of goal. But we do have a moment in time, which would be the release of Gutenberg phase four, where hopefully a large proportion of this would be either in progress or completed, because at that point WordPress itself becomes translatable. And I suppose at that point it would be incredibly useful to have this work done.
\n\n\n\nI just want to touch on a couple of things that may have confused the listeners because we’re all speaking, probably in a bit of an echo chamber here. And so there were a couple of things which were mentioned. The first of which was Rosetta, that got dropped a couple of times, and it may be useful for people to actually know what that means. So if anybody’s willing to just very briefly explain what Rosetta is. I mean we know what the stone is and so we get the connection there but, what is that thing in WordPress?
\n\n\n\n[00:17:57] Javier Casares: The Rosetta sites are the locale sites in WordPress. So we have wordpress.org, everything is in English, it’s the main site. Most of everything is there. But, for example, for Spain we have es.wordpress.org, or for Catalan we have ca.wordpress.org or I don’t know for French we have fr.wordpress.org.
\n\n\n\nThose are translation sites from the main site, but not everything is in there. There are the main contents, for example, the download page, everything is in your language. When you download the WordPress from that site, it’s in your language. It includes the translation files. But each site can be managed by different people.
\n\n\n\nFor example, in Spain we usually publish one post every week talking about things. It can be translation from general post, or it can be local things about WordCamps in Spain or whatever. So that’s more or less the thing inside the Rosetta. It’s the technical name, the project, the Rosetta project is the name or the locale site. So that’s more or less the thing.
\n\n\n\n[00:19:12] Nathan Wrigley: Yeah thank you, that’s perfect. That explains it beautifully.
\n\n\n\nThe other thing that was mentioned was eight languages have been put forward as the language is to get us to 80%. So I guess it would be quite nice for the listeners to know what those languages are. I don’t know if a quick Google search needs to be done there, or if anybody’s got that information to hand. But it would be nice to know eight languages initially are.
\n\n\n\nAnd also to know that isn’t the entire scope of the project. That’s more a, let’s get something over the line with these eight languages, as opposed to that’s what we’re doing and that’s all that we’ll ever do.
\n\n\n\n[00:19:44] Javier Casares: Yeah. I have some information from the hosting team, and it was like, okay, I’m going to analyse where and what language are the most downloaded in WordPress. So these languages are not the eight most top languages in the world, they are are the most used in the WordPress ecosystem.
\n\n\n\nSo that’s the main idea behind having those languages as the main ones. German, more or less the 6% in the WordPress scope. English, the 48%, Spanish 7%, French 5%, Italian 4%, Japanese 6%, Portuguese 5%, and Russian 3%. More or less that covers the 80% of the documentation or languages that WordPress has installations.
\n\n\n\n[00:20:34] Nathan Wrigley: Okay thank you, that’s great. That clears that one up.
\n\n\n\nSo I guess we’ve highlighted a problematic past, well not really problematic, it’s just the way the project evolved where everything is done in a unique way depending on the team, or which part of WordPress you’re touching. And maybe this one is for Estela. The enterprise of this podcast really is to highlight some future where we improve things and we take things forward, and you have outlined, I guess a project is the best way to describe it.
\n\n\n\nWhat is your idea? What is it that you want to happen in the future? We don’t have to create timelines or anything, but let’s just imagine that we’re a decade out from now and it’s all been achieved, what would be your north star for all of this?
\n\n\n\n[00:21:16] Estela Rueda: This is where we are, you know where we are working at right now, where we are starting. I started with this Spanish team. They are my trial team. And the only reason why I started with them is because I speak Spanish and it’s easier for me to guide them. We had to start the project in, you know, baby steps, go little by little. The idea is to create a process or a model that we can replicate into other languages.
\n\n\n\nI started with the style guide and how to write documentation in Spanish, because we have many grammar issues with the language. First of all, you know, we have the way we address each other, like formal, informal or we have the language is genderised, completely genderised. Everything is either female or male, there is no neutral gender in Spanish.
\n\n\n\nThere are so many issues that we need to address. And I’m pretty sure other languages have the same or similar problems in their grammar, you know, grammatically speaking. And we need to address those and, how are we going to use them in documentation, in order to make it as neutral as possible and as easy to understand? They’re going to be like, you know, writing rules.
\n\n\n\nThen we have the translation of the sitemap. Now, what I did with the Spanish team, we spent during a WordC amp, a whole contributor day, translating the site map for end user documentation. But I sat the marketing, the polyglots, and the documentation teams together. And I told them, okay, we’re going to translate but I don’t want you to translate literally. I asked marketing, give us words that are searched for, that will help with the SEO of the site. So that way we can localise also, and we can increase the use of the translation of WordPress.
\n\n\n\nAfter that, I guess we’re going to start working into translating documentation. We’re going to create teams, and we’re going to start working on it. My idea is to start some sort of triage hours with teams. And let’s say twice a month, to review what we have written and to continue writing and just that sort of thing.
\n\n\n\nBecause I know that if I leave it to every contributor day for every WordCamp it’s just never going to happen. And this is something that we need. If we want to progress we need to work, you know, a little bit every day, a little bit every day.
\n\n\n\nSo if we don’t put set goals then this is not going to happen. But that’s where I am right now. And I will reach out to the Brazilian team who approached me and may be the second team that I start working with.
\n\n\n\n[00:23:56] Nathan Wrigley: So Estela, just to be clear the intention here is to delve into, in your case, the Spanish language and come up with a rule set, like a workflow. Where, okay, if we receive things in English, these are the set of constraints that we’ve got when we translate into Spanish. So somebody who is new to the team would be able to look at those guidelines, the workflow document, whatever it may be and have a very strong idea of, okay, this is the way to do it. When you’re going from English to Spanish, this is how you do it. Have I understood that correctly?
\n\n\n\n[00:24:29] Estela Rueda: Yes. But those writing rules, or the style guide, I call them the writing rules because that’s what they are. But I want to apply that for every language, just not for the Spanish team. And that style guide has to be according to the language grammar, not to what we like.
\n\n\n\n[00:24:45] Nathan Wrigley: In my head I’m seeing a website when you say that, but of course, you’re talking about the style of the language, in your case the sort of gender that you’ve got to go to and things like that. That’s interesting. And, can you give us some sort of insight into how that’s going? Has it proven to be fairly straightforward to put that workflow together or is it a really thorny thing to unpick?
\n\n\n\n[00:25:03] Estela Rueda: We are just at the beginning of it. I just pitched this idea at the WordCamp in Pontevedra, which was last month, two months ago. And I realised that I need to sit down and start writing. So I gave them some sort of topics that might affect the language, and gave it to the team, to the Spanish team actually.
\n\n\n\nThey are going to start writing the style guide. And I said listen, I write something, ideas that I have and if they are not okay, feel free to go ahead and edit and change them. And let’s see what affects us where. Is it easy? No it’s not easy. It’s going to be difficult because like I said, we have 14 locales, or 14 Rosetta sites, for 14 different versions of Spanish. And we need to come together to a point where, what is the most common use for everybody?
\n\n\n\n[00:26:03] Nathan Wrigley: So this question is going to sound a bit meta, meta in the real sense of the word. You are creating a document which then you will be able to share to other teams in order that they can run their own process. So a silly example, the Latin version of WordPress would need to look at what your team have put together, how to go through the process? Which they can then implement with their own locale.
\n\n\n\n[00:26:28] Estela Rueda: Yes. I will be documenting. Actually this week I’m going to publish a post in the Polyglots team regarding about this step one, step two. So what is the writing style guide and why are we writing it? And what happened to the sitemap and how we came up to what we have.
\n\n\n\n[00:26:44] Nathan Wrigley: So just talking about it on this podcast, it seems like a fairly solvable problem, but of course when you actually apply thought to it, this really is a gigantic plate of spaghetti. There’s an awful lot to be unpicked. There’s an awful lot of work to be done. And I’m just wondering how you feel about this, whether you’re sanguine.
\n\n\n\nAnd it’s not necessarily for Estela, it’s for everybody on the call. How you feel about whether this project is going to be able to ship its aspiration in the, well let’s say, it’s probably a matter of years not months certainly, but probably under a decade, before Gutenberg four comes out.
\n\n\n\nBecause it does sound, on the face of it, it sounds like you’ve got an awful lot of work to be done. If you complete the Spanish, then you’ve got to move on to another one. You’ve got to get people’s buy in, you’ve got to re educate those people who are contributing their time, as translators. They’ve got to be re educated to do it in a different way. How positive, sanguine do you feel that this is achievable?
\n\n\n\n[00:27:41] Courtney Robertson: Nathan, I’ll jump in here. One of the ideas that a coach in my life has shared with me, the motto of this company is, a world that works for everyone with no one left out. And I think about that a lot in the context of open source, and how we make WordPress possible for the whole globe, right?
\n\n\n\nWe are trying to make this tool that we have available, be available for as many people as would have used it, and make the best of that situation. And if we take that backwards to a place where we might need a mindset shift to go on, let’s think about a couple of features in the WordPress project that have rolled out within the last few versions of releases, and the naming that goes into it.
\n\n\n\nI know the community would like to improve how we name things from this outset, so that we don’t have to rename them later. So one example that I thought went really, really well is what became the Command Palette. The initial proposal was to call it something along the lines of Wayfinder. And one of the great insights, because we were able to identify and put this kind of call out across social media and other places, it was not something that was just buried and obscure over in GitHub.
\n\n\n\nIt was raised throughout the community and a lot of folks said, that doesn’t make sense in my language. If you do a direct translation this does not make sense. So it’s not just about translating after the fact, but it’s also about how we name things really even before it gets widely publicly released.
\n\n\n\nAnd so that’s a mindset shift that I think, I’ll say as an English speaker, I really think that we need to experience more of being the second language to truly appreciate and understand the depth of why naming things matters so greatly. The depth of why we need to consider how this will work with other languages. Consider the workflow process. To the point where we’re not just, yes, it will probably remain English forward first.
\n\n\n\nBut to always tuck in mind the processes that go on downstream after we get the thing out in English or what have you. What are we asking our translation folks to do, and how does this impact somebody in a different language? I learned that when Learn was added the navigation menu across all WordPress sites, that the way it had been translated, particularly into Russian, Olga caught this one, it didn’t make sense in the way that it was translated. And so we have to think about these things before we just ship sometimes.
\n\n\n\n[00:30:22] Nathan Wrigley: I have this intuition that if the Command Palette had been called something, even adjacent to the Command Palette, it would have stayed like that. It the controversy of it being so poorly named that led the community to sort of say, well that’s really not the right idea.
\n\n\n\nAnd so sometimes I wonder if backing yourself into a corner is the best way to get attention, if you know what I mean. It’s probably not the desirable outcome but it is possibly a way that, you know, people get enraged by something and so they go out on social media and change happens more quickly.
\n\n\n\nFrom what I’m hearing there Courtney, you’re basically making a moral argument for this. It’s the right thing to do. It doesn’t matter what the goal is, whether we achieve this in a matter of 2 years, 6 years, 10 years, whatever it may be. The journey is the important thing, making the steps now to make this possible is the important point, not the end goal.
\n\n\n\n[00:31:11] Courtney Robertson: Absolutely true. Yes.
\n\n\n\n[00:31:13] Nathan Wrigley: Okay, thank you.
\n\n\n\nSo I guess in order for this to happen, as with many things in WordPress, bodies need to be on the ground. We need people actually doing this work. There’s probably a whole lot of people listening to this who are already committing their time to translations, but there’s probably a lot of people who haven’t. So I guess we need to speak to them.
\n\n\n\nFirstly, I suppose we need to reassure people that if in the future, if this project has wings and takes off and it all goes in this direction, that they will be educated in the new ways of doing things. But also a call out to people who haven’t yet committed their time and feel that they could commit their time. How do they go about doing it?
\n\n\n\nSo let’s tackle it in two parts. The first one, to people who are already translating, will there be education materials? Will there be instruction as to whatever comes out of this whole process?
\n\n\n\n[00:32:04] Javier Casares: Okay. So for me, we will need two different teams. This is not a polyglots project in a way. Obviously everybody will be invited to participate on everything, but I don’t think that the same people translating WordPress plugins, themes or whatever, needs to be the same people translating documentation.
\n\n\n\nSo in a way, at least for me, because I think those are two very different things. As Courtney was saying, translating a plugin for example, or WordPress per se, maybe you need to be a little more literal in the translation. But documentation is different because people need to learn about what you are explaining. So you need to relate with that person.
\n\n\n\nSo in this case that’s the work Estela is doing. You need to know how to communicate to these people, and that’s very different than translating a thing. So for me, it’s not like translating documentation is adapting or doing your own documentation based on one in another language.
\n\n\n\nSo we don’t need to have the same documentation because, cultural things or whatever. Because not everybody in all the countries, in all the languages, use the same tools, the same things. So that’s one thing we need to have in mind. For example, as I was saying at the beginning, I just started leading the advanced administration handbook like one year or two years ago. That’s something Milana gave me as a gift in a way.
\n\n\n\nSo one thing I started, for me this is the pilot in the technical part, not in the documentation part. But now the only thing, or main thing we have in GitHub, in English, everything synchronised with WordPress, is the advanced admin handbook. So for me the next step is to do the technical part for this translation.
\n\n\n\nWe need to check also the technical part because writing right is one thing, but doing the thing is another step we need to check. And that creates a lot of new problems in a way. Because we have new content, we have updates, and we have changes in the documentation. Because it’s not the same changing or creating a new feature, because I don’t know the command palette and everything. It’s a new thing from one, two versions ago.
\n\n\n\nSo we need to create all the documentation. We need to notify everybody in all the languages that we have this new. So we need to translate everything and we need to check with the Polyglots team, how are you going to name the palette in your language and everything? Everybody should be involved in a way, because documenting in all the languages should be a global thing, not a local thing.
\n\n\n\nAnd also, the notifications. We need to have like three levels in the translation part, because we need the translators. We need people doing the translation per se. And we need something like the GTEs. So people can check that the translation is doing fine, the translation is right. And we need project managers because each documentation is not the same. The advanced admin handbook, the end user documentation, the Learn WordPress whatever, the plugins handbook, the themes handbook, developers handbook. Each documentation needs one or two or a team that can control the publication that everything is right.
\n\n\n\nFor example, one thing we talk in WordCamp US was how we are going to relate it’s language? Because we don’t have that now. So if we publish the documentation in Spanish and somebody wants to go from this page to another language, how are we going to do that? Because that’s not something we have now.
\n\n\n\nSo we are trying to solve phase four before we have phase four. So we have a lot of challenge in the organisation and in the technical part. Also with the translation or the organisation about how we are going to talk to people. Because, for example, the Spanish for me is one of the best examples, because in Spain we have a more direct, we talk to people and in Latin American they talk in another way.
\n\n\n\nSo we need to find like a common ground because we cannot maintain the Spanish documentation in 12 or 15 different ways. So we need to create a standard or international Spanish. That’s something that more or less exists, but we cannot create a lot of different documentation. So we need to have that in the translation part. We need to have that documentation, that style guide. We need to have one international Spanish because we cannot maintain, we don’t have a lot of people maintaining some little languages or whatever, because it’s not possible right now in the WordPress ecosystem.
\n\n\n\n[00:37:35] Nathan Wrigley: Thank you. That was really insightful. I got an awful lot out of that. I just have a little question off the back of that. So, is the intention then to build I guess more or less software to take care of this notification problem? And obviously there’s a lot more than notifications. There’s, you know, the work that needs to be done, and perhaps the order that it needs to be done, and who it’s going to be assigned to.
\n\n\n\nIs the intention to have that as, if you like, paper based web pages or is the intention to have a piece of software that people can log into and assign themselves tasks, and offload tasks, and check things out, and then finally hit publish if something meets all of the different criteria? And it sounded like it was partially done but I don’t know if that’s falling on your shoulders Javier. Just a little guidance around that.
\n\n\n\n[00:38:18] Javier Casares: Yeah. that was one of the main things we have pending. We started talking about this in WordCamp US, in the contributor day. Right now, for example, for the advanced admin handbook I’m going to lead everything in the Spanish part because I think we need to test everything, and I’m going to test this development part or whatever we are doing. I know Milana is doing it for the end user. She’s creating like teams in GitHub and doing actions and everything.
\n\n\n\nShe’s starting to automatising more or less the notifications and everything. So the main idea is we will have translation teams. So for example, the Spanish translation team, or the German translation team. And you will apply in those teams. And when something changed, in the English part, you will get a notification.
\n\n\n\nFor example, there is a new page. This document has changed because of whatever. So we need to inform people that we need a new version, or to update something, or to add something to the documentation. And then we need another step that when somebody translates something, it needs some checking or review or whatever. So we need like the GTEs in Polyglots more or less, the general translation editor. So people that know imperfection, the style guide or whatever. And they will check that this document is ready to be published.
\n\n\n\nThis is something we start talking and I think it will be something good for the project, is to create versions for the documentation. When we have 6.4 or 6.5 or whatever version, we can create a new batch of documentation, and we can create the 1.2 version of the end user documentation. So we can have a history of everything that changed, and we don’t need to put the documentation every day.
\n\n\n\nSo we can have a weekly or a monthly updating. So it’s control, it’s more like the WordPress. So everybody will know where the new version is going to be published. If you need to add this document, priorities or whatever. So that’s something we are working on now, but there are a lot of people involved testing different things.
\n\n\n\nSo for example, Estela is doing the documentation for Spanish. I’m testing the technical part. Milana is testing this notification system. So we need to check everything because we don’t really know if this project is going to be real, but we think it will be. But we need to check everything, and we need to do this in parallel because we cannot wait to have all the work from one person to do the next step.
\n\n\n\nI think that’s something we are going to work on in the next contributor days in some places. At least in Spain I’m going to try to do this. And for example, that’s my next step in the documentation part, is going to test this technical part. How are we going to organise everything?
\n\n\n\nSo everybody is invited to participate. So if anybody wants to check things, we can talk. Probably in the Polyglots or the documentation channel in Slack. So I think a lot of people are doing the right steps right now, and before 2024 we have some pilot or something finished.
\n\n\n\n[00:42:02] Nathan Wrigley: If you’ve ever been involved in creating software, you’ll know that the devil is in the detail. And although it’s easy to say what you’ve just said, I suspect that it will be fiendishly challenging.
\n\n\n\nFirstly, good luck, I hope that your endeavors pay off. And it does sound like you would desperately want some people to cast their eyes over this.
\n\n\n\nAnd we’ll get onto that in a moment. We’ll figure out a way where people can get in touch if they wish to. But you’re clearly all good people. You have the, what I’m going to describe as the right moral intentions here. You are giving up lots of your time for this worthy cause. Nobody could deny that this is a fabulous endeavor.
\n\n\n\nBut for people who are listening to this and sitting on the fence, thinking to themselves, what would I get out of translating? It’s a bit of an ephemeral question really, but I’m wondering if you could portray or explain to us, what do you get out of this? Apart from the fact that you’ve translated a software project, that much is obvious. But, do you get like a warm, fuzzy feeling out of this? Does it make you feel good? Is there a good community? Are there nice people sitting behind translation that you’ve become friends with? I’m trying to offer a path for people who kind of want to commit but haven’t committed, because they just see it as there’s more things to do on my plate each week.
\n\n\n\n[00:43:13] Estela Rueda: I think that friendships, they just come. They are just like part of it. But that’s not the reason why I do it. For me it’s more about empowering people. I think that, you know, if I can translate more of the documentation in another language then there will be more plugin developers, or theme developers, or agencies in that country. And then you will empower people. You will empower more people because they will be able to start their own businesses, you know, create their own little plugins and start small like we all did at some point, and then become bigger and bigger.
\n\n\n\nI don’t know, I kind of took into that Matt’s dream about a hundred years. I think that if we open everything up for more countries, more cultures to join, then WordPress will be bigger and bigger and more people will use it.
\n\n\n\n[00:44:10] Nathan Wrigley: Thank you so much, Courtney. I think maybe you want to chip in there.
\n\n\n\n[00:44:13] Courtney Robertson: I really love solving complex puzzles. And so if we look, devils in the details. Relaying communications between docs and training becomes pretty important. So not only do we want to leverage Milana’s system about the GitHub actions, some of that automation work that can notify people in other languages. But also the communication between the teams about the same topics or the areas in which our topics overlap. It’s a fun thing for me to do that.
\n\n\n\nBut then in addition, as I kind of look more broadly like Estela, I firmly believe in empowering others. And that’s really what open source and the four freedoms give us. You are free to do what you would like with this thing.
\n\n\n\nSo to make that possible my method is to solve big problems, I guess. To work on these interesting challenges so that more people can leverage what’s going on and get involved along the way, and have mentors and others to connect with. Because for every time that I felt personally like I didn’t know what was going on, or I didn’t understand the value that I brought, or understand how I could start contributing with something small, I want to remove those barriers for other people. I want to make their lives a lot better from that process.
\n\n\n\n[00:45:34] Nathan Wrigley: What a fabulous set of answers. Thank you so much.
\n\n\n\nWe’re running short of time. I guess the only thing that we should say before we wrap up is to give out a shout to people who are sitting on the fence, who haven’t contributed so far. What is the best way, the quickest route to finding out more? Is there a particular page that you would highlight more than any others? Is there a particular venue to go to? Is this a contributor day kind of thing? What would you recommend? We could take that one at a time. So let’s start with, well let’s go back to Courtney.
\n\n\n\n[00:46:05] Courtney Robertson: Sure. Since our process looks a little bit different than what you see in Docs, for instance, I would encourage folks to swing by the training team. You can find our main site at make. wordpress. org slash training. There is a handbook in our top navigation area and inside of that has some information on how to get started with content localization. I’ll make sure that we have all those show notes. As well as a GitHub issue to log if you want to take part in that translation effort.
\n\n\n\nAnd for those inside the WordPress project that are really skilled with amazing things like GitHub Actions, if you understand how to make GitHub automate some stuff, there is a channel if you search for GitHub inside of the channels area, you’ll find a channel where we share tips and tools about GitHub activity.
\n\n\n\n[00:46:51] Nathan Wrigley: Thank you so much, Courtney. Estela, anything that you wanted to add?
\n\n\n\n[00:46:55] Estela Rueda: You can go into documentation Slack channels. We meet on Tuesdays, 2 PM UTC, and just join us. And then we can talk about it. We are trying to look now for Documentation writers, but they are also bilingual. So they do need to dominate at least one word so that they can help us in the future once we move into their own language.
\n\n\n\nWe have, actually the documentation team is, most of us are non English speakers. English is not our first language, so we have a lot of people that speak other languages, and they do help when it’s necessary. Now, we have several posts. I’m posting, like I said, I’m documenting what I’m doing, and we’ll be documenting it both in Documentation and polyglots, and just pick it up from there. Join the polyglots team. They are open to every language, or every Rosetta side, locale team. They all need contributors. They all need translators. So that’s the best way.
\n\n\n\n[00:48:01] Nathan Wrigley: Thank you so much. And Javier, if you’ve got anything to add there.
\n\n\n\n[00:48:05] Javier Casares: Yeah. In my case if anybody wants to check the most technical part or be involved in the testing, they can ask me directly in Slack. Because right now it’s like I’m doing the test alone. I probably when I do the main testing, I will explain everything because we did the proposal in the make.wordpress.org slash project. You can look for a proposal, documentation, translation, localization.
\n\n\n\nThat’s the main document explaining everything. It explains why we are doing this. How we are going to do that. I think, right now, Estela, Courtney, Milana, and I are the ones involved. So another way is to, at least for this project, is to contact us, and we will try to put you in the right place to contribute.
\n\n\n\nYeah, we are always open to help people. So another way is to contact directly to us.
\n\n\n\n[00:49:09] Nathan Wrigley: Well, Thank you so much, the three of you, for joining us today. Thank you Courtney, Estela, and Javier. I really appreciate it. Obviously, a very complicated set of challenges to come, but hopefully with your and other people’s contributions, WordPress will be readable by all the world. Thank you so much for your contributions today.
\nOn the podcast today we have Estela Rueda, Courtney Robertson and Javier Casares.
\n\n\n\nCourtney is a former teacher who now focuses on contributing to WordPress. With a background in education, she understands the challenges faced by English Second Language (ESL) learners in the American education system. She’s passionate about providing access to WordPress in multiple languages, as she believes it is unfair to expect non-English speakers to simultaneously translate content and understand it.
\n\n\n\nEstela is a language enthusiast who has spent years navigating the challenges of website localization. As a member of the WordPress community, Estela has come across the intricacies of language differences and the need for accurate translation in various Spanish locales. With 14 different Spanish locales to handle, Estela’s expertise in understanding the subtle nuances and localizations of each language variation has been indispensable.
\n\n\n\nJavier Casares is a dedicated member of the WordPress community. With expertise in creating documentation, Javier has been instrumental in developing handbooks for various sites. However, there have been some technical challenges. Despite these obstacles, Javier, as you will hear, remains committed to addressing and solving the documentation issues at hand.
\n\n\n\nThis episode covers the important topic of translations and making WordPress documentation more accessible to people worldwide. Our guests bring a wealth of knowledge and experience to the table as they discuss the complexities and challenges of language translation in the WordPress ecosystem.
\n\n\n\nWe start by highlighting challenges posed in translating WordPress, such as the tangled processes currently in place, as well as more language focussed topics. We talk about the extensive collaborative effort involved in translating WordPress and the plans to expand translation efforts to documentation with the help of dedicated teams.
\n\n\n\nWe get into how contributors might need to rethink the way that many of the current translation processes are structured. We discuss the different approaches needed for translating plugins and themes versus documentation. We touch upon how technical aspects of these processes, such as content creation and updates, also pose significant challenges.
\n\n\n\nAll three guests stress the importance of global involvement in translation efforts, including translators, reviewers, and project managers. They advocate for the development of standardised style guides for each language to maintain consistency, and they explore the possibility of creating software or tools to manage translation tasks.
\n\n\n\nCourtney, Estela, and Javier all acknowledge the challenges ahead, but express optimism that their ideas will help make WordPress accessible for all. Communicating how WordPress is built and how it works is an endeavour tightly aligned with the project’s overall mission of democratising publishing.
\n\n\n\nWe want to offer non-English speaking people the possibility to access all the WordPress documentation in their language. To accomplish that we need to translate all the actual documentation at HelpHub, DevHub, Learn WordPress and some Handbooks.
\n\n\n\nBut, the problems are not to do the translations per sé, but where to put that in each language, how to get the updates from the English primary documentation, and then how to maintain everything in place.
\n\n\n\nFirst, we need to know where are we putting the documentation, because this project cannot wait until Gutenberg Phase 4. This means that Local Communities should be involved here (for example, where are we putting the documentation in Spanish? es.wordpress.org/documentation, developer.es.wordpress.org?)
\n\n\n\nAfter having the right place… how are we going to know if something changes? The best way is probably using the same way we are translating right now: translate.wordpress.org, (GlotPress). If we can use this platform, each page can be translated and, when arrived to the 90% threshold, it will be shown in the local language page.
\n\n\n\nDiscussion for a proposal for WP.org content translation and localization
\n\n\n\nNew look, new site, new HelpHub
\n\n\n\n\n\n\n\n\n\n\n\nGitHub… Issue: Content Translation Template
\n\n\n\nProposal: Documentation translation / localization
\n\n\n\nWordPress Advanced Administration Handbook
\n\n\n\n\n\n\n\nPrevious podcast episodes with Piermario and Vagelis
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 15:15:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"Do The Woo Community: Do the Woo Day 2 Recap, WooSesh 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77699\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://dothewoo.io/do-the-woo-day-2-recap-woosesh-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:370:\"Conversations around AI and customer support, Amazon Pay, personalization and privacy in ecommerce and shipping trends.
\n>> The post Do the Woo Day 2 Recap, WooSesh 2023 appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 12:23:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"HeroPress: From Sci-fi Dreams to Software Reality\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=5985\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:150:\"https://heropress.com/essays/from-sci-fi-dreams-to-software-reality/#utm_source=rss&utm_medium=rss&utm_campaign=from-sci-fi-dreams-to-software-reality\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7038:\"Growing up, my family didn’t have much. Yet, a quote always resonated with me: “If you’re born poor, it’s not your fault. But if you die poor, it’s your fault.” My humble beginnings never deterred my aspirations.
\n\n\n\nAs a child, my exposure to technology was limited. In our village, neither schools nor homes had computers or mobile phones. My fascination with technology was sparked by sci-fi movies I watched on television, where characters operated these machines called “computers.”. That first moment when I laid my eyes on a computer, I knew my life was about to change. The real encounter with a computer came in 2006 when a neighbor purchased one.
\n\n\n\nIn 2008, My family moved to the town and it opened up a world of opportunities. Later that year a friend introduced me to a Cyber Café, where for just 20 Indian Rupees (24 cents US), I could play games for an hour. After saving the money for two weeks, I visited the café for the first time. Over time, my interest shifted from playing games to exploring the computer itself. It was a Windows XP machine, and I recall being intrigued by its features. This exploration continued almost every month for the next two to three years.
\n\n\n\nBy 2011, I had become proficient with the internet and was familiar with operating systems like Windows, Linux, and Mac. That year, my father bought me my first phone, a Nokia 7210 Supernova. While it wasn’t a smartphone, it sparked my curiosity about the creation of software and websites.
\n\n\n\n\n\n\n\n\nI researched “how to make a website” and encountered HTML and CSS.
\n
Initially overwhelmed by the complexity, I decided to push forward, and by the end of the year, I had launched my first website using an online builder and my Nokia phone.
\n\n\n\nMy passion for technology only grew from there. I self-taught programming languages like JavaScript, PHP, Python, Java, C, and C++. I also learned computer hardware maintenance and served as a go-to tech helper in my community. Impressively, I became a full-time Teacher and SysAdmin for a local school, managing five servers and around a hundred computers. All of this knowledge came from internet tutorials.
\n\n\n\nI truly developed a passion for web technologies.
\n\n\n\n\n\n\n\n\nMy first encounter with WordPress.com in 2012 was underwhelming, as I perceived it to be just another blogging platform like blogger.com.
\n
Yet, a few months later, my discovery of WordPress.org profoundly shifted my perspective. By 2014, I had set up my own WordPress blog. Despite juggling a demanding college schedule and coursework, I consistently set aside time each night to keep up with the latest developments in WordPress and other web technologies. Much of what I’ve learned comes from the generosity of online communities. In gratitude, I’m eager to share my own experiences, hoping to guide others on similar paths.
\n\n\n\nBeing a teacher was a fulfilling and enjoyable experience. One of the highlights for me was the opportunity to share my knowledge with the children and witness their growth and development. Teaching stands out as one of the most rewarding endeavors of my life.
\n\n\n\nDriven by a strong desire to delve deeper into web technology, I realized I had become too comfortable in my current role, working as a Teacher. In October 2020, I made the difficult decision to leave my teaching position and venture into the realm of Web Technologies. This decision did not come easily, as I had no alternate source of income and my savings were limited, only sufficient to last a few months. For the next three months, I found myself unemployed, but I utilized this time to extensively explore web technology, with a particular focus on WordPress.
\n\n\n\nDespite grappling with imposter syndrome at the time, I was completely unaware of its impact on me.
\n\n\n\n\n\n\n\n\nI found myself reluctant to apply for job positions at various companies, filled with doubt about my abilities, and questioning whether I had acquired sufficient knowledge or was proficient enough to undertake the work.
\n
What I failed to realize then was that all I needed was a little push—a smidgen of encouragement—to help me advance with the skills and knowledge I possessed. I am immensely grateful to Topher DeRosia for providing me with that much-needed push. His encouragement was priceless, and it spurred me to send my resume to three different WordPress-related companies. To my delight and relief, I received a response from one of them.
\n\n\n\nFrom those early days in the cyber café to securing a position at rtCamp, my journey has been anything but ordinary. In light of my experiences and the passion I developed from my early encounters with technology, I secured a position as a WordPress developer at rtCamp in February 2021. This was a significant milestone for me, especially recalling my days without a computer in my village and the hours spent in cyber cafes learning the complexities of the digital world. The journey to this point was challenging, especially since I navigated it largely on my own, without a mentor or assistance from anyone./
\n\n\n\nNow, working full-time with WordPress, not only am I able to comfortably cover my bills, but I can also provide for my family.
\n\n\n\n\n\n\n\n\nMost crucially, it has enabled me to fund my brother’s necessary neurological treatments.
\n
I’m delighted to share that he has successfully recuperated and no longer requires medication.
\n\n\n\nThroughout this path, I’ve faced countless challenges, sleepless nights, and stress. Yet, one truth remains clear: moving forward, no matter the obstacle. Failures are just milestones, not endpoints. With perseverance, success is not just a destination but a beautiful journey. If you’re facing doubts about your abilities, remember, we all start somewhere. It’s the perseverance that counts.
\nThe post From Sci-fi Dreams to Software Reality appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Nov 2023 00:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Tremi Dkhar\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"WPTavern: WooCommerce Rebrands as Woo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150841\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/woocommerce-rebrands-as-woo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2569:\"WooCommerce is rebranding to “Woo,” a shorter, more playful version of the company name that many customers are already using. Automattic acquired WooCommerce in 2015, along with WooThemes. The open source commerce platform now powers more than 4.4 million live websites, including 33% of the top 1 million online stores.
\n\n\n\nThe rebranding extends to the Woo Marketplace, WooExperts program, and all other aspects of the Woo experience. It also includes a migration of WooCommerce.com to the woo.com domain.
\n\n\n\n“‘Woo’ is how many loyal customers have referred to us for years. And now we’re leaning into that name for our company and brand,” Woo VP of Creative and Communications David Callaway said. “It’s a fun, punchy name that shows how excited we are to empower success for merchants and developers. Switching to Woo.com is part of this larger strategy.
\n\n\n\n“The move to Woo also allows us to standardize and streamline the names of our products and services. For example, we recently renamed WooCommerce Payments to WooPayments, and we’re gradually changing other product names to support this simplified naming system and better connect our core software, extensions, and programs.”
\n\n\n\nCallaway also noted that while Woo is how they refer to the brand and company, WooCommerce is the open-source e-commerce platform for WordPress, Woo’s core product.
\n\n\n\nWoo Express is another recently launched product that already bears the shorter name. During the 2023 State of the Woo, delivered at WooSesh, the team highlighted a few milestones for Woo Express, the company’s all-in-one Woo plan hosted on WordPress.com’s infrastructure. It launched in 2023 as what the team described as “Woo’s biggest bet ever.” Free trials began in April 2023 and by July 2023, Woo Express had more than 1,000 customers. It features a new onboarding flow and store personlization experience for merchants, with a setup guide and recommendation engine powered by an AI-driven assistant.
\n\n\n\nWoo customers will not be affected by the name change, although merchants may see a note about it in their dashboard or emails. No action is required from store owners.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 31 Oct 2023 12:51:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:43;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"Do The Woo Community: Do the … Woo dot Com\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77718\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://dothewoo.io/do-the-woo-dot-com/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:335:\"Inside Woo. Today the WooCommerce site becomes Woo.com as a strategic part of their branding and product line.
\n>> The post Do the … Woo dot Com appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 31 Oct 2023 12:12:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:44;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"Do The Woo Community: Do the Woo Day 1 Recap, WooSesh 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=77694\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://dothewoo.io/do-the-woo-day-1-recap-woosesh-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:372:\"Day one started with State of the Woo, conversations on open source and hosting, scalable ecommerce and website security.
\n>> The post Do the Woo Day 1 Recap, WooSesh 2023 appeared first on Do the Woo - a WooCommerce and WordPress Builder Podcast .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 31 Oct 2023 10:54:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"BuddyPress: BuddyPress 11.4.0 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=331729\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://buddypress.org/2023/10/buddypress-11-4-0-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1054:\"Immediately available is BuddyPress 11.4.0. This maintenance release fixes 1 bug and adds a new Admin Notifications feature to prepare the next BuddyPress major version (12.0.0). For details on the changes, please read the 11.4.0 release notes.
\n\n\n\nUpdate to BuddyPress 11.4.0 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.
\n\n\n\n\n\n\n\nvapvarun, martenw, dcavins & imath.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Oct 2023 20:58:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WPTavern: WP Data Dashboard Tracks WordPress.org Themes Ecosystem\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150809\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://wptavern.com/wp-data-dashboard-tracks-wordpress-org-themes-ecosystem\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7244:\"Munich-based digital agency owner Hendrik Luehrsen has been tracking the usage of themes with the FSE tag (block themes) using a spreadsheet that pulls in data from the WordPress.org API. Wrangling the data in a spreadsheet became too cumbersome, so Luehrsen launched WP Data Dashboard over the weekend as a “centralized hub for exploring, analyzing, and visualizing data across the WordPress landscape.”
\n\n\n\nThe new website is currently tracking 6,017 themes hosted on WordPress.org with 250 snapshots. It offers stats and data-based insights for those interested in getting a bird’s-eye view on themes hosted in the official directory.
\n\n\n\n\n\n\n\n\n\n\n\n“Right now, the WP Data Dashboard has one main function: It crawls the WordPress Theme Repo (API) and crunches the numbers to identify trends,” Luehrsen said. “With the data stored in my own database, I can analyze and combine it in exciting new ways.”
\n\n\n\nWP Data Dashboard has two unique stats that are interpretations of the data available. The first is a “Usage Score,” which is calculated based on a theme’s active installs vs. total downloads:
\n\n\n\n\n\n\n\n\nA high score indicates a theme that not only has been downloaded frequently but also remains actively installed on many sites. The score undergoes a significant decay if the proportion of active installs to downloads is low, indicating that while the theme might be frequently downloaded, it’s not retained by users. This metric provides insight into both the initial appeal of a theme and its lasting utility to users.
\n
The second unique stat is a “Diversity Score,” which compares the downloads of a single theme author to the overall theme directory (or a tag) and scales that value from 0 to 100:
\n\n\n\n\n\n\n\n\nA high score indicates that downloads are spread across many authors, suggesting a diverse and competitive marketplace. On the other hand, a low score suggests that a few authors dominate the downloads, indicating less diversity. This metric provides insight into the variety of theme offerings and the balance of power in the theme marketplace.
\n
The Usage Scores can be seen on the List page, which is an index of all the themes, as well as on the Tag pages.
\n\n\n\n\n\n\n\nThe Diversity Score is only displayed on the Stats page as a percentage representing the entire WordPress.org ecosystem. The Diversity score goes up when the stats are calculated without the default themes, which get a large number of downloads from the same “WordPress.org” author every year.
\n\n\n\n\n\n\n\nIn a thread on X, Luehrsen highlighted a few data points he has extracted so far from the dashboard.
\n\n\n\n“Fun fact: Did you know that the most downloaded themes ever are Twenty Seventeen, Twenty Fifteen, and Astra?” he said. “Each has crossed over 10 million downloads! But only Astra managed to retain its users and remains today as one of the most widely used themes.
\n\n\n\n“What’s somewhat surprising is the decline in downloads for the newer default themes. While Twenty-Twenty garnered over 8 million downloads, Twenty Twenty-One managed only 6 million, and Twenty Twenty-Two a mere 3 million.”
\n\n\n\nThis may be related to the slow adoption of block themes, which still appears to be stagnating at the end of October. The number of block theme active installs declined from August to September, but is now inching its way back up to previous numbers.
\n\n\n\n\n\n\n\n\n\n\n\n“Did you know that only 2% of overall theme downloads come from themes tagged as ‘Full Site Editing‘?” Luehrsen said. “Given that they’re relatively new, it’s not too surprising!”
\n\n\n\nWhen asked if he has considered trying to include numbers for themes like Elementor and Divi, which make up a large segment of the commercial theme market, Luehrsen said he would like to include external data but the compatibility of that data would be very limited, which in turn limits comparability with WordPress.org-hosted themes.
\n\n\n\n \n\n\n\nThe WP Data Dashboard is a useful way to track trends in WordPress.org themes over time, and the site appears primed to add data for plugins at a future date. It would be even more helpful if Luehrsen could make some of the calculated data available for visitors at a glance, such as 2% of overall theme downloads coming from Full Site Editing tagged themes. There are a lot of ways this data could be visualized with graphs and charts in the future, as the database adds more information over time.
\n\n\n\nThe project is hosted on GitHub under a GPL license, so anyone can dig deeper into the code to see how it works or submit contributions to extend its capabilities.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Oct 2023 20:30:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"WordPress.org blog: WP Briefing: Episode 65: Little Sun Success\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=16227\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://wordpress.org/news/2023/10/episode-65-little-sun-success/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:21522:\"Join WordPress Executive Director Josepha Haden Chomphosy as she looks at a recent WordPress success story, the clean energy solution Little Sun, and learns about their WordPress story.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Special Guest: Romane Guégan
Special Guest: Ashley Mrozek
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[00:00:00] Josepha: Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[00:00:28] (Intro music)
\n\n\n\n[00:00:40] Josepha: Today, I’ve got a special guest with me. I have here a couple of folks from Little Sun, a nonprofit organization that recently moved its entire online presence to WordPress. And we’re talking everything from their mission statement and donations all the way to their blog and shop.
\n\n\n\nWelcome both to the WordPress Briefing.
\n\n\n\n[00:00:59] Ashley: Thank you.
\n\n\n\n[00:01:00] Romane: Thank you.
\n\n\n\n[00:01:01] Josepha: We have with us Little Sun today. Can you start by introducing yourselves and your organization? Just tell us a little bit about what you all do.
\n\n\n\n[00:01:08] Romane: Hi, my name is Romane Guégan. I’m a Senior Press and Communications Manager at Little Sun.
\n\n\n\n[00:01:14] Ashley: And I am Ashley Mrozek. I’m the Senior Digital Manager.
\n\n\n\n[00:01:17] Josepha: So what does Little Sun do for the folks who are listening and maybe don’t know about it yet?
\n\n\n\n[00:01:22] Romane: Little Sun brings full power and light to communities that live off the grid, with the focus on sub-Saharan Africa because most of the people who lack access to electricity and need them. And we also inspire people to take climate action globally.
\n\n\n\n[00:01:39] Ashley: So access to solar energy helps kids who don’t have electricity and study at night. They can complete their homework at night. If their schools are in a more rural area, they will have a light to kind of guide them back home.
\n\n\n\nWe also work on a lot of electric vocation projects and hospitals. So we’re, we’re kind of supporting labors that are, are taking place in the evening, after the sun goes down, among other things.
\n\n\n\n[00:02:07] Josepha: Yeah. It’s, I, I think that that is one of the things that folks, probably most of my listeners, probably take for granted, like the easy access to light. And as we all know, the sun is around a lot. And so that is one of our most readily available resources other than potentially wind power. But I think that that is a great mission. And I really think that that’s wonderful work that y’all are doing.
\n\n\n\nSo, is there a particular reason that you focus on sub-Saharan Africa? Is that where you find a majority of people who don’t have access to that kind of resource are?
\n\n\n\n[00:02:43] Romane: Yeah. 70% of those people actually need in sub-Saharan Africa, where solar is actually a viable source of energy. Actually, it’s only 1% of solar, of the solar capital of the generation when we actually deliver solar energy there because there is so much potential.
\n\n\n\n[00:03:04] Josepha: That’s amazing. So you said that you all were funded in 2012. I imagine that your business has evolved over time. So, obviously, you all are WordPress users. That’s why we have you here with us today. But before we get into the questions about WordPress itself. Why don’t you tell us a bit about how your business needs evolved over time and how you wound up needing a solution that did use WordPress?
\n\n\n\n[00:03:31] Ashley: So I would say our focus and kind of the different initiatives that we’ve taken on since 2012 have shifted a lot based on various reasons, where our donors are, where we’ve kind of found the most need, and where we can be the most impactful.
\n\n\n\nAnd I think as we go into those new geographies, our online presence has become more and more important.
\n\n\n\n[00:03:55] Josepha: So, before you all switched to WordPress, I understand that you had several sites that you had to merge into one. And so I assume that as you evolved the business and your focus has changed, you realized you needed something a bit more streamlined. So, how was that transition, that migration from a lot of different sites to one big site?
\n\n\n\n[00:04:17] Romane: Yeah, because we started as a global project. And then, with the time, we evolved, actually also getting new donations. And in the past, we used to have one website where we have our webshop and our mission, our vision, all of our project descriptions.
\n\n\n\nBut then we had another website only for the foundation. And then you had another foundation in the U.S. So it was the question, okay, how do we put everything together? So we actually switched from littlesun.com to littlesun.org with WordPress, and it was amazing to see how we managed with the team to create an ecosystem approach, including impact, but also sales, and fundraising.
\n\n\n\n[00:05:02] Josepha: That was a big footprint that you all had, and you kind of consolidated it into one. And for all of our folks listening on the podcast, I’m going to include some links, not only to their site but then also to a few other things that we’ve mentioned in here today. So, since you made that change, how has it, how has that impacted the way that you all work with your site or with your online presence?
\n\n\n\n[00:05:27] Ashley: Yeah, I think using WordPress and having access to WordPress has been hugely valuable for us. We’re a small team, we’re a nonprofit, so it is pretty scrappy. Everyone is kind of doing a lot of different things. We don’t have a dedicated development team. And so being able to easily customize our pages and create new landing pages or make adjustments on the site without that development help has been valuable.
\n\n\n\n[00:05:55] Josepha: Yeah, so you don’t have a developer team now. Did you have a developer team when you had all the sites?
\n\n\n\n[00:06:01] Romane: We just still work with freelancers.
\n\n\n\n[00:06:03] Josepha: Okay, yeah. I am also not a developer, for what it’s worth, and have been working with nonprofits for a while. And I understand that problem where you have all these things you need to do and want to do, but there are also things you absolutely have to focus on in order to make your mission possible and your vision come true.
\n\n\n\n[00:06:23] Ashley: Yeah, and I think, I think WordPress has given us a lot more, like a lot more flexibility to kind of produce new content quickly. And because of that, it’s just been a lot more efficient, too, for us, you know.
\n\n\n\n[00:06:38] Josepha: And you all are using Blocks? Are you, like, the best Block builders?
\n\n\n\n[00:06:42] Romane: Yeah, I love Blocks.
\n\n\n\n[00:06:43] Josepha: Blocks are a fairly new innovation for the history of WordPress. WordPress has been around for 20 years, so we’re a nice, mature project. And we’ve really only had blocks as a functional part of the CMS for probably the last five or so. We’ve been working on the project a little bit longer. And it has been fascinating to me, like, in my own work that I have done with WordPress, kind of outside of my work with the project, to see, like, how much autonomy you get to have back as somebody who is not a developer, maybe isn’t a designer, but you do know exactly what you need to have on your site today, right?
\n\n\n\nAnd having to stop and find a freelancer or stop and find some set of developers who can make those changes. For me, when I was specifically working on nonprofit stuff. That was always kind of a moment where I was like, well, I guess I’ll just go to Facebook and put that on there or something because I was faster than trying to find someone to come help you. And so, I’m so glad you love the block.
\n\n\n\n[00:07:48] Ashley: We’ve created many a landing page.
\n\n\n\n[00:07:50] Josepha: Also, your site is adorable, and your brand is adorable, in case no one’s mentioned that lately. Super cute. Super cute.
\n\n\n\n[00:07:58] Josepha: So, we’ve talked about how you kind of took a bunch of stuff and made it into one big thing and how that’s been easier for you all to manage it. But from the standpoint of just, like, somebody who’s running a nonprofit, someone who’s running an organization, how has that transition been for your team? I know you said you don’t have a huge team, but was the move toward WordPress a net benefit over time, or was it immediately beneficial? Like, how has that been for your team?
\n\n\n\n[00:08:27] Romane: So what’s interesting actually is that we have a team that is spread also all over the world. And so we have teams in Berlin and in U.S., and New York. In Zambia, too. What was really interesting was how people identify to the new website because now we have to really think, okay, what is the content we want people to see, but also we want our critics to see. And so it kind of unified all of our content at Little Sun. And it was much more like much easier to understand afterwards.
\n\n\n\n[00:09:03] Josepha: Yeah.
\n\n\n\n[00:09:04] Romane: And it was because we also work at the intersection of creative communications, impacts, fundraising, technology, and to be able to put everything and have it on the front. And then have the stories to tell the stories from sub-Saharan Africa, from universities who got either a Little Sun lamps or solar systems, and then we have the donation page, so basically everything could be integrated in a super easy way, and it could target different audiences easily, either it’s someone who wants to partner with us, or a donor, or just someone who wants to be part of our solar training.
\n\n\n\n[00:09:46] Josepha: Yeah, and I mean, I think that no one will be surprised to hear that if you have multiple things that you have to get everybody to, it really increases the amount of marketing that you have to accomplish, rather than having one place for everyone to go too, and they can see everything that they might want once they arrive. So, that’s wonderful.
\n\n\n\n[00:10:06] Ashley: I think I was just going to say, or kind of echo what Romane said about the fact that we have so many different audiences, we have partners, we have donors, we have people who are just coming to learn about solar energy, or who are interested in purchasing a lamp. I think prior to this, it was a little bit confusing for those different audiences to kind of navigate to where they were intended to go to on the site, and now it’s much more cohesive. And we often hear that from people where it’s like, it’s quite easy to, to kind to find what they need to find on the site.
\n\n\n\n[00:10:39] Josepha: I define the WordPress community as anyone who is using WordPress, regardless of whether they know it or not. And so you all, in my mind, are part of the WordPress Community. And I just wondered if being part of that community has changed your approach to the way that you manage your content online or the way that you have chosen work with your business as like an online entity that also does on-the-ground, in-person thing?
\n\n\n\n[00:11:06] Ashley: I think definitely. I think we’re kind of going back to what I said before. I think we’re much more efficient now. I think in the past, it’s the idea of, like, well, getting this web page live or publishing this is going to be, you know, we have to think about a huge timeline, that’s, is going to require a lot of resourcing, a lot of different types of expertise and people, and everything now feels like something that we can, we can launch pretty immediately, which is really wonderful too.
\n\n\n\nI would also say just like being a part of the WordPress community too. It’s the sort of support that we’ve gotten from your team. It’s always really tailored. And I think as a nonprofit working with a, like, a much bigger business, you can be apprehensive sometimes, feeling like you won’t really get that personalized support.
\n\n\n\nAnd I think that’s something that’s been so nice with WordPress. Is really feeling like the people we’re working with are understanding our business and taking the time to understand our needs. And I think that makes us think differently about our online presence as well because then we feel like we have that additional support, which is great.
\n\n\n\n[00:12:12] Josepha: I’m always a fan of hearing that people who are passionate about WordPress are also passionate about helping others with WordPress. That’s one of my favorite things about us. That’s not true. I have like 25 favorite things about us. And so I need to stop saying that I have one favorite, but I never will.
\n\n\n\nOkay, well, do you all have any last thoughts that you just want to share with me or podcast listeners that we have?
\n\n\n\n[00:12:36] Ashley: Yeah, I think the, the plugins and integrations have been really useful for us. I think it can be really intimidating to bring on, like, a new tech solution or tool and feel like everything that you are already working with or have is going to become outdated or obsolete in some way. And I think it’s just been really nice to work with WordPress and have all of those transitions be really seamless for everything to connect really well. Yeah, I think that’s been. That’s hugely helpful too.
\n\n\n\n[00:13:07] Josepha: So, was that part of the decision-making process? Like, do I know that this software will be around in the future so that you’re making an investment in the site now and know that it’s going to hang around now you can find people help? Like, was that part of the decision-making process?
\n\n\n\n[00:13:21] Ashley: I think so. I mean, I guess I wasn’t completely around during the time, but I would say, like, that’s definitely something that we’re considering in any kind of tech that we’re thinking about is it can require so much work to, to kind of bring something on with such a small team. So we want to ensure that, yeah, it’s going to last, it has longevity, and it’s going to work with the tools that we already have. So I think all of that is really important for sure.
\n\n\n\n[00:13:48] Josepha: Well, thank you both so much for joining me. Like I said, we’ll have a link to littlesun.org in the notes so that you all can learn more about their project and see their beautiful site with their beautiful little solar sunflowers.
\n\n\n\nThank you both for being with me today.
\n\n\n\n[00:14:04] Romane: Thank you so much.
\n\n\n\n[00:14:05] Ashley: Thank you so much for having us.
\n\n\n\n[00:14:07] (Music interlude)
\n\n\n\n[00:14:11] Josepha: What a wonderful organization. I’m so glad that they found WordPress and that it works for them. Let’s continue our tour today with the small list of big things.
\n\n\n\nItem number one, it’s time to save the date: December 11th, 2023, for this year’s State of the Word. State of the Word is the annual keynote address delivered by the WordPress Project co-founder Matt Mullenweg. Every year, the event shares reflections on the project’s progress and aspirations for the future of open source. And so, if that is something that you like to tune into, December 11th is your day.
\n\n\n\nSecond thing on our list is that we are celebrating our 10,000th photo submission. So, on October 11th, the 10,000th photo was approved. The Photo Team is one of the newest ways to contribute to the WordPress open source project, and it feeds all of those photos into Openverse as well.
\n\n\n\nThe third thing on our list today is that I want to tell you about a community team training module that just came out. It’s specifically about the Translate Live tool, and it is ideal for presenting at your local meetups to engage and onboard new translators for your native language. If you’re organizing a WordCamp, consider introducing this tool during your Contributor Day. I will leave a link for this in the show notes so that it is easy to find.
\n\n\n\nAnd item number four, the journey to update WordPress.org, continues with the launch of a new Showcase design. The Showcase is a natural starting point for a lot of visitors who are on WordPress.org. It inspires creativity and also demonstrates what’s possible with WordPress. So, stop on by there, it’s WordPress.org/showcase, and give it a bit of a look.
\n\n\n\n[00:15:58] Josepha: And that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. And don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever a new episode drops. And if you like what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard today, you can share those with me at wprebriefing@WordPress.org.
\n\n\n\nI’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\n\n\n[00:16:24] (Music outro)
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Oct 2023 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Brett McSherry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"WPTavern: Gutenberg 16.9 Lets You Rename (Almost) Any Block, Adds Experimental Form and Input Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150720\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wptavern.com/gutenberg-16-9-lets-you-rename-almost-any-block-adds-experimental-form-and-input-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4201:\"Delivering on an highly-requested feature, Gutenberg contributors have made it possible to rename almost any block in the List View. Version 16.9 was released this week with the new feature, which builds on Gutenberg 16.7‘s introduction of the ability to rename Group blocks.
\n\n\n\nIt works in a similar way to naming Photoshop layers. Users can now open the list view, click on the ellipsis menu, select “Rename,” and enter a custom name.
\n\n\n\n\n\n\n\nvideo credit: Gutenberg PR #54426\n\n\n\n“Allowing users to distinguish between blocks in the List View is becoming increasingly important as the scope of the Site Editor grows,” Automattic-sponsored contributor Dave Smith said in the original ticket proposing the feature for the Group block. “Given that all blocks are currently labelled by the block name (e.g. Group
) it can be difficult to distinguish between them. This is especially important if your Groups represent distinct ‘sections’ of a given page/template.”
Every block can be renamed with the exception of these four:
\n\n\n\ncore/block
core/template-part
core/pattern
core/navigation
More renaming capabilities have been added in 16.9, including the ability to duplicate and rename patterns, as well as pattern categories.
\n\n\n\nThis release introduces new experimental form and inputs blocks to allow building basic forms. It’s a feature that has taken many by surprise, as few would have predicted WordPress core would be adding form building. A very early version is available under Gutenberg > Experiments, under the “Form and input blocks” experiment setting.
\n\n\n\n“Why has there been no proactive outreach to the many developers of longstanding WordPress form solutions currently used by millions and millions of WordPress sites?” Gravity Forms co-founder Carl Hancock commented on the PR.
\n\n\n\n“It seems like proactive outreach to people who are experts in this space and who could do the most to help drive adoption (beyond comments/search/etc.) would have been a good thing. On many levels. Trying to get them on board with contributing, learning from their shared historical knowledge, and even more important of all… building on top of it and adopting it instead of introducing a point of more fragmentation.”
\n\n\n\nThe forms feature is still in the very early stages of experimentation, and more information may be published to the November edition of “What’s New For Developers?“
\n\n\n\nA few other notable highlights from this release include the following:
\n\n\n\nCheck out the release post for Gutenberg 16.9 to see the full changelog and more details on bug fixes and enhancements to performance, tooling, documentation, code quality, and accessibility.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 Oct 2023 22:00:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"WPTavern: WordPress 6.4 Disables Attachment Pages for New Installations\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=150736\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/wordpress-6-4-disables-attachment-pages-for-new-installations\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4090:\"The upcoming 6.4 release, expected on November 7, will disable attachment pages for new installations. Up until now, WordPress automatically created attachment pages when users upload a file through the media upload system. It has been treated as a special post type that holds information about the file and each attachment is accessible under its own URL. SEO plugins have been redirecting attachment pages for years, as they rarely have any significant purpose.
\n\n\n\n“Until WordPress 6.4 was released, WordPress created attachment pages by default for every attachment uploaded,” WordPress contributor Joost de Valk said in the dev note for this change. “On the vast majority of sites, these attachment pages don’t add any meaningful information. They do, however, exist, get indexed by search engines, and sometimes even rank in search results, leading to bad results for users and site owners.”
\n\n\n\nThere will be no changes to existing sites. They will continue to work as they always have, but new sites will have their attachment pages redirected to the attachment URL. Site admins who want to enable or disable attachment pages can use the new wp_attachment_pages_enabled
database option to control attachment pages’ behavior.
There is no interface for changing whether a site disables attachment pages, which was somewhat controversial in the comments on the Trac ticket and the dev note.
\n\n\n\n“In light of the WordPress mantra ‘decisions, not options,’ we’ve decided against making a setting for this,” de Valk said.
\n\n\n\nWordPress plugin developer Sybre Waaijer mades a case for giving users an option with an interface for toggling it on or off:
\n\n\n\n\n\n\n\n\nThe problem with filtering options is that when another plugin provides the option toggle, the option filter will go against user expectations.
\n\n\n\nThis is where “decisions, not options” becomes paradoxical because we’re now deciding to set an option while also not giving the option.
\n\n\n\nSo, as plugins fill in this gap, then A) where will plugins put the option (likely on their custom page instead of options-media.php), and B) of the dozens of types of plugins that are in the market to juggle this, who will ultimately be in control of the option?
\n\n\n\nIf it’s a filter, each plugin promises to set a toggle via a simple condition. But since it’s an option, plugins can add an option to filter an option and add an option to toggle the option. It’ll become a source of bugs because of the logical biconditionals (XNOR).
\n
While an interface isn’t in the cards for WordPress 6.4, and may never be back on the table for consideration, contributors are discussing the possibility of putting this in a core plugin.
\n\n\n\n“Should we not have a core plugin for re-enabling attachment pages on new sites?” Automattic-sponsored contributor Justin Tadlock said. “If there’s not going to be a UI for this, then a plugin that’s not buried in a Trac ticket would be ideal.”
\n\n\n\nde Valk agreed this would be a good idea to have a plugin that simply adds a setting to the Options -> Media page. Users likely will not understand the purpose of attachment pages unless they are looking to enable them for a specific, niche use case. A plugin like this would be useful for those who are not able to write the code to change attachment pages’ behavior, as described in the dev note.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 Oct 2023 17:42:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Fri, 17 Nov 2023 12:52:26 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:13:\"last-modified\";s:29:\"Fri, 17 Nov 2023 12:45:30 GMT\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:16:\"content-encoding\";s:2:\"br\";s:7:\"alt-svc\";s:19:\"h3=\":443\"; ma=86400\";s:4:\"x-nc\";s:9:\"HIT ord 1\";}}s:5:\"build\";s:14:\"20211221003300\";}','no'),(936,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1700268746','no'),(937,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1700225546','no'),(938,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1700268746','no'),(939,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b',' ','no'),(940,'_site_transient_timeout_community-events-6718ef04d3f46d7f6ff6aabe77f33591','1700268755','no'),(941,'_site_transient_community-events-6718ef04d3f46d7f6ff6aabe77f33591','a:4:{s:9:\"sandboxed\";b:0;s:5:\"error\";N;s:8:\"location\";a:1:{s:2:\"ip\";s:10:\"172.18.0.0\";}s:6:\"events\";a:2:{i:0;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:43:\"Frederick Tech Open Workshop - 3rd Saturday\";s:3:\"url\";s:59:\"https://www.meetup.com/wordpress-frederick/events/296877413\";s:6:\"meetup\";s:19:\"WordPress Frederick\";s:10:\"meetup_url\";s:43:\"https://www.meetup.com/wordpress-frederick/\";s:4:\"date\";s:19:\"2023-11-18 10:00:00\";s:8:\"end_date\";s:19:\"2023-11-18 12:00:00\";s:20:\"start_unix_timestamp\";i:1700319600;s:18:\"end_unix_timestamp\";i:1700326800;s:8:\"location\";a:4:{s:8:\"location\";s:18:\"Frederick, MD, USA\";s:7:\"country\";s:2:\"us\";s:8:\"latitude\";d:39.415829;s:9:\"longitude\";d:-77.410446;}}i:1;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:42:\"Core Web Vitals - Speeding Up Your Website\";s:3:\"url\";s:69:\"https://www.meetup.com/the-baltimore-wordpress-group/events/297095111\";s:6:\"meetup\";s:29:\"The Baltimore WordPress Group\";s:10:\"meetup_url\";s:53:\"https://www.meetup.com/The-Baltimore-WordPress-Group/\";s:4:\"date\";s:19:\"2023-12-14 18:00:00\";s:8:\"end_date\";s:19:\"2023-12-14 19:00:00\";s:20:\"start_unix_timestamp\";i:1702594800;s:18:\"end_unix_timestamp\";i:1702598400;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"US\";s:8:\"latitude\";d:39.31;s:9:\"longitude\";d:-76.58;}}}}','no'),(942,'_transient_timeout_tribe_plugin_upgrade_notice-bb3d480e','1700311965','no'),(943,'_transient_tribe_plugin_upgrade_notice-bb3d480e','','no'),(952,'_transient_timeout__tribe_admin_notices','1702822895','no'),(953,'_transient__tribe_admin_notices','a:0:{}','no'),(955,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1700229801;s:8:\"response\";a:1:{s:27:\"woocommerce/woocommerce.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:25:\"w.org/plugins/woocommerce\";s:4:\"slug\";s:11:\"woocommerce\";s:6:\"plugin\";s:27:\"woocommerce/woocommerce.php\";s:11:\"new_version\";s:5:\"8.3.0\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/woocommerce/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/woocommerce.8.3.0.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/woocommerce/assets/icon-256x256.gif?rev=2869506\";s:2:\"1x\";s:64:\"https://ps.w.org/woocommerce/assets/icon-128x128.gif?rev=2869506\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/woocommerce/assets/banner-1544x500.png?rev=2366418\";s:2:\"1x\";s:66:\"https://ps.w.org/woocommerce/assets/banner-772x250.png?rev=2366418\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"6.3\";s:6:\"tested\";s:5:\"6.4.1\";s:12:\"requires_php\";s:3:\"7.4\";}}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:5:{s:33:\"coupon-creator/coupon_creator.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:28:\"w.org/plugins/coupon-creator\";s:4:\"slug\";s:14:\"coupon-creator\";s:6:\"plugin\";s:33:\"coupon-creator/coupon_creator.php\";s:11:\"new_version\";s:5:\"3.3.0\";s:3:\"url\";s:45:\"https://wordpress.org/plugins/coupon-creator/\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/plugin/coupon-creator.3.3.0.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:59:\"https://ps.w.org/coupon-creator/assets/icon.svg?rev=2688941\";s:3:\"svg\";s:59:\"https://ps.w.org/coupon-creator/assets/icon.svg?rev=2688941\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:70:\"https://ps.w.org/coupon-creator/assets/banner-1544x500.png?rev=2688941\";s:2:\"1x\";s:69:\"https://ps.w.org/coupon-creator/assets/banner-772x250.png?rev=2688941\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.9\";}s:49:\"easy-digital-downloads/easy-digital-downloads.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:36:\"w.org/plugins/easy-digital-downloads\";s:4:\"slug\";s:22:\"easy-digital-downloads\";s:6:\"plugin\";s:49:\"easy-digital-downloads/easy-digital-downloads.php\";s:11:\"new_version\";s:5:\"3.2.5\";s:3:\"url\";s:53:\"https://wordpress.org/plugins/easy-digital-downloads/\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/plugin/easy-digital-downloads.3.2.5.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:66:\"https://ps.w.org/easy-digital-downloads/assets/icon.svg?rev=971968\";s:3:\"svg\";s:66:\"https://ps.w.org/easy-digital-downloads/assets/icon.svg?rev=971968\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:78:\"https://ps.w.org/easy-digital-downloads/assets/banner-1544x500.png?rev=2636140\";s:2:\"1x\";s:77:\"https://ps.w.org/easy-digital-downloads/assets/banner-772x250.png?rev=2636140\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.8\";}s:31:\"event-tickets/event-tickets.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:27:\"w.org/plugins/event-tickets\";s:4:\"slug\";s:13:\"event-tickets\";s:6:\"plugin\";s:31:\"event-tickets/event-tickets.php\";s:11:\"new_version\";s:5:\"5.7.0\";s:3:\"url\";s:44:\"https://wordpress.org/plugins/event-tickets/\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/plugin/event-tickets.5.7.0.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:58:\"https://ps.w.org/event-tickets/assets/icon.svg?rev=2259340\";s:3:\"svg\";s:58:\"https://ps.w.org/event-tickets/assets/icon.svg?rev=2259340\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:69:\"https://ps.w.org/event-tickets/assets/banner-1544x500.png?rev=2257626\";s:2:\"1x\";s:68:\"https://ps.w.org/event-tickets/assets/banner-772x250.png?rev=2257626\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"6.2\";}s:27:\"redis-cache/redis-cache.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:25:\"w.org/plugins/redis-cache\";s:4:\"slug\";s:11:\"redis-cache\";s:6:\"plugin\";s:27:\"redis-cache/redis-cache.php\";s:11:\"new_version\";s:5:\"2.5.0\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/redis-cache/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/redis-cache.2.5.0.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/redis-cache/assets/icon-256x256.gif?rev=2568513\";s:2:\"1x\";s:64:\"https://ps.w.org/redis-cache/assets/icon-128x128.gif?rev=2568513\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/redis-cache/assets/banner-1544x500.png?rev=2315420\";s:2:\"1x\";s:66:\"https://ps.w.org/redis-cache/assets/banner-772x250.png?rev=2315420\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.6\";}s:43:\"the-events-calendar/the-events-calendar.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:33:\"w.org/plugins/the-events-calendar\";s:4:\"slug\";s:19:\"the-events-calendar\";s:6:\"plugin\";s:43:\"the-events-calendar/the-events-calendar.php\";s:11:\"new_version\";s:5:\"6.2.8\";s:3:\"url\";s:50:\"https://wordpress.org/plugins/the-events-calendar/\";s:7:\"package\";s:68:\"https://downloads.wordpress.org/plugin/the-events-calendar.6.2.8.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-256x256.gif?rev=2516440\";s:2:\"1x\";s:72:\"https://ps.w.org/the-events-calendar/assets/icon-128x128.gif?rev=2516440\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:75:\"https://ps.w.org/the-events-calendar/assets/banner-1544x500.png?rev=2257622\";s:2:\"1x\";s:74:\"https://ps.w.org/the-events-calendar/assets/banner-772x250.png?rev=2257622\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:5:\"6.2.0\";}}s:7:\"checked\";a:15:{s:33:\"ai-development/ai-development.php\";s:5:\"0.1.0\";s:33:\"coupon-creator/coupon_creator.php\";s:5:\"3.3.0\";s:49:\"coupon-creator-add-ons/coupon-creator-add-ons.php\";s:5:\"3.3.0\";s:41:\"coupon-creator-pro/coupon-creator-pro.php\";s:5:\"3.3.0\";s:49:\"easy-digital-downloads/easy-digital-downloads.php\";s:5:\"3.2.5\";s:31:\"event-tickets/event-tickets.php\";s:5:\"5.7.0\";s:41:\"event-tickets-plus/event-tickets-plus.php\";s:5:\"5.8.0\";s:27:\"redis-cache/redis-cache.php\";s:5:\"2.5.0\";s:43:\"the-events-calendar/the-events-calendar.php\";s:5:\"6.2.8\";s:35:\"event-automator/event-automator.php\";s:5:\"1.3.1\";s:33:\"events-virtual/events-virtual.php\";s:6:\"1.15.5\";s:34:\"events-pro/events-calendar-pro.php\";s:5:\"6.2.4\";s:29:\"volt-vectors/volt-vectors.php\";s:5:\"0.1.0\";s:37:\"volt-vectors-pro/volt-vectors-pro.php\";s:5:\"0.1.0\";s:27:\"woocommerce/woocommerce.php\";s:5:\"8.2.2\";}}','no'),(962,'_transient_timeout_orders-all-statuses','1700831425','no'),(963,'_transient_orders-all-statuses','a:2:{s:7:\"version\";s:10:\"1672924354\";s:5:\"value\";a:0:{}}','no'),(964,'_transient_timeout_woocommerce_admin_payment_method_promotion_specs','1700831425','no'),(965,'_transient_woocommerce_admin_payment_method_promotion_specs','a:1:{s:5:\"en_US\";a:2:{s:27:\"woocommerce_payments:woopay\";O:8:\"stdClass\":8:{s:2:\"id\";s:27:\"woocommerce_payments:woopay\";s:5:\"title\";s:20:\"WooCommerce Payments\";s:7:\"content\";s:393:\"Payments made simple — including WooPay, a new express checkout feature.Your transaction failed; please try again or contact site support.
','Transaction Failed','','publish','closed','closed','','transaction-failed','','','2023-01-05 13:11:42','2023-01-05 13:11:42','',4,'http://wordpress.test/checkout/transaction-failed/',0,'page','',0),(7,1,'2023-01-05 13:11:42','2023-01-05 13:11:42','','Order History','','publish','closed','closed','','order-history','','','2023-01-05 13:11:42','2023-01-05 13:11:42','',4,'http://wordpress.test/checkout/order-history/',0,'page','',0),(8,1,'2023-01-05 13:11:42','2023-01-05 13:11:42','Thank you for your purchase!
','Confirmation','','publish','closed','closed','','confirmation','','','2023-01-05 13:11:42','2023-01-05 13:11:42','',4,'http://wordpress.test/checkout/confirmation/',0,'page','',0),(9,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','','woocommerce-placeholder','','inherit','open','closed','','woocommerce-placeholder','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/wp-content/uploads/2023/01/woocommerce-placeholder.png',0,'attachment','image/png',0),(10,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','','Shop','','publish','closed','closed','','shop','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/shop/',0,'page','',0),(11,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','[woocommerce_cart]','Cart','','publish','closed','closed','','cart','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/cart/',0,'page','',0),(12,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','[woocommerce_checkout]','Checkout','','publish','closed','closed','','checkout-2','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/checkout-2/',0,'page','',0),(13,1,'2023-01-05 13:11:54','2023-01-05 13:11:54','[woocommerce_my_account]','My account','','publish','closed','closed','','my-account','','','2023-01-05 13:11:54','2023-01-05 13:11:54','',0,'http://wordpress.test/my-account/',0,'page','',0),(14,1,'2023-01-05 13:11:54','0000-00-00 00:00:00','\nThis is a sample page.
\n\n\n\nOur refund and returns policy lasts 30 days. If 30 days have passed since your purchase, we can’t offer you a full refund or exchange.
\n\n\n\nTo be eligible for a return, your item must be unused and in the same condition that you received it. It must also be in the original packaging.
\n\n\n\nSeveral types of goods are exempt from being returned. Perishable goods such as food, flowers, newspapers or magazines cannot be returned. We also do not accept products that are intimate or sanitary goods, hazardous materials, or flammable liquids or gases.
\n\n\n\nAdditional non-returnable items:
\n\n\n\nTo complete your return, we require a receipt or proof of purchase.
\n\n\n\nPlease do not send your purchase back to the manufacturer.
\n\n\n\nThere are certain situations where only partial refunds are granted:
\n\n\n\nOnce your return is received and inspected, we will send you an email to notify you that we have received your returned item. We will also notify you of the approval or rejection of your refund.
\n\n\n\nIf you are approved, then your refund will be processed, and a credit will automatically be applied to your credit card or original method of payment, within a certain amount of days.
\n\n\n\nLate or missing refunds\n\n\n\nIf you haven’t received a refund yet, first check your bank account again.
\n\n\n\nThen contact your credit card company, it may take some time before your refund is officially posted.
\n\n\n\nNext contact your bank. There is often some processing time before a refund is posted.
\n\n\n\nIf you’ve done all of this and you still have not received your refund yet, please contact us at {email address}.
\n\n\n\nSale items\n\n\n\nOnly regular priced items may be refunded. Sale items cannot be refunded.
\n\n\n\nWe only replace items if they are defective or damaged. If you need to exchange it for the same item, send us an email at {email address} and send your item to: {physical address}.
\n\n\n\nIf the item was marked as a gift when purchased and shipped directly to you, you’ll receive a gift credit for the value of your return. Once the returned item is received, a gift certificate will be mailed to you.
\n\n\n\nIf the item wasn’t marked as a gift when purchased, or the gift giver had the order shipped to themselves to give to you later, we will send a refund to the gift giver and they will find out about your return.
\n\n\n\nTo return your product, you should mail your product to: {physical address}.
\n\n\n\nYou will be responsible for paying for your own shipping costs for returning your item. Shipping costs are non-refundable. If you receive a refund, the cost of return shipping will be deducted from your refund.
\n\n\n\nDepending on where you live, the time it may take for your exchanged product to reach you may vary.
\n\n\n\nIf you are returning more expensive items, you may consider using a trackable shipping service or purchasing shipping insurance. We don’t guarantee that we will receive your returned item.
\n\n\n\nContact us at {email} for questions related to refunds and returns.
\n','Refund and Returns Policy','','draft','closed','closed','','refund_returns','','','2023-01-05 13:11:54','0000-00-00 00:00:00','',0,'http://wordpress.test/?page_id=14',0,'page','',0),(15,1,'2023-01-06 12:37:03','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2023-01-06 12:37:03','0000-00-00 00:00:00','',0,'http://wordpress.test/?p=15',0,'post','',0),(16,1,'2023-01-06 12:37:19','2023-01-06 12:37:19','[tec_tickets_checkout]','Tickets Checkout','','publish','closed','closed','','tickets-checkout','','','2023-01-06 12:37:19','2023-01-06 12:37:19','',0,'http://wordpress.test/tickets-checkout/',0,'page','',0),(17,1,'2023-01-06 12:37:19','2023-01-06 12:37:19','[tec_tickets_success]','Order Completed','','publish','closed','closed','','tickets-order','','','2023-01-06 12:37:19','2023-01-06 12:37:19','',0,'http://wordpress.test/tickets-order/',0,'page','',0),(18,0,'2023-11-17 07:24:17','2023-11-17 12:24:17','','Test Event','','publish','open','closed','','test-event','','','2023-11-17 07:24:17','2023-11-17 12:24:17','',0,'http://wordpress.test/event/test-event/',0,'tribe_events','',0),(19,0,'2023-11-17 07:24:18','2023-11-17 12:24:18','','Test WooCommerce ticket for 18','Test WooCommerce ticket description for 18','publish','open','closed','','test-woocommerce-ticket-for-18','','','2023-11-17 07:24:18','2023-11-17 12:24:18','',0,'http://wordpress.test/product/test-woocommerce-ticket-for-18/',-1,'product','',0); +/*!40000 ALTER TABLE `wp_posts` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_tec_events` +-- + +DROP TABLE IF EXISTS `wp_tec_events`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_tec_events` ( + `event_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `post_id` bigint(20) unsigned NOT NULL, + `start_date` varchar(19) NOT NULL, + `end_date` varchar(19) DEFAULT NULL, + `timezone` varchar(30) NOT NULL DEFAULT 'UTC', + `start_date_utc` varchar(19) NOT NULL, + `end_date_utc` varchar(19) DEFAULT NULL, + `duration` mediumint(30) DEFAULT 7200, + `updated_at` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), + `hash` varchar(40) NOT NULL, + PRIMARY KEY (`event_id`), + UNIQUE KEY `post_id` (`post_id`) +) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_tec_events` +-- + +LOCK TABLES `wp_tec_events` WRITE; +/*!40000 ALTER TABLE `wp_tec_events` DISABLE KEYS */; +INSERT INTO `wp_tec_events` VALUES (1,18,'2019-01-01 10:00:00','2019-01-01 13:00:00','America/New_York','2019-01-01 15:00:00','2019-01-01 18:00:00',10800,'2023-11-17 12:24:17',''); +/*!40000 ALTER TABLE `wp_tec_events` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_tec_occurrences` +-- + +DROP TABLE IF EXISTS `wp_tec_occurrences`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_tec_occurrences` ( + `occurrence_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `event_id` bigint(20) unsigned NOT NULL, + `post_id` bigint(20) unsigned NOT NULL, + `start_date` varchar(19) NOT NULL, + `start_date_utc` varchar(19) NOT NULL, + `end_date` varchar(19) NOT NULL, + `end_date_utc` varchar(19) NOT NULL, + `duration` mediumint(30) DEFAULT 7200, + `hash` varchar(40) NOT NULL, + `updated_at` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), + PRIMARY KEY (`occurrence_id`), + UNIQUE KEY `hash` (`hash`), + KEY `event_id` (`event_id`) +) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_tec_occurrences` +-- + +LOCK TABLES `wp_tec_occurrences` WRITE; +/*!40000 ALTER TABLE `wp_tec_occurrences` DISABLE KEYS */; +INSERT INTO `wp_tec_occurrences` VALUES (1,1,18,'2019-01-01 10:00:00','2019-01-01 15:00:00','2019-01-01 13:00:00','2019-01-01 18:00:00',10800,'4488dda4f18421f2229725fcd75413eb811f1538','2023-11-17 12:24:19'); +/*!40000 ALTER TABLE `wp_tec_occurrences` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_term_relationships` +-- + +DROP TABLE IF EXISTS `wp_term_relationships`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_term_relationships` ( + `object_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `term_order` int(11) NOT NULL DEFAULT 0, + PRIMARY KEY (`object_id`,`term_taxonomy_id`), + KEY `term_taxonomy_id` (`term_taxonomy_id`) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_term_relationships` +-- + +LOCK TABLES `wp_term_relationships` WRITE; +/*!40000 ALTER TABLE `wp_term_relationships` DISABLE KEYS */; +INSERT INTO `wp_term_relationships` VALUES (19,2,0),(19,6,0),(19,7,0); +/*!40000 ALTER TABLE `wp_term_relationships` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_term_taxonomy` +-- + +DROP TABLE IF EXISTS `wp_term_taxonomy`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_term_taxonomy` ( + `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `taxonomy` varchar(32) NOT NULL DEFAULT '', + `description` longtext NOT NULL, + `parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `count` bigint(20) NOT NULL DEFAULT 0, + PRIMARY KEY (`term_taxonomy_id`), + UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), + KEY `taxonomy` (`taxonomy`) +) ENGINE=InnoDB AUTO_INCREMENT=16 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_term_taxonomy` +-- + +LOCK TABLES `wp_term_taxonomy` WRITE; +/*!40000 ALTER TABLE `wp_term_taxonomy` DISABLE KEYS */; +INSERT INTO `wp_term_taxonomy` VALUES (1,1,'category','',0,1),(2,2,'product_type','',0,1),(3,3,'product_type','',0,0),(4,4,'product_type','',0,0),(5,5,'product_type','',0,0),(6,6,'product_visibility','',0,1),(7,7,'product_visibility','',0,1),(8,8,'product_visibility','',0,0),(9,9,'product_visibility','',0,0),(10,10,'product_visibility','',0,0),(11,11,'product_visibility','',0,0),(12,12,'product_visibility','',0,0),(13,13,'product_visibility','',0,0),(14,14,'product_visibility','',0,0),(15,15,'product_cat','',0,0); +/*!40000 ALTER TABLE `wp_term_taxonomy` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_termmeta` +-- + +DROP TABLE IF EXISTS `wp_termmeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_termmeta` ( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `term_id` (`term_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_termmeta` +-- + +LOCK TABLES `wp_termmeta` WRITE; +/*!40000 ALTER TABLE `wp_termmeta` DISABLE KEYS */; +/*!40000 ALTER TABLE `wp_termmeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_terms` +-- + +DROP TABLE IF EXISTS `wp_terms`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_terms` ( + `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `name` varchar(200) NOT NULL DEFAULT '', + `slug` varchar(200) NOT NULL DEFAULT '', + `term_group` bigint(10) NOT NULL DEFAULT 0, + PRIMARY KEY (`term_id`), + KEY `slug` (`slug`(191)), + KEY `name` (`name`(191)) +) ENGINE=InnoDB AUTO_INCREMENT=16 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_terms` +-- + +LOCK TABLES `wp_terms` WRITE; +/*!40000 ALTER TABLE `wp_terms` DISABLE KEYS */; +INSERT INTO `wp_terms` VALUES (1,'Uncategorized','uncategorized',0),(2,'simple','simple',0),(3,'grouped','grouped',0),(4,'variable','variable',0),(5,'external','external',0),(6,'exclude-from-search','exclude-from-search',0),(7,'exclude-from-catalog','exclude-from-catalog',0),(8,'featured','featured',0),(9,'outofstock','outofstock',0),(10,'rated-1','rated-1',0),(11,'rated-2','rated-2',0),(12,'rated-3','rated-3',0),(13,'rated-4','rated-4',0),(14,'rated-5','rated-5',0),(15,'Uncategorized','uncategorized',0); +/*!40000 ALTER TABLE `wp_terms` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_usermeta` +-- + +DROP TABLE IF EXISTS `wp_usermeta`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_usermeta` ( + `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `meta_key` varchar(255) DEFAULT NULL, + `meta_value` longtext DEFAULT NULL, + PRIMARY KEY (`umeta_id`), + KEY `user_id` (`user_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE=InnoDB AUTO_INCREMENT=32 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_usermeta` +-- + +LOCK TABLES `wp_usermeta` WRITE; +/*!40000 ALTER TABLE `wp_usermeta` DISABLE KEYS */; +INSERT INTO `wp_usermeta` VALUES (1,1,'nickname','admin'),(2,1,'first_name',''),(3,1,'last_name',''),(4,1,'description',''),(5,1,'rich_editing','true'),(6,1,'syntax_highlighting','true'),(7,1,'comment_shortcuts','false'),(8,1,'admin_color','fresh'),(9,1,'use_ssl','0'),(10,1,'show_admin_bar_front','true'),(11,1,'locale',''),(12,1,'wp_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wp_user_level','10'),(14,1,'dismissed_wp_pointers',''),(15,1,'show_welcome_panel','0'),(16,1,'session_tokens','a:1:{s:64:\"f87edbb427e6c886863d67ca01bbe24209c88c0fed4152790d5a3c5b458b6abe\";a:4:{s:10:\"expiration\";i:1700398319;s:2:\"ip\";s:10:\"172.18.0.1\";s:2:\"ua\";s:84:\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/119.0\";s:5:\"login\";i:1700225519;}}'),(17,1,'wp_user-settings','mfold=o'),(18,1,'wp_user-settings-time','1666777420'),(19,1,'wp_dashboard_quick_press_last_post_id','15'),(20,1,'community-events-location','a:1:{s:2:\"ip\";s:10:\"172.18.0.0\";}'),(21,1,'wc_last_active','1700179200'),(23,1,'_woocommerce_tracks_anon_id','woo:5wYlp+5sdH3mKeoMABLSOktJ'),(24,1,'_woocommerce_persistent_cart_1','a:1:{s:4:\"cart\";a:0:{}}'),(25,1,'dismissed_no_secure_connection_notice','1'),(27,1,'tribe-dismiss-notice-time-event-tickets-plus-missing-easydigitaldownloads-support','1700226647'),(28,1,'tribe-dismiss-notice','event-tickets-plus-missing-easydigitaldownloads-support'),(29,1,'tribe-dismiss-notice-time-event-tickets-plus-missing-woocommerce-support','1700226652'),(30,1,'tribe-dismiss-notice','event-tickets-plus-missing-woocommerce-support'),(31,1,'dismissed_update_notice','1'); +/*!40000 ALTER TABLE `wp_usermeta` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_users` +-- + +DROP TABLE IF EXISTS `wp_users`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_users` ( + `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_login` varchar(60) NOT NULL DEFAULT '', + `user_pass` varchar(255) NOT NULL DEFAULT '', + `user_nicename` varchar(50) NOT NULL DEFAULT '', + `user_email` varchar(100) NOT NULL DEFAULT '', + `user_url` varchar(100) NOT NULL DEFAULT '', + `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `user_activation_key` varchar(255) NOT NULL DEFAULT '', + `user_status` int(11) NOT NULL DEFAULT 0, + `display_name` varchar(250) NOT NULL DEFAULT '', + PRIMARY KEY (`ID`), + KEY `user_login_key` (`user_login`), + KEY `user_nicename` (`user_nicename`), + KEY `user_email` (`user_email`) +) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_users` +-- + +LOCK TABLES `wp_users` WRITE; +/*!40000 ALTER TABLE `wp_users` DISABLE KEYS */; +INSERT INTO `wp_users` VALUES (1,'admin','$P$BXTnf5Ms8OdVvNu2ToTsQvL1LsiHRC.','admin','admin@wordpress.test','','2018-04-03 13:14:05','',0,'admin'); +/*!40000 ALTER TABLE `wp_users` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_wc_admin_note_actions` +-- + +DROP TABLE IF EXISTS `wp_wc_admin_note_actions`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_wc_admin_note_actions` ( + `action_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `note_id` bigint(20) unsigned NOT NULL, + `name` varchar(255) NOT NULL, + `label` varchar(255) NOT NULL, + `query` longtext NOT NULL, + `status` varchar(255) NOT NULL, + `actioned_text` varchar(255) NOT NULL, + `nonce_action` varchar(255) DEFAULT NULL, + `nonce_name` varchar(255) DEFAULT NULL, + PRIMARY KEY (`action_id`), + KEY `note_id` (`note_id`) +) ENGINE=InnoDB AUTO_INCREMENT=695 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_wc_admin_note_actions` +-- + +LOCK TABLES `wp_wc_admin_note_actions` WRITE; +/*!40000 ALTER TABLE `wp_wc_admin_note_actions` DISABLE KEYS */; +INSERT INTO `wp_wc_admin_note_actions` VALUES (1,1,'notify-refund-returns-page','Edit page','http://wordpress.test/wp-admin/post.php?post=14&action=edit','actioned','',NULL,NULL),(2,2,'connect','Connect','?page=wc-addons§ion=helper','unactioned','',NULL,NULL),(25,23,'share-navigation-survey-feedback','Share feedback','https://automattic.survey.fm/feedback-on-woocommerce-navigation','actioned','',NULL,NULL),(45,37,'add-first-product','Add a product','http://wordpress.test/wp-admin/admin.php?page=wc-admin&task=products','actioned','',NULL,NULL),(46,38,'visit-the-theme-marketplace','Visit the theme marketplace','https://woocommerce.com/product-category/themes/?utm_source=inbox&utm_medium=product','actioned','',NULL,NULL),(47,39,'learn-more','Learn more','https://woocommerce.com/mobile/?utm_medium=product','actioned','',NULL,NULL),(48,3,'browse_extensions','Browse extensions','http://wordpress.test/wp-admin/admin.php?page=wc-addons','unactioned','',NULL,NULL),(76,28,'wc-admin-wisepad3','Grow my business offline','https://woocommerce.com/products/wisepad3-card-reader/?utm_source=inbox_note&utm_medium=product&utm_campaign=wc-admin-wisepad3','actioned','',NULL,NULL),(81,31,'woocommerce_admin_deprecation_q4_2022','Deactivate WooCommerce Admin','http://wordpress.test/wp-admin/plugins.php','actioned','',NULL,NULL),(82,32,'paypal_paylater_g3_q4_22','Install PayPal Payments','https://woocommerce.com/products/woocommerce-paypal-payments/?utm_source=inbox_note&utm_medium=product&utm_campaign=paypal_paylater_g3_q4_22','unactioned','',NULL,NULL),(83,33,'paypal_paylater_g2_q4_22','Install PayPal Payments','https://woocommerce.com/products/woocommerce-paypal-payments/?utm_source=inbox_note&utm_medium=product&utm_campaign=paypal_paylater_g2_q4_22','unactioned','',NULL,NULL),(84,34,'google_listings_ads_custom_attribute_mapping_q4_2022','Learn more','https://woocommerce.com/document/google-listings-and-ads/?utm_source=inbox_note&utm_medium=product&utm_campaign=google_listings_ads_custom_attribute_mapping_q4_2022#attribute-mapping','actioned','',NULL,NULL),(424,40,'update-db_done','Thanks!','http://localhost:8888/wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s&wc-hide-notice=update','actioned','woocommerce_hide_notices_nonce','woocommerce_hide_notices_nonce','_wc_notice_nonce'),(605,4,'wayflyer_bnpl_q4_2021','Level up with funding','https://woo.com/products/wayflyer/?utm_source=inbox_note&utm_medium=product&utm_campaign=wayflyer_bnpl_q4_2021','actioned','',NULL,NULL),(606,5,'wc_shipping_mobile_app_usps_q4_2021','Get WooCommerce Shipping','https://woo.com/woocommerce-shipping/?utm_source=inbox_note&utm_medium=product&utm_campaign=wc_shipping_mobile_app_usps_q4_2021','actioned','',NULL,NULL),(607,6,'learn-more','Learn more','https://docs.woocommerce.com/document/woocommerce-shipping-and-tax/?utm_source=inbox','unactioned','',NULL,NULL),(608,7,'learn-more','Learn more','https://woo.com/posts/ecommerce-shipping-solutions-guide/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','actioned','',NULL,NULL),(609,8,'optimizing-the-checkout-flow','Learn more','https://woo.com/posts/optimizing-woocommerce-checkout?utm_source=inbox_note&utm_medium=product&utm_campaign=optimizing-the-checkout-flow','actioned','',NULL,NULL),(610,9,'qualitative-feedback-from-new-users','Share feedback','https://automattic.survey.fm/wc-pay-new','actioned','',NULL,NULL),(611,10,'share-feedback','Share feedback','http://automattic.survey.fm/paypal-feedback','unactioned','',NULL,NULL),(612,11,'get-started','Get started','https://woo.com/products/google-listings-and-ads?utm_source=inbox_note&utm_medium=product&utm_campaign=get-started','actioned','',NULL,NULL),(613,12,'update-wc-subscriptions-3-0-15','View latest version','http://localhost:8888/wp-admin/&page=wc-addons§ion=helper','actioned','',NULL,NULL),(614,13,'update-wc-core-5-4-0','How to update WooCommerce','https://docs.woocommerce.com/document/how-to-update-woocommerce/','actioned','',NULL,NULL),(615,16,'ppxo-pps-install-paypal-payments-1','View upgrade guide','https://docs.woocommerce.com/document/woocommerce-paypal-payments/paypal-payments-upgrade-guide/','actioned','',NULL,NULL),(616,17,'ppxo-pps-install-paypal-payments-2','View upgrade guide','https://docs.woocommerce.com/document/woocommerce-paypal-payments/paypal-payments-upgrade-guide/','actioned','',NULL,NULL),(617,18,'learn-more','Learn more','https://woo.com/posts/critical-vulnerability-detected-july-2021/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','unactioned','',NULL,NULL),(618,18,'dismiss','Dismiss','','actioned','',NULL,NULL),(619,19,'learn-more','Learn more','https://woo.com/posts/critical-vulnerability-detected-july-2021/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','unactioned','',NULL,NULL),(620,19,'dismiss','Dismiss','','actioned','',NULL,NULL),(621,20,'learn-more','Learn more','https://woo.com/posts/critical-vulnerability-detected-july-2021/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','unactioned','',NULL,NULL),(622,20,'dismiss','Dismiss','','actioned','',NULL,NULL),(623,21,'learn-more','Learn more','https://woo.com/posts/critical-vulnerability-detected-july-2021/?utm_source=inbox_note&utm_medium=product&utm_campaign=learn-more','unactioned','',NULL,NULL),(624,21,'dismiss','Dismiss','','actioned','',NULL,NULL),(625,22,'share-feedback','Share feedback','https://automattic.survey.fm/store-management','unactioned','',NULL,NULL),(626,24,'learn-more','Learn more','https://developer.woocommerce.com/2022/03/10/woocommerce-3-5-10-6-3-1-security-releases/','unactioned','',NULL,NULL),(627,24,'woocommerce-core-paypal-march-2022-dismiss','Dismiss','','actioned','',NULL,NULL),(628,25,'learn-more','Learn more','https://developer.woocommerce.com/2022/03/10/woocommerce-3-5-10-6-3-1-security-releases/','unactioned','',NULL,NULL),(629,25,'dismiss','Dismiss','','actioned','',NULL,NULL),(630,26,'pinterest_03_2022_update','Update Instructions','https://woo.com/document/pinterest-for-woocommerce/?utm_source=inbox_note&utm_medium=product&utm_campaign=pinterest_03_2022_update#section-3','actioned','',NULL,NULL),(631,27,'store_setup_survey_survey_q2_2022_share_your_thoughts','Tell us how it’s going','https://automattic.survey.fm/store-setup-survey-2022','actioned','',NULL,NULL),(632,29,'learn-more','Find out more','https://developer.woocommerce.com/2022/08/09/woocommerce-payments-3-9-4-4-5-1-security-releases/','unactioned','',NULL,NULL),(633,29,'dismiss','Dismiss','','actioned','',NULL,NULL),(634,30,'learn-more','Find out more','https://developer.woocommerce.com/2022/08/09/woocommerce-payments-3-9-4-4-5-1-security-releases/','unactioned','',NULL,NULL),(635,30,'dismiss','Dismiss','','actioned','',NULL,NULL),(636,35,'needs-update-eway-payment-gateway-rin-action-button-2022-12-20','See available updates','http://localhost:8888/wp-admin/update-core.php','unactioned','',NULL,NULL),(637,35,'needs-update-eway-payment-gateway-rin-dismiss-button-2022-12-20','Dismiss','#','actioned','',NULL,NULL),(638,36,'updated-eway-payment-gateway-rin-action-button-2022-12-20','See all updates','http://localhost:8888/wp-admin/update-core.php','unactioned','',NULL,NULL),(639,36,'updated-eway-payment-gateway-rin-dismiss-button-2022-12-20','Dismiss','#','actioned','',NULL,NULL),(640,41,'share-navigation-survey-feedback','Share feedback','https://automattic.survey.fm/new-ecommerce-plan-navigation','actioned','',NULL,NULL),(641,42,'woopay-beta-merchantrecruitment-activate-04MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','actioned','',NULL,NULL),(642,42,'woopay-beta-merchantrecruitment-activate-learnmore-04MAY23','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-activate-learnmore-04MAY23','unactioned','',NULL,NULL),(643,43,'woocommerce-wcpay-march-2023-update-needed-button','See Blog Post','https://developer.woocommerce.com/2023/03/23/critical-vulnerability-detected-in-woocommerce-payments-what-you-need-to-know','unactioned','',NULL,NULL),(644,43,'woocommerce-wcpay-march-2023-update-needed-dismiss-button','Dismiss','#','actioned','',NULL,NULL),(645,44,'tap_to_pay_iphone_q2_2023_no_wcpay','Simplify my payments','https://woo.com/products/woocommerce-payments/?utm_source=inbox_note&utm_medium=product&utm_campaign=tap_to_pay_iphone_q2_2023_no_wcpay','actioned','',NULL,NULL),(646,45,'extension-settings','See available updates','http://localhost:8888/wp-admin/update-core.php','unactioned','',NULL,NULL),(647,45,'dismiss','Dismiss','#','actioned','',NULL,NULL),(648,46,'woopay-beta-merchantrecruitment-update-WCPay-04MAY23','Update WooCommerce Payments','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(649,46,'woopay-beta-merchantrecruitment-update-activate-04MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','actioned','',NULL,NULL),(650,47,'woopay-beta-existingmerchants-noaction-documentation-27APR23','Documentation','https://woo.com/document/woopay-merchant-documentation/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-existingmerchants-noaction-documentation-27APR23','actioned','',NULL,NULL),(651,48,'woopay-beta-existingmerchants-update-WCPay-27APR23','Update WooCommerce Payments','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','actioned','',NULL,NULL),(652,49,'woopay-beta-merchantrecruitment-short-activate-04MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','actioned','',NULL,NULL),(653,49,'woopay-beta-merchantrecruitment-short-activate-learnmore-04MAY23','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-04MAY23','actioned','',NULL,NULL),(654,50,'woopay-beta-merchantrecruitment-short-update-WCPay-04MAY23','Update WooCommerce Payments','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(655,50,'woopay-beta-merchantrecruitment-short-update-activate-04MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','actioned','',NULL,NULL),(656,51,'woopay-beta-merchantrecruitment-short-activate-06MAY23-TESTA','Activate WooPay Test A','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(657,51,'woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTA','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTA','unactioned','',NULL,NULL),(658,52,'woopay-beta-merchantrecruitment-short-activate-06MAY23-TESTB','Activate WooPay Test B','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(659,52,'woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTA','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTA','unactioned','',NULL,NULL),(660,53,'woopay-beta-merchantrecruitment-short-activate-06MAY23-TESTC','Activate WooPay Test C','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(661,53,'woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTC','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTC','unactioned','',NULL,NULL),(662,54,'woopay-beta-merchantrecruitment-short-activate-06MAY23-TESTD','Activate WooPay Test D','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(663,54,'woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTD','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-06MAY23-TESTD','unactioned','',NULL,NULL),(664,55,'woopay-beta-merchantrecruitment-short-activate-button-09MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(665,55,'woopay-beta-merchantrecruitment-short-activate-learnmore-button2-09MAY23','Learn More','https://woo.com/woopay-businesses/?utm_source=inbox_note&utm_medium=product&utm_campaign=woopay-beta-merchantrecruitment-short-activate-learnmore-button2-09MAY23','unactioned','',NULL,NULL),(666,56,'woopay-beta-merchantrecruitment-short-update-WCPay-09MAY23','Update WooCommerce Payments','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(667,56,'woopay-beta-merchantrecruitment-short-update-activate-09MAY23','Activate WooPay','http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=woocommerce_payments&method=platform_checkout','unactioned','',NULL,NULL),(668,57,'woocommerce-WCStripe-May-2023-updated-needed-Plugin-Settings','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(669,57,'woocommerce-WCStripe-May-2023-updated-needed-Plugin-Settings-dismiss','Dismiss','#','actioned','',NULL,NULL),(670,58,'woocommerce-WCPayments-June-2023-updated-needed-Plugin-Settings','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(671,58,'woocommerce-WCPayments-June-2023-updated-needed-Dismiss','Dismiss','#','actioned','',NULL,NULL),(672,59,'woocommerce-WCSubscriptions-June-2023-updated-needed-Plugin-Settings','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(673,59,'woocommerce-WCSubscriptions-June-2023-updated-needed-dismiss','Dismiss','#','actioned','',NULL,NULL),(674,60,'woocommerce-WCReturnsWarranty-June-2023-updated-needed','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(675,60,'woocommerce-WCReturnsWarranty-June-2023-updated-needed','Dismiss','#','actioned','',NULL,NULL),(676,61,'woocommerce-WCOPC-June-2023-updated-needed','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','actioned','',NULL,NULL),(677,61,'woocommerce-WCOPC-June-2023-updated-needed','Dismiss','http://localhost:8888/wp-admin/#','actioned','',NULL,NULL),(678,62,'woocommerce-WCGC-July-2023-update-needed','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(679,62,'woocommerce-WCGC-July-2023-update-needed','Dismiss','#','actioned','',NULL,NULL),(680,63,'learn-more','Learn more','https://woo.com/document/fedex/?utm_medium=product&utm_source=inbox_note&utm_campaign=learn-more#july-2023-api-outage','unactioned','',NULL,NULL),(681,64,'plugin-list','See available updates','http://localhost:8888/wp-admin/plugins.php?plugin_status=all','unactioned','',NULL,NULL),(682,64,'dismiss','Dismiss','http://localhost:8888/wp-admin/admin.php?page=wc-admin','actioned','',NULL,NULL),(683,65,'woocommerce-WCStripe-Aug-2023-update-needed','See available updates','http://localhost:8888/wp-admin/update-core.php?','unactioned','',NULL,NULL),(684,65,'dismiss','Dismiss','#','actioned','',NULL,NULL),(685,66,'dismiss','Dismiss','#','actioned','',NULL,NULL),(686,67,'woocommerce-WooPayments-Aug-2023-update-needed','See available updates','http://localhost:8888/wp-admin/update-core.php?','unactioned','',NULL,NULL),(687,67,'dismiss','Dismiss','#','actioned','',NULL,NULL),(688,68,'dismiss','Dismiss','#','actioned','',NULL,NULL),(689,69,'avalara_q3-2023_noAvaTax','Automate my sales tax','https://woo.com/products/woocommerce-avatax/?utm_source=inbox_note&utm_medium=product&utm_campaign=avalara_q3-2023_noAvaTax','unactioned','',NULL,NULL),(690,70,'woo-activation-survey-blockers-survey-button-22AUG23','Take our short survey','https://woocommerce.survey.fm/getting-started-with-woo','unactioned','',NULL,NULL),(691,71,'woocommerce-usermeta-Sept2023-productvendors','See available updates','http://localhost:8888/wp-admin/plugins.php','unactioned','',NULL,NULL),(692,71,'dismiss','Dismiss','http://localhost:8888/wp-admin/#','actioned','',NULL,NULL),(693,72,'woocommerce-STRIPE-Oct-2023-update-needed','See available updates','http://localhost:8888/wp-admin/update-core.php','unactioned','',NULL,NULL),(694,72,'dismiss','Dismiss','#','actioned','',NULL,NULL); +/*!40000 ALTER TABLE `wp_wc_admin_note_actions` ENABLE KEYS */; +UNLOCK TABLES; + +-- +-- Table structure for table `wp_wc_admin_notes` +-- + +DROP TABLE IF EXISTS `wp_wc_admin_notes`; +/*!40101 SET @saved_cs_client = @@character_set_client */; +/*!40101 SET character_set_client = utf8 */; +CREATE TABLE `wp_wc_admin_notes` ( + `note_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `name` varchar(255) NOT NULL, + `type` varchar(20) NOT NULL, + `locale` varchar(20) NOT NULL, + `title` longtext NOT NULL, + `content` longtext NOT NULL, + `content_data` longtext DEFAULT NULL, + `status` varchar(200) NOT NULL, + `source` varchar(200) NOT NULL, + `date_created` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `date_reminder` datetime DEFAULT NULL, + `is_snoozable` tinyint(1) NOT NULL DEFAULT 0, + `layout` varchar(20) NOT NULL DEFAULT '', + `image` varchar(200) DEFAULT NULL, + `is_deleted` tinyint(1) NOT NULL DEFAULT 0, + `is_read` tinyint(1) NOT NULL DEFAULT 0, + `icon` varchar(200) NOT NULL DEFAULT 'info', + PRIMARY KEY (`note_id`) +) ENGINE=InnoDB AUTO_INCREMENT=73 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +/*!40101 SET character_set_client = @saved_cs_client */; + +-- +-- Dumping data for table `wp_wc_admin_notes` +-- + +LOCK TABLES `wp_wc_admin_notes` WRITE; +/*!40000 ALTER TABLE `wp_wc_admin_notes` DISABLE KEYS */; +INSERT INTO `wp_wc_admin_notes` VALUES (1,'wc-refund-returns-page','info','en_US','Setup a Refund and Returns Policy page to boost your store\'s credibility.','We have created a sample draft Refund and Returns Policy page for you. Please have a look and update it to fit your store.','{}','unactioned','woocommerce-core','2023-01-05 13:11:55',NULL,0,'plain','',1,0,'info'),(2,'wc-admin-wc-helper-connection','info','en_US','Connect to WooCommerce.com','Connect to get important product notifications and updates.','{}','unactioned','woocommerce-admin','2023-01-05 13:11:56',NULL,0,'plain','',1,0,'info'),(3,'new_in_app_marketplace_2021','info','en_US','Customize your store with extensions','Check out our NEW Extensions tab to see our favorite extensions for customizing your store, and discover the most popular extensions in the WooCommerce Marketplace.','{}','unactioned','woocommerce.com','2023-01-05 13:13:22',NULL,0,'plain','',1,0,'info'),(4,'wayflyer_bnpl_q4_2021','marketing','en_US','Grow your business with funding through Wayflyer','Fast, flexible financing to boost cash flow and help your business grow – one fee, no interest rates, penalties, equity, or personal guarantees. Based on your store’s performance, Wayflyer provides funding and analytical insights to invest in your business.','{}','pending','woocommerce.com','2023-01-05 13:13:22',NULL,0,'plain','',0,0,'info'),(5,'wc_shipping_mobile_app_usps_q4_2021','marketing','en_US','Print and manage your shipping labels with WooCommerce Shipping and the WooCommerce Mobile App','Save time by printing, purchasing, refunding, and tracking shipping labels generated by WooCommerce Shipping – all directly from your mobile device!','{}','pending','woocommerce.com','2023-01-05 13:13:22',NULL,0,'plain','',0,0,'info'),(6,'woocommerce-services','info','en_US','WooCommerce Shipping & Tax','WooCommerce Shipping & Tax helps get your store \"ready to sell\" as quickly as possible. You create your products. We take care of tax calculation, payment processing, and shipping label printing! Learn more about the extension that you just installed.','{}','pending','woocommerce.com','2023-01-05 13:13:22',NULL,0,'plain','',0,0,'info'),(7,'your-first-product','info','en_US','Your first product','That’s huge! You’re well on your way to building a successful online store — now it’s time to think about how you’ll fulfill your orders.