Skip Navigation

[Resolved] Reordering RFGs and nested RFGs loses some data

This support ticket is created 4 years, 3 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 - - 9:00 – 13:00
14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 - - 14:00 – 18:00

Supporter timezone: Africa/Casablanca (GMT+01:00)

This topic contains 4 replies, has 2 voices.

Last updated by darmaJ-2 4 years, 3 months ago.

Assisted by: Jamal.

Author
Posts
#1798513

Hi Jamal, thanks for your confirmation, so this is not a bug and it's not possible, I can work around with that.

How about the second issue that I encounter :

"The second issue is when I rearrange the item in RFG - Modules Pages, to reorder it and click update the post, some of the data in items in Modules Pages also gone"

Is it a bug or did I miss something?

#1798517

First, I thought that this is probably caused by a low value of max_input_vars, so I checked on your website and I can see it at 10000, which should be fine.

So, to be sure, to understand the issue very well, I'd like to ask you to record a short screencast while reproducing this issue. This way, I can see what RFGs are reordered(first or second level), and what fields are lost. And this way, I can try to reproduce this on a clean install.
You can use tools such as Loom or Screencastify.

Thank you!

#1798653

Hi, Jamal thanks for the ticket, okay I will try to record the screen and get back to you at the soonest

#1801561

Thank you! I'll be looking forward to your reply.

#1806663

Hi Jamal,
I think the issue is the server configuration, so when I try to record it, there is no error as I mentioned earlier, so maybe there is some configuration change by server webmaster, that trigger the error earlier

many thanks for your support so far