It seems simply that the case of [+phx+] is not treated !
/**
* stripSnip : Remove modx sensitive tags
*/
function stripSnip($text){
// Regular expressions of things to remove from search string
$modRegExArray[] = ’~\[\[(.*?)\]\]~’; // [[snippets]]
$modRegExArray[] = ’~\[!(.*?)!\]~’; // [!noCacheSnippets!]
$modRegExArray[] = ’!\[\~(.*?)\~\]!is’; // [~links~]
$modRegExArray[] = ’~\[\((.*?)\)\]~’; // [(settings)]
$modRegExArray[] = ’~{{(.*?)}}~’; // {{chunks}}
$modRegExArray[] = ’~\[\*(.*?)\*\]~’; // [*attributes*]
// Remove modx sensitive tags
foreach ($modRegExArray as $mReg)$text = preg_replace($mReg,’’,$text);
return $text;
}
$modRegExArray[] = ’~\[\+(.*?)\+\]~’; // [+phx+]in the stripSnip function.
☆ A M B ☆
☆ A M B ☆
I’m a noob and have been reading through the forums/wiki for half a day (and finding tons of neat stuff but nothing to solve my problem)...Custom search through parents (one specific folder in the doc tree) - ok no problem
But I would like to have multiple drop down select search boxes (with forced choices, users can’t input text) that would look like this:
category:
-oranges
-apples
-bananas
taste:
-sweet
-bitter
Visitors to the website can search category or taste (doesn’t have to be both at the same time).
The ’Category’ and ’Taste’ search results are short descriptions on individual pages in the doc tree ( I was wondering if I could tag something in the doc that would limit what is searched)... these individual pages/tags could be added to or modified through the CMS.
I do not know much about programming and can’t quite figure out TVs... wondering if someone could inform me as to the level of difficulty in doing this. Is there a documented example? Can a noob learn how to do something like this, if so where to start...
Any advice is greatly appreciated, have a great day!
MODX Staff
This discussion is closed to further replies. Keep calm and carry on.