Loading Profile...
Twitter,
Facebook, or email.
{field:all_options}{options}{/field:all_options} isn't working for a P&T Checkboxes field. I'm using the latest code from Gethub and the latest build of EE2.
Currently the template just spits out the tags without parsing them.
:all_options Not Working for P&T Checkboxes
Official
Response
-
Came across this again while trying to add an :images tag pair to Wygwam.
Turns out that EE simply doesn't support tag pairs for custom fieldtype functions, e.g. :all_options.
Upon realizing that, I was going to just make the :all_options functionality parameter-triggered (all_options="yes"), but decided to remove it entirely instead.
Reason for that is, the use cases for :all_options are generally situations where you’d want the options to appear whether there's a selected option or not. But if you have a field that has no value, EE will just remove its tags from the template, rather than give the fieldtype a chance to intervene. So by "fixing" the all_options functionality, I’d just be taking something that currently never works, to something that sometimes works (if there are selections), which is even worse. Better to just get people to hard-code their options, and use the :selected tag.
EMPLOYEE
-
Are you placing the tag inside an {exp:channel:entries} tag pair for an entry that has a P&T Checkboxes field?Comment
-
-
I sure am; removing the :all_options portion of the tag will show the selected items as expected.
-
-
Just looked into this, and I’m able to reproduce. Weird thing is, the :all_options single tag is working fine (outputting a plain <ul>). Really not sure why EE isn’t parsing the tag pair.
-
-
I'm just noticed this issue on our EE2 site as well. Has all_options been removed (either you or EllisLab)? Looking through code I see an all_options method/function in ext.fieldframe.php in an EE1 install, but in my EE2 install I only see a function called replace_all_options in /system/expressionengine/third_party/pt_field_pack/pt_fieldtype.php. -
-
In EE2, tag functions must be prefixed with "replace_". So replace_all_options() is there for :all_options tags.
Why EE isn’t parsing it as a tag pair has me totally stumped though... -
-
Having this problem too. Any solution yet? -
-
When I looked into it I determined it was an EE bug, but I've never taken the time to actually figure out what's going on.
-
-
Came across this again while trying to add an :images tag pair to Wygwam.
Turns out that EE simply doesn't support tag pairs for custom fieldtype functions, e.g. :all_options.
Upon realizing that, I was going to just make the :all_options functionality parameter-triggered (all_options="yes"), but decided to remove it entirely instead.
Reason for that is, the use cases for :all_options are generally situations where you’d want the options to appear whether there's a selected option or not. But if you have a field that has no value, EE will just remove its tags from the template, rather than give the fieldtype a chance to intervene. So by "fixing" the all_options functionality, I’d just be taking something that currently never works, to something that sometimes works (if there are selections), which is even worse. Better to just get people to hard-code their options, and use the :selected tag. -
-
I’m
confused
At this moment, the tag pairs for P&T Checkboxes aren't working for me at all.
When I use the single tag it nicely outputs the selected checkboxes, but using {field_name}{option}{/field_name} outputs nothing.
It's so straight forward I can't imagine that I'm missing something, but am I? :) -
-
What exactly happens when you use the tag pair? Is it removed from the template, or do the tags show up on the front end?
-
-
Nothing shows up (removed from the template). -
-
Can you try updating P&T Field Pack to the version on GitHub?
https://github.com/pixelandtonic/pt_f... -
-
I’m
yay!
Great, that solved it!
Thanks a lot Brandon for your very quick support :). -
-
Glad that worked!
-
