This plugin has compatibility issues with Macintosh keyboards.
Normally, "Alt+L" creates the @ character (which we need for pinging users @frissdiegurke), however due to this plugin "Alt+L" inserts a list into the posting, which is nice but definitely not what I want right now (desperately copy-pasting @ from outside nodeBB sucks).

@psychobunny Did you have any time to look into this?

@julian said:

That's not a bad idea... we just don't have plans to split the sites yet.

I understand that you don't want to split up anything, but how about mentioning the OpenSource version at all?
Right now, when I go to nodebb.org, the only chance to see that there is a free version that I can roll out myself is to know what the github logo looks like and then scroll down all the way to the bottom to spot it there (very small, barely visible).
Additionally, if I have AdBlock Plus turned on, these social buttons do not appear at all.

I perfectly understand that you want to earn money and therefore want to focus the page around your hosting service but I think that you could significantly cut the amount of requests from people who heard about a cool OpenSource forum and who now struggle to find a link to download it.

@Nicolas
After a user created a longer posting with multiple spoilers, the forum stopped working properly for me (unresponsive buttons / missing pop-up menus).

I played around with the posting that was made and figured out some problems related to the spoiler plugin.

First, using a list before a spoiler containing a list breaks the spoiler.
Here's the code:

- asd
- asd
- asd

::: 
This is a spoiler containing a list:

- asd
- asd
- asd

::: 

producing the output

• asd
• asd
• asd

This is a spoiler containing a list:

• asd
• asd
• asd

[empty spoiler tag]

This part on its own does not yet break anything but just creates a badly formatted posting.

Second (probably somewhat related), different kinds of lists inside the same spoiler will break the next spoiler following.

Example code:

::: 
- asd
- asd
- asd

1) asd
2) asd
3) asd
::: 

::: 
- asd
- asd
- asd
::: 

results in

[spoiler containing the part between the first spoiler tags]

• asd
• asd
• asd
  [empty spoiler]

Again, this problem alone does not result in a broken nodebb but just in malformatted output.

Finally, I reduced the problem to a situation when both of the above examples are combined.

A posting like this

::: 
1) asd
2) asd
3) asd

- asd
::: 

- asd

:::
1) asd
2) asd
3) asd
::: 

will break nodebb. The problematic thread / posting becomes impossible to delete without deactivating plugins because the moderation tools cannot be displayed.

@psychobunny said:

Ping me again if I haven't looked at this by end of next week

I guess it's time for a ping then ;).

Thanks @julian for pointing out something that seems to be quite obvious, yet I did not try to do that before :).
Honestly, I didn't even know that dragging the composer is possible.
I have absolutely no idea why it got resized automatically in the first place, even across multiple browsers that I tried, but it seems to work now. I'll report back in case the resizing happens again.

Hey guys,
I upgraded to v0.9.1 and thought that everything went fine, quickly wrote an announcment for my users and then went to bed. Today I am confronted with multiple responses to my announcment stating that essential functionality of the forum is broken.

• Pressing the reply button does not open a text field but only shows a small red plus button in the bottom right corner. Clicking this button twice or pressing the reply button again then takes my to the response text field.
• Editing a posting is not possible at all. The red button is shown but no matter how often I click it or the edit menu entry, nothing happens.
• After one response is made, the reply button stops working, too. I have to completely reload the browser to be able to reply again..
• Same holds for chats windows. After any action I made on the page I cannot open chat windows.

I tried ./nodebb reset -p which restored almost all functionality. I am now able to reply and edit as expected with just nodebb-plugin-composer-default activated.
However, when toggling between the half- and the fullsize response field the page will (after a small number of times where it works as expected) only show the fullsize variant. No matter what I try (reloading the page, logging in and out, even restarting the whole forum) I cannot bring the halfsize variant back.

I then tried ./nodebb reset -a which failed with the following error message:

$ ./nodebb reset -a
8/12 16:26 [25051] - info: [database] Checking database indices.

/path/to/nodebb/node_modules/mongodb/lib/utils.js:98
    process.nextTick(function() { throw err; });
                                        ^
Error: Cannot find module './src/widgets'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at resetWidgets /path/to/nodebb/src/reset.js:107:2)
    at/path/to/nodebb/node_modules/async/lib/async.js:713:13
    at iterate /path/to/nodebb/node_modules/async/lib/async.js:262:13)
    at async.forEachOfSeries.async.eachOfSeries (/path/to/nodebb/node_modules/async/lib/async.js:281:9)
    at _parallel /path/to/nodebb/node_modules/async/lib/async.js:712:9)
    at Object.async.series (/path/to/nodebb/node_modules/async/lib/async.js:734:9)

Can anyone help me to bring my forum back to a working state?
How could I quickly restore the forum to an older version so that I can get it back online for my community?

Edit: By activating all plugins one after another I found that all that reply / edit problems probably come from a custom plugin that we used for text replacement in postings. Which essentially leaves the error message from above as well as the fullsize response window as the only problems I am facing right now.

Do you have a reverse proxy set up so that you can access your nodeBB directly without specifying a port number?
In that case the proxy should handle the certificate stuff as well.

@psychobunny Is there any way to get this working with a recent nodeBB installation?
The plugin installs just fine, however featuring topics via the Thread Tools menu does not do anything.
Thus the widgets stay empty and do not show up (nodeBB log does not show anything).

Imho, together with the custom homepage plugin this would bring nodeBB to be so much more than just a forum. For me this would create the possibility to host an entire community just on nodeBB. No need for a complex blogging or CMS software :>.

I really love the plugin, installed it and it works fine for me!

However, when writing an announcment for my forum that spoilers are now supported I realised that I couldn't show the usage by wrapping the spoiler into a code block.
The spoiler was rendered anyway.