Do not hack MediaWiki core/es

Mientras que "piratería MediaWiki core" es a menudo una solución propuesta en otros foros de soporte de MediaWiki, que es "no" una solución ideal. En general, causará más problemas de los que resuelve y sólo hará que las futuras actualizaciones más difíciles de instalar.

For the purposes of this essay, "core" is meant to include all files that belong to the original MediaWiki installation. That is to say all files except LocalSettings.php, the ones in your "extensions" folder, or other folders which you have added since your installation.

Por qué usted no debe modificar los archivos centrales
No importa lo fácil que es modificar los archivos principales para hacer MediaWiki haga lo que usted quiere que haga,  'resistir la tentación' .


 * Doing so will make it complicated, difficult or near impossible to apply site updates such as security and bug fixes.
 * Va a hacer que sea difícil para los que vengan después de mantener el sitio.
 * Usted podría dejar su sitio vulnerable a exploits.
 * Other developers are less inclined to help you if you have hacked your core - if for no other reason than it is difficult for them to know what has been done.

The MediaWiki core has been designed to be modular, so there should be no reason to hack it. If there is a feature you want and it cannot be accomplished outside of modifying core, consider developing an extension or submitting your hack as a patch. Submit a bug report and tell the community the feature you want to accomplish. It will then be tested and your feature may become a part of the MediaWiki core.

Problems faced by wikis which hack their core

 * MediaWiki upgrade times go from 30 minutes to 6 hours or even 6 weeks if your diff shows 13650 lines have been changed.
 * Increase in spam and other unwanted attacks due to security holes
 * Missing out on new features due to conflicting hacks to core files
 * Inability to use MediaWiki.org documentation - all of which has been written under the assumption that you have not hacked your core files (unless of course you write documentation specifically for how to operate MediaWiki when that particular hack is being used)
 * La repetición del problema original - como un informe de error es una de manera más fiable para resolver un problema de un hack núcleo - si no por otra razón que un grupo de desarrolladores se estudia el problema y puede descubrir código necesario cambia te perdiste
 * Quejarse a los desarrolladores acerca de su núcleo archivos no funciona - y no encontrar mucha simpatía - si hackear archivos principales - un apoyo técnico eficaz es casi imposible

Excepciones
¿Hay excepciones a esta regla?

No.

Okay, very very rarely. But this is generally for specific wikis or implementations by people who are extremely familiar with the MediaWiki code base, development practices and security model. Those who properly document their changes and practice proper revision control with their code. If you have to ask, chances are you shouldn't.

Extensiones
Note that most of this page also applies to important extensions. It's a bad idea to directly start hacking the Semantic MediaWiki extensions, or any of the extensions used on Wikipedia and other Wikimedia sites.

An exception could be if an extension is mainly installed by copying its code from this wiki (instead of getting it from a software repository). It means it's not very seriously maintained.

Qué hacer en su lugar
En lugar de la piratería núcleo MediaWiki, hay varias soluciones alternativas a considerar, más o menos en este orden:


 * 1) MediaWiki is a powerful beast out of the box, you can do a lot with MediaWiki's interface messages such as MediaWiki:Sidebar and many many others, see also other pages on this wiki for e.g. JavaScript and CSS additions and changes.
 * 2) Develop an extension to accomplish what your hack was intended to do
 * 3) Reporta un fallo
 * 4) Contribute your improvement to core to the code repository so others can benefit from your fix