Check out the LimeSurvey source code on GitHub!

Admin screen template is all messed up

More
4 years 8 months ago #80517 by Fred01
Ok I give up. After updating my system, the admin screen is messed up. See the screen shot.

I have been running 1.92 and 2.0beta and rc1 side by side using the same database and had no problem so far.

After poking around, I have concluded the problem is somewhere in settings_global. If I insert some standard 1.92 settings from a new database it looks fine, but then if I go back to my settings then it looks messed up again.

Here are the settings

INSERT INTO `lime_settings_global` VALUES('DBVersion', '156');
INSERT INTO `lime_settings_global` VALUES('force_ssl', 'neither');
INSERT INTO `lime_settings_global` VALUES('timeadjust', '+0 hours');
INSERT INTO `lime_settings_global` VALUES('shownoanswer', '2');
INSERT INTO `lime_settings_global` VALUES('updatecheckperiod', '7');
INSERT INTO `lime_settings_global` VALUES('sitename', 'LimeSurvey');
INSERT INTO `lime_settings_global` VALUES('defaulttemplate', 'default');
INSERT INTO `lime_settings_global` VALUES('defaulthtmleditormode', 'inline');
INSERT INTO `lime_settings_global` VALUES('usepdfexport', '1');
INSERT INTO `lime_settings_global` VALUES('ipInfoDbAPIKey', '');
INSERT INTO `lime_settings_global` VALUES('googleMapsAPIKey', '');
INSERT INTO `lime_settings_global` VALUES('maxemails', '50');
INSERT INTO `lime_settings_global` VALUES('surveyPreview_require_Auth', '1');
INSERT INTO `lime_settings_global` VALUES('filterxsshtml', '0');
INSERT INTO `lime_settings_global` VALUES('usercontrolSameGroupPolicy', '1');
INSERT INTO `lime_settings_global` VALUES('repeatheadings', '25');
INSERT INTO `lime_settings_global` VALUES('showxquestions', 'hide');
INSERT INTO `lime_settings_global` VALUES('showgroupinfo', 'choose');
INSERT INTO `lime_settings_global` VALUES('showqnumcode', 'none');
INSERT INTO `lime_settings_global` VALUES('defaultlang', 'en');
INSERT INTO `lime_settings_global` VALUES('enableXMLRPCInterface', '0');
INSERT INTO `lime_settings_global` VALUES('restrictToLanguages', '');
INSERT INTO `lime_settings_global` VALUES('addTitleToLinks', '0');
INSERT INTO `lime_settings_global` VALUES('defaultquestionselectormode', 'default');
INSERT INTO `lime_settings_global` VALUES('defaulttemplateeditormode', 'default');
INSERT INTO `lime_settings_global` VALUES('emailmethod', 'smtp');
INSERT INTO `lime_settings_global` VALUES('emailsmtphost', 'email-smtp.us-east-1.amazonaws.com:465');
INSERT INTO `lime_settings_global` VALUES('emailsmtppassword', 'XXXXXX);
INSERT INTO `lime_settings_global` VALUES('bounceaccounthost', '');
INSERT INTO `lime_settings_global` VALUES('bounceaccounttype', 'off');
INSERT INTO `lime_settings_global` VALUES('bounceencryption', '');
INSERT INTO `lime_settings_global` VALUES('bounceaccountuser', '');
INSERT INTO `lime_settings_global` VALUES('bounceaccountpass', '');
INSERT INTO `lime_settings_global` VALUES('emailsmtpssl', 'ssl');
INSERT INTO `lime_settings_global` VALUES('emailsmtpdebug', '');
INSERT INTO `lime_settings_global` VALUES('emailsmtpuser', 'XXXXXX');
INSERT INTO `lime_settings_global` VALUES('siteadminbounce', 'XXXX');
INSERT INTO `lime_settings_global` VALUES('siteadminemail', 'XXXXX');
INSERT INTO `lime_settings_global` VALUES('siteadminname', 'LimeSurvey');
INSERT INTO `lime_settings_global` VALUES('sess_expiration', '3600');
INSERT INTO `lime_settings_global` VALUES('updateavailable', '0');
INSERT INTO `lime_settings_global` VALUES('updatelastcheck', '2012-05-16 14:54:49');
INSERT INTO `lime_settings_global` VALUES('sessionlifetime', '3600');
INSERT INTO `lime_settings_global` VALUES('googletranslateapikey', '');
INSERT INTO `lime_settings_global` VALUES('googleanalyticsapikey', '');
INSERT INTO `lime_settings_global` VALUES('updatebuild', '120509');
INSERT INTO `lime_settings_global` VALUES('updateversion', '1.92+');
INSERT INTO `lime_settings_global` VALUES('adminthemeiconsize', '32');
INSERT INTO `lime_settings_global` VALUES('updatekey', 'LIMESURVEYUPDATE');
INSERT INTO `lime_settings_global` VALUES('admintheme', 'gringegreen');
Attachments:

Please Log in to join the conversation.

More
4 years 8 months ago #80518 by holch
I am no developer, but it looks to me as if the css files or the jquery files are missing somehow. Did you try to empty the cache of your browser?

Have a look at the manual! It is a really valuable source for information. Here some helpful links:
Manual (EN) | Question Types | Workarounds

Please Log in to join the conversation.

More
4 years 8 months ago #80520 by Fred01
Hi, thanks. I figured it out. It wasn't the js or css, although clearing the cache again helped me figure out what it was.

It was the most obvious answer as it turned out. The awesome new LS2 admin themes are to blame. LS2 now seems to default to the "gringegreen" theme. If you change it to one of the other themes, then it inserts a row in the settings_global with stg_name='admintheme' and stg_value= theme name. Then if you access the same db with LS1.92 then it doesn't recognize that theme and so it fails.

I just deleted the admintheme row from global_settings and now both LS1.92 and LS2 use their default themes and everything is fine.

Maybe the developers could add a line in 1.92 to ignore this setting? It may seem like an extreme use case, but the database works so well in both versions now that it's a shame to have this little glitch which could be easily resolved.

Please Log in to join the conversation.

More
4 years 8 months ago - 4 years 8 months ago #80521 by holch
Good to hear that you could fix it!

What I am not getting: what is the point of running various versions of LS on the same database (despite the risk of messing things up?)?

;-)

[edit]Fixed horrible English[/edit]

Have a look at the manual! It is a really valuable source for information. Here some helpful links:
Manual (EN) | Question Types | Workarounds
Last Edit: 4 years 8 months ago by holch.

Please Log in to join the conversation.

More
4 years 8 months ago #80522 by Fred01
I am using the central participants database piece of LS2 and testing it out.

There really are virtually no problems, other than this one. Just have to make sure you activate token based surveys from the LS2 side or remember to add the participant_id to the tokens table.

Maybe I'm just lucky though :)

Please Log in to join the conversation.

More
4 years 8 months ago #80527 by Fred01
Although for production use I stick with the correct database for the correct version ...

Please Log in to join the conversation.

More
4 years 8 months ago #80538 by DenisChenu

Fred wrote: Maybe I'm just lucky though :)

think too,

because there some difference between 2 and 1.92, for example the group have "Randomization group:" on 2 and not on 1.92.

2 are in RC, and i think we can't work on a double installation with the same DB with a lot of bug to be corrected on 2 actualy ;).

Denis

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand (or search sondages pro).

Please Log in to join the conversation.

More
4 years 8 months ago #80541 by Fred01
Yes, I don't use randomization groups because I'm already random enough.

Hopefully everything in LS2 is working soon and I won't need 1.92.

Please Log in to join the conversation.

Imprint                   Privacy policy         General Terms & Conditions         Revocation information and revocation form