Extension talk:BetaFeatures
This page used the Structured Discussions extension to give structured discussions. It has since been converted to wikitext, so the content and history here are only an approximation of what was actually displayed at the time these comments were made. |
Erroneous Help URL
The paraminfo says the helpurls is Extension:BetaFeatures/API, but that page doesnt exist. John Vandenberg (talk) 15:12, 1 December 2014 (UTC)
Requirements params
Hi,
The beta feature initialization can have requirements params, such as skins, javascript, blacklist, etc. Are they fully documented anywhere? Amir E. Aharoni (talk) 09:54, 9 December 2014 (UTC)
- Somehow I doubt it...I think User:Jdlrobson is the one who implemented that stuff, maybe he can grace us with some documentation? :) MarkTraceur (talk) 14:14, 9 December 2014 (UTC)
- philed as phab:T78512 Quiddity (WMF) (talk) 00:02, 15 December 2014 (UTC)
Installing Beta Features
I have downloaded the beta features and included it in mediawiki 1.25.1.
- I've placed "only" wfLoadExtension( 'BetaFeatures' ); in the localsettings.php.
- I've added MyExtension.php
- I've added MyExtensionHooks.php according to the auto-enroll groups script
- 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 AmazingTrans (talk) 16:31, 26 October 2015 (UTC)
- 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. MarkTraceur (talk) 15:11, 17 November 2015 (UTC)
Info & Discussion links
RESOLVED | |
Reverted back to 'updated' info and discussion links. |
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.
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. ·addshore· talk to me! 10:07, 20 March 2017 (UTC)
- You should describe in the edit summary as such. "Update example help and talk urls" was not enough. Shirayuki (talk) 10:17, 20 March 2017 (UTC)
- Thanks for the undo ·addshore· talk to me! 09:32, 22 March 2017 (UTC)
$wgBetaFeaturesWhitelist
RESOLVED | |
Documented. |
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.
@MarkTraceur: Could you add documentation about the mysterious $wgBetaFeaturesWhitelist config variable? Kaldari (talk) 20:08, 27 June 2017 (UTC)
- It's documented in
operations/mw-config
which is the only place it's used, I believe. Jdforrester (WMF) (talk) 11:33, 28 June 2017 (UTC) - @Jdforrester (WMF) it is an extension global & in the extension code so should probably be documented here in the extension docs. ·addshore· talk to me! 08:23, 29 June 2017 (UTC)
- I added some documentation to the page here. Kaldari (talk) 22:25, 18 October 2018 (UTC)
BetaFeatures extension is not compatible with php7.2
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.
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星耀晨曦 (talk) 16:40, 1 December 2017 (UTC)
- Filed as https://phabricator.wikimedia.org/T181821, fixed in https://gerrit.wikimedia.org/r/#/c/394739/. Jdforrester (WMF) (talk) 01:23, 5 December 2017 (UTC)
Options to turn on features by default
Is it possible to make an config options to include any feature to be turned on by default? Eagle (talk) 04:33, 30 May 2019 (UTC)
PostgreSQL 11 Database
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. 84.168.204.95 (talk) 17:38, 7 April 2020 (UTC)
- 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. Jdforrester (WMF) (talk) 22:31, 9 April 2020 (UTC)
$wgBetaFeaturesWhitelist
The key can be found by searching codesearch. I guess the result is everything one can add the the configuration parameter. [[kgh]] (talk) 20:07, 20 May 2020 (UTC)
- Sorry, I don't understand your question. Jdforrester (WMF) (talk) 16:57, 21 May 2020 (UTC)
- 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. [[kgh]] (talk) 17:52, 21 May 2020 (UTC)
- 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. Jdforrester (WMF) (talk) 16:02, 22 May 2020 (UTC) - I guess this is just a complete mess. I seek for a list of these keys. So how do I do this? [[kgh]] (talk) 16:06, 22 May 2020 (UTC)
- Don't? This is a bespoke, one-off feature for me personally to manage as a last-gasp security wrapper around Wikimedia production. Jdforrester (WMF) (talk) 17:19, 22 May 2020 (UTC)
- 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. [[kgh]] (talk) 15:03, 25 May 2020 (UTC)
Table 'foo_wiki.foobetafeatures_user_counts' doesn't exist (localhost)
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? Iresprite (talk) 21:19, 9 December 2021 (UTC)