Hi everybody,
It’s taken a few days but it looks as if we have completed all of the tasks related to server migration to our new cloud server location. Like any high-tech endeavor there were a few hiccups, and some folks had difficulty reaching the new website due to DNS propagation delays, old bookmarks, and browser caches that refused to clear.
The problem had to do with the fact that in the old server location on WordPress.com the site was accessible by two different domain names that brought you to the same location. Unfortunately this caused some confusion with browser cache and in some browsers made it nearly impossible to clear. There’s also the issue of people that have subscribed to the website via e-mail. For some reason even though all the subscribers migrated, the connection to receive e-mail automatically did not and people are finding themselves needing to resubscribe to get e-mail notifications of new posts.
So, given what we’ve learned I prepared a few tips and tricks for you and I’m cross posting this to the old website as well.
- DNS propagation seems to have been fully resolved and there should be no problem reaching Wattsupwiththat.com from any location in the world. So, there’s nothing you need to do for that issue.
- Browser caches are still preventing some people from reaching the new website, and even typing in Wattsupwiththat.com sends some people to the old website at wattsupwiththat.wordpress.com. To solve this, you must clear your browser cache. There’s no other way around it if you can’t reach the new website. The biggest problem had to do with Firefox browsers. They have a clear cache function than only defaults back to the last hour of browsing. You need to set that for “all time” and then clear your cache. For Android users, using the default browser that comes with your device you will need to do a similar thing. I can’t cover every possible circumstance here but I can direct you to a webpage that is helpful, which covers all of the most common browsers with specific instructions. Follow this link: http://www.refreshyourcache.com/en/home/ then choose the browser you are using from its menu.
- E-mail subscriptions. look for the “follow by e-mail” box on the right sidebar by scrolling down, it looks like this:
- Simply put in your email address and press the “Follow” button. That should do it.
- Bookmarks. Check any bookmarks you made to be sure they have wattsupwiththat.com rather than wattsupwiththat.wordpress.com in them. Edit as needed.
That should do it. I’m sorry for the hassles, sometimes tech migration isn’t as smooth as you’d like it to be.
If you have any other issues not covered her, please leave a comment.
Top tip:
I used to be a Firefox fan, and a couple years ago I found it to be so buggy and problematic that I gave up on it and use Chrome exclusively now. It continues it’s long slide into obscurity as you can see:
As you can see, it’s not just my opinion.
A few other items worth noting are:
- We now have an edit function in comments that you leave. After you’ve pressed the “Post Comment” button and submitted your comment you’ll see it displayed along with a link below for editing it and a countdown timer. You’ll have 5 minutes to make an edit, and once that 5 min. is expired you would no longer be able to edit the comment. This should be sufficient for most users to fix typos and formatting issues.
- Images will no longer directly display in comments, that was a feature particular to being hosted on WordPress.com. I am examining a fix/workaround for this and I’ll advise if I have a solution.
- The ability to vote for a post using the 1 to 5 stars method is no longer available, again this was a feature particular to WordPress.com
- I believe that I have cleared all of the security warning issues related to displaying the home webpage. initially these were caused by failure of the new WordPress Pressable server to properly activate its certificate until DNS was fully propagated. That’s cleared now, but there were also some issues with images being served by HTTP protocol rather than HTPPS protocol, and this caused some overly alarming security programs to complain. I think I fixed all that but if not, please let me know.
I appreciate your patience and your patronage during this process, please let me know if there’s anything else I can do to make your experience here at WUWT a pleasant and productive one.
-Anthony
Discover more from Watts Up With That?
Subscribe to get the latest posts sent to your email.
Anthony ==> Well Done– this sort of thing took a team of a dozen guys at IBM.
Ok I just have to point out the chicken / egg item:
“Browser caches are still preventing some people from reaching the new website, and even typing in Wattsupwiththat.com sends some people to the old website at wattsupwiththat.wordpress.com. To solve this, you must clear your browser cache.”
but if you are on the old website you won’t see those instructions to clear your browser cache….you have to already be on the new website…..which means your cache is already clear….I’m so confused 🙂 🙂 🙂
Anthony has done a fantastic job keeping the old site updated with instructions on how to get to the new site.
That’s how I finally found my way here.
Outstanding!
I like the edit feature a lot, but I sure do miss the images.
Would it be possible to enable the IMG tag?
One hint: if you use HTML entities like < and   you may see:
I agree with everybody’s comments about the images – they were an important element to help contributors illustrate their discourse & make their points clearly & concisely, right or wrong. It would be REALLY good to get them back!
I have also run into the 500 internal server error for reasons that elude me.
Yes, the edit feature was great (while it lasted), but images are more important than the edit feature.
Phil, do you use & … ; constructs in your posts? That is what trigged the “500 Internal Server Error” for me.
Never even noticed the move, everything working fine. Use Firefox on Samsung S7 edge and Slackware Linux. I do clear data in exit. RSS not problems either, use Feeder on Andriod and QuiteRSS on Linux.
Like the way the site looks.
FYI – Firefox cache clearing, you can clear only the DNS cache.
I’m another “Lunatic”, running it on Linux Mint 17, and can report a perfect transition to the new site – didn’t need to clear the cache or anything, though that’s mostly because I’ve set the browser to clear everything on shutdown anyway. I’ve always liked WP because their sites still work as far as posting comments even without enabling them – or even the host WordPress sites! – in NoScript. Cool stuff.
Congratulations to all concerned on a fine job!
I also agree re PM starting to get sniffy about NoScript. (All they really need is an “Advanced” button somewhere in the settings page, surely, like other software.) Like most NoScript users, my attitude is that the browser may change, but the NoScript won’t!
I had to reset my Android Chrome cash bit interestingly the Dolphin browser worked just fine. I.foind it because I wanted to stop using Chrome but Android Firefox is almost unusable (especially on conservative websites hmm). Anyway for those who find Google evil and want cut back a bit Dolphon browser for Android.
The latest Firefox is very fast. Not so sure about its other features, but it has definitely improved.
The post was truncated in the WordPress app, any idea about that?
Anthony, on the banner the “Home” link is http (not https)
Lie with dogs – like G00gle, AOL, Mozilla – and get fleas. Use a no-performance browser for some security. My text only browser, among others, works fine.
Please note the initial double entendre.
Great job WUWT.
Chrome? I’ll suffer some minor inconvenience before kneeling for the Monopolist SOB’s
One thing that isn’t working are updates to my Guide to WUWT at https://wermenh.com/wuwt/index.html . I’ve been busy the last few months, but I should have time to look into it the next few days. It may be a biggish job to get it going again, it may be easy.
I haven’t look at the WUWT test page in ages. It must be way overdue for a trim, and I guess some big updates. No images? Yikes!
I’m hearing a few reports that the ENSO meter is displaying. That was one thing that needed (has needed!) a http -> https change in the link. It seems to be working for me on various versions of Firefox. Let’s see if it settles down.
“I appreciate your patience and your patronage during this process, please let me know if there’s anything else I can do to make your experience here at WUWT a pleasant and productive one.
Anthony”
Well, it would help make my experience at WUWT pleasant and productive if you would pay me at least $5.00 for every comment I make here. I don’t think that’s asking too much, especially if you charge other posters for their comments.
Very sorry to read of your recent passing, Douglas.
https://www.findagrave.com/memorial/188384650/douglas-j.-bender
Depending on where you’re visiting from, $5 might be on the cheap side for your insights.
This is a test — please ignore.