Creating a custom archive page

hello


someone mentioned that when a page gets archived in matrix that you can create a custom archive page with a nice message … any ideas on how this can be done… of course assuming it can be done at all.



AH

[quote]
hello



someone mentioned that when a page gets archived in matrix that you can create a custom archive page with a nice message … any ideas on how this can be done… of course assuming it can be done at all.



AH

[/quote]



You can create an asset you want to display for these archived assets and then set the created asset to "Archived Asset" on the details screen of Site Asset. Its sort of works like "redirect".

[quote]
You can create an asset you want to display for these archived assets and then set the created asset to "Archived Asset" on the details screen of Site Asset. Its sort of works like "redirect".

[/quote]



sorry I am a little confused, is this any way different from a Page Not Found…



I found a page like that in my site…

[quote]
sorry I am a little confused, is this any way different from a Page Not Found…



I found a page like that in my site…

[/quote]



Yes they are different. Page Not Found is the customised asset that is served by Matrix on "404" return code. As the note there read "The Asset that gets printed when the URI that the user has entered does not exist". And as of the "Archived Asset" configuration is what you would, in this particular case, be looking at.

Also these 2 different fields can point to the same page if you wish.

We have an 'archive' site, as another site asset in the same instance of Matrix as our public website. It uses a different design to indicate that the content available there is out of date and for archival purposes only.


The problem is, when we move something there and a remap is created, the archive page that Ashish mentions above is returning a 404 error, and is messing with the search results within the main site…



I understand that the 'Page not found' page should return a 404 status code, but shouldn't the archive page return a 'successful' 200 status code?



Any ideas on how to fix this?