In this specific case, the nester placeholder is from a text field declared within a MIGX TV. I assumed it would be set by that time, but apparently that simply isn't the case. I'm unsure how I might go about getting that to happen, but as the TV is directly accessible by the template I don't know which order everything would be happening in. It seems my snippet is being evaluated before the MIGX TV is being used.
Do cached things get resolved before uncached? I can't remember where I read about that. Is it possible that if I ran my snippet cached it might have worked? Academic now, as I've found a much better solution, but in either case I would like to be able to run it either cached or uncached without it affecting the snippets success.
-
☆ A M B ☆
- 3,141 Posts
If it's a TV, you are mixing up the tag syntax.
This is a resource field or template variable:
This is a placeholder:
Small difference with huge impact.
Shameless plug to a blog I recently wrote about this very subject:
http://www.markhamstra.com/modx-blog/2012/2/placeholders-resource-fields-tags/
Thanks, but I meant to say that the placeholder is the result of a call to the MIGX list snippet. And, in fact, it's being used inside an inline chunk (@CODE). It's definitely a placeholder I'm using, which works just fine if I don't try to manipulate it.
-
☆ A M B ☆
- 3,141 Posts
Okay, that does change it. I'm not a big fan of inline chunks using @CODE cause it seems somewhat jumpy to me. It may be set by something else on the page, not get passed to the snippet properly etc. My preference goes to either regular chunks or file based if the snippet supports it.
