Thread

I am using 2.1.3 build 20110411.
I have seen a couple of bugs that might be related to the issue I am having (https://support.ellislab.com/bugs/detail/14682/ and https://support.ellislab.com/bugs/detail/14997/), but am not sure if they cover it, so am posting here in case I am doing something wrong or this may be a different bug.

For custom fields that I have set to show by default when added, I am finding that they can revert to closed on the publish/edit screen (i.e. you need to click on the field name to get it to appear and change the arrow icon beside its name to a down arrow).

This is really annoying, because you go in, customise your publish layout, save it for all member groups, and then you will be editing an entry at some point down the line and a couple of fields may not be open by default, so you have to open it and resave your layout until the next time you notice it.

I have not managed to find the circumstances that cause this to occur. I only seem to notice it with fields I have added to a field group after the initial field group set up and post the first publish layout save, but that may not be conclusive.
I think it has happened with fields which have had no field changes to them since the publish layout was saved too.
It can happen on any tab on multi tab publish screens.
There just seems to be no logic to it - I’ll just be editing an entry and notice that some fields are not open and have to fix it.

While annoying, it’s not a big deal for me as a developer, but I can see it causing issues for some clients - I prefer to leave fields open to make the edit screen as obvious and simple to use as possible.

If I’m doing something wrong in saving the layouts etc, please set me straight, or if this is already in the bug tracker, let me know.

Thanks for your time.

Hey Janine—

Hmm… yes, I can see how this is frustrating, especially given its apparent random nature. I was able to reproduce the problem described in the second bug report you linked to, and it looks like the problem you outlined is related to that bug since it can be reproduced by saving a channel’s Publish Layout and then either editing an existing field in a field group or adding a new field to the field group.

Have you been able to reproduce the problem under any other circumstances?

This bug is marked as Fixed in Beta, so if you’re not working on a mission-critical site, you might want to give the 2.1.4 Beta a try. If you do, let me know if you’re still able to reproduce the problem after upgrading to the beta.

Kevin

Hi Kevin,

Thanks for the reply. Yes, I intend trying the beta out on a test environment when I get a chance because most of the bugs I have run into are marked as fixed in that. So, once I have had time to test things out on the beta I will post if there is still an issue.

Thanks,
Janine.

Sounds good, Janine. In that case, closing the thread. Feel free to start a new thread if you have any more questions.