Note prefix selection ignored

Bug #1083922 reported by Wes Groleau
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webtrees
Fix Released
Low
fisharebest

Bug Description

Admin is allowed to specify the prefix to be used for NOTE xrefs, but in
// $Id: functions_print.php 14548 2012-11-16 12:49:56Z greg $
at line 442,
  if (preg_match('/@N([0-9])+@/', $nrec, $match_nid)) {
seems to assume he/she chose 'N' (seem = allowance for my misinterpretation)

Also, what happens when imported GEDCOM uses non-digits in its xrefs?

Revision history for this message
fisharebest (fisharebest) wrote :

AFAICT, this is part of the census-assistant module.

But there appears to be another bug in the "create new XREF" module, which ignores the configured choice of prefix.

Hence all new notes (created by the census-assistant module) will have a prefix of "N".

So, the two bugs cancel each other out ;-)

Changed in webtrees:
status: New → Confirmed
Revision history for this message
fisharebest (fisharebest) wrote :

This took me ages to fix because my default note prefix is "n", and another bug prevented notes from being displayed when there were lower case letters in the XREF.

Changed in webtrees:
status: Confirmed → Fix Committed
importance: Undecided → Low
assignee: nobody → fisharebest (fisharebest)
Revision history for this message
fisharebest (fisharebest) wrote :

Fix released in 1.6.0

Changed in webtrees:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.