Just got a report today from a client using an NT site that we only just upgraded to 7.2 last week. They are entering in a student into the database with the Irish surname of O'Sullivan.
Problem is, when they do this, they cannot then find the student again in the Student Browse locator by typing in "O'Sullivan". It comes up with 0 results. They can however, type in "Sullivan" and because the Locator is a "contains" locator, the record comes up.
However, when they select to [Change] the student details, the update form either throws an error that the record is not found in the primary key, or it brings up a blank record, and the form itself is all always messed up as the CSS for the 6 tabs don't kick in and the form is displayed as a continuous running form with all the tabs under each other. The [Ok] and [Cancel] buttons also don't work. Only happens for any student with a forward single tick in their surname.
(I found some older students in there with the forward ticks in their name, and they exhibit the same behaviour which was never reported by the client before, so I only assume that it used to work okay under NT 6.x but broke under 7.x
)
Conclusion: NetTalk hates Irish names...
I have worked around this for now by changing the names in the database to use back ticks (`) instead of forward ticks in the name and things seem to be working again, but perhaps we need to code the templates defensively against this for the future?
Time for another pint of the black stuff...
Topic: I need a pint of Guinness to fix this possible bug... (Read 1656 times)