Wild cards
TheoRichel - July 17, 2008 - 15:49
| Project: | Advanced User |
| Version: | 5.x-2.0 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
| Issue tags: | translatable strings |
Jump to:
Description
Have been fiddling around with * and % but to no avail: are wild cards allowed in e.g. name and emailfields?
Many thanks for a very useful module!
Theo Richel

#1
I withdraw my question: I suppose your Boolean operators take care of that enough, though I really do not understand why you would use two letter abbreviations for that. Sure I can change that myself?
Update: I thought so. Now I see that you use some popup thing/tip to explain what these abbreviations mean. I apparently cannot change it in the translations. You may have had good reasons to do it this way, but I do not like it.
Thx
Theo Richel
#2
The reason for the abbreviations with a link description happens because of the screen real estate within the template. You should be able to translate the #attributes text for the filter operations. I agree it isn't that pretty. I can consider alternatives if you wish to provide a patch and a picture of the UI the patch provides. Reopen this issue if you provide the patch.