Talk:MediaWiki 1.35

Fixed issue

I have installed the new mediawiki 1.35 and some extensions, during setup I installed Visual Editor however when trying to edit a page with visual editor i get the following error:

Error contacting the Parsoid/RESTBase server: (curl error: 7) Couldn't connect to server

Any help would be appreciated.

My mediawiki install.

Product	Version
MediaWiki	1.35.0
PHP	7.4.12 (fpm-fcgi)
MariaDB	10.3.17-MariaDB
ICU	65.1

me too, the same error, does someone has a solution?

Also getting this error with the latest docker image of mediawiki.

I found out how to do this, the key part is very much missing from the documentation as it says "no configuration"

Add this to LocalSettings.php to use default 1.35 Parsoid code wfLoadExtension( 'Parsoid', 'vendor/wikimedia/parsoid/extension.json' );

I have tried this but still getting the same result

So I did various other things.

I added this to my php.ini

curl.cainfo ="/etc/cacert.pem"

I download the file from curl's site at http://curl.haxx.se/ca/cacert.pem

I tried manually curling my site's api page

curl --cacert /etc/cacert.pem https://<my wiki site>/api.php

That still gave me an error

curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

So I added my SSL pem cert to the end of the file /etc/cacert.pem

Then I added this to my LocalSettings.php

wfLoadExtension( 'Parsoid', '/home/un9/mediawiki/vendor/wikimedia/parsoid/extension.json' );
$wgGroupPermissions['user']['writeapi'] = true;

That's what I did and now it works, not sure if every step is necessary.

Hi Everyone,

I'm tossing this out there since it is a blocker for us. We have a CentOS 7 VM with Red Hat Software Collections (SCL) enabled. We are currently on Mediawiki 1.34, and we cannot migrate to Mediawiki 1.35.

The problem is, Red Hat's SCL only provides PHP 7.3.11. The platform does not offer a PHP that meets minimum requirements for Mediawiki 1.35.

If Mediawiki downgrades the PHP requirements then we can perform the migration.

For completeness, CentOS 7 offers versions of PHP 7.0, 7.1, 7.2 and 7.3. There is no version of 7.4 available.

Also see CentOS Issue 0017826: CentOS 7 with SCL enabled only provides PHP 7.3.11.

I am trying to install on xampp this new version but before setting up the wiki it gives me "internal error Installing some external dependencies (e.g. via composer) is required."

Can someone fix the version for xampp please?

> Installing some external dependencies (e.g. via composer) is required.

I don't know about XAMPP specifically. However, on Linux, here is the procedure we use to update Mediawiki and components via Composer: wiki-upgrade.txt. Steps (5), (6), (7) and (9) are the important ones for Composer.

Hey world!

Do w know when we can have full 1.35 LTE to download?

Hopefully on Friday, if not before. Barring any unforseen issues...

Hy @all!

The migration from parsoid to php really is a game changer! Fantastic! VisualEditor works like a charm.

I tried some more and figured out, that with this release I have trouble saving (or also migrating) lemmas with UTF-8 chars (German Umlaute).

Neither can I save them, nor can I open them (e.g. after importing from another wiki)

At the moment I have no idea how to proceed: Can I provide you any specific data ?

I'm using Lua and semantic wiki.

Bug or feature? I don't know if the problem exists because of misconfig or bug. Umlaute are correctly formatted within the text.

If you tell me where I can write down this topic (if this is not the right place) or whom to address I'll gladly do this.

Thanks a lot and stay COVID-free ;-)

Edit: Here are some general information about my installation:

Software Version

MediaWiki 1.35.0-rc.3

PHP 7.4.10 (fpm-fcgi)

MariaDB 10.2.33-MariaDB-1:10.2.33+maria~bionic

ICU 60.2

Lua 5.1.5

What do you mean by "Lemmas"?

Hi Reedy,

sorry, too long editing in German wikipedia. A content site and also its header is called a lemma there.

Here is an example lemma I was not able to import due to it's "ä" in the header: "Liste der Säugetiere in Deutschland"

https://de.wikipedia.org/wiki/Liste_der_Säugetiere_Deutschlands

Ok, so a lemma is just an "article" or a "content page".

Did you already have any of these pages on your wiki? Do they still work?

Great question. The already existing pages with Umlaut are working correctly. I tried to create a short one myself, and this does work properly as well. Obviously it is not the wiki engine itself which have difficulties here, it might be the problem of one of the extensions (lua maybe?) I will dig deeper and come up with new information. Thanks for that hint!

Hey guys,

Congratulations on the RC release of the much anticipated v1.35. I am super excited knowing that Parsoid and VisualEditor are going to be bundled together within this release.

I installed it just now (using this tarball: https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0-rc.0.tar.gz), ran the installation using PostgreSQL as the database backend and Nginx/PHP-FPM as the HTTP server. I tried editing a page and it defaults to VisualEditor UI, but it stopped short at "Error contacting the Parsoid/RESTBase server: (curl error: 7) Couldn't connect to server".

I found that it is installed, located at the "vendor/wikimedia/parsoid" folder, but how do I get from there? I tried adding this:

wfLoadExtension( 'Parsoid' );

... but it threw this error:

Unable to open file /var/www/mediawiki/extensions/Parsoid/extension.json

Please advise. Thank you!

I believe you can include extensions from non-standard directories with something like the following:

wfLoadExtension( 'Parsoid', "$IP/vendor/wikimedia/parsoid/extension.json" );

However, my one reservation is that I'm not sure if this is the right version of Parsoid. Neither extension.json nor composer.json includes a version number as far as I can see, and HISTORY.md seems out of date.

You shouldn't need to do anything at all. Did you unset VisualEditorParsoidAutoConfig?

Similar situation, but I got

Error contacting the Parsoid/RESTBase server (HTTP 404)

In my nginx log I found

127.0.0.1 - - [16/Aug/2020:15:45:09 +0800] "GET /rest.php/prts.xwbx.ink/v3/page/html/%E9%A6%96%E9%A1%B5/31?redirect=false&stash=true HTTP/1.1" 404 169 "-" "VisualEditor-MediaWiki/1.35.0-rc.1"

2020/08/16 15:45:09 [error] 21#21: *565 open() "/var/www/html/mediawiki/rest.php/prts.xwbx.ink/v3/page/html/首页/31" failed (20: Not a directory), client: 127.0.0.1, server: prts.xwbx.ink, request: "GET /rest.php/prts.xwbx.ink/v3/page/html/%E9%A6%96%E9%A1%B5/31?redirect=false&stash=true HTTP/1.1", host: "prts.xwbx.ink"

maybe there is some configure I shoud do with nginx?

Link to the active release notes.

Would it be helpful to have a draft list of changes in each major release, at a coarse granularity? We already know that 1.35 will include Parsoid/PHP and support PHP 7.4, for example. Or do we? I came to the release page (also the roadmap) hoping to find out and leave still feeling slightly confused about what the plans are for 1.35.

If there's agreement that we should keep updated with some feature hints here, I'd be happy to do my editing shift!

I can see how there might be reasons to not do this as well, such as to avoid disappointment when a feature is pulled.

MW 1.35 will support Parsoid/PHP looking at the release notes. But yes, something like that would be helpful.

I see now, so maybe it's enough to link to https://phabricator.wikimedia.org/source/mediawiki/browse/REL1_35/RELEASE-NOTES-1.35 ...

The RELEASE-NOTES file is the parking lot.

I've added the link here, maybe it's useful to others.

Where's the best place to look for information around the release date? The page links to a MediaWiki 1.35 Branch Cut

anticipated at the beginning of August, is there anywhere else with some more up to date information, message board etc?

No, this is the correct on-wiki venue; announcements to wikitech-l and mediawiki-l might be a few minutes quicker, but not much. As and when people know more, I'm sure this will be updated.

rc.0 has just been released now – https://releases.wikimedia.org/mediawiki/1.35/

Note that this is a testing pre-release, and shouldn't be used for production sites.

Is MW 1.35 going to support PHP 7.4?

That's the plan. Currently we're waiting on upstream for one of our key libraries, and then we'll have to go through all the extensions and skins to check their compatibility futher (we've already found and fixed a number of issues).

MW 1.35 will still support running on PHP 7.2 and PHP 7.3 as well, however (I think).

In fact, the older 1.34 already supports PHP 7.4, so 1.35 will as well.

In fact, the older 1.34 already supports PHP 7.4, so 1.35 will as well.

This isn't true. Bits of it may work, but we found several things in developing 1.35 that weren't working correctly, and there are likely still more in popular extensions, let alone random ones people might find, sadly.

Huh, Compatibility#PHP claims the opposite. It tells not only 1.34 supports PHP 7.4. According to said page, PHP 7.4 support even reaches back to 1.31.

Aha, it was wrongly added by @Jörgi123 in https://www.mediawiki.org/w/index.php?diff=3773590&oldid=3440793&title=Template:Compatibility_PHP; will fix.

Thank you for taking care. :-)

Hello!

By the informations i found, the new version will come in 2 months. Is there any place where I can find new infos about the 1.35? Because this page is still empty.

Thanks

You can read the current version of the RELEASE-NOTES-1.35, but it's not final yet.

Thanks!