Developer forum

Forum » Swift » Default sitemap setup

Default sitemap setup

Anders Ebdrup
Anders Ebdrup
Reply

Dear Dynamicweb,

 

It will be nice to have the right settings on each page telling whether a page should be available in the sitemap (and internal search as well) or not.

And I can see that the pages from "tools" menu is not shown in the sitemap.

 

Best regards,

Anders


Replies

 
Cristina Santos
Reply

Hello Anders,

How did you get those pages  from "tools" menu to appear in the sitemap?

I'm trying all the settings and I can't get it...

Thank you in advance!

Best regards

Cris

 
Anders Ebdrup
Anders Ebdrup
Reply

Hi Cristina,

 

Nope, and I am still wating for a response here.

 

Best regards,

Anders

 
Cristina Santos
Reply

Hi Anders,

We have tried putting the modified sitemap.xml file in the Application folder (where the web.config file is), but it still reads the "bad" sitemap.

Do you know in which path dynamicweb saves the sitemap file to replace it?

or how to configure website so that our file inside de Application folder was the main sitemap?

Thank you!!

 

 
Cristina Santos
Reply

Anders, 

The problem is that the page is placed in a folder. These by default don’t get sitemap.

As workaround if this is urgent, just move the page outsite the folder to the page tree and you will see it gets in the sitemap

This was told to me by support.

All the best!

 
Christoffer Rosendahl Frede
Reply

Hi everyone.

But if pages in folder's is not allowed in the default sitemap, why are all the pages on the swift demo/installations put in folder's ?

that seems really bad that the starting point has the wrong setup, if that is the case.

Does anyone know if this is fixed by changing all the folders in a swift solution, to pages and that there is no drawback to this ?

/best regards Christoffer

 
Anders Ebdrup
Anders Ebdrup
Reply

Dear Swift-team,

 

Can you please update us on this one?

 

Best regards, Anders

 
Nicolai Pedersen
Reply

We cannot do that before we change the internals of how this works - and that is currently in slow progress (works on my machine)

  1. Use new URL provider to create sitemap XML - this has been made and is on its way.
  2. Change the navigation viewmodel setup so it will include all nodes in the tree with information about if it is folder, show in sitemap or something else
    1. Create a custom sitemap.xml.cshtml file that will filter out the pages that is not wanted

@1:

Will look like this:

It will not use the page tree to generate the sitemap. It will use the requesting domain to find all areas that fits to that domain, and then itereate the first 50.000 urls in those URL indexes and print it out. This only works if the new URL providers are used. Probably not perfect, but better.

@2:

There is a change to navigation system. So when using GetNavigation method, you can now pass in a setting on the navigation settings "IncludeFoldersAndHidden" that, when set to true, will return all nodes in the tree no matter what.

Then the NavigationTreeNodeViewModel has 3 new properties "ShowInMenu", "ShowInBreadcrumb" and "ShowInSitemap".

In a custom sitemap.xml.cshtml file the navigation system can be queried and you can do whatever you think is correct.

Thoughts?

BR Nicolai

 
Anders Ebdrup
Anders Ebdrup
Reply

Dear Nicolai,

 

I think this will be a great solution which we will be looking forward to :-)

 

Best regards, Anders

 

You must be logged in to post in the forum