Rhys

Thanks @wissamcloudinary,
I’ve tried setting c_fit,w_960 into the “Additional image transformations” field within the WordPress plugin. The URL now becomes this:

https://res.cloudinary.com/scndit/images/w_960,h_480/c_fit,w_960/f_auto,q_auto/v1664320975/live/Scandit_Passport_Feature_iPhoneX_373b3af4/Scandit_Passport_Feature_iPhoneX_373b3af4.jpg?_i=AA

However the image is still stretched. The responsive image option is turned on too with these options set:

• Breakpoint distance: 280
• Max images: 5
• Image width limit: Max: 1440 Min: 320

Do the images need to be regenerated or something?

Thank you for any insights,
Rhys

Hi @maybellyne
I’ve looked through our error logs, I’ve found this line:

2022/08/05 03:55:48 [error] 58659#58659: *16732839 FastCGI sent in stderr: "PHP message: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4194312 bytes) in /www/xucobuce_886/public/wp-includes/wp-db.php on line 2136" while reading response header from upstream, client: 193.56.253.58, server: www.scandit.com, request: "GET /page-sitemap.xml HTTP/1.1", upstream: "fastcgi://unix:/var/run/php7.4-fpm-xucobuce.sock:", host: "www.scandit.com:64972"

Any ideas? It seems pretty general to me.

Thanks @maybellyne,
I’ve gone back to my hosting provider (Kinsta) and they temporarily bumped up the memory from 256M to 512M, which allowed this file to render. However that was only a temporary fix.

As the page-sitemap.xml file contains over 500 pages, I wonder if there is an upper limit for these types of files? Using your tool “Yoast Test Helper” to limit the maximum entries per XML sitemap to 250 seems to fix the problem on this file. Would that be a possible solution? Using this tool to limit the amount of entries?

Thanks!

Thanks @suascat_wp for the feedback.

No, we’re using Polylang. After twiddling around the past few days, I noticed today there was an update for both Polylang (3.1.2) and Yoast SEO (17.3), which I went ahead and did the updates. Now the problem seems to have been solved, for now at least.

I notice in the changelog for Polylang 3.1.2 there are these lines:
– Enforce Yoast SEO to use dynamic permalinks #882
– Yoast SEO: Fix static front page and blog page breadcrumb

could either of these be related?

thanks again for any insight

@mikes41720 thanks for that pointer, I’ll try and figure out how to make this work with removing certain language og:locale:alternate metas. I see the two functions on the linked documentation either set the default locale (og:locale) or remove it entirely.

No doubt I need to dig deeper into how to unset certain og:locale:alternate metas, but any pointers would be greatly appreciated ??

Thanks again!

While I’m not the OP, I am also seeing this exact issue. I’m about 99.999% sure it’s due to me building a theme using Timber – see about menus here: https://timber.github.io/docs/guides/menus/

I would love to find a resolution to this, as I would like to use this plugin along with Timber.

Awesome, glad to see you all got there in the end. Yeah should have mentioned that you need to be on the business plan or above, need the plugin installed and talk to WPEngine support. That is all listed under the FAQ for this plugin.

No worries, usually the simplest solution is the hardest to come by ??

One sure fire way is to use a VPN. I use Mullvad for testing my GeoIP redirects, then I can place myself anywhere in the world and test until my heart is content ??

Alright lets take a look ??

function country_geo_redirect() {
  $country = getenv('HTTP_GEOIP_COUNTRY_CODE');
    if ( $country == "US" ) {
      wp_redirect( 'https://us.domain.com', 301 );
      exit;
    } else if ( $country == "FR" ) {
      wp_redirect( 'https://fr.domain.com', 301 );
      exit;
    }
  }
add_action('init', 'country_geo_redirect');

A few things to be careful of when copying and pasting

1. Watch the quotes “FR” vs “FR” – smart quotes will give you problems, straight quote marks is what you’re after
2. The formatting of what you had was all off. You had semicolons (;) where you didn’t need and was missing single quote marks (‘)
3. I would stick this function at the top of functions.php due to the importance of the function

I’ve used this GeoIP functionality a bit, so if you have anymore questions just ask.

Goodluck!

So I’m getting a little closer

function country_geo_redirect() {
  $country = getenv('HTTP_GEOIP_COUNTRY_CODE');
  if ( $country == "US" && !is_page( 'us' ) ) {
    wp_redirect( 'https://domain.com/us', 301 );
    exit;
  }
}
add_action('init', __NAMESPACE__ . '\\country_geo_redirect');

The problem I’m having now is when the redirect happens I end up in a redirect loop, though that’s exactly what I’m trying to prevent with the

&& !is_page( 'us' )

piece in the if statement

Yeah as I mentioned to AlfonsBerger via email, it’s a little overkill but in this case we want to be very specific in what we’re hiding!

Yep sure thing: rustybones [at] gmail [dot] com

Hi,
I just updated to 1.10.5 and it still works for me, have you got a URL that I can check?

Nice one David, that fixed it. No worries we all have our off days ?? Keep up the good work!