Featured Image Dead

I should add that images in the body are fine. This is just a featured image issue.

I have the exact same issue and theme. Maybe it’s the theme contributing to our trouble?

Unreal, Ghostpool is asking me if the cloud images used to work. I’m still in build mode and haven’t launched yet, but I’m 95% sure that I felt that the frontend upload component was working through and through. Can you confirm that with 100% certainty that AWS and Cloudfornt were working correctly with featured images in a prior versions of Gauge?

Brad and D-Brains, what say you, any known issues related to this on your side?

I can’t sorry. I get the impression it’s to do with Aqua Resizer rather than the S3 and Cloudfront plugin.

Unreal I, is Aqua Resizer a stand alone plugin or part of the Gauge plugin? I have turned off EVERY plugin and this issue still happens.

Hi museumtrade – it’s a script that the theme uses to resize the images you upload (generating thumbnails etc.).

GhostPool suggested I make some changes to the script however it didn’t work although it’s certainly possible I did it wrong. I’m definitely not 100% it’s the issue.

A workaround that the S3 plugin author could offer us would be to include, for example, a checkbox that lets us exclude an image from AWS/store local or whatever.

Hey Delicious Brains, you getting all this goodness? Unreal has some really nice insights here. I can’t speak for him, but I’d be willing to pay for a pro license to get this working.

What say you???

Do the featured images work when you disable the option ‘Remove Files From Server’ under the advanced options?

In order to test this you will need to set the option to ‘Off’ and upload a new image, ensuring that the image exists locally within the wp-content/uploads directory.

Ashley

@museumtrade

As a work around, edit aq_reziser.php which is located in gauge\lib\inc and comment out the following:

// Check if $img_url is local.
//if ( false === strpos( $url, $upload_url ) )
//    throw new Aq_Exception('Image must be local: ' . $url);

AND

//if ( ! file_exists( $img_path ) or ! getimagesize( $img_path ) )
//    throw new Aq_Exception('Image file does not exist (or is not an image): ' . $img_path);

That has worked for me.

Thanks for the code Unreal! It’s beyond my ability and comfort level to use it, but I passed it on to Ghost pool. He just released 3.7 and looking at the change log he may have worked on the Resizer. Again, a bit beyond me to translate all this info, but promising. I’m going to run tests later tonight.

Apologies for not responding earlier. The update doesn’t (appear) to address the issue that you and I have. Have you had any further success?

The issue I have is relating to thumbnails which appears to be caused by a combination of the Aqua Resizer and this S3 and Cloudfront plugin.

What I’m finding is that when I upload an image, that image and those created in different sizes at that time are successfully uploaded to S3. When I, for example, choose an image as a featured image, the resizer may create an image of 300×300 if that’s the thumbnail size I’ve set for a particular post. That new image is not uploaded to S3.

Hello,

I was having a similar issue with a featured image not displaying while using another Ghostpool theme (Score) and the fix that unreal posted helped me resolve my issue.

It may help someone else so I’ll relay the steps you need to take:

1. This particular theme doesn’t use Aqua Resizer, it uses the vt_resize function (which I believe has been deprecated since 3.5. Why is it still being used?)

2. Anyway, locate a file called image_resizer.php in score/lib/scripts…

3. From line 69, comment out the following:

// check if file exists
			// $base_file = $file_info['dirname'].'/'.$file_info['filename'].'.'.$file_info['extension'];
			// if ( !file_exists($base_file) )
			// return;

4. Done! Try uploading your images again with “Remove Files From Server” set to ON and it should work.

Hopefully, this will reach someone out there!

Hi Unreal, and all others interested in this. I did my best working with Ghostpool (who’s awesome and quite responsive), but alas we could not track down the issue. I think he would have had an easier time if I was more html savvy, but I’m a plugin only kind of guy unfortunately. He did give me a new aq resize file that fixed the problem…but caused a different one. Maybe one of you could try this php file and see what I mean and maybe you could better translate what is working and why, and what it not working and why. Basically it solved the issue entirely, but made the widget and footer areas weird and compacted and the inset featured image in the post became a weird compacted bit of text. Anyway, feel free to write me at [email protected] and I’ll send you the replacement php file to try out (I can tell you where the file resides if you need me to, but I have to go look it up). I HOPE someone can solve this???!!!

Hello out there, I got another reply for the illustrious Ghost Pool, but I can’t really help him back. Does anyone out there know what to say back to him,anyone know what URsS is?

Since the image scripts are different I can’t see how this would relate to the Aqua Resizer script.

However I’ve been speaking with my developer who does all my customers custom work and they say they commented out the lines of code in aq_resizer.php I mentioned previously and the CDN images were working. They said that the customers didn’t use any CDN plugins, to which I asked how they converted the URsS from the WordPress server to the CDN server, but I’m still waiting a response. Do you have any insight into this? If you didn’t use a plugin how would you tell WordPress you’re using a CDN server?