Title: killed database
Last modified: May 24, 2020

---

# killed database

 *  Resolved [bloomraker](https://wordpress.org/support/users/bloomraker/)
 * (@bloomraker)
 * [6 years ago](https://wordpress.org/support/topic/killed-database/)
 * Dear Support-Team,
    today I installed your plugin Complianz for Coockies. After
   installing I followed the assistant. The assistant changed something in the database
   and now my website is crashed. Please help me, what happend! :/

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Author [Aert](https://wordpress.org/support/users/aahulsebos/)
 * (@aahulsebos)
 * [6 years ago](https://wordpress.org/support/topic/killed-database/#post-12882813)
 * Hi [@bloomraker](https://wordpress.org/support/users/bloomraker/),
 * I don’t know what happened. To see what we can do, please either use a back-up,
   or rename the complianz folder via FTP – which can be found here: wp-content/
   plugins/
 * Did you get any error during the process? We haven’t any database issue with 
   other users, so I guess it might be something else.
 * regards Aert
 *  Thread Starter [bloomraker](https://wordpress.org/support/users/bloomraker/)
 * (@bloomraker)
 * [6 years ago](https://wordpress.org/support/topic/killed-database/#post-12882838)
 * Hi Aert,
 * Thanks for your quick answer.
    No, no error during the process. Just the message
   that something will happen / modif with the database. Later on the database was
   crashed.
 * My provider uploaded a backup database. Now the contents are back again but I
   have problems:
    All links in the front-end do not work from now on and in the
   backend, if I change for example a page so I will receive a error message „Aktualisierung
   fehlgeschlagen: Die Antwort ist keine gültige JSON-Antwort“ Do you know what 
   does it mean?
 * I did only installed your plugin and followed the install assistant 🙁
 * Thanks
 *  Plugin Author [Aert](https://wordpress.org/support/users/aahulsebos/)
 * (@aahulsebos)
 * [6 years ago](https://wordpress.org/support/topic/killed-database/#post-12882861)
 * Hi [@bloomraker](https://wordpress.org/support/users/bloomraker/),
 * I found this; in German. Maybe you can follow the same steps, and let me know.
 * [https://de.wordpress.org/support/topic/aktualisierung-fehlgeschlagen-die-antwort-ist-keine-gueltige-json-antwort/](https://de.wordpress.org/support/topic/aktualisierung-fehlgeschlagen-die-antwort-ist-keine-gueltige-json-antwort/)
 *  Thread Starter [bloomraker](https://wordpress.org/support/users/bloomraker/)
 * (@bloomraker)
 * [6 years ago](https://wordpress.org/support/topic/killed-database/#post-12882944)
 * Hi,
 * Year I saw this already before too but it didn’t help.
    Now I think the problem
   is with the permalinks in WordPress (backend -> settings -> permalink)
 * If I change now to Typ of permalink“normal“ the pages will load in the front-
   end but buddy press do not work with normal permalinks so this option is gone.
   
   Can you tell me what do your plugin change there? Steps before
 * 1.) only! install your plugin
    2.) database crashed 3.) Provider uploaded database
   from backup 4.) contents are back but with the errors 4.1)deinstalled your plugin
   4.2) doesn’t changed anything ; errors still there
 * Thanks you
 *  Thread Starter [bloomraker](https://wordpress.org/support/users/bloomraker/)
 * (@bloomraker)
 * [6 years ago](https://wordpress.org/support/topic/killed-database/#post-12883099)
 * Hi Aert,
    Thanks big this solutionnis not for being happy. Can you tell me, what
   do your plugin chance with permalinks? Is there any consensus with?
 *  Plugin Contributor [Rogier Lankhorst](https://wordpress.org/support/users/rogierlankhorst/)
 * (@rogierlankhorst)
 * [6 years ago](https://wordpress.org/support/topic/killed-database/#post-12883518)
 * Hi [@bloomraker](https://wordpress.org/support/users/bloomraker/),
 * Complianz does not affect permalinks, nor does it cause issues with the database
   on the almost 50000 websites it’s currently installed on.
 * The only database action performed on activation (so before you even start the
   wizard) is that some tables are added, which is normal for a plugin.
 * In what way did the database crash? It seems unlikely that this was caused by
   complianz, but with more detailed info we can investigate.
 * If the database was restored, the errors that remain won’t be caused by complianz
   anymore. Clearing all caches and saving permalinks may flush old data.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘killed database’ is closed to new replies.

 * ![](https://ps.w.org/complianz-gdpr/assets/icon-256x256.png?rev=2881064)
 * [Complianz - GDPR/CCPA Cookie Consent](https://wordpress.org/plugins/complianz-gdpr/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/complianz-gdpr/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/complianz-gdpr/)
 * [Active Topics](https://wordpress.org/support/plugin/complianz-gdpr/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/complianz-gdpr/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/complianz-gdpr/reviews/)

 * 6 replies
 * 3 participants
 * Last reply from: [Rogier Lankhorst](https://wordpress.org/support/users/rogierlankhorst/)
 * Last activity: [6 years ago](https://wordpress.org/support/topic/killed-database/#post-12883518)
 * Status: resolved