http://adverset-cdn.objects.cdn.dream.io/ is the OLD url
http://adverset-cdn.objects-us-west-1.dream.io/ is the new one. All new URLs should use that.
The upgrader did it’s best to correct the old ones, but it looks like it couldn’t figure out your old URL pattern and that it needed to upgrade. 🙁
The best fix would be to edit your URLs from http://adverset-cdn.objects.cdn.dream.io to http://adverset-cdn.objects-us-west-1.dream.io
https://wordpress.org/plugins/velvet-blues-update-urls/ can do that.
Hi Mika,
on further investigation, i noticed that the plugin has missed out a “.” in the url
http://adverset-cdnobjects-us-west-1.dream.io/
where as it should have used
http://adverset-cdn.objects-us-west-1.dream.io/
any thoughts? I tried to update with the velvetURLS plugin but it just says 0 records updates
Cheers,
Dan
Did you fill in a CDN path?
Hi Mika,
No I didnt, I selected from the drop down once I’d added in the keys…
not using an alias, so didnt fill that out
Cheers
Dan
Oh…. I think I know what’s going on.
So it looks like there’s one location where the old objects.cdn.dream.io domain is still set. I can’t reproduce that not showing the . in the URL though. In all my tests, it properly uploads images to the ‘right’ wrong URL.
You’ll want to use Velvet and look for adverset-cdnobjects-us-west-1.dream.io and replace with adverset-cdn.objects-us-west-1.dream.io if you haven’t already.
I’ve pushed a beta version – https://github.com/Ipstenu/dreamspeed/archive/REL_0.7.1.zip
– that SHOULD fix this all over, but I’m still fully testing it. If you want to try it, please do. I think it’s good but I haven’t tested it in as many iterations as I’d like to.
If you use it, please make a DB backup first! (I say that for all beta tests of all things)
Hi Mika, thank you – I’ve used the beta, it all seems to be working correctly to me! I had before used the alias to force the plugin to use the correct new URL, just as a quick fix – but this is much better!
Thank you for your time on this! it’s a great plugin – dreamhost should totally make it official!
Cheers, I’ll leave this as unresolved for now just incase something bugs out and I need to let you know
Dan
WHEW!
Okay, I’m going to run the new version through all my usual insane tests (and handle the WP 4.6 upgrades this week) and roll that out to everyone soon.
0.7.1 pushed to address this, plus to prevent people from even entering data that wasn’t used in the first place if they were on SSL 🙂
Awesome! thanks Mika, it’s all been working without issues for me!
