wading through technical difficulties…
It never rains but it pours! Last night and much of this evening I spent chasing down problems of various sorts. (To any rss feed readers, I do apologize; it seems that any changes made to the content of a post results in a few feed being prepared for that post; one of the items on my todo list is to figure out how to turn that off when I’m tinkering under the hood.)
Seems that I had/have a couple of problems. First of all I had a poor permalink customization that didn’t end with a / which caused several problems such as not being able to navigate to paginated posts (which feature I tried for the first time in “flickr slideshow”). At about the same time I noticed that I couldn’t get comments working, either. Then when I checked error logs, I found that the codesnippets and smileys plugins were generating fairly generic (ie impossible to figure out what’s going on) error messages.
Aiee.
So in the process of tracking down the problems, I nuked the plugins, nuked the theme modifications and finally went back down to the default kubric theme. Nothing solved the problem so I put in a support request to find out what’s going on.
Of course, I couldn’t stop just tinkering around and googling around to see if I could find any solutions. That’s when I discovered that Wordpress actually recommends that permalinks end in /. Oh. OH. Right, right, the rewrite rules.
OK, so I went in and fixed that and lo and behold, pagination and comments started to work! Yay!
But there’s still a few oddities, such as the error messages in the log file which do not go away. There are certain plugins that just Do Not Work. Finally I found a bit of news rummaging through DreamHost’s Wiki that allow.url.fopen is disabled over here. I’m wondering if that’s the problem showing up in the log files, but grepping thru the directories for instances of include or fopen didn’t get me any results. DreamHost recommends curl wrappers instead, which I’ll be happy to do if this is the problem and if I can locate which are the problematic calls. So that part’s on hold for now.
Of course I couldn’t quite leave well enough alone, and I decided to go ahead (since I’d been munging my permalink structure all day anyway) and reorganize the WordPress setup in my account to put everything tidily away in a subdirectory while leaving the blog as the “main” item regardless. To that end, I followed the instructions here quite faithfully — putting all but index.php into a subdirectory called wordpress. It actually went pretty smoothly for the most part, so after finishing I went back and reloaded the blog. Oooh, pretty! Except my title gif is missing. So I went back and hunted thru and changed the bloginfo call from url to a more appropriate template_directory.
Only now none of the links on the page work: the about page, the pagination pages, the permalink, nothing. So it’s clearly some sort of rewrite rule and something with generating the permalinks. All of the bad links have an extra index.php in the middle of them. I went through a half dozen google articles moderately relevant to the issue, but didn’t really find anything. Then on a hunch I went back to the article and decided that step 4 seemed wrong, given everything I’d done. So I changed the blog address to just digitalramble.com instead of digitalramble.com/index.php as it says & redid the permalinks. *cough* As I was saying about buggy documentation the other day *cough*…
Voila. Everything looks like it works, aside from the error.log generation messages, and at this point I think I have to wait for DreamHost support to get back to me. Unless I can google up more info for allow_url_fopen and find anything else that it might be tripping that’s present in the affected plugins…


