I had been using config_builder 7.x-1.0-beta2 for about a month and just upgrades to 1.0 yesterday. I'm now having a problem moving a field into a fieldset. All were created before the upgrades. I've cleared cache, no luck.

I tried adding a new fieldset and then adding the existing fields to it. While the fieldset saved successfully, the fields will not stay in the fieldset when saved.

Tried to roll back to beta2, but ran into problems.

Comments

vinmassaro’s picture

vinmassaro CreditAttribution: vinmassaro commented

I've got the same problem with fieldsets in 7.x-1.0. Added some fields to a fieldset, save, and they are back out of the fieldset.

Deciphered’s picture

Deciphered CreditAttribution: Deciphered commented
Version: 7.x-1.0 » 7.x-1.x-dev

Can you test with dev and see if this is an issue? I've built a few forms inside of fieldsets myself, while there is the occasional weighting issue, resolvable via moving it after the initial save and saving again, the fieldsets seem to work as expected.

vinmassaro’s picture

vinmassaro CreditAttribution: vinmassaro commented

Still seeing it with the latest dev - 7.x-1.x-dev seems to be the same code as 7.x-1.0. Here is a video showing the behavior I'm seeing: http://www.youtube.com/watch?v=7kx5bmfvrvs

Two issues:

1. Naming the fieldset the first time does not save the fieldset name.
2. After adding two fields to my fieldset and saving, you'll see the "Sidebar heading color" field disappears after saving and I have no way to access it.

Deciphered’s picture

Deciphered CreditAttribution: Deciphered commented

Hmm, it does look somewhat related to the issue I've previously had, where I was seeing some aspects missed after the first save, but it's an item going completely missing isn't really all that good.

Can I recommend that you cross post this issue (and video) to Form Builder as well, as there's a chance it could also be related to the that, but given that I had to implement Form Builder in a non-standard way there's no way of telling for sure (without digging into the issue).

I will try to set out some time in the next few days to try to reproduce and nail down the issue, in the mean time, you should still be able to get the desired end result by re-adding the missing field and saving and tweaking and saving until it's all working as expected. Not ideal, but it should work.