Thread

This question may be related to a resolved thread.
This question may also be related to a resolved thread.
Also see this related Feature Request.

I have a client who’s wanted to search for this entry on their site:

http://greatmuseums.org/explore/more/a_womans_touch_national_museum_of_women_in_the_arts

They searched for the word “woman’s” with a standard apostrophe, not a curly apostrophe. The entry wouldn’t come up in search. I looked in the database and saw the apostrophe had been converted to an HTML entity. The actual data’s content was turned into

A Woman’s Touch: National Museum of Women in the Arts

It seems then that Expression Engines’ simple search wouldn’t translate between a search for the apostrophe and the entity that it was changed to in the database.

For the time being, I’ve manually gone into the database for this entry and changed the & # 8 2 1 7 ; into a regular apostrophe, but this isn’t a really workable solution.

How can I make the simple search recognize the character properly without manually changing the database. I saw somewhere on the forums a suggestion to make a new field with its formatting set to None for this channel and have the client enter the title in that field and have EE not convert the apostrophe in that field since there isn’t that option available for the “Title” field, but that’s not a workable solution currently. I’d really like the search to do this conversion and find the even if a special character has been encoded.

Any thoughts on solving that?

Hi John,

Can you please confirm which version of EE you are using?

Cheers

Greg

I’m on v2.1.0 Build 20101220.

Hi John

Can I ask you to check your version please? 2.1.3 was released on 20101220 but if your installation is showing this date but a version of 2.1.0 then it’s possible that an upgrade you performed did not complete correctly. What is the history of this site? Has it been upgraded? If so, from which version?

Cheers

Greg

Hi Greg,

I’m not able to do that upgrade in a timely fashion. Is that the reason this search issue is happening or just a separate issue you’ve spotted?

Regarding the history of the site. It was developed on EE. Development began in October 2010 with whichever version was most current at that point. I did an upgrade in December 2010 before the launch.

-John

Hi, John. I didn’t test in 2.1.3, but in 2.1.4beta, the search worked exactly as expected when using the Agile Theme. I’m not suggesting you upgrade to 2.1.4beta, but I’d certainly suggest 2.1.3. It might take less time to upgrade than to have to bandaid the entries.

Make sense?

Thanks as always, Sue. Perfect answer for my situation. I’ve got a temporary fix in place for the site and now I’ve got a solid answer for what next steps will be. When 2.1.4 comes out of beta, I can deal with this issue again then. We can close this thread for now. If I run into problems at that point, I’ll post again.

Cheers,
John

Thanks John. Closing as requested