Thanks for reporting this. Are you able to reproduce it? If so can you give me the steps or maybe a screenshot of your properties and their entries in the /config/DocTypeFieldsets.config file?
Also, when it happened, did you check any of the other tabs? Currently it's possible for the package to move properties to another tab, for example if a Master Doctype has a fieldset called "Meta" on a tab called "SEO", and you child doctype also has a fieldset called "Meta", the properties on the child doctype will get moved to the Meta tab. So I wonder if you had a fieldset defined with the same name on a parent type and the properties were just on another tab? This is sort of a bug, on my list to look into other ways to handle this (fieldsets should be per tab instead of per content type).
Ok, I've attached 2 screenshots of the config file.
Screenshot 1: Before save: Everything is almost ok, though I don't understand why there are keys without fieldset value. Screenshot 2: After save: I've added Toolbox 1 and Toolbox 2, but at the same time address, email, phone, fax and footerDescription now have fieldset values.
Thanks for sending the screencast on Github - apologies for the delay as I've been traveling all week.
I think I have an idea where the problem could be, I posted a new DLL for you to try on the Github issue. Just posting this here in case you don't receive emails from Github :)
Worked like a charm ... the first time.
The first time I assigned a few properties to a fieldset it worked fine. Then I changed the order to the properties and added a new property.
Now when I go to that tab on the document none of the properties are visible. If I remove the content in the fieldset input all properties are back.
Hi Sebastian,
Thanks for reporting this. Are you able to reproduce it? If so can you give me the steps or maybe a screenshot of your properties and their entries in the /config/DocTypeFieldsets.config file?
Also, when it happened, did you check any of the other tabs? Currently it's possible for the package to move properties to another tab, for example if a Master Doctype has a fieldset called "Meta" on a tab called "SEO", and you child doctype also has a fieldset called "Meta", the properties on the child doctype will get moved to the Meta tab. So I wonder if you had a fieldset defined with the same name on a parent type and the properties were just on another tab? This is sort of a bug, on my list to look into other ways to handle this (fieldsets should be per tab instead of per content type).
Thanks,
Tom
Hi Tom
Ok, I've attached 2 screenshots of the config file.
Screenshot 1: Before save: Everything is almost ok, though I don't understand why there are keys without fieldset value.
Screenshot 2: After save: I've added Toolbox 1 and Toolbox 2, but at the same time address, email, phone, fax and footerDescription now have fieldset values.
Does it make any sense ?
Hi Sebastian,
Thanks for sending the screencast on Github - apologies for the delay as I've been traveling all week.
I think I have an idea where the problem could be, I posted a new DLL for you to try on the Github issue. Just posting this here in case you don't receive emails from Github :)
Let me know if you're able to test it out
Thanks,
Tom
is working on a reply...