Extension talk:BetaFeatures

Previous page history was archived for backup purposes at Extension talk:BetaFeatures/LQT Archive 1 on 2015-07-10.

I'm seeing this error:

Error 1146: Table 'foo_wiki.foobetafeatures_user_counts' doesn't exist (localhost)

Function: MediaWiki\Extension\BetaFeatures\Hooks::getUserCounts

Query: SELECT feature,number FROM `foobetafeatures_user_counts` WHERE feature = 'popupsreferencepreviews'

I have the backtrace, if that helps. I was able to confirm that foobetafeatures_user_counts does exist (confirmed both by update.php and by visual inspection of the DB). Can anyone help me sort this out?

As a note, I'm running Mediawiki 1.36.2.

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

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

Sorry, I don't understand your question.

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.

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.

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

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

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.

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.

bye.

Thanks for the suggestion; I've cleaned it up and posted it as a patch at https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/BetaFeatures/+/587879 but I don't have a local postgres install to test this with.

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

Documented.

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

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

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

I added some documentation to the page here.

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

Filed as https://phabricator.wikimedia.org/T181821, fixed in https://gerrit.wikimedia.org/r/#/c/394739/.

Reverted back to 'updated' info and discussion links.

So, I updated the links to not point to the extension namespace in https://www.mediawiki.org/w/index.php?title=Extension:BetaFeatures&diff=prev&oldid=2390878 as that is what I was told was expected in https://gerrit.wikimedia.org/r/#/c/332904/ by @Jdforrester (WMF).

This change has since been reverted by @Shirayuki so I was wondering if we could come to some sort of agreement here for a best practise and what should be documented.

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

Thanks for the undo

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?

Thanks!

AT

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.

Hi,

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

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

philed as phab:T78512

The paraminfo says the helpurls is Extension:BetaFeatures/API, but that page doesnt exist.