Title: Problems after eeeeevery update Last modified: October 9, 2024 --- # Problems after eeeeevery update * Resolved [CDHeumann](https://wordpress.org/support/users/cdheumann/) * (@cdheumann) * [1 year, 8 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/) * After each update, my blocks break, and I can not repair them. I have to manually recreate them by copying the content and setting up a new accordion group with individual elements. This is very frustrating. Is this a known problem? Viewing 15 replies - 1 through 15 (of 28 total) 1 [2](https://wordpress.org/support/topic/problems-after-eeeeevery-update/page/2/?output_format=md) [→](https://wordpress.org/support/topic/problems-after-eeeeevery-update/page/2/?output_format=md) * Plugin Author [Sajjad Hossain](https://wordpress.org/support/users/codersajjad/) * (@codersajjad) * [1 year, 8 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18062765) * Hello, * We sincerely apologize for the inconvenience you’re facing. We’re aware of this issue and are actively working on a fix. In the next version release, we will ensure that you don’t experience the same problem with future updates. Thank you for your patience, and we appreciate your understanding. * Thanks & regards * [doplp](https://wordpress.org/support/users/doplp/) * (@doplp) * [1 year, 7 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18106766) * Hello, * Please we need an update concerning this bug cause I had to revert to an old version to keep my accordions working. And I cannot update them because everything is deleted when I click on “Attempt Block Recovery”. Please please do something or I’ll have to find another plugin and post a really bad comment on this one! * Thanks for your understanding. * Thread Starter [CDHeumann](https://wordpress.org/support/users/cdheumann/) * (@cdheumann) * [1 year, 7 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18106798) * Hi [@doplp](https://wordpress.org/support/users/doplp/). That’s a bit of an odd threat, haha… It annoys me too. But I’m sure they’re working on it. What helped me was creating a new accordion group and then dragging the individual (old) accordion elements into it. It was annoying, but it went pretty quickly. * [doplp](https://wordpress.org/support/users/doplp/) * (@doplp) * [1 year, 7 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18106829) * Hi [@cdheumann](https://wordpress.org/support/users/cdheumann/), thanks for the tips. * I’m just facing with a multisite with 6 sub-sites with almost 30 accordions in each one. So I just wanted to know if an update is scheduled for the coming days/ weeks or if I have to keep my head down and follow your solution. I understand I was a little bit negative but my client lacks patience. Sorry about that [@codersajjad](https://wordpress.org/support/users/codersajjad/), do you have some insights about an upcoming fix? * Thanks for your help. * Plugin Author [Sajjad Hossain](https://wordpress.org/support/users/codersajjad/) * (@codersajjad) * [1 year, 7 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18108937) * Hello [@doplp](https://wordpress.org/support/users/doplp/) , * Sorry for the delay. We’re actively working on this issue and will release an update as soon as possible. In our upcoming version, you won’t encounter this type of problem again. We appreciate your patience and understanding. * [jellet](https://wordpress.org/support/users/jellet/) * (@jellet) * [1 year, 6 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18184790) * I have sort of the same problem. Maybe it will not happen again with the latest update but we will see. I have noticed that it depends on the page if “block repair” is possible and how easy it is. Even on seamingly unrepairable pages I’m able to repair the blocks after several tries (refesh the edit page and quickly click “block repair”). * I hope this helps and I hope the issue will get resolved quickly. * Plugin Author [Sajjad Hossain](https://wordpress.org/support/users/codersajjad/) * (@codersajjad) * [1 year, 6 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18186331) * Hello [@jellet](https://wordpress.org/support/users/jellet/) We have already resolved this issue in the current version (4.7.4). Starting with the next update, you will no longer encounter the “block repair error.” * [kmaynard](https://wordpress.org/support/users/kmaynard/) * (@kmaynard) * [1 year, 6 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18190664) * I have been updated to version 4.7.4 since last week and am still having to manually recreate blocks. They also disappear if we make other edits on the page and save. Do you mean the update following this current version? - This reply was modified 1 year, 6 months ago by [kmaynard](https://wordpress.org/support/users/kmaynard/). * [Morten_Hjort](https://wordpress.org/support/users/morten_hjort/) * (@morten_hjort) * [1 year, 6 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18191423) * Just to add that I have the same issue. Using the latest WP, so it also states that its not necessarily compatible. * Is there an expected fix for this coming soon? * Plugin Author [Sajjad Hossain](https://wordpress.org/support/users/codersajjad/) * (@codersajjad) * [1 year, 6 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18192003) * Hello [@kmaynard](https://wordpress.org/support/users/kmaynard/) [@morten_hjort](https://wordpress.org/support/users/morten_hjort/), We have thoroughly tested the issue across multiple environments but, unfortunately, we have been unable to replicate the problem where the content disappears. * To assist us in investigating further and identifying a solution, could you please provide more details about the issue? For example, the theme you are using, the PHP version, or server details etc. * Alternatively, it would be extremely helpful if you could provide temporary access to a test environment. This will allow us to conduct a deeper investigation and address the issue more effectively. * Looking forward to your response. * [Morten_Hjort](https://wordpress.org/support/users/morten_hjort/) * (@morten_hjort) * [1 year, 6 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18194154) * Hi [@codersajjad](https://wordpress.org/support/users/codersajjad/) * Is this useful? I checked our staging environment and updated everything. Here it seemed to be possible to click the “Attempt Recovery” which worked. So its odd. * ```wp-block-code - **Server architecture:** Linux 4.18.0-553.27.1.lve.el8.x86_64 x86_64 - **Web server:** LiteSpeed - **PHP version:** 8.3.13 (Supports 64-bit values) - **PHP SAPI:** litespeed - **PHP max input variables:** 5000 - **PHP time limit:** 60 - **PHP memory limit:** 512M ``` * Plugin Author [Sajjad Hossain](https://wordpress.org/support/users/codersajjad/) * (@codersajjad) * [1 year, 6 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18194201) * Hello [@morten_hjort](https://wordpress.org/support/users/morten_hjort/) Thank you for providing the details. Could you please consider testing this issue by switching your current web server from “LiteSpeed” to either “Apache” or “Nginx”? * [bekee](https://wordpress.org/support/users/bekee/) * (@bekee) * [1 year, 5 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18201871) * The update to 4.7.4 broke accordions on several of my client’s sites. You really should have a red alert in the admin telling people there are breaking changes, and they need to prepare to rebuild every “old” accordion to accommodate the code changes in this version. Not having done this is irresponsible. * Plugin Support [SpiderThemes Support](https://wordpress.org/support/users/spiderthemes247/) * (@spiderthemes247) * [1 year, 5 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18202913) * Hello [@bekee](https://wordpress.org/support/users/bekee/) , Has the issue occurred on the frontend as well?Additionally, are all the old accordions displaying an“ attempt recovery” message? If so, this will be the last time this happens, and in the next version, this notice will no longer appear. * Please let me know so I can assist you further. * [Morten_Hjort](https://wordpress.org/support/users/morten_hjort/) * (@morten_hjort) * [1 year, 5 months ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/#post-18203051) * @[Sajjad Hossain](https://wordpress.org/support/users/codersajjad/) I’m unfortunately not able to control such settings through my hosting 🙁 Viewing 15 replies - 1 through 15 (of 28 total) 1 [2](https://wordpress.org/support/topic/problems-after-eeeeevery-update/page/2/?output_format=md) [→](https://wordpress.org/support/topic/problems-after-eeeeevery-update/page/2/?output_format=md) The topic ‘Problems after eeeeevery update’ is closed to new replies. * ![](https://ps.w.org/advanced-accordion-block/assets/icon-256x256.png?rev=3196321) * [Advanced Accordion Gutenberg Block – Create Beautiful FAQs, Content Accordions & Interactive Tabs](https://wordpress.org/plugins/advanced-accordion-block/) * [Frequently Asked Questions](https://wordpress.org/plugins/advanced-accordion-block/#faq) * [Support Threads](https://wordpress.org/support/plugin/advanced-accordion-block/) * [Active Topics](https://wordpress.org/support/plugin/advanced-accordion-block/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/advanced-accordion-block/unresolved/) * [Reviews](https://wordpress.org/support/plugin/advanced-accordion-block/reviews/) * 28 replies * 10 participants * Last reply from: [SpiderThemes Support](https://wordpress.org/support/users/spiderthemes247/) * Last activity: [1 year, 1 month ago](https://wordpress.org/support/topic/problems-after-eeeeevery-update/page/2/#post-18446676) * Status: resolved