The warning that occasionally popped up a few weeks ago has returned with a vengeance as we get closer to its deadline. It’s showing for all my listings, now.
Today, all new uploads mention it. Again, it’s a warning not an error, but it does feel as if some fundamental change has been building up. The question is, is it something in the templates we’re using? What exactly happens when we use a GS template that refers to EPS? I honestly just use one off the shelf, and have never examined its source code very closely.
Of course, all of the built-in design templates only use HTTPS URLs (for many many years).
I still think it’s just a general info message from eBay and nothing is wrong with your listing.
If you want to let GarageSale suppress that warning in future, right-click on the message text and select “Ignore Future Warnings”.
Just here to chime in saying that I am seeing the same with with every listing I upload to eBay, even though I do not use http anywhere in any of my templates. Can we confirm for sure that this is an issue on eBay’s end, and not something in GS that needs tweaked? Thanks!
can you send me a link to a running listing that had triggered the warning when you listed them? I doubt that this is an issue on our side as we have migrated all our links from http to https years ago. But maybe there are still links somewhere buried in your other settings (e.g. the footer, text snippets, image captions).
we have indeed found something in GarageSale that triggers this warning. You will only get this when you use EPS images and when verifying the listing. The reason for this is that we inject fake-URLs into the API call for verifying the listing (as we do not know the actual URLs at this point). These fake-URLs were wrongly using the deprecated http protocol (and were not changed/forgotten in 2017 when all the migration to https were done in GarageSale).
So yes, GarageSale is causing this warning and we are sorry about that. But, on the other hand, this will not be triggered when actually listing an item, so you can just ignore it.
A beta version with a fix for this warning will be released soon.
