Error Message on Wordpress site - wordpress

Hey all, this is my first post. I recently upgraded a wordpress site, all things load but on the top of the page and bottom of the page I get this error.
Warning: session_start() [function.session-start]: open(/tmp/sess_6v2kul3t823ah9074g3cl2lrt6, O_RDWR) failed: Permission denied (13) in /home/admin_m3/incommunion.org/wp-content/plugins/wordpress-automatic-upgrade/wordpress-automatic-upgrade.php on line 121
How can I remove it from the page? I believe the server automatically upgraded the version of Wordpress.
Its running on Apache, PHP5 Fast CGI
Any idea?
Newbie A

That error is usually from extra white space or garbage characters before the opening <?php of a file, or from a file being saved at UTF-8 with BOM rather than without BOM (Byte Order Mark). Did you edit any files? It could also be simply a transient error from the automatic upgrade and those problematic files were deleted.

We've just run into this today and the sys-admin guys had to change permissions of that directory. Which could be done with chmod. Not sure that this is the issue, but worked in our scenario.
If you're just wanting to suppress the error, there should be a setting in the wp-config.php file that you can change to suppress WP errors
define('WP_DEBUG', false);
Which more info can be found at http://codex.wordpress.org/Editing_wp-config.php
Otherwise, if you're just wanting to suppress general php errors, the answer from this post should work too.
Best way to suppress php errors on production servers

Related

WordPress internal Server Error 500 when moving hosts

I am trying to move my WordPress site from one hosting service to another. I made a backup and restored it on the new host. But I am getting internal server 500 error on the site. I have tried to fix the .htaccess file but its still giving error.
The issue is, if I try to rename it to test it, its not giving the internal 500 error but redirecting me to WordPress installation page called wp-admin/install.php
Can someone help me for solve the issue.Thanks
All the suggestions that are given are great, but if those do not work, then you can try to downgrade PHP. It had worked in my case when I was facing the same error.
You can dig in the error log and find what exactly is causing the error.
Steps for debug.
As previously said: stop all plugins and try again. If problem still exists check logs again. Then switch to default theme and so on.
Btw have moved the DB properly? With the same connection settings.
I think you should check your wp-config.php and PHP version. make sure you have entered correct DB info in wp-config like db_name, password, and table_prefix etc...
if You have changed hosting, probable You need to check database and .htacess file. If You are getting installation page means its database issue, Please check database prefix in wp-config.php file and it will solve your issue.
there are lot of causes for internal server error. The main reasons for internal server errors are.
Corrupt .htaccess file
PHP Memory limit
Faulty code in Theme
Corrupted plugin
Corrupted core files
Incompatible PHP version
In oder to fix this issue, you need to investigate in step by step order.
To solve this issue first of all you need to enable Debug mode and check the issue.
after that try with restoring .htacess file, enabling default theme, disabling plugins etc.
if you still facing 500 internal server issue, follow tutorial on WPERA to fix 500 internal server error. Hope this helps.

I get an error when I try to move a Wordpress site for development

I am re-designing someone's Wordpress website and moslty need to change the CSS I wanted to move the entire website over to my server in order to develop it. Mostly I am just changing the design/CSS but there are some custom parts I want to keep such as there is a testimonial plug-in/widget that has a custom place in the dashboard and a way to post testimonials.
I downloaded the entire site.
Exported the database
And then moved it to my server and uploaded the files and created a new database and imported it.
Then I used this to change the database to the correct directory:
https://interconnectit.com/products/search-and-replace-for-wordpress-databases/
Now I am getting a crazy error:
Warning: Cannot modify header information - headers already sent by (output started at /home//public_html/wordpress/wp-config.php:156) in /home/public_html/wordpress/wp-content/plugins/wp-greet-box/includes/wp-greet-box.class.php on line 493
Warning: Cannot modify header information - headers already sent by (output started at /home/llhimhi1/public_html/wordpress/wp-config.php:156) in /home/l/public_html/a/wordpress/wp-includes/pluggable.php on line 1121
I don't know if I should continue trying to make this work, or just copy the theme to a fresh install. But I am not sure what else to copy since there are custom plugins and stuff in the dashboard.
Help would be much appreciated.
A "headers already sent" error is a very common PHP error having to do with white space or junk characters in a file, or a file that was corrupted during FTP transfer. Check your wp-config.php file.
From FAQ Troubleshooting » Headers already sent warning « WordPress Codex
It is usually because there are spaces, new lines, or other stuff
before an opening tag, typically in
wp-config.php. This could be true about some other file too, so please
check the error message, as it will list the specific file name where
the error occurred (see "Interpreting the Error Message" below).
Replacing the faulty file with one from your most recent backup or one
from a fresh WordPress download is your best bet, but if neither of
those are an option, please follow the steps (at the link above).
And read http://codex.wordpress.org/Debugging_in_WordPress on how to set up debugging to find causes of "white pages" and other PHP errors.

Wordpress - wp-admin showing blank

Every part of my web site is working fine after I moved it from one hosting to another. The problem I have now is that I can't access wp-admin.
I now get the following error:
Warning: Cannot modify header information - headers already sent by (output started at /home/everd1/public_html/precision/wp-content/themes/Avada/Avada/admin/functions/functions.options.php:1) in /home/everd1/public_html/precision/wp-includes/pluggable.php on line 1121
So far I've tried:
Removing trailing white space before and after functions.php and pluggable.php
Increasing the allowed memory size on the .htaccess file
Creating a php.ini within the wp-admin folder with the following memory_limit = 64M ;
Renamed the plugins folder to plugins-removed
Still no joy, anything I can do to fix this?
The warning that you have posted shows the exact error and the place that it is happening.
It looks like something within the Avada theme has broken when you were transfering it and it has since messed up the headers being sent through.
Only 1 set of headers can be sent to the client otherwise it cannot be handled and therefore throws an error.
I would recommend going to the theme creators (click here) and putting in a support ticket. One of their support team should be able to fix the problem that you are having.
You can check if some file of your Wordpress copy contains UTF-8 with BOM files and convert it to UTF-8 without BOM.
You can try this php script to make it faster : https://github.com/emrahgunduz/BomCleaner
Be sure to make a backup before running it.

Drupal - White Screen of Death after updates (and login page returning 403 error)

I have just updated a site that is using Drupal and have now experienced the horrible WSOD.
I have searched through Google looking for any sort of solution/error log to help me find and fix the issue but nothing has worked. I have tried adding in the 'display errors' code in the index.php file and looked at the error_log file in the public directory and nothing.
I can not login to the admin page and check any modules as the login page for this is returning a 403 error.
Any suggestions?
Please go to Apache Error log. You will exact error messages there.
The log file's location is different for different OS and versions.
e.g httpd/log/error.log
Maybe your Drupal registry is broken.
Fix this using the registry_rebuild script (this is no module!)
There are times in Drupal 7 when the registry gets hopelessly hosed and you need to rebuild the registry (a list of PHP classes and the files they go with). Sometimes, though, you can't do this regular cache-clear activity because some class is required when the system is trying to bootstrap.
You might get something like:
PHP Fatal error: Class 'EntityAPIControllerExportable' not found in ...sites/all/modules/rules/includes/rules.core.inc on line 11
If this happens when you're trying to run update.php, and happens when you're trying to clear your cache, well, you have some trouble. That's what Registry Rebuild is for.
It also may happen that you've moved some module that Drupal requires to bootstrap, and you get a horrible error. Registry Rebuild will also rebuild the system table to get the modules in the right place so you can bootstrap.
You will need PHP-CLI or drush to run this.
https://drupal.org/project/registry_rebuild

Wordpress Blog :: 500 Internal Server Error

I am getting this error message while trying to access a wordpress blog which is installed in a directory. Is this due to .htaccess or something? Any help is appreciated.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster#xxxxx.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache Server at xxxx.com Port 80'
This is almost always a problem with your Apache configuration. Errors originating in PHP won’t trigger the Apache 5xx handler, which is what you’re seeing.
Unfortunately, without more information, your problem is impossible to diagnose. I’d recommend that you:
Check the logs. First thing! It should give you a better idea where your problem is.
Stop and restart Apache. If there is a problem with permissions on something Apache needs write access to (logs), it could completely fail to start. This should give you the proper motivation to fix the problem, particularly if there are other VirtualHosts on that Apache.
Move your .htaccess file(s) somewhere else. If Apache works, you know it’s a problem with that file.
It sounds like you're getting some sort of PHP error but PHP isn't set to display errors. You'll want to check your Apache logs for detailed error info.
The mostly likely culprit is that you're missing some prerequisite for running WordPress, although all you should really need is Apache, MySQL, & mod_rewrite.
I was able to fix it by adding the following line to my .htaccess file:
php_value memory_limit 128M
Russ
This is happening to me RIGHT NOW.
As to from what I know, my hosting providers did a DNS change and so I'm waiting for the DNS to propagate, it's been like three hours and still zero.
Blog is showing ok, apache is up and working, I just can't get access into the WP Admin area.
If it does get fixed by tomorrow, I'll reply here so it can be of help for others.
Edit: I just fixed my problem.
In my case it was determined that the Fast Contact Form plug-in was creating the problem. I modified the folder name from si-contact-form to si-contact-form-hold then I regained WP Admin access.
After that I created a php.ini file with this string inside 'memory=64MB' and saved that into the wp-admin folder.
Manually deleted the si-contact-form-hold (to avoid possible corrupted files) and reinstalled the Fast Contact Form.
All my settings were already there and everything is back up and running good!
Hope this helps.
Look at http://zemalf.com/1470/wordpress-htaccess-the-definite-guide/, and look for the paragraph which says something like "Good and default .htaccess looks like this...."
My issue was a little bit different. I had an .htaccess file inside the wp-admin directory. I deleted the .htaccess inside of wp-admin and that fixed my problems.
Unfortunately it could be anything. Do static pages on the site work properly.
Have you checked the server logs.
I think it is likely to do with php. If static pages are there then possibly your config for wordpress is incorrectly configured or files missing.
Has php be working? Did the blog work and then stop? Did you get through the install process?
Check wordpress files ownership for the user are correct or not.
In linux ls -laZ command will display the ownership.
For setting the ownership for a folder use this command
chown -R username:username /user/username/public_html/
An HTTP 500 error could be caused by a great many things. Have you changed your .htaccess file recently? If you try to use a .htaccess feature that is disabled on your host, that is one possible cause.
Some more points
Blog has been running successfully. Just observed this problem since yesterday.
Blog is in a directory so it works something like this www.xyz.com/blog. Apparently www.xyz.com is working perfectly.
Update on logs
Getting these two errors in the logs:
File does not exist: /home/directory/public_html/500.shtml
/home/sub-directory/public_html/sub-directory/.htaccess: RewriteCond: bad argument line '%{REQUEST_FILENAME}!-f'
/home/directory/public_html/sub-directory/.htaccess: # without matching # section
How do I restart apache on cpanel ?
memory = 64MB;
The above line inside a php.ini file uploaded to the wp-admin folder solved my problem. I was not being able to log into the dashboard either through /wp-admin or /wp-login.php, and was getting a HTTP server error 500.
There can be multiple causes for this, I just solved mine, after 2-3 hours of going crazy.
I had another WP instance in a subdirectory inside the main WP instance (in the root folder).
Have checked / deleted .htaccess
deleted plugin folder
In the end, it was to do with the permission of the subfolder in which second instance was running. It was originally 775 (write permission for group), I had to change it to 755 (no write permission for group) and this finally fixed it, like magic.
This is of course just one of possible the answers to your question, I wanted to write it down though as I didn't find it explicitly written anywhere so it might save others some time.

Resources