-
Notifications
You must be signed in to change notification settings - Fork 261
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
Tabular.Table - Tabular.Table options must specify collection - Roles Collection #216
Comments
+1 |
I had similar issue few weeks ago but this is related to aldeed:tabular package. Try to report an issue there. One thing you can do is to check if collection causing a problem is |
Try to open .meteor/packeges file and put |
My package looks like this (with roles after collection2) but still getting the above error while trying to add roles to admin page meteor-platform |
Put it after dburles:collection-helpers We did it today ;) |
tried that and various other ordering, still getting the error, may i see your package list, maybe if i just copied your exact packages and ordering... i'd like to rule this out before looking at code/file ordering? |
meteor-platform How you add the collection to the admin configuration file? type in browser console Meteor.roles and check if the has a insert,update, etc. Rights just like Meteor.users |
Also try to switch |
that didn't work either: meteor-platform however, I moved helpers, hooks and roles to just under collections and that did work... meteor-platform hopefully, someone fines this obscure ordering helpful. or rather, hopefully, no one else has to go through random permutations to get it compiling. Is there a more reliable way of debugging the build process to work out dependencies? |
That's the question |
Yup that sorted it for me too, thanks! |
I moved
No other changes to ordering were necessary, where before I was getting the following error:
|
After further investigation, the issue seems related to the position of
Our project is based on |
I have posted an issue describing the load order of the 'comments' and 'collection-hooks' packages in yogiben:meteor-starter that may be the underlying cause of this issue. |
This looks like an old issue, but I am having trouble with this nearly three years later. No amount of rearranging the packages made this work for me, I went through each of the suggestions and applied what was relevant to my code. I am still receiving this 'options must specify collection' error, which prevents my app from starting. Was there a final fix for this? |
I have enabled the Roles collection to be shown in meteor-admin as discussed in a separate issue, however for some reason showing roles and using collection-hooks, even with nothing configured for it cause the following error:
Removing either from the equation fixes the problem, but obviously isn't a real solution. Having the users, or any other collection added to meteor-admin doesn't cause any issues?
Thanks
Gareth
The text was updated successfully, but these errors were encountered: