pluginfile.php doesn't require login unless it has been customized. The require login is left to the discretion of the calling component. So you need to start with identifying which component calls these file and examine the respective code. For instance in modules the code would be in mod/modname/lib.php mod_modname_pluginfile().
Itamar Tzadok
Мнения, написани от Itamar Tzadok
You can put any element in a group. For instance:
$arr = array();
$arr[] = &$mform->createElement('select', "searchandor$count", null, $andoroptions);
$arr[] = &$mform->createElement('selectgroups', "searchfield$count", null, $fieldoptions);
$arr[] = &$mform->createElement('select', "searchnot$count", null, $isnotoptions);
$arr[] = &$mform->createElement('select', "searchoperator$count", '', $operatoroptions);
$arr[] = &$mform->createElement('text', "searchvalue$count", '');
$mform->addGroup($arr, "customsearcharr$count", "$fieldlabel$i", ' ', false);
hth
Thanks Darko. I do understand what clean_param does and it is precisely because it calls the validateUrlSynax function that I hoped it would actually validate the url syntax and I have noticed that with default options it merely checks compliance with rfc2396 which is also what php filter_var does with FILTER_VALIDATE_URL. It seems however that there is some inconsistency in the clean_param function as for PARAM_COMPONENT, for instance, it does more than just cleanup and checks for valid component syntax and returns empty string if invalid.
I'm inclined to think that it should not consider such a string a valid url and yet it does return it as valid url. Am I missing something here?
Mary, with forum posts automatically parsing double brackets as docs links it may be useful to adjust the filter (I'm assuming this is done via a text filter) to recognize the <nowiki> tag and skip double brackets which are nowiki-ed. We have a problem explaining and posting working examples of double bracketed patterns such as the Database module's because the double brackets are filtered out.