Please select a module from the dropdown on top right?

[mwaschkowski]

Hi,

Just trying out this package and not sure why I'm seeing this message, is there a config issue?

Thanks,

Mark

[kaoskeya]

Hey, could you share your kAdminConfig here so I can see if there is an issue with it.

[kaoskeya]

Hey, "dropdown on top right" refers to the dropdown which reads, "Choose module". Selecting a module from it would then show a table with the rows in that collection.

[mwaschkowski]

Hi,

Here is my config:

kAdminConfig = { name: 'Admin Panel', roles: ["admin"], collections: { LoanScenario: { tableColumns: [{ label: 'Loan Cap', name: 'locCap' }, ] }, loan_scenario:{ tableColumns: [{ label: 'Loan Cap', name: 'locCap' }, ] }, Finances:{ tableColumns:{ label: 'test', name: 'applicantName' } } } }

and my view:

[image: Inline image 1]

but nothing in the Choose module dropdown.

Thanks!

Mark

On Tue, Mar 8, 2016 at 9:58 PM, Karthikeyan [email protected] wrote:

Hey, "dropdown on top right" refers to the dropdown which reads, "Choose module". Selecting a module from it would then show a table with the rows in that collection.

— Reply to this email directly or view it on GitHub https://github.com/kaoskeya/meteor-admin/issues/20#issuecomment-194090442 .

[kaoskeya]

If you are using nemo64 bootstrap package, make sure you have set true for dropdowns and collapse.

Any error message in your browser/server console?

[mwaschkowski]

Just using standard bootstrap.

Here is my Collection definition:

Finances = new Mongo.Collection('finances');

if (Meteor.isServer) { Finances.allow({ insert: function(userId, doc) { return true; },

update: function(userId, doc, fieldNames, modifier) {
  return true;
},

remove: function(userId, doc) {
  return true;
}

}); }

Finances.attachSchema(new SimpleSchema({ userId: { type: String, autoValue: function() { return this.userId; } }, applicantName: { type: String, label: "Applicant Name", optional: true, }, ...

On Wed, Mar 9, 2016 at 5:56 AM, Karthikeyan [email protected] wrote:

If you are using nemo64 bootstrap package, make sure you have set true for dropdowns and collapse.

Any error message in your browser/server console?

— Reply to this email directly or view it on GitHub https://github.com/kaoskeya/meteor-admin/issues/20#issuecomment-194240796 .

[mwaschkowski]

Sorry, forgot to mention, no error messages in console.

Do you have a simple config file that I can create a collection in mongo to match it and see if it works?

Thank you!

Mark

On Wed, Mar 9, 2016 at 6:01 AM, Mark Waschkowski [email protected] wrote:

Just using standard bootstrap.

Here is my Collection definition:

Finances = new Mongo.Collection('finances');

if (Meteor.isServer) { Finances.allow({ insert: function(userId, doc) { return true; },

update: function(userId, doc, fieldNames, modifier) {
  return true;
},

remove: function(userId, doc) {
  return true;
}

}); }

Finances.attachSchema(new SimpleSchema({ userId: { type: String, autoValue: function() { return this.userId; } }, applicantName: { type: String, label: "Applicant Name", optional: true, }, ...

On Wed, Mar 9, 2016 at 5:56 AM, Karthikeyan [email protected] wrote:

If you are using nemo64 bootstrap package, make sure you have set true for dropdowns and collapse.

Any error message in your browser/server console?

— Reply to this email directly or view it on GitHub https://github.com/kaoskeya/meteor-admin/issues/20#issuecomment-194240796 .

[kaoskeya]

Hey, your configuration seems alright.

Here is some sample code that works:

kAdminConfig = {
    name: "KAOS Agency Admin",
    roles: [ "admin" ],
    collections: {
        Content:{
            tableColumns:[
                { label:'Title', name:'title' },
                { label:'Description', name:'description' },
                { label:'Slug', name:'slug'}    
            ]
        }
    }
}

Content = new Mongo.Collection('content');

Content.attachSchema(new SimpleSchema({
  title: {
    type: String
  },
  description: {
    type: String,
    autoform: {
      afFieldInput: {
        type: 'summernote'
      }
    }
  },
  slug:{
    type:String
  }
}))

[mwaschkowski]

Thanks for the config. I added in the content collection and tried the new config but didn't work, button doesn't do anything and no error messages. This was the first time trying it and I have a lot of libraries in place already, maybe some kind of incompatibility?

Unless you have any other suggestions?

Thanks

Mark

Here are my libs:

accounts-base 1.2.2 A user account system accounts-facebook 1.0.6 Login service for Facebook accounts accounts-password 1.1.4 Password support for accounts alanning:roles 1.2.15 Authorization package for Meteor aldeed:autoform 5.8.1 Easily create forms with automatic insert and update, and automatic reactive validation. aldeed:autoform-bs-datepicker 1.1.1 Custom bootstrap-datepicker input type for AutoForm aldeed:collection2 2.9.0 Automatic validation of insert and update operations on the client and server. aldeed:delete-button 2.0.0 Provides a delete button UI component blaze-html-templates 1.0.1 Compile HTML templates into reactive UI with Meteor Blaze cfs:filesystem 0.1.2 Filesystem storage adapter for CollectionFS cfs:standard-packages 0.5.9 Filesystem for Meteor, collectionFS dburles:collection-helpers 1.0.4 Transform your collections with helpers that you define ecmascript 0.1.6* Compiler plugin that supports ES2015+ in all .js files es5-shim 4.1.14 Shims and polyfills to improve ECMAScript 5 support fortawesome:fontawesome 4.5.0 Font Awesome (official): 500+ scalable vector icons, customizable via CSS, Retina friendly hinas:meteor-bootstrap-confirmation 0.9.0 Bootstrap powered popover confirmation. houston:admin 2.0.6 A zero-config Meteor Admin huttonr:bootstrap3 3.3.6_6* Modular, customizable Bootstrap 3. iron:router 1.0.12 Routing specifically designed for Meteor jquery 1.11.4 Manipulate the DOM using CSS selectors kaoskeya:admin 0.2.5 Simple autoform based admin that integrates with your bootstrap design. less 2.5.1 Leaner CSS language meteor-base 1.0.1 Packages that every Meteor app needs mobile-experience 1.0.1 Packages for a great mobile user experience mongo 1.1.3 Adaptor for using MongoDB and Minimongo over DDP mrt:chosen-package 0.11.1 Chosen is a library for making long, unwieldy select boxes more friendly. mrt:jquery-ui 1.9.2 jQuery-UI - jQuery user interface msavin:jetsetter 1.5.2 In-App Session Editor msavin:mongol 1.6.2 In-App MongoDB Editor rajit:bootstrap3-datepicker 1.5.1 Meteor packaging of eternicode/bootstrap-datepicker for Bootstrap 3 session 1.1.1 Session variable standard-minifiers 1.0.2 Standard minifiers used with Meteor apps by default. tracker 1.0.9 Dependency tracker to allow reactive callbacks twbs:bootstrap 3.3.6 The most popular front-end framework for developing responsive, mobile first projects on the web. underscore 1.0.4 Collection of small helpers: _.map, _.each, ... useraccounts:bootstrap 1.13.1 Accounts Templates styled for Twitter Bootstrap. useraccounts:iron-routing 1.13.1 UserAccounts package providing routes configuration capability via iron:router. yogiben:autoform-file 0.4.2* File upload for AutoForm

On Wed, Mar 9, 2016 at 6:34 AM, Karthikeyan [email protected] wrote:

Hey, your configuration seems alright.

Here is some sample code that works:

kAdminConfig = { name: "KAOS Agency Admin", roles: [ "admin" ], collections: { Content:{ tableColumns:[ { label:'Title', name:'title' }, { label:'Description', name:'description' }, { label:'Slug', name:'slug'} ] } } }

Content = new Mongo.Collection('content');

Content.attachSchema(new SimpleSchema({ title: { type: String }, description: { type: String, autoform: { afFieldInput: { type: 'summernote' } } }, slug:{ type:String } }))

— Reply to this email directly or view it on GitHub https://github.com/kaoskeya/meteor-admin/issues/20#issuecomment-194253627 .

[kaoskeya]

Hey, I don't see anything that could cause a conflict.

Could you please do a quick check by creating a new project, adding the admin package and dependencies and just copy pasting the schema and the admin from my previous reply and see if it works? You can then try adding the other packages to see what is breaking the admin panel.