Ticket #5912 (closed Bugs: fixed)

Opened 11 months ago

Last modified 10 months ago

Display Name Apostrophe

Reported by: TreadingWater Assigned to: tm1000
Priority: crash Milestone: 2.10
Component: Endpoint Manager (OSS) Version: 2.10-branch
Keywords: Apostrophe SQL Error Cc:
Confirmation: Need Feedback Distro:
Backend Engine: Asterisk 1.8 Distro Ver:
Backend Ver: 1.8.8.0 SVN Revision (if applicable):

Description

Apologies if this has already been requested, but I have been unsuccessful in finding any FreePBX documentation on the Fatal SQL Error received when attempting to use an apostrophe (ie single quote) in the Display Name field of Extensions (ie O'Brien). I was able to find external documentation (http://www.4guysfromrolla.com/webtech/051899-1.shtml) directing me to enter 2 apostrophe's and this is working for the moment in FreePBX. Hard to believe I could possibly be the first to whine about this. But, perhaps no one has made the effort to submit a ticket? :]

The link above does provide code for a fix if it helps.

Actual Error when using a single quote = hi FATAL SQL ERROR! ::::: UPDATE endpointman_line_list SET line = '1', ext = '3605', description = 'Maureen O'Brien'

WHERE luid = 60 [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'Brien' WHERE luid = 60' at line 1]SQL -..............can reproduce remainder of code if needed.

Change History

07/03/12 16:53:23 changed by TreadingWater

Just in case the majority vote is not to address this pesky error, could we then consider adding a "note" to the pop-up hint stating two single quotes are required for names containing apostrophes? :]

(follow-up: ↓ 3 ) 07/03/12 17:13:52 changed by tm1000

  • priority changed from minor to crash.
  • status changed from new to assigned.
  • confirmation changed from Unreviewed to Need Feedback.
  • milestone changed from 2.11 to 2.10.

This will get fixed. Why wouldn't I fix it? Strange.

anyways I believe it's already fixed as you never stated what version you are using. You even selected 2.11 for the milestone which is the default.

Please provide me with these answers

(in reply to: ↑ 2 ) 07/03/12 17:29:32 changed by TreadingWater

Oh buggers. Yes, it is 2.10. Sorry, I over looked that. I do try to be thorough for the most part (fail!). And I was only guessing the Endpoint Manager module since the error was pointing its finger there and didn't see a specific Extensions one under applications. The EPM version we have is 2.10.3.7.

I just know you all do have your plate full with probably more important issues (although, the O'Briens and O'Malleys probably think this is most important).

Thank you so much for the quick response! :)

07/03/12 21:17:40 changed by tm1000

07/05/12 12:22:56 changed by TreadingWater

Yes! Perfect. Whooohoo. Thank you. :)

07/16/12 13:09:14 changed by tm1000

  • status changed from assigned to closed.
  • resolution set to fixed.