> -----Original Message-----
> From: Stephen Collins [mailto:[EMAIL PROTECTED]]
>
> I am building a site navigation tree using a combination of
> CFA_TREE/CFA_TREEITEM and CFA_SITEELEMENTGETCHILDREN. I have
> the tree fully functional on the test/development box, but
> have navigated the content object store and .cfm files to the
> prod server (not yet available to the client) in order to get
> the site up and running. Trouble is, when the code tries to
> build the tree on the prod box, it craps out after building
> the first level with the error:
>
> Error Occurred While Processing Request
> Error Diagnostic Information
> ERROR: containers can not have children in the site model.
By looking at the customtag.
\\ServerXX\spectra\customtags\system\tier1\sitemodeling\cfa_siteelementgetch
ildren.cfm
.. it seems like you for some reason or another do now have a _container_ in
the site object model (SOM).
Having not experienced the same myself I can't answer why, but if you were
to run the following code on your two servers and compare the results,
hopefully it should help you on your way.
`<cfloop
collection="#server.cfa.sitemodel[request.cfa.datasource.dsn].sections#"
item="i">
` <cfif len(i) gt 6 and right(i,5) eq "props">
` <cfset objectuuid = left(i,35)>
` <cfa_dump
var="#server.cfa.sitemodel[request.cfa.datasource.dsn].sections[i]#">
` <cfoutput><p></cfoutput>
` </cfif>
`</cfloop>
` means the following is supposed to constitue one line; all outlook
enforced linebreaks are to be edited out ;)
The above will loop through the entire site struct and show the relevant
data for each node; I found by using the dump that all the keys ending with
"_props" constitute a category/node in the SOM.
On the topic of the Site Object Model:
Now, I'd really like to see more _standard_ PITA tags for working with the
SOM - GetChildren is currently the only one... To rectify I've created a
customtag that returns any of the properties, such as the parent ID or the
absolute path. Next, I found that creating an object type for extended
category properties (eg. sort order, graphics file, bVisible) and storing a
searchable UUID for the SOM objectid allowed me to extend the SOM into
something more practically useful. I hope Version 2.0 will bring more
functionality on this quite practical level. Writing fully static, "hard
coded" menus is something I last did ... umm ... 5 years ago. ;)
J�rgen
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebarRsts&bodyRsts/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
