Using "show this field only if", no values are stored!

[horst]

Hi,

I have setup a new blank site with PW 2.6.0 stable version.

I have created a template that has two fields, the Title and a PageTable.

The PageTable 's template contains besides the title a single Pagefield with radios plus three other fields (text or integer) that should only be shown if the right option from the Pagefield is selected. This works fine and as expected!

But the values entered into the fields do not get stored in the DB!

If I strip the showOnlyIf condition, the values get stored as expected!

With the SHowOnlyIf condition, the data isn't stored when opening the page from the PageTable-field in a modal window,

nor when selecting the page from the pagetree and open it directly for editing.  ??

Is this expected behave or do I miss something?

Edited May 9, 2015 by horst
edited subject

[LostKobrakai]

Just to clarify, are the fields you're talking about hidden on saving the page or does this even happen if they are visible? Latter one can hardly be intentional.

[horst]

It is when they are visible.

[LostKobrakai]

I just tested it on a new installation and it's working fine for me. 

[horst]

Have you used the showOnlyIf conditional?

Here is a exported siteprofile of it. It is a clean and fresh install from 2.6.0 stable from today started with a blank profile: site-wrongShowonlyif.zip

[tpr]

Played with your siteprofile but I couldn't spot anything. I can confirm that the issue exists. If I remove the ShowOnlyIf condition then the min-max-step values are saved properly. Putting back ShowOnlyIf and re-saving the page doesn't remove previous min-max-step values, so it seems that saving the page completely ignores these fields.

POST parameters contains all the values though.

[horst]

Thanks for looking at it.

Is there a chance that I have setup something wrong? The place in pagetree where the data is saved?

[tpr]

Try using this instead of "fua_fe_item_antwort.name=fua-form-slider"

fua_fe_item_antwort=1023

Seems to work here but don't ask me why

(trial and error)

[horst]

Hey,

this works here too. But it isn't the best solution because hardcoded page-ids isn't practical. I need to export / import that at some point to another site and need to use generic properties like name. I will file an issue with this, at least I'm interested why it works with id but not with subfield.name.

But also nice to have it working for a first tests here.