$modx->getChunk not parsing placeholders

394 Posts

b03tz Reply #1, 15 years, 3 months ago

If I would do this:

$modx->getChunk('test', array(
   'human' => array(
       'name' => 'b03tz'
   )
));

And in my chunk I would do this:

[[!+human.name]]

This would normally have to work right...
It doesn’t even parse the placeholder at all :S

Follow me on twitter: @b03tz
Follow SCHERP Ontwikkeling on twitter: @scherpontwikkel
CodeMaster

5,888 Posts

Bruno17 Reply #2, 15 years, 3 months ago

<?php
$output = $modx->getChunk('test', array(
   'human' => array(
       'name' => 'b03tz'
   )
));

return $output;

this did work for me, when using

[[+human.name]]

as placeholder

-------------------------------

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

☆ A M B ☆
3,141 Posts

Mark Hamstra Reply #3, 15 years, 3 months ago

Calling it uncached will make it "skip" the parse cycle iirc.

Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.

48 Posts

Digital Butter - MODX Premiere Partners Reply #4, 15 years, 3 months ago

Quote from: Mark at Jun 21, 2011, 03:23 AM

Calling it uncached will make it "skip" the parse cycle iirc.

That makes sense I think? That PHP block would only be executing in the event that the snippet being run had not already been cached, therefore the only use case for using an uncached placeholder in a chunk this way would be that it’s value should *not* be set by the calling snippet but something higher up.

This is The Churn - A blog by a MODx addicted web agency based out of Hong Kong & Vancouver | [img]http://churn.butter.com.hk/web_assets/css/images/butterlogo.jpg[/img]

67 Posts

jcamachott Reply #5, 13 years, 4 months ago

Good tip - thanks.