Forum OpenACS Q&A: Trying out CMS... am I doing it right?

Collapse
Posted by Jun Yamog on
Hello,

I am trying to poke again on CMS.  I have poked around it about 3
months ago.  Now I am trying it again seems to work now.  Since I was
able to try CMS early on I was able to make my site contents almost
CMS ready.  I initially used templating and sub sites to make the
pages of my site.  /about/content.adp only contained just contents and
some properties while /templates/site_master.adp & .tcl is a template
that renders the page according to the url of the content.

site_master.tcl has some logic on it and a handful of string assignments
that used on site_master.adp.  Now that I have put the contents on CMS
I made another template cms_master.adp and cms_master.tcl.
My main concern is that since the lack of examples I would like to
know if I am using CMS correctly.

Are these steps correct?

- upload /about/content.adp to a CMS basic item

- upload the cms_master.adp

- change the "set a value" on site_master.tcl to "request set_param a
-datatype text -value value"

- register cms_master to the content item

- set to live and publish to plain old html.

I do get the rendered finished html.  I really dont know if "request
set_param..." is the way to pass values to my adp template?  I have
read the docs but I still cant yet understand fully the child,
relation tags.  Anybody care to explain them better?

BTW if DanW is reading this, I am not sure but there may be a bug
publish::set_publish_status as the call to publish_revision does not
get the publish_roots on the CMS parameters.  So I pass the optional
parameter "-root_path [get_publish_roots]".  Also multiple
publish_roots does not work as expected.  Not sure if this is a bug or
I may not be using CMS correctly.

Collapse
Posted by Dan Wickstrom on
Yes, you're correct.  publish::publish_revision is not working correctly due to a problem with the initialization of  opts(root_path).  I'm going to try and take a look at this later this week.
Collapse
Posted by Dan Wickstrom on
I fixed the problem with publish_revision, and I also fixed the problem with multiple publishing roots.  It turns out that there was also a bug in publish::foreach_publish_path.
Collapse
Posted by Jun Yamog on
Thanks Dan.  I will try to send you out more email to help out.... Dont you just love this community?