MediaWiki - User contributions [en]

Extension:BetaFeatures/es

2021-09-12T00:47:32Z

IShareFreedom: Created page with "Cada cadena debe ser el nombre de una característica beta tal y como se especifica en la definición de preferencias pasada a <code>onGetBetaFeaturePreferences()</code>."

<languages />
{{Extension
|status = stable
|type1 = media
|type2 = hook
|type3 = database
|newhook1 = GetBetaFeaturePreferences
|newhook2 = GetBetaFeatureDependencyHooks
|author = Mark Holmquist
|username = MarkTraceur
|description = Permite a otras extensiones registrar sus funcionalidades beta en las preferencias del usuario
|image = BetaFeatures 2013-09-06.png
|imagesize = 400
|update = Continous updates
|compatibility policy = rel
|mediawiki = 1.25+
|php = 5.4+
|download = {{WikimediaDownload|server=gerritonly}}
|readme =
|changelog =
|namespace = Special
|tags =
|example = [[Special:Preferences#mw-prefsection-betafeatures]]
|phabricator = BetaFeatures
|table1 = betafeatures_user_counts
}}

La extensión '''BetaFeatures''' permite a otras [[Special:MyLanguage/Manual:Developing extensions|extensiones de MediaWiki]] registrar funciones beta con la lista de preferencias de usuario en la wiki. Utiliza la arquitectura de preferencias del usuario existente y algunas páginas especiales para realizar su función.

== Instalación ==
{{ExtensionInstall
|repo-name=BetaFeatures
|db-update=1
|registration=required
|custom-steps=* [[#Configuration|Configurar como sea necesario.]]
}}

== Usando los nuevos ganchos en tu extensión ==

Usar esta extensión para respaldar tu función beta es fácil. Registre un gancho de tipo "{{ll|Extension:BetaFeatures/Hooks/GetBetaFeaturePreferences|GetBetaFeaturePreferences}}" en su archivo de {{ll|Manual:Extension registration|extension.json}}; la sintaxis es casi idéntica a la del gancho de {{hook|GetPreferences}}, con pequeños cambios para admitir el tipo de preferencia que necesitamos en este caso.

En <code>extension.json</code>:

<syntaxhighlight lang="json">
"Hooks": {
"GetBetaFeaturePreferences": "MediaWiki\\Extension\\MyExtension\\Hooks::onGetBetaFeaturePreferences"
},
</syntaxhighlight>

En <code>MyExtension/includes/Hooks.php</code>:

<syntaxhighlight lang="php">
namespace MediaWiki\Extension\MyExtension;
class Hooks {
public static function onGetBetaFeaturePreferences( User $user, array &$betaPrefs ) {
$extensionAssetsPath = MediaWikiServices::getInstance()
->getMainConfig()
->get( 'ExtensionAssetsPath' );
$betaPrefs['myextension-awesome-feature'] = [
// The first two are message keys
'label-message' => 'myextension-awesome-feature-message',
'desc-message' => 'myextension-awesome-feature-description',
// Paths to images that represents the feature.
// The image is usually different for ltr and rtl languages.
// Images for specific languages can also specified using the language code.
'screenshot' => array(
'ru' => "$extensionAssetsPath/MyExtension/images/screenshot-ru.png",
'ltr' => "$extensionAssetsPath/MyExtension/images/screenshot-ltr.png",
'rtl' => "$extensionAssetsPath/MyExtension/images/screenshot-rtl.png",
),
// Link to information on the feature - use subpages on mw.org, maybe?
'info-link' => 'https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:MyExtension/MyFeature',
// Link to discussion about the feature - talk pages might work
'discussion-link' => 'https://www.mediawiki.org/wiki/Special:MyLanguage/Help_talk:Extension:MyExtension/MyFeature',
];
}
}
</syntaxhighlight>
{{note|1=Por ahora, 'etiqueta-mensaje', 'desc-mensaje', 'info-enlaza', y 'discusión-enlaza' son necesarios. Asegúrese de utilizarlos todos.}}

Luego, puedes utilizar la función de conveniencia proporcionada por FuncionesBeta para verificar si la función está habilitada.

<syntaxhighlight lang="php" style="overflow:auto">
// SpecialMyExtension.php
class SpecialMyExtension extends SpecialPage {

public function execute() {
if ( BetaFeatures::isFeatureEnabled( $this->getUser(), 'my-awesome-feature' ) ) {
// Implement the feature!
}
}
}
</syntaxhighlight>

También puede usar una verificación de preferencia normal, pero no verifique con valores verdaderos o falsos; use los valores de la clase de CampodeCaracterísticasHTML.

<syntaxhighlight lang="php" style="overflow:auto">
// SpecialMyExtension.php
class SpecialMyExtension extends SpecialPage {

public function execute() {
if ( $this->getUser()->getOption( 'my-awesome-feature' ) === HTMLFeatureField::OPTION_ENABLED ) {
// Implement the feature!
}
}
}
</syntaxhighlight>

Dado que la BetaFeatures debería estar presente en todas partes, podrías utilizar la función conveniente en cualquier hook, página especial o cualquier otra cosa que quisieras. Sólo ten en cuenta los posibles problemas de rendimiento o de caché que puedas introducir con esos cambios.

Si quiere utilizar también su extensión ''sin'' BetaFeatures, deberá comprobar también su existencia, por ejemplo:

<syntaxhighlight lang="php">
if (
!ExtensionRegistry::getInstance()->isLoaded( 'BetaFeatures' )
|| \BetaFeatures::isFeatureEnabled( $user, 'my-awesome-feature' )
) {
// Implement the feature!
}
</syntaxhighlight>

{{anchor|Configuration}}
== Configuración ==
La variable de configuración <code>$wgBetaFeaturesWhitelist</code> puede utilizarse para limitar las características beta que se muestran en las preferencias.
Por defecto está vacío, y se muestran todas las características beta.

Si se utiliza, para que una función beta aparezca en las preferencias debe figurar en la lista blanca.
Este config la variable acepta una variedad de cuerdas.
Cada cadena debe ser el nombre de una característica beta tal y como se especifica en la definición de preferencias pasada a <code>onGetBetaFeaturePreferences()</code>.
<span lang="en" dir="ltr" class="mw-content-ltr">For example, in the code given above, the name of the beta feature is <code>myextension-awesome-feature</code>, so you would need to add that string to the <code>$wgBetaFeaturesWhitelist</code> array in your wiki's configuration:</span>

<syntaxhighlight lang="php">$wgBetaFeaturesWhitelist = [
'myextension-awesome-feature'
];
</syntaxhighlight>

== Uso avanzado ==

¿Quieres ver algo realmente genial?

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Auto-enroll groups ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
With this example, we register a preference that's an "auto-enroll" one - if a user checks this, and new features come out that are in a particular group, the user will be automatically enrolled in those features.
</div>

<syntaxhighlight lang="php" style="overflow:auto">
// MyExtensionHooks.php
class MyExtensionHooks {

static function getPreferences( $user, &$prefs ) {
global $wgExtensionAssetsPath;

$prefs['my-awesome-feature-auto-enroll'] = array(
// The first two are message keys
'label-message' => 'beta-feature-autoenroll-message',
'desc-message' => 'beta-feature-autoenroll-description',
// Link to information on the feature - use subpages on mw.org, maybe?
'info-link' => 'https://wwww.mediawiki.org/wiki/Special:MyLanguage/MyFeature',
// Link to discussion about the feature - talk pages might work
'discussion-link' => 'https://www.mediawiki.org/wiki/Talk:MyFeature',
// Enable auto-enroll for this group
'auto-enrollment' => 'my-awesome-feature-group',
);

$prefs['my-awesome-feature'] = array(
// The first two are message keys
'label-message' => 'beta-feature-message',
'desc-message' => 'beta-feature-description',
// Paths to images that represents the feature.
// The image is usually different for ltr and rtl languages.
// Images for specific languages can also specified using the language code.
'screenshot' => array(
'ru' => "$wgExtensionAssetsPath/MyExtension/images/screenshot-ru.png",
'ltr' => "$wgExtensionAssetsPath/MyExtension/images/screenshot-ltr.png",
'rtl' => "$wgExtensionAssetsPath/MyExtension/images/screenshot-rtl.png",
),
// Link to information on the feature - use subpages on mw.org, maybe?
'info-link' => 'https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:MyExtension/SomeFeature',
// Link to discussion about the feature - talk pages might work
'discussion-link' => 'https://www.mediawiki.org/wiki/Extension_talk:MyExtension/SomeFeature',
// Add feature to this group
'group' => 'my-awesome-feature-group',
);
}
}
</syntaxhighlight>

=== Administración de dependencias ===

<div lang="en" dir="ltr" class="mw-content-ltr">
Next up, we can actually define dependency management per-feature. To do this we first register the ''name'' of a hook that we want to use for this with the hook "[[Manual:Hooks/GetBetaFeatureDependencyHooks|GetBetaFeatureDependencyHooks]]", then we register a hook of that type that checks some dependency, and returns '''true''' if it's met or '''false''' if not.
</div>

<syntaxhighlight lang="php" style="overflow:auto">
// MyExtension.php
$wgAutoloadClasses['MyExtensionHooks'] = __DIR__ . '/MyExtensionHooks.php';
Hooks::register( 'GetBetaFeaturePreferences', 'MyExtensionHooks::getPreferences' );
Hooks::register( 'GetBetaFeatureDependencyHooks', 'MyExtensionHooks::getDependencyCallbacks' );
Hooks::register( 'CheckDependenciesForMyExtensionFeature', 'MyExtensionHooks::checkDependencies' );
</syntaxhighlight>

<syntaxhighlight lang="php" style="overflow:auto">
// MyExtensionHooks.php
class MyExtensionHooks {

static function getPreferences( $user, &$prefs ) {
global $wgExtensionAssetsPath;

$prefs['my-awesome-feature'] = array(
// The first two are message keys
'label-message' => 'beta-feature-message',
'desc-message' => 'beta-feature-description',
// Paths to images that represents the feature.
// The image is usually different for ltr and rtl languages.
// Images for specific languages can also specified using the language code.
'screenshot' => array(
'ru' => "$wgExtensionAssetsPath/MyExtension/images/screenshot-ru.png",
'ltr' => "$wgExtensionAssetsPath/MyExtension/images/screenshot-ltr.png",
'rtl' => "$wgExtensionAssetsPath/MyExtension/images/screenshot-rtl.png",
),
// Link to information on the feature - use subpages on mw.org, maybe?
'info-link' => 'https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:MyExtension/SomeFeature',
// Link to discussion about the feature - talk pages might work
'discussion-link' => 'https://www.mediawiki.org/wiki/Extension_talk:MyExtension/SomeFeature',
// Mark as dependent on something
'dependent' => true,
);
}

static function getDependencyCallbacks( &$depHooks ) {
$depHooks['my-awesome-feature'] = 'CheckDependenciesForMyExtensionFeature';
return true;
}

static function checkDependencies() {
$dependenciesMet = false;
// Do some fancy checking and return the result
return $dependenciesMet;
}
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can <s>abuse</s> use this feature to do per-wiki disabling of features, if they're marked as dependent. But that sounds really hacky. You probably shouldn't. I can hear you thinking about it right now, just stop it.
</div>

== Consideraciones sobre la base de datos ==

<div lang="en" dir="ltr" class="mw-content-ltr">
There's a database table (<code>betafeatures_user_counts</code>) defined, and used, by BetaFeatures. But you might get confused by it if you try to use it locally.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
We use the job queue to run updates for this table, when the cache expires (30 minutes TTL). If your wiki is configured to run jobs on each request, this will make about one request every 30 minutes reeeeeeally slow, but the rest will be relatively fast. If you configure your wiki to run jobs via cron, things will work much better.
</div>

== Véase también ==

* [[Beta_Features/es|Funcionalidades Beta]]
* [[Extension:BetaFeatures/Roadmap|Hoja de ruta]]
* [[Extension:BetaFeatures/Rollout plan|Plan de lanzamiento]]
{{onWikimedia}}

[[Category:Beta Features{{#translation:}}]]

2021-09-08T11:44:57Z

IShareFreedom: traducción semi completa

Tendrás que instalar versiones actualizadas del {{ll|Manual: de MediaWiki en Red Hat Linux#Instalar paquetes del sistema operativo|Colección de Software (SCL) o "AppStreams"}}

MediaWiki 1.35/es

2021-09-08T11:41:00Z

IShareFreedom:

<languages/>
{{Expand}}
{{MW release status|legacy}}

'''MediaWiki 1.35''' es la versión actual con soporte a largo plazo de MediaWiki.
Consultar el archivo {{RELEASE-NOTES|MediaWiki 1.35}} para la lista completa de cambios.
Se implementó en los wikis de la Fundación Wikimedia a través de incrementales secundarios de-"{{ll|WMF product development process|wmf}}" a partir del 1 de octubre de 2019.
La versión estable 1.35.0 salió el 25 de septiembre de 2020.
Descargue {{MW legacy release link}} o consulte la sucursal de <code>{{git file|text=REL1_35|project=mediawiki/core|branch=REL1_35}}</code> [[Special:MyLanguage/Download from Git|en Git]] para seguir este lanzamiento.
Dejará de recibir soporte en Septiembre de 2023.
{{clear}}
{{MediaWiki Release navigation|1.35}}

{{warning|1=MediaWiki 1.35 ya no soporta PHP 7.2. Se requiere PHP 7.3.19 o posterior.}}
{{MediaWiki PHP 8}}
=== Nuevas funcionalidades ===

* Páginas especiales -Special: EditPage, Special: PageHistory, Special: PageInfo y Special: Purge- se han creado como accesos directos para cada acción. Especial: EditPage/Foo redirige a title=foo&action=edit, con PageHistory, PageInfo, and Purge corresponding to &action= history, info and purge respectively. Cuando está vinculado a, su subpágina se utiliza como destino. De lo contrario, muestra un dispositivo periférico básico para permitir que el usuario especifique el objetivo, manualmente (consulte {{Phab | T13456}}).
* El formulario en "?action=watch" tiene una nueva lista desplegable para admitir las fechas de vencimiento de los elementos de la lista, (if{{Ll|Manual:$wgWatchlistExpiry|
<code>$wgWatchlistExpiry</code>}} is
<code>true</code>).

=== Nuevas extensiones incluidas ===

MediaWiki 1.35 incorpora la extensión {{ll|Extensión:VisualEditor|nsp=0}}, que proporciona una experiencia de edición visual como una alternativa al editor tradicional. No será necesario configurar una instancia separada de [[Parsoid]], ya que está integrada en el núcleo de MediaWiki.

Además están incluidas las extensiones {{ll|Extensión:SecureLinkFixer|nsp=0}} y {{ll|Extensión:TemplateData|nsp=0}}. Que fuerzan a que los enlaces de la wiki sean https y añaden una etiqueta y un api para permitir a los editores especificar cómo deben ser invocadas las plantillas.

=== Acción API cambios ===
* The 'suggest' parameter of action=opensearch has been deprecated. The API behaves the same with and without this parameter. It was previously used by {{ll|Manual:$wgEnableOpenSearchSuggest|$wgEnableOpenSearchSuggest}} to partially disable the API if set to false. Specifically, it would deny internal frontend requests carrying this parameter, whilst accepting other requests.
* Integer-type parameters are now validated for syntax rather than being interpreted in surprising ways. For example, the following will now return a badinteger error:
** "1.9" (formerly interpreted as "1")
** " 1" (formerly interpreted as "1")
** "1e1" (formerly interpreted as "1" or "10", depending on the PHP version)
** "1foobar" (formerly interpreted as "1")
** "foobar" (formerly intepreted as "0") parameters. Ranges should be assumed to be enforced.
* Many user-type parameters now accept a user ID, formatted like "#12345".
* The 'assert' parameter used by all API modules now supports the value 'anon'. When specified, the API will return the 'assertanonfailed' error if the user is logged in.
* action=edit now supports the 'baserevid' parameter for edit conflict detection, as an alternative to 'basetimestamp'. Note that self-conflicts will continue to be ignored if 'basetimestamp' is set, but not if only 'baserevid' is set.
* A new module was added to change the content model of existing pages. Use action=changecontentmodel. Unlike Special:ChangeContentModel, the api module does not work for pages that do not already exist.
* If {{ll|Manual:$wgWatchlistExpiry|$wgWatchlistExpiry}} is true, the following API changes are made:
** action=watch accepts a new 'expiry' parameter analagous to the expiry accepted by action=userrights, action=block, etc., except it must be no greater than {{ll|Manual:$wgWatchlistExpiryMaxDuration|$wgWatchlistExpiryMaxDuration}}, or an infinity value.
** action=query&list=watchlistraw returns pages' watchlist expiry dates.
* ({{PhabT|249526}}) action=login will now return Failed rather than NeedToken on session loss.

=== Acción API cambios internos ===
* The Action API now uses the Wikimedia\ParamValidator library for parameter validation, which brings some new features and changes. For the most part existing module code should work as it did before, but see subsequent notes for changes.
** The values for all ApiBase PARAM_* constants have changed. Code should have been using the constants rather than hard-coding the values.
** Several ApiBase PARAM_* constants have been deprecated, see the in-class documentation for details. Use the equivalent ParamValidator constants instead.
** The value returned for 'upload'-type parameters has changed from WebRequestUpload to Psr\Http\Message\UploadedFileInterface.
* Validation of 'user'-type parameters is more flexible. PARAM constants exist to specify the type of "user" allowed and to request UserIdentity objects rather than name strings. The default is to accept all types (name, IP, range, and interwiki) that were formerly accepted.
* Maximum limits are no longer ignored in "internal mode".
* The $paramName to ApiBase::handleParamNormalization() should now include the prefix.
* ({{PhabT|245931}}) meta=siteinfo&siprop=interwikimap no longer reports language or extralanglink when {{ll|Manual:$wgInterwikiMagic|$wgInterwikiMagic}} is false.

{{note|1=Red Hat 8 y CentOS 7 proporcionan PHP 7.2 por defecto. <span lang="en" dir="ltr" class="mw-content-ltr">You will need to install updated versions from {{ll|Manual:Running MediaWiki on Red Hat Linux#Install operating system packages|Software Collections (SCL) or AppStreams}}.</span>}}

== Subpáginas ==
{{engine|MediaWiki 1.35|work=MediaWiki 1.35}}
{{subpages}}
[[Category:MediaWiki Releases{{#translation:}}]]

Translations:MediaWiki 1.35/19/es

2021-09-08T11:40:59Z

IShareFreedom:

Red Hat 8 y CentOS 7 proporcionan PHP 7.2 por defecto.