thelyall

I’m having the same issue. Am I understanding correctly that once my app has been reviewed and approved, it will work to show the profile photo and name? At the moment for the testing users it only brings back the username, but the app is not yet reviewed.

Thanks

That’s no problem at all, thank you for checking and getting back to me. Still a great plugin ??

I would actually like to add it as the second option if possible after ‘Browse’: morgansmiths.com is the link (site is still in progress). I appreciate this might not be possible.

Many thanks for your help

Thank you for the quick reply!

Thanks for the information – I have already done that but it adds it to the bottom of the menu (last item), the only way I can position it in the menu is via short code.

It will be ok for now it’s just not ideal, perhaps this can be added in a future version (ability to include style in the shortcode)?

Thanks

After a LOT of experimentation I haven’t been able to find a caching plugin that doesn’t interfere with the rewrite rules (i.e. they all stop the language part of the URL being added to links)

Do you have any recommendations for a caching plugin that doesn’t interfere?

Thanks

Disabling W3 Total Cache plugin fixed the issue with CSS/JS and page links – it was adding it’s own re-write rules which stopped GTranslate from working.

I am actually able to recreate this on desktop, and I’ve also noticed that unless full links are used the links break (i.e. relative links like /checkout become /izrakst instead of /lv/izrakst)

I think this is an issue with the .htaccess rules not being applied properly? That might explain CSS or JS files being incorrectly referenced causing problems(?)

Thanks for the quick reply ??

I know it’s not supported by all browsers at the moment (well, basically only Apple don’t support it in real terms) which is why I use the small .js file to offer both. I’m already using a CDN with my hosting (WPX) and all the images are already optimised as webp apart from this one…

But that’s ok, something to consider adding in the future. It’s still a great plugin…

Thanks,
Lyall

I’ve fixed this by installing WooCommerce Locations Pack plugin to add the list of correct UK counties to the list of incorrect ones, then I added the following function to my child theme to remove the ones that shouldn’t be there:

add_filter( 'woocommerce_states', 'custom_uk_states', 10, 1 );
function custom_uk_states( $states ) {
    $non_allowed_uk_states = array( 'England', 'Scotland', 'Wales', 'Other', 'Isle of Man', 'Anguilla', 'Bermuda', 'British Indian Ocean Territory', 'British Virgin Islands', 'Cayman Islands', 'Falkland Islands', 'Gibraltar', 'Montserrat', 'Northern Ireland', 'Pitcairn Islands', 'South Georgia & South Sandwich Islands', 'St Helena, Ascension, Tristan da Cunha', 'Turks and Caicos Islands', 'Guernsey', 'Jersey'); 

    // Loop through your non allowed us states and remove them
    foreach( $non_allowed_uk_states as $state_code ) {
        if( isset($states['GB'][$state_code]) )
            unset( $states['GB'][$state_code] );
    }
    return $states;
}

Unlike with US states which use the state code as the value, it appears the UK ones just use the full name.

Is this going to be fixed/included in an update or do I need to write a function to change the field to text instead of a select?

Thanks

Another option would be to change it to an empty text input (not a select list) as most of the time that’s how the county field appears in stores here in the UK. That would actually be more normal/common.

I solved it with this snippet – thanks for pointing me in the right direction with the translations:

function translate_terms_strings( $translated, $untranslated, $domain ) {
   if ( ! is_admin() && 'woocommerce' === $domain ) {
      switch ( $translated) {
         case 'terms and conditions' :
            $translated = 'terms of use';
            break;     
      }
   }   
   return $translated;
}

Thanks for the explanation.

I’ll have to find another way though I think – I installed the plugin and it’s a bit of a sledgehammer to crack a walnut when I only need to change two words in the entire site. I need to keep the site as lean as possible.

Thanks for your help,
Lyall

Does Loco Translate translate on the server side? As I use a third party translation service on the front end to translate the site into 68 different languages, so I need the code to be translatable (it can’t translate things added on the client side). Thanks

Moving this to a support topic