I’ve seen a couple of different reports here that the contact form isn’t working properly. That said, the form seems to work for me in the latest versions of Firefox, Chrome, and IE. If you have tried to contact me via the form and gotten an error, please leave a comment with this post. I’d love to know what browser you see the issue in, and what the error is. Thanks.
This website now enforces the use of https, thanks to the Let’s Encrypt initiative and the good folks at DreamHost. I initially had a number of problems in getting WordPress to behave, but I found this helpful article that pointed me in the right direction. I believe the bit of magic that helped me was running the wp CLI tool:
wp search-replace http://www.borngeek.com https://www.borngeek.com --precise --recurse-objects
Things now seem to be working, though if you spot a problem anywhere, let me know.
The commenting system on this site was throwing some nasty errors, as I found out this morning. They were due to an outdated comment spam plugin I was using. I have removed the offending plugin, replacing it with another, so commenting should work once again.
Well, that was fast! I’ve found the problem with the contact form and corrected it, so emails should now actually make it to my inbox. Apologies for the problem!
I discovered this morning that my site contact form is not working properly. I will investigate why and hope to have a fix in place soon. Until then, if you’ve sent me an email recently, I likely didn’t get it. Feel free to leave a comment here or email support at borngeek dot com. It’s been fixed!
After sitting on an XHTML Strict template for years and years, I’ve finally migrated this site’s theme to HTML 5. A number of new elements have been put to use, styles have been trimmed a little, and I’m using one less web-font. Hopefully I haven’t broken too much; if you spot something, let me know in the comments below. As always, expect sporadic updates as I add polish.
I recently made a change to this site to remove the ‘www’ from the front of the URL. Well, it turns out this caused a large number of headaches with WordPress (though I think the actual root cause of the problem lies in a custom .htaccess rule set that I wrote). Anyways, I’m going back to the old-school ‘www’ style URL until I have more time to fix it. If you see problems with the site, please let me know.
I have just pushed out the responsive version of this site’s theme, so you should see it immediately. Though the various tweaks may not be immediately apparent, the experience of this site on a mobile device or tablet (or a smaller screen in general) should be much better than before. Resize your browser window in the horizontal direction to see the style changes in real time!
There are still a few pain points to work through:
- I’m still a little unsure how to handle the syntax-highlighted code snippets in the various posts around the site. Snippets that don’t use syntax highlighting will word-wrap, but the syntax-highlighted blocks currently just offer a horizontal scroll bar.
- Various images in older posts need to have their hard-coded sizes removed from the
imgtags, so that they’ll scale appropriately. This is just a matter of going through and making those changes.
There could be other issues that I have yet to stumble across. From my limited testing, the site looks alright in Firefox, Chrome, and IE-9. I’m sure I’ll be tweaking stuff here and there over the next few days. If you spot problems, please let me know by leaving a comment.
I have decided to start using the SyntaxHighlighter package here at this website, to make various code snippets a little easier to read. This package really appeals to me since it supports a number of languages, has a graceful fallback mechanism, and looks nice. Rolling out these changes will be slow, however, since I have to go through and apply some styling to all the appropriate code blocks. As always, let me know if you spot a problem with this new feature.
I just realized that a number of posts that were imported to this site from my old blog are missing backslash characters. After doing some investigation, I found out that there’s an associated WordPress bug (Ticket #21007) against the importer utility. Apparently, backslashes aren’t preserved as they should be.
I’m working to fix all of the relevant posts and comments. When I’ve completed this task, I’ll update this post.
I believe I have fixed all of the relevant posts. If you spot a problem somewhere, let me know!