升级umbraco 4博客包时出错
我收到此处概述的错误 http://blog4umbraco.codeplex.com/workitem/5399。该页面表示问题已解决，其中一条评论提供了修改数据类型的 sql 语句。但是，sql语句不起作用。正如帖子中所示，我得到的错误是“无法找到 id 为 71b8ad1a-8dc2-425c-b6b8-faa158075e63 的数据类型”，因此在 cmsDataType 表中搜索此 id 不会返回任何内容，并且没有任何可修改的内容。
我已经从 umbraco 3.0 升级，设法升级到 v4，但虽然我可以在前端看到博客，但尝试在后端编辑帖子时没有问题，但在单击博客帖子时显示错误（错误页面为出现在内容编辑窗格通常出现的右侧）。由于我的下一步是升级到 v4.5.2（在升级到 4.7 的路上），我想知道它是否可以修复，但它没有。我的逻辑选择是升级博客（因为原来的博客是2006年的旧博客包）。所以现在已经搞砸了。 :(
任何人都可以阐明这个问题或告诉我如何升级博客包吗？
I'm getting the error as outlined here http://blog4umbraco.codeplex.com/workitem/5399. The page says the issue has been resolved and one of the comments provides sql statements to modify the dataTypes. However, the sql statements don't work. The error I get, as in the post, is 'Could not find datatype with id 71b8ad1a-8dc2-425c-b6b8-faa158075e63' so searching for this id in the cmsDataType table is returning nothing and leaving me with nothing to modify.
I've been upgrading from umbraco 3.0, managed to get to v4 but whilst I could see the blog on the front end no problem trying to edit a post in the back end was showing an error when clicking on the blog post (error page was appearing on the right where the content edit pane would normally appear). Since my next step was to upgrade to v4.5.2 (on the path to getting to 4.7) I wondered if it might fix up, but it hasn't. My logical choice was to upgrade the blog (as the original blog was the old blog package from 2006). So it's now screwed up. :(
Can anyone throw some light on the issue or tell me how I can get the blog package upgraded?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
你使用什么博客包？您是否尝试过删除该软件包并重新安装？
听起来数据库已损坏。在我继续之前，我会说将其全部备份，以便您有一个尝试和修复它的起点...
然后您可以制作数据节点的包备份，这是在开发人员包下完成的。如果一切顺利，您将能够添加这个包，它会通过别名找出它的数据类型。它不确定是否会火，这就是我说备份的原因。
然后我建议删除已添加数据类型的包（博客）。您也可以在设置下手动执行此操作。
您可以在开发人员->中执行此操作还可以通过选择要备份的内容节点来进行打包。删除并重新添加您的博客包，然后尝试将数据推回到顶部。
what blog package are you using? Have you tried removing the package and reinstalling it?
By the sounds of it the database is corrupt. Before i continue i would say to back it all up so you have a starting point to try and fix it...
You can then make a package back up of your data nodes this is done under developer packages. If all goes well you will be able to add this package and it will figure out what datatype it is by alias.. It is not sure fire and that is why i say back up.
I would then recommend removing the packages(blog) that have added the datatypes. You could also do this manually under settings.
You can do this in developer -> Packages also by picking what content nodes to back up. Remove and then re-add you blog package then try to push the data back over the top.