FamilySearch Wiki:Known Issues/Archive 2

From FamilySearch Wiki
Jump to navigation Jump to search

Populated Places Links not active in Firefox/Chrome<br>[edit | edit source]


There are many county pages with "Populated Places" sections where the links in those sections are not active. Two examples are:

Trousdale County, Tennessee<br> Greene County, Tennessee

These links work ok in Internet Explorer. --janellv 22:16, 12 April 2011 (UTC)


Remove the "align="left"" tag from the table properties in that section and the links will work again. janellv 17:28, 14 April 2011 (UTC)


Right hand navigation sidebar displayed below main content[edit | edit source]

This question or concern has been resolved.
by means of a workaround - problem will still occur

Some pages when viewed instead of displaying the navigation sidebar along the right hand side of the page, it is displayed underneath the main content of the article.

This is caused by a missing </div> tag, often innocently removed automatically by the Rich Text Editor.
When this problem is found add the template {{closing div}} to an appropriate section of the page. This will restore the navigation bar to the right hand edge of the screen
--Steve 18:56, 2 November 2010 (UTC)
Steve, the heading indicates that this issue has been resolved. Has it actually been resolved, or is there just a workaround in place? --Mark 18:25, 29 November 2010 (UTC)
Hi Mark, I have edited the {{resolved}} flag to explain that the solution is only a workaround for the problem. A solution to fix the problem happening I believe would involve improvements to the Rich Text Editor. --Steve 15:25, 30 November 2010 (UTC)

Return-to page after sign on[edit | edit source]

This question or concern has been resolved.

Users that are browsing a page in the Special namespace are not returned to that page after they have signed on.

StringhamDB It appears as if the page URL is being mis-translated when handed over to CIS. Redirects can be the death of the web and this is an example of that statement. More research is being put into this issue to resolve it.

01-08-2010 A fix for this can be tested out at Research Wiki Beta

Problems When Using Internet Explorer 8[edit | edit source]

This question or concern has been resolved.

Some users have reported being unable to sign-in using Internet Explorer 8. When clicking on wither of the sign-in links on the home page, the new sign-in page does not come up. In fact, nothing happens. A work-around is to place a short-cut on your desk-top, which takes the user to the new sign-in page from which the user can then sign-in.

Linking to GNIS (Geographic Names Information Systems)[edit | edit source]

This question or concern has been resolved.

These instructions need to be moved to the FamilySearch Wiki:Manual of Style

1. is the public access point entry.

2. FAQ link has the information concerning proper linking to the GNIS records.

a. My bookmarks and links to the GNIS query do not work?

When you log on, the system adds temporary session identification numbers to the URL, so it looks like this: If you bookmark or copy and paste this entire URL with numbers, it will not work in the future. Delete all after the word “gnispublic.” The correct URL is:

b. # How do I link to an individual feature record?

To save a link to an individual feature record detail report:

1. Search for the U.S. feature and note the Feature ID.

2. Copy and paste the following URL exactly as shown for US features:

nnnnnnn = Record identification number.

Wrong:,P3_TITLE:15257%2CAll%20Faiths%20Memorial%20Park All Faiths Memorial Cemetery


You can mask the link. In this case it would be.

All Faiths Memorial Cemetery

Hopefully this resolve the issue of proper linking. dsammy

Strange Characters Automatically Added During Edits[edit | edit source]

This question or concern has been resolved.

The following characters appear on the page when you are trying to edit:

<input type="hidden" id="gwProxy"></input><input type="hidden" id="jsProxy" onclick="jsCall();"></input>

Resolution[edit | edit source]

This bug has been traced back to the Browser Highlighter Firefox plug-in. See the thread Weird gwProxy code is inserted in WYSIWYG textareas from the Mozilla support forum. Removing the offending add-on in Firefox should fix the problem.

Help Copying[edit | edit source]

This question or concern has been resolved.

It seems there is a large section of the Help files from Mediawiki explicitly for inclusion in new wikimedia installs. Can we get these help files copied over? Thanks, The Earl 10:55, 17 March 2008 (MDT)

The MediaWiki Help pages that are relevant in the Research Wiki were copied to in April 2010. This included Help:Contents. Many of them include a notice {{PD Help Page}} at the top to indicate that they have been copied over. Once they have been checked and updated to tie in with the Research Wiki this header template can be removed --Steve 11:13, 3 August 2010 (UTC)

Create Place Holder on Home page[edit | edit source]

This question or concern has been resolved.

Create Place Holder on Homepage (Done - Created Main_PageFamilySearch Research Wiki Portal)

Editing existing pages[edit | edit source]

This question or concern has been resolved.

See discussion at Edit a page

Creating and Populating Tables[edit | edit source]

This question or concern has been resolved.

I seem to be able to create a table, specify the number of rows and columns, size of cell, etc. But I couldn't get the table centered. I used the centering feature but the table remained on the left side of the page. What am I doing wrong. Also, how do I populate the cells of the table. As I started to type in a cell, the sizes of the columns changed. Jbparker 11:14, 14 February 2008 (MST)

Go to Help:Tables for more information about working with tables. Molliewog 14:11, 6 March 2008 (MST)

Is there a training manual?[edit | edit source]

This question or concern has been resolved.

Currently, help articles can be found at Category:Help Molliewog 14:26, 6 March 2008 (MST)

HTML and other unusual characters in Search Results[edit | edit source]

This question or concern has been resolved.

We have documented an issue with HTML and other Wiki syntax showing up in the search results. For example, if you search on Alaska, the following items will be included in the results:

3: * Alaska State Archives<br />141 Willoughby Avenue <br ...
4: ...41<br />Internet:<br />
5: * Genealogical Society of Southeastern Alaska<br />P.O. Box 6313 <br />Ketchikan, AK 99901
6: ...<br />Fax: 907-276-1596<br />Internet:<br />
7: * Alaska State Library<br />Alaska Historical Collections<br />State Office Building... If you click on the Wikitext button (upper left corner of the tool bar)
while you are in the edit mode and delete the HTML language it will disappear from the final saved page--usually.

This appears to no longer be an issue. Molliewog 14:54, 6 March 2008 (MST)

FamilySearch Wikis in other languages[edit | edit source]

This question or concern has been resolved.

For a discussion about this site and languages, please see FamilySearch Wiki:Non-English versions of the wiki -Molliewog 15:14, 6 March 2008 (MST)

General Structure[edit | edit source]

Please join the discussion at Talk:Meta:US_Structure. The Earl 17:24, 7 March 2008 (MST)

Look and feel and navigation[edit | edit source]

This question or concern has been resolved.

This page was created when the content in Plone was ported over to the Wiki. Some concerns were raised dealing with the look and feel of the new home for content and also the navigation. The concerns at the time have been resolved. See the discussion that took place at Talk:Look and feel and navigation. This page is currently categorized as FamilySearch Wiki, but likely needs a new category related to the ongoing development of the design and navigation of wiki content.

Search problems[edit | edit source]

See discussion at Searching for specific articles or topics

foreach[edit | edit source]

This question or concern has been resolved.

Could you install #FOREACH for me? Thanks The Earl 18:00, 7 March 2008 (MST)

If you have a new feature or process you'd like to suggest -- or if you feel an existing plugin/extension fills a customer need -- please submit a proposal to the wiki forum. (It's also a good idea to attach a poll to your post.) This allows the community to discuss and refine the idea. If the community agrees that the idea should be deployed, our development team will prioritize the request against the others in the queue. When we are planning an iteration (or a release), we add features/ideas/use cases to it using the requests as they are prioritized in the queue. Thanks. Molliewog 10:01, 11 March 2008 (MDT)

I have started a forum topic as to why the forum is a bad place to discuss wiki issues. Please comment there. That said, if the above is the preferred way to submit requests, I will do so there.
Thanks The Earl 13:53, 11 March 2008 (MDT)
I have started a forum topic about extensions since I had a request as well. You may find it at:
Thank you, Thomas Lerman 15:36, 13 March 2008 (MDT)
Poll for Parser functions and #foreach is at Thanks The Earl 10:53, 17 March 2008 (MDT)