@briankb-0 NodeBB FTforumW. 👍

@nebulon said in I swear the favicon on NodeBB was stated to be fixed:

Can you refresh your browser cache? Seems to work here for me.

That did it! 😂 Thanks.

Looks like this is fixed (and also the header bar in the category view, as well)

Indeed I see that also as the last remaining artifact from the missing translation. I rebuilt and restarted nodebb but that didn't change this at least so far.

@girish ****ing amazing! Light mode made me blind to it! 🐶

Could you make an already happy man any happier! 😹

f65208a6-a0b2-4b6a-87ce-62c7c39a4794-image.png

♥

@yusf said in Images on NodeBB:

@jdaviescoates said in Images on NodeBB:

you can't upload images here

Sure you can! 8F330363-A097-4699-95FC-AAE10C831DA7.png

@vjvanjungg said in Images on NodeBB:

the vertical image icon next to the smiley face is good for uploading img, i saw it yesterday maybe there is a way to disable it @jdaviescoates

Heh, thanks, not sure how I'd missed that! 😛

Have edited my post above to add a D'Oh! 😄

thank you guys, very helpful

It's still fine on my small screen

alt text

@bangden07 It looks like the plugin installed. Just restart nodebb and you are set (in Console -> Restart).

@girish Thanks!

@nebulon There is a configuration UI, you can't use the plugin without it. I'll reach out to the Node.BB community for a deeper look.

A bit of thread necro, but I had the same problem. It appears that NodeBB is correctly configured, BUT in the Cloudron portal, by default, the "custom mailbox name" flag in the advanced app configuration settings is set to off. Thus, the email credentials correctly entered into NodeBB led to an account that, by default, was deactivated in Cloudron's mail server.

For others who stumble here:

From your Cloudron control panel, click the Configure tool (the pencil overlay over the app icon). In the Advanced tab of the pop-up, ensure that Custom Mailbox Name is checked, and that the name matches the name as configured in NodeBB's email control panel. By default, it's nodebb.app@.

Problem solved, although whether it immediately resolved or whether it fixed when I rebooted Cloudron to install security updates about three seconds later, well .... 🙂