Index: openacs-4/packages/acs-content-repository/www/doc/guide/items.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/guide/items.adp,v diff -u -r1.4 -r1.5 --- openacs-4/packages/acs-content-repository/www/doc/guide/items.adp 30 Apr 2018 08:15:07 -0000 1.4 +++ openacs-4/packages/acs-content-repository/www/doc/guide/items.adp 3 Sep 2024 15:37:31 -0000 1.5 @@ -1,9 +1,13 @@ -{/doc/acs-content-repository {ACS Content Repository}} {Content Repository Developer Guide: Creating Content +{/doc/acs-content-repository/ {ACS Content Repository}} {Content Repository Developer Guide: Creating Content Items} Content Repository Developer Guide: Creating Content Items +

Creating Content Items

Content Repository : Developer @@ -12,8 +16,7 @@

Content items are initialized using the content_item.new function. A name is the only parameter required to create an item:

-
-item_id := content_item.new( name => 'my_item' );
+
item_id := content_item.new( name => 'my_item' );

The name represents the tail of the URL for that content item. In most cases you will want to create items in a particular context with the repository hierarchy:

@@ -45,8 +48,7 @@

If a content item has at least one revision, then it can be published by calling the content_item.set_live_revision procedure, which takes as input a revision_id:

-
-content_item.set_live_revision( revision_id => :revision_id );
+
content_item.set_live_revision( revision_id => :revision_id );

karlg\@arsdigita.com

Last Modified: $‌Id: items.html,v 1.2 2017/08/07 23:47:47 gustafn