ProcessWire - Performance - Versionsgeschichte

84.136.104.26: /* wireCache */

2020-02-13T15:56:07Z

wireCache

2020-02-13T15:54:24Z

Caching

2020-02-13T15:52:17Z

Caching

2020-02-13T14:56:40Z

Caching

2020-02-13T14:55:29Z

Caching

2020-02-13T10:17:07Z

2020-02-13T10:12:35Z

Caching

2020-02-12T10:19:31Z

Performance und Repeater Matrix

2020-02-12T10:07:03Z

2020-02-12T09:31:44Z

@@ Zeile 19: / Zeile 19: @@
 	$content = renderLayoutBlocks($page,$additionalHeaderData); // 2nd passed by reference
 	$cache->save($cacheId, $content);
+}
 </syntaxhighlight>

@@ Zeile 10: / Zeile 10: @@
 ''' Beispiel - delayed output variable eines Templates cachen.
 <syntaxhighlight lang="php">
 $cacheId = 'c_content_'.$page->id;

@@ Zeile 5: / Zeile 5: @@
   https://processwire.com/talk/topic/10548-my-way-of-using-wirecache-and-some-hints-to-make-life-easier-with-it/
-Example als Hook für die ready.php (ungetestet)
+Auf die WireCache Klasse kann mit der '''$cache''' variable zugegriffen werden. Die angelegten Caches werden in der PW Datenbank gespeichert. Es gibt diverse Methoden
 <syntaxhighlight lang="php">
-// the next ensures that the following code will only run on front end (otherwise back end would get cached, too which results in problems)
+$cacheId = 'c_content_'.$page->id;
-// make sure to place anything you need in the backend before this line or change it to your needs..
+$content = $cache->get($cacheId);
-if ((strpos($page->url, wire('config')->urls->admin) !== false) || ($page->id && $page->is('parent|has_parent=2'))) return;
+if(!$content) {
+	include("./partials/layout-blocks.inc");
-$cacheName = "prefix__$page->id-$page->template-{$user->language->name}";
+	$content = renderLayoutBlocks($page,$additionalHeaderData); // 2nd passed by reference
-if ($urlSegment1) $cacheName .= "-$urlSegment1";
+	$cache->save($cacheId, $content);
+}
 </syntaxhighlight>

@@ Zeile 5: / Zeile 5: @@
   https://processwire.com/talk/topic/10548-my-way-of-using-wirecache-and-some-hints-to-make-life-easier-with-it/
-Example (ungetestet)
+Example als Hook für die ready.php (ungetestet)
 <syntaxhighlight lang="php">
 // the next ensures that the following code will only run on front end (otherwise back end would get cached, too which results in problems)

@@ Zeile 3: / Zeile 3: @@
   https://processwire.com/blog/posts/processwire-core-updates-2.5.28/#wirecache-upgrades
   https://processwire.com/talk/topic/15286-delete-and-generate-new-markup-cache/
 == Performante Datenbankabfragen ==

@@ Zeile 1: / Zeile 1: @@
 == Caching ==
 === wireCache ===
 == Performance Testen ==

@@ Zeile 40: / Zeile 40: @@
 == Performance und Repeater Matrix ==
 === Backend ===
 * Repeater Items per AJAX laden
@@ Zeile 51: / Zeile 52: @@
 * Layoutblock -> Select Feld
 * Optionen werden geladen.

← Nächstältere Version		Version vom 12. Februar 2020, 10:07 Uhr
Zeile 38:		Zeile 38:
	<syntaxhighlight lang="php">		<syntaxhighlight lang="php">
	</syntaxhighlight>		</syntaxhighlight>
		+
		+	== Performance und Repeater Matrix ==
		+	=== Backend ===
		+	* Repeater Items per AJAX laden
		+	https://processwire.com/blog/posts/more-repeaters-repeater-matrix-and-new-field-rendering/#repeater-upgrades-continued-in-pw-3.0.5
		+	=== Frontend ===
		+	* Können viele Datenbank (PDO) Queries auslösen, da alle Page Objekte geladen werden müssen.
		+
		+	=== Auswahl aus verschiedenen Repeatern über ein Select, statt einzelnes RepeaterMatrix Feld ===
		+	Evtl. könnte man ein Auswahlfeld generieren, das dann wiederum einen Contentblock wählt, statt alles in ein RepeaterMatrix Feld zu packen.
		+
		+	* Layoutblock -> Select Feld
		+	* Optionen werden geladen.