-
-
Notifications
You must be signed in to change notification settings - Fork 346
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
Unable to comment on research module #3508
Comments
Thanks @pizzaisdavid. Starting to look now. |
Like @pizzaisdavid I can't replicate locally. I'm copying over a research item from prod into the dev db to see if there's some about the shape of the live data that's causing a problem. The research which I couldn't add a comment to on prod (https://community.preciousplastic.com/research/turn-precious-plastic-into-a-dao) I could add a comment to on dev (https://dev.onearmy.world/research/turn-precious-plastic-into-a-dao) |
I can still make a comment... |
Oh wait, is this because of the updated security roles...? Update: no. |
Did some more prod testing(!) I was able to add a comment to the last update on this research: https://community.projectkamp.com/research/can-we-renovate-a-granite-ruin |
I can't replicate the 'fine for newer' but 'broken for older' locally. All are fine. |
I wonder if it's something about pre-existing but empty discussion documents. |
I deleted the discussion for the last update on here: https://community.preciousplastic.com/research/turn-precious-plastic-into-a-dao I was then able to sucessfully add a comment. |
I then added a second comment, deleted both and then sucessfully added a new 'first' comment. So it's not about the comments being empty. The only difference is the new discussion object had a 'contributorIds' array. So that looks like the issue. |
I've updated the prod data so all discussions now has the contributorIds arrray. Now users can add comments again! YAY! Tomorrow I'll fix the brittle implementation that caused this. And update the contributorIds to have the ids each should. |
Describe the bug
As a user, I want to be able to give feedback on someone's research but cannot. Trying to leave a comment doesn't work.
Steps to reproduce the behaviour
Expected behaviour
My comment is published.
Additional context
There is some output in the console, this snippet might be of interest:
click here for full console log output
Currently, commenting works on the development environment (https://precious-plastics-v4-dev.firebaseapp.com/research/lc-test-240506-0059 I am the account called testtesttest.)
source: https://discord.com/channels/586676777334865928/1237309179937689625/1237415816375435438
The text was updated successfully, but these errors were encountered: