vBulletin の URL を Discourse の URL にリダイレクト

[Discourse]

vBulletin から Discourse へ移行中で、古い vBulletin の URL を新しい Discourse の URL にリダイレクトしたいですか？続けてお読みください！

もし古いフォーラムと新しいフォーラムのベース URL が同じ場合は、代わりに以下のハウツーに従ってください：

Redirect old forum URLs to new Discourse URLs using permalinks

このハウツーでは、以下を前提としています：

• vBulletin のベース URL: www.example.com/forum
• Discourse のベース URL: forum.example.com
• www.example.com 用の Nginx サーバー

始めましょう！

Nginx マップファイルの生成

カテゴリとトピックのリダイレクトを設定するには、Nginx の map モジュールを使用します。CSV ファイルは、create_permalink_file メソッドを使用してインポートを実行する際に生成されます（script/import_scripts/vb_map.csv）。この CSV ファイルの内容をサーバー上のマップファイルに貼り付けます。

ファイルのサンプル内容：

...
/forum/forumdisplay.php?6  http://forum.example.com/c/games;
/forum/forumdisplay.php?7  http://forum.example.com/c/movies;
/forum/forumdisplay.php?13  http://forum.example.com/c/admin;
/forum/showthread.php?1  http://forum.example.com/t/x/22;
/forum/showthread.php?2  http://forum.example.com/t/x/23;
/forum/showthread.php?3  http://forum.example.com/t/x/24;
/forum/showthread.php?4  http://forum.example.com/t/x/25;
...

生成された CSV ファイルの全内容を、www.example.com サーバー上の etc/nginx/vb_forum.map にコピーしてください。

nginx.conf の編集

/etc/nginx/nginx.conf ファイルを編集して、http ブロックに以下のコードを追加します：

map_hash_bucket_size 128;
map_hash_max_size 80000;

map $request_uri $new {
    include /etc/nginx/vb_forum.map;
}

server {
    listen 80;
    server_name www.example.com;

    location ~ ^/forum\\/showthread.php {
        if ($args ~* ^(\\d+)-(.+)$) {
            set $tid $1;
            set $args '';
            rewrite ^ /forum/showthread.php?$tid permanent;
        }
        if ($args ~* ^t=(\\d+)$) {
            set $tid $1;
            set $args '';
            rewrite ^ /forum/showthread.php?$tid permanent;
        }
        return 301 http://forum.example.com;
    }

    location ~ ^/forum\\/forumdisplay.php {
        if ($args ~* ^(\\d+)-(.+)$) {
            set $tid $1;
            set $args '';
            rewrite ^ /forum/forumdisplay.php?$tid permanent;
        }
        if ($args ~* ^f=(\\d+)$) {
            set $tid $1;
            set $args '';
            rewrite ^ /forum/forumdisplay.php?$tid permanent;
        }
        return 301 http://forum.example.com;
    }

    if ($new) {
        rewrite ^ $new permanent;
    }

    location /forum {
        return 301 http://forum.example.com;
    }
}

map_hash_max_size は、マップファイルに含まれる URL の数に応じて調整する必要があります。

nginx.conf の検証

Nginx 設定ファイルを検証します：

nginx -c /etc/nginx/nginx.conf -t

変更を反映させるために Nginx 設定をリロードします：

sudo systemctl reload nginx

www.example.com/forum にアクセスしてみてください。これで forum.example.com にリダイレクトされるはずです。

上記の Nginx 設定で処理される URL の種類は以下の通りです：

• www.example.com/forum → forum.example.com
• www.example.com/forum/forumdisplay.php?6 → forum.example.com/c/games
• www.example.com/forum/forumdisplay.php?6-Games → forum.example.com/c/games
• www.example.com/forum/forumdisplay.php?f=6 → forum.example.com/c/games
• www.example.com/forum/showthread.php?2 → forum.example.com/t/topic-slug/23
• www.example.com/forum/showthread.php?2-topic-slug → forum.example.com/t/topic-slug/23
• www.example.com/forum/showthread.php?t=2 → forum.example.com/t/topic-slug/23

[webdawe (Anil Paul)]

Hi Arpit,

I have implemented your method and its working fine. But the problem is when I rebuild the app again all my nginx changes getting lost. please advise

Anil

[pfaffman (Jay Pfaffman)]

The sample assumes that you’ll do the redirects on the old server, not the Discourse server.

If your discourse server is using the same name as your old server, you want to use permalink redirects, and perhaps permalink normalizations in discourse.

[webdawe (Anil Paul)]

Thanks @pfaffman.
I used Permalink.create and solved the problem

Redirect old forum URLs to new Discourse URLs using permalinks

This reference explains how Discourse permalinks redirect old URL paths to new destinations, how permalink normalizations work, and how to test and troubleshoot redirects after a migration or URL structure change. Required user level: Administrator Console access required only when creating permalinks from an importer, script, or Rails console When you migrate from another forum or change your site’s URL structure, old links from search engines,…

[Walker_Blackwell]

For those who do not have MAP or can’t figure it out, I have figured out the easy (dumb) way to do it for topics at least. This works for VBulletin 4. I have not tested on 5 nor do a really want to deal with VBulletin ever again, so I probably won’t. I think the URL structure is the same though. This is for migrating from VBulletin 4 (hosted on NGINX) to Discourse (also hosted on NGINX).

*** Note, there are security implications with this process, but if you are new to NGINX (like I am) and just need to get this done and then figure out the fancy way later, this is what I did. In short, it requires you to keep your old vbulletin running for a while *****

1. Change your VBulletin URLs to “Advanced Friendly URLs” >Admin>Settings>Options>Friendly URLS. This will get rid of the argument character “?” in all your urls. All the destination posts will be at “…showthread.php/(the-post-id-number)-blablablabla…” Old urls with google juice will forward to the new urls. Don’t worry.

2. Now import your vbulletin and make sure that you uncomment the permalinks section (as described in this thread).

3. After import, open the vb_map.csv. You will see post to post (ID to ID) maps like xxxx837 yyyy589. The first is the ID of the VB thread and second is the ID of the Discourse thread.

The VB thread is at http://myamazinglyoldforum.com/showthread.php/837- and the new discourse one is at https://myawesomenewforum.com/t/589

4. You can probably guess what to do now. Just create a rewrite in your site-available file (above your root delineation).

Using the example above:

rewrite /showthread.php/837- https://myawesomenewforum.com/t/589 permanent;

5. The “-” is key in this whole equation so remember to put it in there. A simple txt editor with “find-replace” will convert the map file to nginx rewrite directives.

Nginx seems to be able to handle several thousand rewrites (or several hundred thousand as the case may be). I have seen no performance issues so far.

best,
Walker

[Walker_Blackwell]

Just a note on all of this. I did finally get rid of the VB forum (for security reasons).

To redirect the showthread.php?bla- to /showthread.php/bla- in nginx instead of with VB’s own PHP you do this (above your re-write rule list)

(in my case, the old forum lives at “tech” but you will change this to be whatever folder it lives at)

location ~ ^/tech(?:/(.*))?$ {
  rewrite ^/tech/showthread.php /tech/showthread.php/$args permanent;
  rewrite ^/tech/content.php /tech/content.php/$args permanent;
}

then all the redirect rules live below here:

rewrite /showthread.php/837- https://myawesomenewforum.com/t/589 permanent;

On a further note, it took me FOREVER to figure out how to simply replace a question mark with a forward slash in NGINX. Maybe I’m dumb (no I’m certainly dumb), but the above little snippet works like a charm and I don’t see it widely documented elsewhere.

edit> Thanks for the formatting.