Forum Replies Created

Viewing 15 replies - 46 through 60 (of 386 total)
  • Hello Donncha, I’m facing exactly same problems as rfischmann right after moving to DreamHost VPS from shared hosting. And for the past one+ month my blog is just dead. And top of all, I’ve started receiving about 500 trackback/pingback spams every single mintue, draining all available resources.

    I’ve tried all possible HTACCESS rules to avoid spammers generating PHP load, but to no avail., I’m truly sure, I’ve done something wrong.

    To cut short, the only alternative is to move elesewhere, as suggested by DreamHost.

    I just cann’t go elsewhere (as suggested by some senior support members), because $70 advanced payment is quite big amount for me, and I cann’t affoard to loose it.

    Still awaiting their reply, meanwhile the site as usual remains dead as it takes 4+ minutes to each HTTP request and dies with 500, 404, error establishing database connection etc. errors.

    Thread Starter Rok

    (@rok)

    I’m currently using Akismet & WP-SpamFree, but they’re coontinously attacking and draining server resources causing 100% CPU/Memory load. Both these plugins are preventing spam reaching WordPress, but I want to block spaming via HTACCESS to reduce some server load, becasue I don’t have access to Apache.

    Please advice.

    Thanks

    Forum: Fixing WordPress
    In reply to: Super Cache
    Thread Starter Rok

    (@rok)

    Hi Donncha,

    Thanks for the reply, the blog is hosted on DreamHost.

    1. Seconds before, DreamHost moved my blog to VPS, I was running Super Cache plugin (since 1st day of its release), and it was working flawlessely.

    The blog was also running smoothly, except 1-2 hrs downtime (somtimes daily or on alternate basis).

    The problems started, only after VPS shift.

    What do you advice?

    Rok

    (@rok)

    Otto, following code generates 404 error, right after adding it to wp-config.php

    define('SAVEQUERIES', true);

    Rok

    (@rok)

    If you’re using WordPress 2.5, open the page and under the “Title” box, you’ll find “edit” page URL. Just add “.html” or “.php”, whatever you like your page to end with and click “save” next to the URL box. It should do the trick.

    If it doesn’t work, there’s a plugin that allows you to add “Dots” inplace of “Dashes”. Right now, I’m not able to locate the URI. You can try to Goolge or search on WordPress.

    Rok

    (@rok)

    You’re welcome. Also, make sure to optimize your indexes, if you’re on shared hosting. As, this plugin will raise DB queries, if you display “Top Posts /Pages” etc. function.

    Rok

    (@rok)

    You can post videos after the jump, then video will appear only on single page:

    <!--more-->

    Hi, would you add auto killing Trackback/pingback spams, as requested earlier in my review post of WP-SpamFree and in the comments on your blog.

    Permissions are correct & “Build the sitemap in a background process” is ticked. Eventhough, it doesn’t work in WordPress 2.5

    Earlier in WordPress 2.3.3, I was able to generate sitemap with just one click under 5-15 seconds. Now after upgrading, I only gets “last run didn’t finish” error.

    @rdkr

    Where you turned off and deleted sitemap files in “WordPress” or “Google Webmaster Tools”?

    WP-postviews from GamerZ.

    I’m also facing same problem, right after upgrading to WordPress 2.5. Sitemap generator is not working and ends with following error:

    “The last run didn’t finish! Maybe you can raise the memory or time limit for PHP scripts”

    Earlier on WordPress 2.3.3, I was able to generated sitemap with just one click and it used to take between 5-15 seconds.

    Can someone zip up the previous version

    It won’t make any affect. As I’m also experiencing the same problem, right after upgrading to WordPress 2.5. Earlier on WordPress 2.3.3, I was able to generate sitemap with just one click and withing 15-35 sec.

    All you’ve to do is insert following code in your desired template file to display “related posts”. Majority of bloggers display related posts at the post end. In this case, you’ll have to edit “signle.php” (if your theme uses it to display full post) or “index.php” and add the code ad the desired location.

    <?php wp_related_posts(); ?>

    @peter, Otto is 100% right, if you hard code or remove now, next when you upgrade, same things will apear again. And you’ll have to do the same excercise of finding & removing code.

    If you still want to do manual removal, you can read this post.

    This might help you.

Viewing 15 replies - 46 through 60 (of 386 total)