You can reproduce this even with Twenty Nineteen, by adding <?php $blocks = gutenberg_parse_blocks( $post->post_content ); ?> to header.php.

Replacing gutenberg_parse_blocks() calls with parse_blocks() seems to work around the issue (for me at least), and the issue here, if any, is apparently just one of confusion: renaming the function broke backwards compatibility, but since gutenberg_parse_blocks() is still defined, instead of a ”Call to undefined function” you get this attempt to redefine WP_Block_Parser (via inclusion of parser.php), resulting in the ”name is already in use”.

”Using the occ command” documents using versions:cleanup either globally or for specific users, with example invocations for both cases. However, said examples are identical in the current revision:

This example deletes all versions for all users:

sudo -u www-data php occ versions:cleanup
Delete all versions
Delete versions for users on backend Database

[…]

You can delete versions for specific users in a space-delimited list:

sudo -u www-data php occ versions:cleanup
Delete versions of   freda
Delete versions of   molly

Unless I’m misinterpreting this, the latter example should have the space-delimited list of users following the invocation, like so:

sudo -u www-data php occ versions:cleanup freda molly

My test blog is running WP 5.0-beta3-43867 with Gutenberg 4.3.0-alpha-0841246 (from Daniel Bachhuber’s nightly), and the theme I’m using is Cover2 (Github here), which also appears to exhibit this in single post view.

I’ve narrowed it down to this function (called from header.php), where the gutenberg_parse_blocks() call triggers the issue.

I’m not saying I’m 100 % sure it’s Gutenberg and not the theme(s) at fault here, but I just thought I’d post this just in case it helps to find out either way.

Amended to replace whitespaces mixed with tabs in extension.json, and to fix description message id.

Refactor file structure so that the extension can be loaded using MW 1.25+ style wfLoadExtension(), and makes MW 1.25+ a requirement. Otherwise the core functionality should remain just as it was (i.e., if it doesn’t, that’s unintentional on my part).

This closes issue #3.

Since MediaWiki 1.25, the suggested method of registering extensions has been to use wfLoadExtension() instead of a direct require_once. AddBodyClass currently (v1.2.0 from 2016-03-21) still uses the old style, so I’m opening this issue to suggest converting the extension to use the new method.

I’m also preparing a pull request with the minimal changes that I think should accomplish this, and I’ll post it next.

Here’s a small patch to fix the spelling of comparative + than, which is currently misspelled as comparative + then in a couple of places.

Not sure if this URL is supported, but the error message doesn’t look quite right, nor clear as to what the problem is from a user’s perspective:

$ yle-dl 'https://yle.fi/aihe/artikkeli/2013/04/11/aanien-illoissa-kuunnellaan-kadonneitakin-aania'
yle-dl 2.37: Download media files from Yle Areena and Elävä Arkisto
Copyright (C) 2009-2018 Antti Ajanki <antti.ajanki@iki.fi>, license: GPLv3

Traceback (most recent call last):
  File "/usr/local/bin/yle-dl", line 11, in <module>
    load_entry_point('yle-dl==2.37', 'console_scripts', 'yle-dl')()
  File "build/bdist.linux-x86_64/egg/yledl/yledl.py", line 377, in main
  File "build/bdist.linux-x86_64/egg/yledl/yledl.py", line 252, in download
  File "build/bdist.linux-x86_64/egg/yledl/extractors.py", line 543, in extract
  File "build/bdist.linux-x86_64/egg/yledl/extractors.py", line 736, in extract_clip
  File "build/bdist.linux-x86_64/egg/yledl/extractors.py", line 983, in program_info_for_pid
  File "build/bdist.linux-x86_64/egg/yledl/extractors.py", line 791, in media_flavors
  File "build/bdist.linux-x86_64/egg/yledl/extractors.py", line 875, in download_flavors
  File "build/bdist.linux-x86_64/egg/yledl/backends.py", line 499, in __init__
  File "build/bdist.linux-x86_64/egg/yledl/backends.py", line 40, in __init__
AttributeError: 'NoneType' object has no attribute 'startswith'

I made a note about the failure in my kanban (yesterday) at ”13:17:10 GMT+0300 (EEST)”, so that would have been 10:17:10 UTC.

The build-android target calls the pre-build target as pre-buid, resulting in build failure for the build-android target. This PR fixes the issue.

(PR #2272 did the same for a typo in the build-pr target.)