CMS MADE SIMPLE FORGE

Glossary / FAQ

 

[#1419] Glossary terms containing special characters not found

avatar
Created By: Eberard Friedrich (steppenwolf)
Date Submitted: Tue Mar 27 10:24:02 -0400 2007

Assigned To:
Version: None
CMSMS Version: None
Severity: None
Resolution: None
State: Open
Summary:
Glossary terms containing special characters not found
Detailed Description:
- Glossary V. 0.5
- CMS Made Simple 1.0.4 "Lanai"
- Charset UTF-8

Glossary terms containing special characters (like Umlaut äöüÄÖÜß) are not
found.




History

Comments
avatar
Date: 2007-03-28 19:37
Posted By: Samuel Goldstein (sjg)

When I check this, it seems to be a symptom of the WYSIWYG editor substituting
in html entities.

If you have a good solution, I'd be happy to give you developer or admin access
to the svn repository :)
      
avatar
Date: 2007-03-30 07:40
Posted By: Eberard Friedrich (steppenwolf)

Samuel,
you are right: the problem depends on HTML entities from the WYSIWYG editor. The
only working solution I found at short notice, is to switch the editor to source
view. As far as it concerns me, you could remove this request.
      
avatar
Date: 2009-02-10 05:54
Posted By: Elaine  (broony)

I have a similar issue with adding more than one word as a term and I suspect
the problem is the spaces (Or  )  between words unless  the glossary is
deliberately set to only have one word terms?

More than one word in a glossary term does not display - I get a 404 error. 
Any advice really appreciated.. Thanks

      
avatar
Date: 2010-07-30 04:41
Posted By: david silvester (davids355)

I have modified the glossary so that it works with terms of more than 1 word -
its probably a really dirty fix - I justed added another column into the DB and
modified the code slightly so that the term is entered into one column exactly
as you type it in (spaces etc) then its also entered in another column with the
spaces removed.

When you display the terms/defs it searches the DB by the no spaces term but
displays the original term.

I wouldnt be able to help with proper development, but if anyone desperately
needs to get it working with spaces, just drop me a line - david[at]ds32.com