10
You need to make a choice between static and dynamic linking:
The advantage of dynamic links is that if you move the search page, the link URL is updated automatically. however, in your case using static links is not so bad if the search page is never going to be moved or unpublished (which seems likely to be the case) - especially if there are many ...
7
The DXA Web App has to be configured for Category/Taxonomy-based navigation too; OOTB it uses a so-called Static Navigation Provider and for Taxonomy-based Navigation you need the Dynamic Navigation Provider.
The Dynamic Navigation Provider looks for a published Taxonomy with [Navigation] in its title and if it doesn't find it, it falls back to SG-based ...
5
Taxonomy, like Folders and Structure Groups, does not have versioning functionality from Tridion.
If you would like to know who changed what and when, without rolling back, it is fairly simple. You would write an Event System class that listens for the Save Keyword event and writes this info to a DB (OrmLite, SQLite, MongoDB, etc) and then write an asp.net ...
3
What you want to avoid here is having to republish every page each time the navigation changes. It sounds like you are including the navigation as a TBB in each page, which is inefficient.
In this situation, in my mind anyway, you want the navigation to be a page in its own right. You can then include that in your page template (via a JSP/.NET include or ...
3
Your webpage is dynamic so you can probably build the link yourself using the tridion api directly (rather than a tag as you are above) - doing so will most likely be really fidly but for something a bit more robust you could write your own custom tag, you'll find more information about creating a custom tag here: http://sdllivecontent.sdl.com/LiveContent/...
2
You need to have Content Delivery to resolve Component links and Page links on the website.
On Navigation TBB, you need to render the hyperlinks in the form of TCDL tags. Where Content deployer will change TCDL tags cooresponding to your Component Link and Page Link Controls on the published page.
2
if i understand your questions right & you are using a .net solution. you can give try to following.
You can publish XMl of your navigation in .sitemap format
Create UserControl and use the asp:menu control in that usercontrol
Add that user control to your master page
examples:
Xml format
<?xml version="1.0" encoding="utf-8" ?> <siteMap
...
2
This would need to be custom functionality as Rob already mentions in his answer. I'd like to add that you can store your custom versioning data in AppData for each keyword. No need for a custom DB.
1
Are you using DXA's OOTB navigation or do you have a custom solution for generating the navigation?
Furthermore, are we just talking navigation here, or do you want to affect the actual URLs of the pages?
In its current form, the question is quite vague, so the answer I can give you will be as well. I am assuming this is for navigation only as you cannot ...
1
You can create your own navigation component template with an include page and have it included in your page template with your own custom module and controller.
In your entity view, you can add to or replace the linkUrl with your redirect pages, based on the inputs from your include page which should now be available in the default model.
You may also ...
1
Not really sure what you mean with "it only fails in the publication that save information in DataBase, in the rest of publications works", but the fact that you get a timeout during rendering of aprox. 500 Structure Groups sounds like you might have a database maintenance issue to start with.
Furthermore a Publish Transaction taking 1 hour really sounds ...
Only top voted, non community-wiki answers of a minimum length are eligible