How to check if AllowOverride FileInfo options in vhost is set to ALL?

My first thought was your webhost is a jerk.

I have a feeling your host spoke poorly and meant to say that it is, and you can find out how to USE it (i.e. use .htaccess) via google. Which still makes your host a jerk, cause generally people ask their host for tech help, and a decent host will at least give you a link to get started!

I’d give WordPress a try, and you’ll find out pretty fast if you have it set or not.

Hm, may be he’s a jerk, but your advice didn’t help me much. Could any one help me with this issue?

Put it at the top of your htaccess file.

The reason we think the advice is lame, is because he basically told you “to force the server to read this file, put this code in the file”

If it’s not reading the file, then how can it read the new code in the file?

Andrea I followed you, i.e. I put the code:
<Directory />
AllowOverride All
</Directory>

at the top of my htaccess file, but

it didn’t work completly – in result I have error [500] when entering my blog path.

Any sugesstion?

When you DON’T have that code in your .htaccess, does your blog work at all or do you get an error?

My advice was to just try it without any changes to .htaccess which you said ‘didn’t help much’.

Can you elaborate? What happened or did not happen?

What happenes when I leave .htaccess without any changes?

When I don’t put that code in my .htaccess, my blog works, however when I open the blog I see only text, without any theme I chosen. That’ s not normal blog view :).
The main blog is ok. , however all other blogs in my network – when I open them, there is only text.

What happenes when I put the above code at the top of my .htaccess?
I have Error 500, an no access to my blog at all.

Something is missing, but I have no idea what’s that?

In order to fix that problem you should Clear your cache files and also update your permalinks. I have found that to fix the no theme problem! if it persists than it is something more!! Might try to change themes and change back to see if that fixes that also!!

The subfolder blogs absolutely need the .htaccess rules to work. that’s *how* they work.

What’s the content of your htaccess right now? Without the fix.

Without fix the content of my .htaccess is as follows

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /public.html/wordpress/#
RewriteRule ^index\.php$ – [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
</IfModule>

# END WordPress

Change your rewrite base to JUST be
RewriteBase /wordpress/

After the change I cannot enter the blog at all, and I receive following information

[404] File Not Found

The requested URL /wordpress/bp was not found on this server.

The requested URL /wordpress/bp was not found on this server.

What’s the real URL and where, on your server, is WordPress installed?

Example:

my URL is https://ipstenu.org
WordPress is installed in /home/ipstenu/public_html (NO other folder).
My .htaccess says RewriteBase /

This: RewriteBase /public.html/wordpress/#

Just looks wrong on many levels. First is the # sign, which makes no sense to me at all. And declaring public_html shouldn’t matter, since it’s not asking for the folders you can’t see from the web. It wants to know where, FROM public_html, should it look for WordPress?

Yeah, but I don’t have problems with my ‘htaccess and file public html. I followed installation documentation and it works in case of one blog. Ipstenu, I am not sure whether you undestand my problem i.e I cannot see my other blogs (my network), I see only text. Somebody suggested in other threat that I have to verify this code
< Directory />
AllowOverride All
</Directory>

and check my paralinks

But I don’t know how to do that. Shall I put this code in .htaccess, may be into other file?

That code is what you need to fix the issue, but it does not go in your .htaccess file. It goes in Apache’s httpd.conf file, which you probably do not have access to.

Again, contact your web host. tell them you made htaccess changes and they are not kicking in. Tell them to fix it.