Viewing 13 replies - 16 through 28 (of 28 total)
  • Plugin Author Chip Bennett

    (@chipbennett)

    @virtualmotorpix thanks for confirming! I’ll push out a bugfix ASAP.

    Plugin Author Chip Bennett

    (@chipbennett)

    I’ve just pushed out Version 2.1, which fixes this bug.

    Note: I’ve also moved the Plugin settings from their own custom settings page to Dashboard -> Settings -> Reading. I think that is more intuitive, since that’s the same place where the default posts_per_page is set for the blog posts index/archives.

    Thanks again for using the Plugin, and let me know if you have any other issues!

    Hi Chip,

    Don’t know why but when I replace the old plugin with the new one (update of today), my whole website turns blank..

    Plugin Author Chip Bennett

    (@chipbennett)

    Don’t know why but when I replace the old plugin with the new one (update of today), my whole website turns blank..

    I can’t recreate this on my end.

    Can you enable debug (i.e. set define( 'WP_DEBUG', true ); in wp-config.php, and report back any fatal error messages you have?

    The problem is that I cannot activate it anymore cause it’s a live site with 10k+ visitors a day.

    I’ll try during the night.

    Plugin Author Chip Bennett

    (@chipbennett)

    No problem. Let me know when you get the chance; just post any error messages here.

    Not that it would affect you, as you’re running WordPress 3.4.2, but the Plugin now requires at least WordPress 3.3, due to use of the is_main_query() function. But, if you were running an older version of WordPress, that change would result in an undefined function fatal error.

    Well, I tried anyway..

    Didn’t get any fatal error messages and no warnings related to your plugin. Just white pages.

    Plugin Author Chip Bennett

    (@chipbennett)

    Didn’t get any fatal error messages and no warnings related to your plugin. Just white pages.

    No fatal error messages on either the front end or back end? A WSOD generally means a fatal error somewhere. Do you have WP_DEBUG enabled?

    Also: do you have any other Plugins (or Theme) that interacts with loop queries?

    No, also not in the back-end.
    Yes, I had WP-DEBUG enabled.

    About the plugins; I really don’t know for sure, but probably yes since we use about 20 plugins.

    In the back-end there was no white screen by the way. Only the front-end.

    Plugin Author Chip Bennett

    (@chipbennett)

    About the plugins; I really don’t know for sure, but probably yes since we use about 20 plugins.

    If you’re willing, can you post a list of active Plugins (and let me know what Theme you’re using)?

    In the back-end there was no white screen by the way. Only the front-end.

    That makes me even more strongly believe that the issue is your Theme, or another Plugin. Something somewhere is probably doing something with query_posts() or something similarly _doing_it_wrong(), but, it could be just an honest incompatibility. I’ll be happy to investigate.

    Sure, thanks!

    Akismet
    Blubrry PowerPress
    cbnet Different Posts Per Page
    Cookie Law Info
    Query Collapse-O-Matic
    Link Cloaking Plugin
    Posts By Tag
    Redirection
    SEO Friendly Images
    Shortcode Manager
    SocialBox
    Subscribe to Comments Reloaded
    UberMenu 2
    Widget Context
    WordPress Post Tabs
    WordPress SEO
    WordPress SEO News
    WP-Table Reloaded
    WP Minify
    WP Super Cache

    Theme: Techblog (newest version, Themeforest)

    if you want to take a look at the website, let me know where to send an e-mail.

    Plugin Author Chip Bennett

    (@chipbennett)

    Theme: Techblog (newest version, Themeforest)

    As it is a commercial Theme, I can’t provide specific support, but please check to see if your Theme uses query_posts(). If so, that is almost definitely the problem.

    (To verify that the problem is Theme-related, switch to Twenty Eleven, and see if you still get the WSOD.)

    If that’s the case, you might let the Theme developer know. Using query_posts() is always _doing_it_wrong(), and causes just this sort of problem.

    To modify the main loop query, filter pre_get_posts.

    To create secondary, custom loops, use WP_Query().

Viewing 13 replies - 16 through 28 (of 28 total)
  • The topic ‘Activated, so where is it?’ is closed to new replies.