The LimeSurvey Fund-Raiser 2012 is complete. Thank you for donating a total of 25,000 USD!     List of donors »
Welcome, Guest
Username: Password: Remember me
Forgot your password? Forgot your username?
  • Page:
  • 1

TOPIC: old_survey old_tokens table clean-up

old_survey old_tokens table clean-up 2 years 3 months ago #57474

  • khoy
  • khoy's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 17
  • Karma: 0
We have set up a Limesurvey environment with about 200 users and 300 surveys for the moment.
Our users activate and deactivate surveys constantly.
Limesurvey doesn't delete old_survey_XXXX and old_tokens_xxxx tables when a survey is deleted.
Is there a reason why the old tables are left?
Did someone already set up some processes to clean up these tables?
The administrator has disabled public write access.

Re: old_survey old_tokens table clean-up 2 years 3 months ago #57478

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 4431
  • Thank you received: 460
  • Karma: 167
khoy wrote:
Is there a reason why the old tables are left?
Sometimes, you can want to acess to old survey.
And when you activate an unchanged survey, you can reimport the old answer.
Did someone already set up some processes to clean up these tables?
Check data integrety, on the first menu-bar

:)
The administrator has disabled public write access.

Re: old_survey old_tokens table clean-up 2 years 2 months ago #57648

  • khoy
  • khoy's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 17
  • Karma: 0
Ok. I found the button. But it didn't work for our set-up.
It only works if you use a prefix 'xxxx_' for the tables in the database.
Here $dbprefix is '' in config.php.
Maybe the code in integretycheck.php could be changed to work for no db-prefix or maybe even more (xxx_xxx_) because this seems to be the only place where it makes a difference what dbprefix you use.
The administrator has disabled public write access.

Re: old_survey old_tokens table clean-up 2 years 2 months ago #57652

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 4431
  • Thank you received: 460
  • Karma: 167
khoy wrote:
Maybe the code in integretycheck.php could be changed to work for no db-prefix or maybe even more (xxx_xxx_) because this seems to be the only place where it makes a difference what dbprefix you use.
Can you see at our bug report system if this bug appear. And if not, put a complete bug report. Did you have some error in screen ?
Please test if the problem still exists at the latest release. If so please open a ticket at the bugtracker and...

1. Give as much information as possible

2. Attach your survey. You can mark your ticket "private" so that only the developers will be able to take a look at it.

3. Provide step-by-step instructions how to reproduce the problem.

4. If possible/helpful please provide screenshots

Afterwards please post the link to the bugtracker so we can follow the progress.

Thanks!

:)
The administrator has disabled public write access.

Re: old_survey old_tokens table clean-up 2 years 2 months ago #57779

  • khoy
  • khoy's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 17
  • Karma: 0
bug report entered #04995
The administrator has disabled public write access.

Re: old_survey old_tokens table clean-up 2 years 2 months ago #57805

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 4431
  • Thank you received: 460
  • Karma: 167
khoy wrote:
bug report entered #04995
Fixed for svn version.

I think you can try with replace the file integritycheck.php in 1.90+ version

limesurvey.svn.sourceforge.net/viewvc/li...n/integritycheck.php

(do a backup before)
The administrator has disabled public write access.
  • Page:
  • 1
Moderators: DenisChenu, ITEd
Time to create page: 0.644 seconds
Donation Image