Footer Builder and AWS

Hi,

I am building a site for a client and utilizing both Pro and WP Offload with AWS for media storage. Unfortunately, the footer builder in the latest release of Pro is overwriting the AWS location for the images with the domain address. The odd thing is in the builder itself it looks like it is working and the links are good but once I save and go to the live site it is broken. I have turned off the caching plugin. This is causing the images to be broken links.

thanks

justin

Hi there,

Thanks for writing in.

Why doesn’t this image exist http://spectral1.bostonelf.com/wp-content/uploads/us_flag1.gif? Does that mean you’re directly adding your images to your CDN

Plus, it’s only normal for the theme and plugins to use the site’s URL, then it’s the optimization plugin that usually changes those URLs. Could you try checking this first https://theme.co/apex/forum/t/header-toggle-bug/25097

Thanks!

Thanks for the quick response. I cannot understand why that link would have anything to do with images being overwritten by Pro theme. I am uploading images via the library but once it is uploaded to AWS it deletes the copy on the site to keep the size of the site down. Also, this is not normal. This is not happening in the Header Section if you look at the site. And when I am working in the footer builder and add the image the theme is using the AWS link. It breaks when I save it and then exit the footer builder and go back in. This is extremely frustrating. I am using the latest version of Pro 2.01. Please check the site and advise.

thanks

justin

hi There,

Can you please send us login details in secure note so that we can have a look.

Thanks

If that was the case then the header would be doing the same thing. And all the images on the pages would be the same thing.

Hi there,

There is no overwriting, the Pro only uses the URL provided by the system (Wordpress itself). The plugins do the same, it uses the URL provided by the system. The optimization or CDN plugin could change the URLs, but only after the theme and plugins inserted them.

Try re-uploading your images on your server and turn off this options Remove Files From Server, then insert it to your footer again. Maybe it’s failing to rewrite the URL since the images are now deleted on your site. And test it again.

Thanks!

If that was the case then none of the images would show up in the header or the content areas built with cornerstone but it is only happening in the footer. and that works but then it serves the image from my server and not from AWS which is the point of using a CDN.

Hi there,

What do you mean by it works when serves from your server? Haven’t tried that since images are already deleted from your server. But I’ll continue checking, again, it’s only normal for theme and plugins to use of site’s URL itself, and it’s job of the CDN to change it after the URL is inserted and not before.

Thanks!

When I turned off the option Remove Files From Server the image showed on the front end when I refreshed my browser but the address it was being served from is http://spectral1.bostonelf.com/wp-content/uploads/us_flag1.gif and not http://spectralevolution.s3-us-east-2.amazonaws.com/assets/20180301202439/us_flag1.gif like all the other images and documents. So the footer is utilizing the media folder for the site and not the CDN.

thanks

justin

So I have been doing a lot of troubleshooting. I rolled back to the last stable version of Pro and it works perfectly. Then I updated to the first 2.0 and it broke. There seems to be an issue with the header and the footer builder in the new 2.0 and WP Offload AWS. Can you please confirm or provide a workaround? I would like to be able to use Pro 2.0 but unfortunately also need to be able to utilize AWS.

thanks

justin

I believe I fixed it. I think it has something to do with the way the new V2 an Header/Footer builder output dynamically generated CSS. When I clear the cache in settings for Pro it seems to be working.

thoughts?

thanks

justin

Unfortunately, that worked but now does not and I have to revert to version 1.2.7

Hi there,

How about cloning your site in staging, the one has older version and another is with latest. So we could compare what’s changed. Then provide the credentials for the staging.

Thanks!

This has got to be the worse customer support I have ever had. I troubleshooted my issue without any help from Themeco and when I find the issue and tell you what is going on you want me to spend additional time and resources in order to help you guys do your job. I am very sorry to come across anger but you guys broke this when you implemented the V2 caching. How can you not figure out what is going on? I used to buy this theme for projects because when you broke something on updates you knew how to fix them. Guess I will start to go elsewhere. This is extremely frustrating. This has been 2 days of spotty response from you at best. Please tell me how to either disable the dynamic css portion that your V2 so that I may keep my sites updated and secure.

thanks

justin

Hey Justin,

We’re sorry you’re frustrated. But, it is necessary to copy your site to staging so we could freely do some testing which involves removing customizations and plugins, testing settings, etc… If creating a staging site is not possible, we could troubleshoot in your live site but please note that troubleshooting might override your progress. We also would need to test the case with Pro and WP Offload AWS plugin enabled only to completely eliminate other conflicts. With that said, please update your site to Pro 2 and also give us FTP access.

Regarding V2 Elements Style Cache, it is recommended to clear the cache. For more details, please see https://theme.co/apex/forum/t/troubleshooting-site-frontend-appears-broken-after-updating/24859

I hope you’ll understand the process. We want to help and know the cause of the issue.

It is very frustrating because it seems to be isolated to the Footer builder. Something is overwriting the img. I have create 2 sites. One for 1.2.7 and one for 2.0.1. I do not use FTP so hopefully that isn’t an issue. I will supply login in secure message. And I tried deactivating all the plugins and still happens.

Ok so a possible update as I hunt down what is going on. I tried an experiment and created a global block using V2 image and Classic Image and everything looks great when I am in editor. Once I insert the Global Block in the footer or on a page the image using classic reverts to the wp-content instead of AWS and breaks and the V2 image displays perfectly. Could there be in issue in the way that both the header/footer builder and Global Blocks are saving and rewriting the images? thanks

Hi there,

I’m sorry if I’m requesting another staging, it’s the only way for us to investigate it since I can’t reproduce this issue on my installation. Plus, it’s something unknown to us, especially how the CDN works. The CDN shouldn’t modify the internal URLs of Wordpress, rather, it changes the URL only after the output is created/generated. So it shouldn’t have any problem even if the builder or editor inserted the original URL.

I created a sample footer in staging site with 2.0.1 and inserted a global block, the image URLs aren’t replaced or overwritten, they are still from CDN. Then I inserted and standard element and it does insert a URL with /wp-content/, I’ll continue checking in that area. And please provide your FTP login credentials, it could be related to wp_get_attachment_image_src()

Thanks!

I have supplied 2 sites one with 1.2.7 and one with 2.0 and the login credentials and explained I do not use ftp. This issue seems to be isolated to the footer builder and it overwriting the media address. I have even tried to hardcode the images using them as backgrounds withe the AWS address and it looks fine in editor until I save and then refresh and then it is wp-content. Thanks

Is there a way to temporarily disable the dynamically generated CSS for the footer by adding a function to the child theme so that I can test to see if that is causing the issue? It seems to be isolated to when the footer is saved and then the page is refreshed. thanks