I just noticed that Kriesi added a form id to the input fields with the update. I changed the code above to incorporate this change.

The answer to the question “What do you mean by “if your field name is different”?” – Enfold allows you to change the “Form Element Label”

This label text will be used for the form name too. If your “subject” field is not labeled with “subject” the above code will not work. You’d need to replace the word “subject” in

$new_post['subject_'.

with your field label text – i.e. if the field label is “Test” the code would look like

add_filter('avf_form_subject','avia_change_mail_subject', 10, 3);

function avia_change_mail_subject($subject, $new_post, $form_params)

{

$subject = urldecode($new_post['test_'.(avia_form::$form_id - 1)]);

return $subject;

}

Tbh I don’t know why the plugin author claims things like “My guess is the theme has completely FUBARed the permalinks data or interface.”. Our theme does not rewrite the permalinks in general but only the permalink of the custom post type “portfolio” (registered in wp-contentthemesenfoldincludesadminregister-portfolio.php) uses a rewrite rule and the WPML rewrite rule the author mentions in his mail (probably he refers to the code in wp-contentthemesenfoldconfig-wpmlconfig.php) does not affect other post types too. Kriesi just rewrites the slugs for all post types which are stored in the $avia_config array and that’s actually just the portfolio post type (compare following line in wp-contentthemesenfoldincludesadminregister-portfolio.php)

$avia_config['custom_post']['portfolio']['args'] = $args;

Also the url rewrite just affects the portfolio post type – compare the code:

function avia_wpml_url_filter($lang)

{

$post_type	= get_post_type();



if("portfolio" == $post_type)

{

$slug 		= avia_wpml_get_options('portfolio-slug');



$current 	= isset($slug[ICL_LANGUAGE_CODE]) ? $slug[ICL_LANGUAGE_CODE] : "";

foreach ($lang as $key => $options)

{

if(isset($options['url']) && $current != "" && $current != $slug[$key] && "" != $slug[$key])

{

$lang[$key]['url'] = str_replace("/".$current."/", "/".$slug[$key]."/", $lang[$key]['url']);

}

}

}

return $lang;

}

If you still think our config.php breaks the permalink open up functions.php and replace

require_once( 'config-wpml/config.php' );

with

//require_once( 'config-wpml/config.php' );

Afterwards WP will complete ignore all WPML related rewrite rules which are part of the theme code and no other rewrite rules will be applied (by the theme) to the permalinks.

That said I didn’t notice any permalink issues with other plugins (WooCommerce & WPML or bbpress & WPML) and I agree with the author above – it’s probably a conflict in your configuration (plugin/plugin conflict or plugin/theme conflict). You can try to deactivate all plugins and then activate them one by one to find the conflicting plugin(s).