BBCode and Markdown User Guide

ash3T

I tried to summary a clear cheatsheet of how to use BBCode and Markdown for my website users. I use flarum 1.1.1 and also installed these following extestion: BBCode, Markdown, Formatting by FoF.

I found this one pretty good.However, this following BBCode won't work in my site.

[chat-a="A" who="Me"]
[chat-b="B" who="Mary"]
[chat-a="话效果" who="Me"]

I already found Billy's guide.

Does anyone have come across a comprehensive guide for using BBCode or Markdown? Just in case, other flarum sites already got one for their user. I tried to use Rich Text Editor, but it has some layout issue after I turn it on.

By the way, I believe FriendsOfFlarum's Formatting won't influence on the BBCode and Markdown, right?

askvortsov

ash3T The challenge with BBCode is that the set of available codes differs from site to site, depending on which plugins you have installed. There isn't really a standard set of codes.

https://github.com/flarum/bbcode/blob/master/extend.php lists the codes available through the flarum/bbcode extension. Some other Flarum BBCode extensions exist. But if something isn't supported in any extension, a custom extension would be necessary.

As to the rich text formatter issues, sorry I missed your reply on that thread. If you enable rich text again I'd be glad to take a look.

010101

ash3T The BBCode you are mentioning is from a BBCode extension I no longer maintain. I don’t even have the code anymore. If you find someone who has the code let me know and maybe I’ll revive it.

jordanjay29

awslabspl This is getting off-topic for what OP has asked for help with. Let's stick to the topic or move to a new discussion about CSS symbology as it pertains outside of Flarum.

ash3T Billy's guide is pretty good, here's the original for Markdown (Litedown) you can reference as well, it should also update if things change in the future: https://s9etextformatter.readthedocs.io/Plugins/Litedown/Syntax/

ash3T

askvortsov https://github.com/flarum/bbcode/blob/master/extend.php lists the codes available through the flarum/bbcode extension.

I see.

askvortsov If you enable rich text again I'd be glad to take a look.
No need to say sorry. Thanks very much for willing to take a look. 😃

I got a user name : User
and password: 12345678

So you won't need to register a new account.

askvortsov

ash3T Do you have anything in your custom less that looks like:

.Post-body {
    overflow: initial !important;
}

It's either there or in one of your extensions, and that's the thing that's causing scroll issues in the editor.

awslabspl

askvortsov Quick note: !important direrctive is now deprecated in CSS.
Your code should be:

.Post-body {
    overflow: @initial
}

Char @ means !

ash3T

Thanks everyone to pitch in for whatever thoughts you got.

I am working on find out which extension has included this

askvortsov .Post-body {
overflow: initial !important;
}

I will share my findings soon.

010101 maybe I’ll revive it.

That's a good news indeed. I will let you know if I hear any feedback from that website maintainer.

jordanjay29 here's the original for Markdown (Litedown) you can reference as well

Thank you. Yes, I also looked for it on their site, but missed this Syntax page.

askvortsov

awslabspl Really? It's definitely bad practice but I hadn't heard that.

To clarify my post above, the code snippet in question is what's breaking your forum, and it should be removed. I'm not encouraging that be added.

awslabspl

askvortsov Really? It's definitely bad practice but I hadn't heard that.

TBH all this fuss around usage of !important rule/deprecation/being bad practice is just exaggerated A LOT........

010101

awslabspl Where have you seen !important is deprecated? I can’t find that. It’s “bad practice” but seems to still be a thing. I know I use it a lot. Because I’m bad. 💀

awslabspl

010101 Some CMSs ( IntelliA ) ASKS you to map CSS outrogatives like this:

[FSS]
F[!]: tploy('!', assright, '@');

Mozilla is VILLAIN. It wasnt for them, we wouldnt have to do it.

ash3T

Problem solved. Find it in

I will let the keyword extension developer know about it. 😀