If you set a background image, the image class can be used to change how it is stretched. See this article for options
Custom class is exactly what it says, it allows you to define a class that is applied to the category. In Lavender, this is used to position blocks in certain arragements (e.g. 3 to a row, 4 to a row, etc). In Persona, they are not used, but you can still used them if you wish to apply special styling to certain category rows.
Problem of Emoji.
Please check the url attribute within your config.json (within NodeBB root).
See https://community.nodebb.org/topic/3392/config-json-updated-base_url-and-relative_path-no-longer-exist/10 for more details on this.
I have previous 0.5.0-2 version of forum on Heroku. It works fine. When I updated NodeBB to 0.6.1 version it crashed with error. Any ideas?
2015-04-30T06:31:05.151177+00:00 heroku[web.1]: State changed from crashed to starting
2015-04-30T06:31:12.946261+00:00 heroku[web.1]: Starting process with command npm start
2015-04-30T06:31:16.159469+00:00 app[web.1]: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
2015-04-30T06:31:16.159494+00:00 app[web.1]: Recommending WEB_CONCURRENCY=1
2015-04-30T06:31:16.817890+00:00 app[web.1]: > firstname.lastname@example.org start /app
2015-04-30T06:31:16.817892+00:00 app[web.1]: > ./nodebb start
2015-04-30T06:31:16.854535+00:00 app[web.1]: sh: 1: ./nodebb: Permission denied
2015-04-30T06:31:16.873738+00:00 app[web.1]: npm ERR! Linux 3.13.0-49-generic
2015-04-30T06:31:16.878037+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2015-04-30T06:31:16.878041+00:00 app[web.1]: npm ERR! email@example.com start: ./nodebb start
2015-04-30T06:31:16.878043+00:00 app[web.1]: npm ERR! Exit status 126
2015-04-30T06:31:16.878044+00:00 app[web.1]: npm ERR!
2015-04-30T06:31:16.878046+00:00 app[web.1]: npm ERR! Failed at the firstname.lastname@example.org start script './nodebb start'.
2015-04-30T06:31:16.878048+00:00 app[web.1]: npm ERR! This is most likely a problem with the nodebb package,
2015-04-30T06:31:16.878049+00:00 app[web.1]: npm ERR! not with npm itself.
2015-04-30T06:31:16.878050+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2015-04-30T06:31:16.878052+00:00 app[web.1]: npm ERR! ./nodebb start
2015-04-30T06:31:16.878054+00:00 app[web.1]: npm ERR! You can get their info via:
2015-04-30T06:31:16.878693+00:00 app[web.1]: npm ERR! npm owner ls nodebb
2015-04-30T06:31:16.878696+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2015-04-30T06:31:16.899848+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2015-04-30T06:31:16.874577+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2015-04-30T06:31:16.875101+00:00 app[web.1]: npm ERR! node v0.12.2
2015-04-30T06:31:16.876089+00:00 app[web.1]: npm ERR! npm v2.7.4
2015-04-30T06:31:16.897668+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2015-04-30T06:31:17.925842+00:00 heroku[web.1]: Process exited with status 1
2015-04-30T06:31:17.938969+00:00 heroku[web.1]: State changed from starting to crashed
Thanks @nhl-pl I was using Ajenti V and the only reason I switched away from using it was do to the lack of documentation. I have used the traditional Apache based web server setups for many years and the Nginx server was all foreign to me so it was a challenge any time I wanted to add something or even troubleshooting issues.
It reminds me of when I was evaluating blog/cms alternatives for a Coldfusion based website back when Wordpress was less than a year old. I looked at Wordpress and Drupal and decided to go with Wordpress because at the time Drupal was too complicated and didn't have very good documentation. I switched to Drupal just before Drupal 7 came out and was amazed at the progress it had made and how much simpler it was from what I remembered. It is possible however, that it seemed easier because my knowledge base was a lot bigger.
That was a long winded way of saying I may revisit Ajenti eventually once I have learned more about the Nginx and Node.js way of server management.
Thanks ... Pops
I'm writing a bot that GETs a specific post from a category on my forum, and this category is only accessable by admins. Only problem is, GETting that post always returns a 401 Not Authorized response, because it's not open to users.
I've tried using auth=(username, password), Authorization: Bearer, even sending it in the GET params, but they all just return 401.
Any way of doing this?
just installed dev version 0.7, in console log that buildin plugins can cause err -)
installed sso steam in 0.7, plugin unstable, sometime working, sometime not working
is there compabality list for plugins? or compabality tests for plugins?