This is outside the realm of WordPress. I’ll give you a basic answer that should help you figure out what you need to do. The general idea is you will point your new domain names to point to your web server’s IP address. Then your web server will see which domain name is being called … Read more
This is definitely not related to a “missing” .htaccess file. WordPress will create an .htaccess file if needed (for permalinks) and re-create a deleted file if needed. If you have deleted all previous data as you state and installed WordPress several times, you likely have a very messy DB and/or file situation going on. Why … Read more
Did you add the query vars via the query_vars-hook in addition to the defintion of the rewrite rule in the init-hook? add_filter( ‘query_vars’, ‘my_add_query_var_function’ ); function my_add_query_var_function( $vars ) { $vars[] = ‘a’; $vars[] = ‘cat’; $vars[] = ‘where’; return $vars; }
This question seems simple, but if you use some of the basic features of WordPress (such as categories), then the solution can become very complex and difficult. My suggestion below assumes that you use a very simple setup. First, I will assume that when you convert your content to WordPress that what you call [pagename] … Read more
With some help (also asked on SO, as this wasn’t a strict WP question), and some testing, the following ended up working for me (added a slash just before the $ sign): RewriteRule ^galleries/(.*)/$ /portfolio/$1 [R=301,NC,L] As the galleries are actual directories, not files, they have a slash at the end: http://subdomain.example.com/galleries/headshots/ Here —^
Try replacing your line with this RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^([^\.]+)$ $1.php [NC,L]
Turns out the file was the problem, as @TheDeadMedic suspected. The permissions were 640. After changing them to 644, the problem was solved! Thanks for the help.
I would suggest an alternative route: the rewrite API – did you know it supports external URLs*? function wpse_199898_add_htaccess_rule() { // No need for the caret “starts with”, WP will add it add_rewrite_rule( ‘article/([/_0-9a-zA-Z-]+)$’, ‘http://www.domain.tld/?id=$1 [R=301,L,NC]’ ); } add_action( ‘init’, ‘wpse_199898_add_htaccess_rule’ ); *Almost. We just need a fix for WP’s quirky path prefixing: function wpse_199898_fix_htaccess_rule( … Read more
The way the wordpress htaccess works is that first it looks if there is a file matching the request location, in which case it is being “run”, otherwise the wordpress handles the URl. Basically you don’t even “execute” your subdirectory’s htaccess unless you access an existing fie there. What you should do is to add … Read more
I was having a similar problem recently. It turned out it was due to a code injection in the /wp-includes/nav-menus.php file. There was a Base64 malware code injected that was causing my .htacess file to chmod itself to 444. Something called some kind of darkleech malware. See this link for more, maybe it’s what’s happening … Read more