Customization - Revision history

KKoPV: /* vzlogger compatibility */

2015-07-07T10:18:52Z

‎vzlogger compatibility

2015-07-07T10:18:09Z

‎Custom API routes

2015-07-07T10:13:34Z

‎vzlogger compatibility

2014-11-19T20:07:17Z

‎Predefined HTML output hooks

2014-05-13T13:04:32Z

2014-05-13T13:03:58Z

‎vzlogger compatibility

2014-05-13T13:03:31Z

‎vzlogger compatibility

2014-05-13T13:01:49Z

‎vzlogger compatibility

2014-05-13T13:01:39Z

‎vzlogger compatibility

2014-05-13T13:01:29Z

‎vzlogger compatibility

@@ Line 106: / Line 106: @@
   "middleware" : "<nowiki>http://localhost/</nowiki>'''''api/latest'''''",
-The coding is prepared in <tt>routes.custom.php.dist</tt>, copy to <tt>routes.custom.php</tt> and uncomment the relevant coding:
+The coding is prepared in <tt>routes/custom.php.dist</tt>, copy to <tt>routes/custom.php</tt> and uncomment the relevant coding:
   $api->post( ...

@@ Line 81: / Line 81: @@
 === Custom API routes ===
-For [[API]] since <tt>r3</tt> you can define your own routes in <tt>route.custom.php</tt>.
+For [[API]] since <tt>r3</tt> you can define your own routes in <tt>routes/custom.php</tt>.
 The API is based on the [http://www.slimframework.com/ Slim framework].
-See <tt>route.custom.php.dist</tt> for reference and refer to the other route definitions in <tt>route.*.php</tt> for middleware helper functions and help.
+See <tt>routes/custom.php.dist</tt> for reference and refer to the other route definitions in <tt>routes/*.php</tt> for middleware helper functions and help.
 === vzlogger compatibility ===

@@ Line 104: / Line 104: @@
 to
-  "middleware" : "<nowiki>http://localhost/</nowiki>'''''api/r3'''''",
+  "middleware" : "<nowiki>http://localhost/</nowiki>'''''api/latest'''''",
 The coding is prepared in <tt>routes.custom.php.dist</tt>, copy to <tt>routes.custom.php</tt> and uncomment the relevant coding:

@@ Line 43: / Line 43: @@
 | <tt>frontend/View/hook.head.tpl</tt> || Injected just before <tt></head></tt> tag
 |-
-| <tt>frontend/View/hook.body.before.tpl</tt> || Injected just after <tt><body></tt> tag
+| <tt>frontend/View/hook.body.before.tpl</tt> || Injected before header inside content wrapper
 |-
 | <tt>frontend/View/hook.content.before.tpl</tt> || Injected between header & menu and page content
@@ Line 49: / Line 49: @@
 | <tt>frontend/View/hook.content.after.tpl</tt> || Injected between page content and footer
 |-
-| <tt>frontend/View/hook.body.after.tpl</tt> || Injected just before <tt></body></tt> tag
+| <tt>frontend/View/hook.body.after.tpl</tt> || Injected after footer inside content wrapper
 |}

@@ Line 1: / Line 1: @@
 {{TOCright}}
 == Configuration ==
@@ Line 108: / Line 113: @@
    Please keep in mind, that there will be by design NO security against unwanted postings like PVLng implements with the API key concept!
 </p>

@@ Line 103: / Line 103: @@
   $api->post( ...
-There will be no conflict with PVLng data storage logic, because PVLng ueses <tt>PUT</tt> requests for that.
+There will be no conflict with PVLng data storage logic, because PVLng uses <tt>PUT</tt> requests for that.
 <p style="color:red;font-weight:bold">

← Older revision		Revision as of 13:03, 13 May 2014
Line 102:		Line 102:

	$api->post( ...		$api->post( ...
		+
		+	There will be no conflict with PVLng data storage logic, because PVLng ueses <tt>PUT</tt> requests for that.

	<p style="color:red;font-weight:bold">		<p style="color:red;font-weight:bold">

@@ Line 106: / Line 106: @@
   Please keep in mind, that there will be by design NO security against unwanted postings like PVLng implements with the API key concept!
   </p>
 [[Category:Internals]]
 [[Category:Software]]
 [[Category:Example]]