I'm running NodeBB v0.7.0-dev.
Edit: I've run git pull and upgrade. All problems have been fixed. Thank you a lot. 
I love how persona looks clean and nice but as others have said before, it would be great if we have an option to keep the old magazine-like homepage.
I'm currently having a banner in global header. My members think it'd be great if we could have a separate banner for each category. The image that we have for each category in the front page could also become a banner within that category. I know how to write codes for headers but I'm not sure where to place them to achieve the goal. Can anyone help me?
Hi NodeBB community,
I've just found out about nodeBB a few days ago, I absolutely love the modern and fresh feel of your forum as well as the features that come with it. I'm considering moving a sizable facebook community to nodeBB for better organization and archive. My concern is that the level of participation may go down since...well, visiting a forum is much more of a hassle than just checking facebook. Most of my members are facebook goers rather than forum goers. This would not be a problem if we can write a plugin that integrates nodeBB into facebook, gives members notification of forum new posts and messages on facebook newsfeed page. Do you think such plugin is writeable?
I am not a programmer, I would greatly appreciate anyone who can help me resolve this concern.
Thank you a lot.
Is the mobile interface okay for everyone? It is missing category icons for me and the menu button is not functional on my site, thought it works fine here.
I've reactivated all plugins on the new forum and everything still works.
I did the same thing on my old forum, reset all plugins then reactivated all of them and the problem is gone.
Perhaps the issue is in an old version of Vanilla or Lavender that was installed by default?
I did as you said and it worked. flip theme must have been the one causing problem. Thank you.
It turned out I was looking at the wrong default file, it's supposed to be in sites-enabled.
I filled in the missing s, and ran sudo nginx -t and got the following message
nginx: [warn] conflicting server name "domainname.com" on 0.0.0.0:80, ignored
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
my site is still not up on the domain
what is this conflict it's telling me?
======
Edit: Ok, so I've removed all files in sites-enabled and sites-available. Started over. Created a file in sites-available again. Then ln -s it to sites-enabled.
All [warn] lines disappeared. Configuration of nginx.conf was successful.
Then I tried sudo service nginx reload. Got the same message: reload: Unknown instance: 
=====
Edit: I've rebooted my droplet. Reloading nginx was successful. My site is now up on the domain.
Thanks guys!
I don't recall modifying that file.
I've purged and reinstalled nginx before so I don't think what I've done before purging would matter.
I did "sudo nano default" while in directory "/etc/nginx/sites-available/"
I can't find any "erver" without an s in that file. Am I looking at the right file?
Here's the content of that file.
##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##
# Default server configuration
#
server {
listen 80 default_server;
listen [::]:80 default_server;
# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;
root /var/www/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php5-cgi alone:
# fastcgi_pass 127.0.0.1:9000;
# # With php5-fpm:
# fastcgi_pass unix:/var/run/php5-fpm.sock;
#}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}
# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
# listen 80;
# listen [::]:80;
#
# server_name example.com;
#
# root /var/www/example.com;
# index index.html;
#
# location / {
# try_files $uri $uri/ =404;
# }
#}
@julian these are the errors i got
/etc/nginx/sites-available$ sudo nginx -t
nginx: [emerg] unknown directive "erver" in /etc/nginx/sites-enabled/default:1
nginx: configuration file /etc/nginx/nginx.conf test failed
I used sudo apt-get install nginx
nginx version is 1.8.0-1
Operating system is Ubuntu 14.04 x64
I got this error line
ln: failed to create symbolic link ‘./domainname.com’: File exists (possibly because I've created this file before, with the same content)
I did sudo service nginx reload and got this message reload: Unknown instance:
So I tried start in place of reload, this message appeared nginx stop/pre-start, process 7332
Yet my domain is not up.
http://domainname.com:4567 worked
but http://domainname.com returned an error page.
I've reactivated all plugins on the new forum and everything still works.
I did the same thing on my old forum, reset all plugins then reactivated all of them and the problem is gone.
Perhaps the issue is in an old version of Vanilla or Lavender that was installed by default?
On the new forum, the active plugins were
dbsearch
markdown
mentions
soundpack default
rewards essentials
theme lavender
theme persona
theme vanilla
widget essentials
Yes it works after I've tried ./nodebb reset plugins
Now none of the plugins is active.
@julian I've just installed nodebb on a new server and the same problem occurred
I upgraded persona but the issue still persists
