Posted on

WordPress plug-in hacks

I’ve been meaning to post this ever since I transitioned to the new blog.

I’ve already explained in another post the frustrations I have with regards to the approach of WordPress plugins 1 How “snobbishly self-contained they tend to perform, etc.

This post however is to assert that despite all these “limitations” there is one developer that seems to have found an awesome workaround – and if people just get on board with his plugin architecture, most of the “silly issues” plaguing WP plugins could be solved.

So yeah, I guess this post is more of an evangelical one to [hopefully] give more exposure to Mr. Rob Marsh SJ and his extremely versatile Post-Plugin Library. Read More

Notes

Notes
⇡1 How “snobbishly self-contained they tend to perform, etc.
Posted on

Why didn’t I think of this sooner!?

So I was giving myself a hard time by manually adding .htaccess match conditions whenever there was a 404 (file not found) error reported 1 which was related to the old permalink formats I used in my MovableType days.

I realized just how much of an idiot I was when I could’ve used regular expressions. As such, I was able to replace all of them with just these five lines of code:

RedirectMatch permanent ^/blog/archives/(.*)/([0-9]{4})_([0-9]{2})_([0-9]{2})(.*)\.php$ http://nargalzius.com/blog/archives/$2/$3/$4
RedirectMatch permanent ^/blog/archives/(.*)/index_([0-9]{4})\.php$ http://nargalzius.com/blog/archives/$2
RedirectMatch permanent ^/blog/archives/(.*)/index_([0-9]{4})_([0-9]{2})\.php$ http://nargalzius.com/blog/archives/$2/$3
RedirectMatch permanent ^/blog/archives/(.*)/index_([0-9]{4})_([0-9]{2})_([0-9]{2})\.php$ http://nargalzius.com/blog/archives/$2/$3/$4
RedirectMatch permanent ^/blog/archives/([a-z]{1,})($|/$) http://nargalzius.com/blog/archives/category/$1

Let’s break them down shall we? Read More

Notes

Notes
⇡1 which was related to the old permalink formats I used in my MovableType days.
Posted on

Now powered by WordPress

Recently, during my downtime, I’ve been slowly migrating the blog to a new system 1 doesn’t take a rocket scientist to figure out what that system is 😉

The “move” wasn’t really prompted by one being superior over the other (i.e. MT vs WP). Truth be told, while migrating it became very clear to me that MovableType was by far the more superior system simply by the way it tackles data-flow processes. The best analogy I could give now is similar to why I still use Windows for my audio recording when I use OS X for everything else: because it’s more practical.

PC audio apps are cracked left and right whereas OS X audio apps aren’t as easy to find. Take out the whole piracy aspect out of it, and we have a similar situation: WordPress has more plugins being developed than MovableType 2 or at least the plugins I use. I initially wanted to upgrade to MT 4.x, but when I looked for the plugins I considered to be indispensable, I found that WordPress was the better choice.

I’ll do another post for my opinion regarding the switch; for now, let me just welcome you to the new system by pointing out the changes. Read More

Notes

Notes
⇡1 doesn’t take a rocket scientist to figure out what that system is 😉
⇡2 or at least the plugins I use
Posted on

Don’t mind this post (CSS Test)

I just posted so I can put all the “features” of Markdown, Smartypants, and Bo in one entry on the front page so I can style the site properly without having to change the archive pages just yet. You may disregard this post…

However, you may also check out the entry just to see the different element stylings. (e.g. quotes, code, footnotes, etc. etc.)

Let me just warn you though, since I’m doing this on the fly; I’m pretty sure this will keep on changing just in case you catch me editing the CSS (or if it breaks the page now and then). Read More