Migrar un foro del plugin bbPress de WordPress a Discourse

Discourse · 19 Agosto, 2016 14:24

Recientemente realicé con éxito una migración de base de datos de bbPress utilizando el script de migración integrado de Discourse. Ahora lo compartiré como un tutorial paso a paso.

Nota: Este tutorial es para el plugin bbPress, no para la versión independiente heredada de bbPress.

¿Qué datos se pueden importar?

Usuarios (incluidos los usuarios anónimos)
Categorías
Temas
Publicaciones
Mensajes privados (a través de BuddyPress)
Archivos adjuntos
Enlaces permanentes (Permalinks)

Antes de iniciar la migración, configure un entorno de desarrollo en su máquina (o dentro de una máquina virtual) y ejecute la importación allí en lugar de dentro del contenedor Docker. Cuando lo intenté dentro del contenedor Docker, obtuve el problema peer authentication failed. Por lo tanto, le recomiendo encarecidamente que utilice una máquina de desarrollo. Consulte la guía de instalación para desarrollo en macOS o Ubuntu / Debian.

Discourse requiere Ruby 3.4 o superior. Puede verificar su versión de Ruby con:

ruby -v

Ahora necesitamos instalar la dependencia libmysqlclient-dev para poder usar el gem mysql2.

sudo apt-get install libmysqlclient-dev

Después de la instalación exitosa, vaya a la ruta de su instalación de desarrollo de Discourse (típicamente ~/discourse).

cd ~/discourse

Configurando la conexión a la base de datos

El script de importación de bbPress lee toda la configuración de conexión a la base de datos desde variables de entorno. No es necesario editar el archivo del script. Se admiten las siguientes variables de entorno:

Variable	Valor predeterminado	Descripción
`BBPRESS_HOST`	`localhost`	Host de la base de datos MySQL
`BBPRESS_USER`	`root`	Nombre de usuario de MySQL
`BBPRESS_PW`	(vacío)	Contraseña de MySQL
`BBPRESS_DB`	`bbpress`	Nombre de la base de datos MySQL
`BBPRESS_PREFIX`	`wp_`	Prefijo de tabla de WordPress
`BBPRESS_ATTACHMENTS_DIR`	`/ruta/a/adjuntos`	Ruta al directorio de archivos adjuntos de bbPress

Si está migrando su base de datos desde localhost, generalmente solo necesita establecer el nombre de la base de datos:

IMPORT=1 bundle \u0026\u0026 IMPORT=1 BBPRESS_DB="mi_bbpress" bundle exec ruby script/import_scripts/bbpress.rb

Si está migrando su base de datos desde un servidor externo, también necesitará establecer el host, el nombre de usuario y la contraseña:

IMPORT=1 bundle \u0026\u0026 IMPORT=1 BBPRESS_HOST="NOMBRE_HOST_REMOTO" BBPRESS_USER="NOMBRE_USUARIO_DB" BBPRESS_PW="MI_CONTRASENA_SEGURA" BBPRESS_DB="NOMBRE_DB" bundle exec ruby script/import_scripts/bbpress.rb

¡Felicitaciones! Su base de datos se migró con éxito de bbPress a Discourse

Ahora tome una copia de seguridad desde la página de administración /admin/backups e impórtela en su sitio web de Discourse en vivo.

Después de mover su foro de bbPress a Discourse, si aún va a usar su sitio web de WordPress como sitio principal y desea conectarlo con Discourse, instale el plugin oficial de WordPress de Discourse.

kellbot · 14 Febrero, 2017 14:16

Just wanted to thank you for providing this step-by-step guide. We migrated our site from bbpress to Discourse with minimal headache thanks to you. Since we’re running multisite wordpress there were a few tweaks to make to the importer, but other than that it went very smoothly. Thanks!

vinothkannans · 14 Febrero, 2017 15:43

If you can share your tweaks then it will be helpful to other multisite owners.

kellbot · 14 Febrero, 2017 15:57

Admittedly I didn’t take very good notes, and have since killed the VM it
was on (sorry!) but the basic gist is that if your bbpress install is not
on the primary site of the Multisite setup you’ll need to a) set the
environmental variable for BBPRESS_PREFIX to include your site’s ID number
(e.g. wp_6_ ) and then edit the migration script to use wp_users rather
than #{BBPRESS_PREFIX} for the Users sql. This is because on Multisite
installations the wp_users table is shared across sites and then each site
has its own tables for posts, postmeta, etc.

vinothkannans · 14 Febrero, 2017 18:27

thanks for the details

lead4good · 25 Mayo, 2017 11:26

I recently posted on how to import bbpress into discourse

erlend_sh · 5 Junio, 2017 15:21

Great job on the tutorial! But it’s confusing to have two different guides on this. Do they serve different purposes? Otherwise we should figure out how to merge them.

lead4good · 12 Junio, 2017 14:57

That guide is about how to import bbpress inside of a development environment, mine is how to import bbpress using the docker container. It’s just 2 different ways to go. I’d recommend importing via docker container since it doesn’t ask for the additional step of setting up a development environment, which can be cumbersome.

lcestou · 4 Junio, 2019 16:46

Hello I am stuck trying to import successfully after all users are done importing.

As soon it begins to import anonymous users it cancels with an error of “Invalid Email… and Validation failed: Username can’t be blank (ActiveRecord::RecordInvalid)”.

I added the error below, does anyone encountered this before or have any ideas on what I should do?

Thanks,

importing anonymous users...
Invalid email '' for ''. Using '6be92499a6f885cb271d94bffd5e667b@email.invalid'
Error on record: {:id=>"", :email=>"", :name=>"", :website=>nil}
Traceback (most recent call last):
	23: from script/import_scripts/bbpress.rb:512:in `<main>'
	22: from /home/lutechi/discourse/script/import_scripts/base.rb:49:in `perform'
	21: from script/import_scripts/bbpress.rb:31:in `execute'
	20: from script/import_scripts/bbpress.rb:153:in `import_anonymous_users'
	19: from /home/lutechi/discourse/script/import_scripts/base.rb:249:in `create_users'
	18: from /home/lutechi/discourse/script/import_scripts/base.rb:249:in `each'
	17: from /home/lutechi/discourse/script/import_scripts/base.rb:261:in `block in create_users'
	16: from /home/lutechi/discourse/script/import_scripts/base.rb:337:in `create_user'
	15: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/transactions.rb:212:in `transaction'
	14: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/database_statements.rb:267:in `transaction'
	13: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/transaction.rb:236:in `within_new_transaction'
	12: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/2.6.0/monitor.rb:230:in `mon_synchronize'
	11: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/transaction.rb:239:in `block in within_new_transaction'
	10: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/database_statements.rb:267:in `block in transaction'
	 9: from /home/lutechi/discourse/script/import_scripts/base.rb:338:in `block in create_user'
	 8: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/suppressor.rb:48:in `save!'
	 7: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/transactions.rb:315:in `save!'
	 6: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/transactions.rb:385:in `with_transaction_returning_status'
	 5: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/transactions.rb:212:in `transaction'
	 4: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/database_statements.rb:265:in `transaction'
	 3: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/transactions.rb:387:in `block in with_transaction_returning_status'
	 2: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/transactions.rb:315:in `block in save!'
	 1: from /home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/validations.rb:52:in `save!'
/home/lutechi/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activerecord-5.2.3/lib/active_record/validations.rb:80:in `raise_validation_error': Validation failed: Username can't be blank (ActiveRecord::RecordInvalid)

RCheesley · 13 Agosto, 2019 17:09

Thanks for this useful tutorial - worked for me although I have a couple of small issues:

The install process seemed to install postgres 11 and Discourse hosted version support postgres 10, so that’s giving them a bit of a headache!
My imported users don’t seem to be able to log into Discourse with their WordPress credentials - I tried it with my own user account, both with the username and the email address, but neither work. I can log into WordPress fine and the user account is present in Discourse, with the associated forum threads. Something changed with passwords/auth maybe?

Stephen · 13 Agosto, 2019 17:46

Are you using SSO from WordPress?

michaeld · 13 Agosto, 2019 20:42

This requires the migrate password plugin. Did you install that?

RCheesley · 13 Agosto, 2019 21:19

Hi Michael,

No, that is the first reference I’ve found to the plugin, so thank you for highlighting it - maybe I missed a step somewhere! Thanks for sharing I will take a closer look tomorrow when my eyes aren’t quite so tired!

Ruth

p0fi · 23 Septiembre, 2019 14:45

Hi

Can user uploaded pictures also be migrated?
The plugin for the user uploads was GD bbPress Attachments

Cheers

pfaffman · 23 Septiembre, 2019 16:46

The script appears to import attachments.

github.com/discourse/discourse

script/import_scripts/bbpress.rb

main


      
           FROM #{BB_PRESS_PREFIX}postmeta pm
           JOIN #{BB_PRESS_PREFIX}posts p ON p.id = pm.post_id
          WHERE pm.meta_key = '_wp_attached_file'
            AND p.post_parent > 0

You need to set a BB_PRESS_ATTACHMENTS_DIR ENV variable with the path to the attachments.

p0fi · 29 Septiembre, 2019 12:11

The uploads of the bbPress plugin appear to be stored in the /uploads folder of the WordPress installation. The GD bbPress Attachments was used for this. Im not sure which kind of path I should put in the BB_PRESS_ATTACHMENTS_DIR variable. Could you help me here a bit? Should I put the full URL path to the uploads e.g. http://www.example.com/httpdocs/wp-content/uploads/2018/02/picture.png or what else?

I saw that the import script didn’t finish successfully since the import_private_messages step failed. Private messages were not activated in the forum. I removed that step form the script and it fails with the message: table wp_bb_attachments doesn't exist which is true. I can’t find any table for attachments in the database tho. How could that attachments have worked in the first place?

pfaffman · 29 Septiembre, 2019 14:07

The attachments need to be in a directory on the server where you run the import.

If you don’t see the attachment table that the script is looking for It may be that you have used some different means of handling attachments than the script expects. My guess is that they are either in a different table that you haven’t found or that the relative filename is in the posts themselves.

It sounds like you need to another function to import them. If you have a budget I can help. Discourse Migration — Literate Computing, LLC has information about imports. You don’t need full service, it seems, so your cost would be less than suggested there.

p0fi · 30 Septiembre, 2019 16:03

Since Discourse always runs in a docker container should this directory be linked into the import container?

pfaffman · 30 Septiembre, 2019 16:05

Correct. If you’re running the import from a container then you need to put those images somewhere that the can be seen from the container and use that path.

p0fi · 30 Septiembre, 2019 16:12

One last question. Since you mentioned your import service I checked the site and did some more digging into my database and found where the attachments are stored. One sentence on your page made me worry a bit:

For example, some forums can attach files to a post without mentioning them in the body of the message, the import script identifies attachments by replacing references to them in the message body; when this happens, those un-linked attachments are omitted.

I found that my attachments where stored in the wp_postsmeta table as _wp_attached_file. The post itself which had this attachment linked however does not have a mention of this in the post body. It seems the only link here is the post_id and its meta_id. Does this mean that this is an “un-linked attachment” and will be omitted?

Tema		Respuestas	Vistas
Use an import script that requires MySQL Sysadmins how-to	51	13055	12 Diciembre 2023
Migrate a phpBB3 forum to Discourse Migrating to Discourse how-to	467	98877	4 Septiembre 2025
Migrate a MyBB forum to Discourse Sysadmins how-to	22	8450	24 Mayo 2023
Migrate a vBulletin 4 forum to Discourse Sysadmins how-to	183	30636	9 Noviembre 2025
My phpBB Migration Journey (postgresql) Migration phpbb	23	1868	30 Marzo 2023

Migrar un foro del plugin bbPress de WordPress a Discourse

¿Qué datos se pueden importar?

Configurando la conexión a la base de datos

Temas relacionados