philippze

No. In the string translations the string fluid_button_text was not found. It does not appear in a translation function the plugin. It’s an array key in the translation with the following default value defined in ast-customizer.php:

'fluid_button_text' => __( 'Track Your Order', 'woo-advanced-shipment-tracking' )

I will find “Track Your Order” in the translation strings. However, it will not make a difference when I translate it because it is the default value and will be replaced with the actual value from the plugin settings.

Here is what I see when I grep for your string in the plugin settings:

$ grep -r fluid_button_text plugins/woo-advanced-shipment-tracking/
plugins/woo-advanced-shipment-tracking/templates/myaccount/tracking-info.php:$fluid_button_text = $ast->get_option_value_from_array( 'tracking_info_settings', 'fluid_button_text', $ast_customizer->defaults['fluid_button_text'] );
plugins/woo-advanced-shipment-tracking/templates/myaccount/tracking-info.php: plugins/woo-advanced-shipment-tracking/templates/emails/fluid-tracking-info.php:$fluid_button_text = $ast->get_option_value_from_array( 'tracking_info_settings', 'fluid_button_text', $ast_customizer->defaults['fluid_button_text'] ); plugins/woo-advanced-shipment-tracking/templates/emails/fluid-tracking-info.php: plugins/woo-advanced-shipment-tracking/wpml-config.xml: plugins/woo-advanced-shipment-tracking/includes/customizer/ast-customizer.php: 'fluid_button_text' => _( 'Track Your Order', 'woo-advanced-shipment-tracking' ),
plugins/woo-advanced-shipment-tracking/includes/customizer/ast-customizer.php: 'fluid_button_text' => array(
plugins/woo-advanced-shipment-tracking/includes/customizer/ast-customizer.php: 'default' => !empty($tracking_info_settings['fluid_button_text']) ? $tracking_info_settings['fluid_button_text'] : $this->defaults['fluid_button_text'],
plugins/woo-advanced-shipment-tracking/includes/customizer/ast-customizer.php: 'class' => 'fluid_button_text',
plugins/woo-advanced-shipment-tracking/includes/customizer/assets/Customizer.js:jQuery('#fluid_button_text').on("keyup", function(){
plugins/woo-advanced-shipment-tracking/includes/customizer/assets/Customizer.js: var fluid_button_text = jQuery(this).val();
plugins/woo-advanced-shipment-tracking/includes/customizer/assets/Customizer.js: jQuery("#email_preview").contents().find('.track-button').text(fluid_button_text);

Hi @gaurav1092 ,

thank you for your answer! Probably my problem description was not clear enough.

Customizing the button text for one language works well. Just, our shop is in two languages (German and Italian). So, we need to use the translation system somehow. One global setting for the button text is not enough.

In the mean time, I have solved the problem with copying the template file fluid-tracking-info.php to the theme and changing the line that defines the button text, so it uses a normal translation instead of the text defined in the configuration.

Of course, it would still be nice to have a better solution 🙂

The default CSS is registered with an wp_ajax_ action. To remove it, we must first wait until we are sure the action has taken place – e.g. by using the wp_loaded hook. Then, we can remove the action we don’t like. I do it like this:

add_action('wp_loaded', function () {
    remove_all_actions('wp_ajax_gridfrontendCSS');
    remove_all_actions('wp_ajax_nopriv_gridfrontendCSS');
});

• This reply was modified 8 years, 11 months ago by philippze.

By using the action grid_boxes_search.

Example:

add_action( 'grid_boxes_search', function($result, $grid_id=null, $post_id=null) {
    $final_results = [];
    $allowed_types = ["media", "posts", "facebook_feed", "post", "my_type"];
    foreach ($result as $item) {
        if (in_array($item['type'], $allowed_types)) {
            array_push($final_results, $item);
        }
    }
    return $final_results;
});

• This reply was modified 8 years, 11 months ago by philippze.

Hi Sark,

thank you for your answer! No errors are logged, and I also cannot find anything using the WordPress 404 Debugger https://gist.github.com/soulseekah/2321074.

However, your comment has motivated me to investigate a bit further.

• The Post Variables are correct.
• The 404 Error will not happen when I buy the product on the standard Woocommerce product page.
• It does only happen when I crate the content type “Product Page” with the WPBakery Visual Composer and the commercial theme Agile.

So – it’s not the plugin’s fault 🙂 If nevertheless you have some rough idea what could cause the strange problem, I’d be curious.

I’ll report this as a bug to the developers of the Agile theme.

Best regards
Philipp

The canonical tag is neither displayed. I’ll have a look if the theme does anything nasty with the wp_head.

Thanks for your quick support!

We have bought a theme called emulate
http://themeforest.net/item/emulate-multipurpose-responsive-wordpress-theme/6058805

At the end of the <header>, theres a line
<?php wp_head(); ?>