WordPress Bug – They are Working On It

Everyone that has a WordPress Blog and uses WordPress WYSIWYG interface to write their blog enteries would have noticed that the guys at WordPress have introduced auto-save. Great idea but it has come with a bug.

Each time it auto saves during authoring it throws your cursor back to the top of your post. Just so people know, they know about it and it is a matter of priority that they fix it.

So while they are working on fixing it I suggest not planning any long posts! The other thing I suggest is not to flood them with support requests or bitching about it, that is part the reason that I have posted this :). So give them a chance and you will be loving the new feature in no time.

The only information that I have come across about it is in the WordPress Forum. No doubt they will blog about the new feature when it is fixed! Thanks for the hard work guys, this is one of those rare occasions on WordPress that the users are adversely affected.

UPDATE: Just got this reply via support from WordPress: great service once again, thanks guys – keep at it.

Hi, I’m really sorry for the problems. It is top of the list to be fixed as it was a feature requested by many and this bug was very unexpected. My apologies again. Podz

Updated the Webpage

Nothing major today, I have made a few changes to the Global Geek Podcast Homepage.

Because the web-page for the Global Geek Podcast was such hard work I have avoided changing anything for fear it would all be ruined. But I can say that now it is all set and basically the way it will be for a while, editing it in a minor way was easy. I just cut and paste the HTML our and into Nvu which is an open source WYSIWYG editor for web pages. It is excellent because as you would know from the podcast Sebastian and I do not try to pass ourselves off as HTML guru’s at all. Quite the opposite; we suck! Nvu is highly recommended by myself, especially if you don’t want to spend any money – it works!

As you might know from Sebastian’s blog, he purchased a domain name: sebrt.com for his blog page, which he has “masked” with that domain. So I thought it only fair that the link to his blog be that, so that done he should now be happy.

The other change is that you will notice that there is a link to The Knightsite. There is a bit of a story behind this one. Another great story of networking, Skype and the community of podcasters, bloggers. Turns out that this Belgian dude called Joe (a.k.a Knightwise) was cruising around the Skype “search for contacts” option in Skype. I don’t know what for but eh, he was there. He happened across Sebastian’s Skype id which detailed his podcasting involvement. So Joe called him up, as it happens Sebastian and I were talking at the time and we invited the Knight into the conversation and we all hit it off. Joe is a top bloke and he has a podcast called the Knightcast. It is a great quality podcast; hell he uses VBR encoding at high bit rates – bandwidth must be cheap in Belgum! Plus I think his accent is cool.

The KnightcastSo Knightwise should have a place on our Podcast Homepage. We often talk now and encourage each other with our projects and we are planning some joint ones coming up so that will be fun. It is true that the internet does not know borders or nationality. I am stoked that I have yet another person added to my own community that is mutually moving towards bettering our “space”. There is no way in the world that my own universe would have opened up as much as it has without this wonderful medium called the internet, which is starting to reflect real world interactions and ways of meeting new friends. And that is just plain cool.

By the way please have a listen to the Knightcast, great quality and very impressive editing, he deserves a bigger audience and he is a top bloke.

So that’s about it for the web-page update, but as usual I can talk about anything for too long!

RSS Fixed: With No Help from LibSyn!

Well I got the best news today, the RSS feed for Global Geek Podcast is now fixed and I fixed it!

I went to the site today and saw that we had our first comment on the page, which was great so I clicked on the comment to see what was said. The sight I saw was awful, the side bar was all screwed up! Then Sebastian had the idea that it might be the template that was corrupted in my efforts at HTML (which I am crap at…). So I thought yeah distinct possibility, so we saved the HTML code and selected the same template to use without any additions from me and looked at it and fair enough the comments page was all screwy. Bingo! The template that we had chosen was a dud.

NvuSo after choosing another template I pasted in the HTML and found that the code was different because the style sheet was different! Back to square one. So tonight I have re-coded the page from scratch and I think it actually looks better. The other thing that I did was that I used a WYSIWYG editing program called Nvu; an open source HTML editor. Great stuff really helped. I spent ages by trial and error seeing what different headings and HTML coding worked with the style sheet, then I wrote all the settings down and put everything in that I wanted. So I was really pleased with what Nvu enabled me to do, so have a go of it and support the open source community.

I will say that in my opinion the template that we choose originally should be removed as an option on Libsyn’s site. It obviously has some major flaws and is problematic for new users. The other thing is that I sent an email regarding the RSS problem over five days ago and I am yet to hear a response, other then an auto responder. I know that it has been Easter and all but I thought I might have got a reply today at the latest! The other thing is that as soon as they hear RSS and look at the template they should know that it is a misbehaving template and give advice accordingly. My advice to users is that you need to get a little HTML savy and a try different things other than email first. This is one thing that I am hoping do with Podcast Periodical, give others this advice regarding issues that I have struggled with.

An admission from myself, the original RSS being invalid was due to the fact that I had omitted a full-stop from an email address, but the problem with the RSS not being detected in browsers was a direct result of the Template.

Regardless of how I got here, “here” is a happy place.