like every other plugin…
like every other plugin…
I’m getting the same error, everything has been updated and I manually changed the import template for the mariadb bug before building the container:
root@xx:/var/discourse# ./launcher enter import
The phpBB3 import is starting…
loading existing groups…
loading existing users…
loading existing categories…
loading existing posts…
loading existing topics…
importing from phpBB 3.0.14
_query': Table 'phpbb.phpbb_users' doesn't exist (Mysql2::Error) from /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/mysql2-0.4.4/lib/mysql2/client.rb:107:inblock in query’
handle_interrupt' from /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/mysql2-0.4.4/lib/mysql2/client.rb:106:inquery’
query' from /var/www/discourse/script/import_scripts/phpbb3/database/database_base.rb:16:inquery’
count' from /var/www/discourse/script/import_scripts/phpbb3/database/database_3_0.rb:7:incount_users’
import_users' from /var/www/discourse/script/import_scripts/phpbb3/importer.rb:28:inexecute’
perform' from /var/www/discourse/script/import_scripts/phpbb3/importer.rb:20:inperform’
<module:PhpBB3>' from script/import_scripts/phpbb3.rb:12:inmodule:ImportScripts’
from script/import_scripts/phpbb3.rb:11:in `'
sql dump was done from the phpbb admin interface.
I’m not sure why this is happening. The InnoDB engine is disabled because there are performance issues when used with Docker. It should use MyISAM as fallback when the specified engine doesn’t exist. And in all my tests that’s exactly what’s happening.
Can you send me a database dump (export only the structure, no data) from the phpBB admin interface? I’d like to compare it with mine. I’d really like to solve this issue.
Here’s a workaround: Try replacing
ENGINE=InnoDB in your database dump with
ENGINE=MyISAM and restart the import.
You’ll probably need to delete the file
/var/discourse//shared/standalone/import/mysql/imported in order to recreate the database on next import.
Replacing every ENGINE=InnoDB to ENGINE=MyISAM inside the dump did the trick for me! Thank you!
Just imported my phpbb3 install into a blank discourse install and am having an issue with missing user profiles. The weird thing is, profiles work just fine for some users, but not others. I get an “Oops! That page doesn’t exist or is private.” error. I’ve been looking at the user table in the postgresql db trying to find some correlation between users with missing profiles, but no avail. I’ve attached a few screen shots. Any suggestions?
Figured out why profiles broke. Background: I am migrating from a phpbb3 installation where everyone had a local account. We are going to use LDAP for authentication in discourse and want to ensure that each username matches what we have in Active Directory. I accomplished this by grabbing all user email addresses and made a bunch of LDAP queries to grab valid usernames. After the import, in an effort to ensure that we had correct AD usernames for everyone, I ran update commands on the postgresql db (users table). We had a few stragglers that didn’t use their company email when they signed up initially, so those profiles didn’t break. All records that were touched by my sql statements, regardless of whether or not the username actually changed, caused the user profile to break. Lesson learned.
Does anyone know of the correct way to mass update usernames?
I suggest updating the usernames in phpBB3 before the import.
I updated the initial post with a more detailed guide for the Docker based import and added lots of entries to the FAQ.
Please don’t hesitate to ask if something is still unclear or in need of a better explanation.
I am really lost since 5 hours now. Docker is new for me aswell as discourse as well as digitalocean.
Just wanted to try something new since phpbb don’t be compatible with php7 (yet).
But don’t worry I am not a complete newby. Just mysql is not my strength.
So everything worked till the mysql remote stuff / import script.
First I got all the time Access denied so I tried different solutions to fix it. Now I got till that part here:
But don’t know why… in my phpmyadmin the prefix is exactly like the console saying it is wrong
Would really appreciate any help
Please check the table prefix in the
settings.yml. It should be
phpbb_ without the dot.
I guess I need to change the comment in the settings file.
Well I did this because I thought, ok, if the sql don’t give me the stuff I put it in the settings.yml
If I am doing it like you mentioned it is coming:
This is my settings.yml
host: localhost port: 3306 username: root password: schema: phpbb table_prefix: phpbb_
Thank you very much for helping me!!
Are you trying to connect to a remote database or did you put a database dump in the
/var/discourse/shared/standalone/import/data/ directory? The database configuration you posted is for the internal database of the Docker container which needs a database dump for it to work.
You can find the correct
table_prefix in phpBB’s Administration Control Panel. In the following screenshot the prefix is
phpbb_ since all tables start with this. You can set the prefix to blank if the table names have no prefix.
I tried both but for now I trying the local dumb. I did what you show. Downloaded the gzip file. Renamed it to phpbb_mysql.sql and placed it in /var/discourse/shared/standalone/import/data/
So still if I try it I get the screenshot above.
Do I need to update anything after I moved the .sql file to the import/data container?
I am missing one stupid thing for sure, sorry
Did you unpack the gzip file? What’s the output of the import script when you start it? It should look like this:
Loading database dump into MySQL…
The phpBB3 import is starting…
If it doesn’t try deleting the following file on the host:
Afterwards try to start the import script one more time.
oooooh man… after 7 hours… this little command did it!! Thank you so much Gerhard.
(Ich wusste es war was blödes, aber darauf wäre ich nie gekommen )
Thanks so much for keeping this script up to date @gerhard.
I’m just having two consistent problems with importing from phpBB 3.1.9.
What’s happening is that all of my users are being ‘suspended’ or are somehow considered ‘anonymous’.
Say a user is called ‘John’.
The discourse install ends up with ‘John’ and his correct email address but with no posts by that user.
It also creates ‘John1’ with the anonymous string email address, and it attributes all posts to ‘John1’ rather than ‘John’.
It seems simple, but I’ve spent ages trying to figure it out - any tips?
The second issue I’m having is that returns from phpBB3 are being converted to some kind of courier new left/right scrolling window in discourse.
So it looks like this:
Looks like you have 4 spaces in front of text there.
4 spaces in front of text means a code block
<-- 4 spaces there
Wonderful, thanks Jeff, I’ll run a query to remove them.
(Interestingly, clicking edit and then save edit removed them on the running site - thought that was pretty cool).
EDIT: looks like some are tabs …
That’s strange. Could it be that those posts by John look like they were posted by an anonymous user? Were the affected posts created by phpBB or did you import them from another forum software into your current phpBB3 forum?
Take a look at a post by John in the database:
SELECT poster_id, post_username FROM phpbb_posts
post_username should be empty unless it was posted by an anonymous user.
Great thinking @gerhard.
Yes it was translated from ‘esoTalk’ which allows spaces in the usernames.
I had gone through the users and posts tables to make ‘James North’ become ‘JamesNorth’ but it appears something is still missing. After doing that, it just makes all users suspended/anonymous and at least isn’t creating the duplicate users.
I’m guessing it’s exactly what you are suggesting - post_username in the phpbb_posts table. Might got check that out, do another export from phpbb3 and post back.
Thanks again guys - it’s all going to be worth it as Discourse looks powerful and visually stunning.