Closed Comoque1 closed 2 years ago
I think if you were to reset the db, and then start up the server with comms enabled this issue may not happen.
Looking at the stack trace above it is the assign user to community that is failing, so the user is created ok.
I think if you were to reset the db, and then start up the server with comms enabled this issue may not happen.
Looking at the stack trace above it is the assign user to community that is failing, so the user is created ok.
Will give it a try locally. Same behavior was experienced on demo env.
think any ecoverse / challenge / opportunity that was created without comms enabled has this issue. Should be straightforward to fix, and am pretty sure on @Enderedne radar...
Can you please retest this with the server-937 branch?
The issue is reproducible on Test env. The error is a bit different.
Needs a clean home server database?
Not able to reproduce the issue on DEV env. Closing.
Describe the bug When populating datа to server with enable "communications" feature, error is thrown.
To Reproduce Steps to reproduce the behavior:
Precondition: the server has "communications" feature enabled
Using
populator
dev branch, upload "alkemio-sdgs.ods"Error is thrown, regarding
rooms/communications
In addition, when try to query messages, error is thrown