hallsey

Yes, in that case, replace .thinborderfloat { with img { (no period). Now you don’t have to put class='... in your <img tags; all images will automatically display formatted with that class.

Stakota, some more info: a directory is the same thing as a folder. A subdirectory is just a directory inside another directory, or a folder insider another folder.

When you connect with your FTP program, you should be able to navigate the folders (directories) on your website just like you do the folders on your own computer. Just imagine your website as an extension of your own computer, with folders, files, and folders inside of folders.

The file is your theme’s style.css file, under wp-content/themes/[your_theme].

The code to add there is:

.thinborderfloat {
float:left;
border:solid 1px silver;
padding:5px;
margin-right:10px;
}

Later, in your posts, when adding an image, you’d use:

<img class='thinborderfloat' src='... />

Just a thought: go into Options | Miscellaneous and confirm that jpeg is an allowed file extension. WP comes by default set to allow files with both jpg and jpeg extensions, but check anyway.

What baffles me is that the code appears to try to set fileupload_url correctly. The install.php routine calls function populate_options() in upgrade-schema.php. There we find this code:


function populate_options() {
global $wpdb;
$guessurl = preg_replace('|/wp-admin/.*|i', '', 'https://' . $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI']);
add_option('siteurl', $guessurl, __('WordPress web address'));
//other add_options calls removed from example for brevity
add_option('fileupload_url', get_option('siteurl') . '/wp-content');

It looks like the code tries to set fileupload_url to something more than just /wp-content, but it’s as if siteurl is blank at the time this line executes.

However, at the end of the installation, I’ve verified that siteurl does have the correct value, and moreover, I can’t find a place where it might have acquired the correct value afterward.

I’m not up to speed on PHP enough to figure out what’s going on here.

Yes, an intermittent error like that must be something on your host’s side.

And, by the way, just FYI, I was NOT lame, and I’m not anymore, anyway! ??

The Blogroll is just the name of a links category that contains links. You can delete the links from the admin panel, under Links. After that, you can delete or modify the link category called Blogroll.

To prevent new installations from generating blogrolls, you can modify the install.php file in the wp-admin directory. But maybe post more details about what you want to do before we go thre?

Thank you! Actually, the correct edit is one line above the one suggested in the link you gave.

In functions-post.php, line 353 reads
|| ($author_data->user_level > $post_author_data->user_level)

“or if this author’s level is greater than the original author’s level…”

So just change the > to >= and that does it.

You need to get Apache, MySQL and PHP working before WordPress will work. The setup you need is called WAMP if you’re using Windows, and LAMP if you’re using Linux. Maybe you can google for that. From your post before, it sounds like you Apache running but it’s not configured right. Sorry, I don’t know much about Apache.