Looking pretty spiffy. When is the official champagne ridden launch date?

@velderia said:

So... As far as npm install I'm having issues pretty much the same here: https://community.nodebb.org/topic/540/-nodebb-theme-lavender-lavender-theme-for-nodebb/73 (at the bottom) but I'm not sure how to reinstall npm on the stack or if that would even help.

I guess I should be developing Node.js on linux but so far I've been dual booting and I'm thinking about investing in like a Gigabyte Brix and having two monitors side by side (or even a KVM switch). I use Windows for graphics and I like Ubuntu for developing stuff and it's kind of my dream setup to begin with.

Edit: After rolling around in bed and drinking some coffee, I manually inserted the lavender theme in the node_modules folder, removed it from the npm-shrinkwrap.json file (created a npm-shrinkwrap-backup don't worry), and tried npm install again. It seemed to work up until "[email protected]" saying "no repository field" as a warning. I had to ctrl-C because it was literally stuck there. Now I have a bunch of nice modules installed in the node_modules folder but I'm assuming not all of them to be able to get NodeBB up and running.
Tl;Dr: npm is really not liking .tgz I think

Edit 2: I screwed up the entire NodeBB installation by typing node app too early and rushing everything. I'm going to take a break and probably upgrade the Ubuntu partition I have and do everything on there.

Hmm... What's the problem you're having exactly. I've been running nodebb on a windows bitnami mean stack for a long time without any issues whatsoever. Just make sure you pick the latest BITNAMI version (sometimes they hide them in favour of older more stable releases), install git and you're off to the races

@Schamper
Cool plugin but we have this error brewing in the console:
Uncaught TypeError: Illegal invocation
/plugins/nodebb-plugin-webrtc/static/js/lib/module.js?v0.3.2-2158-gbb9caa7:11

I second multichat and broadcasting

@trevor any time. Let me know when you've patched it up so I can give it another once over.

Ran into the same issue with this week's pull and npm install fixed it.

./nodebb upgrade is what appears to be breaking it.

@trevor got to agree with you on that. You always have to think of your end users here or at least give the option to dumb down the composer view. 98% of users in my forums are middle aged non-tech guys. They like boring kitchen sinks, big buttons to insert links and so forth. They also like one place to type. It's really not supposed to be a tech demo.

Double panes is a cool option that may be applicable to a certain demographic but it will be a small one.

Have to agree with this. Live preview doesn't do it for me either. Confusing to new users and somewhat needless. Like the old way for previews.

@trevor Finally got to try M4 out on mobile on your convoe site.

Few glitches on my Samsung Note 3 using chrome.

Hitting reply works ok but when the keyboard pops out the composer is entirely obscured. Kind of inoperable. Also has this rather confusing "Replying to What s.." in the middle which throws me off completely.

I like where you're going with the upvote buttons on mobile, the rest of them also need appropriate resizing i.e. quote/reply/share.

Do the standard widgets operate well with M4 or are the widget areas preset to what we see?

Screenshot attached:
https://s3.amazonaws.com/pushbullet-uploads/ujyTa0DhLSS-YOev95ePQjpvKI8u5OkwrNwHZVXO7WWx/Screenshot_2014-07-04-22-20-36.png

Keep up the good work sir. Just constructive feedback for you.

@fyhao Very cool. Add imgur and S3 support for pics and you have one glorified plugin to handle most of your media.

I'm totally impressed by this endeavour as it's something not far from what I've been contemplating for a while. Let me know when you get started and will try to contribute

Make your life easier, created issue #1744 on github for the FAQ update.

@julian said:

@nik Yes, that looks to be the problem then, set it to false and give it a whirl. (If you're using nginx, use_port should be false, in 99.99% of cases)

That did the trick. Thanks sir. Maybe update the doc in case it wasn't mentioned plainly enough.

@julian said:

@nik Your config.json file (If this is the source of the problem, then perhaps this is a candidate for inclusion into the NodeBB FAQ...)

use port set to true

@julian said:

Is your use_port set to false? If so, NodeBB will trust referrer IP as passed in via nginx. Otherwise, it will assume 127.0.0.1, as that is really where the requests are coming from

Being thick here, but where's that set?

@Scuzz said:

I have noticed this too, it does also display different IP addresses but everyone has a 127.0.0.1 too.

OK so it's not just me then. @julian want this logged in github? Can't recreate it on here but seems at least another member is seeing this.

Not a bug as I cannot recreate this on here, but on two of my nodebb instances the Recently logged IP parameter in the profile page is showing my localhost IP.

Running ubuntu 14.04, nginx 1.6 and my nginx directives are setup correctly. Funnily enough my access log file (generated by nginx) is correctly showing the client IP so it's passing through in the header BUT node bb is not displaying it correctly.

location / {
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://127.0.0.1:4568/;
proxy_redirect off;

Socket.IO Support

proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}

Which module is nodebb is reading the IP in the header? Will have a look.

@trevor said:

@a_5mith New composer. Hooray!
I need to update M4 then with all of these changes.

New composer is much better on desktop but alas still pretty samey experience on mobile.

For mobile I would literally strip away the header bar, the utility/kitchen sink bar (buttons too small to use anyway). Write /preview bar can go and move up the whole edit box to take up the top half of the screen.

A lot of wasted real estate. Also the mouse over edit/quote buttons don't translate to a good experience on mobile as most users won't know to click in that area.

@trevor Yep. In hindsight a mishmash of chat and PM might make navigation a pain. Keep them separate on a page and a PM widget would be excellent.

Italy is the one to watch today in the group of death.

@a_5mith good idea. That's sort of what I was thinking also. Maybe if feeling adventurous you can allow multiple recipients also from the user list.