Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • I guess when upgrading, the ‘enable’ setting got turned off.
    The Comments > Disqus > Settings tab, it said ‘Disqus comments are currently disabled’.
    Issue fixed when I clicked ‘enable’.

    The same thing happened to our client’s site.
    When we updated to 2.7.7 on our staging site, we did not get the button to ‘Upgrade’ database. On production, we did.

    We are getting the same in our error logs.

    Our client reports the following:
    “I’m having trouble again after editing regular pages and it seems to be breaking the website, though it only breaks it for about 5-10 minutes. I edited the same page again and it seemed to work fine. However, after going to view the post, I clicked the edit button from within the page, and just get a white screen with ‘error’

    After the first test, I could get both the Home page and some interior pages to load, but I couldn’t get the blog page to load, the admin area, or the other main pages along the main navigation. Hector, Steve, and I tried Chrome, Firefox and Explorer, and I cleared cache in all of them. Firefox and Chrome gave us just the “error” message. IE says its HTTP 403 Forbidden. After about 5 minutes, all the pages loaded again.

    For the second test, I was able to break the site at 10:23 am and this time I couldn’t load anything (white page with ‘error’). Refreshing the site at 10:38 loaded everything again.”

    Thread Starter strottrot

    (@strottrot)

    @MindBlender3D
    Thank you for the suggestions–I’ll give the second one a try.
    And thanks for saying something about bumping the thread–I didn’t realize, but it makes sense.
    -Julie

    Thread Starter strottrot

    (@strottrot)

    Hi again,
    Just another request for some help on this…
    Thanks.

    I, too, am trying to order posts on a category page based on a custom field.
    What I would like is:
    Get all posts for the category. If the custom field with a key of phs-post-order is assigned, order first by that key’s value, then by date.
    (The only custom field I have is ‘phs-post-order’)

    However, when I remove the where statement restricting the query to only posts with
    AND $wpdb->postmeta.meta_key = ‘phs-post-order’
    then I get redundant listings of posts in the page.

    I’d appreciate any help on the SQL.
    This is what I’m using:

    $querystr = “
    SELECT * FROM $wpdb->posts
    LEFT JOIN $wpdb->postmeta ON($wpdb->posts.ID = $wpdb->postmeta.post_id)
    LEFT JOIN $wpdb->term_relationships ON($wpdb->posts.ID = $wpdb->term_relationships.object_id)
    LEFT JOIN $wpdb->term_taxonomy ON($wpdb->term_relationships.term_taxonomy_id = $wpdb->term_taxonomy.term_taxonomy_id)
    WHERE $wpdb->term_taxonomy.term_id = 8
    AND $wpdb->term_taxonomy.taxonomy = ‘category’
    AND $wpdb->posts.post_status = ‘publish’
    AND $wpdb->postmeta.meta_key = ‘phs-post-order’
    ORDER BY ABS(0 + $wpdb->postmeta.meta_value) ASC
    “;

    Thanks!

    Thread Starter strottrot

    (@strottrot)

    Thanks, Alex.
    I tried disabling Akismet (the only other plugin I had goign at the time–no dice.) I reinstalled and that worked. (Little silly I didn’t try that b4 posting!)

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