We have some Feed Manager instances dating back a couple of years to when we went live. In chasing down broken links, I found a couple of them are appearing because of the Feed Manager aggregate link and the "Add Aggregate Feed Discovery Link To Head" setting.
Any ideas of what I should check or how I can "restore" these broken aggregate links? We're running a build from source as of 5/10. I rebuilt our development environment this morning and the same aggregate link in the dev version of this site works correctly. Very strange.
Example feed manager instance is the Upcoming Events section on the homepage of http://library.escondido.org. The aggregate link for that module (880) should be http://library.escondido.org/aggregator880rss.aspx, but instead:
2012-05-14 15:48:10,508 ERROR 74.62.192.170 - en-US - /aggregator880rss.aspx - mojoPortal.Web.PageNotFoundHttpModule - Referrer(none) PageNotFoundHttpModule handled error.
System.Web.HttpException (0x80004005): The file '/aggregator880rss.aspx' does not exist.
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)