|
|
I turned on debugging (2) but no php errors were returned.
Would it be advisable for instance to upgrade to DB version 157 first? (By splitting up the upgrade script...) |
|
|
|
This should be resolved by assigning more memory. Can you try? |
|
|
|
php_memory_limit now set to 1024. We're getting to DbVersion 165 now!
Upgrade stops in "upgradePermissions166()": error message: The table "{{permissions}}" for active record class "Permission" cannot be found in the database.
I have added "$oDB->schema->refresh();" before "Permission::model()->refreshMetaData();" in upgradePermissions166(), but this does not seem to help..... |
|
|
|
I cannot reproduce this. Try to clear the model cache by clearing limesurvey\tmp\runtime\cache |
|
|
|
Cache cleared. Debugging set to 1. Skipped "upgradeSurveyTables164()" which resulted in error messages and is not necessary in our case.
Now I'm stuck in "upgradePermissions166()" where I added "$oDB->schema->refresh();" (see above). This statement gives error msg: "Undefined variable: oDB ".
I don't understand because same statement is used after "upgradeSurveys156()".... and passed without errors. |
|
|
|
use $oDB = Yii::app()->getDb(); to get the db object, |
|
|
|
Thank you.
I turned off debugging (which gave too many errors).
There was a unique constraint on 'email' (table users) which I had to drop, before the column could be altered. I couldn't find where this constraint was added and if it's even essential?
Managed to get to db version 177 this way, but got another sql error when trying to log in:
SELECT [t].[sid] AS [t0_c0] ,
...
[t].[private] AS [t0_c35] , -- column doesnt exist! (now "anonymized)"
[t].[notification] AS [t0_c36] ,-- col. was dropped (145)!
[languagesettings].[surveyls_survey_id] AS [t1_c0] ,
...
[languagesettings].[attachments] AS [t1_c23]
FROM [dbo].[surveys] [t]
LEFT OUTER JOIN [dbo].[surveys_languagesettings] [languagesettings] ON ( [languagesettings].[surveyls_survey_id] = [t].[sid] )
WHERE ( surveyls_language = language )
ORDER BY surveyls_title |
|
|
|
Clear the model cache again and this final issue should be gone.
The contraint will be fixed in the next version. |
|
|
|
One part of the problem seems to be that you are using still PHP 5.3. With PHP 5.4 most of the issues are gone. |
|
|
|
2.05+ Build 140320 released |
|
