Index: openacs-4/packages/search/www/doc/guidelines.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/search/www/doc/guidelines.adp,v diff -u -r1.1.2.2 -r1.1.2.3 --- openacs-4/packages/search/www/doc/guidelines.adp 25 Aug 2015 18:02:23 -0000 1.1.2.2 +++ openacs-4/packages/search/www/doc/guidelines.adp 5 Jul 2016 16:52:02 -0000 1.1.2.3 @@ -13,19 +13,19 @@ In most of the cases, choosing the object type is straightforward. However, if your object type uses the content repository then you should make sure that your object type is a subclass of the -"content_revision" class. You should also make sure all content is -created using that subclass, rather than simply create content with -the "content_revision" type. +"content_revision" class. You should also make sure all +content is created using that subclass, rather than simply create +content with the "content_revision" type.
acs_object_type__create_type
, but those that use the
CR need to use content_type__create_type
.
content_type__create_type
overloads
acs_object_type__create_type
and provides two views
for inserting and viewing content data, and the CR depends on these
views.datasource
and url
. The specification for
@@ -70,9 +70,9 @@
That is, change impl_name
with your object type and
the impl_owner_name
to the package key. Next, you have
to create associations between the operations of
-FtsContentProvider
and your concrete functions. Here's
-how an association between an operation and a concrete function
-looks like:
+FtsContentProvider
and your concrete functions.
+Here's how an association between an operation and a concrete
+function looks like:
select acs_sc_impl_alias__new(
'FtsContentProvider', -- impl_contract_name
'note', -- impl_name
@@ -91,7 +91,7 @@
then you are done. If not, an extra step is required to inform the
search_observer_queue of new content items, updates or deletions.
We do this by adding triggers on the table that stores the content
-items of your object type. Here's how that part looks like for
+items of your object type. Here's how that part looks like for
note
.
create function notes__itrg ()
returns opaque as $$