Well if I had thought about how much work with was going to be before writing it, you wouldn’t be able to get me points right now. 🙂 Needless to say, it’s rather involved (though I don’t think it really should have to be, but it is what it is.) First off, you can’t (easily) … Read more
use this https://wordpress.org/plugins/wp-htaccess-editor/, if you are not willing to use any plugin, understand the code and implement in functions.php or your own custom plugin. cheers.
I believe you should investigate using WordPress Multi Site. It will allow you to update and maintain a single site and database that will neatly store each subdomain’s specific info. Using DNS settings you will also be able to set up each subdomain to be seen as a separate entitity in Google’s eyes. Take a … Read more
Ok here is a test working solution: <?php /* Plugin Name: wpse26719 Plugin URI: http://en.bainternet.info Description: Need to make a php file inside theme accessible via url Version: 1.0 Author: Bainternet Author URI: http://en.bainternet.info */ // Register a URL that will set this variable to true add_action(‘generate_rewrite_rules’, ‘wpse26719_rw’); function wpse26719_rw($wp_rewrite) { $newrules = array(); $new_rules[‘^adserver.js.php$’] … Read more
The old site was based on php and there are lot of pages which are indexed, since we are keeping same urls in new wp sites but without .php extension at the end… Assuming your “old site” .php documents no longer exist (they shouldn’t) then your current rule block to remove the .php extension would … Read more
Do you have the line Options +FollowSymlinks defined in the .htaccess file before your rewrite rules? If so, remove it. If not, add it.
Problem 1 Your hook ci_add_rules() will still run when you flush rules, so remove it first (and avoid “unsetting” non_wp_rules, you’ll break other plugins that make use of it). function ci_remove_rules() { remove_action( ‘generate_rewrite_rules’, ‘ci_add_rules’ ); $GLOBALS[‘wp_rewrite’]->flush_rules(); } Problem 2 Pretty sure you want: plugin_dir_url( ‘proxy.php’, __FILE__ ) ..instead of: plugin_dir_path( __FILE__ ) . ‘proxy.php
You can inject a made-up referer into WordPress’ HTTP request by filtering pre_http_request. All you need is a simple class like this (untested!): class FakeWpReferer { private $referer; private $url; private $is_regex; /** * @param string $referer * @param string $url URL to fake the referer for. * @param bool $is_regex Is $url a regular … Read more
Assuming you have already changed the permalinks structure as @RickHellewell suggests, then you can do something like the following near the top of your .htaccess file (before the existing WP front-controller) to redirect the old URLs (with the stated format) in order to preserve SEO. RewriteRule ^\d{4}/\d\d/([a-z-]+\.html)$ /$1 [R=301,L]
Adding junk doesn’t do anything either. That suggests your .htaccess file is not being processed at all. You need to set AllowOverride All in the appropriate <Directory> container in the main server config (or <VirtualHost> container) to enable the parsing of per-directory .htaccess files (to allow .htaccess directives to override the server config). The FollowSymLinks … Read more