-
AuthorPosts
-
March 19, 2014 at 5:00 am #1155
Hi this is my first post here, I am tearing my hair out.
I am not with Blue Host, I am hosting Easycgi … I have been with them for years and didnt want to change at this stage.
After all sorts of problems I finally have a basic wordpress on my site.
When I install Symbiostock theme (just the basic one for now) I get this error:
“wp-adminincludesfile.php on line 869”
I am not sure what this effects or how to fix it at this stage, I am trying to work out one glitch at a time.
March 19, 2014 at 7:02 am #10520That is a first for me.
Disable all plugins except the most basic Symbiostock ones.
Does the error still come up? That is saying something in the administration screens (not the front end of the site) could be tripping it up.
Do you know what version of PHP you are using?
March 19, 2014 at 7:11 am #10521I have no plugins going at all except for the basic symbio theme. I had installed jetpack but it is deactivated. I have not got any of the other plugins downloaded yet.
I am running php 5.2.5 according to the web site information.
I, like you, think it might be something in my administration, but if I use the wordpress 2013 theme no error message, activate symbiostock and the error message pops up.
March 19, 2014 at 7:31 am #10522researching now …
March 19, 2014 at 7:32 am #10523Thank you Leo 🙂
March 19, 2014 at 7:42 am #10524This might explain why its a hosting-specific issue. Forgive me if this might seem overwhelming … its for future eyes 😯
Following the path of the error …
wp-adminincludesfile.php on line 869
We are brought to this file:
/**
* Functions for reading, writing, modifying, and deleting files on the file system.
* Includes functionality for theme-specific files as well as operations for uploading,
* archiving, and rendering output when necessary.
*
* @package WordPress
* @subpackage Administration
*/
Then we are brought to this function (line 869)
/**
* Initialises and connects the WordPress Filesystem Abstraction classes.
* This function will include the chosen transport and attempt connecting.
*
* Plugins may add extra transports, And force WordPress to use them by returning the filename via the 'filesystem_method_file' filter.
*
* @since 2.5.0
*
* @param array $args (optional) Connection args, These are passed directly to the WP_Filesystem_*() classes.
* @param string $context (optional) Context for get_filesystem_method(), See function declaration for more information.
* @return boolean false on failure, true on success
*/
function WP_Filesystem( $args = false, $context = false ) {
global $wp_filesystem;
require_once(ABSPATH . 'wp-admin/includes/class-wp-filesystem-base.php');
$method = get_filesystem_method($args, $context);
if ( ! $method )
return false;
if ( ! class_exists("WP_Filesystem_$method") ) {
$abstraction_file = apply_filters('filesystem_method_file', ABSPATH . 'wp-admin/includes/class-wp-filesystem-' . $method . '.php', $method);
if ( ! file_exists($abstraction_file) )
return;
require_once($abstraction_file);
}
$method = "WP_Filesystem_$method";
$wp_filesystem = new $method($args);
//Define the timeouts for the connections. Only available after the construct is called to allow for per-transport overriding of the default.
if ( ! defined('FS_CONNECT_TIMEOUT') )
define('FS_CONNECT_TIMEOUT', 30);
if ( ! defined('FS_TIMEOUT') )
define('FS_TIMEOUT', 30);
if ( is_wp_error($wp_filesystem->errors) && $wp_filesystem->errors->get_error_code() )
return false;
if ( !$wp_filesystem->connect() )
return false; //There was an error connecting to the server.
// Set the permission constants if not already set.
if ( ! defined('FS_CHMOD_DIR') )
define('FS_CHMOD_DIR', ( fileperms( ABSPATH ) & 0777 | 0755 ) );
if ( ! defined('FS_CHMOD_FILE') )
define('FS_CHMOD_FILE', ( fileperms( ABSPATH . 'index.php' ) & 0777 | 0644 ) );
return true;
}Particularly these lines (in vicinity of 869)
// Set the permission constants if not already set.
if ( ! defined('FS_CHMOD_DIR') )
define('FS_CHMOD_DIR', ( fileperms( ABSPATH ) & 0777 | 0755 ) );
if ( ! defined('FS_CHMOD_FILE') )
define('FS_CHMOD_FILE', ( fileperms( ABSPATH . 'index.php' ) & 0777 | 0644 ) );
So what we are seeing here is that wordpress is having a permissions issue – this is related to the hosting environment. Its possible this host is a little too strict (or even misconfigured) with permissions.
This error is very likely coming from the installer which creates some directories for the uploader and other directories, and installs some default plugins.
If you email your host this answer you might make some progress. (of course I could be wrong)
March 19, 2014 at 7:45 am #10525Thank you for looking into it Leo, I will get onto them and see if I can get it resolved …. 🙂
March 19, 2014 at 8:03 am #10526Hi Wendy and Welcome to Symbiostock.
I have edited the heading of your post in case anyone else gets the same problem to make it easier to find answers. (fingers crossed)
http://kerioakimaging.com - trying to reopen
http://nail-art-at.kerioak.com - Art and Nail ArtMarch 19, 2014 at 4:39 pm #10527Welcome Wendy. I hope your hosting folks can sort out the problem for you. I know that it can seem overwhelming when getting started, but it does get better – honest 🙂
March 21, 2014 at 1:14 am #10528@christine wrote:
Hi Wendy and Welcome to Symbiostock.
I have edited the heading of your post in case anyone else gets the same problem to make it easier to find answers. (fingers crossed)
Thank you Christine.
@joannsnover wrote:
Welcome Wendy. I hope your hosting folks can sort out the problem for you. I know that it can seem overwhelming when getting started, but it does get better – honest 🙂
JoAnn I have been battling this for over 2 weeks now, I thought it was me at first.
Anyway the web host has fixed the error, it had to be escalated to their SysAdmin dudes.
I am still having trouble though 🙁 I will start a new thread on the latest issues …. all I want is for it to work lol.
March 21, 2014 at 1:32 am #10529Thanks Leo for giving me the right things to say to the web host 🙂
March 21, 2014 at 1:52 am #10530what was the actual error message reported? you just gave the point where the error occurred
March 21, 2014 at 11:40 pm #10531@cascoly wrote:
what was the actual error message reported? you just gave the point where the error occurred
The full message was
“Warning: fileperms() [function.fileperms]: stat failed for … address deleted … wp-adminincludesfile.php on line 869The system administrators had to go in and weave their voodoo and I no longer get the message.
-
AuthorPosts
You must be logged in to reply to this topic.