Hehe, it looks like it breaks things. I wanted to try out to see if everything worked. Surprisingly, it worked on the preview! I used this markup: pastebin.com/raw.php?i=yGe35n49 and it looked like this: i.imgur.com/nldhJT8.png

Hmm... I wonder which of those things broke it.

I don't know, but "call to undefined function" could mean that some file is not being included. I'd recommend searching for "function parse_inline", and including the file that defines it. It may just work.

(also, this is a good reason for using require instead of include, because IIRC include means that it won't complain if it's not there. Also, require_once makes sure not to load the same file twice).

I don't know what you did, bro. XD
I copied and pasted your pastebin into the wiki and forums, and it worked fine. Observe...

Edit: Found the problem.



You missed a line break. Yes, it really does break the page when you do that, lol. XD

The line after Item 3 needed two linebreaks before it. I'm not 100% sure why. Looking into it now.

Edit 2: For SOME reason, it seemed to have ignored your line break altogether. I messed with it a bit, and it is now suddenly working with one line break rather than two. However, if I remove the line breaks, I get the same error, so that was DEFINITELY the problem.

Edit 3: AHA! I got it. When you have a line break, be extra careful not to press spacebar. The line may then LOOK empty, but it's totally not, so it doesn't count as a linebreak!

hypnohub.net/#auto-linked-url

bold
italic

never enough bold and italic

[[help:rules and policies]]

{{kinkyloli}} posts

{{loli ahegao}} posts

search by user: {{user:kinkyloli}}

post #7547

forum #273

comment #344

pool #44

Some spoiler text


h1. An Important Header


h2. A Less Important Header


h6. The Smallest Header




Lists:

* Item 1
* Item 2
** Item 2.a
** Item 2.b
* Item 3

LOL


Hm, maybe if one filters the input before letting the thing do its parsing, it won't break.

To do this, you could look where the post is parsed, see what's the variable that contains the possibly-overwhitespaced post, and (supposing it's called "$post")



to clean these.

wow I did this error today, is impressive XD