FamilySearch Wiki:Known Issues/Archive 3

Known issues in FamilySearch Wiki are reported below, with the most recent at the top of the list:

Headings interfering with Menu links
Whenever a heading is just opposite a link in a menu "box," https://wiki.familysearch.org/en/Template:Box that particular link will not work. There is no padding around this template so the little edit box is right up against the border on the template and seems to affect the links inside the menu box. The mouse over does not change the link to underline either.
 * One work around is to change the headings to normal text the links work fine.
 * A second work around and a better option is to create the same menu in a "helpbox" https://wiki.familysearch.org/en/Template:Helpbox rather than in "box". The "helpbox" has padding built-in to the template and the links inside are not effected by the position of the headings.

Images with Captions
Captions added to images disappear after the page is edited.

Cause:

This is a problem with the FCK editor.

Fix/Workaround:

Create a template that includes the image and caption that can be placed on the page. Example: Monroe County Courthouse

Migration to LDS Account
A discussion of the issues that have arisen as a result of the migration to LDS Account can be found in the FamilySearch Wiki Technical Support forum

Shorter timeouts
Users have reported that they are logged out after a shorter time period than before the change. It is believed that this is due to the wiki inheriting the timeouts from new FamilySearch which is intentionally short due to the risk of confidential information being left open by users working from public access computers. It is believed that the programmers are already working on this issue.

StringhamDB That is correct. The Research Wiki's timeout is set at 45 minutes but since the change to CIS authentication we are limited to 24 minutes. This issue needs to be set with a high priority on the Research Wiki backlog.

Combined accounts not successful
Several users have reported that they had not been able to successfully combine their old accounts with their new LDS Accounts. This resulted in a loss of their watchlist notifications and their old edits not being shown against their new account.

This is still a problem if the user name includes spaces " " or underscores "_".

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:

http://geonames.usgs.gov/pls/gnispublic

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:

http://geonames.usgs.gov/pls/gnispublic/f?p=gnispq:3:::NO::P3_FID:nnnnnnn

nnnnnnn = Record identification number.

Wrong:

http://geonames.usgs.gov/pls/gnispublic/f?p=116:3:827734824577216::NO::P3_FID,P3_TITLE:15257%2CAll%20Faiths%20Memorial%20Park All Faiths Memorial Cemetery

Right:

How do I upload files or images?
The article Uploading files or images has minimal information. We need additional instructions.

Integrating Family History Library Internet favorites
See discussion at Talk:Feedback:_Integrating_Family_History_Library_Internet_favorites

Editor bugs
See discussion at Help talk:The Editing Tool (FCK Editor)

Missing content
See discussion at Content from previous version is missing or links are missing

I don't know what I'm doing. I found some web pages that indicated "Web Page cannot be found" while in the Georgia, Pulaski Co., cemetary listing. Should I submit the names of the cemetaries here? Thanks

foreach
Could you install #FOREACH for me? http://www.mediawiki.org/wiki/Extension:LoopFunctions 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. http://tech.lds.org/forum/showthread.php?t=1091 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: http://tech.lds.org/forum/showthread.php?t=1106 Thank you, Thomas Lerman 15:36, 13 March 2008 (MDT)
 * Poll for Parser functions and #foreach is at http://tech.lds.org/forum/showthread.php?t=1126. Thanks The Earl 10:53, 17 March 2008 (MDT)

The Displaying of the Username
In the Wiki:Technical Meeting Agenda 28 December 2010, there was some concern expressed about MediaWiki or the wiki.familysearch.org default to make public and display the username rather the display name for example https://wiki.familysearch.org/en/Special:ListUsers. After talking with the engineers over the Wiki, they said that it was the default code that MediaWIki came with and if it could be changed it would require a "Core Change" to change it. I submitted an enhancement request and maybe that change will be made. Warren 13:15, 4 January 2011 (MST)