Open quantjin opened 8 years ago
Hi @JerryYangJin , I had the same issue, in the short time I managed it adding the route as first option inside routes.js... something like:
module.exports.routes = {
'get /api/:id/journal': 'JournalController.index'
//...
};
I found that it was catching according to the order they were created. Check setting it as the first key in routes. Hope it helps!
Same issue on:
"sails": "~0.12.3",
"sails-auth": "^2.1.3",
"sails-permissions": "^2.2.0",
Try creating a model with the name Journal?
The file should be in your model directory, Journal.js with the following content:
module.exports = {};
Hello, I'm using sails
0.12.1
, sails-auth2.1.3
, sails-permissions2.2.0
in my app, i have route set as
JournalController
when i go to
/myaccount/journal
, it doesn't work per controller/action, i got500
server error. Before i use sails permission, this part works.In the console there's warning and error:
so just wondering if sails-auth, sails-permission already use some routes, i can find some in sails-auth, it seems it has no conflict with my own route:
route from sails-auth
also, what's the autoCreatedBy error about?
some update: if i only use sails-auth, it still works, it seems the issue is with sails-permissions
Thanks!