adamtinsley

Looks like you have a comment “/*” before the <!DOCTYPE> declaration at that URL which would usually be in your header.php file. That is probably causing the broken page. The closing comment “*/” is right after <div id=”casing”> probably at the top of index.php or maybe the bottom of header.php.

Hmmm. That’s the default index.php file for the root directory, at least for the latest versions. It basically just loads your wordpress installation, but if it is set up incorrectly it could not only NOT load the other files, it could also hide them which is probably why you can’t access wp-admin.

I get the same return when I try to navigate to the default feed URL which should also be in the root of the installation, so I would say that file is your problem. Somehow it is returning nothing more than “0”.

I can’t think of any reason that file should have more defines in it. If you would like to copy the extra code in the file I’ll take a look at it. But if it where me, I would make a backup of that file, and then re-upload the default index.php file for whatever version of WordPress you are using which is probably just the code above.

If all your files are still in that directory then check your index.php file. It should contain the following code. If it doesn’t, then that’s the problem.

<?php
/**
 * Front to the WordPress application. This file doesn't do anything, but loads
 * wp-blog-header.php which does and tells WordPress to load the theme.
 *
 * @package WordPress
 */

/**
 * Tells WordPress to load the WordPress theme and output it.
 *
 * @var bool
 */
define('WP_USE_THEMES', true);

/** Loads the WordPress Environment and Template */
require('./wp-blog-header.php');
?>

Nevermind… I’m a bit slow this morning. You have your blog in a subdirectory named “blog”?

It looks like your blog is at https://www.pearlskeywest.com/. Did you change the Site address URL in General settings? You should be able to access your admin account at https://www.pearlskeywest.com/wp-admin.

I like RackSpace the best. Right now I have a VPS through Slicehost, which is owned by RackSpace and I could be happier. Here’s a price list for their cloud servers. My next choice would be a DV server at Media Temple.

Do you have a caching plugin installed?

Sounds like you need a new hosting company.

I would suggest using a heading or a span class. Like this:

<h2>This Line Bigger</h2>

You need to know the name of the <div> tag that the widget is positioned under. You can “View Source” code in most browsers to figure this out. We’ll call it ‘example’. You would then style it in CSS like so:

h2.example {
  font-size: XXpx;
}

or you can use a span class like this:

<span class="example">This Line Bigger</span>

and style it like this:

.example {
  font-size: XXpx;
}

Hope that helps.

Easy, just add an index.php file to the directory with this in it:

<?php
// Silence is golden.
?>

The browser will then render a blank page.

Duh. Somehow I overlooked this article. Using too many keywords in Google I guess?

Many thanks.

Sorry. The link I posted was supposed to direct to view-source:www.printedthreads.com. You must be using a Chrome browser to see your code like this. In Safari select View > View Source. In any case, you will have to locate the code in your installation and delete it or follow the instructions in the link that Ipstenu posted above. The code appears to be located at the top of the page in your header.php file so start there. I would also check your .htaccess file for anything unusual. Also note that WordPress recommends 644 permissions for .htaccess. If your .htaccess permissions are set higher than this then that may be the security issue.

You have an extra closing brace ‘}’ in your css file after the body style. That may be the reason.

The code starts on line 152 just after the </head> tag: source code. First, I would change passwords for your WordPress install and your web host and then try to find the location of the code in your files.

That sucks.

You might check out Slicehost’s articles repository to find your answer. I think it’s covered here for the Debian distributions.

When I ran one of your pages through the w3c validator this is the source code that I see https://pastebin.com/vkCUhAgA

This code is probably in your comments.php file but it’s being output by a function in your page file. Look for something like <?php comment_form(); ?> Note: there may be $args between the parenthesis. It’s hard without seeing the actual code in your theme but this is how most themes are set up.