WordPress admin redirecting on Nginx

I had an odd problem this morning.  I moved my blog over to a new VPS last week, switching from Apache to Nginx w/ PHP-FPM 7.  But when I tried to log in this morning to do a quick blog post on starting Solr on CentOS 7 (which I eventually did not do) but I found that I was getting infinite redirects on my login page.  Turns out that my Nginx configuration was wrong.  Following is the Nginx configuration I had server { listen 80; server_name eschrade.com www.eschrade.com; root <root>; index

Integrating Zend_View with WordPress

I just read a blog post about integrating Zend Framework and WordPress and figured I’d add some commentary of my own, since I’ve done something similar.  In my ESchrade plugin I use Zend_View to render some of my admin pages, though there is no reason why you couldn’t use it elsewhere, as long as the plugin has already been loaded. Getting Zend Framework set up with WordPress is super simple.  Assuming you have Zend Framework already in your include path all you need to do is put the autoloader in

Added (PHP 5.3) job queuing to my WordPress instance

One of the things I liked on my old blog was the ability to have a Popular Posts section that was based off of Google Analytics. I had also like that I was using pre-caching, i.e., a cache that does not expire but is, rather, overwritten.  There are two benefits to this.  1) There is no lag time when the cache expires and I need to contact Google to get new data. 2) If my connection goes down for whatever reason (bad data, time expired, modified password), the data stays

Migrated the blog… to WordPress

… to WordPress? Yep.  I had written my blog from scratch, partially because I wanted to use it as a testing ground for various ideas and such.  However, part of the problem of maintaining your own blog software is maintaining your own blog software.  I think that I’ve pretty much milked the code for all it’s worth.  So now I’ll stop maintaining my own code and start using someone else’s. But… WordPress? Yep.  Let’s face it; the code base is a horrible stinking mess.  The API is not intuitive in