It’s likely a plugin. Disable them, and see if that fixes it. If it does, enable one by one, until you find the culprit. If it’s not a plugin (and even if it is), you can try to increase the memory allocated for PHP. Add this to your config.php: define(‘WP_MEMORY_LIMIT’, ’64M’); You can read more … Read more
I’ve found that I need to change the siteurl and home entries in wp_options when I move from local to a live server. Not sure that should affect a connection to the database though.
This is actual mail server trouble, where email cannot be sent. This link will useful. http://angstrey.com/index.php/2009/04/22/how-to-send-e-mail-with-wordpress-from-godaddy-windows-hosting/
Looks like you have 2 WordPress installations. One for the main site, other for the Blog. http://parlourdc.com/wp-content/plugins/akismet/readme.txt http://parlourdc.com/blog/wp-content/plugins/akismet/readme.txt If that’s not on purpose, you have a blog folder in your site root that should be renamed/deleted as it contains a blank WordPress. If you made a page on your main site titled Blog (and with … Read more
Turn off all plugins. Switch to TwentyTen. Then install the debug bar and helpers. Then switch back to custom theme – reload. Turn one plugin on – reload, next plugin – reload, etc.
Could be a problem with your .htaccess. Check the permalink settings, change to something else and hit save. If there is an error, there’s your problem. It could also be with the theme. Try out another theme (such as the default) to see if any error appears.
Identifying errors via error code Run add_user_to_SF with an earlier priority, to make it execute first add_filter( ‘registration_errors’, ‘add_user_to_SF’, 9, 3 );` Let’s assume you have two possible errors in your add_user_to_SF: function add_user_to_SF( $errors, $sanitized_user_login, $user_email ) { $has_errors = false; if ( /* some condition that should throw an error */ ) { … Read more
I figured it out. Turns out that using the field name was the culprit. It appears that name and other field names like attachment, attachment_id, etc will cause WordPress to produce a 404 error. There’s a whole list of reserved terms in the Codex.
One way to do this is to use the status_header filter. Adding the following to the functions.php file or your theme (or an appropriate plugin file) would do the trick: add_filter( ‘status_header’, ‘your_status_header_function’, 10, 2 ); /** * Substitutes a 202 Accepted header for 404s. * * @param string $status_header The complete status header string … Read more
If you can log into your host with SSH or FTP, it’s an easy fix. Like the comments said before, check your permissions for the WordPress directory. For example, if you check the hosting directory with ls -al (typically /var/www, as on DigitalOcean), they should look something like this: drwxrwxr-x 6 www-data www-data 4096 Nov … Read more