magic tag {@type} returns pod name when a field of name = 'type' does exists.

[ghost]

In an Advanced Content Type pod you are allowed to create a field with name = 'type'. You can access this field with PHP: $pods->field('type'). However, the magic code {@type} gives the pod name. As process_magic_tags() has this code: if ( 'type' == $field_name ) $value = $this->pod; - this seems to be by design. In this case should you allow the creation of a field with name = 'type' when it cannot be accessed with a magic tag.

[pglewis]

It's quite possible that 'type' is meant to be reserved, Scott will know the answer.

[sc0ttkclark]

{@type} is indeed a vestige from Pods 1.x days. I'm not entirely sure if it's ever even been used by anyone... I'm thinking we should deprecate it for 2.x and have it only evaluate as the pod name when using get_field or deprecated template functions.

[ghost]

My feelings is that the behavior of $pods->field('type') (which returns the value of the field named 'type') and {@type} should be identical so I vote for deprecation.

---

From: Scott Kingsley Clark notifications@github.com
To: pods-framework/pods pods@noreply.github.com
Cc: magenta-cuda magenta.cuda@yahoo.com
Sent: Wednesday, October 31, 2012 6:27 AM
Subject: Re: [pods] magic tag {@type} returns pod name when a field of name = 'type' does exists. (#689)

{@type} is indeed a vestige from Pods 1.x days. I'm not entirely sure if it's ever even been used by anyone... I'm thinking we should deprecate it for 2.x and have it only evaluate as the pod name when using get_field or deprecated template functions.
—
Reply to this email directly or view it on GitHub.