A customer is asking if there is anything we can do to remove "/Pages" from his Internet-facing MOSS publishing site. Some Googling reveals that some clever use of HTTPModules may be able to hide the presence of Pages, but I've yet to see an end-to-end working solution. Have any of you come up against this particular requirement, and if so, how did you resolve it?
客户询问我们是否可以采取任何措施从其面向互联网的MOSS发布网站中删除“/ Pages”。一些谷歌搜索显示,一些巧妙使用HTTPModules可能能够隐藏页面的存在,但我还没有看到端到端的工作解决方案。你有没有人反对这个特殊要求,如果有,你是如何解决的?
The customer's main concern with /Pages is the SEO impact of it - if anyone has any way to mitigate those issues or can explain why having this extra level in your URL would not be a concern, that would be appreciated as well (and probably better, in the long run!)
客户对/ Pages的主要关注点是它对SEO的影响 - 如果有人有任何方法可以缓解这些问题,或者可以解释为什么在你的URL中有这个额外的级别不会成为一个问题,那也是值得赞赏的(也许更好) , 长期来说!)
5 个解决方案
#1
Check out this posting. http://blog.mastykarz.nl/semantic-urls-in-moss-2007-imtech-sharepoint-semantic-urls-free-feature/
看看这个帖子。 http://blog.mastykarz.nl/semantic-urls-in-moss-2007-imtech-sharepoint-semantic-urls-free-feature/
#2
The main issue you'll have is that Microsoft won't provide support for a SharePoint instance that has "hidden" the pages library.
您将遇到的主要问题是Microsoft不会为“隐藏”页面库的SharePoint实例提供支持。
Yes, you can use a URL re-writer to exclude the /pages section of the path, and you will also need to perform a search and replace on the response stream to strip it out of all generated URLS - this will obviously have a performance hit on the server - but with careful use of caching, it might not be that noticable.
是的,您可以使用URL重写器来排除路径的/ pages部分,并且您还需要在响应流上执行搜索和替换以将其从所有生成的URL中剥离 - 这显然会有性能点击服务器 - 但仔细使用缓存,可能不是那么明显。
PSS will require you to remove the setup before they will investigate any issues with your site, so you (or your client) will need to weigh up the perceived benefits with the performance and support issues.
PSS将要求您在调查您的网站的任何问题之前删除设置,因此您(或您的客户)需要权衡感知的好处与性能和支持问题。
I believe we've done it for one of our clients in the past, but most are happy to stick with the /pages element - it really doesn't have that much effect.
我相信我们过去曾为我们的客户做过这件事,但大多数人都乐于坚持使用/ pages元素 - 它实际上并没有那么大的影响。
#3
I know ASP.NET 3.5 SP1 has the URL routing engine that ASP.NET MVC uses built in. If you wanted to run against that version of the .NET framework, you could use routes to eliminate the /Pages part of the URL. But I'm not positive about running MOSS on that version of .NET. That's the first place I'd check, though.
我知道ASP.NET 3.5 SP1具有ASP.NET MVC内置的URL路由引擎。如果您想针对该.NET版本的框架运行,您可以使用路由来消除URL的/ Pages部分。但我对在该版本的.NET上运行MOSS并不乐观。不过,那是我要检查的第一个地方。
#4
You can get a list of public facing websites using MOSS here. You can see they use the "page" libraries and you can check your favorite search engines against the content. Hopefully this will be enough to demonstrate that the "Page" libraries aren't going to be too much of an issue and you can save them a bunch of cash.
您可以在此处使用MOSS获取面向公众的网站列表。您可以看到他们使用“页面”库,您可以根据内容检查您喜欢的搜索引擎。希望这足以证明“页面”库不会出现太多问题,你可以为它们节省大量现金。
#5
You can change the name (and the url) of the /Pages library.
您可以更改/ Pages库的名称(和URL)。
#1
Check out this posting. http://blog.mastykarz.nl/semantic-urls-in-moss-2007-imtech-sharepoint-semantic-urls-free-feature/
看看这个帖子。 http://blog.mastykarz.nl/semantic-urls-in-moss-2007-imtech-sharepoint-semantic-urls-free-feature/
#2
The main issue you'll have is that Microsoft won't provide support for a SharePoint instance that has "hidden" the pages library.
您将遇到的主要问题是Microsoft不会为“隐藏”页面库的SharePoint实例提供支持。
Yes, you can use a URL re-writer to exclude the /pages section of the path, and you will also need to perform a search and replace on the response stream to strip it out of all generated URLS - this will obviously have a performance hit on the server - but with careful use of caching, it might not be that noticable.
是的,您可以使用URL重写器来排除路径的/ pages部分,并且您还需要在响应流上执行搜索和替换以将其从所有生成的URL中剥离 - 这显然会有性能点击服务器 - 但仔细使用缓存,可能不是那么明显。
PSS will require you to remove the setup before they will investigate any issues with your site, so you (or your client) will need to weigh up the perceived benefits with the performance and support issues.
PSS将要求您在调查您的网站的任何问题之前删除设置,因此您(或您的客户)需要权衡感知的好处与性能和支持问题。
I believe we've done it for one of our clients in the past, but most are happy to stick with the /pages element - it really doesn't have that much effect.
我相信我们过去曾为我们的客户做过这件事,但大多数人都乐于坚持使用/ pages元素 - 它实际上并没有那么大的影响。
#3
I know ASP.NET 3.5 SP1 has the URL routing engine that ASP.NET MVC uses built in. If you wanted to run against that version of the .NET framework, you could use routes to eliminate the /Pages part of the URL. But I'm not positive about running MOSS on that version of .NET. That's the first place I'd check, though.
我知道ASP.NET 3.5 SP1具有ASP.NET MVC内置的URL路由引擎。如果您想针对该.NET版本的框架运行,您可以使用路由来消除URL的/ Pages部分。但我对在该版本的.NET上运行MOSS并不乐观。不过,那是我要检查的第一个地方。
#4
You can get a list of public facing websites using MOSS here. You can see they use the "page" libraries and you can check your favorite search engines against the content. Hopefully this will be enough to demonstrate that the "Page" libraries aren't going to be too much of an issue and you can save them a bunch of cash.
您可以在此处使用MOSS获取面向公众的网站列表。您可以看到他们使用“页面”库,您可以根据内容检查您喜欢的搜索引擎。希望这足以证明“页面”库不会出现太多问题,你可以为它们节省大量现金。
#5
You can change the name (and the url) of the /Pages library.
您可以更改/ Pages库的名称(和URL)。