<?php
$daten=array('ph1'=>'erster','ph2'=>'zweiter','ph3'=>'dritter');
return $modx->parseChunk('parsetest', $daten);
?>[[+ph1]]<br/> [[+ph2:ucase]]<br/> [[+ph3]]<br/>
[[!parsechunk]]
erster dritter
if ($chunk= $this->getChunk($chunkName))
function parseChunk($chunkName, $chunkArr, $prefix=’[[+’, $suffix=’]]’) {
$chunk= ’’;
if ($chunk= $this->getChunk($chunkName,$chunkArr)) {
if(is_array($chunkArr)) {
reset($chunkArr);
while (list($key, $value)= each($chunkArr)) {
$chunk= str_replace($prefix.$key.$suffix, $value, $chunk);
}
}
}
return $chunk;
}
$modx->parseChunk('@FILE'.$filename, $daten);
<?php
/**
* Process and return the output from an HTML chunk by name.
*
* @param string $chunkName The name of the chunk.
* @param array $properties An associative array of properties to process
* the chunk with.
* @return string The processed output of the chunk.
*/
function getChunk($chunkName, $properties= array ()) {
$output= '';
if(substr($chunkName, 0, 5) == "@CODE") {
$content = trim(substr($chunkName, 5));
$chunk= $this->newObject('modChunk');
$output= $chunk->process($properties,$content);
//$chunkName='empty';
}
elseif ($chunk= $this->getObject('modChunk', array ('name' => $chunkName), true)) {
$chunk->setCacheable(false);
$output= $chunk->process($properties);
}
return $output;
}
/**
* Parse a chunk using an associative array of replacement variables.
*
* @param string $chunkName The name of the chunk.
* @param array $chunkArr An array of properties to replace in the chunk.
* @param string $prefix The placeholder prefix, defaults to [[+.
* @param string $suffix The placeholder suffix, defaults to ]].
* @return string The processed chunk with the placeholders replaced.
*/
function parseChunk($chunkName, $chunkArr, $prefix='[[+', $suffix=']]') {
$chunk= '';
if ($chunk= $this->getChunk($chunkName,$chunkArr)) {
if(is_array($chunkArr)) {
reset($chunkArr);
while (list($key, $value)= each($chunkArr)) {
$chunk= str_replace($prefix.$key.$suffix, $value, $chunk);
}
}
}
return $chunk;
}
?>
MODX Staff
No, this needs to be done at the modElement level for all elements, and needs to be supported outside of the modX class functions like parseChunk() or getChunk(). That is the beauty of an OO API though, as the modElement class has getContent() and setContent() functions that can be used to implement similar behavior (though I do not think @CODE or @FILE should be used personally; this should be simply specified as the content in the database entry for the chunk), then you can do stuff like:
had only a short Test for this, but couldn’t we do it this way?:
so we can get a filecontent before calling parseChunk and can send it with @CODE................................. in $chunkName
[[!MySnippet? &tplFromChunk=`[[$MyChunk]]` &tplFromFile=`[[GetFileContent? &filename=`foo/bar/`]]`]]
or$modx->parseChunk(’parsetest’, $daten);
or$modx->parseChunk(’@CODE[[+ph1]]
[[+ph2]]
[[+ph3]]
’, $daten);
$modx->parseChunk(’@CODE’.$filecontent, $daten);
<?php
$filecontent='[[+ph1]],[[+ph2]],[[+ph3]]';
$daten=array('ph1'=>'first','ph2'=>'second','ph3'=>'third');
$chunk= $modx->newObject('modChunk');
$chunk->setCacheable(false);
$output= $chunk->process($daten,$filecontent);
return $output;
?>
<?php
$daten=array('ph1'=>'first','ph2'=>'second','ph3'=>'third');
return $modx->getChunk('parsetest', $daten);
?>
MODX Staff
Not at all. The problem is they now do all sorts of things internally to deal with input themselves (i.e. @CODE was made up by one of those snippets I believe, and has never been part of the core); they just need to accept the content as input, since that is now possible. You can pass content directly in tag strings now, so how it is retrieved is irrelevant. In addition, you can nest tags infinitely, so there is no limit to how you decide to get content in and out of your various elements.
So, if I understand, every snippet which handles with templates and/or chunks like Ditto, wayfinder, maxigallery and so on needs its own template-processor-class?
There is, for chunks:
I was hoping there is an easy way in revolution where you can send your placeholders and your template/chunk name or code to a given function and it would return the processed and PHx-filtered output-string as in my little experiment
$modx->getChunk('parsetest', $daten);[[!$parsetest? &ph1=`value1` &ph2=`value2` &ph3=`value3`]]
$content = file_get_contents(MODX_BASE_PATH . 'path/to/file/content.tpl');
$chunk= $modx->newObject('modChunk');
$output = $chunk->process($properties, $content);
return $output;<?php
$content = isset($content) ? $content : '[[+ph1]]<br/>[[+ph2]]<br/>[[+ph3]]<br/>';
/* turn the script properties into placeholders and keep overwritten values for restoration */
$restore = array();
$placeholders = $scriptProperties;
if (is_array($placeholders) && !empty($placeholders)) {
$restoreKeys = array_keys($placeholders);
foreach ($restoreKeys as $phKey) {
if (isset($modx->placeholders[$phKey])) $restore[$phKey]= $modx->getPlaceholder($phKey);
}
$modx->toPlaceholders($placeholders);
}
/* collect element tags in the output and process them */
$maxIterations= isset ($modx->config['parser_max_iterations']) ? intval($modx->config['parser_max_iterations']) : 10;
$modx->parser->processElementTags('', $content, false, false, '[[', ']]', array(), $maxIterations);
/* remove the placeholders set from the properties of this script and restore global values */
$modx->unsetPlaceholders(array_keys($scriptProperties));
if ($restore) $modx->toPlaceholders($restore);
return $content;
?>
And soon, Revolution will support file-based content for all chunks directly, so if you want the content managed in an external file, you will be able to use it without doing anything special; it’ll just be an element that references it’s source content from the file-system. But this feature will likely be in a release after the initial one.