Talk:Beta Features/PHP7

Jump to navigation Jump to search

About this board

Tortliena (talkcontribs)

I activated the Beta of PHP7 today and tried to give it a go.

However, on my second (third?) edition, after I have tried to preview the article, my mouse went mad and everything I clicked or hovered on had some sort of offset compared to where the pointer actually is. For instance, if I wanted to click on the preview button, I had to have the mouse over the text edition zone, This offset changed every time I managed to preview or review my changes, without a clear pattern.

Also, this offset only applied inside the web page, not on Mozilla Firefox window (v65.0.2 64bits, it got that far?!), nor on my Windows computer.

Ultimately, I had to abandon the changes, because when I wanted to preview one last time before publishing them, all the edition zone and more generally the bottom of the page (including some of the article) went blank, like if someone cut it clean. Therefore, without the magic button :'(...

I did not register to any other beta (the last one about mixing wikicode editor and the visual one's toolbar gave me the itches, due to how fearful the publish-but-you-can-also-preview-and-review-changes button is). However I do use some gadgets, which are :

  • AncreTitres : Adds links to copy in the clipboard the internal links or URLs to reach directly a section.
  • ArchiveLinks : Adds a link to [archive] next to every external link, pointing to a cached version. This is actually a gadget??
  • LastContrib : Indicates on page loading whether it has been modified recently or not, to avoid nasty conflicts. Never saw it, to be honest.
  • DotsSyntaxHighlighter : More colorful colors on the wikicode editor.
  • MonobookToolbarStandard : Adds the standard buttons during the -layouting? in French it's "mise en forme"- when editing an article. The question is, what is the standard? And why is it not standard to have the standard buttons?
  • DeluxeHistory : More colorful colors in the history!
  • Wdsearch : Don't actually know what it does; maybe it was on by default when I registered? Description is talking about adding Wikidata when researching on Wikou and add them at the bottom of the page. When I think about it, if I don't know what it does, why do I have it x_x.
  • Accessibilité : A toolbox for accessibility on the left menu.
  • Oh and not in the gadget menu, but I have the fast preview enabled to avoid a full page refresh every time I want to preview/review.

In my opinion, none of the gagdets are responsible for that. I mean, they've been on for more than a year and more than 365 edits, so the reverse would be surprising.

Jdforrester (WMF) (talkcontribs)

I don't think it's likely that the PHP runtime will have an impact on the JavaScript experience directly. It's possible that there was already a race condition between your gadgets that is exposed due to different server-side timings. I'd recommend disabling all gadgets and then enabling them one by one until it works. Note that you can load a page without any gadgets, users scripts, or site scripts with ?safemode=1, e.g. – if you can find a way to replicate your issue in safe mode, I'd be very interested!

Tortliena (talkcontribs)

Oh no! Not my colorful history and wikicode... Alas, the bug is not happening frequently, so enabling the gadgets one by one will probably make me miss the bug.

But alright, I'll disable all gadgets for a while (most of them aren't useful to me anyway :p) and I will reach back to you if I stumble on the issue again!

Reply to "Bug of course, but PHP7?"

Is IP users enabled to choose whether to use the PHP7 feature?

WQL (talkcontribs)

I have noticed some edits in Chinese Wikipedia. It seems that an IP user can choose which PHP engine they use? (talkcontribs)

It looks like the PHP_ENGINE cookie, which the beta feature uses, is not deleted on logout, so if a user selects the PHP7 beta feature and then logs out, I think they’ll continue to use PHP7. Perhaps that is what happened here?

That said, there are also plans to enable PHP7 for some anonymous users as part of A/B testing (T216676), so I would expect this to happen more frequently soon.

WQL (talkcontribs)

@Lucas Werkmeister (WMDE): Some local sysops are wondering if these IPs are socket puppets, since enabling a beta feature manually is strange for an IP user. Anyway, thank you.

Lucas Werkmeister (WMDE) (talkcontribs)

Bahaha, I had logged out on metawiki to test this and apparently I needed to reload this talk page after the re-login :D (filed T217774 for this)

Reply to "Is IP users enabled to choose whether to use the PHP7 feature?"
Summary by Lucas Werkmeister

set the PHP_ENGINE cookie to php7 to use PHP7 in a tool’s API requests

Lucas Werkmeister (talkcontribs)

As a tool author, is there a way I can set the API requests I make to use PHP7 instead of HHVM? That might provide some additional coverage of code not usually reached by website users.

Mainframe98 (talkcontribs)

The way the beta feature works is by setting a cookie, which is sent along with every request. The cookie indicates PHP7 should be used - extract this cookie and adjust the tool so that it will always send that cookie along with its requests.

Mainframe98 (talkcontribs)

From what I can see in my browser, the cookie that should be sent is called PHP_ENGINE and should have the value of php7, as observed by toggling the beta feature.

Lucas Werkmeister (talkcontribs)
Drmies (talkcontribs)
ToBeFree (talkcontribs)

Is that really PHP7 related? I'd expect an editor bug to have happened instead.

Reply to "Here's a bug"
TheDJ (talkcontribs)
Deskana (talkcontribs)

This might be the same issue as T214984?

TheDJ (talkcontribs)
Reply to "lua / maps issue"

Lines appearing in "pending changes"-protected pages while enabling en-wp's Legacy Toolbar gadget and using IE11

Summary by George Ho

Realized that it's not the fault of PHP7 but the gadget itself.

George Ho (talkcontribs)
  1. Open Microsoft Internet Explorer 11, especially if you have either Microsoft Windows 7 or 8
  2. The PHP7 Beta feature should be enabled.
  3. Then go to "Gadget" tab in Preferences
  4. Un-check the "Enable the editing toolbar" (2010 wikitext editor) to disable the toolbar
  5. When the editor goes back to the default/2003, toolbar-less editor, checkmark the "Enable the legacy (2006) editing toolbar" option
  6. Go to any page listed under w:en:Special:StablePages
  7. Use the mouse scroll wheel, i.e. mouse scroller, to scroll down the if your mouse has one.

Expected result: The lines should not appear around the editor.

Actual result: The lines appear when scrolling down and then up (seen in the below picture). The lines then disappears when:

  1. the mouse pointer moves out of the editor (with the Legacy toolbar enabled)
  2. you press the "Enter" key within the editor
  3. you press "Page Down"/"PgDown" and/or the "Page Up"/"PgUp" key
  4. you use a mouse to highlight any text within the editor

I wanted to take this to the Phabricator, but the gadget is not part of the Mediawiki software. I decided to describe the issue here instead.

I found out that it's the gadget itself, not the PHP7. I disabled the PHP7, and I found the same results.

What interest for the wikisource contributor ?

Summary by Krenair

Added a FAQ entry.

Hsarrazin (talkcontribs)

Hi, we have recently seen this Beta feature appear on wikisource, and like all beta features, I gave it a try... but I don't see any difference, nor do I understand what it should do.

Could you please explain ?

Krenair (talkcontribs)

It is a technical backend thing. Not seeing any difference is, in this case, ideal. It shows that using a different piece of software to run the wiki's code is not breaking anything noticeable.

Hsarrazin (talkcontribs)

OK, the thins is a PHP7 tag appears in log of Recent modifications, and there has been no explanations about it... admins and patrollers were a little anxious :)

Krenair (talkcontribs)

I have added an entry to the Q&A section. You'd think by now I would know how translations work around here, but I don't, so it might not show up right in translations. If someone reading this knows what to do please help :)

Hsarrazin (talkcontribs)

LOL I see what you mean ! I'm always in trouble with it too...

ToBeFree (talkcontribs)

I am amazed by the possibility to enable something as deeply server-side as PHP7 in the beta preferences, with a single click, for only those who would like to participate in the beta project. Thank you for making both PHP7 and this beta test possible.

Krenair (talkcontribs)

I haven't looked into the mechanism in use but I wouldn't be surprised if it's a simple cookie or something that indicates to varnish to send to a different server, or to apache to handle differently or something. But yes, yay for testing new stuff.

Reply to "Beta feature"

PHP7 Timeout causes plaintext warning

Summary by ToBeFree

Moved to phab:T214660

ToBeFree (talkcontribs)


MediaWiki internal error.

Original exception: [XEparwpAIC0AAKvnybwAAACB] 2019-01-25 00:40:33: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"

Exception caught inside exception handler.

Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.

ToBeFree (talkcontribs)

The timeout is nothing new, my preferences show 1000 entries by default, and that's too much for 60 seconds. Wondering if PHP7 accelerates this process enough to finish within 60 seconds, I opened the page, and received plaintext instead of the "usual" warning design. I guess this is relatively intentional and can be ignored.

There are no older topics