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,

Unfortunately we have no converting tool yet and the only solution is to modify the data directly in the database with tools like phpmyadmin. Access the wordpress database and click on the “wp_options” table. Then search for the data field with the “option_name” value “avia_options_enfold” and replace “enfold” with your child theme name. If the child theme name is “Enfold Child theme” the new “option_name” would be “avia_options_enfold_child_theme”.