Actualizar Elgg

Actualice un sitio existente a una nueva versión de Elgg.

Si ha escrito complementos personalizados, debería leer también las guías para desarrolladores para así obtener información sobre cómo actualizar el código de esos complementos </guides/upgrading> para adaptarlo a la última versión de Elgg.


  • Back up your database and code
  • Mind any version-specific comments below
  • Upgrade only one minor version at a time (1.6 => 1.7, then 1.7 => 1.8)
  • Pruebe la nueva versión en un sitio de prueba antes de realizar la actualización.
  • Report any problems in plugins to the plugin authors
  • If you are a plugin author you can report any backwards-compatibility issues to GitHub

Basic instructions

  1. Log in as an admin to your site
  2. Disable caching in Advanced Settings
  3. Back up your database, data directory, and code
  4. Download the new version of Elgg from
  5. Update the files
    • If doing a patch upgrade (1.9.x), overwrite your existing files with the new version of Elgg
    • If doing a minor upgrade (1.x), replace the existing core files completely
  6. Merge any new changes to the rewrite rules
    • For Apache from install/config/htaccess.dist into .htaccess
    • For Nginx from install/config/nginx.dist into your server configuration (usually inside /etc/nginx/sites-enabled)
  7. Merge any new changes from settings.example.php into settings.php
  8. Visit


Cualquier modificación de Elgg debería estar hecha mediante complementos, de forma que no se pierda nada al substituir la instalación de Elgg actual por una nueva. Si no es este el caso, preocúpese de mantener sus propias modificaciones.

From 2.2 to 2.3

PHP Version

PHP 5.5 has reached end of life in July 2016. To ensure that Elgg sites are secure, we now require PHP 5.6 for new installations.

Existing installations can continue using PHP 5.5 until Elgg 3.0.

In order to upgrade Elgg to 2.3 using composer while using PHP 5.5, you may need to use --ignore-platform-reqs flag.


  • PHPUnit bootstrap is deprecated by composer autoloader: Tests should no longer bootstrap themselves using /engine/tests/phpunit/bootstrap.php. Instead, tests should extend \Elgg\TestCase.
  • Some core files now sniff if PHPUNIT_ELGG_TESTING_APPLICATION constant is set to determine whether Elgg is being bootstrapped for PHPUnit tests. phpunit.xml configuration needs to updated to include this constant definition.
  • PHPUnit bootstrap no longer sets global $CONFIG. Tests should use _elgg_services()->config instead.
  • Core and tests no longer use private global values in $_ELGG->view_path and $_ELGG->allowed_ajax_views


  • The database GUID columns need to be aligned. In the admin section an upgrade is available to handle this. Please make sure you have a backup available

From 1.x to 2.0

Removed plugins

The following plugins are no longer bundled with Elgg core:

IE-specific workarounds have been dropped

Several views (css/ie, css/ie7, css/ie8, etc.) as well as conditional comments have been discarded now that IE10+ browsers are more standards-compliant. If you need browser support farther back than that, you will need to find or build a plugin that introduces its own compatibility layer or polyfills.

Update your webserver config

URL paths like cache/* and rewrite.php now use the main front controller script. You must remove these rewrite rules from your webserver config (e.g. .htaccess).

Also remove the rules for paths like export/*; these endpoints have been removed.

Settings location

After upgrading, move your settings.php file from engine/ to elgg-config/.

From 1.10 to 1.11

Breaking changes

In versions 1.9 and 1.10, names and values for metadata and annotations were not correctly trimmed for whitespace. Elgg 1.11 correctly trims these strings and updates the database to correct existing strings. If your plugin uses metadata or annotations with leading or trailing whitespace, you will need to update the plugin to trim the names and values. This is especially important if you are using custom SQL clauses or have hard-coded metastring IDs, since the update might change metastring IDs.

De la versión 1.8 a la 1.9

Elgg 1.9 is a much lighter upgrade than 1.8 was.

Breaking changes

Plugins and themes written for 1.8 are expected to be compatible with 1.9 except as it pertains to comments, discussion replies, and notifications. Please report any backwards compatibility issues besides those just listed.

Upgrade steps

There are several data migrations involved, so it is especially important that you back up your database and data directory before performing the upgrade.

Download the new version and copy these files from the existing 1.8 site:

  • .htaccess
  • engine/settings.php
  • any 3rd-party plugin folders in the mod directory

Then replace the old installation directory with the new one. This way you are guaranteed to get rid of obsolete files which might cause problems if left behind.

Follow the basic instructions listed above.

After you’ve visited upgrade.php, go to the admin area of your site. You should see a notification that you have pending upgrades. Click the link in the notification bar to view and run the upgrades.

The new notifications system delivers messages via a minutely cron handler. If you haven’t done so yet, you will need to install and configure crontab on your server. If cron jobs are already configured, note that the scope of available cron periods may have changed and you may need to update your current crontab to reflect these changes.

Time commitment

Running all of the listed upgrades took about 1 hour and 15 minutes on the Elgg community site which at the time had to migrate:

  • ~75,000 discussion replies
  • ~75,000 data directories

You should take this only as a ballpark estimate for your own upgrade. How long it takes will depend on how large your site is and how powerful your servers are.

De la versión 1.7 a la 1.8

La versión 1.8 ha sido el mayor salto en el desarrollo de Elgg desde la versión 1.0. Es por ello que para actualizar el núcleo de Elgg y sus complementos hace falta más trabajo que en anteriores actualizaciones.

Actualizar el núcleo

Elimine las siguientes carpetas (se encuentran en el mismo nivel que «_graphics» o «engine»):

  • _css
  • account
  • admin
  • dashboard
  • entities
  • friends
  • search
  • settings
  • simplecache
  • views


Tendrá problemas si no elimina estas carpetas antes de actualizar.