Inside of your config you have the following: <Directory /> Options FollowSymLinks AllowOverride None </Directory> You should change it to the following: <Directory /> Options FollowSymLinks AllowOverride All </Directory> The AllowOverride directive is what allows the .htaccess file to be read. If you still have trouble, make sure you change this in the <Directory “/var/www/html”> … Read more
I did not test this, but this should do what you want. Put the following in your functions.php: add_filter(‘rewrite_rules_array’, ‘new_category_name_rewrite_rule’); function new_category_name_rewrite_rule($rules) { $new_rules = array(); $categories = get_categories(); foreach ($categories as $category) { $cat_name = preg_replace(‘#\s+#’, ‘-‘, $category->name); $new_rules[“https://wordpress.stackexchange.com/”.$category->slug.”https://wordpress.stackexchange.com/”] = “https://wordpress.stackexchange.com/”.urlencode($cat_name).”https://wordpress.stackexchange.com/”; } return $new_rules + $rules; }
This should cover everything: function wpa_rewite_translate(){ global $wp_rewrite; $wp_rewrite->pagination_base=”pagina”; $wp_rewrite->author_base=”autor”; $wp_rewrite->comments_base=”comentarios”; $wp_rewrite->feed_base=”alimentar”; $wp_rewrite->search_base=”busqueda”; $wp_rewrite->set_category_base( ‘categoria/’ ); $wp_rewrite->set_tag_base( ‘etiqueta/’ ); } add_action( ‘init’, ‘wpa_rewite_translate’ ); Feel free to laugh at my translations, haha. Also, to flush rewrite rules when your theme is activated, add this: function wpa_flush_rewite(){ flush_rewrite_rules(); } add_action( ‘after_switch_theme’, ‘wpa_flush_rewite’ );
Judging from other threads, here are the two most common causes of this problem on freshly built servers: .htaccess override is disabled by apache2.conf Apache mod_rewrite module isn’t enabled. In the file /etc/apache2/apache2.conf: <Directory /var/www/> AllowOverride All </Directory> “AllowOverride” is the switch that tells Apache whether to listen to .htaccess files or not. WordPress relies … Read more
In my experience you don’t need to mess with .htaccess with a WordPress site. Just set the General Settings -> “WordPress Address” and “Site Address” to the preferred version (www or non www) and WordPress takes care of the redirection for you.
You can add a RewriteRule to your .htaccess to instruct mod_rewrite to stop processing any URI that begins with Staff/ or resolves to Staff: # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ – [L] RewriteRule ^/?Staff(/|$) – [END,NC] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> In effect, this … Read more
You can actually change them in Settings -> Permalinks and it will change the link that generated for the post. And if you still be unhappy with result you can remove WordPress rewrite rules for dates with date_rewrite_rules filter. UPDATE: In this case, you can use post_rewrite_rules to keep the date to post rule working … Read more
If your permalink structure is /%postname%/ with a trailing slash, you need to pass the hash like this: /faqs/#b with the trailing slash.
You can use add_rewrite_rule in WordPress to capture the query args or add_rewrite_endpoint. If you really just want to redirect based on certain rules then template_redirect can be a good place to use a header redirect.
This was covered extensively in Steps to Take to Hide the Fact a Site is Using WordPress. The answer in that question covered renaming the wp-content and the plugin directory. If you prefer rewriting those directories you can use these functions found in the Roots WordPress theme to rewrite the directories relative to your sites … Read more