Bug Reports

@julian Will do, assuming what I suggested in the issue will actually work. 😆 Currently shopping for a new PC. the pain, but will do it soon.

@dylenbrivera said:

@a_5mith What I meant by +1 and -1 is that the guest counter could be at 12 and then flicker from 11 to 13.

Oh I see in that case then

@a_5mith said:

A guest counts as any active connection, so could be google. Or a spammer, or any other range of things.

You could have more than one bot from the same company viewing your site (it's quicker to do this)

@psychobunny I believe it has something to do with CentOS or running Plesk/cPanel as I have not for the life of me been able to make it work properly, even with that guide. We are switching to a Debian server soon without Plesk or cPanel so hopefully that will render the issue solved.

@julian said:

People in the past have tried pre-generating reset links and sending them out, but because of the expiration, you end up with a bunch of users who try clicking the link after it times out, which obviously doesn't work.

I would be interested to know how they did it!
I guess it is possible to change the 2 hours expiration?

Any hints?

@psychobunny Applied fix, 86% solved.

URL is now q&ampa. Assuming because & gets run through the next line in your fix, which removes the ;.

@baris I wouldn't until the widget issue is looked at. 🙂

@Albus You pay the hosting bill, change it however you like. 😆 That's what I did anyway, I went from this:

this

to http://35hz.co.uk

But I made them slightly happier by adding the lightbulb icon below the page width changing button. So they weren't too shocked,

@julian No wait julian - something's wrong. Look here the tags work!

http://146.185.184.104:4567/category/4/blogs

neV8ecf.png

@a_5mith NodeBB should properly support Waterfox 28 when we upgrade to socket.io 1.0.

Still waiting on Automattic/socket.io#1630... grrr

I just upgraded to the current git version of nodebb after I noticed that upgrading to 0.4.3. removed the Reply and New Topic buttons (no idea why that happened). The upgrade fixed that, but now when I try to create a new topic I just get the message "Category doesn't exist" when I click Submit (reply works though).
I'm running nodebb on Windows using mongodb. I had problems with categories before but managed to fix it manually, see https://community.nodebb.org/topic/1434/category-disappeared

@julian said:

I imagine if href is missing, this.href would be undefined, no? smile

No. 😛

I was surprised that it's been an empty string that got checked instead of undefined too, but it seems I'm to adapted to jQuery ^^

This is because you use the DOM-element rather than jQuery to get the href:
document.createElement('a').href === ''
$('<a></a>').attr('href') === undefined

Haha, and now I have a legit excuse not to update the level driver... (at least until connect-level is updated :P)

@vivek-tailor Yes but if you re-activate those plugins, you will have this issue again.

Did you see which plugin caused the crash?

Duplicate posts are showing up:

duplicate.jpg

npm install installs everything in package.json but we have different dependencies based on what database you pick during node app --setup (redis, mongo, level). Usually just running npm install is enough but in this case there were changes to the database dependencies.

@frissdiegurke Good point, that's never been an issue for us as we always use the defaults for those settings.

I'm re-designing the install step at the moment, so will take this into account.

@psychobunny Hmm, updated, cleared the cache etc, no difference. 😕

On a sidenote, running git pull gives me an error about node_modules/cookie-parser not being on npm.

Sorry, I think I look at wrong number, there's no version 0.6.x.... still 0.4.3

@baris Thank you it's fixed 😉

Fixed as of https://github.com/NodeBB/NodeBB/commit/5ec289eee2c44f4dd49e7b2884d27dd1acb20d5c.

The problem was I was deleting tags that no longer had topics but was doing it in the wrong place. If a user couldn't see any topics the code was deleting the tag. I moved it up to actually check the tids and not the topics the user can see.