[Resuelto] Latest update cause select field to populate empty option.

[Autor]

Mensajes

[Akhil]

hi guys, it was all good before the update, after update i have this strange issue,

i looked at the code its generated as ' <option value="" checked="checked"></option> '

again i hope this is a known issue.

[Nigel]

I can't replicate the issue, can you give more details about where exactly you see this?

I have a Types select field which works fine on the backend post edit screens, fine in front-end Forms, and also outputs its value correctly in templates.

[Akhil]

i can confirm the latest update cause the issue but its not that serious,

i am guessing its attr 'default label', or the empty label issue. ill post some updates soon.

[Akhil]

previously >

display_values="default,option1,option2" .....values=",option1,option2" ....default_label="default"

curently need to adjust to >

display_values="option1,option2 "... values="option1,option2 " .... default_label="default"

not an issue i just need to edit all the codes for 10 cpt. going to take some time to do this unless there is another way.

[Nigel]

Sorry, I can't tell where you are seeing the problem.

The custom fields settings screen?
A post edit screen?
A Toolset Form?
A View?

Can you show me a screenshot and then I'll recognise where this is happening.

[Akhil]

wordpress archive edit page, code generated from the filter plus custom attributes.

could you just get some info from the developers on the changes made so that we know its the case and can close this case ?

thanks!

update : i am thinking that previously the attr "default-value" was not supported fully, now it does.

[Nigel]

OK, I have it now.

When you insert a select field filter control in an archive with manual options where you include a default option, since Views 2.6.2 an additional empty default option has been added automatically, too.

Let me check with the developers before you go making any changes, because you might edit your archives to remove the manual default option, only to find that the automatic default option gets removed in a future update.

I'll update you when I hear from them about how to proceed.

[Akhil]

oh my i just edited all my 10 cpt :0 . hope i am doing the right thing, wait for your update soon then, cheers

[Nigel]

I just confirmed with the developer that this was unintended and it will be reverted to the prior behaviour.

Sorry I didn't get back to you more quickly, but at least they will look correct in the meantime until a fix is released.

[Akhil]

Sorry but i have to voice out on this.

This is so unproffesional !
. why would you want to include something thats not permanent and confuse the end users ?

it's time consuming for us to update all the codes to fit the latest release.

[Nigel]

As I said, it wasn't intended, the change looks to be a side effect of something else that was changed in Views 2.6.2, we can call it a bug, and it will be fixed soon.

If you have made changes to adapt to the bug then I'm sorry if that involves changing back again when the bug is fixed.

I expect it to be resolved quickly and I'll let you know when it is.

[Nigel]

A quick update to confirm that this issue will be fixed in the next Views release, and that a patch is available as described in this erratum: https://toolset.com/errata/default-value-issues-for-frontend-filters-styled-as-select-or-radio-fields/

Again, sorry for the inconvenience caused.

[Akhil]

Thank you , its not on you Nigel .
appreciate the effort,
now im back to adjust the code again.