Looking for the experienced Flarum developer ASAP

NikolayBezhko

Hey guys! I've almost got the Flarum work for our community, you can take a look:
http://forum.mcfly.aero/tags

But still there are some issues. Like this. I'm trying to create few posts. For example:

[TAG] Meta
[TOPIC] About the community

[TEXT]
It's like Quora, but exclusively about flying cars.

We want to build a space on the internet where flying cars enthusiasts and anyone who's interested could talk, learn, exchange ideas and meet cool like-minded people.

We are Frequent Flyers — people who care about flying cars, worldwide.

We want to improve the world collectively by making flying cars an everyday thing — the sooner, the better.

Join the conversation. Have a good time.

But I got an error:

"Oops! Something went wrong. Please reload the page and try again."

I click "debug" and get this:

500 Internal Server Error
POST http://forum.mcfly.aero/api/discussions
null

Though I can post something like this:
http://forum.mcfly.aero/d/21-asdasdasd

And I see no difference why this is posted and other not.

I'm looking for someone who will help me with some troubleshooting. I can pay!
I can even pay you with McFly tokens for our future flights. Or boring old $ ?

Please leave contacts if you can help.

Cheers,
Nik

luceos

Summons @clarkwinkelmann

clarkwinkelmann

You could probably troubleshoot that via the community, but I can take a look in-depth if you want. You'll find my contact info here https://clarkwinkelmann.com/flarum ?

NikolayBezhko

clarkwinkelmann

Thanks Clark! Oh, you know, we've found the source of the problem 5 minutes ago.
It happens if we use "—" and "–" symbols. If you use "-" symbol then everything is okay.

clarkwinkelmann

NikolayBezhko ?

Anyway feel free to contact me if you need custom help !

clarkwinkelmann

In case somebody else encounters it, here's what the issue was and how to solve it.

The 500 null error is in fact a timeout of the TextFormatter Parser. The server logs contained something like:

[date] [:error] [pid xxxxx] [client xxx.xxx.xxx.xxx:40900] PHP Warning:  mb_strpos(): Offset not contained in string in /var/www/flarum/vendor/s9e/text-formatter/src/Plugins/Litedown/Parser.php on line 240, referer: https://example.com/
[date] [:error] [pid xxxxx] [client xxx.xxx.xxx.xxx:40900] PHP Warning:  mb_strpos(): Offset not contained in string in /var/www/flarum/vendor/s9e/text-formatter/src/Plugins/Litedown/Parser.php on line 240, referer: https://example.com/
[date] [:error] [pid xxxxx] [client xxx.xxx.xxx.xxx:40900] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/flarum/vendor/s9e/text-formatter/src/Parser.php on line 357, referer: https://example.com/

The issue is that mbstring.func_overload was enabled in php.ini. This replaces calls to strpos with calls to mb_strpos and breaks the Litedown markdown parser ? This feature is deprecated and usually disabled by default.

So just set mbstring.func_overload to 0 to disable that "feature" and you'll get the parser working again.