-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import Slack users (via CSV or ZIP) won't work #25363
Comments
maybe some of this problems related to #19454 |
Hi, I'm also encountering this problem. Is Slack CSV import known to be working with the latest Rocketchat? Description:Importing file containing Slack users won't work. Steps to reproduce:
Expected behavior:Rocket chat gives the ability to select users which I want to import and Import succeeds without a problems. Actual behaviors:The results of an attempted import are: File Uploaded Successfully
Server Setup Information:Version 4.8.0 Deployment ID zqMHQwXX2NW5YogoG Apps Engine Version 1.32.0 Node Version v14.18.3 Database Migration 265 (June 7, 2022 7:20 PM) MongoDB 5.0.8 / wiredTiger (oplog Enabled) Commit Details HEAD: (0e38639) Branch: HEAD PID 9 Client Setup Information
Relevant logs:
or
|
Description:
Importing file containing Slack users won't work. There is many iterations of that problem, but I can't find a way to stably reproduce any of them.
Steps to reproduce:
Expected behavior:
Rocket chat gives the ability to select users which I want to import and Import succeeds without a problems.
Actual behaviors:
There are more than one behaviors:
Server Setup Information:
Version of Rocket.Chat Server: 4.6.3
Operating System: CentOS Linux release 7.9.2009 (Core)
Deployment Method: yum + src
Number of Running Instances: 1
DB Replicaset Oplog:
NodeJS Version: v14.0.0
MongoDB Version: 4.4.13 / wiredTiger (oplog Enabled)
Proxy: nginx/1.20.1
Firewalls involved: iptables, ACCEPT ALL
Client Setup Information
Additional context
Maybe the problems caused because of non-latin (cyrillic) symbols in users names.
Relevant logs:
-
The text was updated successfully, but these errors were encountered: