Forum OpenACS Q&A: Re: site-map problems with aolserver 4

Collapse
Posted by Vinod Kurup on
The latest AOLserver 4 CVS has fixed the 'return no data' problem. Instead, it properly returns a 500 error, so now adding a subfolder to the sitemap errors out in all browsers. At least it's consistent now 😊 So we need to find out why the error is happening in the first place.

I haven't found any spots which match Andy's bug report for the nsv problem (but I haven't looked exhaustively yet). Here's what I do know:

Adding a folder to the site map calls site_node::update_cache which runs this bit of code:


ns_eval {
    global tcl_site_nodes
    if { [info exists tcl_site_nodes] } {
        array unset tcl_site_nodes "${node(url)}*"
    }
}
According to the docs, ns_eval is meant to maintain global vars across interpreters. But, this is the only place in the toolkit that ns_eval is used. Usually we use nsv's to maintain info across interps, right? Getting rid of the ns_eval brackets solves the problem. Does it make sense to switch to a nsv in this case?