• Status Closed
  • Percent Complete
  • Task Type Bug Report
  • Category Backend/Core
  • Assigned To No-one
  • Operating System All
  • Severity Critical
  • Priority Medium
  • Reported Version 1.0 alpha1
  • Due in Version 1.0
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray
Opened by jordanmendler - 12.09.2015
Last edited by peterdd - 02.03.2016

FS#2051 - During upgrade need to set reasonable defaults for any missing prefs

Since there are new prefs adding in, if anything is missing during an upgrade, we need to set reasonable defaults to avoid error messages. Here are some I see are missing:


Closed by  peterdd
02.03.2016 19:50
Reason for closing:  No customer feedback
Project Manager

Where do you see the error messages? I haven't seen such error messages with in my tests yet.
(even upgrades from a fresh installs to current master)
Which php version, which error reporting level?

  • max_votes_per_day: may full replaced by the votes_per_project setting, which is more userfriendly and "democratic" in the meaning of that users have same power of voting.
  • (maybe a new task) emailNoHTML setting: Naming a setting variable should be avoided to avoid confusion. Especially with the background, that double negation in a sentence has different logical meaning in different languages ( )

Could be changed to "emailHTML" (with switched values of course)

We send emails now in every case also as text too. So emailHTMl=1 would be the option for sending also as HTML.


Everywhere :-O

I will send some screenshots tomorrow. Also will be making some commits then as well.

Project Manager

Which env/php settings?

Jordan, I asked you before but please, please:
If we setup that travis-ci for Flyspray/Flyspray and write good tests, we could detect such things in future automatic.

I have set travis-ci for peterdd/Flyspray, but we need it for Flyspray/Flyspray and only you can do it for us.

If you need help for that I can do some screenshots how to set it up.

One of the dreams I have for flyspray is having complete tests that run with every merge to master.

Do automatic test (flyspray install / flyspray upgrade / different use case tests):

  • on different php versions X different databases X different (env) settings

And this is possible with the travis-ci on github.

There are even exists tools for travis-ci for testing with a real web browser (just read about it, never did yet) selenium ..


PHP 5.6.12+dfsg-1 on debian unstable.

I went ahead and activated travis-ci for flyspray site and website, atleast on the travis side. Haven't used it before, but it should be on now if you to do steps 2 and 3 from

Project Manager

travis-ci now working for Flyspray/flyspray. Thx.

Project Manager

Jordan, you marked this as critical. Could you please provide the promised screenshots?

I think next step is doing preparing the FS1.0 beta release.


Available keyboard shortcuts


Task Details

Task Editing