Migrare un forum vBulletin 4 a Discourse

Questa guida illustra come migrare un forum vBulletin 4 a Discourse utilizzando lo script di importazione in script/import_scripts/vbulletin.rb.

:warning: Aspettati di dover apportare modifiche allo script. Ogni installazione di vBulletin ha i suoi plugin, campi personalizzati e peculiarità BBCode. La maggior parte delle importazioni reali richiede piccole modifiche allo script. Esegui un’importazione di prova completa su una macchina di sviluppo prima di toccare la produzione.

Quale importer dovrei usare?

Forum Script
vBulletin 4 script/import_scripts/vbulletin.rb (questa guida)
vBulletin 3 script/import_scripts/vbulletin3.rb (stessi passaggi, nome dello script diverso)
vBulletin 5 script/import_scripts/vbulletin5.rb
Forum molto grandi (milioni di post) script/bulk_import/vbulletin.rb (molto più veloce, ma con meno funzionalità e più difficile da personalizzare)

Cosa viene importato

  • Gruppi
  • Utenti (gli utenti bannati diventano utenti sospesi)
  • Forum: ogni forum genitore e figlio diventa una categoria e una sottocategoria
  • Argomenti
  • Thread fissato → argomento fissato (pinned)
  • Thread chiuso → argomento chiuso
  • Thread eliminato in modo morbido o moderato → argomento non elencato (unlisted)
  • Post
  • Messaggi privati
  • Allegati
  • Avatar (solo se sono archiviati nel database, vedi sotto)
  • Permalink per gli argomenti

Avvertenze

  • Puoi riprendere un’importazione interrotta e rieseguirla su uno snapshot più recente del database per recuperare nuovi contenuti. I contenuti già importati non verranno aggiornati con modifiche successive.

  • Discourse supporta due livelli di categorie. I forum annidati più profondamente vengono appiattiti.

  • Le liste BBCode ([ul], [ol], [li]) non vengono convertite completamente e potrebbero richiedere una pulizia manuale.

Prima dell’esportazione

Se vBulletin archivia gli avatar nel file system, l’importer non li troverà. Visita /admincp/avatar.php?do=storage sul tuo sito vBulletin e sposta gli avatar nel database prima di esportarlo.

Quindi esporta il database sul server vBulletin:

mysqldump -u USERNAME -p DATABASE_NAME | gzip > vb4_dump.sql.gz

Copia il dump e la cartella degli allegati sulla macchina su cui eseguirai l’importazione (ad esempio, con scp o rsync). Le impostazioni di amministratore di vBulletin indicano dove sono archiviati gli allegati.

Opzione A: Importazione su una macchina di sviluppo (consigliata)

Importare localmente consente di iterare rapidamente e di scartare i tentativi falliti. Quando il risultato sembra corretto, effettua un backup del sito e ripristinalo in produzione.

  1. Configura un ambiente di sviluppo Discourse seguendo la guida per Ubuntu/Debian o macOS.

  2. Installa MariaDB. È un sostituto diretto di MySQL, e i pacchetti di MySQL 5.7 non sono più disponibili nelle distribuzioni attuali.

    # Ubuntu/Debian
    sudo apt-get update
    sudo apt-get install mariadb-server libmariadb-dev
    sudo service mariadb start
    
     # macOS
     brew install mariadb
     brew services start mariadb
    
  3. Installa i gem dell’importer. mysql2 è incluso quando IMPORT=1 è impostato. php-serialize deve essere aggiunto:

    cd ~/discourse
    echo "gem 'php-serialize', require: false" >> Gemfile
    IMPORT=1 bundle install
    
  4. Carica il database di vBulletin:

    sudo mysql -e "CREATE DATABASE vb4"
    gunzip < vb4_dump.sql.gz | sudo mysql vb4
    
  5. Inizia con un database Discourse vuoto:

    bin/rails db:drop db:create db:migrate
    
  6. Esegui l’importer. Puoi fermarlo e riavviarlo in qualsiasi momento, poiché salta i contenuti già importati.

    export DB_HOST="localhost"  
    export DB_NAME="vb4"
    export DB_USER="root"
    export DB_PW=""                                # Password root di MariaDB, se ne hai impostata una
    export TABLE_PREFIX="vb_"                      # Il prefisso delle tue tabelle, o "" se non ce n'è uno
    export ATTACHMENT_DIR="/path/to/attachments"   # La cartella degli allegati che hai copiato
    export TIMEZONE="America/Los_Angeles"          # Il fuso orario usato da vBulletin
    
    IMPORT=1 bundle exec ruby script/import_scripts/vbulletin.rb
    
  7. Avvia Discourse e lascia finire i job in background. Esegui bin/dev e in un secondo terminale esegui bundle exec sidekiq. La rielaborazione dei post (post rebaking) e l’elaborazione delle immagini possono richiedere molto tempo su un forum grande. Puoi monitorare i progressi su http://localhost:4200/sidekiq.

  8. Passa alla produzione. Effettua un backup e ripristinalo sul tuo sito di produzione seguendo Spostare un sito Discourse su un altro VPS.

Opzione B: Importazione direttamente nel container di produzione

  1. Installa Discourse con la guida di installazione standard.

  2. Regola le impostazioni del sito (vedi Impostazioni del sito consigliate sotto).

  3. Copia il dump e gli allegati in /var/discourse/shared/standalone/ sull’host. All’interno del container appaiono sotto /shared/, e i file lì presenti sopravvivono a una ricostruzione del container.

  4. Entra nel container e installa MariaDB:

    cd /var/discourse
    ./launcher enter app
    apt-get update
    apt-get install -y mariadb-server libmariadb-dev
    service mariadb start
    
  5. Installa i gem dell’importer:

    cd /var/www/discourse
    echo "gem 'php-serialize', require: false" >> Gemfile
    su discourse -c 'bundle config set --local deployment false && bundle config set --local frozen false'
    su discourse -c 'IMPORT=1 bundle install'
    
  6. Carica il database di vBulletin:

    mysql -e "CREATE DATABASE vb4"
    gunzip < /shared/vb4_dump.sql.gz | mysql vb4
    
  7. Esegui l’importer. Eseguilo dentro tmux o screen così una disconnessione SSH non lo interromperà.

    cd /var/www/discourse
    su discourse -c 'DB_NAME=vb4 DB_USER=root DB_PW="" TABLE_PREFIX=vb_ \
    ATTACHMENT_DIR=/shared/attachments TIMEZONE=America/Los_Angeles \
    IMPORT=1 bundle exec ruby script/import_scripts/vbulletin.rb'
    
  8. Pulisci. Elimina i file che hai copiato in /shared, poi ricostruisci il container. La ricostruzione rimuove MariaDB e i gem aggiuntivi e ripristina il Gemfile originale.

    exit
    cd /var/discourse
    ./launcher rebuild app
    

Impostazioni del sito consigliate

Imposta queste opzioni prima di importare. Puoi anche impostarle in get_site_settings_for_import in script/import_scripts/base.rb, il che è utile quando si eseguono importazioni di prova ripetutamente.

  • login_required: attiva questa opzione finché l’importazione non è completata e verificata.

  • slug_generation_method: imposta su encoded se il tuo forum non è in inglese, così gli URL degli argomenti manterranno i titoli non ASCII.

  • download_remote_images_to_local: disattiva questa opzione se non vuoi che Discourse scarichi le immagini collegate direttamente nei vecchi post (hotlinked).

  • disable_system_edit_notifications: attiva questa opzione in modo che gli utenti non ricevano notifiche per ogni post modificato dal sistema durante l’elaborazione delle immagini.

Problemi noti

  • Integer values are not supported (ArgumentError) in parse_timestamp. Questo influisce sulle copie più vecchie dello script in esecuzione con versioni più recenti di tzinfo. Aggiorna all’ultima versione di Discourse, oppure cambia `parse_timestamp` in:

    def parse_timestamp(timestamp)
    return nil if timestamp.blank?
       Time.zone.at(@tz.utc_to_local(Time.at(timestamp.to_i)))
    end
    
  • Le citazioni con nomi utente che contengono spazi, o le citazioni nidificate, non vengono convertite. Vedi questa risposta per regex migliorate.

  • Can't connect to local server through socket. MariaDB non è in esecuzione. Avvialo con service mariadb start.

21 Mi Piace

The script will now import avatars, but they must be embedded into the database. To do so, I’m told that you visit /admincp/avatar.php?do=storage and do something there. It seemed to work for the last client I did an import for.

Hey, @erlend_sh, make this a wiki and I’ll add to it in a few days when I submit a PR for this importer.

6 Mi Piace

I was following your guide to import my vBulletin forum to Discourse. I am using a docker container for Discourse. I ran the following command:

I got a long list of errors:

sudo: no tty present and no askpass program specified
sudo: no tty present and no askpass program specified
[...]
sudo: no tty present and no askpass program specified
sudo: no tty present and no askpass program specified

Bundler::SudoNotPermittedError: Bundler requires sudo access to install at the moment. Try installing again, granting Bundler sudo access when
prompted, or installing into a different path.
An error occurred while installing rake (11.2.2), and Bundler cannot continue.
Make sure that `gem install rake -v '11.2.2'` succeeds before bundling.

I am new to ruby on rails and dockers. I do understand the concept of gems and Bundler.
What do these errors mean and how can I resolve them?

1 Mi Piace

Ok so basically I had to install all the necessary gems.
The script worked quite well.

However, I am not able to login with one of the users I created on my vBulletin forum just before importing the database over to discourse.

1 Mi Piace

You’ll need to set passwords. The script doesn’t import them (last I looked).

And even if it did, you’d need to install a plugin to make them work.

1 Mi Piace

I am planning to write a script that will import the passwords for my case.
I know the mysql tables I need to consider for vBulletin. What is the table in PostgreSQL for Discourse that stores passwords and is used during login?

Prakarsh would you be able to share the forum url that you are trying to switch from? The vBulletin one. Will the Discourse one have the same URL?

Yes. Here it is: Brainstorm

Our plan is to keep the URL same for now. I cannot say when it will be live. Probably by end of next week if everything goes right :stuck_out_tongue:

1 Mi Piace

Before you do that, you should read this topic.

You don’t want to directly touch the Discourse tables. You want a script like this. When I last used it and tried to import the passwords, it ran really slowly. I’m not sure why, but after reading this I decided that it’s probably not a bad idea to make people change their passwords.

3 Mi Piace

@pfaffman - You mentioned you used import_pass field in your import script.
Where exactly do you put the import_pass field? And how do you use it?
If you could share it would be great help.

I have tried using this script but it failed 90% into the import of the users:

su discourse -c 'RAILS_ENV=production ruby script/import_scripts/vbulletin.rb'
root:XXXX@localhost wants vb4
loading existing groups...
loading existing users...
loading existing categories...
loading existing posts...
loading existing topics...

importing groups...
        6 / 19 ( 31.6%)  Failed to create group id 7 Moderators: ["Name has already been taken"]
       19 / 19 (100.0%)  
importing users
     2746 / 15319 ( 17.9%)  W, [2017-10-12T10:07:05.104837 #3578]  WARN -- : Bad date/time value "0000:00:00 00:00:00": mon out of range
W, [2017-10-12T10:07:05.106562 #3578]  WARN -- : Bad date/time value "0000:00:00 00:00:00": mon out of range
W, [2017-10-12T10:07:05.107305 #3578]  WARN -- : Bad date/time value "0000:00:00 00:00:00": mon out of range
    13901 / 15319 ( 90.7%)  script/import_scripts/vbulletin.rb:137:in `strip': invalid byte sequence in UTF-8 (ArgumentError)
        from script/import_scripts/vbulletin.rb:137:in `block (2 levels) in import_users'
        from /var/www/discourse/script/import_scripts/base.rb:226:in `block in create_users'
        from /var/www/discourse/script/import_scripts/base.rb:225:in `each'
        from /var/www/discourse/script/import_scripts/base.rb:225:in `create_users'
        from script/import_scripts/vbulletin.rb:133:in `block in import_users'
        from /var/www/discourse/script/import_scripts/base.rb:784:in `block in batches'
        from /var/www/discourse/script/import_scripts/base.rb:783:in `loop'
        from /var/www/discourse/script/import_scripts/base.rb:783:in `batches'
        from script/import_scripts/vbulletin.rb:117:in `import_users'
        from script/import_scripts/vbulletin.rb:78:in `execute'
        from /var/www/discourse/script/import_scripts/base.rb:45:in `perform'
        from script/import_scripts/vbulletin.rb:902:in `<main>'

Anyone have any suggestions regarding how to debug and fix this?

You have an encoding problem in your database.

The database claims is using one encoding, but some of the data is encoded some other way. A job I just did had a similar problem. UTF-8 likely does not exist when you started your forum.

This is probably a problem for stack exchange or a database person. It’s not a problem with the importer.

It’s the kind of problem that will take 10 minutes following a recipe that you don’t understand, ten hours looking for that recipe, or 100 hours fixing it by hand.

3 Mi Piace

Cheers @pfaffman I was approaching the same conclusion… I started writing up the following before your comment…

It looks like it might be caused by non-ascii characters in usernames, so dumping the usernames into a text file and searching for UTF-8:

echo "select username from user" | mysql -p vb4 | grep --color='auto' -P -n "[^[:ascii:]]"

These were the entities this threw up:

’ ´ – é ã Ñ í ó 

So I used this page to generate encoded versions and updated the usernames in the database, for example:

UPDATE user SET username="&rsquo; &acute; &ndash; &eacute; &atilde; &Ntilde; &iacute; &oacute;" WHERE username="’ ´ – é ã Ñ í ó"

But the script still fails:

script/import_scripts/vbulletin.rb:137:in `strip': invalid byte sequence in UTF-8 (ArgumentError)
        from script/import_scripts/vbulletin.rb:137:in `block (2 levels) in import_users'
        from /var/www/discourse/script/import_scripts/base.rb:226:in `block in create_users'
        from /var/www/discourse/script/import_scripts/base.rb:225:in `each'
        from /var/www/discourse/script/import_scripts/base.rb:225:in `create_users'
        from script/import_scripts/vbulletin.rb:133:in `block in import_users'
        from /var/www/discourse/script/import_scripts/base.rb:784:in `block in batches'
        from /var/www/discourse/script/import_scripts/base.rb:783:in `loop'
        from /var/www/discourse/script/import_scripts/base.rb:783:in `batches'
        from script/import_scripts/vbulletin.rb:117:in `import_users'
        from script/import_scripts/vbulletin.rb:78:in `execute'
        from /var/www/discourse/script/import_scripts/base.rb:45:in `perform'
        from script/import_scripts/vbulletin.rb:902:in `<main>'

So I then dumped the whole users table into a text file:

echo "select * from user" | mysql -p vb4 > /tmp/allusers.txt

And then tried all the suggesting in this stackexchange thread for finding non-ascii characters and none were found, so now to search the whole database for the problem…

When I find a solution I’ll post it here in case it helps others…

2 Mi Piace

The problem almost certainly exists in other tables.

You need to figure out what it’s encoded in and fix it.

Or, it could be that for some years it’s in one encoding and other years it’s another.

Best of luck. I was relieved they my client had engineers they solved the problem so I didn’t have to. I may have some notes that I’ll try to find when I get out of bed.

1 Mi Piace

The database on the old server was UTF-8 but clearly it has some non-UTF-8 in it, the site has been in use for a long time and has 13k users… so taking care with dumping the old database:

mysqldump -uroot -p database -r dump.sql

And trying various methods to check the encoding (thanks to Stackexchange):

file dump.sql 
  dump.sql: ASCII text, with very long lines

apt install uchardet 
uchardet dump.sql
  UTF-8

iconv -f utf-8 -t utf-8 dump.sql > dump.utf-8.sql
  iconv: illegal input sequence at position 29618109

apt install moreutils
isutf8 dump.sql 
  dump.sql: line 2995, char 42, byte 29618109: Expecting bytes in the following ranges: 00..7F C2..F4.

And this is a image line:

INSERT INTO `customavatar` VALUES (6355,'ÿØÿà\0^PJFIF\0^A^A\0\0^A\0^A\0\0ÿþ\0;CREATOR: gd-jpeg v1.0 (using IJG JPEG v62), quality = 75

And before I delete the line using vim I need to increase the size of the partitions as it is a 1.4G file and I’m running out of space when editing it…

1 Mi Piace

The problem was a user with &#55357;&#56444; in the username field, once the HTML entities were removed the import script ran, but there were a lot of errors like this:

ERR Error running script (call to f_b06356ba4628144e123b652c99605b873107c9be): @user_script:14: @user_script: 14: -MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error. 

Is this something that I should be concerned about and something that I should fix and then redo the import?

Are you out of disk space?

1 Mi Piace

Yes! I’m now spinning up a new virtual server with a huge amount of disk space, CPUs and RAM and I’m going to start from scratch…

By the way, I’m following the instructions above for the Docker version and found that I needed to add an additional step in the container

echo "discourse ALL = NOPASSWD: ALL" >> /etc/sudoers

Before running:

su discourse -c 'bundle install --no-deployment --without test --without development'

In the non-docker instructions above there is this step to delete data from the database before doing the import:

  • Clear existing data from your local Discourse instance
cd ~/discourse
bundle exec rake db:drop db:create db:migrate

Was this omitted from the Docker instructions on purpose?

1 Mi Piace

There are two, different, vbulletin import scripts, in the docker container:

cd /var/www/discourse
find ./ -name vbulletin.rb
./script/bulk_import/vbulletin.rb
./script/import_scripts/vbulletin.rb

The second one is twice the size of the first one and it is the one I have been using.