View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 10
IDProjectCategoryView StatusDate SubmittedLast Update
06479Bug reportsSurvey editingpublic2012-08-13 21:332013-07-12 07:51
Reporterlolo Assigned Toc_schmitz  
PrioritynormalSeverityminor 
Status closedResolutionfixed 
Product Version2.00RC8 
Target Version2.00RC9Fixed in Version2.00RC9 
Summary06479: Cannot re-activate survey after it has been expired
Description

After a survey has been stopped by expiration, then by de-activation, it is not possible to put the survey back to active state.

Another point is that when expiring survey, the Expiry date/time becomes: 01.01.1970 00:00 (don't know if that is to be expected to or not).

Steps To Reproduce

  • create survey, activate

  • expire survey
    => Expiry date/time becomes: 01.01.1970 00:00 [OK or not?]

  • deactivate survey
    => survey is deactivated [OK]

  • try to reactivate survey
    => survey comes back to expired state [NOT OK]

The only way to put the survey back to active state is to clear the 'expires' column directly in table lime_surveys

TagsNo tags attached.
Attached Files
summary_screen.png (57,651 bytes)   
summary_screen.png (57,651 bytes)   
publication_and_access_control_screen.png (55,309 bytes)   
publication_and_access_control_screen.png (55,309 bytes)   
Bug heat10
Complete LimeSurvey version number (& build)120803
I will donate to the project if issue is resolvedNo
BrowserSafari 5.1.7 (Mac)
Database type & versionMysql 5.5.24
Server OS (if known)Linux 2.6.27.52
Webserver software & version (if known)Apache 2
PHP Version5.3.14

Users monitoring this issue

bluemind

Activities

sammousa

sammousa

2012-08-14 09:39

reporter   ~20413

I can only partly reproduce this.

  • Yes, the survey is still expired after reactivation.
  • No, the expiration date is not set to 1970, but to yesterday.
  • I can change the expiration date in the survey settings, after changing that it works.

Dev: A possible solution is to check the expiration date on survey activation; if it is in the past then we remove it, if it is in the future we leave it. We CAN NOT always remove it on activation since this would also remove values configured by the user before survey activation.
Optionally this removal could be accompanied by a message like "Since the expiration date was in the past we have removed it. Please reconfigure the expiration date if you wish to use this feature."

--> Assign it to me if you agree with my proposed solution.
DenisChenu

DenisChenu

2012-08-14 10:02

developer   ~20414

sammousa:
I think we have to leave "expiration date" even if it's in past.

For me the real bug is here:
"The only way to put the survey back to active state is to clear the 'expires' column directly in table lime_surveys"

No ?
sammousa

sammousa

2012-08-14 10:16

reporter   ~20417

Yes, but the setting is also available via survey -> general settings -> publication & access control.
lolo

lolo

2012-08-14 13:28

reporter   ~20418

Hello, could you just check again the point about showing "01.01.1970 00:00" ?
The expiration date is indeed correctly displayed in the "survey -> general settings -> publication & access control" page (by default set to yesterday).
It is however still showing "01.01.1970 00:00" on the survey summary page (reachable by showing detailed list of surveys, then clicking on the survey).
Thanks for your time.
sammousa

sammousa

2012-08-14 13:31

reporter   ~20419

As I said in my first post, this is not reproducable for me.
13.08.2012 13:29
lolo

lolo

2012-08-14 13:39

reporter   ~20420

@sammousa: I uploaded two screenshots:
summary_screen.png -> expiry date is "01.01.1970 00:00"
publication_and_access_control_screen.png -> expiry date is "13.08.2012 13:20"
It seems like a display issue only.

PS: using RC8, also tried clearing my browser cache
sammousa

sammousa

2012-08-14 13:47

reporter   ~20421

Can indeed reproduce it on RC8, seems to be fix on github latest version though.
c_schmitz

c_schmitz

2012-08-16 10:23

administrator   ~20448

Version 2.00 RC 9 released.

Issue History

Date Modified Username Field Change
2012-08-13 21:33 lolo New Issue
2012-08-14 09:39 sammousa Note Added: 20413
2012-08-14 10:02 DenisChenu Note Added: 20414
2012-08-14 10:16 sammousa Note Added: 20417
2012-08-14 12:24 c_schmitz Status new => resolved
2012-08-14 12:24 c_schmitz Fixed in Version => 2.00RC9
2012-08-14 12:24 c_schmitz Resolution open => fixed
2012-08-14 12:24 c_schmitz Assigned To => c_schmitz
2012-08-14 13:28 lolo Note Added: 20418
2012-08-14 13:28 lolo Status resolved => feedback
2012-08-14 13:28 lolo Resolution fixed => reopened
2012-08-14 13:31 sammousa Note Added: 20419
2012-08-14 13:36 lolo File Added: summary_screen.png
2012-08-14 13:36 lolo File Added: publication_and_access_control_screen.png
2012-08-14 13:39 lolo Note Added: 20420
2012-08-14 13:39 lolo Status feedback => assigned
2012-08-14 13:47 sammousa Note Added: 20421
2012-08-14 13:47 sammousa Status assigned => resolved
2012-08-14 13:47 sammousa Resolution reopened => fixed
2012-08-15 00:22 c_schmitz Target Version => 2.00RC9
2012-08-16 10:23 c_schmitz Note Added: 20448
2012-08-16 10:23 c_schmitz Status resolved => closed
2013-07-12 07:51 bluemind Issue Monitored: bluemind
2019-11-01 17:25 c_schmitz Category Survey design => Survey editing
2021-08-07 09:58 guest Bug heat 8 => 10