(Site News)
As you have noticed (unless you’re reading the feed), the site has undergone a pretty hefty redesign. It’s been two years since the last new look, and as with people, sites start to look old.
↓↓(show more)↓↓
I had to update the Read More Right Here plugin for the recent 2.8.1 Wordpress release (details below). The most important item to note is that now the minimum required version of WP is 2.8.
(It’s fixed….see second update below)
I just updated this site to use the latest WP (2.8) and now my “Read More Right Here” plugin doesn’t work quite right. When you click the “Read More” text, the rest of the post successfully downloads and is displayed. However, the next “click” takes you to the post’s single page display instead of just collapsing the new content.
I will hopefully get this sorted out soon. Whenever I do, I’ll update here.
UPDATE:
Unfortunately I haven’t been able to fix this. The problem is caused by the latest version of jQuery (1.3.2), to which WP apparently updated. Actually, it was caused somehow in the changes made in between 1.2.6 and 1.3.
Specifically, the function curCSS is throwing exceptions during the animation of the new content “away” (i.e. hiding).
800 | var computedStyle = defaultView.getComputedStyle( elem, null ); |
The elem parameter being passed to getComputedStyle that causes the exception is a “\n“. With jQuery 1.2.6, I don’t see that element being passed to that function.
I tried some of the other animation techniques, but they I guess they all hit curCSS at some point or another. Even plain old hide causes problems.
So…..sorry. As of right now, the RMRH plugin does not work with WP 2.8. The only solution I can see at the moment is to include the older version of jQuery with the plugin. But I’m not sure yet how that will work out.
UPDATE 2: FIXED
↓↓(show more)↓↓
Over on the post announcing my “Read More Right Here” wordpress plugin, an interesting few comments popped up by Thijs (I love these drawings). He found that the plugin breaks when a domain lets wordpress run its root, but the actual Wordpress files are stored in a subdirectory (see this codex article for the how to).
And awesomely enough, he found the cause of the problem!
↓↓(show more)↓↓
I’m releasing the first of what I hope are many plugins for Wordpress. All of the details are at the new “WP Plugins” page here at wooliet.
If you’re reading this on the wooliet main page (with multiple posts listed), you can see it in action by clicking the link below. If the is the “single post page” display then..well….there’s nothing to see! Just go to Wooliet and find an entry with a link to more content.
(Updated with official WP plugin link)
I added an archive page to the site. Unfortunately, I’m out of time and energy and so will have to put off actually linking to it as part of….how do you say….site navigation.
Until then, here’s one way to get there from here: LINK.
I finally reached a point in developing my own theme where I felt I could go ahead and put it to use. There’s still bunches of work that needs to be done. The most glaring is the lack of any sort of navigation or menu. I don’t, however, think it’s an absolute necessity at the moment. Ultimately I’d like it to be along the bottom of the header, and contain dropdown menus for browsing old posts by date and by “category”. Sooner or later it’ll happen. Along with everything else that needs to be done. But hey, you can read this can’t you?! Shouldn’t that be enough?!
Despite the quality (or lack thereof), it is a much better feeling knowing that it’s all mine, and not some twiddled version of somebody else’s work. There is the sense of accomplishment and satisfaction at having created something of your own that you just can’t get by dropping in a theme yanked from the internets.
So look for revisions and updates and new items to the right from time to time. Before you know it, we’ll be at version 1.0!
I spent too much time trying to tinker with the theme to make this space feel more like…mine. At some point you’ve got to start doing instead of preparing. I expect that the content will be fairly varied. I like the quick hits with brief comments (e.g. Waxy) and the slightly longer “links with thoughts” (e.g. Kottke). Beyond sharing links, I hope to also make the occasionally helpful post (you know…actual original content). When I’ve struggled with something and then found the solution, I plan to share it. Adding solutions for the great google spider to eat seems like a pretty nice thing to do.
So, on we go.
