Talk:MediaWiki 1.35

PHP 7.4 Support

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Is MW 1.35 going to support PHP 7.4? Nirobbins (talk) 16:17, 28 January 2020 (UTC)

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). Jdforrester (WMF) (talk) 18:23, 28 January 2020 (UTC)

In fact, the older 1.34 already supports PHP 7.4, so 1.35 will as well. 2001:16B8:1033:9A00:155:4D70:C667:17E9 (talk) 07:13, 10 May 2020 (UTC)

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. Jdforrester (WMF) (talk) 18:51, 12 May 2020 (UTC)

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. 2001:16B8:1005:FE00:8000:333E:D12D:4BAF (talk) 09:40, 30 May 2020 (UTC)

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. Jdforrester (WMF) (talk) 16:29, 1 June 2020 (UTC)

Thank you for taking care. :-) 2001:16B8:104C:8000:9CCB:FAE6:BF84:5B0F (talk) 21:11, 4 June 2020 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

1.35 version infos

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 165.225.72.124 (talk) 10:02, 24 March 2020 (UTC)

You can read the current version of the RELEASE-NOTES-1.35, but it's not final yet. Jdforrester (WMF) (talk) 16:24, 25 March 2020 (UTC)

Thanks! 165.225.84.159 (talk) 09:24, 26 March 2020 (UTC)

Release date info

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? Odoxo (talk) 11:47, 27 July 2020 (UTC)

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. Jdforrester (WMF) (talk) 09:40, 28 July 2020 (UTC)

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. Jdforrester (WMF) (talk) 14:10, 31 July 2020 (UTC)

MediaWiki 1.35.0-rc.0, VisualEditor, and Parsoid

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! Aixnr (talk) 20:03, 1 August 2020 (UTC)

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. Adamw (talk) 14:42, 10 August 2020 (UTC)

You shouldn't need to do anything at all. Did you unset VisualEditorParsoidAutoConfig? Jdforrester (WMF) (talk) 16:58, 10 August 2020 (UTC)

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? 夕舞八弦 (talk) 07:47, 16 August 2020 (UTC)

Is there a "parking lot" for upcoming features?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

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. Adamw (talk) 19:51, 9 August 2020 (UTC)

MW 1.35 will support Parsoid/PHP looking at the release notes. But yes, something like that would be helpful. Leaderboard (talk) 14:26, 10 August 2020 (UTC)

I see now, so maybe it's enough to link to https://phabricator.wikimedia.org/source/mediawiki/browse/REL1_35/RELEASE-NOTES-1.35 ... Adamw (talk) 14:36, 10 August 2020 (UTC)

The RELEASE-NOTES file is the parking lot. Jdforrester (WMF) (talk) 10:38, 11 August 2020 (UTC)

I've added the link here, maybe it's useful to others. Adamw (talk) 11:10, 11 August 2020 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

MediaWiki 1.35.0-rc.3: Problems with UTF-8 in Lemma

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 Yrwyddfa (talk) 16:56, 16 September 2020 (UTC)

What do you mean by "Lemmas"? Reedy (talk) 20:48, 16 September 2020 (UTC)

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 Yrwyddfa (talk) 20:41, 17 September 2020 (UTC)

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? Reedy (talk) 01:42, 18 September 2020 (UTC)

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! Yrwyddfa (talk) 20:06, 19 September 2020 (UTC)

The date of expected release

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hey world!

Do w know when we can have full 1.35 LTE to download? Fokebox (talk) 14:11, 22 September 2020 (UTC)

Hopefully on Friday, if not before. Barring any unforseen issues... Reedy (talk) 00:21, 23 September 2020 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Help

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? 181.31.245.15 (talk) 22:24, 25 September 2020 (UTC)

> 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. Noloader (talk) 06:15, 1 November 2020 (UTC)

Visual editor can't connect to server

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

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

Hcadby (talk) 10:15, 30 October 2020 (UTC)

me too, the same error, does someone has a solution? 91.166.116.231 (talk) 21:54, 10 November 2020 (UTC)

Also getting this error with the latest docker image of mediawiki. Bluedreamer1 (talk) 20:30, 22 November 2020 (UTC)

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' ); Bluedreamer1 (talk) 12:44, 23 November 2020 (UTC)

I have tried this but still getting the same result Hcadby (talk) 14:12, 23 November 2020 (UTC)

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. Bluedreamer1 (talk) 16:16, 23 November 2020 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

PHP 7.3.19 is too new for CentOS 7

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. Noloader (talk) 06:27, 1 November 2020 (UTC)

MediaWiki 1.35.1 release announcement, where is the Extensions Security Release Supplement?

[MediaWiki-announce] Security and maintenance release: 1.31.11 / 1.35.1 includes the sentence: "An "MediaWiki Extensions Security Release Supplement" email will follow this one." but this doesn't seem to have been sent. What extensions are impacted by security issues? Peculiar Investor (talk) 14:50, 18 December 2020 (UTC)

I personally would love to see these two announcements sent the same day to allow people touch their wiki at the same time. Anyhow, this announcement is still in the pipeline. If you have the Widgets extension running - you can update now. All the rest will be disclosed in the upcoming announcement. [[kgh]] (talk) 18:24, 18 December 2020 (UTC)

Thanks. Based on the first announcement and the fact that security fixes were publicly disclosed I would have thought they would come of close together for exactly the reason you mention. That would have been helpful. I had already found the information about the Widgets extension. Peculiar Investor (talk) 18:45, 18 December 2020 (UTC)

Given the number of Support Desk topics about character-encoding problems should the Release Notes for 1.35 include a warning?

There are a number of topics in the Support Desk that indicate that installing/upgrading to MediaWiki 1.35.x can render a wiki unusable. See Index.php displayed with wrong characters on Project:Support desk (mediawiki.org) and Has MW 1.35 changed when/how the HTTP header, Content-Length, are used? on Project:Support desk (mediawiki.org) as two examples, there are more.

This is being tracked as ⚓ T235554 MediaWiki::outputResponsePayload seemingly causes net::ERR_HTTP2_PROTOCOL_ERROR 200 and compression issues in 1.35 (wikimedia.org) and a few others.

Should the Release Notes page include a warning about these problems so that anyone upgrading is aware of the problem? Peculiar Investor (talk) 14:11, 1 January 2021 (UTC)

I believe that this should be finally fixed as of 1.35.2. Jdforrester (WMF) (talk) 03:42, 9 April 2021 (UTC)

MediaWiki 1.35 internal error - Installing some PHP extensions is required.

I have just installed MediaWiki and am getting the below error. I do not know what I need to do. I have called my host site, HostGator, and they did not know what to do. I have tried installing MediaWiki using the installer in my cPanel. I have also extracted the MediaWiki tar file and both result in the same internal error.

I do not know how to install or add the below extensions. The links do not provide any downloads either.

I am using HostGator as my host site. I have updated my PHP to version 7.3.26. The domain is an addon domain.

I have been trying to research this issue for a while now and I cannot find anything online to help.

---

MediaWiki 1.35 internal error

Installing some PHP extensions is required.

Required components

You are missing a required extension to PHP that MediaWiki requires to run. Please install:

• mbstring (more information)
• xml (more information)
• ctype (more information)
• json (more information)
• iconv (more information)
• fileinfo (more information) WillC93 (talk) 00:35, 17 January 2021 (UTC)

net::ERR_HTTP2_PROTOCOL_ERROR 200

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

After the upgrade to MediaWiki 1.35 we run into annoying errors on some (Special-)Pages with Edge, Chrome and Internet Explorer.

Blank page, nothing worked, not one byte was loaded. The console in the webdeveloper window shows error net::ERR_HTTP2_PROTOCOL_ERROR 200

First thought was, that we had issues with the SSL certificate. But it wasn't.

Then we found https://phabricator.wikimedia.org/T235554

$wgDisableOutputCompression  = true;

in the LocalSettings solved the problem. 80.152.229.133 (talk) 09:55, 21 January 2021 (UTC)

It solved the problem for us too, but only on 1.35.0, after that per the phab task there is not a resolution as of yet for folks that encountered this issue previously. Setting $wgDisableOutputCompression  = true; in 1.35.1 only resulted in random characters being displayed for Chrome and iOS Safari (on our setup). For us the 1.35.0 problem happened on FF, Chrome and iOS Safari (Edge always being fine, edge still being fine on 1.35.1, where FF is now also fine on 1.35.1, but Chrome and iOS were messed up, strangely got Chrome working by accident by toggling on and off random caching options... then putting it back to exactly how I had it before!--inexplicable, and iOS Safari still broken with "cannot parse response" error). --We're using Dreamhost VPS. Trying to decide if we should move our prod site to 1.35.0 with $wgDisableOutputCompression  = true; so we can have VE, or if other issues might emerge... for now staying on our current version. TiltedCerebellum (talk) 08:28, 26 February 2021 (UTC)

Is there a conclusive fix for this problem ?

Thanks. Nipperus (talk) 10:06, 3 March 2023 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

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

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Getting this error when trying to use the visual editor. Can create a new page fine but cannot save them (same error).

MediaWiki	1.35.1
PHP	7.3.25 (apache2handler)
MariaDB	10.3.27-MariaDB
ICU	63.1

Any help is appreciated. Sccotty (talk) 10:53, 5 February 2021 (UTC)

This section may help you: Extension:VisualEditor#Troubleshooting. Jaider ^msg 14:00, 10 February 2021 (UTC)

Meine Lösung:

setsebool -P httpd_can_network_relay 1 2003:C0:4F1B:CB40:78F1:237A:6989:B7B9 (talk) 11:47, 15 February 2021 (UTC)

sudo setenforce 0

worked for me! SELINUX causing problems. Vick Dolce (talk) 02:25, 26 May 2021 (UTC)

@Jaideraft

this section didn't provide a really solution, just an explication. Xiangpeng.zhang (talk) 04:55, 31 October 2021 (UTC)

Try to add next line to your LocalSettings.php

$wgCanonicalServer = "http:||localhost:80"; 178.88.191.208 (talk) 13:27, 15 February 2022 (UTC)

|| replace with // 178.88.191.208 (talk) 13:28, 15 February 2022 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

PHP 8

Regarding the PHP 8 incompatibility notice, I am using MediaWiki 1.35.1 LTS with PHP 8.0.1 and haven't had any problems yet. Nicole Sharp (talk) 04:23, 28 February 2021 (UTC)

Possible fix for Parsoid PHP curl error: 7 in Docker

I noticed that if the service name of the MediaWiki Container is the same as the domain e.g.:

...
services:
  my-wiki.com:
    image: mediawiki:1.35.0
    container_name: my-wiki.com

...

VisualEditor will fail with either 404 or curl error 7

After suffixing or prefixing the service and container_name with an arbitrary string like:

...
services:
  my-wiki.com_mw:
    image: mediawiki:1.35.0
    container_name: my-wiki.com_mw

...

VisualEditor successfully connected to Parsoid PHP.

The issue is, that containers running in compose automatically resolve to their name to the local ip of the container. In this case it tries to connect to the domain using the name (as intended) but then getting the local ip back which causes the error (at least when running https) Octfx (talk) 12:37, 19 March 2021 (UTC)

Maybe it is related to one of these: https://phabricator.wikimedia.org/T266971 Alistair3149 (talk) 13:16, 19 March 2021 (UTC)

MediaWiki 1.35/37

Následující řádek není připraven k překladu. ENeRZet (talk) 11:53, 8 June 2023 (UTC)

MediaWiki 1.35/43

Následující odrážky nejsou připraveny k překladu ENeRZet (talk) 11:54, 8 June 2023 (UTC)

MediaWiki 1.35/23

Následujících několik odrážek není připraveno k překladu ENeRZet (talk) 12:04, 8 June 2023 (UTC)

Not EOL yet?

MediaWiki 1.35 has been scheduled to be EOL'ed by the end of November, yet now is already December and it still has not been EOL'ed yet.

So, when will it be EOL'ed then? GTrang (talk) 04:00, 4 December 2023 (UTC)

I believe that as is usual there'll be a final release as part of the regular quarterly process. Jdforrester (WMF) (talk) 13:52, 4 December 2023 (UTC)