### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [January 27, 2022, 11:10pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/667 "2022-01-27T23:10:18Z")
Markdown should work as well, but I guess using `` could work around even more edge cases. Mind, mixing HTML and Markdown has some gotchas as well… Here’s a simple Markdown solution:
```plaintext
**multiline\
\
text**
```
I’m curious, from which version of phpBB are you importing? The conversion of BBCode to Markdown is a lot better for 3.2 than it is for previous versions. Ideally you shouldn’t even see `[b]` in imported posts anymore.
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [January 27, 2022, 11:33pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/668 "2022-01-27T23:33:56Z")
> [@gerhard](#):
>
> Markdown should work as well
I guess you’re right, I don’t know why I didn’t think about that first…
I’m migrating from phpBB **3.0.7-PL1**.
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [January 28, 2022, 8:51am UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/669 "2022-01-28T08:51:07Z")
You will do yourself a big favor if you upgrade to 3.2 before the import. 😉
Make sure the BBCodes in all posts are migrated to the new storage format by running the phpBB reparser: [https://www.phpbb.com/support/docs/en/3.3/kb/article/phpbb-32%2B-text-reparser/](https://www.phpbb.com/support/docs/en/3.3/kb/article/phpbb-32%2B-text-reparser/)
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [January 28, 2022, 12:24pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/670 "2022-01-28T12:24:26Z")
> [@gerhard](#):
>
> You will do yourself a big favor if you upgrade to 3.2 before the import. 😉
I thought about that at the beginning, but… I hate computer stuff 😅
I don’t know phpBB well and I didn’t want to have to handle any error that could happen during an update from such an old version.
Since the Discourse migration script is compatible with phpBB 3.0, I chose not to upgrade phpBB…
Maybe some bbcode issues I encountered would have been avoided with a phpBB upgrade. Stuff like nested lists, `[b]` with new lines, etc…🤷♂️
But since I started working on the import in December, I’m close to having an import that works well (ideally, the new forum would be online in maybe two weeks…) and I’m not sure I want to experiment right now an update of phpBB, especially if I have to review all the custom import fixes I’ve done to see if the phpBB 3.2 importer manages these things better 😅. It would be time-consuming.
That said… I could experiment with stuff this ~~weekend~~ afternoon if I’m bored enough!
* * *
edit: I tried; moving on a new server and then upgrading to pbpBB 3.2 is a hassle. HTTPS issues. Cache issues. Other issues. Circonvoluted and frustrating procedures. The official tutorial advises using tools requiring outdated PHP version (hey, PHP 5, long time no see…). Apparently, I’m sometimes bored but not insane - not enough to do this kind of stuff at least.
Gerhard! You’re misleading! Upgrading to 3.2 is not a big favor! 😆
But enough talking about phpBB itself… And praise the one-click upgrade from Discourse.
---
### Author:  [@j3ang](https://meta.discourse.org/u/j3ang)
#### Post date: [February 24, 2022, 11:16pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/671 "2022-02-24T23:16:26Z")
Hi,
I’m trying to migrate WordPress users to discourse. I was able to follow the instructions to connect to our WP database and import users in the docker container. I wanted to make sure no emails will be sent during or after the migration because we are using SSO WordPress plugin.
I prefixed the emails with “import\_” so they don’t receive in case there are background tasks sending email confirmation after the migration completed.
I see that there is last\_emailed\_at column set after migration:
I know that it’s set by `opts[:last_emailed_at] = opts.fetch(:last_emailed_at, Time.now)` in the `ImportScripts::Base::create_user()`
Is there similar function to ` admin.email_tokens.update_all(confirmed: true)` used in `ImportScripts::Base::create_admin` where it confirms the email?
I don’t see any log showing the emails sent. Was there emails actually sent? Will discourse try to send emails after I change the email to valid ones?
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [February 25, 2022, 9:06am UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/672 "2022-02-25T09:06:33Z")
This is off-topic, since this topic is about the phpBB3 migration… 😉
> [@j3ang](#):
>
> I prefixed the emails with “import\_”
I recommend using a `.invalid` domain if you want to make sure that some users will never receive any emails (e.g. `foo@mywpimport.invalid`). But, if you just want to disable outgoing emails until you are ready, setting the `disable_emails` site setting to “yes” or “non-staff” is your best option!
Outgoing emails are automatically disabled _during_ an import. The values of the `last_emailed_at` attribute are probably from Discourse _trying_ to send an email, before it discovered that it isn’t allowed to.
Discourse will definitely try to send emails _after_ the migration.
---
### Author:  [@j3ang](https://meta.discourse.org/u/j3ang)
#### Post date: [February 25, 2022, 9:55pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/673 "2022-02-25T21:55:40Z")
> [@gerhard](#):
>
> Discourse will definitely try to send emails _after_ the migration.
Thanks, I first tried empty string for the email field and the ImportScript base class generated fake emails with the invalid domain. They also have the `last_emailed_at` attribute set.
So what you are saying is as soon as I corrected the email from database, discourse will try to send the email? But a normal sign on authenticated by WordPress doesn’t require email confirmation. There’s no way around that with the ImportScript ?
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [March 7, 2022, 12:03pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/674 "2022-03-07T12:03:50Z")
My migration is done and successful.
However, I face two issues. Let me know if it’s off-topic.
1. Some post contents have this kind of content:
2. Like many old forums, old Imageshack links have been broken for a long time, and for ever. But some links now display a Ukraine flag instead of nothing:
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [March 7, 2022, 5:29pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/675 "2022-03-07T17:29:05Z")
> [@Canapin](#):
>
> Some post contents have this kind of content
Is it the line break that’s causing the issue? That would be my guess. You will need to remap those BBCodes to remove the line break. [Replace a string in all posts](https://meta.discourse.org/t/replace-a-string-in-all-posts/48729) should be helpful.
> [@Canapin](#):
>
> How would you handle this behavior?
Maybe convert them to HTML comments for now? You could later replace them with the stored images.
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [March 7, 2022, 5:46pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/676 "2022-03-07T17:46:25Z")
> [@gerhard](#):
>
> Is it the line break that’s causing the issue?
It doesn’t seem that’s the issue:
I added line breaks so the content looks like this:
```xml
[url=https://www.casimages.com/i/1907271141431956116331631.jpg.html]
[img]https://nsm09.casimages.com/img/2019/07/27//1907271141431956116331631.jpg[/img]
[/url]
```
And the result:
Example posts:
> **[Frensh Vw Bus CHERIZET 2019 SK](https://vw-camper.fr/t/frensh-vw-bus-cherizet-2019-sk/12719/13?u=canapin)**
>
> trois photos du meeting :
> [@gerhard](#):
>
> Maybe convert them to HTML comments for now? You could later replace them with the stored images.
Yes, that’s a good idea! 👍 So basically, replacing the strings (from the topic you linked) using regexes to target Imageshack links only, right?
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [March 9, 2022, 10:45pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/677 "2022-03-09T22:45:45Z")
> [@gerhard](#):
>
> Is it the line break that’s causing the issue? That would be my guess. You will need to remap those BBCodes to remove the line break. [Replace a string in all posts](https://meta.discourse.org/t/replace-a-string-in-all-posts/48729) should be helpful.
So, this is not the issue after experimenting with new lines.
But if I copy-paste the post content into a **new** post on the **same** forum, the content is correctly displayed 🥴 ❓ :
(and also the hotlinked images are successfully downloaded locally)
Vs:
I tried rebaking the post with the broken images (that are correctly displayed in the message preview, see my previous post) but it didn’t fix anything.
As far as I know, the raw content from both posts is exactly the same.
But the cooked content from the first post (second line) leads to broken images:
I’m puzzled.
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [March 10, 2022, 12:50pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/678 "2022-03-10T12:50:46Z")
Odd thing:
If I try to rebuild the HTML of **any post** , I got an error 500:
Logs show a fatal error and a warning:
### Screenshot of the log window:
### Fatal error:
`ArgumentError (wrong number of arguments (given 0, expected 1)) lib/guardian/ensure_magic.rb:11:in 'method_missing' app/controllers/posts_controller.rb:570:in 'rebake' app/controllers/application_cont`
```plaintext
plugins/discourse-chat/lib/guardian_extensions.rb:71:in `can_rebake?'
lib/guardian/ensure_magic.rb:11:in `method_missing'
app/controllers/posts_controller.rb:570:in `rebake'
actionpack (6.1.4.1) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
actionpack (6.1.4.1) lib/abstract_controller/base.rb:228:in `process_action'
actionpack (6.1.4.1) lib/action_controller/metal/rendering.rb:30:in `process_action'
actionpack (6.1.4.1) lib/abstract_controller/callbacks.rb:42:in `block in process_action'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:117:in `block in run_callbacks'
app/controllers/application_controller.rb:397:in `block in with_resolved_locale'
i18n (1.10.0) lib/i18n.rb:328:in `with_locale'
app/controllers/application_controller.rb:397:in `with_resolved_locale'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:126:in `block in run_callbacks'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:137:in `run_callbacks'
actionpack (6.1.4.1) lib/abstract_controller/callbacks.rb:41:in `process_action'
actionpack (6.1.4.1) lib/action_controller/metal/rescue.rb:22:in `process_action'
actionpack (6.1.4.1) lib/action_controller/metal/instrumentation.rb:34:in `block in process_action'
activesupport (6.1.4.1) lib/active_support/notifications.rb:203:in `block in instrument'
activesupport (6.1.4.1) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
activesupport (6.1.4.1) lib/active_support/notifications.rb:203:in `instrument'
actionpack (6.1.4.1) lib/action_controller/metal/instrumentation.rb:33:in `process_action'
actionpack (6.1.4.1) lib/action_controller/metal/params_wrapper.rb:249:in `process_action'
activerecord (6.1.4.1) lib/active_record/railties/controller_runtime.rb:27:in `process_action'
actionpack (6.1.4.1) lib/abstract_controller/base.rb:165:in `process'
actionview (6.1.4.1) lib/action_view/rendering.rb:39:in `process'
rack-mini-profiler (3.0.0) lib/mini_profiler/profiling_methods.rb:85:in `block in profile_method'
actionpack (6.1.4.1) lib/action_controller/metal.rb:190:in `dispatch'
actionpack (6.1.4.1) lib/action_controller/metal.rb:254:in `dispatch'
actionpack (6.1.4.1) lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
actionpack (6.1.4.1) lib/action_dispatch/routing/route_set.rb:33:in `serve'
actionpack (6.1.4.1) lib/action_dispatch/journey/router.rb:50:in `block in serve'
actionpack (6.1.4.1) lib/action_dispatch/journey/router.rb:32:in `each'
actionpack (6.1.4.1) lib/action_dispatch/journey/router.rb:32:in `serve'
actionpack (6.1.4.1) lib/action_dispatch/routing/route_set.rb:842:in `call'
lib/middleware/omniauth_bypass_middleware.rb:71:in `call'
rack (2.2.3) lib/rack/tempfile_reaper.rb:15:in `call'
rack (2.2.3) lib/rack/conditional_get.rb:40:in `call'
rack (2.2.3) lib/rack/head.rb:12:in `call'
actionpack (6.1.4.1) lib/action_dispatch/http/permissions_policy.rb:22:in `call'
lib/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:358:in `call'
rack (2.2.3) lib/rack/session/abstract/id.rb:266:in `context'
rack (2.2.3) lib/rack/session/abstract/id.rb:260:in `call'
actionpack (6.1.4.1) lib/action_dispatch/middleware/cookies.rb:689:in `call'
actionpack (6.1.4.1) lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:98:in `run_callbacks'
actionpack (6.1.4.1) lib/action_dispatch/middleware/callbacks.rb:26:in `call'
actionpack (6.1.4.1) lib/action_dispatch/middleware/actionable_exceptions.rb:18:in `call'
actionpack (6.1.4.1) lib/action_dispatch/middleware/debug_exceptions.rb:29:in `call'
actionpack (6.1.4.1) lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
logster (2.10.1) lib/logster/middleware/reporter.rb:43:in `call'
railties (6.1.4.1) lib/rails/rack/logger.rb:37:in `call_app'
railties (6.1.4.1) lib/rails/rack/logger.rb:28:in `call'
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
actionpack (6.1.4.1) lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
actionpack (6.1.4.1) lib/action_dispatch/middleware/request_id.rb:26:in `call'
lib/middleware/enforce_hostname.rb:23:in `call'
rack (2.2.3) lib/rack/method_override.rb:24:in `call'
actionpack (6.1.4.1) lib/action_dispatch/middleware/executor.rb:14:in `call'
rack (2.2.3) lib/rack/sendfile.rb:110:in `call'
actionpack (6.1.4.1) lib/action_dispatch/middleware/host_authorization.rb:92:in `call'
rack-mini-profiler (3.0.0) lib/mini_profiler/profiler.rb:249:in `call'
message_bus (4.2.0) lib/message_bus/rack/middleware.rb:60:in `call'
lib/middleware/request_tracker.rb:202:in `call'
railties (6.1.4.1) lib/rails/engine.rb:539:in `call'
railties (6.1.4.1) lib/rails/railtie.rb:207:in `public_send'
railties (6.1.4.1) lib/rails/railtie.rb:207:in `method_missing'
rack (2.2.3) lib/rack/urlmap.rb:74:in `block in call'
rack (2.2.3) lib/rack/urlmap.rb:58:in `each'
rack (2.2.3) lib/rack/urlmap.rb:58:in `call'
unicorn (6.1.0) lib/unicorn/http_server.rb:634:in `process_client'
unicorn (6.1.0) lib/unicorn/http_server.rb:739:in `worker_loop'
unicorn (6.1.0) lib/unicorn/http_server.rb:547:in `spawn_missing_workers'
unicorn (6.1.0) lib/unicorn/http_server.rb:143:in `start'
unicorn (6.1.0) bin/unicorn:128:in `'
vendor/bundle/ruby/2.7.0/bin/unicorn:25:in `load'
vendor/bundle/ruby/2.7.0/bin/unicorn:25:in `'
```
It was in safe-mode with all theme and plugins disabled, but this code block mentions on the first line:
`plugins/discourse-chat/lib/guardian_extensions.rb:71:in 'can_rebake?'`
### Warning:
`Failed to handle exception in exception app middleware : ArgumentError : wrong number of arguments (given 0, expected 1)`
```plaintext
/var/www/discourse/plugins/discourse-chat/lib/guardian_extensions.rb:71:in `can_rebake?'
/var/www/discourse/lib/guardian/ensure_magic.rb:11:in `method_missing'
/var/www/discourse/app/controllers/posts_controller.rb:570:in `rebake'
actionpack-6.1.4.1/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
actionpack-6.1.4.1/lib/abstract_controller/base.rb:228:in `process_action'
actionpack-6.1.4.1/lib/action_controller/metal/rendering.rb:30:in `process_action'
actionpack-6.1.4.1/lib/abstract_controller/callbacks.rb:42:in `block in process_action'
activesupport-6.1.4.1/lib/active_support/callbacks.rb:117:in `block in run_callbacks'
/var/www/discourse/app/controllers/application_controller.rb:397:in `block in with_resolved_locale'
i18n-1.10.0/lib/i18n.rb:328:in `with_locale'
/var/www/discourse/app/controllers/application_controller.rb:397:in `with_resolved_locale'
activesupport-6.1.4.1/lib/active_support/callbacks.rb:126:in `block in run_callbacks'
activesupport-6.1.4.1/lib/active_support/callbacks.rb:137:in `run_callbacks'
actionpack-6.1.4.1/lib/abstract_controller/callbacks.rb:41:in `process_action'
actionpack-6.1.4.1/lib/action_controller/metal/rescue.rb:22:in `process_action'
actionpack-6.1.4.1/lib/action_controller/metal/instrumentation.rb:34:in `block in process_action'
activesupport-6.1.4.1/lib/active_support/notifications.rb:203:in `block in instrument'
activesupport-6.1.4.1/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
activesupport-6.1.4.1/lib/active_support/notifications.rb:203:in `instrument'
actionpack-6.1.4.1/lib/action_controller/metal/instrumentation.rb:33:in `process_action'
actionpack-6.1.4.1/lib/action_controller/metal/params_wrapper.rb:249:in `process_action'
activerecord-6.1.4.1/lib/active_record/railties/controller_runtime.rb:27:in `process_action'
actionpack-6.1.4.1/lib/abstract_controller/base.rb:165:in `process'
actionview-6.1.4.1/lib/action_view/rendering.rb:39:in `process'
rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:85:in `block in profile_method'
actionpack-6.1.4.1/lib/action_controller/metal.rb:190:in `dispatch'
actionpack-6.1.4.1/lib/action_controller/metal.rb:254:in `dispatch'
actionpack-6.1.4.1/lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
actionpack-6.1.4.1/lib/action_dispatch/routing/route_set.rb:33:in `serve'
actionpack-6.1.4.1/lib/action_dispatch/journey/router.rb:50:in `block in serve'
actionpack-6.1.4.1/lib/action_dispatch/journey/router.rb:32:in `each'
actionpack-6.1.4.1/lib/action_dispatch/journey/router.rb:32:in `serve'
actionpack-6.1.4.1/lib/action_dispatch/routing/route_set.rb:842:in `call'
/var/www/discourse/lib/middleware/omniauth_bypass_middleware.rb:71:in `call'
rack-2.2.3/lib/rack/tempfile_reaper.rb:15:in `call'
rack-2.2.3/lib/rack/conditional_get.rb:40:in `call'
rack-2.2.3/lib/rack/head.rb:12:in `call'
actionpack-6.1.4.1/lib/action_dispatch/http/permissions_policy.rb:22:in `call'
/var/www/discourse/lib/content_security_policy/middleware.rb:12:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:358:in `call'
rack-2.2.3/lib/rack/session/abstract/id.rb:266:in `context'
rack-2.2.3/lib/rack/session/abstract/id.rb:260:in `call'
actionpack-6.1.4.1/lib/action_dispatch/middleware/cookies.rb:689:in `call'
actionpack-6.1.4.1/lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
activesupport-6.1.4.1/lib/active_support/callbacks.rb:98:in `run_callbacks'
actionpack-6.1.4.1/lib/action_dispatch/middleware/callbacks.rb:26:in `call'
actionpack-6.1.4.1/lib/action_dispatch/middleware/actionable_exceptions.rb:18:in `call'
actionpack-6.1.4.1/lib/action_dispatch/middleware/debug_exceptions.rb:29:in `call'
actionpack-6.1.4.1/lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
logster-2.10.1/lib/logster/middleware/reporter.rb:43:in `call'
railties-6.1.4.1/lib/rails/rack/logger.rb:37:in `call_app'
railties-6.1.4.1/lib/rails/rack/logger.rb:28:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:23:in `call'
/var/www/discourse/config/initializers/100-silence_logger.rb:31:in `call'
actionpack-6.1.4.1/lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
actionpack-6.1.4.1/lib/action_dispatch/middleware/request_id.rb:26:in `call'
/var/www/discourse/lib/middleware/enforce_hostname.rb:23:in `call'
rack-2.2.3/lib/rack/method_override.rb:24:in `call'
actionpack-6.1.4.1/lib/action_dispatch/middleware/executor.rb:14:in `call'
rack-2.2.3/lib/rack/sendfile.rb:110:in `call'
actionpack-6.1.4.1/lib/action_dispatch/middleware/host_authorization.rb:92:in `call'
rack-mini-profiler-3.0.0/lib/mini_profiler/profiler.rb:249:in `call'
message_bus-4.2.0/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:202:in `call'
railties-6.1.4.1/lib/rails/engine.rb:539:in `call'
railties-6.1.4.1/lib/rails/railtie.rb:207:in `public_send'
railties-6.1.4.1/lib/rails/railtie.rb:207:in `method_missing'
rack-2.2.3/lib/rack/urlmap.rb:74:in `block in call'
rack-2.2.3/lib/rack/urlmap.rb:58:in `each'
rack-2.2.3/lib/rack/urlmap.rb:58:in `call'
unicorn-6.1.0/lib/unicorn/http_server.rb:634:in `process_client'
unicorn-6.1.0/lib/unicorn/http_server.rb:739:in `worker_loop'
unicorn-6.1.0/lib/unicorn/http_server.rb:547:in `spawn_missing_workers'
unicorn-6.1.0/lib/unicorn/http_server.rb:143:in `start'
unicorn-6.1.0/bin/unicorn:128:in `'
/var/www/discourse/vendor/bundle/ruby/2.7.0/bin/unicorn:25:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/bin/unicorn:25:in `'
```
Do this information help?
I’m doing what I can to try to repair these posts, but I’m starting to believe this has something to do with Discourse itself and not something on my side maybe? 🤷
* * *
edit: see the automatically linked post below.
* * *
Issue resolved:
> [@Discourse-chat (even disabled) leads to error 500 when rebaking posts](https://meta.discourse.org/t/discourse-chat-even-disabled-leads-to-error-500-when-rebaking-posts/220618/5):
>
> Good catch! I’ve just merged a PR to fix this:
Now I just have to rebake all my posts. 😉
* * *
Another edit:
> [@gerhard](#):
>
> Is it the line break that’s causing the issue? That would be my guess. You will need to remap those BBCodes to remove the line break. [Replace a string in all posts](https://meta.discourse.org/t/replace-a-string-in-all-posts/48729) should be helpful.
Could have worked for sure, and will for images that still have their old plain URL, but:
- Since all the old Imageshack broken links were replaced by **valid images** displaying a Ukraine flag by Imageshack itself, they were automatically uploaded to Discourse, changing their URL to a markdown local image link.
- Fortunately, all these flags were uploaded to Discourse with identical links (`` in my case - excellent Discourse behavior by the way 👍), which means that they will be very easy to target and remove/replace with something else. 🙂
I’m just writing this to inform people that would encounter the same issue as me after a migration.
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [May 25, 2022, 2:03pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/679 "2022-05-25T14:03:24Z")
> [@Sebastien\_Guilbaud](#):
>
> I’m able to query all polls votes, and for 2 of them, I have negative “anonymous\_votes”. It seems this forum somehow allowed anonymous voting, actually
It seems like the `poll_option_total` value is off sometimes. I’m seeing more non-anonymous votes per option than the value of `poll_option_total`. And all those users exist.
> [@gerhard](#):
>
> Please let me know when you’ve found a solution
Using `GREATEST(..., 0)` fixes it. At least, it doesn’t crash.
```plaintext
SELECT o.poll_option_id, o.poll_option_text, o.poll_option_total AS total_votes,
GREATEST(CAST(o.poll_option_total AS SIGNED) - (
SELECT COUNT(DISTINCT v.vote_user_id)
FROM #{@table_prefix}poll_votes v
JOIN #{@table_prefix}users u ON (v.vote_user_id = u.user_id)
JOIN #{@table_prefix}topics t ON (v.topic_id = t.topic_id)
WHERE v.poll_option_id = o.poll_option_id AND v.topic_id = o.topic_id
),0) AS anonymous_votes
FROM #{@table_prefix}poll_options o
WHERE o.topic_id = #{topic_id}
ORDER BY o.poll_option_id
```
---
### Author:  [@Greg\_Shepperd](https://meta.discourse.org/u/Greg_Shepperd)
#### Post date: [June 26, 2022, 10:04pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/680 "2022-06-26T22:04:45Z")
I really want to migrate my company’s phpbb 3.3 forum to Discourse. Does anyone have any idea when that will be supported?
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [June 26, 2022, 10:07pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/681 "2022-06-26T22:07:28Z")
> [@Change from phpbb to Discourse](https://meta.discourse.org/t/change-from-phpbb-to-discourse/230968/4):
>
> We’re currently finishing the last touches for PHPBB 3.3 import support, I will create a PR for that within two weeks.
---
### Author:  [@Greg\_Shepperd](https://meta.discourse.org/u/Greg_Shepperd)
#### Post date: [June 26, 2022, 10:07pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/682 "2022-06-26T22:07:55Z")
Oh wow, thats great! Thanks!
---
### Author:  [@linux4me](https://meta.discourse.org/u/linux4me)
#### Post date: [July 7, 2022, 6:30pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/684 "2022-07-07T18:30:39Z")
If I should start a new thread for this, I apologize in advance.
I’ve got a phpBB forum in a subfolder:
```plaintext
thedomain.com/forum/
```
I’m planning to use the import script to migrate from phpBB to Discourse in a subdomain; i.e.:
```plaintext
forum.thedomain.com
```
So, it looks like all I’ll need to do–for the domain and permalinks–is set the following in settings.yml using HTTPS on the new site:
```plaintext
site_prefix:
# this is needed for rewriting internal links in posts
original: thdomain.com/forum # without http(s)://
new: https://forum.thedomain.com # with http:// or https://
# Enable this, if you want to redirect old forum links to the the new locations.
permalinks:
categories: true # redirects /viewforum.php?f=1 to /c/category-name
topics: true # redirects /viewtopic.php?f=6&t=43 to /t/topic-name/81
posts: true # redirects /viewtopic.php?p=2455#p2455 to /t/topic-name/81/4
# Append a prefix to each type of link, e.g. 'forum' to redirect /forum/viewtopic.php?f=6&t=43 to /t/topic-name/81
# Leave it empty if your forum wasn't installed in a subfolder.
prefix: forum
```
And then, on the original server, which runs Apache, in the .htaccess with RewriteEngine already on, I’ll need:
```plaintext
RewriteCond %{HTTP_HOST} ^thedomain.com
RewriteRule ^forum/(.*)$ https://forum.thedomain.com/$1 [L,R=301]
```
If it’s really that easy, this script rocks! 😀
I do have a couple of additional questions:
1. Posts are set to “false” in the permalink settings. I know there are links out there to specific posts, so I’d like them permalinked as well. Is there any reason not to set them to true; e.g., performance or something?
2. Is the prefix okay without single quotes, or should it be quoted as in the comment?
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [July 7, 2022, 6:54pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/685 "2022-07-07T18:54:11Z")
> [@linux4me](#):
>
> there any reason not to set them to true
It will slightly slow down the import, but you shouldn’t worry about that. It’s mostly disabled by default because it’s rarely needed.
> [@linux4me](#):
>
> Is the prefix okay without single quotes
Yes, that’s fine.
---
### Author:  [@linux4me](https://meta.discourse.org/u/linux4me)
#### Post date: [July 7, 2022, 9:43pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/686 "2022-07-07T21:43:39Z")
I ran into a snag as I’m preparing for this import.
The phpBB forum I’m planning to migrate is using a custom BBcode that creates HTML img tags for images stored in folders by year in a directory outside phpBB, but on the same user account on the server. The BBcode takes the following format:
```plaintext
[Gallery]{NUMBER1}|{NUMBER2}|{NUMBER3}|{SIMPLETEXT}[/Gallery]
```
The `{NUMBER1}` and `{NUMBER2}` are integers for the width and height of the image, respectively. The `{NUMBER3}` is an integer for the year-folder the image is in, and the `{SIMPLETEXT}` is the image file name. The HTML replacement for the BBcode looks like this:
```plaintext
```
What I need to figure out is how to handle this custom BBcode with the migration script, both to convert the custom BBcode to something Discourse can use, and figure out where to put the image files in the file tree for the import.
I took a look at [Ruby-BBcode-to-MD](https://github.com/nlalonde/ruby-bbcode-to-md), which says it “allows to easily extend this set with custom tags by editing tags.rb.” I took a look at [tags.rb](https://github.com/nlalonde/ruby-bbcode-to-md/blob/master/lib/tags/tags.rb), but since this is my first time looking at Ruby code, I’m at a loss as to how to deal with my custom BBcode since its pipe-separated format differs from any of the official BBcodes that the tags.rb file includes which I might have used as a guide.
I don’t have `templates/import/phpbb3.template.yml` loaded yet, so I’m guessing that will add the Ruby BBcode to MD gem?
So I have questions:
1. What is the best way to handle this custom BBcode for the migration? Is editing the tags.rb file the way to go? (If so, I’m going to do some research on Ruby coding and maybe regex next, but any hints will be welcome!)
2. What is the best place to put the image files for this gallery in the import file tree so that they’re saved in Discourse and show up in the imported posts?
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [July 7, 2022, 9:52pm UTC](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810/687 "2022-07-07T21:52:03Z")
That gem isn’t really used anymore. From which version of phpBB are you importing? If it’s v3.1 or below, you will need to apply some regex magic in [discourse/script/import\_scripts/phpbb3/support/text\_processor.rb at ea2fd75d10e81687334f8d29e0d3e786dbdb4a53 · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/ea2fd75d10e81687334f8d29e0d3e786dbdb4a53/script/import_scripts/phpbb3/support/text_processor.rb).
For v3.2 you can add BBCode handling in [discourse/script/import\_scripts/phpbb3/support/bbcode/xml\_to\_markdown.rb at a71b219c9a18ad418e330282fde511bcb79ba7c4 · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/a71b219c9a18ad418e330282fde511bcb79ba7c4/script/import_scripts/phpbb3/support/bbcode/xml_to_markdown.rb)
[Previous page](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810.md?page=17)
[Next page](https://meta.discourse.org/t/migrate-a-phpbb3-forum-to-discourse/30810.md?page=19)