I’m posting this merely as an aide memoire to myself and also in case it helps anyone tearing their hair out regarding a reCaptcha form that was refusing to pass variables over.
I had a form on an old site using tables. On one page the recaptcha form worked well. On another, the reCaptcha was failing due to invalid-request-cookie. On further investigation, it turns out that reCaptcha form wasn’t passing any form variables to the next page, even though the rendered HTML on the page had the form input fields in the correct place.
To cut a long story short (too late), I noticed that the form declaration was inside a table - ie <table><form name=”form-with-recaptcha-in-it”…..</form></table> which isn’t valid HTML.
Swapping the form to be positioned outside the table worked first time.
iTunes match doesn’t seem to be working on iOS6 for a lot of people.
Every device of mine was fine until iOS6 and the iPhone5. When I went to play a song, the phone waited for a second or so, and then went crazy. It skipped to the next song and the next song and the one after that. Looking at it in the iTunes app, it was attempting to download each song for ¼ of a second and then going on to the next.
Even if I turned my phone to another app and had the music on pause, it would skim through until it found one in my downloads. We often got to #538.
I went to the apple site and got the usual unhelpful gubbins.
I tried the turning it off and on, disabling network data, resetting music device, resetting settings, resetting phone, but it wasn’t coming back.
Finally, I was on iTunes proper on my mac buying a song when it appeared that iTunes Ts&Cs had changed, meaning that I couldn’t buy.
Once I had updated my Ts&Cs iTunes Match was back on my iPhone. Problem solved.
It strikes me as pretty poor that Apple doesn’t give a correct error screen when on the music app or the iTunes app when using iTunes Match. It’s up to you to work out the problem yourselves.
Twenty-five years ago, as digging starts on the Channel Tunnel, Rick Astley tops the charts and Black Monday sparked the last recession, the seeds of the internet were sown by world wide web pioneers: whilst Amstrad were launching the Spectrum 128k+3 complete with floppy drive, the first .co.uk address was registered.
It took almost ten further years for requests for domain names to outstrip capabilities of the Naming Committee (requests were initially emailed to Dr Willie Black) and for Nominet to be formed, by which time we had tiny mobile phones resembling Star Trek transponders and the first version of Google was coded and sat on Standford University servers.
Back in 1996 it was the received wisdom that a .co.uk domain was generally considered second best to a .com domain. Then again, in 1996 Gina G and Peter Andre were considered viable pop stars. It was a funny time.
These days, for UK businesses – especially ecommerce sites – .co.uk is the preferred option. In part, Google has driven this trend on: local search is far more important than it was 16 months ago, let alone 16 years ago. But in part, it is also driven from user experience and customer feedback – people feel safer knowing that if they find a .co.uk site in the Google result pages it will definitely ship to their location; making the same presumption with a .com is always a risk.
In fact, 80% of British users prefer a .co.uk domain to a .com in SERPs, and you can only see this figure rising. With search engines requiring a preferred TLD, the .coms are becoming used as placeholders, as local search becomes the norm.
So what do the next 25 years have in store for Britain? Voice activated computers connected to massive data, moon holidays, robot servants and hoverboards (please, please can we have this one)? Who knows, but Nominet will still be here and the .co.uk domain will be as popular as ever.
This post has been sponsored by ‘A great place to be’
Why are Apple making developing websites with Safari a pain? It used to be my favourite tool, but recent changes in Mountain Lion will make Safari my least-favoured browser.
You can see the argument for deprecating RSS feeds. They’re a bit like cassette tapes: cherished by a dwindling minority and ignored by the majority. But here’s where Apple have made a totally inexplicable decision: When you load up an RSS feed, the page refuses to show you a damn thing.
OK, but you’re going to show me the XML, right?
No. Safari has received the XML, interpreted it as RSS, then decided not to show you anything. No view source code or view source XML, nothing.
Who at Apple took this decision? Why did they think that developers would not like to be able to see the XML that they’ve created? What kind of madness is this?
This one blew me away just now. Absolutely shocked me to the core. When I view source now, it’s not the source of the loaded page at all, but the source of the rendered DOM, once all JS has been executed.
If I had wanted sautéed potatoes, I would have ordered sautéed potatoes. I ordered fries, so give me my goddam fries.
Safari was the only browser doing view source properly before now and now they’ve killed it. Firefox and Chrome used to load in the source as a separate request, which didn’t work either.
Out and out the most used feature on Safari by me was the activity monitor.
What element on the page is holding up page load? Find out with activity monitor.
How many calls are my adserving partner making? Find out with activity monitor.
Is that an official Twitter feed? Find out with activity monitor.
What’s the filesize of that image? Find out with activity monitor.
How many different hosts does this page? Find out with activity monitor.
How many elements are on this page? Find out with activity monitor.
Of these, how many come from 3rd parties? Find out with activity monitor.
I could go on, but you see where I’m coming from.
Why does Apple see fit to remove these things and not give you an inkling as to where the information now resides?
This was awesome. See what tabs your other devices have open. Great, let me have a look.
But wait, what? Although the tab sits on Safari now, the iOS devices won’t be able to fill this space until iOS6 comes out in 2 months time?
THEN WHY PUT IT IN NOW?
To most users, the Safari 6.0 will be great – faster browsing, tab view, err, Chinese stuff – but for developers Safari sucks big time. Hopefully this is just Apple’s customary slap on the wrists for early adopters and this will get fixed, but then again it could be a symptom of the direction of Apple in the future..
Every now and again, you come across an unGoogleable problem. This particular one drove me nuts…
I have a new SVN project on an Ubuntu box. I copy files from my Mac desktop to this project via AFP (dragging and dropping with the Ubuntu box mounted as a /Volume) and clean up any resource fork files (those beginning with ._ ) that I can see (I use TinkerTool for this)
Problem is, that I then drag across tiny_mce which has hundreds of the buggers nested deep within the file structure.
But I didn’t notice, and clicked the ‘Add’ button to the parent directories in Versions and then commit.
After the commit, I get a few error messages, including things like:
Can’t open file ‘/Path/To/MyDirectory/app/Plugin/Admin/Model/.svn/tmp/text-base/._AdminAppModel.php.svn-base’: No such file or directory
And now, I’m stuck. I can’t commit files, update anything, nothing works. So I try to checkout a new version to a different directory on the same Ubuntu box and get an error telling me I can’t.
So, I root around a little and work out that the repository has a copy of the resource fork files. All of them. The problem is that Versions hasn’t created a text-base version in the .svn directories. Any of them. But it has passed on the actual files and their contents, which leaves you in a right pickle.
I created a new project, exported my old content there, recreating where necessary and then (this is the important bit), I ran this command in Terminal
dot_clean -m /Volumes/path/to/my/new/working/copy/
Which recursively deletes all resource fork files – the -m deletes the files, rather than merge them. As I don’t need the files, I want them gone, but you may want them, so please read the dot_clean man page if you plan to do this.
Then, I add the files in Versions and commit – job’s a good’un
A better solution would be for Versions to support resource files properly – either add the files to the repo and the text-base or don’t add them to either, don’t do one and not the other – madness.
Or, if you only have a few resource fork files that have borked up your SVN project, you may want to use a different SVN GUI app, or command line, and delete (SVN delete, not Mac delete) the files, then return to Versions after this
It’s been over a year since Apple announced that they were going to kill off MobileMe galleries but I think I have just found a decent replacement.
Zing Zang is a completely free alternative to MobileMe that doesn’t clog up your hard drive, as DropBox would, and that has no ads whatsoever. The interface uses a lot of AJAX. It’s slick and user friendly. It can connect to your old MobileMe galleries and download all the content for you, creating new ZingZang galleries.
Initially each user receives 2Gb of space, which can be bumped up to 10Gb if you get friends to join on your unique link – mine is http://zan.gy/MvuZ08 - you get 250Mb for each friend that signs up.
From next month, ZingZang is going to charge for extra storage up to a maximum of 108Gb for $20 a month.
A little while after this post, ZangZing closed their site for business. There has been no official word as to why this was, but my guess is one of the following:
There’s a saying that even in a recession, the undertaker’s is the only business that is unaffected. It seems that in a digital age, this applies also to domain name vultures.
As a rule of thumb, domain names are leased for fixed length periods from a registry such as Nominet or ICANN. The domain name ‘owner’ will generally do this through a third party, such as Go Daddy. When the fixed term is up, they chose to renew the domain name, or they let it slide. If they choose to let the domain name go it is then released on the open market again.
Companies exist whose sole business model is to pick up lapsed domain names and then sell them on to either the same punter or different ones. A bit like a digital rag and bone man.
One such example was my father-in-law, who mistakenly let his domain go – chalidze.com – and it was picked up by some such company who have now held onto it for 3 years. There can’t be many people who want this domain name (it’s his surname. Georgian surname), and it has cost this company somewhere in the region of £50 to renew it for 3 years. More fool them, I thought. And then it happened to me…
I have a site that helps you keep track of your finances with graphs and so on called Pimp My Statement. Now when I first set the site up, I bought both the .com and the .co.uk TLDs. But this being a recession and the site not performing that well, I decided to keep the .co.uk and dump the .com.
A few days after the expiry I received this:
I’m currently considering selling the domain name pimpmystatement.com. As you own a very similar domain I was wondering whether you’d like to submit a bid or offer for pimpmystatement.com. (Price range $2500 to $5000)
And it was early in the morning. And I hadn’t had a cup of tea yet. And this made me grumpy, so…
don’t be so silly
I owned the domain pimpmystatment.com until the 18th March this year, when I decided it wasn’t worth the $19 fee.
You then picked it up for $19 and now, a few days later, you are only ‘considering’ selling it? Pull the other one. This schtick may work, and evidently keeps your business afloat, but the domain name isn’t worth $5 to me, let alone $5,000.
Good luck with selling it to some schmuck, but I think you’ve just wasted your $19
Result? That person relinquished the domain name a day after I sent this email. Could be a good tactic for getting your domain name back from the vultures