Extension talk:BetaFeatures

Jump to navigation Jump to search

About this board


Summary by Kghbln

Not a question, just a note on how to find the settings to this configuration parameter.

Kghbln (talkcontribs)

The key can be found by searching codesearch. I guess the result is everything one can add the the configuration parameter.

Jdforrester (WMF) (talkcontribs)

Sorry, I don't understand your question.

Kghbln (talkcontribs)

This is actually not a question. It is a note/reminder. Since you oppose to keep a list of settings to this configuration parameter and I am sick of searching my b.... off every time I look for them I figured that just adding this as a note/reminder is the best we can do.

Jdforrester (WMF) (talkcontribs)

OK. But your assertion is wrong. Not everything uses the key only for the Beta Feature preference to see if it's enabled – see for example VisualEditor. If you really need to know, look at array keys returned on the GetBetaPreferences hook for values. But, again, you absolutely should not ever use this.

Kghbln (talkcontribs)

I guess this is just a complete mess. I seek for a list of these keys. So how do I do this?

Jdforrester (WMF) (talkcontribs)

Don't? This is a bespoke, one-off feature for me personally to manage as a last-gasp security wrapper around Wikimedia production.

Kghbln (talkcontribs)

I did not understand your answer. The issue I am trying to solve is hiding features which do not make any sense for isolated instances, e.g. "Compact language links" are things which are more or less senseless to offer to users in such environments.

Reply to "$wgBetaFeaturesWhitelist" (talkcontribs)

The script: sql/create_counts.sql do not work in PostgreSQL Database 11. 11 is the Version i use. I change the script into:

CREATE TABLE <your_wg_prefix_here>.betafeatures_user_counts (

  feature character varying(255) NOT NULL,

  "number" integer NOT NULL DEFAULT 0,

  CONSTRAINT betafeatures_user_counts_pkey PRIMARY KEY (feature)


now it works.


Jdforrester (WMF) (talkcontribs)
Reply to "PostgreSQL 11 Database"

Options to turn on features by default

Chowpakhin (talkcontribs)

Is it possible to make an config options to include any feature to be turned on by default?

Reply to "Options to turn on features by default"


Summary by Kaldari


Kaldari (talkcontribs)

@MarkTraceur: Could you add documentation about the mysterious $wgBetaFeaturesWhitelist config variable?

Jdforrester (WMF) (talkcontribs)

It's documented in operations/mw-config which is the only place it's used, I believe.

Addshore (talkcontribs)

@Jdforrester (WMF) it is an extension global & in the extension code so should probably be documented here in the extension docs.

Kaldari (talkcontribs)

I added some documentation to the page here.

BetaFeatures extension is not compatible with php7.2

星耀晨曦 (talkcontribs)

Today, I upgraded php7.1 to php7.2. Page tell me:

Fatal error: Declaration of HTMLFeatureField::getInputHTML($value) must be compatible with NewHTMLCheckField::getInputHTML($value, $attr = NULL) in /InstallPath/w/extensions/BetaFeatures/includes/HTMLFeatureField.php on line 26
Jdforrester (WMF) (talkcontribs)

Info & Discussion links

Summary by Addshore

Reverted back to 'updated' info and discussion links.

Addshore (talkcontribs)
Shirayuki (talkcontribs)

You should describe in the edit summary as such. "Update example help and talk urls" was not enough.

Addshore (talkcontribs)
AmazingTrans (talkcontribs)

I have downloaded the beta features and included it in mediawiki 1.25.1.

  1. I've placed "only" wfLoadExtension( 'BetaFeatures' ); in the localsettings.php.
  2. I've added MyExtension.php
  3. I've added MyExtensionHooks.php according to the auto-enroll groups script
  4. I've added SpecialMyExtension.php

In the beta link, all i got in there is the checkbox: Automatically enable all new beta feature

A. What do have to do next to add VisualEditor Opt-in, math function, media, sidebars etc?

B. What do i have to add in LocalSettings.php to call those hook?

C. Or maybe i'm misunderstanding this beta extension. Maybe, all it does is to create extension enable/disable in the beta category rather than in the overall extension directory?



MarkTraceur (talkcontribs)

Hi, sorry I missed this until now, but I think your point C is roughly correct, if unclear.

BetaFeatures is a ''framework'', it allows other extensions to register preferences as "beta" and gives them a nice visual display. It does not actually give you features.

Most of the extensions using BF as a framework offer the features they've marked as "beta" without BetaFeatures itself - if they don't, they're doing it Wrong - so you should feel free to simply install VisualEditor, Math, MultimediaViewer, or whatever else you want.

Reply to "Installing Beta Features"
Amire80 (talkcontribs)


The beta feature initialization can have requirements params, such as skins, javascript, blacklist, etc. Are they fully documented anywhere?

MarkTraceur (talkcontribs)

Somehow I doubt it...I think User:Jdlrobson is the one who implemented that stuff, maybe he can grace us with some documentation? :)

Reply to "Requirements params"
John Vandenberg (talkcontribs)
Reply to "Erroneous Help URL"
There are no older topics