Wiki refresh problem when using BBCode

Stefan Münz

Sat, 15 Dec 2018 13:08:39 +0000

I want to report a problem with Hubzilla wikis when BBCode is chosen for page formatting.

Currently I'm working on a "refugee directory" for users from GooglePlus who have moved to the fediverse:
GooglePlus-Refugees: Home (public read access)
This wiki is using BBCode. When you click on one of the tabs "source" or "history" and than switch back to the "view" tab, the content isn't rendered correctly. Instead HTML source code is shown. After a page reload in browser the page appears correcty formatted again.
I could reproduce this in Google Chrome 71.0 and Firefox 64.0 (no others tested).

I would like to announce this directory on GooglePlus and encourage users from there who have moved to fediverse to tell me where they have moved to so that I can add their entries to the directory. But I don't want to present a wiki to them with that buggy behavior (instead I want to make users finding this wiki curious about the extended features of Hubzilla).

I hope that this can be fixed easily.

wiki bug

show all 5 Comments

Sat, 15 Dec 2018 15:09:49 +0000

Just tested from mobile using Brave (Chromium 70 engine) and am unable to reproduce the reported behavior.

Oddly, Chrome mobile (also Chromium 70) does not trigger the refresh of the view tab unless you change focus to another field (like the commit message input) though Brave does.

Quick question for @Stefan Münz - the HTML you are seeing - are you typing HTML in the edit window? Or are you typing BBCode and it's showing up HTML until a refresh?

Stefan Münz

Sat, 15 Dec 2018 16:08:10 +0000 last edited: Sat, 15 Dec 2018 16:15:19 +0000

I'm only typing BBCode in the edit window, no HTML. As far as I can see only links typed in wiki syntax are affected. If I create external links using the BBCode syntax [url...]...[/url], they are rendered correctly. But if I create a wiki link using [[name-of-the-page]], it is rendered as HTML when switching from one of the other wiki tabs to "view".

I add screen shots to make it more clear:

And here is the effect I try to describe:

And then, after a page reload in browser. everything is fine again:

Sat, 15 Dec 2018 16:38:32 +0000

Ah... I see what you're saying... now that I have a reproducible test case, maybe I can find a solution.... maybe ;)

Stefan Münz

Sat, 15 Dec 2018 16:45:44 +0000

Fine, and thank you for the feedback.

Mario Vavti

Sat, 15 Dec 2018 17:22:39 +0000

Thanks, this should be #fixed now.