Impossibile accedere a sottodirectory non wordpress perché wordpress le sovrascrive con un errore 404

Presumo chetumetta WordPressnella radice deltuo sitoe che anche le directoryesterne sianonella radice deltuo sito. Ilmotivoper cui ciò sta accadendo è chei file .htaccess seguono unagerarchia. Qualunque sia la direttiva contenutanelfile .htaccess diprimo livello,scorre versoilbassoe si applica atutte le directory sottostanti.

In questo caso,puoieseguire una delle seguenti operazioni:

1. Spostailtuo WordPressnella sua directory. Vedi: http://codex.wordpress.org/Moving_WordPress Se sposti WordPressnella sua directoryin modo che sia allo stesso livellonellagerarchia delle directory del server delle altre directory,le regole di riscrittura di WordPressnonpossonoinfluenzare le altre directory.

2. RewriteEngine Off:normalmentefunzionerebbe. Senonfunziona,verifica dinon utilizzare un'impostazione DNS con caratterijolly. Se hai un record dinome host con caratterijolly * chepunta altuo server webnelleimpostazioni DNS,può causareil caos con .htaccesse sottodomini.

3. Nelfile .htaccessnella radice deltuo sito,aggiungi quanto segue SOPRA le direttive .htaccess di WordPress:

    <IfModule mod_rewrite.c>
   RewriteEngine On
   RewriteBase /
   RewriteCond %{REQUEST_URI} ^/subdirectoryname1/(.*)$ [OR]
   RewriteCond %{REQUEST_URI} ^/subdirectoryname2/(.*)$ [OR]
   RewriteRule ^.*$ - [L]
   </IfModule>
   

Uno di questi dovrebbefunzionareperte.

I'm assuming that you put WordPress in your site root and the external directories are also in your site root. The reason this is happening is that .htaccess files follow a hierarchy. Whatever directives are in the top-level .htaccess file flow down and apply to all directories below it.

If this is the case, you can do one of several things:

1. Move your WordPress into its own directory. See: http://codex.wordpress.org/Moving_WordPress If you move WordPress into its own directory so that it is on the same level in your server directory hierarchy as the other directories the WordPress rewrite rules cannot affect the other directories.

2. RewriteEngine Off - this would normally work. If it isn't working check that you are not using a wildcard DNS setting. If you have a wildcard * hostname record pointing at your web server in your DNS settings it can cause havoc with .htaccess and subdomains.

3. In the .htaccess file in your site root, add the following ABOVE the WordPress .htaccess directives:

   <IfModule mod_rewrite.c>
   RewriteEngine On
   RewriteBase /
   RewriteCond %{REQUEST_URI} ^/subdirectoryname1/(.*)$ [OR]
   RewriteCond %{REQUEST_URI} ^/subdirectoryname2/(.*)$ [OR]
   RewriteRule ^.*$ - [L]
   </IfModule>
   

One of these should work for you.

Questo hafunzionatoperme inpassatoper una situazione simile:

Mettilo sopra .htaccess

 ErrorDocument 401 default
 

This has worked for me in the past for a similar situation :

Put this on top of .htaccess

ErrorDocument 401 default

Vedo che questothread è vecchio dipochimesi,manel casonon lo avessimaifattofunzionare!

Ho avuto unproblema simile,mailmioproblemaera che l'installazione di wordpress sitrovavanella sottodirectory cheimpediva l'accesso URL alle cartelle all'interno della root (al difuori della directory diinstallazione di WP),ma solo quandoi permalinkerano abilitati. Per risolvere questoproblema,ho copiato siaindex.php che .htaccess (copianon sposta) dalla sottodirectoryin cui sitrova l'installazione di WPe li hoposizionatientrambinella rootpublic_html (o qualsiasi sottodirectory a cui staitentando di accedere al difuori dell'installazione di WP directory). Ilfile .htaccess hagià le condizioni di riscritturaperi permalink:

 RewriteEngine On
RewriteBase /subdirectoryinstallfolder/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
 

Abilitai permalinkper l'aggiornamentoe ha risoltotuttii problemi. Assicurati che anchei tuoipermessiper le cartelle di root sianoimpostati correttamentepoiché questomi ha causatoproblemiin passato.

I see this thread is a few months old, but just in case you never got it to work!

I had a similar issue, but my problem was that the wordpress install was located in the subdirectory which prevented URL access to folders within the root (outside the WP install directory), but only when permalinks were enabled. To solve this, I copied both index.php and .htaccess (copy not move) from the subdirectory where the WP install is located and placed them both in the root public_html (or whatever subdirectory that you're trying to access outside the WP install directory). The .htaccess file has the rewrite conditions for permalinks already:

RewriteEngine On
RewriteBase /subdirectoryinstallfolder/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

Enable permalinks for refresh and it solved all issues. Make sure your permissions for the root folders are set correctly too as this has caused me problems in the past.

quando copioi mieifilenello stesso serverma con una cartella di sottodirectory diversa,quindi quando hoprovato ad accedere allemie pagine,index.phpfunzionabene ma le altrepaginenon lo sonoe mi dà unerrore 404.Scusaperilmio cattivoinglese !!

Guardo solonelmio htaccess l'originale:

# INIZIA WordPress

RewriteEngine On
RewriteBase/
RewriteCond% {REQUEST_FILENAME}! -F
RewriteCond% {REQUEST_FILENAME}! -D
RewriteRule./index.php [L]

# FINE WordPress 

e inserisci quellonuovo con

# INIZIA WordPress

RewriteEngine On
RewriteBase/sottodirectoryfolder
RewriteCond% {REQUEST_FILENAME}! -F
RewriteCond% {REQUEST_FILENAME}! -D
RewriteRule./subdirectoryfolder/index.php [L]

# FINE WordPress

when i copy my files into the same server but with different subdirectory folder so when i tried to access my pages, index.php is working fine but the other pages are not and giving me a 404 error. Sorry for my bad english!!

I just look into my htaccess the original:

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

and put the new one with

# BEGIN WordPress

RewriteEngine On
RewriteBase /subdirectoryfolder
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /subdirectoryfolder/index.php [L]

# END WordPress

Se stai ancora ottenendo 404 con htaccess disabilitatoe hai verificatoi percorsie sai chei file sono lì,letue uniche opzioni rimaste sono questetre ...

Opzioni ...

1. Èmoltoprobabile cheil server utilizzi un sistema operativo chefa distinzionetramaiuscolee minuscole.Ciò significa che se stai digitando unpercorsoe non usii caratteriesattie ilmaiuscolo/minuscolo semplicementenonfunzionerà.
2. Autorizzazioni:potresti avere le autorizzazioni sbagliateperilfile,la cartella o una cartellaprincipale.Prova amodificare le autorizzazioniin 755 sufile,cartellee cartelleprincipali.Se hai accesso ssh (terminale),vai allatua rootedesegui questo "chmod -R 755mydir"e questoimposterà ricorsivamentei permessipertutti loro.
3. Se hai ancora unproblema dopotutto ciò,allora hai unproblema di configurazione del server (probabilmente Apache).Dovraiparlarne coniltuoprovider di hosting.

Senessuna di queste soluzionifunziona,ènecessario unnuovo host.

If you are still getting 404's with the htaccess disabled and you have verified the paths and you know the files are there then your only options left are these three...

Options...

1. Server is quite possibly running a case-sensitive operating system. Which means if you are typing in a path and not using the exact characters and casing it simply will not work.
2. Permissions: You may have the wrong permissions on the file or folder or a parent folder. Try to change the permissions to 755 on the files, folders, and parent folders. If you have ssh (terminal) access to it then go to your root and run this "chmod -R 755 mydir" and that will recursively set the permissions for all of them.
3. If you are still having a problem after all of that then you have a server config problem (Apache probably). You will need to talk to your hosting provider about it.

If none of that works then you need a new host.

Dopoessermi quasi strappatoi capellimodificando htaccess,hofinalmentetrovato una soluzione chefunzioneràper WordPress.

Ho riscontrato questoproblema dopo averinstallato uno script codeiginter sulla stessa directoryprincipalein cui èinstallato WordPress.

Dopo averprovatotuttii trucchi quielencati,ricevevo ancoraerrori 404nellepagine associate alnuovo script.

Honotato che htaccess di WordPress sovrascriveva htaccess dello script. Ho anchenotato che altreinstallazioni di WordPressnella stessa directorynonpresentavano questoerrore 404.

Ho semplicemente adottato htaccess dallanuovainstallazione di WordPressnella stessa directory del servere l'ho aggiuntonella cartellain cui sitrovailmio script. Ecco come appare:

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

Sostituisci subdirectoryname conilnome dellatua directorye posiziona questofile htaccess all'interno della cartellain cui sitrova lo script.

Esempio: seil sito èinstallato qui

public_html/

e sitrova lanuova cartella

 `public_html/example`
 

copia l'htaccess soprae salvalonella cartella "example"e dovrebbefunzionare.

After nearly plucking my hair editing the htaccess I finally found a solution that will work for WordPress.

I had this problem after installing a codeiginter script on the same root directory that WordPress is installed.

After trying all the tricks listed here I was still getting 404 errors on the pages associated with the new script.

I noted that the WordPress htaccess was overiding the script's htaccess. I also noted that other WordPress installations in the same directory did not have this 404 error.

I simply adopted the htaccess from the new WordPress installation in the same server directory and added it in the folder where my script is located. Here is how it looks like :

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

Replace subdirectoryname with the name of your directory and place this htaccess file inside the folder where your script is located.

Example : If the site is installed here

public_html/

and the new folder is located

`public_html/example`

copy the htaccess above and save it inside the folder 'example' and this should work.

Hoesaminato le risposte qui un certonumero di volteperchémi sonoimbattutoin unproblema simile.Ho deifilein una sottodirectory chegenererebbero unerrore 404 quando hoprovato ad accedervi.Tutta la roba .htaccessnon è riuscita a risolverlo,come dice Kirsten Douglas,Wordpressfagiàil lavoro.

Lamia soluzione

Hotrovato questo articolo dopo aver controllato l'errore_log sul server.Stavo ricevendo unmessaggio sull'uid sbagliatopergli script.Ho anchenotato cheil 404non veniva lanciato a causa delfile,maperchéil servernonpotevafornire unfile 500.html,cioè ho avuto unerrore 500.

È venutofuori che avevo creatofile come roote dovevo cambiare laproprietà alproprietario deifile web.

Spero che questo aiuti altri che hanno avuto lo stessoproblema!

I've looked at the responses here a number of times as I'd run into a similar problem. I have files in a subdirectory that would throw a 404 error when I tried to access them. All the .htaccess stuff failed to rectify it, as Kirsten Douglas says, Wordpress does the job already.

My solution

I found this article after checking the error_log on the server. I was getting a message about wrong uid for scripts. I also noticed that the 404 wasn't being thrown because of the file, but because the server couldn't serve up a 500.html file i.e. I had a 500 error.

Turns out I'd created files as root, and needed to change ownership to the webfiles owner.

I hope this helps others who've had the same issue!

Dovrestiesserein grado di aggiungere semplicemente una direttiva RewriteCond che assicurerà che le regole di WordPress venganoignorateper le richieste all'interno dellatua sottocartella.

 RewriteCond %{REQUEST_URI} !^/mysubdirectory
# rest of WordPress rewrite rules
 

Tuttavia,dici che anche con no WordPress .htaccess stai riscontrandoilproblema?Qual èil contenuto dellatua sottodirectory .htaccess?

You should be able to just add a RewriteCond directive that will make sure the WordPress rules are ignored for requests inside your subfolder.

RewriteCond %{REQUEST_URI} !^/mysubdirectory
# rest of WordPress rewrite rules

However, you say that even with no WordPress .htaccess you're experiencing the problem? What's the contents of your subdirectory .htaccess?