eBay

ricarmic · ‎11-18-2017

As I mentioned in other, earlier threads, my plan was to ignore the HTTPS stuff because it simply hides the problem and it was only affecting my oldest listings.

However last week I got a fairly dramatic ebay message telling me immediate action was required on 380 of my listings. (however buried in the wording it said that I was "encouraged" to make the changes).

I called my buddies on the support desk but apparently a number of people were also wondering about these messages because I was awaiting a CSR for an hour....fortunately I was busy listing other items whilst on hold.

I gave up after the hour wait, and never did talk to anyone, however I realized that that list of 380 items were the ones that pointed to my self hosted pictures.

Back in 1999 in the early days, one really had to do self hosting. In those days my needs were high in terms of storage space so I worked my way up to their largest plan over the next few years (simply because of the space needs)!

Since then, a couple years ago I quit using self hosted pictures, but alas I was saddled with the "someday" job of finding all the listings that had the self hosted pictures, and converting the items to ebay hosted pictures before I could divest myself of the self hosting site.

Someday was probably never going to come, there is almost nothing I hate more than doing something over again!! However the annual fees for that site are over $350 Canadian.

However, the light bulb finally went off, ebay had inadvertently given me that master list of all the self hosted lots!

Sadly these suckers reach back to 2007 so there are a lot of things that need to be modernized in the descriptions etc. The good news is that as I am fixing them I'm correcting, upgrading the descriptions and categories which I think will help them move faster (they have been selling since I use a progressive "on sale" program with the oldest stuff most on sale).

It takes me about 5 or so minutes an item to do the conversion, so there's over 30 to 40 hours of work to convert them.

However I'm consoling myself that a weeks work is going to save me $350 per year going forward so that is making things seem a little happier.

Anyway, I suppose I'd better get back to converting.....down to 277 left to convert!!!

boutiquestepup · ‎11-29-2017

Sorry Guys I just saw your posting

I found a really quick way to update all of my listings from HTTP to HTTPS

go into Selling Pro Manager click on Summary, then click on Improve your listing and click on all the listing that need to remove HTTP click edit, then click on all your listings, click edit fields, select item description, and then select Edit Listing in Bulk - Find and Replace. In Find you enter HTTP and replace with HTTPS

Good Luck

Christine

ricarmic · ‎12-30-2017

@ricarmic wrote:
Down to 189 left to convert.....WOO HOO half done......

WOOO HOOOO!!!!!!

Report now says: "Non-secure content (HTTP) issues(0)"

Just moments ago finished converting the last one!!!!!

Glad to have that pain in the bum job done.......

Happily some of the converted lots have sold, many had old categories that weren't nearly as appropriate as some of the new ones....and or descriptions that could really have used modernization....

pjcdn2005 · ‎12-30-2017

Congrats!

rose-dee · ‎12-30-2017

@boutiquestepup wrote:
I found a really quick way to update all of my listings from HTTP to HTTPS

go into Selling Pro Manager click on Summary, then click on Improve your listing and click on all the listing that need to remove HTTP click edit, then click on all your listings, click edit fields, select item description, and then select Edit Listing in Bulk - Find and Replace. In Find you enter HTTP and replace with HTTPS

I think this was discussed a while back, on another thread on this topic. However, I just want to flag the warning that was posted there. Don't just Find/Replace "http" with "https" -- what you will end up with is code that is already https reading "httpss", because the letters "http" will be replaced by "https" everywhere they appear. So what you'll be doing is making your already-compliant code non-compliant (or, more accurately, turning it into digital gobbledygook).

What you need to specify is a Find/Replace of "http://" with "https://" so that only the non-compliant code is impacted. You can probably leave out the "//" (double forward-slashes), but I wouldn't, just to be certain. But then I'm a belt-and-suspenders type.

rose-dee · ‎12-30-2017

@ricarmic wrote:

WOOO HOOOO!!!!!!

Report now says: "Non-secure content (HTTP) issues(0)"

That must feel good!!

Haven't even started on mine -- I caught a horrendous 'flu on Dec. 21st that went straight into my chest and am just now finally recovering. No Xmas dinner (turkey is still in the freezer, thank goodness), no holiday festivities, and there certainly won't be any partying for me tomorrow either. Like it never even happened...

DH is the real hero, eating up all the Xmas treats for the last 10 days before they expired.