Forum

I see, indeed, then we should update checkTime if $old->value != $new->value, right?

Logs clearly show that ProjeQtOr was not correctly installed, there are missing tables (parameter, resource) in the database. I suggest you delete yo...

Understood. Function br2nl() also needs to be added to projeqtor.php Thanks!

Hi, how did you fixed #2560? I want to try to backport the fix to 6.0.8 while waiting to have time to upgrade to 6.1.x. Thanks!

What about hiding these columns by default and if we really need them, we can add them despite the performance issues? I discovered the Risk manageme...

Hi, Just to notice you I made some improvements to the "select multiple" feature you already included:(remember to only copy the changes as your br...

Actually, the "days before warning" was supposed to highlight jobs that should have begun, not be done, according to the specifications. However, they...

I didn't see this, thank you!

Thank you for the fix! Can you also look to make the width of the name automatic instead of fixed to 300px? See screenshot. We can't see the full na...

Indeed, this feature is big enough to need a documentation. First, I developed this feature apart and not on top of checklist because it was incomp...

Found out how to fix the issue (or how to convert the cp1252 data stored as UTF8, as UTF8MB3). Note that it will NOT work if you have a mixed cp125...

I can confirm I installed ProjeQtOr on version 4.5.7 and never received the $enforceUTF8 parameter. I installed ProjeQtOr on a CentOS machine and the ...

After investigating this issue, I discovered that you were actually storing cp1252 data into UTF8 tables. To be more precise, you store "default char...

I think that's how my users want to work. However, they don't want to go through a lot of fields that would require 50-100 days of development, they ...

I'm using the "Print" button, it is the 3rd button in the Follow up -> Planning screen. It lets me choose my columns to print and the printing for...

All fields can be truncated if they are longer than the defined width so actually, it would be better to have columns with no specified width so colum...

But what realy bothers me, is that these tasks won't participate to Project Pogress... Indeed, I didn't think of this side effect. Would it be better...

I came up to another possible implementation while looking at the algorithm behind: By default, progress is inputable and when real work != 0 or left...

It shouldn't be needed to put charset in SQL update scripts, the DBMS will guess it from the database charset and collation. Plus, the "utf8mb4" is on...