The LimeSurvey server timezone can not be checked because your LimeSurvey site is hosted on an external server.
Test abord.Check it manually on the LimeSurvey global setting page

If it fails, yo may check the Time difference setting on your LimeSurvey global setting page.
Note : informations from the LimeSurvey admin interface are the trusted ones.

There are a few spelling errors
yo > you
abord > abort
informations > information

Beyond that I'm not able to get past this error and need a bit of support.

CommentFileSizeAuthor
#1 ls_settings.png69.63 KBthedut

Comments

thedut’s picture

thedut commented
StatusFileSize
new ls_settings.png69.63 KB

Hi akayani,

Thanks for reporting this spellings errors.
Pay attention : The test does not return a failure message but a warning message : this means your synchronization setting may be correctly set but the drupal site is not able confirm it.
You have to follow the provided link (the LimeSurvey global settings, general tab) and check if the "corrected time" is the same as your own time : the attached snapshot will be you.

akayani’s picture

akayani commented

The regional setting in Drupal is Brisbane Australia +17 hours on the server.

Both the Drupal and Limesurvey are on the same Dreamhost machine.

Users in Drupal can set their own time zones.

On 0 or +17 the warning is flagged.

I'm guessing this should be set to 0 as they are on the same server? Otherwise the user time will need to be fixed and no time selection by the user in Drupal would work.

Is that right?

Message reads...

The LimeSurvey server timezone can not be checked because your LimeSurvey site is hosted on an external server.
Test abord.Check it manually on the LimeSurvey global setting page

thedut’s picture

thedut commented

Hi akayani,

The time synchronization is going to be redesigned in the next LimeSurvey Sync release. It will be available soon, within 1 or 2 weeks.
It will fix several limitations of the current system.
The current release :
- does not handle drupal users with their own timezone.
- may miscalculate the Limesurvey dates. If you met such issue, as a workarround you can set on the LimeSurvey Sync synchronization setting page the timezone in seconds. In your case, setting the 'Adjust time between the Drupal server and the LimeSurvey server' parametter to 61200 seconds (17*3600) may fix it, even if the system throws a warning message.

Your Drupal and Limesurvey sites are on the same Dreamhost machine but the system consider that your LimeSurvey site is hosted on an external server.
I guess you may use a distinct database name or a distinct database driver (mysql/mysqli, etc...) : That why the system buggy detects your LimeSurvey on a external server (and should not) and throw a warning message in all cases.
I'm going to fix this on the next release.
The limesurvey_sync_external_server() function from the limesurvey_sync.inc file is involved.
Thanks.

In order to help me, could you provide some informations :
- On your LimeSurvey admin inteface, general settings : what is your 'Time difference' value in order to read a valid 'corrected time'
- What is your drupal timezone setting on your drupal site : /admin/settings/date-time ?
- do you met some issues when creating answers for survey wich are using token invitations ?

akayani’s picture

akayani commented

On your LimeSurvey admin inteface, general settings : what is your 'Time difference' value in order to read a valid 'corrected time'

17 hours

What is your drupal timezone setting on your drupal site : /admin/settings/date-time ?

Only local images are allowed.

akayani’s picture

akayani commented

I can wait for 2 weeks and early test this for you. There are bugs in a few modules that I need to use, I'm going to fit the development schedule here to those fixes.

thedut’s picture

thedut commented

Hi Akayani !

I'm on the verge of releasing the new LimeSUrvey Sync version.
Here is the new version. Please tell me if it fix you issue !

thedut’s picture

thedut commented

Hi Akayani,

Don't waste your time testing this version, it does not solve your issue.
I have completly rebuild the "time system", everything works now.
Wait for the new release !

thedut’s picture

thedut commented
Status: Active » Closed (fixed)

Fixed into the LimeSurvey Sync 7.x-1.2 and 6.x-1.2 releases.