When you edit an article with IE and select the HTML editor, you have a Find button, which includes Find and Replace functionality. This is not available if you edit the article with Firefox. This makes it difficult to fix TOC and color issues using Firefox. You cannot search for "<h" in the HTML to find headings for the TOC, or replace "rgb(0, 0, 255)" with "blue" to fix color issues. STATUS: 08/09/2013 Still exists FireFox 23.0
Add additional known issues at the bottom of this section.
WORKAROUNDS: Search in your browser on Bing Search. Include "TechNet Wiki" along with the title you're searching for.
STATUS: Verified 05/30/2013. Cannot find newly published articles unless they are more than about 1 month old.
If the search results includes one more Wiki article than will fit on one page of results, there may be no link to the second page.
STATUS: Verified 06/13/2013. As of this date, the following tag search results in 13 articles, but there should be 14. http://social.technet.microsoft.com/wiki/tags/rlmueller/default.aspx This tag search results in 12 articles, but one of them (the last) does not appear in the first results (as it should): http://social.technet.microsoft.com/wiki/tags/rlmueller/active+directory/default.aspx
WORKAROUND: To fix the symptoms of this bug, click the HTML View tab, find the section that begins the indentation in the code, and make sure there is a closing ordered list </ol> or unordered list </ul> tag above it. STATUS 08/23/2012: This problem is seen often. Generally, a closing </li> tag (less often </ol> or </ul>) was missing, and the Wiki editor "fixed" the HTML by adding the missing tag, but in the wrong location. Often, the </li> tag is added after the next heading line, so the heading line is indented. Sometimes, the </li> tag is added after the next list, so the entire list is indented relative to the first list. In all cases, the fix is to move the errant </li> tag in the HTML editor. I check the last item in each list. If the last item does not have a closing </li> tag, I search for the next </li> tag, verify that it is in the wrong place, then move it to where it belongs. STATUS: Bug verified 05/29/2013. Also using the Indentation button causes everthing, including text before and after the text you are working on, to be indented. And it is very difficult to add subsequent text that is not indented.
WORKAROUND: You'll need to remove the title text from the <a name> argument. For example, if your HTML is... <h2><a name="Title1">Title1</a></h2>... then you need to remove the text from the <a> tag. Instead write it like this: <h2><a name="Title1"></a>Title1</h2>. Also, do not add anchors to your article. Instead, just use headers. At the top of your article, type the wiki code [toc] in the Design tab, and the Wiki platform will turn the text into a table of contents that lists out all the header sections, including their hierarchy (where an h2 is indented under an h1 section). Because of this TOC feature, you don't need to add anchors.
STATUS: Bug verified 05/29/2013. But is this a problem?
WORKAROUND: Do not highlight/select the whole line. Highlight/select only the text and not the space after the text (which is what happens to show you that the whole line is highlighted/selected). If you cannot highlight only the text, highlight all the text except for the last letter. Then when you click the Insert Link or Anchor button from the Editor toolbar, add the missing letter back to the text in the Link Text box, enter the new URL, click OK, and when you return, delete the last letter that is not in the hyperlink.
STATUS: Bug verified 05/29/2013. Also, on each subsequent save a new blank bullet item can be added to the collection, and a new symbol indicating an external url can be added to the previous bullet item (the item before the one made into a hyperlink).
WORKAROUND: See Create Quick and Basic Tables Using the Wiki HTML Editor for information about creating tables using the Wiki HTML editor. This method requires that you edit the raw HTML for your article by clicking the <> HTML option in the status bar at the bottom of the Wiki Editor. STATUS: Bug verified 06/12/2013. Besides losing colors, tables can get cut off. The table in the article does not appear like the table in the editor. For example, in revision 3 of this article, Choose your MAP Toolkit Goal, the table is cut off at the right. The colors were also lost, but were restored by replacing RGB values with color names in the HTML.
WORKAROUND: When your article gets into this state (you are waiting for it to save for a long time), click the Save button again. If you see the error message that you already updated the article, then click the Article tab to see your changes. Your changes were saved correctly.
Another problem is duplicate header lines in the article. The text of header lines can be duplicated in an article, and all will appear in the Table of Contents, but the links will not work. Duplicate header lines will have duplicate <a name> tags, so all of the duplicate entries in the Table of Contents will link to the same point. The fix is to modify the <a name> tags of the headers in the HTML editor to make the names of the anchor tags unique in the article. A duplicate header line can result unexpectedly if the header has leading digits. When the <a name> tag is automatically created, any leading digits are ignored. This means that the headers "1.3 References" and "3.3 References" will have the same <a name> tag. You must edit the <a name> tags in the HTML editor to make them unique. Digits can appear anywhere else in the <a name> tag with no problems. For example, you can modify the tags as follows: <a name="References_1_3"> and <a name="References_3_3">. Note that spaces and periods must be replaced by underscores. These <a name> tags will be recognized. Of course, do not introduce zeros (the character "0"). A less common problem is when the entry in the Table of Contents includes the heading line plus all or part of the next paragraph. The cause is a missing </h1> tag (or </h2> etc). The Wiki editor adds the missing tag when you save, but in the wrong location; not at the end of the heading line, but after the next sentence or paragraph. The fix is to find the heading line in the HTML editor, verify that the terminating </h1> tag is missing (or </h2> etc), then find the next </h1> tag in the article and move it to where it belongs. For assistance fixing a Table of Contents, refer to this Wiki article: Tips & Tricks to Fix the Wiki Article [TOC] (Table of Contents)
STATUS: 1/Aug/2012, BUG REPORT FILED, and bug confirmed. Last seen in May, 2013.
WORKAROUND: Sadly, the workaround is to use non-Microsoft browsers, such as Firefox or Chrome. STATUS: 07/11/2013. This problem happens if you edit using Internet Explorer, but not if you use Firefox or Chrome to edit the article. In fact, if you edit an article with "broken" colors in Firefox or Chrome, even if you make no changes, the colors will be restored after you save. Of course, the RGB values will remain in the HTML (which is not affected by this), so if someone else edits the article later using Internet Explorer, the colors will be lost. 07/23/2013 Confirmed Confirmed Confirmed
WORKAROUND: You can actually paste it from another place in the article (where it's already working). That's what I did to get the blockquote indentation on this line to work properly. If you don't have one to copy and paste in from the same article, you can go into the HTML. The problem is usually that the Blockquote tag is on the wrong side of the Paragraph (<p>) tag, thus it's indenting everything in your P tag, which is often everything under your header. So you have to move the Blockquote tag inside of your P tag. NOTE: I have not seen this bug in the blogs. STATUS: Verified 8/14/13. If we upgrade to the blogs editor (slated for end of summer, 2013), then we might get this fixed with the upgrade (since it's not an issue in the blogs).
WORKAROUND: You have to tweak it in the HTML. It's often a mismatched tag between the OL (Ordered List) and UL (Unordered List) tags. You might also be able to fix it in the Editor... delete each bullet (keep the text on the lines but delete the bullets by pressing Backspace at the front of each bullet)... except for the top one and then press enter, pushing each line down in the same OL tag that your top item is in. STATUS: Verified 8/14/13
WORKAROUND: It's an HTML mismatch between the tags. You can go in the HTML tab and remove the embedded UL tag, or you can fix it in the Editor. In the Editor, at the front of the top bullet under the corrupted bullet, press Backspace until it's on the line of the uncorrupted bullet above the corrupted one. Then press Enter to push that line back down. You created a new bullet above the corrupted one. Keep doing this for each bullet under the corrupted one. Usually, when you get to a Level 1 or even Level 2 bullet, the corrupted bullet gets cycled out. Then you can format them correctly with the proper indentations. STATUS: Verified 8/14/13
WORKAROUND: Go to the bottom bullet. Press Backspace until you delete the two additional bullets and are left with the top new one (of the three), the only bullet you intended to create. Then proceed. Note that this problem won't come up again until you save and re-edit the article. STATUS: Verified 8/14/13
STATUS: Bug verified 05/29/2013. A fix is planned.
http://social.technet.microsoft.com/wiki/contents/articles/list-of-microsoft-support-knowledge-base-articles-related-to-microsoft-virtualization-technologies-for-2011.aspx http://social.technet.microsoft.com/wiki/contents/articles/705.aspx#comments http://social.technet.microsoft.com/wiki/contents/articles/10061.th-th.aspx
STATUS: Cause is not proven. Still exists as of May 2013.
STATUS: Verified that this is a problem in Farsi/Persian on 06/01/2013. STATUS: Still exists in Japanese on 06/05/2013. STATUS: Still exists in Russian articles on 08/17/2013.
STATUS: Reported on 06/01/2013.
Some foreign characters in Japanese articles display as the double byte (DBCS) representation (for example "格") instead of the Japanese. The characters display correctly in the Edit tab, but not in the published article.
STATUS: Still exists on 06/18/2013.
WORKAROUNDS: Delete the extra spaces. Use a different browser. Try using IE9 in Compatibility View.
STATUS: Cannot reproduce (4/17/13). Confirmed as fixed in the forum.
STATUS: IE9 seems to be supported well now.
WORKAROUNDS: Try removing the horizontal line rule and adding a new one. Use a different browser.
STATUS: This is the same as # 6 in the "Wiki Editor" heading
WORKAROUNDS: Unknown.
STATUS: Not seen in a long time.
WORKAROUND: Check an article often for comments (about three times a week, if it is time sensitive, such as release notes, or once every 2-3 weeks if it is not time sensitive).
STATUS: Currently a fix is being planned to be released on July 13th, 2011.
Unlike Wikipedia, there is no clear way of knowing when a link is external.
WORKAROUND: For external links, until we have an external link flag (like Wikipedia does), paste the link URL in the Editor so that it is obvious to a user that the link is not internal to TechNet Wiki. For the feature request, see Links #1 in the TechNet Wiki Feature Requests.
In the previous profile, pages that you selected as Favorites appeared in your Favorite pages section. With the new profile, there is no such section. Currently the Favorite this page link (at the bottom of every article page) does nothing.
STATUS: Fixed in June, 2011. The Favorites button was removed.
STATUS: Solved because you can no longer search by names.
Currently you can only earn points in your profile from Forum contributions, Gallery contributions, and not Wiki contributions. A new point solution that includes Wiki contributions is currently being planned.
STATUS: Fixed on July 13th 2011, with other Profile features (like profile user cards and contribution points for blogs and annotations).
WORKAROUND: You need to press Enter when the focus is in the search box to execute the search.
STATUS: Current plans are to remove this icon.
WORKAROUND: As a temporary work-around, use the tag as a keyword in a search and subscribe to the resulting RSS Search feed.
STATUS: Fixed in 2010.
STATUS: Still exists, as of May 2013, but already covered in the article "Feature Requests for TechNet and MSDN Profiles and Social Platform Tools".
WORKAROUND: As a contributor/editor, only edit tags in the Edit tab. As an author, when you first write an article, make a first edit to the article as well. This will protect your authorship credit from ever being removed by this bug.
STATUS: Fixed in May 2011 with the upgrade to CS 5.6.
STATUS: Fixed.
STATUS: Cannot be duplicated May 24, 2013.
WORKAROUND: To fix the symptoms of this bug, click the HTML View tab, and then delete the Header tag content.
STATUS: Need to verify this bug still exists (6/10/11). Ed: As of 10/15/12, I cannot repro.
WORKAROUND: Highlight all the text in the article, select Segoe UI from the Font Name drop-down list in the Editor toolbar, and select 12px from the Real font size drop-down list in the Editor toolbar. If you also have italics and font color issues, change those manually as well.
STATUS: Cannot be replicated. Not seen in a long time (05/30/2013).
NOTES: This could be the same bug as #8 below. This might be an IE9 bug.
STATUS: Cannot be duplicated 05/29/2013.
STATUS: This could be the same bug as #6 above. This might be an IE9 bug. Cannot be replicated. Not seen in a long time (05/30/2013).
WORKAROUND: Click the Article tab to make sure your saves were made. You also might want to copy text you added just in case (because if you leave after making significant changes that were not saved, you cannot get back to what you wrote).
STATUS: Same as # 11 in Wiki Editor heading
<style>.ClassName { margin-left:100px; }</style> <p class="foo">This is a paragraph with 100px padding.</p>
<style>.ClassName { margin-left:100px; }</style>
<p class="foo">This is a paragraph with 100px padding.</p>
. ClassName { margin-left:100px; } This is a paragraph with 100px padding.
. ClassName { margin-left:100px; }
This is a paragraph with 100px padding.
STATUS: 05/30/2013. Styles are now commented out. They are ignored, but do not show up in the article.
STATUS: Same as # 1 in Comment heading