-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.permalink traversal for related taxonomies don't work #2779
Comments
L795 (in 2.x) looks like where it should pick up the term link. But it doesn't since the conditional that is wrapped in is based on $params->name which has the full value passed for field. But I think I'm missing something, since that would apply to all .permalink traversals, which work otherwise. |
It could also get picked up on 1472, but that doesn't get hit because the conditional on 1415 correctly is not passed. |
Alright just tested this earlier and confirm it works. Here is how I tested. I created a taxonomy called "tags2". I tested it with |
@NikV That's good, but what happens if there are two terms associated with the post? Please report what happens with |
For the |
Sounds like this patch needs more work. What does the var_dump look like? |
The |
close via f615242 |
Commit needs revisit |
If you do a
|
Issue #2779: `permalink` field traversal has only been working for post types (2.x)
Issue #2779: `permalink` field traversal has only been working for post types (3.0)
for info, this may or may not be related, but .permalink traversal for related ACTs had been working correctly for me on a theme i develop until upgrading to Pods 2.5.5 - but 2.5.5. version broke the .permalink traversal for me, somehow. not sure whether it's a distinct bug, and i couldn't find any issue for the ACT behaviour change, so apologies if i'm creating noise here 😏 'fixed' by getting the entire related ACT via |
I've opened #3155 for the regression this has caused. |
.permalink traversal for related taxonomies don't work submitted via Slack by josh
The text was updated successfully, but these errors were encountered: