Caching Template Library - Revision history

Tom: /* PHP Code in a Template Files */

2022-01-13T15:22:47Z

‎PHP Code in a Template Files

2018-11-30T14:07:21Z

‎Example 4

2018-11-30T14:06:52Z

‎Example 4

2018-11-30T14:06:30Z

‎Comments

2018-11-30T14:03:17Z

‎Example 4

2018-11-30T14:02:23Z

‎Example 4

2018-11-30T14:02:11Z

‎Example 3

2018-11-26T21:46:09Z

‎Replacement Variable Manipulation Modifiers

2018-11-26T21:13:21Z

‎Replacement Variable Manipulation Modifiers

2018-08-15T17:16:46Z

‎TEMPLATE_OPTIONS

@@ Line 458: / Line 458: @@
 == PHP Code in a Template Files ==
-This feature allows you to embed PHP code directly in templates. To embed PHP code directly in a template, use the following example:
+This feature allows you to embed PHP code directly in templates. Remember you need to be very careful when using PHP and selecting variable names for variables you create in your code. Make sure they are unique as variables can unintentionally be overwritten if they are for example global in scope and/or are local in scope but are being used in the Geeklog function already that will be evaluating your PHP code.
 <pre>
 <div class="welcomeanddate-text">

@@ Line 426: / Line 426: @@
      {!!set myVar1 array_slice({myVar}, {myCount}, 1)[0] !!}
      myVar: {myVar1}<br>
     {!inc myCount}
 {!endwhile!}
 The output then looks like this:
 <pre>

@@ Line 422: / Line 422: @@
 {!!set myVar array('a', 'b') !!}
 {!!set myCount 0 !!}
 {!!while !empty(array_slice({myVar}, {myCount}, 1)) !!}
      {!!set myVar1 array_slice({myVar}, {myCount}, 1)[0] !!}
      myVar: {myVar1}<br>
     {!inc myCount}
 {!endwhile!}

@@ Line 368: / Line 368: @@
 === Comments ===
-You can include comments in the template files that do not appear in the cached PHP file by enclosing the comment within {# and #} symbols. This is useful for explaining why you have some weird construct in your code without cluttering the cached template with lots of HTML comments.
+You can include comments in the template files that do not appear in the cached PHP file by enclosing the comment within {# and #} symbols. This is useful for explaining why you have some weird construct in your code without cluttering the cached template with lots of HTML comments. If you want these comments to appear in the cache and the HTML source of the page you can in the Geeklog Configuration enable "Template Comments in Output". See example 3 to see how to use a comment.
 === Examples ===

@@ Line 423: / Line 423: @@
 {!!set myCount 0 !!}
 {!!while !empty(array_slice({myVar}, {myCount}, 1)) !!}
-{!!set myVar1 array_slice({myVar}, {myCount}, 1)[0] !!}
+    {!!set myVar1 array_slice({myVar}, {myCount}, 1)[0] !!}
-myVar: {myVar1}<br>
+    myVar: {myVar1}<br>
-{!inc myCount}
+   {!inc myCount}
 {!endwhile!}
 The output then looks like this:

@@ Line 433: / Line 433: @@
 </pre>
-==== Example 4 ====
+==== Example 5 ====
 This example is Geeklog specific to help illustrate how you might use even the simplest !if construct:
 <pre>

@@ Line 415: / Line 415: @@
 of 5: 8
 of 5: 9
 </pre>

@@ Line 190: / Line 190: @@
 * :u Call urlencode on the variable before output.
 * :s Call htmlspecialchars on the variable before output.
-* :h Call strip_tags on the variable before output.
+* :h Call strip_tags on the variable before output. (as of Geeklog v2.2.1)
 * :t### Truncates the variable to ### characters.

@@ Line 102: / Line 102: @@
 * 'device_mobile' ⇒ $_DEVICE->is_mobile(),
 * 'front_page' ⇒ COM_onFrontpage(),
-* 'current_url' ⇒ COM_getCurrentURL()
+* 'current_url' ⇒ COM_getCurrentURL() (Note: This returns the current URL as PHP sees it on the server. If the server is setup to rewrite the URL then it may be different from the actual URL)
 ''' 'incl_phpself_header' (optional) '''