Flyspray - The bug killer!

  • Status Closed
  • Percent Complete
  • Task Type Feature Request
  • Category Installer and Upgrader
  • Assigned To No-one
  • Operating System Linux
  • Severity Medium
  • Priority Very Low
  • Reported Version 1.0-rc9
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 1
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by Olivier Humbert - 30.08.2019
Last edited by peterdd - 08.12.2019

FS#2566 - syntax_plugin after an upgrade from -> 1.0-rc9

database: mysql - version: 5.5.62-0+deb8u1
php version: 5.6.40
Debian (probably a Buster one)

Steps done to create the problem: I used to run a version, and today, I decided to go for a 1.0-rc9 update.

Expected behavior: all works

Experienced behavior: most works, but not all

Details: after the update, I had weird display behaviour where the task weren’t displaying breaklines:

while the code was supposed to have breaklines:

Then, I’ve read: which leads me to:

Then, I’ve changed




in flyspray.conf.php, and now all is fine:

I’m already enjoying bold/italic/code/… very nice addition from, thank you!

That said, something which looks to be an issue from my (user) perspective is that when upgrading from → 1.0-rc9, I wasn’t asked for a “syntax plugin” thing and it looks that the only way to change it so far is to CLI-edit the flyspray.conf.php file.

I would strongly suggest to make this an option in the admin panel.

Thanks for flyspray that I’m using fo my librazik project.
All the best,

Closed by  peterdd
08.12.2019 03:00
Reason for closing:  Fixed in devel
Additional comments about closing:  

nl2br() used again for syntax_plugin 'none'

First (nonfunctional) link should have been:

Project Manager

Link fixed.

Are you sure you run PHP 4.3.9 on a Debian 10 Buster?
Flyspray 1.0-rc9 current minimal support is PHP 5.4 and my Debian 10 (Buster) vagrant boxes have PHP 7.3.4-2 by default ..

Well, the reason why there is no easy option for toggling syntax_plugin setting just in admin panel is that they work quite differently behind the curtain and would require complex conversions to do it correctly. (and cannot be reversed in some cases like nested html tags to dokuwiki back to html not possible)

none and html just store the descriptions and other text fields (hopefully full) sanitized when saving in database and later outputed.
dokuwiki syntax_plugin instead is stored ‘as is’ in database, parsed later and final html rendered before output and is more flexible to extended (like adding a user mention plugin or other things)

Having these different systems in Flyspray is not optimal, and there also exist some related tasks like FS#2052 .

Link fixed.

Thank you.

Are you sure you run PHP 4.3.9 on a Debian 10 Buster?

My bad, 4.3.9 is the version of phpmyadmin. PHP is 5.6.40-0+deb8u5 .

Thanks for you explanation.

I'd like to add a question then: how is that possible that was fine, then the update to 1.0-rc9 with


gave me a badly formated text in the tasks? Shouldn't it be considered as a bug maybe, what do you think?

Project Manager

The TextFormatter::render() now uses nl2br() when syntax_plugin is '' or 'none'.

The call was there, but commented out. This was probably a leftover from former devs who thought html/CKEditor will be the only option.


Available keyboard shortcuts


Task Details

Task Editing