simo
simo
Which version of Express Admin you are using? I don't see such expression in `\lib\qb\lst.js` on line 42
Check your `settings.json` file, it should be generated and filled with defaults on first start. Your configuration is corrupted for some reason. I can't tell exactly what it is just...
Which version of node do you use? How is your url looking in the browser's address bar, I can't imagine `req.params` being empty.
Yeah but in order to get the error in the listview route you have to navigate to something like http://192.168.0.2:8080/backend/[slug] And after login the admin redirects to the mainview, not...
@yhmtg my [system tests](https://github.com/simov/express-admin-tests) just hanged on the login screen when using sqlite in node 0.12. It seems that there is a breaking change in 0.12 that affects the admin,...
@yhmtg it turned out that I needed to re-build my sqlite3 module for node 0.12 Here is what I did ``` bash $ nvm use 12 # you use `nvm`...
If you can create a small test case that reproduces the bug it will be great. Like a small db with only one table + the config you are using.
Thanks for the feedback @bnny ! express-admin requires you to have primary keys in your tables. I'm adding rowid to my sqlite tables as well.
Currently it's not possible to configure such relationship through the configuration.
It's probably because NPM is trying to install the module somewhere else. Try this: - create new folder - initialize new project using `npm init` - this will generate `package.json`...