

Bug bash 1-18-2010-Bug bash 1-18-2010

ARCHIVED

！注意“归档”

This chapter has not been updated for the current version of Orchard, and has been ARCHIVED.

• Archive data is not displayed in all themes (e.g. classic theme, green theme)

• 存档数据不会显示在所有主题中（例如经典主题，绿色主题） *

• Need a "Preview" button for editing pages and posts

• 需要一个“预览”按钮来编辑页面和帖子 *

• (loudej) Need to bring back the "Delete this draft" operation on the page/post editing page (perhaps as a small link to deemphasize it, ala WordPress)

• （loudej）需要在页面/帖子编辑页面上带回“删除此草稿”操作（也许作为一个很小的链接来强调它，ala WordPress） *

• Theme Preview button to be implemented

• 要实现的主题预览按钮 *

• (heskew) Implement Javascript Datetime Picker for post/page scheduling UI

• （heskew）为帖子/页面调度UI实现Javascript Datetime Picker *

• (suhacan-FIXED) Need ability to delete a user in Manage Users

• （suhacan-FIXED）需要能够在“管理用户”中删除用户 *

• (suhacan-FIXED) Bug: /Tags/{tagName} just redirects to /Tags (even when there are content items that tag is attached to)

• （suhacan-FIXED）错误：/ Tags / {tagName}只是重定向到/标签（即使有附加标签的内容项） *

• (suhacan-FIXED)Bug: Tags aren't added to a content item when the content item is first created (edit works fine) Repro: Add a blog post with a tag of "test" and save (and notice there is no tag of "test" on that blog post).

• （suhacan-FIXED）错误：首次创建内容项时，标签不会添加到内容项中（编辑工作正常）Repro：添加标签为“test”的博客文章并保存（并注意没有标签）在该博客文章中的“测试”）。 *

• (heskew-FIXED) Pre-fill comment form with authenticated user name and email <- authenticated user needs a different form (body only, other fields as hidden - include user name) since there's no reason for them to change the user info

• （heskew-FIXED）带有经过身份验证的用户名和电子邮件的预填充注释表单< - 经过身份验证的用户需要不同的表单（仅限正文，其他字段为隐藏 - 包括用户名），因为他们没有理由更改用户信息 *

• (heskew-FIXED) Tags and comments should work for CMS pages (aspect UI should appear on the Edit page admin screen, like for posts)

• （heskew-FIXED）标签和注释应该适用于CMS页面（方面UI应该出现在编辑页面管理屏幕上，就像帖子一样） *

Pri-2 Issues:

Pri-2问题：

• Implement MORE tag support (excerpts) for posts (used on front-end list of posts for a blog)

• 为帖子实施更多标记支持（摘录）（用于博客的前端列表） *

• Validation on comment form (name, email required)

• 评论表格上的验证（姓名，电子邮件要求） *

• Bug: create comment missing name or email -> create view not found.

• 错误：创建评论缺少姓名或电子邮件 - >创建未找到的视图。 *

• Bug: After creating a folder in media, you should get back to the folder where it was created, not to the media root.

• 错误：在媒体中创建文件夹后，您应该返回创建文件夹的文件夹，而不是媒体根目录。 *

• Bug: Uploading a zip full of media did not work but in a weird way (Ask Bertrand for the zip file)

• 错误：上传一个完整的zip文件不起作用，但是以一种奇怪的方式（询问Bertrand的zip文件） *

• Bug: Media image captions do not seem to be persisted. Apply a caption to an image, save, navigate away and back to the image editing page: caption is gone.

• 错误：媒体图片标题似乎没有持久化。为图像应用标题，保存，导航并返回图像编辑页面：标题消失。 *

• Front-end: Get rid of this on blogs list front end (see image screenshot in email)

• 前端：在博客列表前端摆脱这一点（参见电子邮件中的图片截图） *

• Front-end: Clean up on Blog and post details in front-end -- put Edit button and stats above and move blog/post text up (see image screenshot in email)

• 前端：清理博客并在前端发布详细信息 - 将编辑按钮和统计信息置于上方并移动博客/发布文本（请参阅电子邮件中的图片屏幕截图） *

Needs design (admin UI consistency issues): Jonathan and Michael are working on an admin UI proposal to share this week...

需求设计（管理员UI一致性问题）： _Jonathan和迈克尔正在制定一个管理UI提案，以便在本周分享......

• Bulk operations on Manage Blog page (e.g. delete post) (put same drop downs that we have for pages on top of blog list)

• “管理博客”页面上的批量操作（例如删除帖子）（在博客列表顶部为页面添加相同的下拉菜单） *

• Bulk operations on Manage Blogs page, like CMS pages... (put same drop downs that we have for pages on top of blog post list)

• “管理博客”页面上的批量操作，例如CMS页面...（在博客帖子列表顶部为页面添加相同的下拉菜单） *

• Ability to filter posts by published/draft/schedule on Manage Blogs , like CMS pages

• 能够按管理博客（如CMS页面）上的已发布/草稿/计划过滤帖子 *

• How to Unpublish a post on the Manage Blog page? Like CMS pages...

• 如何在“管理博客”页面上取消发布帖子？像CMS页面一样...... *

• Blog Details Page needs UI cleanup (placement, icons need text), also need ability to View blog from here:

• 博客详细信息页面需要UI清理（放置，图标需要文本），还需要能够从这里查看博客： *

• Media list is inconsistent: all other contents have separate edit links. For media, you click on the image name.

• 媒体列表不一致：所有其他内容都有单独的编辑链接。对于媒体，您单击图像名称。 *

• All screens that have bulk actions have a header item in the drop down. Media has delete only (which also redirects to the root)

• 具有批量操作的所有屏幕在下拉列表中都有一个标题项。媒体只有删除（也会重定向到根目录） *

• Bug: Multiple error messages for the same thing (repro: media management, create a folder with an empty name: 2 errors message: 1 top message, 1 field validation)

• 错误：同一事物的多个错误消息（repro：媒体管理，创建一个空名称的文件夹：2个错误消息：1个顶部消息，1个字段验证） *

Pri-3 Issues:

Pri-3问题：

• Finalize this text: Possible text about setting up and managing a blog goes here.

• 最后确定本文：关于设置和管理博客的可能文本在此处。 *

• New Post: helper text for "Tags" (comma-separated)

• 新帖子：“标签”的帮助文本（以逗号分隔） *

• Finalize this text: "X" Allow new comments, Enable to show the comment form. Disabling still allows the existing comments to be shown but does not allow the conversation to continue.

• 完成此文本：“X”允许新注释，启用以显示注释表单。禁用仍然允许显示现有注释，但不允许对话继续。 *

• "Your Site" in Admin header should render Site Name setting instead (should be separate from "preview site" link?)

• 管理员标题中的“您的网站”应该呈现“网站名称”设置（应该与“预览网站”链接分开？） *

• Rename "Manage Folders" to "Manage Media"

• 将“管理文件夹”重命名为“管理媒体” *

Do Later:

再做一次：

• What UI do we want for change ownership? Do we want to display owner textbox on every content item?

• 我们想要更改所有权的UI是什么？我们是否要在每个内容项上显示所有者文本框？ *

• If only one blog, "Manage Blog" goes to blog details page. Else goes to list of blogs (as it is today). May also need a way to get to a specific blog from the admin panel menu.

• 如果只有一个博客，“管理博客”会转到博客详情页面。否则会进入博客列表（就像今天一样）。可能还需要一种从管理面板菜单访问特定博客的方法。 *

Stylesheet applied to TinyMCE content should be style of applied theme.

应用于TinyMCE内容的样式表应该是应用主题的样式。

• Revisit whether we should validate duplicate slugs at publish-time (log a bug for this)

• 重新审视我们是否应该在发布时验证重复的slug（记录一个bug） *

• Uploading an image file should attempt to extract title or subject from embedded meta-data and make those the values for the image name and caption.

• 上传图像文件应尝试从嵌入的元数据中提取标题或主题，并使其成为图像名称和标题的值。 *

• The embed field could have script on focus that selects the whole value (makes it a lot easier to copy).

• 嵌入字段可以在焦点上使用脚本来选择整个值（使复制更加容易）。 *

• The embed field could have a copy button.

• 嵌入字段可以有一个复制按钮。 *

Untriaged:

Untriaged：

• None

• 没有 *

• XMLRPC/LiveWriter support seems to be broken. I found Louis' previous instructions, which said to type "http://localhost:/xmlrpc. However, I tried that and it didn't work. Any ideas?

• XMLRPC / LiveWriter支持似乎被打破了。我找到路易斯先前的说明，其中写着“http：// localhost： / xmlrpc。但是，我试过了，它没有用。有什么想法吗？ *

No repro:

没有repro：

• Tags mysteriously disappeared from my post after I deleted a tag from the tag admin. Can't reproduce it anymore though. (no clear repro for now...)

• 我从标签管理员中删除了一个标签后，标签神秘地从我的帖子中消失了。但是不能再复制它了。 （现在没有明确的责备......） *

DONE:

DONE：

• (erikpo-FIXED)When in an archive page, the archive navigation with the collapsible years should be there too. Here's what I was doing: I clicked on the January 2010 archive link from my blog, then I clicked the "2010" link. That didn't give me a way to get back to January. Two ways this can be fixed is by showing "subarchives" links under where you are (2010 would have a link for January) or you have the full archive menu there at all times (that's probably simpler).

• （erikpo-FIXED）在归档页面中，具有可折叠年份的归档导航也应该存在。这就是我在做的事情：我点击了我博客上的2010年1月归档链接，然后点击了“2010”链接。这没有给我一个回到1月的方法。可以解决的两种方法是在你所在的位置显示“subarchives”链接（2010年将有一月份的链接），或者你总是在那里拥有完整的存档菜单（这可能更简单）。 *

• (rpaquay-FIXED) Attempting to access an incorrectly cased page results in a null ref exception: create a page with the slug "About" (uppercase A) then try to access "/about" (lowercase a).

• （rpaquay-FIXED）尝试访问错误的cased页面会导致null ref异常：创建一个带有“About”（大写字母A）的页面，然后尝试访问“/ about”（小写字母a）。 *

• (erikpo-FIXED) Finish blog archive and remove fake archive data

• （erikpo-FIXED）完成博客存档并删除虚假存档数据 *

• (rpaquay-FIXED) Bug: Exception: When creating a new post (no theme applied) - System.InvalidOperationException: The view 'NotFound' or its master was not found.

• （rpaquay-FIXED）错误：例外：创建新帖子时（未应用主题） - System.InvalidOperationException：未找到视图'NotFound'或其主页。 *

• (rpaquay-FIXED) Bug: Draft posts affect the number of posts listed for a blog (on front-end and back-end)

• （rpaquay-FIXED）错误：草稿帖子会影响为博客列出的帖子数量（在前端和后端） *

• (suhacan-FIXED) Bug: When saving a draft post, should redirect to/Edit admin URL for that post

• （suhacan-FIXED）错误：保存草稿帖子时，应重定向到/编辑该帖子的管理员URL *

• (suhacan-FIXED) Bug: When publishing a post from the "edit post" page, should redirect to the list of posts

• （suhacan-FIXED）错误：从“编辑帖子”页面发布帖子时，应该重定向到帖子列表 *

• (suhacan-FIXED) Bug: Post Publishing Now button on Blog Details page throws 404 error

• （suhacan-FIXED）错误：“博客详细信息”页面上的“立即发布后发布”按钮引发404错误 *

• (heskew-FIXED) Blog slug generation: "!!!Brad's Blog!!!" -Brad-s-Blog- (remove beginning/trailing slashes)

• （heskew-FIXED）Blog slug generation：“!!! Brad的博客！” -Brad-s-Blog-（删除开头/尾部斜杠） *

• (heskew-FIXED) Blog slug generation: "todo: (heskew) need path to here"

• （heskew-FIXED）Blog slug generation：“todo :( heskew）需要通往这里的路径” *

• (heskew-FIXED; still need to be selective on when to show the manage bits) When I'm on a post's front-end page, logged in as an admin/author/owner with the default blue theme, I don't have a direct link to edit the post.

• （heskew-FIXED;仍需要选择何时显示管理位）当我在帖子的前端页面上，以默认蓝色主题的管理员/作者/所有者身份登录时，我没有编辑帖子的直接链接。 *

• (rpaquay-FIXED) Page front-end has weird URLs: http://localhost:30320/Pages/Page/Item?slug=About (it used to work) (heskew: ISlugConstraint functionality hasn't been hooked up since cms pages migration)

• （rpaquay-FIXED）页面前端有奇怪的URL：http：// localhost：30320 / Pages / Page / Item？slug =关于（它曾经工作过）（heskew：ISlugConstraint功能自cms页面以来还没有被连接起来移民） *

• (rpaquay-FIXED) Why do published posts still say "Draft" on the blog front-end page? (bug <- related to create as published problems?)

• （rpaquay-FIXED）为什么发布的帖子仍然在博客前端页面上说“草稿”？ （bug < - 与创建发布的问题有关吗？） *

• (rpaquay-FIXED) Implement "true" versioning for blog posts (we currently only keep the latest version of posts in the DB)

• （rpaquay-FIXED）为博客文章实现“真实”版本控制（我们目前只在数据库中保留最新版本的帖子） *

• (heskew-FIXED) We need to use IDs instead of slugs for admin URLs where slugs aren't guaranteed to be unique

• （heskew-FIXED）我们需要为管理URL使用ID而不是slugs，其中slug不能保证唯一 *

• (rpaquay-FIXED) Implement "?? comments" on: Manage Blog (for blog), Blog Details Page (for posts in a list) - both admin and front-end (for now we are going to append aspect UI in some deterministic order at some placeholder in a template, similar to what we do for aspects on a content item editor today). Will tackle the bigger problem of UI composition and placement within a template later (not sure if before Mix?). "xx Comments" in admin for blog post summary should be a link to comments page filtered on the blog post. FIX COMMENTS ON BLOG POST TO BE CONSISTENT! (Punt on blog for now)

• （rpaquay-FIXED）实现“??评论”：管理博客（用于博客），博客详细信息页面（用于列表中的帖子） - 管理员和前端（现在我们将在某些确定性中附加方面UI在模板中的某个占位符处订购，类似于我们今天对内容项编辑器的方面所做的操作）。稍后将解决模板中UI组合和放置的更大问题（不确定是否在Mix之前？）。 admin for blog post summary中的“xx Comments”应该是在博客文章中过滤的评论页面的链接。在博客上发布一致的评论是一致的！ （暂时在博客上发布） *

• (rpaquay-FIXED) FIX COMMENTS on blogs (same as posts, but aggregated for blogs)

• （rpaquay-FIXED）在博客上修改评论（与帖子相同，但为博客汇总） *