Archive for blog

My theme - it’s got form!

And it has nice pastel colors, heh. ;)

Actually, I did the pastels to tell where stuff was, I’ll work on final look and all that stuff later. Right now, it’s a basic shell of how the site will be, with the just the bare essentials in there at the moment.

The good news is that so far, I’ve only managed to completely break the site 3 times, but that was due to missing bits of code from the page that were kinda necessary (i.e. ?> at the end of a PHP statement).

Anyway, the moment you may have been waiting for (and I gotta say, it kinda came quickly considering that just a couple of hours ago, I was looking at one of the files from the default WP theme and going “Huh?” at some of the stuff in there; I’m still doing that, but not as much ;) ) - when I show off a first screenshot of the theme in action.

Theme as it is now

It will be a little while before I have anything releasable to y’all, but I just wanted to give you a look at what might be coming down the pike. :)

Tomorrow Later today: TW3, and/or shopping for a bank. ;)

Comments (4)

Making a Theme - Step 1.

I’ve taken the first step in getting a theme out there for y’all to view - and I’m still quite a long way from having anything concrete. Why? That’s because I am taking the time to read the documentation on how to go about making a theme. I started this afternoon by printing a couple of articles out from the Codex - Theme Development and Designing Themes for Public Release.

As I was reading through the first article as I was working, I started getting bombarded by terms that made no sense. For example, the WordPress Loop (which is explained in another article or two) and the word concomitant (which, incidentally, is a correctly-spelt word in Windows Live Writer, while swear words aren’t - makes no sense to me!). I’m all for expanding language, but when using the word concurrent would suffice, why not use that one?

Anyway, I then read the article about designing themes, and one of the most interesting bits of advice was couched in a long blockquote section (which was on the first printed page, as I had printed it in WLW - which turned out really stunning because of the font it’s printed in ;) ). The advice was something so simple, that if you think about it, this makes total sense, and even if you don’t think about it, you should see the sense.

That advice is - lay out your theme on paper first, and do it away from the computer. After getting that down solid, then you can start dealing with writing the code for it, and by solid, he means that you should have the layout decided on, along with the main colors of the site. Fortunately, I have a bit of an idea in my mind, but now I need to get those onto paper - and decide on some base colors to go with.

However, you know what? I know it’s going to be a quite challenging project to start with, but I’m looking forward to the challenge. :)

Comments (1)

This was the Week that Was, Vol. 40

This is a bit of a rain-shortened version of the weekly wrap up, but I have all the regular features in here, with a slightly different focus. ;)

Posts I liked

  • First up, some sad news in the blogging world - Radioactive Jam is calling it quits. At least for today. ;)
  • Also, if you’re in the UK, you can check out BBC’s iPlayer for video of penguins flying; or just view the spot that aired showing off this rare species of the bird. :)

New Blogs in the US Blogs Community on Bumpzee

None this week

The US Blogs community is open to bloggers in the US that are a part of the Bumpzee community. If you’re interested in more about the community, you can view the main page of it. :)

Keywords

  • scroogle blog - They don’t have one as far as I know. However, I can do nothing other than wholeheartedly recommend using their search instead of google - it’s the same, just without the tracking. ;)
  • offline blog writer - I’ve talked about w.bloggar, however I think that there’s a new winner in my book - look for the details soon. ;)
  • home security - This came in via Google Blog Search; why are you searching blogs for that? If you’re concerned, try regular google or the yellow pages…
  • blogger paid move to new domain and host - If you’re looking to move your blogger blog to a new domain, then that’s as easy as setting it up. If you want a paid service, then you might want to consider going with WordPress 2.3
  • wordpress 2.5 why do dashboards look different on different blogs - Well, that’s likely because some blogs upgraded to the new version and others didn’t. Apparently user input was sought for the 2.5 dashboard - I’m still not buying it…

Around the blog

This week, I talked about my misadventure when it came to my first go at releasing a theme. I’m glad that I’ve learnt a lesson from that, and now I just need to get cracking on reading the information in the Codex about themes.

Another adventure I had was the one in getting the ingredients for an attempt at making risotto. It came out fantastic, and the leftovers tasted really good, especially when I added a bit more cheese to it. ;)

Also, with the release of WordPress 2.5, came my trying it out. First, I wasn’t excited, and now I know it’s going to be given a wide berth when it comes to being placed on my main site now.

Coming up in this shortened week, I’ve got a bit of a complaint about gasoline - yes, the price is high, but everyone is pointing fingers everywhere but where they deserve to go.

‘Til next week y’all! ;)

Comments (1)

WordPress 2.5 - Not coming here soon

Just a note - if you’re looking for the week in walks, they’ll be up tomorrow, pictures and all. However, WordPress 2.5’s release is more recent news, and an issue that I believe is worth pushing my normal schedule back a day for. :)

I bit the bullet and installed WordPress 2.5 on my testing blog, and I’ve been playing with it for a few hours now, and my impression is that the number of things I don’t like far outweigh the number of things I do like. Before I get to my critique, however, I have a couple of important questions.

First, why was this released on a Saturday? Every other major release of software - free or not - has happened on a weekday. To have something as seemingly major as WordPress 2.5 released on Saturday suggests to me that the folks at Automattic almost wanted this release to be as low-key as possible, as most of the “major” web writers usually go at a more relaxed pace on the weekend.

The next question I have is pointed at everyone who is raving over the new interface - what specifically about it makes this particular version superior to the old interface? All I’ve seen are generalities. Something tells me that a lot of this is related to a disease known as “fanboyism” (which I know doesn’t exist, but is noted by the almost-fanatical praise heaped by certain people whenever something comes from one place, no matter how poor it is), and that is never a good thing as it allows hype to take over real substance.

The last question I have, and this is something that I’ll keep coming back to throughout my discussion of dislikes, is about this supposed research that they did. Who exactly did they ask for input? It seems like they’ve asked some quite inept people to get their suggestions when it comes to getting an opinion on the current dashboard’s so-called downfalls.

I’ll be reasonable, however, and let you in on the couple of things that I do like -

Things I like

First, is that in the Theme editor (under Presentation Design -> Theme Editor), they’ve split up the template and style files into their own groups. Actually, I’m surprised they didn’t try to prettify that and manage to totally screw it up in the process. Sure that’s a dumbed-down option that they did, but it’s quite useful when you consider that currently, all the files are listed in one big list.

Another thing that I like is the addition of a link to edit a newly-published post. Also, the fact that they did make the size of the fonts smaller wasn’t a bad idea either.

And that’s about where this ends.

Things I don’t like

Where do I start with this? There are a lot more things that I don’t like about the new admin panel, but let’s start with the most obvious one -

New-look menus

Instead of sticking with the normal set of menus, they decided to split the main toolbar into two parts - with the connections between them being loose at the best. Thankfully, it’s easy to hack the admin-header.php file to get the Plugins, Options Settings, and Users down with the rest of the menu items, it’s something that shouldn’t have to have been done in the first place (not to mention that cForms and Polls are now to the left of these other sections). Also, the dashboard is an integral part of the WordPress admin panel - why is the link to that relegated to a teeny-weeny link in the upper left that almost blends into the background?

Widget redesign

Pardon my French, but what the fuck were they thinking when they thought this one up? Actually, what the fuck were they smoking and/or drinking at the time? I’d like to have a sample. ;)

Since I’ve been using WordPress, the Widget page has been a straight-forward drag-and-drop affair where you could take the available widgets (at the bottom of the page) and drag them up to either sidebar. You could also have multiple text widgets at your disposal, and if you wanted to take one away for a short while, all you had to do was drag it out of the sidebar and it’d be saved.

Now? Well, now you can only work on one sidebar at a time, and those saved text widgets you had off of the sidebar before you upgraded? Gone. Hope you saved the code to them.

Oh, by the way, if you remove a text widget from a sidebar - you can say goodbye to whatever text was in there before. It’s not saved. It was something important? Sorry, but it’s not OK to take text widgets away anymore; game over, you lose.

The other thing that is completely ass-backward is that they show you all available widgets, including those you already have activated. How useless is that?

Like whitespace?

If you’re a fan of completely wasted space on a webpage, then you’ll love a lot of the pages in WordPress 2.5! Why? Well, on most of them, there’s a maximum width of just less than 1000 pixels. It wouldn’t be so bad if it was centred on the page, but infinite wisdom was used to put it all aligned to the left. Fortunately, if you’re using Stylish, you can create a new style for your URL and put this in between the curly braces -

.wrap, .updated, .error {
max-width: 100% !important;
}
.narrow {
width: 100% !important;
}

That will fix one of the few things you can actually fix on your own.

Categories are dead. Long live tags.

Or that’s what they want you to believe when you look at the write screen. Instead of the current setup of having categories at the top of the right hand column, easily accessible, they put them at the bottom of the write screen (where you can’t move the elements anymore, like you used to), under tags. The message here is clear - categories are less important than tags.

Gaping security hole

One of the more ballyhooed new features in this new version is the ability to automatically upgrade plugins from your plugin page. On my site, I had tried out a different plugin that allowed me to do just that, but it didn’t work because of server permissions that there are.

However, WordPress have made a great decision to usurp any server’s security when it comes to running zip files by including its own unzipping program in the WordPress install - that’s got to be part of the reason why the zip file is 30% larger than it was previously. By doing this, anyone running a plugin has the potential of opening themselves up to a major problem with their server by upgrading to a new version of a plugin that has a malicious file in it.

The chances of this happening are slim, but it is not outside of the possible realm of things that can happen. Fortunately, there is a way to fix this and to break the plugin upgrade function - set the permissions of the wp-content/plugins folder to 555, thus making it read only, and forcing an error on the update page.

Lazy time

The last item I have on my list of dislikes is that they’ve changed the way you select your timezone - it used to be that you just typed in a number, say, -6 for Central Standard Time, like you would on a forum run by SMF. However, apparently in these supposed interviews, they discovered that people had a hard time typing in a simple combination of a plus or minus sign and a number between 0 and 14. It’s been replaced with a drop-down box with selections for timezones, with minor half-hour intervals.

Overall initial verdict

If I had to give a grade to their efforts in regards to what they did, I would give them a grade of about 60/100, or just barely a D-minus in school grading terms. The biggest thing that they lose points for is the rule of “don’t fix something that ain’t broke”. The Admin interface in previous iterations of WordPress worked perfectly, and were, after a bit of a learning curve, very intuitive.

However, doing patently stupid things like splitting the options panel into two distinct menus, making the dashboard into the least important thing in the dashboard (by the way, where can you see the stats for your blog? the stats sub-panel under the dashboard has gone missing.), and making everything fixed width only goes to hurt the cause further.

Unfortunately, it seems that the folks who are at the head of WordPress are only more concerned with glorifying their latest release, but don’t be surprised if there are urgent updates to 2.5 coming out as soon as a week from now, as it seems that they’ve gotten creative with the roadmap, making up nearly 30% of the overall progress in their planning within a week or two.

As far as my site is concerned, I’m going to stick with 2.3.x series WordPress releases for at least the near future. Maybe if someone comes out with an admin theme that looks like the old version, and maybe fix the widget issue (come on, they seriously fucked up there).

What do you all think about this release? More importantly, do you know anyone who was interviewed to help them out? I’m sure that there are a lot of people out there who would love to know how they came to the conclusion that this was “needed”.

Comments (11)

When Good Deeds go bad

I don’t know where it went wrong with what I did when I posted my first attempt at editing a theme, but what happened was something that, to this day, still confounds me quite a bit. Just to recap the story up to here, I had found a theme that I liked for my blog, but after finding some major flaws with it (i.e. “F–K THIS” written out in the header, the CSS file being lumped together in one big chunk), I changed themes to this one. However, I then wanted to revisit the theme and see if I could improve upon it. The final result wound up being my first foray into theme tweaking.

However, I made a critical error in that post - I took the initiative to find the actual site of the person who created the theme, and linked to his post that announced the original release of it. I made sure to give the credit where it was due, because a lot of the hard work was done already, and I thought that the original creator would not have issues with having a theme redone (with all original links left intact in the theme’s files - even though they go to sites which aren’t the same as when the theme was made originally).

Clearly, I was wrong.

I published the post at 11.44PM, and got a comment shortly afterward, but about 6 hours after publishing, I got this notification of a new comment -

comment1

That was followed, almost immediately after, by an email about a new contact form that I received, with a similar message -

contactform

Now, after receiving these messages, I dutifully did what I was asked by him to do - removed the download link. I would have thought that it was enough to just do that, but apparently he didn’t like my only doing that - he wanted the whole thing scrapped, so about 12 hours after the first comment was dropped, I received this comment -

comment2

The hilarious thing about all of this is that he claims to hold copyright over that particular theme, but a quick inspection of the theme’s files yields nothing in the way of a license, or even a copyright notice in the CSS file (which is the standard place for doing things like that). Even themes released with a license are released under the GPL license, which allows you to modify the work, so long as you keep record of the originator of the work, which I had done. After receiving the mails and contact forms, it was time to do a bit of a mea culpa, by sending an email with a profuse apology for any infringements:

myreply

Any even-handed person probably would have taken note of the fact that I hadn’t done this before, and been slightly lenient about it, even possibly allowing the download to be available again. Again, I was wrong. This was the reply that I received to my email:

herreply

It was at this point that I started to do some searching into his supposed claims over copyright and everything to do with him, and this brought up an interesting revelation. Let me share the line I used when I found this bit of information out -

[1/13/2008 8:13:51 PM] Sephy says: hmm…i was assuming that he had dangly bits, apparently i’m wrong…M1l0 IllVIl has the right to contact and demand Participant to remove any non-suitable display or use of her work at any time (without reasons or explanations necessary).

That line was culled from her page with all the disclaimers she holds, which also has this hilarious bit of text, which would mean anyone who has downloaded one of her themes and changed even one thing would be in violation of these disclaimers -

Participant also agrees not to alter, disassemble, decompile, reverse engineer, or otherwise modify the Downloaded Material.

By that same logic, anybody who uses one of themes at all without asking her permission would fall afoul of this line -

ANY USE OR PARTIAL USE OF THE IMAGES; ILLUSTRATIONS; SENTENCES OR LOGOS OF M1L0I11IVII WORKS WITHOUT PERMISSION IS STRICTLY PROHIBITED

After that, Snoskred said that I should go ahead and re-release the theme without any of the supposedly copyrighted things - images, sentences, etc. In other words, release the theme as my own original work. There were a few other revelations that were discovered in searching her site. I did a little bit of digging into her site and found a post about a forum that this person had created. Now, for someone who had such a fit over one person modifying one of her themes, I was shocked to find this tidbit in the post -

post your modified m1l0 themes with screenshots

That sounds like a completely different story to what she was complaining about to me. In fact, if you look at the thread in which the themes are posted, one person asked if he could post his themes for others to use. The most hilarious thing is that the reply from her to his post was saying that his way of showing off the edited themes was the way it was intended! Anyone smell the irony? ;)

Along with what I’d done already, I’d sought the input of someone who has done quite a bit of theme modification, and basically, they told me that if they were asked to take something down, they would. It was with that bit of information that I decided that maybe, the best way to handle this was to let her go on her way and let this go away as it was something that I didn’t need to deal with. That doesn’t mean that I had started to draft a reply back to her in response to her second email. This is what it looked like after I had stopped working on it -

draft

But, the story doesn’t end there.

A couple of days later, she sent me another email that was very different to the other emails, which made the whole situation even more strange, as this was a mail that was actually halfway polite. This is what she sent -

lastreply

For sure, it’s an interesting query; however, if you think about it taking and modifying a theme (with, as I noted in my reply to her, none of the acknowledgements changed), and try to correlate it to someone scraping your blog’s content, it doesn’t make any sense.

As it is, my plans for the near term when it comes to WordPress themes is that I’m going to take some time and read the information that is available on the WordPress codex in relation to writing your own themes. I have some ideas for my own. I might just start out with the sandbox theme to start with, just to get my bearings as to what is involved in a theme.

Comments (5)

« Previous entries · Next entries »