Bug Reports

thank you.

@julian lost all data 😞 but all working fine now.

@nexed Can you reset all of your plugins for now and see if that helps? ./nodebb reset plugins

I also this problem:

Looks like I have an issue with some MIME types for images. Not quite sure what is going on though to be honest. So... if I use the refresh button in my browser, the avatars are the correct size. After I click around on NodeBB, the avatars are massive.
Big Avatars Screen
MIME

Has anyone seen this before?

Environment:
Ubuntu 12.04 LTS 2.6.32
Redis version 2.8.9
NodeBB v0.4.3
Default fresh install, I had the same issue on a CentOS 6.5 box.

I too got the same error recently when I tried to install Emoji plugin. I had to reset all plugin as mentioned in above post and it took almost 5 restarts to get my site back online. As for why it is happening, I don't think I am the right person to answer it.

I can for the first time say..

Upgraded without any problems. 2 minutes in Terminal and I was rolling in .4.3 🙂

But that's more on me, than on you guys.

Thanks for the tip. Worked without glitches. 👍

@julian said:

@Dazzuh If you're running a flavour of Linux, best bet is to install using their package manager... Ubuntu? CentOS?

oh I tried, according to ubuntu package manager I was already up to date.
Already figured it out though. Thanks for your help.

Hehe -- glad you figured it out 🙂

No clue why npm is sometimes serving old versions of our themes...

@a_5mith Cool. Thanks for your help

@nexed said:

@Xiph

Since there is currently no easy way to migrate over from redis to mongo... running the install on an existing installation is necessary to populate mongo (even just the administrative user)... So running setup is the only option to switch over at this point. Hence the problem and the reason I posted.

Alright, but the fact remains that before running ./nodebb setup, npm install has to be run first. Because npm install makes sure all of the requirements are met, there is no reason to perform those same checks again in ./nodebb setup.

Considering there is currently no "proper" way to switch between databases, you are right in saying that ./nodebb setup needs to be run to populate the database. However, it will not move over the already existing data, hence it would be easier to just install another copy of NodeBB with your new database settings in another folder and copy over the old node_modules folder from the previous installation afterwards. This should also solve the error you are having.

@julian yes fixed!

If you run

it specifically updates both Vanilla and the current default theme, Lavender. so after a git pull, make sure you run that command and you should be good 🙂

@psychobunny That's done the trick, no csrf error when enabling emoji-extended. 👍

@a_5mith ah yes, display: none works better! thank you!

@psychobunny said:

Moved this to Bug reports, it was originally in General discussion. More importantly it seems to work 😛 Gief repro steps if not 🙂

Yeah wasn't a whole lot to repro, maybe just a weird anomaly who knows. I'll watch and mess around to see if I can do it again while watching.

@psychobunny the config.json not being set. Not sure how I missed that. Thanks for the reply!

@baris awesome!

@julian said:

Subfolder install ACP inaccessible

should also add in login redirect issues with subfolder