Do you mean the standard text strings like on the search page: http://www.volantexrc.com/cn/?s= (“If you are not happy with the results bellow please do another search”, etc.)? If yes you must translate these strings with a po/mo translation file. I’d suggest to generate the po file with Codestyling: http://wordpress.org/plugins/codestyling-localization/

Install the plugin, go to Tools > Localization and select “Themes”. Then search for “Enfold” in the list and click on “Add new language”. Afterwards select your language from the list and click the “create po-file” button. Click on “Rescan” to fetch all text strings. Then click on “Edit” and translate the required strings from the “avia_framework” textdomain. At least click the “create mo file” button next to the “Textdomain” selection dropdown (top left corner).

Or do you want to translate i.e, “ABOUT US”? If yes just open up the textblock element (seems to be part of a color section) and replace the text with your translation…

ok, I found a perfect solution, that shows automatically the excerpts, too – thanks to Dude’s code modification with using the plugin Relevanssi:

Here is the code modification, so that Relevanssi works perfect with ENFOLD:

https://kriesi.at/support/topic/instant-search-not-matching-search-results#post-135415

You can change it in wp-contentthemesenfoldframeworkphpclass-form-generator.php – search for

$this->output  = '<form action="'.$params['action'].'" method="post" class="ajax_form '.$extraClass.'" data-avia-form-id="'.$this->formID.'"><fieldset>';

You can modify the post query but note that it will affect ALL portfolio grids. Open up wp-contentthemesenfoldconfig-templatebuilderavia-shortcodesportfolio.php and search for

$query = array(	'orderby' 	=> 'post_date',

'order' 	=> 'DESC',

'paged' 	=> $page,

'posts_per_page' => $params['items'],

'post_type' => $params['post_type'],

'tax_query' => array( 	array( 	'taxonomy' 	=> $params['taxonomy'],

'field' 	=> 'id',

'terms' 	=> $terms,

'operator' 	=> 'IN')));

Replace the operator value and use AND instead of IN

In this case I’d contact the hoster – ask them if any redirect rules are in place which can block or affect search queries. You can also try to switch to another theme (like TwentyTwelve). If this link: http://www.lighthousemktg.com.au/?s=test still redirects you to the front page it’s definitely a sever configuration issue.

Hi!

Sounds like a javascript issue/conflict. You can use the browser console to determine which script breaks the website.

Best regards,

Peter

Actually we just use the standard search query and we have no influence on the search results. You can use this plugin to maximize the search power of your website: SearchWP

Refer to this link in order to integrate the plugin on ajax search: http://kriesi.at/documentation/enfold/use-searchwp-instead-of-the-standard-search/

It seems like the standard search query doesn’t work in your case. Eg

http://www.lighthousemktg.com.au/?s=test doesn’t work but the same search works on the demo page:

http://kriesi.at/themes/enfold/?s=test

Try following

1) Deactivate all plugins and check if the search works. If yes activate them one by one until the search doesn’t work again.

2) If 1) does not solve the problem upload all wordpress and theme files again. Use the latest versions (wp3.6 and Enfold 2.0.x).

3) If 2) doesn’t work go to Settings > Permalinks and hit the “save” button to flush the rewrite rules.

Open up wp-contentthemesenfoldincludeshelper-post-format.php and search for

$heading = is_singular() ? "h1" : "h2";

Replace h1 and h2 with any headline type of your choice. h1 is used on single post pages, h2 on the blog & archive page. If you’re using a child theme you can duplicate the avia_default_title_filter() function and overwrite the parent theme function if you like.

You can use Relevanssi for the ajax search query. Open up enfoldfunctions-enfold.php and replace

$defaults = array('numberposts' => 5, 'post_type' => 'any', 'post_status' => 'publish', 'post_password' => '', 'suppress_filters' => false);

$_REQUEST['s'] = apply_filters( 'get_search_query', $_REQUEST['s']);



$query = array_merge($defaults, $_REQUEST);

$query = apply_filters('avf_ajax_search_query', http_build_query($query) );

$posts = get_posts( $query );

with

$defaults = array('numberposts' => 5, 'post_type' => 'any', 'post_status' => 'publish', 'post_password' => '', 'suppress_filters' => false);

$_REQUEST['s'] = apply_filters( 'get_search_query', $_REQUEST['s']);



$searchquery = array_merge($defaults, $_REQUEST);



if(!function_exists('relevanssi_do_query'))

{

$searchquery = apply_filters('avf_ajax_search_query', http_build_query($searchquery));

$posts = get_posts($searchquery);

}

else

{

global $query;

$tempquery = $query;

$searchquery = apply_filters('avf_ajax_search_query', $searchquery);



$tempquery->query_vars = $searchquery;

relevanssi_do_query($tempquery);

$posts = $tempquery->posts;

}

Unfortunately this is not possible at the moment but you can hide certain menu items by inserting “noMobile” into the css class field of these items (if you can’t find this option field on the menu option page search for the “Screen Options” tab in the right top corner and click on it. Then tick the checkbox next to “CSS Classes” to activate this field).

If you really need to separate menus you can suggest the feature here: https://kriesi.at/support/topic/enfold-feature-requests and we’ll look into it if more users request it.

Hello Dude,

Thanks for your response.

In this case, all these two ‘��’ should be removed. Therefore, the breadcrumb is created, the PHP code should cut off the string before these two invalid characters. Sometimes, you will see one of these as ‘�’. But this is just a representation of UTF-8 encodings in a browser, and using W3C HTML Validator reveals invalid character code is “xE3” in this case.

This can happen when you are trying to truncate a UTF-8 string at any character boundary. For example, if you have a string “あ”, which consists of 3 bytes “E3 81 82”. If you cut the string within these 3 characters, the original character “あ” will be corrupted, and it is represented like this ‘�’.

This issue is not limited to Japanese. In German, for example, a character ‘ä’ can be encoded as two bytes: “C3 A4”, and cutting these two bytes into half will make the ‘ä’ character invalid.

With a little search, I found a similar article:

http://stackoverflow.com/questions/8484162/how-to-truncate-an-utf8-string-in-php

I think using mb_strimwidth instead of substr will resolve this issue.

Thank you,