I AM testing as a 'Regular' user

I want the registered-users and Guests to access the Category/Topics. I want registered-users to be able to reply to the Posts in this Category.
But I do not want them to be able to create new Topics in this Category.
So, I think the Settings are correct, no ?

Please look at my category privileges settings -

But,

1. Registered users are able to create new Topics !
2. but, they are not able to see the Posts under the Topics !!

What gives ?

any help will be appreciated
SD

@pichalite said in How to delete all topics from a Category ?:

delete/purging topics from the client side does not remove the category

You are right....so I am left with a 'fake' category which I disable anyway

@pichalite said in How to delete all topics from a Category ?:

@assamese how are you moving all the topics to the "fake category"

@pichalite I was not ignoring you...but I do not remember how I did it

and, the Chrome (Developer Tools) console looks like this -

When the user navigates to http://<mylandingpage.com>/bb , the browser screenshot looks like this -

I have a similar problem with nginx configuration (and, redirection) - https://community.nodebb.org/topic/8955/where-is-the-htaccess-file/1

Any help will be apreciated

SD

I have a landing page (eg. mylandingpage.com) from where a link takes my users to my NodeBB which is hosted on a different server eg. some-ip-address:4567 .
After the browser travels to the NodeBB -page, I want the browser address to display <mylandingpage>.com/bb as opposed to some-ip-address:4567

How do I solve this ?

@pichalite - I did the changes to NINX conf, it does not seem to work.
Here is the relevant portion the nginx.conf file where <mylandingpage>.com is hosted -

server_name <mylandingpage>.com;
location / {
root html;
index index.html index.htm;
}

    location /bb {
            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://<ip-address-of-nodeBB-host>:4567/;
            proxy_redirect off;

            # Socket.IO Support
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
    }

My nginx version is: nginx/1.10.1

I changed the config.json file for NodeBB -
{
"url": "http://<mylandingpage>.com/bb",
..
}

When the user navigates to http://<mylandingpage>.com/bb , the browser shows -
/ Not Found
You seem to have stumbled upon a page that does not exist. Return to the home page.

Folks,
I have a landing page (eg. mylandingpage.com) from where a link takes my users to my NodeBB which is hosted on a different server eg. some-ip-address:4567 .
After the browser travels to the NodeBB -page, I want the browser address to display <mylandingpage>.com/bb as opposed to some-ip-address:4567

How do I solve this ?
Thanks in advance,
SD

any help will be appreciated

Needless to say, I want to add a custom home page

Because I need to preserve the CaiegoryID which is used by the WriteAPI-plugIn

On the ACP, I select General -> Home Page
then, I select Custom
for Custom Route, I enter 'myhome'
then, what do I do ?

BTW, I have installed and activated the nodebb-plugin-custom-pages
Thanks in advance
SD

I collected this data when my NodeBB became unresponsive (ie. could not access forum from my browser)

vmstat output from my AWS host -
procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----
r b swpd free buff cache si so bi bo in cs us sy id wa st
0 0 0 263132 150504 178488 0 0 1 2 0 2 0 0 100 0 0

logs from my Chrome console -

nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:13 nodebb-plugin-custom-pages: loaded
http://127.0.0.1:4567/api/?_=1464717261007 Failed to load resource: net::ERR_EMPTY_RESPONSE
nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11 Uncaught TypeError: Cannot read property 'bodyClass' of undefined(anonymous function) @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11e.translate @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:15(anonymous function) @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11f @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:10t.parse @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:10o @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11r @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11(anonymous function) @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11$.ajax.error @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:11u @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:1f.fireWith @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:1T @ nodebb.min.js?8cb834b4-180f-4e3d-9f1e-619a63792609:3i @ no

I found another way -

1. create a fake category
2. move all topics (from the category from where you want to delete all topics) to this fake category
3. purge the category from where you want to delete all topics
4. delete the fake category

Any recommended solutions ?

I somehow feel (Not sure !) my situation is related to the nodebb-plugin-custom-pages

@julian Not sure if the CPU usage spikes to 100%. I will keep an eye when it freezes the next time. Thanks
SD