henriquemattos

I’m in favor that plugin developers start to operate ONLY in PHP7+. That way the users would force the hostings to upgrade! ;P

Undoubtedly it’s a CDN routing problem. When I was serving straight out of EC2 AMI (Linux) using Apache’s HTTPD I had never noticed it. Only caught my attention because I’ve moved to CloudFront + S3 and it stopped working.

I’m cherry-picking this commit, thanks!

Great, @deltafactory. Will try it and let you aware of the result.

Really thankful. ??
Rick

Using WP Super Cache and now installed Memcached out-of-the-box and got the same error. Wouldn’t like to overwrite default code to make it work. ??

Hi, @eve. Thanks for your support. I am doing that already, yet the main goal in this post was to evidentiate an improvement that could be made. I’m glad you will be able to forward this suggestion to the responsibles. Let me know if I can be of any help! ??

Kind regards,
Rick.

Make sure you’re using pt_BR on your WordPress configuration and save the .po and export the .mo then upload both files to the server.

Sorry to ask, Kamila, but did you upload the file back to the FTP server??

Hi, @kamilanr

You have to open the file wp-content/themes/gridsby/languages/pt_BR.po and edit the translation. I highly recommend the software PoEdit by Gettext. You can get it at poedit dot net.

Let me know if you have any issues.

Regards,
Henrique

Sorry for my confusion, mxxcon. But you got it, trackTiming is exactly what we need! ??

I’ve changed the line in plugins/amazon-s3-and-cloudfront/classes/amazon-s3-and-cloudfront.php as the below code:

[original]

elseif ( is_ssl() || $this->get_setting( ‘force-ssl’ ) ) {
$domain_bucket = ‘s3.amazonaws.com/’ . $s3object[‘bucket’];
}

[edited]

elseif ( is_ssl() || $this->get_setting( ‘force-ssl’ ) ) {
$domain_bucket = $s3object[‘bucket’] . ‘.s3.amazonaws.com’;
}

Beware to remove the extra ‘/’ URI and that it only happens with SSL mode enabled.