f71b3742e123afd3f5036f5a512de34740bfe5e2.js?meteor_js_resource=true:9 Uncaught (in promise) Error: GraphQL error: {"id":"app.operation_not_allowed","value":"check"}
at new t (f71b3742e123afd3f5036f5a512de34740bfe5e2.js?meteor_js_resource=true:9)
at f71b3742e123afd3f5036f5a512de34740bfe5e2.js?meteor_js_resource=true:9
at f71b3742e123afd3f5036f5a512de34740bfe5e2.js?meteor_js_resource=true:1
This is what I get in the console when I click “Suggest Curation” (there is no other apparent effect from clicking the button).
Ah, turns this will be a moderate chunk of time to fix (or at least, requires some delicate work to get right, or requires a very different approach than the one I’d been using). I’d accidentally only tested this using users that were also moderators, who had higher level permissions, and it’s a finicky process to give users _some_ ability to modify a post but not full access to it.
Alas – for the immediate future I’ll be changing this feature to be mods only, and will hopefully get a broader version working sometime in the next week or so. (Since my plan for next week was to work on the karma overhaul, I’m now leaning towards just waiting till after that)
This is what I get in the console when I click “Suggest Curation” (there is no other apparent effect from clicking the button).
(Mac, 10.9, Chrome 66.stuff)
Ah, turns this will be a moderate chunk of time to fix (or at least, requires some delicate work to get right, or requires a very different approach than the one I’d been using). I’d accidentally only tested this using users that were also moderators, who had higher level permissions, and it’s a finicky process to give users _some_ ability to modify a post but not full access to it.
Alas – for the immediate future I’ll be changing this feature to be mods only, and will hopefully get a broader version working sometime in the next week or so. (Since my plan for next week was to work on the karma overhaul, I’m now leaning towards just waiting till after that)
Apologies!
Huh. Alas. Looking into a fix.