Viewing 15 replies - 1 through 15 (of 22 total)
  • Plugin Author Mike Walsh

    (@mpwalsh8)

    Can you try temporarily switching to one of the default WordPress themes (TwentyTen, TwentyEleven, or TwentyTwelve) and let me know if the problem persists?

    Is there anything unusual about your server environment? Do you know what version of PHP you are running?

    I need some additional information in order help you out.

    Thread Starter majo_wordpress

    (@majo_wordpress)

    I switch to Twenty Eleven theme, problem persists. I have PHP Version 5.2.17.

    Plugin Author Mike Walsh

    (@mpwalsh8)

    I am also running PHP 5.2.17 on my web site. A 500 Error means the web server has failed which usually means some sort of internal PHP error. Do you know what platform your site is running on? I am running under Linux with Apache with MySQL 5.0 and PHP 5.2.17.

    If you want me give me access to your Dashboard I would be happy to take a look. I am not sure what else to suggest at this point. There isn’t any unusual PHP in the plugin that I am aware of.

    Thread Starter majo_wordpress

    (@majo_wordpress)

    OK, I can give you access to my WP Dashboard. But I have WordPress in Czech Language. I can also send you phpinfo output, if you want.

    Plugin Author Mike Walsh

    (@mpwalsh8)

    I wonder if we’re running into a language support issue. Any chance you can switch your blog to English and see if the problem persists?

    Thread Starter majo_wordpress

    (@majo_wordpress)

    I changed ‘WPLANG’ in wp-config.php to correct English string (“define ‘WPLANG’, ‘cs_CZ'” to “define ‘WPLANG’, ‘en_US'”). My WordPress site is completely in English. I this case problem also still persists.

    Plugin Author Mike Walsh

    (@mpwalsh8)

    Ok – let’s try this (and if you can leave English on when you do it that would be helpful to me):

    In your wp-config.php add the following:

    define('WP_DEBUG', true); // or false
    if (WP_DEBUG) {
        define('WP_DEBUG_LOG', true);
        ini_set('display_errors', 'on');
        error_reporting(E_STRICT | E_ALL);
        define('SAVEQUERIES', true);
        define('SCRIPT_DEBUG', true);
        error_log('Debug On!') ;
    }

    The WP_DEBUG_LOG setting will cause all PHP errors to be logged to a file called “debug.log” in your wp-content directory. Hopefully by doing this we’ll see some sort of PHP error when it fails.

    You can ignore the SAVEQUERIES and SCRIPT_DEBUG settings if you want, that fragment is from my development area.

    Thread Starter majo_wordpress

    (@majo_wordpress)

    I added your code to wp-config. I have WordPress still in English. This is part of my actual wp-config:

    /**
     * For developers: WordPress debugging mode.
     *
     * Change this to true to enable the display of notices during development.
     * It is strongly recommended that plugin and theme developers use WP_DEBUG
     * in their development environments.
     */
    define('WP_DEBUG', true); // or false
    if (WP_DEBUG) {
        define('WP_DEBUG_LOG', true);
        ini_set('display_errors', 'on');
        error_reporting(E_STRICT | E_ALL);
        define('SAVEQUERIES', true);
        define('SCRIPT_DEBUG', true);
        error_log('Debug On!') ;
    } 
    
    /* That's all, stop editing! Happy blogging. */

    I replicate error but the debug.log file is not created in the wp-content directory. What is wrong?

    Plugin Author Mike Walsh

    (@mpwalsh8)

    There is nothing there at all? That is odd. Can you disable WordPress Google Form and see if the file gets created? Information on WP_DEBUG_LOG can be found here.

    You can also try this code fragment from the WordPress Codex instead of the one I provided:

    // Enable WP_DEBUG mode
    define('WP_DEBUG', true);
    
    // Enable Debug logging to the /wp-content/debug.log file
    define('WP_DEBUG_LOG', true);
    
    // Disable display of errors and warnings
    define('WP_DEBUG_DISPLAY', false);
    @ini_set('display_errors',0);
    
    // Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
    define('SCRIPT_DEBUG', true);

    Let me know how you make out.

    Hey guys

    I am having a similar issue. After installing plugins I got the 505 internal server. I have to rename my web.config to view my site.

    It seemed like it was going to be okay until i go into settings and go into permalinks. As soon as I exit, 505 error.

    Even if I go to reading in settings and change main page from static to post or vise versa, 505 error.

    Also when I click on a post from my main page,it says not found and takes me to another website,which is my primary domain.

    Any help would be greatly appreciated

    Thread Starter majo_wordpress

    (@majo_wordpress)

    Mike, if you want, i can prepare a special subdomain for you on my webhosting with new instalation of English WordPress and of course with FTP access. I think that it will be the best to determine the cause of problem with 505 error.

    Is it possible send you PM about access information?

    Plugin Author Mike Walsh

    (@mpwalsh8)

    Yes – you can reach me at mpwalsh8 at gmail dot com.

    Thread Starter majo_wordpress

    (@majo_wordpress)

    Ok, I just send it to your email.

    Plugin Author Mike Walsh

    (@mpwalsh8)

    I have just posted a new beta release which should fix this issue. It turns out that preg_match_all(), a built-in PHP function, was crashing on the server. This beta update resolves the problem by retrieving and parsing the remote content using the WordPress Plugins API.

    Plugin Author Mike Walsh

    (@mpwalsh8)

    @hanklin – your issues doesn’t sound like the same problem @majo_wordpress was running into. Are you still having the issue?

Viewing 15 replies - 1 through 15 (of 22 total)
  • The topic ‘Cannot show WP GF settings – error 500’ is closed to new replies.