zachurbanbird

I understand, thanks for reaching out even after a few days! I was able to resolve the issue today (5/23/2024). Turns out, the issue was not with Simply Static.

Posting for anyone else who may have a similar problem:

The issue for me appeared to be dealing with Elementor actually, as when an image is resized using Elementor, that plugin will create a copy of the file with the exact dimensions during the resize. When this happens, Elementor appends several random characters to the end of the file to distinguish it from the original, which it also keeps.

So in my case, the image was being renamed by Elementor, and then Simply Static was just going with what Elementor gave it. Elementor was being a little problematic there, but on my local machine I just moved the export to a lower nested folder which allowed the file path to be within the 260 character limit for Windows, and since the URL character limit over the internet is over 2000 characters, the image displays properly when on a live site. Ergo, I needed to work around Elementor’s naming scheme and accept a lower nested folder in my files (at least temporarily while troubleshooting).

Thanks for being willing to check this out!

Ah, Elementor! Well, I’m glad the issue was unrelated to Staatic.

Yes, when I place the export onto a live web server, the PNG displays as intended. Thankfully, internet URLs have a much larger character limit, so the browsers don’t have the same problem that they do handling offline files. If I want to edit the file name to be closer to the original, that’s going to be a problem for the Elementor support forums or an additional plugin.

While I’d love to troubleshoot my exports from within very specific file paths, the solution here is really just to accept Window’s file path character limit and work around it by having the export on a live site or in a lower nested folder, or to just ignore that the file doesn’t display properly. Either way, this issue is unrelated to Staatic.

Thank you for your information and support!

Thank you so much for your in-depth reply and your willingness to give support! Your team is excellent.

To answer your requests:

1. The logo does display properly on https://urbanbirdservices.local.
2. Here are some file paths as requested:

The username given on my system is ‘zachb’ (my name) and yes, the file paths mostly follow the standard setup.

For the logo from within Local WP, which displays properly:
C:\Users\zachb\Local Sites\ubs-website\app\public\wp-content\uploads\elementor\thumbs\UBS-Logo-2024-02-06-High-Quality-Cornerless-qlggdi1juyf9cleg0psnukzxka2r3my325cxh7weie.png
Character length: 176
The fact that this PNG file here already has a file name with the appended 40 characters is interesting, as this file is within LocalWP, which may indiciate that this is an issue unrelated to Staatic.

For the logo from within the Staatic Export, which does not display properly:
C:/Users/zachb/Documents/Zach’s%20Documents/Projects/Active%20Projects/UBS%20Wordpress%20Migration/Project%20Files/Staatic%20Files/Staatic%20Export%201.1/wp-content/uploads/elementor/thumbs/UBS-Logo-2024-02-06-High-Quality-Cornerless-qlggdi1juyf9cleg0psnukzxka2r3my325cxh7weie.png
Character length: 280

When the Staatic Export is moved into a lower nested folder, such as the following:
C:/Users/zachb/Documents/Staatic%20Export%201.1/wp-content/uploads/elementor/thumbs/UBS-Logo-2024-02-06-High-Quality-Cornerless-qlggdi1juyf9cleg0psnukzxka2r3my325cxh7weie.png
Character length: 174
the PNG does display as intended, which leads me to think it is an issue with the file path length.

If the PNG was able to retain the same name as it had received when entered into wordpress, then it would have the file path of:
C:/Users/zachb/Documents/Zach’s%20Documents/Projects/Active%20Projects/UBS%20Wordpress%20Migration/Project%20Files/Staatic%20Files/Staatic%20Export%201.1/wp-content/uploads/elementor/thumbs/UBS-Logo-2024-02-06-High-Quality-Cornerless.png
Character length: 237
Which leads me to think that the PNG would display as intended when named properly.

3. Checking if the logo URL referenced in the HTML source code of the page matches the one referenced in the error:

When on the dynamic version of the site, if I right-click to inspect the page or open the image in a new tab, the URL in both cases is given as:
https://urbanbirdservices.local/wp-content/uploads/elementor/thumbs/UBS-Logo-2024-02-06-High-Quality-Cornerless-qlggdi1juyf9cleg0psnukzxka2r3my325cxh7weie.png

The URL mentioned in the error was:
https://urbanbirdservices.local/wp-content/uploads/2024/03/elementor/thumbs/UBS-Logo-2024-02-06-High-Quality-Cornerless-qlggdi1juyf9cleg0psnukzxka2r3my325cxh7weie.png

These two are not the same, but I’m not sure what to make of that. I suppose that means the error is unrelated to the logo displaying?

Thank you for your timely reply! I look forward to hearing more about this.