xjessie007yahoocom

Can you, pls, post the whole SQL statement here? Just the error does not tell the whole story as it is missing a lot of information.

__________________
[signature moderated Please read the Forum Rules]

You can do exports and imports at the database level. What database and db interface do you use? PhpMyAdmin? MySQL-Front? Log into the server through the db interface and look for something that says import / export.

Here is a correct syntax for these settings and some explanation Order allow,deny

Just a guess, I know these config files are pretty touchy about forward slashes. When for example setting your DocumentRoot, the following two lines are not the same thing

DocumentRoot /var/www/wordpress
DocumentRoot /var/www/wordpress/

Just an idea, I was dealing with similar issues when I turned off FollowSymLinks in one of my directory. Everything was working fine with FollowSymLinks and when I turned it off, everything suddenly went to blank. Just guessing. See here for FollowSymLinks if you like: FollowSymLinks

I agree, something was missing in your code. The directives are often enclosed with the <Directory> tag in your httpd.conf. When talking about the .htaccess file, they are often enclosed with <FilesMatch> tag.

See here for the correct syntax: Order allow,deny

Hi,

You did good job. Just a few clarification.

A)
The IndexIgnore directive adds to the list of files to hide when listing a directory. When adding the IndexIgnore directive to the httpd.conf file, it is good idea to specify where it should be applicable. If you just type it into httpd.conf, it will be applicable to your whole website. So, it is a good idea to enclose it with the <Directory> tag, for example:

<Directory “C:/WWW_ROOT”>
IndexIgnore *
</Directory>

This setting is global. If you want to disable listing for just some folders, then:

B)
If you can edit your .htaccess file (the one in the folder you want prevent from dir listing), insert the following:

Options -Indexes

This stops showing directory listings for URLs which map to the directory.

C)
You could also disable dir indexing completely. Find the following line in your httpd.conf and place a # in front of it.

LoadModule autoindex_module modules/mod_autoindex.so

This will disable directory listing completely for everyone and everywhere.

D)
The Allow,Deny you mentioned relates to restricting access . Again, this can be either in your httpd.conf or in your .htaccess. Note, you did <Files .htaccess>. This gives/restricts access to that file only. If you want to control a folder, you would use <Directory xxx>.

Here is a good page on IndexIgnore: IndexIgnore

See here if interested learning about Order Allow,Deny: Order Allow,Deny

You can take care of this in three places.

A)
If you have access to your httpd.conf (server configuration) file, add the following to the <Directory> section. The IndexIgnore directive adds to the list of files to hide when listing a directory.

IndexIgnore *

B)
If you can edit your .htaccess file (the one in the folder you have problem with, the plugins directory), insert the following:

Options -Indexes

This stops showing directory listings for URLs which map to the directory.

C)
You could also disable dir indexing completely. Find the following line in your httpd.conf and place a # in front of it.

LoadModule autoindex_module modules/mod_autoindex.so

Here is a good page on IndexIgnore: IndexIgnore

Btw, you could also just restrict access to the directory completely with the Allow,Deny directive, but that is another story. See here if interested: Order Allow,Deny

Yeah, having two copies of .htacess with the same content is the problem. You do not need to define rewrite rules twice.

Quote wpbct7:

Usually the mod_rewrite is enabled….

mod_rewrite is usually not enabled. Most of the time, hosting providers have it disabled and you have to do some job find one that has it enabled, just my experience…

Just for the sake of clarity…
When enabling FollowSymLinks, it has to be defined in two places:

First, FollowSymLinks needs to be enabled in httpd.conf. Here is an example what you might want to have in your httpd.conf.

<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Satisfy all
</Directory>

Second, FollowSymLinks may need to be mentioned in .htaccess too. Here is an example
Options +FollowSymLinks

Third, know that FollowSymLinks improves the performance slightly. The effect is almost negligible, but just so you know. Whenever you can, use FollowSymLinks.

Fourth, FollowSymLinks is good for security. You can hide your true location of your files and folders through it.

Here is a good page on FollowSymLinks
FollowSymLinks

Just on the side, you were lucky to find your solution this way. Just for the sake of clarity…
When enabling FollowSymLinks, it has to be defined in two places:

First, FollowSymLinks needs to be enabled in httpd.conf. Here is an example what you might want to have in your httpd.conf.

<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Satisfy all
</Directory>

Second, FollowSymLinks may need to be mentioned in .htaccess too. Here is an example
Options +FollowSymLinks

Third, know that FollowSymLinks improves the performance slightly. The effect is almost negligible, but just so you know. Whenever you can, use FollowSymLinks.

Fourth, FollowSymLinks is good for security. You can hide your true location of your files and folders through it.

Here is a good page on FollowSymLinks
FollowSymLinks