Yii database cache? Can you clear your tmp/ folder, please?

How did you update? With Comfort Update or manually?

Manual update
--> New folder, unziped the files, confirmed the permissions, copied the contents of upload and the config file.
tmp folder was not copied.

Just cleared the tmp folder and got the same error.

Yeah, you will need help to rewind the database. Did you do a backup before the update?

I have a backup but it's not an option right now.
on going project! already have new data.
only made more tests after some time.
in search for this fix (14975), I've took the risk and updated in the middle of a project. clearly it's a DND, but, nowhere in the details was an information about version "4.0.. RC".

Is your survey still running properly?

not really.
in this specific one, I can't view the quota page. It just "freezes". the page starts the "loading screen" and never gives back a page. Other surveys the quota shows ok.
The survey was working ok, until this afternoon, where it just stopped responding.

OK, well, in any case, it's not easily done to revert the database to a previous state once it's upgraded. Best option is to finish your current running survey, backup your database, export all your surveys, and then do a fresh install with 3.17.8.

but what happened? I'm sure that I downloaded 3.17.8, not 4.0.0 Rc1 (or at least, I'm sure that I downloaded from "stable-release" or is 3.17.8 actually 4.0 RC1? )

Why fresh install? I was hopping to recover a DB version before the upgrade and return to 3.17.7

Yes, you downloaded a package that said 3.17.8, but we had a bug in the release process, actually putting LS4 into the package instead. We apologize for that, and can recommend that you use ComfortUpdate to update in the future (this will give you access to paid support).

If you have a backup of your database before the upgrade, that's great. You can use that after your running survey is finished.

I backup everything daily... :)
now I'm trying to download the data in SPSS version.. and I can't.. gives a "file not found error". (I already reported it)
I tried to make a copy (same DB) and give an error. Exported, imported, error...
Installed a new version (RC2 btw..), new DB, tried to import, again.. error.. (only the structure)

500: Internal Server Error
CDbCommand falhou ao executar o comando SQL: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '56-pt' for key 'lime_idx1_group_l10ns'

where "56-pt" is kind of random...

Can you help me understand the "lime_idx1_group_l10s" table so I can try to fix this?

@andre_ars : for production my advice is to get your backup …

Even some core developer have some difficulty with all this bug in 4.0.0-RC2, it's clearly not ready for production.

@DenisChenu I'm going back to the backup.. but I need to extract the data in SPSS format first... this was just bad timing...

I think you can export only the survey table and import it in your backup,
You can check the difference before …

i've already tried. I've installed a 3.18.8 and tried to import. It doesn't give any error, but no questions are created.
To many differences in the structure I believe

No, i mean only the data,
If you have new data since you last backup, i think the table survey_XXX have near same format.

Ok. I'll give that a try! thanks!

Dear DenisChenu,

I've just returned to the real 3.17.8 version and, has you said, the tables survey_xxxxx are the same.

I've imported and successfully restored the history from 4.0 rc1/rc2

Many Thanks!

I don't know if i can help you testing another upgrade from 3.17 to 4.0? (this time in a test environment)

Great :)

I check (again) an upgrade to see what happen.

Are there still issues with this bug report? As far as i understand, it started from the check integrity functionality - I tried to replicate it but I couldn't. I see that an upgrade was done to 3.17.8, but then the db version was updated from 359 to 419.

sory dorin,
I didn't had a chance yet to retry.
I'll give it another try till the end of the week, this time from 3.17.9 to the most recent RC.
regards

Hey @andre_ars,

Thanks for the feedback. Please wait for the RC4 release and try then (should be released till the end of the week) :)

To be tested again in LS4 RC4