RocketChat / Rocket.Chat

The communications platform that puts data protection first.
https://rocket.chat/
Other
40.06k stars 10.34k forks source link

Problem for importing a channel from Slack #26553

Open aleciane opened 2 years ago

aleciane commented 2 years ago

Dear all

I have just registered to Rocket.chat, and I am trying to transfer a project from Slack. I am following the procedure you describe here:

https://docs.rocket.chat/guides/administration/admin-panel/import/slack

However when I finally click on "Start importing", I have a message saying "Failed to start import operation".

Could you please help me to solve this problem as soon as possible ?

Many thanks in advance. Evelyne Capture d’écran 2022-08-12 à 11 47 11 Capture d’écran 2022-08-12 à 11 47 06 Capture d’écran 2022-08-12 à 11 46 31

PS: attached are screenshot of several different steps of the procedure.

dotty37 commented 2 years ago

Hi, this issue was reported starting from 5.0.1, and still happening on 5.0.3 The previously reported issue was #26479 Thanks for adding to this, hopefully, the devs will have some time to solve this.

dudanogueira commented 2 years ago

Hi! It should be fixed in 5.1.0.

aleciane commented 2 years ago

Still not working. I am on a Mac, and the only version I can install is 3.8.4

Evelyne

Le 15 août 2022 à 16:04, Duda Nogueira @.***> a écrit :

Hi! It should be fixed in 5.1.0.

— Reply to this email directly, view it on GitHub https://github.com/RocketChat/Rocket.Chat/issues/26553#issuecomment-1215050747, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJQPZTTGQHDYTAMZODVMXYTVZJE5FANCNFSM56LDGHOA. You are receiving this because you authored the thread.

dudanogueira commented 2 years ago

@aleciane version 5.1.0 is the server version, and it was not released yet.

vinogradovia commented 2 years ago

@alecian, do you have users without email in your Slack export file?

I haved similar problem, and i added field user["profile"]["email"] in user.json for every user without email in my slack.zip. Fixed for me.

version 5.1.0

DarinDev1000 commented 2 years ago

I also fixed the issue by adding an email field to all the slack bots that didn't have an email

wishx commented 2 years ago

Would someone be kind enough to show us how to do this? I have the user.json open in VS Codium, but I don't see anywhere to add user["profile"]["email"] or even any actual email addresses from Slack users (no @something anywhere). Thanks in advance!

Edit: I added it on profile like so:

{
        "id": "U040AFSF5QF",
        "team_id": "THJ1RHKPV",
        "name": "slashgif",
        "deleted": true,
        "profile": {
            "title": "",
            "phone": "",
            "skype": "",
            "email": "",
. . .  etc.

I did this at first for bots, then for all users, and it still fails even with bots unselected.

I'm still on 5.0.3 because I'm using a Cloud instance at rocket.chat.

wishx commented 2 years ago

I also fixed the issue by adding an email field to all the slack bots that didn't have an email

How did you do it exactly? I can't get it to work in 5.0.3.

DarinDev1000 commented 2 years ago

I added email like you have but filled in the value with a dummy email:

{
        "id": "U040AFSF5QF",
        "team_id": "THJ1RHKPV",
        "name": "slashgif",
        "deleted": true,
        "profile": {
            "title": "",
            "phone": "",
            "skype": "",
            "email": "botname@example.com",
. . .  etc.
wishx commented 2 years ago

I added email like you have but filled in the value with a dummy email:

Thanks. I replaced the actual user email addresses with their real email addresses (exported from the Slack user CSV) and the bots with their bot emails, but no luck. It still craps out. I might just have to wait for 5.10.0 on the Cloud server. If you have any other tips, I'm all ears.

shaymdev commented 2 years ago

I think there were several other changes to the slack importing code in 5.1.0. @DarinDev1000 You performed your workaround against 5.1.0, right? I performed that workaround against 5.1.0 and the import succeeded.

Perhaps @wishx is right and he'll need to wait for 5.1.0 (or even 5.1.x where this issue has been fixed).

I think this is officially a duplicate of #26479 so should probably be closed. Anyone disagree?

DarinDev1000 commented 2 years ago

Looks like you're need to wait for the 5.1.0 update. I used 5.1.2 As long as the PR that closed #26479 works, this should be fine to close