Skip to content
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

[v0.11.0-rc1] not able to create new board - insert failed #650

Closed
rgoltz opened this issue Jul 20, 2016 · 5 comments
Closed

[v0.11.0-rc1] not able to create new board - insert failed #650

rgoltz opened this issue Jul 20, 2016 · 5 comments

Comments

@rgoltz
Copy link

rgoltz commented Jul 20, 2016

Dear Maxime,

great that you released the 1st RC of wekan v0.11.0 via #648. Here my current setup: wekan-v0.11.0-rc1, mongodb-v2.4.14, node-v0.10.41
The mongodb was empty before the inital startup of wekan. I created a new user [I ran into #473 again] and after login as this user, I tried to create a new board.

Unfortunately on UI side nothing happens after click on "Create". In the Console of Firefox, I see:

insert failed: n@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:97:2600
t@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:97:2472
c.Collection.prototype[n]@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:97:6503
@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:131:4344
d/</c[r]@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:131:1720
e@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:298:18011
i/c/t[n]/</<@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:254:6210
f._withCurrentView@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:60:22623
i/c/t[n]/<@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:254:6171
e._withTemplateInstanceFunc@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:62:5222
i/c/t[n]@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:254:6149
a/</</</<@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:60:26550
f._withCurrentView@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:60:22623
a/</</<@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:60:26511
i/this.delegatedHandler</<@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:60:8872
u<.node_modules.meteor.jquery["jquery.js"]/</ie.event.dispatch@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:29:18035
u<.node_modules.meteor.jquery["jquery.js"]/</ie.event.add/g.handle@http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:29:14743

On the server-side there is no wekan- or mongo- expection thrown/shown.

Does this test-case works on your side by using v0.11.0-rc1 along a clean mongodb?

Cheers, Robert

@rgoltz
Copy link
Author

rgoltz commented Jul 20, 2016

Maybe the output of Chrome-Console is better:

insert failed: Error: members.0.isInvited is not allowed by the schema
    at n (http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:97:2600)
    at t (http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:97:2472)
    at c.Collection.(anonymous function) [as insert] (http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:97:6505)
    at .<anonymous> (http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:131:4346)
    at c.(anonymous function) [as insert] (http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:131:1722)
    at n.e [as onSubmit] (http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:298:18018)
    at http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:254:6212
    at Object.f._withCurrentView (http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:60:22623)
    at http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:254:6173
    at e._withTemplateInstanceFunc (http://collaboration.recs.work/5ebe4b2c2c7f577f51c979da5292843b0b80e995.js?meteor_js_resource=true:62:5222)

@mquandalle
Copy link
Contributor

mquandalle commented Jul 20, 2016

I haven’t reseted my database before doing my pre-publish tests, and since we don’t have automated tests I didn’t catch this critical bug. Thank you for the report.

@AlexanderS
Copy link
Contributor

Oh this is a result of #616. It was a leftover from a local change.

AlexanderS added a commit to AlexanderS/wekan that referenced this issue Jul 20, 2016
@chriswunsch00
Copy link

Will this fix be released for the deploy via heroku ? As i'm still hitting this error.

@mquandalle
Copy link
Contributor

I’ve just tested it and Heroku deployment is working. I think you started your deployment just before I released rc2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants