You don’t have to touch the Apache configuration for this, you can do this all from the WordPress rewrite system. But indeed, your general idea is correct: you should append ?cat=3 (or category_name=blog if you want to be even clearer). Remember that your blog archive can have multiple pages, maybe you want to handle this … Read more
Only way I knowit to do this it’s using this function: /* * Redirects search results from /?s=query to /search/query/, converts %20 to + * @link http://txfx.net/wordpress-plugins/nice-search/ * ======================================= */ function search_redirect() { if (is_search() && strpos($_SERVER[‘REQUEST_URI’], ‘/wp-admin/’) === false && strpos($_SERVER[‘REQUEST_URI’], ‘/find/’) === false) { wp_redirect(home_url(‘/finde/’ . str_replace(array(‘ ‘, ‘%20’), array(‘+’, ‘+’), urlencode(get_query_var(‘s’)))), 301); … Read more
Why does multisite bypass WordPress for wp-content, wp-admin, wp-includes and .php files?
You’ll need to use mod_rewrite (RewriteRule and RewriteCond) directive(s) instead, as opposed to a mod_alias Redirect directive, in order to check the requested Host header. For example, try the following near the top of the .htaccess file, before the # BEGIN WordPress section (the order of directives is important): RewriteCond %{HTTP_HOST} ^foo\.org [NC] RewriteRule ^events$ … Read more
# Only allow access to this directory if they are coming from your domain; excluding you, your server, Google and any other IPs RewriteEngine On RewriteCond %{REMOTE_ADDR} !^(xxx\.xxx\.xxx\.xxx|xxx\.xxx\xxx\.xxx|66\.249\.) RewriteCond %{HTTP_HOST} !^(127\.0\.0\.0|localhost) [NC] RewriteCond %{HTTP_REFERER} !^https?://(.+\.)?yourdomain\.com/ [NC] RewriteRule .* http://yourdomain.com/ [L] That should help, I think
Not sure if I understood you right, but there’s an option when registering the custom post type: register_post_type( ‘your_cpt_name’, array( ‘rewrite’ => array( ‘with_front’ => true ) ) );
RewriteCond %{HTTP_HOST} ^example\.me [NC] RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.example.me/$1 [R,L] You’ve not stated where exactly you are adding these rules in your .htaccess file(s). The order is important. These directives need to go at the top of the .htaccess file, before the WordPress front-controller, otherwise they won’t redirect anything other than static resources. This … Read more
yes, this: https?://yoursite.com doesn’t do anything you want, just make it http://yoursite.com. Next to that, make sure your server actually supports RedirectMatch.
A quick fix could be to change the permissions on your .htaccess file so if you change settings in WordPress, it’ll show you what you need to manually change your .htaccess to since it won’t have direct write access to the file anymore.
For data that’s been cached, the two caches should perform equivalent. In general, most folks will find that WP-Supercache is easier to setup and use from an admin perspective (purging & pre-populating). People cache for two reasons: 1) Improved concurrency at handling many visitors simultaneously. This is only relevant to high-traffic sites. For this, both … Read more