4

better alternatives like Apache Virtualhosts or something. If you have access to the server-config, then you can use the Alias directive in the vHost to route all requests for /content/images to /wp-content/images. For example: Alias "/content/images/" "/wp-content/images" Now, a request for /content/images/example.jpg would be sent to /wp-content/images/...


2

Found the solution through .htaccess Never sure if it's the best, but it works: RewriteRule ^([_0-9a-zA-Z-]+/)?content/(.*) /wp-content/$2 [QSA,L]


1

I expect www.filmstore.sandwiches.org to go to sandwiches.org, ... This does not work, but sends me to filmstore.net, which I think is the default behaviour for multiple cPanel domains. Ah, but the "problem" here is that the www.filmstore subdomain maps to the /filmstore subdirectory off the main domains document root (as stated in comments) - this ...


1

RewriteCond %{REQUEST_FILENAME} !^/PhP/?$ RewriteCond %{REQUEST_FILENAME} !^/forms/?$ RewriteCond %{REQUEST_URI} !^/PhP/?$ RewriteCond %{REQUEST_URI} !^/forms/?$ You don't need to check against both REQUEST_FILENAME and REQUEST_URI - you're just repeating the same check. It's easier to use REQUEST_URI (the URL-path) in this instance. The ...


1

It sounds like you may have put the directives in the wrong place in your .htaccess file. The HTTP to HTTPS redirect needs to go near the top, before any other rewrites. The nature of your URLs suggest you are using a front-controller type pattern and rewriting requests to a common script. However, the "homepage" does not need to be rewritten (since mod_dir ...


1

It would seem "the problem" is in your PHP code, not .htaccess as you seem to suggest. RewriteRule ^(.+)$ index.php?page=$1 [QSA,L] All requests are rewritten to index.php (your "front-controller") which then routes your URLs. It is this PHP script that determines whether /login or /login/asdasdasd, etc. resolve to a valid page on your site. This has ...


Only top voted, non community-wiki answers of a minimum length are eligible