Sounds like to that the Allow Override directive is still set to NONE for your VHOST By default this is disabled, so even if you enable mod_rewrite via sudo a2enmod rewrite your .htaccess will be ignored. You’ll want to login to your server (via Terminal / shell) and then … sudo nano /etc/apache2/sites-available/default look through … Read more
As @MarkKaplun suggests, it would be preferable to store this non-WordPress file in a different area of the filesystem altogether and rewrite the URL in .htaccess. Instead of mimicking the WordPress URL in the physical directory structure – which will likely only cause you (more) problems (not least that you would need to override the … Read more
To fully enable permalinks, you also need to ensure that .htaccess is also created. To do that, you need to set an option and flush the rules with a Boolean. global $wp_rewrite; //Write the rule $wp_rewrite->set_permalink_structure(‘/%postname%/’); //Set the option update_option( “rewrite_rules”, FALSE ); //Flush the rules and tell it to write htaccess $wp_rewrite->flush_rules( true ); … Read more
You can skip the first Part of your .htaccess, just use the standard WordPress configuration. The main problem is, you need to create a new index.php in the root directory of your webspace, containing the following: <?php /** * Front to the WordPress application. This file doesn’t do anything, but loads * wp-blog-header.php which does … Read more
WordPress actually 301’s these out of the box! It handles a number of basic structures by default, so unless you’re switching to or from a very unique configuration (e.g. /blog/%postname%/), it will probably work.
There is a plugin for that called WP No Category Base. As the name suggests this plugin will completely remove the mandatory ‘Category Base’ from your category permalinks ( e.g. myblog.com/category/my-category/ to myblog.com/my-category/ ). https://wordpress.org/plugins/wp-no-category-base/
Your best option is to register neighborhoods as a custom taxonomy and use that instead of categories. In your theme’s functions.php file, you just need to add: function neighborhoods_init() { // create a new taxonomy register_taxonomy( ‘neighborhoods’, ‘post’, array( ‘label’ => __( ‘Neighborhoods’ ), ‘hierarchical’ => true ) ); } add_action( ‘init’, ‘neighborhoods_init’ ); Next, … Read more
Edit your existing code to exclude the index.php from redirecting like this: RewriteCond %{HTTPS} on RewriteCond %{REQUEST_URI} !^/info/ RewriteCond %{REQUEST_URI} !^/index\.php$ RewriteRule (.*) http://%{HTTP_HOST}%{REQUEST_URI} [R=301,QSA,L] For an explanation, check the answer to this question at Stackoverflow: Issue with .htaccess redirecting all pages to HTTPS except one .
If you installed WordPress Multisite starting with version 3.0 to 3.4.2, you’ve got the correct .htaccess file contents. However, if you started with a newer version (3.5 or higher)—and I’m assuming you did, if you’ve just installed WordPress Multisite recently—your .htaccess file should look like this: RewriteEngine On RewriteBase / RewriteRule ^index\.php$ – [L] # … Read more
The default .htaccess-file will already support the behaviour you want; # 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 The magic is in the lines that start with RewriteCond. They instruct Apache to apply the rule RewriteRule … Read more