@julian
Hahaha, good question. I didn't even notice. I just googled for the documentation to get to it quickly. I didn't even pay attention to the URL.
I run into the same issue with nginx without any Cloudfare rules set for the forum and without any CDN active, so the webserver serves content directly.
Fix:
NodeBB
config.json
There should be no forward slash at the end which complies with the documentation:
"url": "https://blabla.com/forum",
nginx.conf
here note the double slash on the first line /forum/
The double slash solves the issue, at least during initial testing on different browsers and devices.
Not sure if this is a Windows/nginx specific thing as the path's are set a bit different.
[...]
location /forum/ {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
# proxy_pass http://127.0.0.1:4567;
proxy_pass http://io_nodes;
proxy_redirect off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
@pichalite said in Show post edit timestamp:
@JaredBusch you can create a plugin to listen to the filter for getting category posts and modify the data as required.
I have no desire (well not much of one) to become a dev for something like this.
I taught myself how to write VB in 1995 and VB .Net back in the early 2000's and have a number of applications to my credit, but it is not my desired path.
But, if there is nothing out there for this already, I guess it is something I can look into.
In 0.8.x, any plugin that appears in the ACP plugin list is compatible. Or if you're on GitHub, in the package.json will be something like:
"nbbpm": {
"compatibility": "^0.6.0 || ^0.7.0 || ^0.8.0"
},
note the ^0.8.0 part. If a plugin is missing this, it's deemed not compatible.
