Skip to main content
Exemplified domain according to recommendation ("example.com"), minor formatting, tags.
Source Link

I have a WordPress instance running on my domain's root.

One WordPress page is located at www.mydomainexample.com/product/. I placed some static HTML files in a path below that so that visitors can go to www.mydomainexample.com/product/documentation/ where an index.htmlindex.html and other htmlHTML files live.

Now I can access the static HTML files just fine, but when going to the WordPress site (i.e. www.mydomainexample.com/product/), I get a 403 Forbidden error.

How can I make the static HTML files available at that URL while retaining access to the WordPress page?

Here is my .htaccess.htaccess file (I think it is the unmodified default)

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

Sorry if this question has been answered already, but I have only found questions about problems with displaying the static content rather than the WordPress content.

I have a WordPress instance running on my domain's root.

One WordPress page is located at www.mydomain.com/product/. I placed some static HTML files in a path below that so that visitors can go to www.mydomain.com/product/documentation/ where an index.html and other html files live.

Now I can access the static HTML files just fine, but when going to the WordPress site (i.e. www.mydomain.com/product/), I get a 403 Forbidden error.

How can I make the static HTML files available at that URL while retaining access to the WordPress page?

Here is my .htaccess file (I think it is the unmodified default)

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

Sorry if this question has been answered already, but I have only found questions about problems with displaying the static content rather than the WordPress content.

I have a WordPress instance running on my domain's root.

One WordPress page is located at www.example.com/product/. I placed some static HTML files in a path below that so that visitors can go to www.example.com/product/documentation/ where an index.html and other HTML files live.

Now I can access the static HTML files just fine, but when going to the WordPress site (i.e. www.example.com/product/), I get a 403 Forbidden error.

How can I make the static HTML files available at that URL while retaining access to the WordPress page?

Here is my .htaccess file (I think it is the unmodified default)

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

Sorry if this question has been answered already, but I have only found questions about problems with displaying the static content rather than the WordPress content.

Tweeted twitter.com/StackWordPress/status/898655149782179840
Added .htaccess file
Source Link

I have a WordPress instance running on my domain's root.

One WordPress page is located at www.mydomain.com/product/. I placed some static HTML files in a path below that so that visitors can go to www.mydomain.com/product/documentation/ where an index.html and other html files live.

Now I can access the static HTML files just fine, but when going to the WordPress site (i.e. www.mydomain.com/product/), I get a 403 Forbidden error.

How can I make the static HTML files available at that URL while retaining access to the WordPress page?

Here is my .htaccess file (I think it is the unmodified default)

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

Sorry if this question has been answered already, but I have only found questions about problems with displaying the static content rather than the WordPress content.

I have a WordPress instance running on my domain's root.

One WordPress page is located at www.mydomain.com/product/. I placed some static HTML files in a path below that so that visitors can go to www.mydomain.com/product/documentation/ where an index.html and other html files live.

Now I can access the static HTML files just fine, but when going to the WordPress site (i.e. www.mydomain.com/product/), I get a 403 Forbidden error.

How can I make the static HTML files available at that URL while retaining access to the WordPress page?

Sorry if this question has been answered already, but I have only found questions about problems with displaying the static content rather than the WordPress content.

I have a WordPress instance running on my domain's root.

One WordPress page is located at www.mydomain.com/product/. I placed some static HTML files in a path below that so that visitors can go to www.mydomain.com/product/documentation/ where an index.html and other html files live.

Now I can access the static HTML files just fine, but when going to the WordPress site (i.e. www.mydomain.com/product/), I get a 403 Forbidden error.

How can I make the static HTML files available at that URL while retaining access to the WordPress page?

Here is my .htaccess file (I think it is the unmodified default)

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

Sorry if this question has been answered already, but I have only found questions about problems with displaying the static content rather than the WordPress content.

added 108 characters in body; edited title
Source Link

Place static HTML files in path below wordpressWordPress page

I have a WordPress instance running on my domain's root.

One WordPress page is located at www.mydomain.com/product/. I placed some static HTML files in a path below that so that visitors can go to www.mydomain.com/product/documentation/ where an index.html and other html files live.

Now I can access the static HTML files just fine, but when going to the WordPress site (i.e. www.mydomain.com/product/), I get a 403 Forbidden error.

How can I make the static HTML files available at that URL while retaining access to the WordPress page?

Sorry if this question has been answered already, but I have only found questions about problems with displaying the static content rather than the WordPress content.

Place static HTML files in path below wordpress page

I have a WordPress instance running on my domain's root.

One WordPress page is located at www.mydomain.com/product/. I placed some static HTML files in a path below that so that visitors can go to www.mydomain.com/product/documentation/ where an index.html and other html files live.

Now I can access the static HTML files just fine, but when going to the WordPress site (i.e. www.mydomain.com/product/), I get a 403 Forbidden error.

Sorry if this question has been answered already, but I have only found questions about problems with displaying the static content rather than the WordPress content.

Place static HTML files in path below WordPress page

I have a WordPress instance running on my domain's root.

One WordPress page is located at www.mydomain.com/product/. I placed some static HTML files in a path below that so that visitors can go to www.mydomain.com/product/documentation/ where an index.html and other html files live.

Now I can access the static HTML files just fine, but when going to the WordPress site (i.e. www.mydomain.com/product/), I get a 403 Forbidden error.

How can I make the static HTML files available at that URL while retaining access to the WordPress page?

Sorry if this question has been answered already, but I have only found questions about problems with displaying the static content rather than the WordPress content.

Source Link
Loading