nauran81

@spiderthemes247 … some feedback from our client:

The Advanced Accordion Block update is being a little problematic. It feels like a coin toss whether or not the block will expand on the editing screen to allow for the editing of content inside of each block. I can work around it for now by using the outline view to drag content into and out of the accordions, but suspect some of our other users will not be as thrilled with that workaround. I haven’t looked in the support forums yet, but I’m curious to know if others are experiencing this problem.

On the upside, the repair blocks feature seems to be working well for the corruption issue.

@spiderthemes247 … so the latest version change says this in the changelog:

New: Added Custom Recovery Button On top toolbar that recovers all recovery block in a single click (If you see the attempt recovery notice, you’ll find a button on the top toolbar. Clicking it will dismiss all recovery notices instantly)

Is this really the fix to the issues we have outlined over the past couple months? Or only a band aid to help the recovery process — that really isn’t a fix to the accordions breaking on the frontend as well, IMHO.

@codersajjad, @spiderthemes247, and @jellet … this if from the client:

In some ways, it has gotten worse. The expansion problem doesn’t seem to be an issue any more, but the block recovery is still problematic. But now instead of the blocks at least hanging around on the edit screen in the supposedly corrupted state so that one could make a new group accordion and drag the block content from the old block to the new one (using the outline view), now when you edit a page oftentimes the entire accordion block resets itself and you are left copy and pasting from the published page to restore the content of those accordions.

• This reply was modified 1 month, 3 weeks ago by nauran81.

Thanks for updating us all @codersajjad!

Could you clarify what fixes will be addressed in your next update release? Looking over the several comments from other members, it seems we are all encountering slightly different issues with the plugin. (e.g. when we attempt recovery, we don’t lose content like @lukermiller said. And the front end blades on our site don’t work when the error isn’t fixed)

As @loganjudy mentioned, a rollback to the previous version might be a better option in the interim. Do you have a download link to that version that we can revert to?

Another thing we noticed is that it’s only happening to us when we’re signed in as WordPress admins. If I open a “broken” page in incognito/private/Guest mode, the blades on the front end to the end user does still expand.

Could there be something conflicting with your accordion blocks plugin and the extra admin navigation bar along the top of the site?

Not quite the response I was hoping. To further ask…why does the functionality of the accordion blade cease to work on the front end? This should be something you need to fix, right…?

Hello Riza.

Thanks for looking into the issue. I tried your hotfix update and it did in fact work!

I appreciate your quick response and fix to this.

When will this fix be available for all websites to update to?

@sixaxis … any word from the Toolset team yet on this?

Is your latest update including a fix for this? The changelog seemed vague, so I thought to ask.

Also, can you give me access to download the older version 3.5.0 as a fallback for my clients running into this issue on their site?

Hey Konrad,

Thanks for confirming all this.

So to clarify, our options are:

1. setup the code snippet to force to re-update these specific bidirectional fields while being able to use the duplicate post/page plugins?
If so, we’d have to setup a snippet for each created bi-direction field, yes?
Lastly, does this situation affect other ACF fields other than bi-directional relationship fields?

2. instead of using the code snippet, and after a duplication, we would have to go into the new post, remove all related posts from the field, save, then re-add them, and save…and this SHOULD update the other related post’s bi-direction field values?

Hi Konrad,

So actually, what we discovered yesterday is when manually added, it works.

BUT we were using a post duplicator plugin to duplicate entries that had existing bi-directional relationship fields filled in.

The plugin in question we were using: Duplicate Page Version 4.4.1 | By mndpsingh287

So the original FinanceOption entry related to multiple products works fine…but when we duplicate the entry to a new FinanceOption for the same set of products, the new one does not seem to “update” the related Product’s Bi-direction related field of Finance Options to add the duplicated Finance Option.

…does that make sense?