Unfortunately I haven't had the time to look at this in depth yet 😞
0.4.2. admin panel cant't save & ajaxify app undefined
-
using 0.4.2 admin panel clicking save is unresponsive, seems like javascript are not initiated. and ajaxify app is undefined
Uncaught ReferenceError: app is not defined ajaxify.js?v=v0.3.2-1550-g7f6ae6d:273
ive already upgraded to the latest npm package which fixed the ajaxify.js bug on the homepage.
-
Have you updated vanilla and lavender packages as well?
-
@julian i did here are the dep ver
"nodebb-plugin-mentions": "~0.4.0",
"nodebb-plugin-markdown": "~0.4.1",
"nodebb-widget-essentials": "~0.0.21",
"nodebb-theme-vanilla": "~0.0.19",
"nodebb-theme-lavender": "~0.0.25",
"nodebb-plugin-soundpack-default": "~0.1.1",
"nodebb-plugin-dbsearch": "0.0.9" -
It sounds like the minified javascript file does not compile properly. Can you run NodeBB in development mode
./nodebb dev
and let me know if you run into any errors? -
@julian during compilation this is the only warning
warn: [plugins/nodebb-widget-essentials] staticDir is deprecated, use staticDirs insteadi've also set it up one directory up so /forum, when trying to login it redirects the user to /user/name instead of /forum/user/name
-
Ah! A subfolder install!
Those are not so well supported by NodeBB (though @planner knows I've tried)... best bet is to stick with a subdomain install (e.g. forum.yourdomain.com) if at all possible.
If you're insistent, we can take a look -- what is "relative_path" set to in your
config.json
? -
{ "base_url": "http://localhost", "port": "4567", "use_port": true, "secret": "hidden", "bind_address": "127.0.0.1", "database": "redis", "redis": { "host": "127.0.0.1", "port": "6379", "password": "", "database": "1" }, "bcrypt_rounds": 12, "upload_path": "/public/uploads", "relative_path": "/forum" }
im planning to connect my user database to this nodebb later, and didnt want to shell out another server, can check it. http://yako.io/forum.
-
hm... and your nginx config?
base_url
should behttp://yako.io
use_port
should befalse
-
upstream app_nodebb { server localhost:4567; } location /forum { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_set_header X-Nginx-Proxy true; proxy_pass http://app_nodebb/forum; proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }
-
@clinraus Awesome -- looks like it is set up perfectly. The issue on the admin end is probably a bug on our end.
Feel free to follow along at #1497
-
@julian said:
Subfolder install ACP inaccessible
should also add in login redirect issues with subfolder