But looking at the last commit on git, it seems to be some updates to translations. Could that be related to a Portuguese installation?

github.com/LimeSurvey/LimeSurvey/commit/...a3d53efcb3b88adac371

github.com/LimeSurvey/LimeSurvey/commit/...239273633508768f9da9

Found a related bug:
bugs.limesurvey.org/view.php?id=19332

with a possible fix:
github.com/LimeSurvey/LimeSurvey/pull/3686/files

Could that be related to a Portuguese installation?

There is no real such thing as "Portuguese installation". It is all the same installation, just the language settings are different. So if it would be a language issue, it could be easily checked by switching to for example English and see if it happens.

PostgreSQL is always risky, because less people test Limesurvey on Postgre. In theory it should work, because the framework works with Postgre, but you know how things are in software development, you need to test everything to make sure it works. I would guess that 90% of all installations are on MySQL and similar, then there are a few on MsSQL and some on Postgre. Both are a lot less tested and thus those things can happen.

I personally would always try to run Limesurvey with MySQL, just because it runs smoother from what I can see, for above reasons.

I know there isn't a Portuguese installation. That was just a figure of speech, we can change a survey to English to try it, that did work in the past, but this issue with the latest release was affecting just right after login.

I was just pointing out the fact that in the latest release, we had some translations updated, and one of them was in fact the Portuguese one.

I had to downgrade the version so we can use the platform.


Sure, we can change it again to MySQL, is there any migration script or plan for that?

Changes in any language just means that there has been an update to the language file, mostly because more strings have been translated or translations have been updated. This should not impact the functionality of the installation, just have more parts translated. Of course, issues can never be excluded 100%, but I think it is pretty safe to say, that this should have nothing to do with the update for the Portuguese language files. I think at the moment there is little you can do than wait for the bug report to be worked on.

Hi mferraz,

> I had to downgrade the version so we can use the platform.

to which version did you downgrade and how did you do that? Same procedure as upgrading to a new version?

Hi.

Exactly, I've downloaded directly from github, from the last week commit: github.com/LimeSurvey/LimeSurvey/tree/52...eccfb4eaa900d1dde9f4

Check you are providing a valid value for the qid parameter when creating a new survey. The error suggests an invalid input syntax for type integer, indicating that an empty or non-integer value is being used where an integer is expected.

Ex,

UPDATE lime_question_l10ns SET qid = 1 WHERE qid = ' ';
 

JiyaHana wrote:

Check you are providing a valid value for the qid parameter when creating a new survey. The error suggests an invalid input syntax for type integer, indicating that an empty or non-integer value is being used where an integer is expected.

Ex,

UPDATE lime_question_l10ns SET qid = 1 WHERE qid = ' ';
 

Nonsense, dumb advice ... done with chatGPT?

Just do not set qid, since it's a serial for pgSQL, AUTO_INCREMENT for MariaDB and IDENTITY for Mssql

Hi,
any news on this? Not being able to use multiple-choice-questions is very inconvenient. As I see this, my options are:

• downgrade to a version where this bug does not exist. As it appears this must be a version before 6.1.x and I'm afraid of downgrading so far back because of possible database changes on the way from 6.0 (or before) to 6.4.xx
• try to apply the mentioned fix ( bugs.limesurvey.org/view.php?id=19332#c79146 ), although this did not pass some tests

Any advice on how to handle this is welcome!

mmilinovsky wrote:

• try to apply the mentioned fix ( bugs.limesurvey.org/view.php?id=19332#c79146 ), although this did not pass some tests

If i use PG : i surely do this.
And try to help on the test (i clearly not understand too …)

Hi.

I guess I will give up this fix, and start a new LS installation from scratch.

Hi mferraz,

as I understood the problem, it will also occur on a new installation with Postgres, but I may be wrong.

Hi

Yes, what I've meant was a new installation on a MySQL database.

Ah, ok, I understand.

did you try the mentioned fix on your Postgres installation ( github.com/LimeSurvey/LimeSurvey/pull/3686/files )?