One reason I love working with the NZCS as a client is that they promote professionalism when it comes to ICT.
That brought my mind to software in general, especially if I am to shift this blog to Wordpress.
If you follow my Tweets, you’ll know that I suffer a daily Firefox crash ever since I upgraded to 3.5. The earlier 3.0 was ﬁne, and it still runs successfully on my Asus laptop, running Vista.
Today I took the PageMaker 7 trial off my desktop machine after discovering many ﬁles crashed on opening. The old 6.5.2 works ﬁne. We still have a few stationery templates on it, not to mention my résumé—important in those expert-witness cases.
It’s not the only program to be more buggy with a newer edition. Others that come to mind include:
It makes you wonder if these chaps ever tested their software in real-world conditions, or took note of the feedback offered. I’m wondering if another country can do it better.Posted by Jack Yan, 12:00
Why can’t the Firefox people post this very simple solution?
For years now, I will occasionally happen upon a bug where Firefox refuses to open a PHP page. Instead, it prompts me to save it:
If I attempt to open it, it is a tiny XML header ﬁle. The error is with Firefox’s ﬁle type handling.
I can go back to 2006 and ﬁnd this error being discussed, usually among Ubuntu users: it seems to surface more often with them than with Windows users. Nevertheless, it comes up often enough.
You’d be hard pressed to ﬁnd a straight answer. Most technical people prefer blaming the user, or the site, or the server, before they blame Firefox. I do not understand this, given that the error never surfaced in Internet Explorer and I have yet to see it in Safari. It is, as with the character set problem I encountered many years ago, a Firefox bug, but one that Mozilla does not seem to acknowledge.
In all these years, I have only seen one non-Ubuntu geek discuss it as though it were real and not a product of the collective imaginations of certain computer users. That page is here. Sadly, Firefox has moved on since he wrote the page, so the tips about editing about:conﬁg do not work, and the browser no longer allows for the deletion of ﬁle types from the Tools–Options–Application menu (the successor to the Tools–Options–File Types–Manage page he writes about).
However, one tip he gives still works, and I have managed to overcome the error.
One needs simply to delete the mimeTypes.rdf ﬁle he writes about. There are indeed two copies of this ﬁle, so the one that needs to go is in a folder called something like this (in Vista and, presumably, in Windows 7):
The parts in asterisks will be customized to your details. A similar one is in C:\Documents and Settings on Windows XP.
1. Find this, or use the search tool.
2. Go into the folder.
3. Close your Firefox browser.
4. Go to the mimeTypes.rdf file. In my case, I renamed the ﬁle to mimeTypes-old.rdf.
5. Restart Firefox.
All being well, a new mimeTypes.rdf will automatically appear, and will probably be smaller than the original. Once it does, delete the old one. If it doesn’t appear, put the old one back to its original name—you are now in uncharted waters.
The trouble has disappeared for the time being, so here’s hoping a few more of you, who ﬁnd that Firefox cannot open PHP pages without prompting you to save it, can get a resolution with the above. It’s taken over a year for me to ﬁgure it out; hopefully, you will only need a few minutes! Jack 1, computer bofﬁns 0.Posted by Jack Yan, 00:00
I’m very likely returning to Blogger for my own posting, after the failure of Vox.
The Six Apart people, who run Vox, have been amazing in trying to help me ﬁgure out my issue, but despite eliminating dormant neighbours and about 7 kbyte of tags from the blog—which should make it more trim than it was before the site ceased to let me compose readily on October 28—I’m still at my wit’s end.
As I removed today’s set of neighbours, I discovered many who had left Vox after being fed up with its various bugs. However, only author Patricia Volonakis Davis has exactly the same symptoms as me, and she has relatively few tags to her 50 or so blog posts. Whether it’s down to the tags, dodgy neighbours or a corrupted Vox database is anyone’s guess.
The compose screen takes anywhere between two seconds and two days to emerge, and generally takes between 15 minutes to six hours. I have put up with this for nearly two months.
Another possibility is shifting this entire blog on to Wordpress, which remains an option, since Blogger itself has been shown to be horribly unreliable on numerous occasions.
I will still have to go on to Vox to moderate some of the groups I run. Another down side to the site is the number of sploggers who create fake accounts and overrun the groups. (That’s right: sploggers can create posts where I can’t.) I left one yesterday, on social media, after ﬁnding it overrun by sploggers: the site owner herself had left, so there was no one to take care of business.
I’ve prided myself on running very clean groups there, where members can operate in a spam-free environment.
It looks like December 2009 is when I might undo the split between a work blog and a personal blog. Back in 2006, as a Vox beta tester, I liked the site but could not see myself abandoning this blog, which is, after all, at a domain named for me.
It’s lucky I kept this going, otherwise, I’d face the difﬁculty of building an audience here back up from scratch.
Vox offered numerous advantages, including storage space for images and videos, which suited my forays into digital photography nicely. I was able to share some work-related videos there. It’s something I’m going to have to do without (YouTube is too unreliable, and Vimeo too strict, even for licence holders of videos), although I do have a lucire.vox.com blog there where some of these things can still go. (My hesitation is that it is branded with the Lucire name, so it limits what I might like to put up.)
I also enjoyed having the luxury of tags, and I am not sure about whether Blogger labels are related. It might be time to ﬁnd out.
So for three years, the trivial, throw-away comments, clips from favourite TV shows and other non-sensical items went to Vox, and this space was left to more “serious” matters (with some exceptions along the way).
All this is, of course, moot. I don’t know if I will enjoy returning to Blogger, for starters. I have to hack in HTML because the compose screen here will not allow hard spaces for paragraphing, and I don’t believe in having line breaks between paragraphs. Tumblr has proved to be a fairly good platform if I don’t want comments—but what is the point of a blog, and the engagement that they should have, without them?).
There is no point forcing myself to adapt to a technology when the opposite should hold true. But right now, this looks like the way forward, so expect less work-like items surfacing back here from time to time.Posted by Jack Yan, 00:12
Get this blog via email
Individual JY&A and Medinge Group blogs
Earlier entries at the Beyond Branding Blog
Rate me on the Eatonweb Portal
(Bad) 1 2 3 4 5 (Good)
Rice Bowl Journals
Blog Search Engine
< ? kiwi blogs # >
Globe of Blogs
Truth Laid Bear
World Blog Directory
Blog Directory Submit
DonateIf you wish to help with my hosting costs, please feel free to donate.
Copyright ©200210 by Jack Yan & Associates. All rights reserved. Photograph of Jack Yan by Chelfyn Baxter.