I really do not understand the rationale behind removing this. I had the beta feature enabled, and now I have never seen a time on the site when I was not using HHVM again. Seems that something is broken. I am talking mainly about the en wikipedia, but I have observed this on other wikis, too.
Jump to navigation Jump to search
Reply to "Elimination of the PHP7 beta Selection"
Reply to "Tag PHP suddenly"
Reply to "Thanks for the really clear explanation"
Reply to "Moved out of Beta; "PHP7" still tagged in edit summary"
Reply to "Bug of course, but PHP7?"
It looks like the
Reply to "Is IP users enabled to choose whether to use the PHP7 feature?"
From what I can see in my browser, the cookie that should be sent is called
Reply to "Here's a bug"
Reply to "lua / maps issue"
Elimination of the PHP7 beta Selection
Tag PHP suddenly
Hello from en.wiktionary. Suddenly, since the 27th of May, all my edits are marked with the phrase: '''Tag: PHP7'''. How could I stop it from appearing please? --Sarri.greek (talk) 03:36, 29 May 2019 (UTC) [Sarri.email@example.com (talk)]
Ok! thanks: it vanished --~~~~
10% of all traffic is currently being randomly assigned to the PHP7 testing servers. The tag will show up on any edits made from servers running php7 to help us track issues that may ultimately be related to the php7 software. This isn't anything that a particular editor should be concerned about.
If it doesn't concern us and isn't an issue, then make the tagging invisible to the editors. What purpose does it serve marking all the public spaces with this backend issue?~~~~
@LlywelynII MediaWiki doesn't generally have different levels of user interface details for editors vs patrollers vs other general classes of users. These tags are very useful for patrollers and folks working on the roll-out of the PHP7 runtime system as they help us correlate problems seen in the content with the PHP runtime that was active when the changes were made.
Thanks for the really clear explanation
I am not technical at all but I found the explanation really easy to understand. Thanks whoever wrote it :)
Moved out of Beta; "PHP7" still tagged in edit summary
I noticed that PHP7 is no longer a Beta Feature. However, I see that "PHP7" is still tagged in edit summaries. Is "PHP7" tagging still necessary? If so, how long?
The removal of the beta feature doesn't mean the functionality is gone. 5% of users, randomly selected, go to PHP7. I expect they will continue tagging until 100% of users get PHP7.
@Krenair is correct.
When do you believe will 100% of users get PHP7?
Looking at phab:T219127 they appear to be targetting the next six weeks.
Bug of course, but PHP7?
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.
?safemode=1, e.g. https://fr.wikipedia.org/w/index.php?title=Special:Random&redirect=no&veaction=edit&safemode=1 – if you can find a way to replicate your issue in safe mode, I'd be very interested!
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!
Is IP users enabled to choose whether to use the PHP7 feature?
I have noticed some edits in Chinese Wikipedia. It seems that an IP user can choose which PHP engine they use?
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.
@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.
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)
Using PHP7 via the API
PHP_ENGINE cookie to
php7 to use PHP7 in a tool’s API requests
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.
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.
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.
Here's a bug
Note how the sample unblock request is signed. ~~~~
Is that really PHP7 related? I'd expect an editor bug to have happened instead.
lua / maps issue
"The is showing "Syntax error" as an output for all instances of its use (for example, and ."
When previewing the page, it seems that toggling php7 beta feature triggers this error.
This might be the same issue as T214984?
I fixed trailing comma's https://en.wikipedia.org/w/index.php?title=Template:Highway_system_OSM_map&diff=prev&oldid=882181669
and an incorrect value: https://en.wikipedia.org/w/index.php?title=Template:OSM_Location_map/Labelitem&diff=prev&oldid=882186194 (wikicode generated the literal 0 + 1, but json doesn't do calculations ;)
This seems to fix it. Interesting that the inline comments did not cause a validation error.
Lines appearing in "pending changes"-protected pages while enabling en-wp's Legacy Toolbar gadget and using IE11
Realized that it's not the fault of PHP7 but the gadget itself.
Open Microsoft Internet Explorer 11, especially if you have either Microsoft Windows 7 or 8
- The PHP7 Beta feature should be enabled.
- Then go to "Gadget" tab in Preferences
- Un-check the "Enable the editing toolbar" (2010 wikitext editor) to disable the toolbar
- When the editor goes back to the default/2003, toolbar-less editor, checkmark the "Enable the legacy (2006) editing toolbar" option
- Go to any page listed under w:en:Special:StablePages
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:
- the mouse pointer moves out of the editor (with the Legacy toolbar enabled)
- you press the "Enter" key within the editor
- you press "Page Down"/"PgDown" and/or the "Page Up"/"PgUp" key
- 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.