Diogo

Cool, let us know!

Also, pretty permalinks are actually available under IIS 6, you just need to use ASAPI_Rewrite.

You’re better not changing anything if you’re unsure. It is safe to assume that if have never changed the .htaccess file it has the default rules in it, and those rules would allow access to the file.

We can also look at file permissions. If your FTP client can change the file’s permissions, try setting it as 644, or RW-R-R. This will give the owner (your ftp user) Read and Write permissions, and give Read only permission to everyone else.

Yes.. you’re correct, leejosepho. I wasn’t clear.

The default .htaccess file should allow direct access to any non-wordpress files under the directory. If your .htaccess is different than the default, you may need to make changes.

Cheers!

Hi Matty,

Are using using Apache as web server? With Apache, WordPress will create a .htaccess in the installation directory and write some rules to it. The rules will tell how the webserver should serve files under that directory.

The default .htaccess file looks something like this:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

You can check a line-by-line explanation of the rules to understand what it does.

To access the file under root, you may need to create or modify some of the rules, but be careful! Those rules are essential to have pretty permalinks working.

Hola Tom,

I don’t have a windows machine to test, but I think the Microsoft Web Platform Installer (Web PI) won’t allow you to change the directory where WordPress is installed. However, I also think that the default is to install in wwwroot sub directory. Once Web PI is installed, restrictions may apply to further web apps installs.

Ah, there were some issues with Permalinks and IIS 6, you should also check this before installing, or upgrade to IIS 7, if possible.

Here’s a link with the detailed description on how to Install Internet Information Services 7.0 and WordPress 3.x by Using the Microsoft Web Platform Installer 3.0

If you’re not afraid of a little server grooming, you can instally WordPress manually by following these simple instructions: Famous 5-Minute Install – The same document also offers a few other ways to install WordPress.

Cheers

Hi, Dan

You’ll have to change that in the theme’s CSS.

Just login to your site and go to Appearance > Edit CSS and you will be presented with a CSS Stylesheet Editor that you can use to write custom code to override the defaults.

In Twenty Ten the fonts definitions begin on line 113 of the styles.css file. Here’s what you’ll find there:

/* =Fonts
-------------------------------------------------------------- */
body,
input,
textarea,
.page-title span,
.pingback a.url {
	font-family: Georgia, "Bitstream Charter", serif;
}
h3#comments-title,
h3#reply-title,
#access .menu,
#access div.menu ul,
#cancel-comment-reply-link,
.form-allowed-tags,
#site-info,
#site-title,
#wp-calendar,
.comment-meta,
.comment-body tr th,
.comment-body thead th,
.entry-content label,
.entry-content tr th,
.entry-content thead th,
.entry-meta,
.entry-title,
.entry-utility,
#respond label,
.navigation,
.page-title,
.pingback p,
.reply,
.widget-title,
.wp-caption-text {
	font-family: "Helvetica Neue", Arial, Helvetica, "Nimbus Sans L", sans-serif;
}
input[type="submit"] {
	font-family: "Helvetica Neue", Arial, Helvetica, "Nimbus Sans L", sans-serif;
}
pre {
	font-family: "Courier 10 Pitch", Courier, monospace;
}
code {
	font-family: Monaco, Consolas, "Andale Mono", "DejaVu Sans Mono", monospace;
}

Cheers,

-Diogo

Hi!

A lot of things can hurt your load time. Try using PageSpeed Insights to can get a better idea of what is slowing you down.

The problem seems to be with the encoding value. Did you set it manually? I’m not sure if the ‘charset’ should be there. Here’s how a valid encoding declaration looks like:

<?xml version="1.0" encoding="UTF-8"?>

Being hacked is never fun.

Are you using the latest version of WP? Do you use any plugins to generate your feed?

Hey! Good stuff!

Looks like there’s another piece of configuration that needs to be added to the php.ini. Your server appears to be running the Suhosin Extension, and there are some specific configuration need in this case. bemdesign mentions it above, and there are also some clues in the article I referred. Basically, you have to add the info bellow to your php.ini:

suhosin.post.max_vars = 3000
suhosin.request.max_vars = 3000

Let us know if it works!

I’m sorry to hear that. Could you do us a favor? To better debug this it would be very useful to get some information from the php_info() function.

If you can upload files directly to your server, simply create a file named info.php with the following contents:

<?php

phpinfo();

?>

Upload the file to your web root and access it with your browser. It will output a lot of information, search for the max_input_vars and let us know what value is listed there. While on it, see if there are other related vars (request.max_vars, post.max_vars), and also let us know.

The php_info() function might output some sensitive information, so it is not a good idea to leave the file in your server for too long.

Hope it helps!

I don’t think the order matters, but Google uses #2 in their examples:

https://support.google.com/webmasters/answer/96569?hl=en

Hi Zarausto,

I’m a little rusty on theme/plugin development, and a quick look in the Function Reference didn’t give me much hope. I think you’ll indeed need some custom SQL for that, nothing too complex though.

Cheers!

What do you mean? The URL is working fine for me…

Hi Jerry,

How do you access your DB server? Do you have phpMyAdmin?

If you have a direct connection to you DB, you can achieve it with the following command:

DROP DATABASE wordpress

There is no undo, so be careful with it.

If your database was provided by your hosting provider, its better to contact them and ask for detailed directions.

Cheers!