From 1757ef1d76240516b0fc218701695d06807b9943 Mon Sep 17 00:00:00 2001
From: brettp <brettp@36083f99-b078-4883-b0ff-0f9b5a30f544>
Date: Thu, 15 Apr 2010 21:32:10 +0000
Subject: Updated docs with a FAQ.

git-svn-id: http://code.elgg.org/elgg/trunk@5754 36083f99-b078-4883-b0ff-0f9b5a30f544
---
 mod/ecml/README.txt | 39 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)

(limited to 'mod/ecml/README.txt')

diff --git a/mod/ecml/README.txt b/mod/ecml/README.txt
index f57dc1b8d..67d452241 100644
--- a/mod/ecml/README.txt
+++ b/mod/ecml/README.txt
@@ -159,3 +159,42 @@ CONTENTS:
 	* If making a custom keyword, avoid underscores in your params.  They
 	look funny.
 
+	* Are disabled keywords in comments still working?  This is probably
+	because a parent view is including comments directly.  For example:
+
+	blog page handler:
+		...logic...
+		echo elgg_view_entity($blog);
+		...logic...
+
+	view object/blog:
+		...logic...
+		echo $blog;
+		echo elgg_view_comments($blog);
+
+	The output of object/blog includes the output of the comments, so if
+	the view object/blog allows the youtube the comments will also be parsed
+	for ECML.  The solution is to keep views for the object and comments
+	separate.
+
+	blog page handler:
+		echo elgg_view_entity($blog);
+		...logic...
+		echo elgg_view_comments($blog);
+
+	view object/blog:
+		...logic...
+		echo $blog
+
+	Alternatively, you can keep the blog and comments in the object view, but
+	pull out the blog into its own view to register with ECML.
+
+	view object/blog:
+		...logic...
+		elgg_view('blog/blog', array('blog' => $blog);
+		...logic...
+		elgg_view_comments($blog);
+
+	view blog/blog:
+		...logic...
+		echo $blog
\ No newline at end of file
-- 
cgit v1.2.3