the Browse element

[Damon]

What would I need to do to show the headline of the next article in the browse link below?  I tried bracketing it within a dynamic block but that didn't work.

<!IoRangeConditional><a  href="<%brs_Next%>"><%hdl_Headline%> &rarr;</a><!/IoRangeConditional>

[Damon]

Hmmm, is this the best practice?

https://groups.google.com/forum/#!topic/reddot-cms-users/gUJxldkuiLg

[Tony Chung]

If you don't care that search engines and non-javascript enabled computers can find the title, sure.

-Tony

-- 

[Tim D]

Do you use Navigation Manager?

[Damon Sit]

H

i Tim, 

I do but my content pages aren't indexed, only the pages used for navigation.   Should they be?  Awhile I back I was lead to believe to leave content pages outside of the navigation structure.

--
You received this message because you are subscribed to a topic in the Google Groups "RedDot CMS Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/reddot-cms-users/U56p0c4h7WI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to reddot-cms-use...@googlegroups.com.
To post to this group, send email to reddot-c...@googlegroups.com.
Visit this group at http://groups.google.com/group/reddot-cms-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Tim D]

You can leave them out. However, if the pages were in navigation you could perhaps use a new render area and navigation templates to display the next item, it may be pretty complex. I think you want to "pull through" additional fields not a feature of the browse element. I believe there is another way to do this with rendertags similar to this: https://groups.google.com/d/topic/reddot-cms-users/tRaUZ6nu_HM/discussion you may end up in the cache situation Jian warns of.

[Damon Sit]

Thanks Tim.  Using navigation manager for everything would make my life easier.  Are there any serious downsides to including all my content in it?  I have another similar issue where I would like to show other items in a specific list that could be solved with 1 renter tag, as opposed to making a few containers and referencing them.

[Jian Huang]

Hi Damon,

Navigation manager was written to manage and render navigation.  Just like a database or lookup table, you want to keep it as small as possible.  For example, a site with 2000 pages, not all 2000 pages are navigational pages whose links are outputed in a navigation area, so there is no reason to have 2000 pages in navigation manager; and when it is time to output a navigation, 75% (assume 75% of the 2000 pages are to be skipped) of the rendering operations are spent on if (dont show in nav) skip.  It is a major performance issue as I have seen in many customer's projects.  I have seen publication, SmartEdit view and page preview performance increase of 30%-50% just by removing those article or new pages out of navigation manager.

Also, as the size of navigation structure grows, and more not yet trained users get into the project, navigation pages begin to get connected to multiple site sections, and that is when you start getting bug tickets like "a site section just, out of its own, disappeared in A...couple of hours later, I found it in B...WHY DOES IT DO THIS?  I AM SCARED."  Then you will be forced to try to NUKE button (reset navigation index), which is a nice thing to do on a project with a small navigation structure (300-500 pages no problem and no uh oh moments).

"I have another similar issue where I would like to show other items in a specific list that could be solved with 1 renter tag, as opposed to making a few containers and referencing them."

A list can pull element data from follow page, similar to the foreach rendertag, just without the memory cost and known issues.  Unless you are try to pull data from grandchildren pages, but there are also native blockmark solutions.

Best regards,

-Jian

[Damon Sit]

Jian,

Thank you for that well-detailed reply.  I'll proceed with that in mind and and also stick with a list for my other issue.

-Damon