URL Changes with No Forwards/Redirects?

[JasonHinsperger]

I have noticed that the Sybase communities have had the "Sybase" name removed from them.  This has the side effect of changing all URLs that point to the community as well.  As far as I can tell, no forwards have been set up to forward the old 'Sybase' urls to the new non-Sybase URLs.

This means anyone who has saved or referred to a link in those communities over the last year have bad URLs.  I have already had several people ask me where the content has gone.

For example, the URL to a blog post in the SQL Anywhere community was this when the post was created:

http://scn.sap.com/community/sybase-sql-anywhere/blog/2013/05/21/licensing-sql-anywhere-in-virtualiz...

Now, the URL has been updated to this:

http://scn.sap.com/community/sql-anywhere/blog/2013/05/21/licensing-sql-anywhere-in-virtualized-envi...

Is there any chance of getting some forwards/redirects set up for people, or at least a better information page so they don't just get a 404 when trying to get to these pages?

Thanks,

--Jason

[JasonLax]

When the URL of a space is changed, the URLs of blog posts also change.  Document and discussions thread URLs remain the same.

Generally, links withing SCN to those blog posts are updated automatically (i.e. if they were embedded properly).

Redirects are only setup for the space overview page.  As for the content, the majority of visits to content arrive from search, such as Google, and the search engine indexed get updated automatically. 

Please contact your content strategist to inquire about setting up redirects for all the blog posts.