30 Jul 2012
07 Jul 2011
Link to this post
Thanks for the reply.
We've dealt with the error by coding around it, as you've said. Still, this means that no content rendered by controls that depend upon GetActualCurrentNode() can ever be indexed by the search. It would seem that this is could be a pretty serious drawback for developers creating custom modules and controls that tie pages to custom content together.
For example, we have a custom module that stores restaurant information (name, location, hours of operation, contact info, etc), and have pages in the site structure for each. Usercontrols figure out which page node we're looking at based on GetActualCurrentNode(), load the correct restaurant from our module based on the node path, and render all that info from the module directly to the page. Unfortunately, the limitation you've described with GetActualCurrentNode() means that none of that info will ever be rendered for the search crawler to index it.
We'll keep looking for workarounds. Any chance you can get GetActualCurrentNode() working in index mode in a future release?