WP Multi Network

Descripción

Convierte tu instalación WordPress multisitio en muchas redes multisitio, alrededor de un conjunto global de usuarios.

  • Reveals hidden WordPress Multisite functionality.
  • Includes a «Networks» top-level Network-Admin menu.
  • Includes a List Table for viewing available networks.
  • Allows moving subsites between networks.
  • Permite a los administradores globales crear nuevas redes con sus propios sitios y distribución de dominios.
  • Group sites into logical networks using nearly any combination of domain (example.org) and path (/site/).

Capturas

Instalación

  • Descárgalo e instálalo usando el instalador integrado de plugins de WordPress.
  • Actívalo en el menú «Plugins» del escritorio de red usando el enlace «Activar para la red».
  • Comenta la línea DOMAIN_CURRENT_SITE en tu archivo wp-config.php. Si no tienes esta línea, probablemente necesites activar el modo multisitio.
  • Comienza a planificar y crear tus redes.

Preguntas frecuentes

¿Cada red puede tener un dominio diferente?

Sí, puedes. ¡Esto es lo mejor que hace este plugin!

Piensa en cómo funciona WordPress.org:

  • wordpress.org
  • make.wordpress.org/core
  • buddypress.org
  • codex.buddypress.org
  • bbpress.org
  • codex.bbpress.org
  • wordcamp.org
  • us.wordcamp.org/2021

Users are global, and they can login to any of those domains with the same login and password. Each of those domains has their own subdomains and subdirectories, many of which are sites or (networks of them).

¿Esto funcionará en una instalación estándar de WordPress?

Puedes activarlo, pero no hará nada. Antes, debes tener la funcionalidad multisitio activada y funcionando.

¿Dónde puedo conseguir soporte?

Create a GitHub issue: https://github.com/stuttter/wp-multi-network/issues/new

¿Qué pasa con las constantes multisitio?

Para una máxima flexibilidad, usa algo como…

// Multisite
define( 'MULTISITE',           true                  );
define( 'SUBDOMAIN_INSTALL',   false                 );
define( 'PATH_CURRENT_SITE',   '/'                   );
define( 'DOMAIN_CURRENT_SITE', $_SERVER['HTTP_HOST'] );

// Likely not needed anymore (your config may vary)
//define( 'SITE_ID_CURRENT_SITE', 1 );
//define( 'BLOG_ID_CURRENT_SITE', 1 );

// Un-comment and change to a URL to funnel no-site-found requests to
//define( 'NOBLOGREDIRECT', '/404/' );

/**
 * These are purposely set for maximum compatibility with multisite and
 * multi-network. Your config may vary.
 */
define( 'WP_HOME',    'https://' . $_SERVER['HTTP_HOST'] );
define( 'WP_SITEURL', 'https://' . $_SERVER['HTTP_HOST'] );

¿Qué pasa con las cookies?

Usa algo como esto para permitir que las cookies funcionen en las redes…

// Cookies
define( 'COOKIEHASH',         md5( 'yourrootdomain.com' ) );
define( 'COOKIE_DOMAIN',      'yourrootdomain.com'        );
define( 'ADMIN_COOKIE_PATH',  '/' );
define( 'COOKIEPATH',         '/' );
define( 'SITECOOKIEPATH',     '/' );
define( 'TEST_COOKIE',        'thing_test_cookie' );
define( 'AUTH_COOKIE',        'thing_'          . COOKIEHASH );
define( 'USER_COOKIE',        'thing_user_'     . COOKIEHASH );
define( 'PASS_COOKIE',        'thing_pass_'     . COOKIEHASH );
define( 'SECURE_AUTH_COOKIE', 'thing_sec_'      . COOKIEHASH );
define( 'LOGGED_IN_COOKIE',   'thing_logged_in' . COOKIEHASH );

¿Y las subidas?

As of version 3.5, new WordPress multisite installs use a more efficient way to serve uploaded files.
Unfortunately, this doesn’t play well with multiple networks (yet). Installs that upgraded from 3.4 or below are not affected.

WP Multi-Network needs to be running to help set the upload path for new sites, so all networks created with this plugin will have it network activated.
If you disable it on one of your networks, any new site you create on that network will store its uploaded files under that network’s main site’s uploads folder. It’s not pretty.

Simplemente deja este plugin activado en todas la red (o en «mu-plugins») y se encargará de todo.

Can I achieve a multi-level URL path structure (domain/network/site) with a subfolder network?

To achieve nested folder paths in this fashion network1/site1, network1/site2 etc,
please follow the steps in https://paulund.co.uk/wordpress-multisite-nested-paths to construct a custom sunrise.php (Thanks to https://paulund.co.uk for providing these steps).

¿Dónde puedo encontrar documentación?

No hay mucho de qué hablar realmente. ¡Consulta el código para obtener más detalles!

Reseñas

24 de septiembre de 2021
I had a problem creating a network on one site when it didn't create a user but on a different multisite - I set all wp-config in advance, deactivated almost all plugins and it created a new network appropriately.
19 de marzo de 2018
Less is More. The plugin is an easy learning, no-brainer (for the Super Admins), it just does what it says: adds a simple and beautifull UI to manage Multi Networks.
12 de diciembre de 2017
This has enabled me to use two separate domains in a multi-site for testing before roll-out to production.
Leer todas las 22 reseñas

Colaboradores y desarrolladores

«WP Multi Network» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«WP Multi Network» ha sido traducido a 11 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «WP Multi Network» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

2.5.0

  • Fix new networks sometimes not being created.
  • Fix moving sites sometimes not working.
  • Fix network name always being «New Network».
  • Fix several debug notices related to filter_input().
  • Fix several redirection & admin-notice issues.
  • Allow networks to be created with empty network name & site name.
  • Update author link & plugin meta data.

2.4.2

  • Update code for WordPress coding standards.
  • Other small bug fixes.

2.4.1

  • Update required PHP / wordpress versions.

2.4.0

  • Add networks REST API endpoint.

2.3.0

  • Add network capability mapping.
  • Add WP CLI command.
  • Other improvements.

2.2.1

  • Fix upload paths still using blogs.dir.

2.2.0

  • WordPress 4.9 minimum version bump.
  • Fix bug preventing sites from being moved.
  • Tweak some styling.
  • Use more WordPress core functions for sites & networks.

2.1.0

  • Add nonce checks to forms.
  • Add validation & output sanitization to form fields.

2.0.0

  • WordPress 4.6 minimum version bump.
  • Caching improvements for WordPress 4.6.
  • Reprogramación de la lista de tablas y del código del método de administración.

1.8.1

  • Fix site reassignment metabox from moving sites incorrectly.

1.8.0

  • Support for core compat functions.
  • Fix bug causing site moves to break.
  • Fix bug allowing duplicate site URLs.
  • Remove _network_option() functions.
  • Remove network.zero placeholder.
  • WordPress 4.5 & 4.6 compatibility updates.

1.7.0

  • WordPress 4.4 compatibility updates.
  • Metabox overhaul.
  • network.zero improvements.
  • Fix site assignments.
  • Various UI improvements.
  • Global, class, function, and method cleanup.

1.6.1

  • WordPress 4.3 UI compatibility updates.
  • Remove site «Actions» column integration.

1.6.0

  • Move inclusion to muplugins_loaded.
  • Introduce network switching API.
  • Introduce network options API.
  • Update action links to better match sites list.
  • Better support for domain mapping.
  • Refactor file names & locations.
  • Deprecate wpmn_fix_subsite_upload_path().
  • Include basic WPCLI support.
  • Escaped gettext output.
  • Fix bulk network deletion.
  • Scrutinized code formatting.

1.5.1

  • Fix debug notices when creating networks.
  • Fix incorrect variable usage causing weird output.
  • Adds default path when creating new networks.

1.5

  • Support for WordPress 3.8.
  • Finally, a menu icon!
  • Improved output sanitization.

1.4.1

  • Fix issue when changing network domain or path – contributed by mgburns.
  • Improve support for native uploaded file handling.

1.4

  • Fix admin pages (let us know if you find something broken).
  • Add support for WP 3.5+ upload handling – thanks, RavanH (see notes: «What’s up with uploads?»).

1.3.1

  • Fix prepare() usages.
  • Fix some debug notices.

1.3

  • Refactor into smaller pieces.
  • Add PHP docs.
  • Deprecate functions for friendlier core-style functions.
  • Code clean-up.
  • Remove inline JavaScript.

1.2

  • Implemented 3.1 Network Admin Menu, backwards compatibility maintained.
  • Fix multiple minor issues.
  • Add Site Admin and Network Admin to Network lists.
  • Add various security and bullet proofing.

1.1

  • Mejor compatibilidad con WordPress 3.0.

1.0

Primeros pasos.