Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter SubLo

    (@sublo)

    OK. After a ton of hairpulling, I think I figured it out. I went through each and every plugin, deactivated, and tested the feed. When deactivating “Advanced Permalinks,” the feed came back to life.

    Now my question is, I migrated from plain URLs to fancy permalinks over a year ago. I had used this plugin to assist in 301 redirection without losing the previous indexing.

    Do you think I still need this plugin at this point?

    Thread Starter SubLo

    (@sublo)

    I had some problems with w3 total cache right after the upgrade. It took down my entire site and Dashboard. I had to SSH in and manually deactivate it to bring the site back up, which – obviously – fixed that specific issue.

    I have two dozen or so plugins. You’re saying try deactivating them one by one?

    Thread Starter SubLo

    (@sublo)

    So here’s another thing. For the last 24 hours, I haven’t slept because I could not accept the fact that WordPress Permalinks was requiring an /index.php in front of my custom permalink to avoid redirects to the home page. It was really irking me that my urls all began with domain name/index.php/slug. Ugly!

    What WordPress doesn’t tell you, or what fixe the issue in my case, was not only enabling mod_rewrite in Apache, but putting this line below specifically in my virtual server’s respective area in httpd.conf.

    AllowOverride All

    Geez.

    SubLo

    (@sublo)

    Oh boy. Are you hosted on a Windows box or Linux? Sounds like Windows/IIS based on your response. If you’re Administering the operating system and Web Server yourself, and don’t know what these terms mean, or how to “tune” whatever Web server you may be running, you may need to enlist the help of someone who does – at least initially.

    SubLo

    (@sublo)

    Well, I’m going to assume it’s some flavor of *NIX and Apache/HTTPD you’re running. I struggled with the same problem for the first few months. I don’t know you’re exact setup, but I used an inexpensive Rackspace virtual/cloud server with only 512MB RAM. Now, it’s been fine for a long time using Apache Virtual Server on one IP with numerous fast loading Web sites – that is until I threw a WordPress site on it.

    The other sites were fast as hell but my WordPress blog would take a horrifically long 10 – 20 seconds to load each page. Did endless searching. I ruled out the server and MySQL as culprits. I finally came across a post that went over tuning the entire LAMP stack. What did the trick finally for me was to tune my httpd.conf for WordPress – again, although the 6 other sites on the same instance were all super speedy. Here’s what I changed in my httpd.conf:

    <IfModule prefork.c>
    StartServers       5
    MinSpareServers    5
    MaxSpareServers   10
    ServerLimit       50
    MaxClients        50
    MaxRequestsPerChild  4000
    </IfModule>
    <IfModule worker.c>
    StartServers         5
    MaxClients         300
    MinSpareThreads     25
    MaxSpareThreads     75
    ThreadsPerChild     25
    MaxRequestsPerChild  2000
    </IfModule>
    KeepAlive Off

    Every situation/server will be slightly different, but this worked for me and completely resolved my slow WordPress issues (after restarting Apache). I also signed up for CloudFare Content Delivery Network (CDN). That seems to have contributed to a slight speed increase as well.

    Good luck.

    Thread Starter SubLo

    (@sublo)

    Jesus Christmas! I FIXED IT finally!!!!!!!!! w00t!

    It’s all thanks to this post: http://strangelyperfect.tv/11622/wordpress-permalinks-generated-but-not-redirected/

    After many attempts, it wasn’t my Apache, htaccess, plugins or anything else. All I did was insert “index.php” in front of the Custom URL Structure and voila!

    All is working! I don’t understand why, but whatever.

    SubLo

    (@sublo)

    Are you self hosted? Your own server?

    Thread Starter SubLo

    (@sublo)

    Thanks for the prompt reply. Yeah. I tried that. The problem still exists unfortunately.

Viewing 8 replies - 1 through 8 (of 8 total)