ProcessWire - Render Funktionen - Versionsgeschichte

109.193.152.88: /* Use Cases und Unterschiede */

2024-12-04T11:51:29Z

Use Cases und Unterschiede

2024-12-04T11:49:12Z

Kleine ProcessWire Renderübersicht

2024-12-04T10:20:23Z

Use Cases und Unterschiede

2024-07-22T13:48:47Z

Kleine ProcessWire Renderübersicht

2024-04-19T17:12:52Z

Kleine ProcessWire Renderübersicht

2024-04-19T17:11:03Z

Kleine ProcessWire Renderübersicht

2024-04-19T17:09:55Z

Kleine ProcessWire Renderübersicht

2024-04-19T17:04:42Z

2024-04-19T16:59:23Z

Links

2024-04-19T16:55:51Z

← Nächstältere Version		Version vom 4. Dezember 2024, 11:51 Uhr
Zeile 63:		Zeile 63:

	It seems to me that you're trying to use '''$page->render()''' to something it's really not meant for: $page->render() is intended for rendering a specific page (optionally using a specific file), while '''wireRenderFile()''' renders a specific file without the need for a Page object. Those are two different use cases.		It seems to me that you're trying to use '''$page->render()''' to something it's really not meant for: $page->render() is intended for rendering a specific page (optionally using a specific file), while '''wireRenderFile()''' renders a specific file without the need for a Page object. Those are two different use cases.
		+
		+	=== $page->render vs $files->render ===
		+	PAGE
		+	$page rendert inkl. head etc. (also eine richtige html Seite
		+	Zugriff auf Variablen über $options Array $foo -> $options['foo']
		+
		+	FILES
		+	$files rendert nur das was return zurück gibt (kein html, body, etc)
		+	Zugriff auf Variablen direkt über den Namen. Wenn du $foo bleibt $foo

@@ Zeile 28: / Zeile 28: @@
 echo $page->renderValue($results, 'children');
 // $files->renderUsage
 $files->render('teasers', ['items' => $pages->find("template=article")]); // mostly for delayed output

@@ Zeile 53: / Zeile 53: @@
 == Use Cases und Unterschiede ==
-$page->render('some_field') does indeed call renderField(), but only if the given param is a field name. Take a look at PageRender for more details. If you provide a filename as a param, $page->render() will use that file to render given page.
+ $page->render('some_field')
-If you provide a filename (actual filename, not just something like "file") to $page->render() as the first param, you can provide an array as the second param, and the values stored in that array can then be accessed via $options.
+does indeed '''call renderField(), but only if the given param is a field name'''. Take a look at PageRender for more details.
-It seems to me that you're trying to use $page->render() to something it's really not meant for: $page->render() is intended for rendering a specific page (optionally using a specific file), while wireRenderFile() renders a specific file without the need for a Page object. Those are two different use cases.
+If you provide a '''filename as a param''', $page->render() will use that file to render given page.

@@ Zeile 35: / Zeile 35: @@
 //$page->render() is intended for rendering a specific page (optionally using a specific file)
 //wireRenderFile() renders a specific file without the need for a Page object
 </syntaxhighlight>

@@ Zeile 10: / Zeile 10: @@
 Die häufigsten...
 <syntaxhighlight lang="php">
 $page->render($filename); // $filename (including .php) assumed in /site/templates/
 $page->render($pathname); // $pathname is full path, but must resolve somewhere in web root
@@ Zeile 18: / Zeile 19: @@
 $mixed = $page->renderValue(mixed $value);
 $mixed = $page->renderValue(mixed $value, string $file = '');
 // Render a value using site/templates/fields/my-images.php custom output template
 $images = $page->images;

@@ Zeile 22: / Zeile 22: @@
 echo $page->renderValue($images, 'my-images');
-// In Template access $results as $value / template is .../fields/children.php
+// In Template .../fields/children.php access $results as $value
 $results = $pages->find("body%=some text");
 echo $page->renderValue($results, 'children');

@@ Zeile 15: / Zeile 15: @@
 $page->render($fieldname) // short for $page->renderField() IF parameter is a fieldname - then pw looks for template file in /fields
-// render the pages using templates/fields/myFieldTemplate and access ther with $page->
+// renderValue basic usage
-$page->renderValue($myPageArray, 'myFieldTemplate');
+$mixed = $page->renderValue(mixed $value);
-$page->renderValue($myValue, 'templateName'); //
 $files->render('teasers', ['items' => $pages->find("template=article")]); // mostly for delayed output

@@ Zeile 5: / Zeile 5: @@
   [[ProcessWire - Rendering Templates mit fields Ordner]]
   https://processwire.com/blog/posts/processwire-3.0.7-expands-field-rendering-page-path-history-and-more/#theres-also-page-gt-rendervalue
 == Kleine ProcessWire Renderübersicht ==

@@ Zeile 9: / Zeile 9: @@
 Die häufigsten...
 <syntaxhighlight lang="php">
-$page->render($filename); // $filename assumed in /site/templates/
+$page->render($filename); // $filename (including .php) assumed in /site/templates/
 $page->render($pathname); // $pathname is full path, but must resolve somewhere in web root
-$page->render($filename, $options); // specify filename and options/vars, etc.
+$page->render($filename, $myArray); // $myArray can be accessed via $options in Template
 // render the pages using templates/fields/myFieldTemplate and access ther with $page->
@@ Zeile 20: / Zeile 21: @@
 wireRenderFile('my_template', array('pid' => $child->id)); // old version of $files->render
 wireIncludeFile() // for direct output
 </syntaxhighlight>