Status v1.1.0

[Jenkler]

In other words

Add this in your nginx conf (Server block) (After X-Forwarded-For)

proxy_set_header X-Forwarded-Proto $scheme;

if you are using Nginx before NodeBB in all cases?

[AOKP]

@Jenkler thats a good question. Maybe this is required for NGINX 1.10.1 and up.

[Jenkler]

At the moment i have

       location /
       {
           proxy_http_version 1.1;
           proxy_set_header Connection "upgrade";
           proxy_pass http://forum-mammagrupper-com:4567;
           proxy_set_header Host $host;
           proxy_set_header Upgrade $http_upgrade;
           proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
           proxy_set_header X-Real-IP $remote_addr;
       }

correct should be

       location /
       {
           proxy_http_version 1.1;
           proxy_set_header Connection "upgrade";
           proxy_pass http://forum-mammagrupper-com:4567;
           proxy_set_header Host $host;
           proxy_set_header Upgrade $http_upgrade;
           proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
           proxy_set_header X-Forwarded-Proto $scheme;
           proxy_set_header X-Real-IP $remote_addr;
       }

Right? Is it safe to always have proxy_set_header X-Forwarded-Proto $scheme; set?
If something else looks crappy, feel free to point it out

[SuperMike]

emoji could not active after upgrade to 1.1.0

I am upgrading from 1.0.3 to 1.1.0, everything goes well except emoji plugin. Active button is unavailable, I clicked update files, but it's processing with endless.

[Jenkler]

This is an old bug

1. Klick update
2. Klick activate
3. stop Nodebb and start Nodebb from the console.

If it now works, check the file perms (Nodebb user must have write access to everything). Later on you can restore your perms after updating and enable of emoj

My dev is updated now and no problems yet. Will continue to test ... I be Back !

[scottalanmiller]

We updated at MangoLassi and all seems well.

[Jenkler]

Works on all my 3 dev sites. Seams good !

[torn2]

Are there some notes on what was changed for 1.1?

[mechanix]

@torn2 yeah, a changelog would be great

[frissdiegurke]

You can view the list of closed issues on github for a detailed insight.

[rod]

A possible issue. I have created two new sets of topics and posts in v1.1.0 yet the category analytics do not indicate that. They continue to show zero new posts or topics. Are other people having this issue?

[julian]

@rod It may be that the analytics haven't persisted to the database yet. They're stored temporarily in memory and pushed to the database periodically, so if you restart NodeBB in the interim, those analytics may be lost to the ether

[rod]

@julian I will refrain from restarting v1.1.0 for a few hours now to let the software do what it is supposed to and, yes, I have been stopping and starting 1.1.0 many times as I change and look at things in my dev environment.

[Jenkler]

If I create a new topic the category analytics changes at the category listings as it should. Anyone else having the same issue as @rod!

@rod what db type do you use, mongodb?

@julian Are there anyway to recalculate the stats if lost?

[rod]

@Jenkler I use Redis. And as of my testing today no stats are being collected for new topics or new posts (well, as reported from the analytics tab under ACP > Manage > Categories > analytics tab )

[rod]

@Jenkler @julian Err, I spoke too soon. I am seeing analytic data now!

[Jenkler]

Ahh, "ACP > Manage > Categories > analytics tab" works fine for me 2. (MongoDB). I thought you ment the category listings

In other words, still safe to upgrade, wee