This is a late answer but this works for me: Change the RewriteCond to this RewriteCond %{HTTP:X-Forwarded-Proto} !https Should be like this: RewriteEngine On RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteRule ^(.*)$ https://yourdomain.com/$1 [R,L]
Before I give you the CODE, let me explain a few points: Point 1: It’s better if you only allow https links. Mixing http & https for the same content breaks the security added by https. With http, you can never be sure that your visitors are shown the same page you are providing from … Read more
You can delete files per plugin if the server’s PHP user has write permissions. The trick is to delete it immediately on activation. Here is a basic sample code: <?php # -*- coding: utf-8 -*- /** * Plugin Name: Delete .htaccess * Description: Deletes the .htaccess file on activation, deactivates itself then. * Plugin URI: … Read more
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