customise the search_base (prefix) ??

Search for this in your nice-search.php file:

if ( is_search() && strpos($_SERVER[‘REQUEST_URI’], ‘/wp-admin/’) === false && strpos($_SERVER[‘REQUEST_URI’], ‘/search/’) === false ) {
wp_redirect(get_bloginfo(‘home’) . ‘/search/’ . str_replace(‘ ‘, ‘+’, str_replace(‘%20’, ‘+’, get_query_var(‘s’))));

Replace with this:

if ( is_search() && strpos($_SERVER[‘REQUEST_URI’], ‘/wp-admin/’) === false && strpos($_SERVER[‘REQUEST_URI’], ‘suche/’) === false ) {
wp_redirect(get_bloginfo(‘home’) . ‘/suche/’ . str_replace(‘ ‘, ‘+’, str_replace(‘%20’, ‘+’, get_query_var(‘s’))));

doesn’t work -> returns a 404 (well, this would have been too easy – furthermore i already tried that version!)

did i mention that wp2.02 seems to have the word ‘search’ deeply in its code? it doesn’t make any sense to me (as every visitor just sees ?s=blabla per default) but thats what my problem is. redirecting dont work (neither the way you mentioned nor via mod_rewrite nor via a separate search.php (sending headers) as mentioned elsewhere in this forum.

*sad* ??

(edit) it seems wordpress needs the word “search” to recognize a request being a search… but where exactly can i influence this hardcoded wp-inconsequency? imho it would be clever to have a seperate field for this setting in the permalink-section. (/edit)

ok, whats up? silly explained, or also too stupid for such mods? ??

no replies since? if this little piece of mod can be done with lightpress -> should be possible with wp, no?

Out of curiosity, are you running the english version of WP or another language? ( WP in other languages)

Have you contacted the plugin author to see if he has i18n support?

well, im running wp localised in german with a language file (de_DE.mo). anyway: this language-file has no effect on wp’s search. by default, search results are seen on a site with the following url:
https://www.domain.tld/wordpress/?s=searchterm
right?
i dont see what a language-file should translate here.

even the plugin “nice search” or the instructions from the codex (that tell to create a search.php in /wordpress/ that sends a new header to /wordpress/search/searchterm) cant be customised, because simply translating the word search to my desired “suche” causes a 404-error.
again: translating the “normal” way or with poedit doesn’t work here.
i dont understand why wordpress internally accepts /search/ but /suche/ causes a 404…

no ideas on fixing this localised url’s wordpress is persisting on?

again: my problem is not to localise a theme or plugin, my problem is wordpress being pre-localised… ??

kindly

? up! ?

arghhh…