linnovate / mean-tokens

This is the repository to manage the menio cli npm package.
7 stars 6 forks source link

Editable content is hidden #5

Open mediahack opened 10 years ago

mediahack commented 10 years ago

I installed this package and my nav links are hidden and uneditable.

dtelaroli commented 10 years ago

After to install a warn and 404 happens

npm WARN engine mean-tokens@0.0.3: wanted: {"node":"0.10.x","npm":"1.3.x"} (current: {"node":"v0.10.28","npm":"1.4.10"})
GET http://localhost:3000/tokens/title [HTTP/1.1 404 Not Found 9ms]
GET http://localhost:3000/tokens/title/site-title [HTTP/1.1 404 Not Found 12ms]
GET http://localhost:3000/tokens/title/home-default [HTTP/1.1 404 Not Found 13ms]
GET http://localhost:3000/tokens/title/all%20articles [HTTP/1.1 404 Not Found 13ms]
GET http://localhost:3000/tokens/title/create%20article [HTTP/1.1 404 Not Found 28ms]
GET http://localhost:3000/tokens/title/mypackage%20example%20page [HTTP/1.1 404 Not Found 12ms]
GET http://localhost:3000/tokens/title/all%20tokens [HTTP/1.1 404 Not Found 67ms]

I changed the npm version to 1.3.x and work fine.

isorna commented 10 years ago

I've the same problem, with npm 1.4.3, should I change my version to use mean-tokens?

dtelaroli commented 10 years ago

It's a workaround while the problem isn't solved.

ryanrankin commented 10 years ago

What is the status of this issue? It would be nice to play with this feature but it is unusable for me at this point.

Here is what I get ==>

$ mean install mean-tokens Installing module: mean-tokens from branch (version): master

npm WARN package.json karma-chrome-launcher@0.1.4 No README data npm WARN package.json karma-coffee-preprocessor@0.2.1 No README data npm WARN package.json karma-coverage@0.2.4 No README data npm WARN package.json karma-phantomjs-launcher@0.1.4 No README data npm WARN package.json mean-translate@0.0.1 No repository field. npm WARN package.json mean-connect-mongo@0.4.3 No repository field. npm WARN engine mean-tokens@0.0.4: wanted: {"node":"0.10.x","npm":"1.3.x"} (current: {"node":"v0.10.28","npm":"1.4.16"}) mean-tokens@0.0.4 node_modules/mean-tokens

$mean user hey@ryanrankin.me --addRole Admin

When I fire it up in the browser, I get the nice little on off switch but no link to admin panel and no edits can be made. Is this what's expected for npm > 1.3.x?

mkanev commented 10 years ago

@ryanrankin I have almost the same problem. But in my case after installation I see the nav link Token Administration but it routes to nowhere. And on page loading there is an error:

Error: [ng:areq] Argument 'AdminController' is not a function, got undefined
http://errors.angularjs.org/1.2.18/ng/areq?p0=AdminController&p1=not%20aNaNunction%2C%20got%20undefined
at http://localhost:3000/system/lib/angular/angular.js:78:12
at assertArg (http://localhost:3000/system/lib/angular/angular.js:1475:11)
at assertArgFn (http://localhost:3000/system/lib/angular/angular.js:1485:3)
at http://localhost:3000/system/lib/angular/angular.js:7198:9
at http://localhost:3000/system/lib/angular/angular.js:6592:34
at forEach (http://localhost:3000/system/lib/angular/angular.js:327:20)
at nodeLinkFn (http://localhost:3000/system/lib/angular/angular.js:6579:11)
at compositeLinkFn (http://localhost:3000/system/lib/angular/angular.js:6028:13)
at publicLinkFn (http://localhost:3000/system/lib/angular/angular.js:5923:30)
at link (http://localhost:3000/system/lib/angular/angular.js:19656:38) 

Additional info

>mean list
MEAN Packages List:
-----------------
Contrib: mean-admin@0.0.3  Author: Linnovate
Contrib: mean-tokens@0.0.4  Author: Rivka Tzur
Custom: articles@0.0.1  Author: Linnovate

>mean user <email>
DB connection successful!

[ { __v: 0,
_id: 53b06bb2ff89080417e7eda9,
email: '<email>',
hashed_password: '9vyoWRtAmbyplfeacWTZKi5yxDphZAGa9cgwT95w7lf12qjR5a6Uz+p8HTyySirm7oHG2Z0+qX632KGh8ssSwQ==',
name: 'Maksim Kanev',
provider: 'local',
roles: [ 'authenticated', 'admin' ],
salt: 'jPJYLLRfFm6kaMjHYBfwQA==',
username: 'mkanev' } ]
Jameshu229 commented 10 years ago

After installing the module, I have "Token Administration" on the nav bar but it cannot be clicked.

liorkesos commented 10 years ago

Maybe we he role is case sensitive . Try adding admin (lower case a) instead. Liir On Jun 26, 2014 9:36 PM, "ryanrankin" notifications@github.com wrote:

What is the status of this issue? It would be nice to play with this feature but it is unusable for me at this point.

Here is what I get ==>

$ mean install mean-tokens Installing module: mean-tokens from branch (version): master

npm WARN package.json karma-chrome-launcher@0.1.4 No README data npm WARN package.json karma-coffee-preprocessor@0.2.1 No README data npm WARN package.json karma-coverage@0.2.4 No README data npm WARN package.json karma-phantomjs-launcher@0.1.4 No README data npm WARN package.json mean-translate@0.0.1 No repository field. npm WARN package.json mean-connect-mongo@0.4.3 No repository field. npm WARN engine mean-tokens@0.0.4: wanted: {"node":"0.10.x","npm":"1.3.x"} (current: {"node":"v0.10.28","npm":"1.4.16"}) mean-tokens@0.0.4 node_modules/mean-tokens

$mean user hey@ryanrankin.me --addRole Admin

When I fire it up in the browser, I get the nice little on off switch but no link to admin panel and no edits can be made. Is this what's expected for npm > 1.3.x?

— Reply to this email directly or view it on GitHub https://github.com/linnovate/mean-tokens/issues/5#issuecomment-47262541.

mkanev commented 10 years ago

@liorkesos As you can see in my case it is already in lowercase. roles: [ 'authenticated', 'admin' ],

daton89 commented 10 years ago

i have the same error: daton$ mean install mean-tokens Installing module: mean-tokens from branch (version): master

npm WARN engine mean-tokens@0.0.5: wanted: {"node":"0.10.x","npm":"1.3.x"} (current: {"node":"0.10.28","npm":"1.4.23"}) /

mean-health@0.1.5 postinstall /Users/daton/WebstormProjects/prMean/node_modules/mean-tokens/node_modules/mean-health node postinstall

mean-tokens does not have a pulse mean-tokens@0.0.5 node_modules/mean-tokens └── mean-health@0.1.5

Contrib: mean-tokens@0.0.5 Author: Rivka Tzur

installing v 1.3 of npm is the only solution?