Using Microsoft Expression Web, I recently redesigned my web site to remove its reliance on the FrontPage Server Extensions and the FrontPage Search Component.
Removing the FrontPage Search Component meant finding a replacement – I chose Google’s Custom Search Engine – $100 gets you 20,000 search queries a year. It was very easy to implement on my site – create an account with Google, grab the code that verifies you own the site, and you’re good to go. I actually did this on the old site before I started the redesign.
Removing the dependence on the FrontPage Server Extensions meant, among other things, changing the filename extension on any .asp page to .htm. I did this as part of the site redesign.
Once the redesigned site was launched, however, I found that the renamed and/or deleted pages with the .asp extension were still showing up in the search results on my site. Fortunately, Google makes it very easy to fix that. Go to the "sites" link in the Control Panel of your Custom Search. On the "Basics" page, under Sites to search, click "Advanced" and under "Excluded Sites" add the URLs of the pages you want removed from the index. You can exclude individual pages, or exclude sites in bulk, one per line.
The great thing about this feature? It takes effect immediately.
What would you do if you got an email like this?
If you practice “safe-hex” you would know not to click on the link to confirm your email address – to anybody, any time. Not your bank, not the government, not any business, and not Network Solutions. But that’s who sent me this email – Network Solutions.
This email has all the characteristics of a “phishing” email – “Phishing is typically carried out by email spoofing or instant messaging, and it often directs users to enter details at a fake website whose look and feel are almost identical to the legitimate one.”
I’m sure if I had clicked on the Confirm button it would have taken me to a web site where I would have been asked to enter my Network Solutions Username and Password.
Sorry, Network Solutions, I’m not going to do that. Clicking that link would go against everything we’ve been trying to teach people about how to practice safe computing.
If you want me to confirm my email address, send me an email that contains the instructions on how to do that.
I had a conversation on Twitter this morning with Network Solutions about this – they apologized for the “inconvenience” and pointed me to a post on their blog that says: “please rest assured that these are legitimate, and not a “phishing” scam.”
I’m still not going to click that link, Network Solutions. Sorry – you’ll have to find another way.
So it’s been 2 1/2 weeks since I replaced the SIM Card in my DROID DNA, and the “SIM Card not detected” message has not returned. That’s the good great news.
The more interesting news, however, is from a conversation I had with a Verizon Tech Support guy this morning about an unrelated issue. He happens to have an HTC DROID DNA and also had the problem with the SIM card. He told me that the problem is not with the SIM card, it’s the SIM card tray. The SIM card tray is too small and that’s what causes the card to lose it’s connection to the phone.
I did some searching in various forums and found some threads that confirm that’s what Verizon is saying:
https://community.verizonwireless.com/thread/801377 (In this thread, there is a post from TamaraH_VZW where she says: “I also had the same concern with my DNA. It seems to be a hardware issue with the SIM card tray. HTC will replace the tray for you if you call them 866-449-8358.”)
So my takeaway from this is that if you get a new SIM card from Verizon and it doesn’t fix the problem, call HTC at 866-449-8358 and ask them to send you a new SIM card tray.
Over the last year I’ve gotten the “SIM Card not detected” error message on my HTC DROID DNA a number of times. I would try one or more of the first 3 solutions I found on the Internet which I listed in my post in February 2013. Recently it started happening too often and those solutions did not work for too long.
So I decided to move down the list to item #5: Go to the nearest Verizon store and get a new SIM card. * I did this a week ago today and haven’t had the error message since then. The Verizon rep put in an NFC SE SIM card which adds an additional level of security that other SIM cards don’t have by helping protect your personal information (e.g., credit/debit card numbers, account numbers, access codes, etc.). It’s required to support apps and services, such as the Isis Mobile Wallet.
Here’s hoping this puts an end to the error message and keeps me connected to the Verizon network.
* I made a conscious decision to skip over item #4: Do a hard reset of the phone. It was much quicker to make the drive to my local Verizon store.
The Ellen Show has a segment from time to time called “Oh Puhlice” where she reads fantastically weird police reports. Yesterday, Oak Island, North Carolina was “honored” – you have to watch!
On the Verizon web site it says: Key device enhancements include: Support for the TalkBack feature has been added – this enhancement makes Internet accessibility easier for the visually impaired. After the update, you should be at Version 2.07.605.1 710RD. During the install, it optimized all the apps on my phone – I’m guessing to take advantage of the features added with TalkBack.
At the Google Play Store, it says: TalkBack is an Accessibility Service that helps blind and vision-impaired users interact with their devices more easily. This application adds spoken, audible, and vibration feedback to your device. It is a system application that was pre-installed on most devices and is updated when the accessibility service is improved.
Jason Mackenzie, the President of HTC, has clarified what updates are coming for the DROID DNA, and when. Last night on Twitter, he posted that “Regarding Droid DNA. Update and clarification is that DNA customers will get new Sense experiences (w/ 4.2.2) before end of year.” While I’m happy for the update (I can stop checking for software updates for a while), I’m disappointed that it’s taking so long. But as a long-time developer, I totally understand that no software should be released until it’s ready.
Yesterday I blogged about a Verizon KB article that stated a Droid DNA Smartphone Software Update was coming soon. If you click that link today, you get a page that says: “We’re sorry! No resolution is currently published in the knowledgebase. Select device link to go back to the main Devices page.”
So we are wondering – what’s the story here? Has Verizon reversed course? Or maybe the update’s not coming this month after all? Or maybe somebody just jumped the gun posting it when they did? We’d love to know. And now we are wishing we had grabbed those screenshots we talked about yesterday.