Forum Access control have no options to choose/set

apaunganhote

Hello,

Please check the attachment below

I am using NodeBB v0.7.0-dev and is it known bugs?

Is there any other way around to solve this? I can't seem to set any permission to the forum.

Best Regards,

julian

@apaunganhote This is not a known bug, but thank you for reporting. I'll do a fresh install and take a look today.

julian

Can't reproduce on MongoDB or Redis.

apaunganhote

Hello @julian ,

Thank you. I will be waiting for a resolution.

Best Regards,

julian

@apaunganhote

Can you please provide the following information to help us debug?

Server or client operating system (if applicable)
NodeBB version and hash
- To get the hash, run git rev-parse HEAD from the root of your NodeBB folder
If applicable, theme versions
- npm ls nodebb-theme-persona

Thanks!

apaunganhote

Hello @julian

Sure.

Digital Ocean, Ubuntu 14.04, node v0.12.1
NodeBB v0.7.0-dev and hash tag "ed8d60b76bf77b2bc6508a6ecb1f9547557db4ce"
Lavendar, Version 1.0.26

I am using on Redis.

Best Regards,

apaunganhote

And here is a log of NodeBB incase you need it.

28/3 12:49 [17674] - warn: [plugins/nodebb-plugin-jsfiddle] This plugin may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing.
28/3 12:49 [17674] - warn: [plugins/nodebb-plugin-jsfiddle] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset plugin="nodebb-plugin-jsfiddle".

28/3 12:49 [17674] - warn: [plugins/nodebb-theme-lavender] This plugin may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing.
28/3 12:49 [17674] - warn: [plugins/nodebb-theme-lavender] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset plugin="nodebb-theme-lavender".

28/3 12:49 [17674] - error: A Google Analytics ID (e.g. UA-XXXXX-X) was not specified. Please complete setup in the administration panel.
28/3 12:49 [17674] - info: NodeBB is now listening on: 0.0.0.0:4567
28/3 12:49 [17674] - info: NodeBB Ready

julian

@apaunganhote Thanks -- hopefully I am able to reproduce, otherwise I am afraid I wouldn't be able to triage this problem!

Edit: On that hash, I saw what you see, although this was resolved in the latest commits from master, so I'd just recommend pulling the latest code.

apaunganhote

Hello @julian,

Thanks for your help. I've got it resolved by pulling latest code.

Best Regards,

Aza Noriega

@julian said:

Can't reproduce on MongoDB or Redis.

I was able to reproduce that bug 2 days ago. Steps to reproduce were: Going to any page in ACP via ajaxify

I'm pretty sure, it was because of the error of requiring ../utils on the client-side. 'cuz these and some others bugs weren't appeared on cold-load, but on ajaxify they were.
I didn't interacted any NodeBB installation for approx 2 days, perhaps these bugs indeed were fixed by someone already. I'll check that today-tomorrow and will post here.

Aza Noriega

@Mega said:

I'll check that today-tomorrow and will post here.

aight
doesn't reproduced anymore on latest