Forum Replies Created

Viewing 12 replies - 61 through 72 (of 72 total)
  • Handy: for what it’s worth, I installed a fresh copy of WP 2.0.6 into a clean database, and added the Search Static plugin as well as two static pages. Search results still return zero results. The plugin simply looks for status=static which is a very basic query. However, it is not returning any results — neither on my production blogs, development site, or the new one I tried today.

    I’m hoping the author, or someone here can look at the 5 or 6 lines of code in the Search Static plugin and offer a fix for me.

    I have a feeling it may be due to the new query filter. However, not being a programmer, I cannot be certain.

    For reference, here’s the entire plugin code… it’s not much, but it worked extremely well under 2.0.5


    <?php
    # version constant
    define('k_SEARCH_STATIC_VER', '0.1');
    function search_static($where) {
    if (is_search())
    $where = preg_replace("'(post_status = "publish".*'", "(post_status = 'static' OR post_status = 'publish')", $where);
    return $where;
    }
    add_filter('posts_where_paged', 'search_static');
    ?>

    Still waiting for a reply from the plugin author himself. But as of yet, no reply.

    I’ve also lost the Search Static plugin functionality since upgrading to 2.0.6, which is absolutely critical to the site I am developing — I need the ability to search both pages and posts. This is a vital aspect to a site being built for a client.

    I’m interested in hearing of any solution as well. I’ve written the author of the Search Static plugin, to see if he could offer a solution. But as of yet, no reply.

    Rongo

    (@rongo)

    Try deleting the log file that Google Sitemaps creator plugin creates. Deleting that log file (which was huge) resolved all of my issues. I would love to see an option to turn off the log file altogether from this plugin.

    Rongo

    (@rongo)

    Just an update on this… my problem is resolved.

    It was the log file created by the plugin, Google Sitemap Generator for WordPress 3.0b3 — note, I am using the BETA version of the plugin. Once I cleared that log (which was very, very long), everything is working perfectly again.

    As it turns out, it was not a problem with WordPress itself, for me anyway. I was mistaken.

    Rongo

    (@rongo)

    Has anyone from the WP team been able to duplicate this error, or have any further suggestions?

    It’s been a couple of weeks since upgrading to 2.0.5 from what *was* a perfectly working 2.0.4. No matter what I have tried, there is a problem in the post.php refreshing after *any* use. (Save and Continue, Save, and Publish).

    Is the *only* suggestion left to simply wipe out the entire site and start over?

    Rongo

    (@rongo)

    HandySolo: one of the things I tried (see my earlier post with bulleted entries), was to try removing all the update services. I think I have tried just about everything.

    It never helped any, but honestly, I never expected it to since the problem for me is that it is “hanging” even when using the “Save and Continue Editing” feature. Everything is saved, but the problem is that the page never refreshes. it stalls between the pushing of the button and the refreshing of the page.

    Thanks though for the suggestion(s). Much appreciated.

    Thread Starter Rongo

    (@rongo)

    Short of a built-in option, does anyone know of a plugin to make the above happen?

    Rongo

    (@rongo)

    HandySolo: Thanks. While I cannot speak for anyone else in this thread, I have tried that plugin a few days ago. It unfortunately did not correct the issue for me.

    I’m unsure what else to do. It’s not a widespread issue, obviously, as only a handful of people are reporting the problem. But it is indeed frustrating nonetheless trying to resolve the issue.

    Rongo

    (@rongo)

    Danfef: Thanks for the tip. But honestly, I am hoping for a more practical solution/fix from the WP team. Starting from scratch is, for me, a very last resort and one I am very reluctant to do.

    At the very least, the fact that more than one person is experiencing this after upgrading to 2.0.5 is an indication to me that an oversight or incompatibility exists in the upgrade process from 2.0.4 to 2.0.5.

    Rongo

    (@rongo)

    David, I’ve continued to search for a resolution to this issue, but still none found.

    Short of downgrading to 2.0.4 (where everything worked flawlessly), I’m not sure what else to suggest. Downgrading is not a reasonable option either, however, since it contained security flaws that have been patched in 2.0.5.

    I don’t see many other people posting publicly about this, so it’s likely not a widespread issue that you and I are experiencing. Thus, unless many more people start experiencing the same thing, or until the WP crew can find time to duplicate this same issue, my guess is we’re SOL.

    Rongo

    (@rongo)

    I am having a similar problem, except for me it is 100% of the time since upgrading to 2.0.5. and it is happening for me in FF2, IE6, and Opera 9. In my case, clicking Publish, Save and Continue Editing, or just Save will cause the “post.php” to appear as if it has stalled. Then the page goes blank. If I log back in, however, what i posted has been saved and/or published. As such, it seems to me the problem is in the refreshing the existing page. But I cannot figure out why and cannot find a solution anywhere for it so far.

    So far, I have tried:

    1. disabling plugins
    2. re-uploading the wp-admin/post.php file (figuring it might be corrupted)
    3. increased my server’s PHP RAM from 12mb to 16mb
    4. deleted cookies and javascript from my browser’s cache
    5. re-uploaded all of 2.0.05 to see if that would help
    6. removed all links to pingomatic and other update services
    7. Installing the “WP-Tuneup” Plugin to see if that would help. It didn’t.

    So far, nothing has corrected this for me.

    The server is a dedicated dual xeon with 2 GB of RAM, and the only sites on it are my own which are low traffic.

    I’m stumped, that’s for certain. I too would be interested in anything else I could try to resolve this issue.

    Thread Starter Rongo

    (@rongo)

    Wow, I never expected a reply so quickly, let alone a modification to an already great plugin.

    Thanks so much, it is greatly appreciated. I’m off to play with it ??

Viewing 12 replies - 61 through 72 (of 72 total)