geoffe

It happens when you click on past archives or any permalink for a post or anything that would require the pretty permalinks system to be working.

What will work is an ugly link such as https://www.captainsdead.net/?p=234
or for your june archives https://www.captainsdead.net/?m=200606

You need to check your .htaccess file — what it contains, if there is one — also check that you are on a linux and not a windows server. And get back on your way to Permalinks.

But before you do any of that, upgrade WordPress to 2.0.4 ….immediately. Don’t delay.

doodlebee, AddType application/x-httpd-php .php .html is only good for telling Apache to treat files with the .html extension as PHP files (as well as .php). Some people will also not have the power to do this on their server and only applies if you have files with the html extension that you need parsed by PHP. This won’t be relevant to anything in wordpress, unless you want to rename files like wp-login.php to welcome.html (and then you have to edit all references to wp-login.php but that’s another discussion).

Changing category to a more useful keyword should have an effect but adding html should not please any search bot. Once again, the instructions are here: codex.www.ads-software.com/Using_Permalinks#Tips_and_Tricks

All you do is add .html to your Permalink structure. You could add .cfm or .ass if you liked, the power is in your hands.

covered in the Codex: https://codex.www.ads-software.com/Using_Permalinks#Tips_and_Tricks

See https://www.devlounge.net/articles/customizing-vanilla — the short answer is no, no easy plugin exists yet. But if you know what you’re doing, anything can be done.

Relevant link: https://www.devlounge.net/articles/customizing-vanilla

What you want is a customized Admin Theme. If you want to edit the write post form, see wp-admin/edit-form-advanced.php

p.s. Use i.e., not IE so as not to confuse with another IE.

You could write an .htaccess file yourself. That’s what I do and prefer, rather than let WP attempt it.

could give this plugin a shot
https://wordpress.ex-libris.jp/inline-multiple-uploading/

which allows you to edit the thumbnail height. I’ve hacked this and the original send to editor functions to fix problems in IE and add functions to put in the caption. You’re right, there are problems with IE.

Not sure if this is identical to your troubles, but you can tell me if this discussion I had with myself sheds any light: https://www.ads-software.com/support/topic/73361

You edit the options table in your database, look for Blog address and remove index.php from the address.

The address is for a directory, not a file and will interpret the address for your admin as domain.com/blogname/index.php/wp-admin/

Why is domain.com/blogname not sufficient?

If you are set to use permalinks and no htaccess is set up you will always get a 404 for a url of yourserver.com/2006/07/30/not-able-to-do-blogathon-2006/

The trouble is that type of address is only possible with permalinks and url rewriting. You’ll get a 404 so long as htaccess is not set to send all requests for non-existent files and folders to the index.php of your WordPress root. Can you not create an htaccess file?
Here’s a sample .htaccess
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

If WordPress is not installed in the root directory, this will need to be modified.

If it comforts you at all, I found a similar problem here: https://www.issociate.de/board/post/190669/mod_rewrite_conflicting_with_htpasswd_protection.html

WordPress forums really aren’t the greatest for these types of issues.

Your options appear to be to make a subdomain to get a safe address for user authentication or to move your blog (and hence, the URL rewriting) out of the site root to avoid the conflict.

Have you seen the page for wp_list_authors?

If you use <?php wp_list_authors('hide_empty=1'); ?> then any users without posts won’t be displayed.

so what do you have in that bottom file, the .htaccess in the site root?

It will have an effect on subdirectories that you’ll need to negate.

You should seek help on understanding htaccess, not WordPress, to find help on this. What you want to have is a htaccess RewriteCond conditional rule, that excepts your [ protected ] directory from forcing everything to WP, which is what I presume is happening.

Thanks, I tried there and no thing is happening.