WordPress has a good writeup about this at Giving_WordPress_Its_Own_Directory. Many people want WordPress to power their site’s root (e.g. http://example.com) but they don’t want all of the WordPress files cluttering up their root directory. WordPress allows you to install it into a subdirectory, but have your blog exist in the site root. You could also … Read more
Fixed it by adding following code. (just update for others to use it) <IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{QUERY_STRING} . RewriteCond %{QUERY_STRING} !^(s|p)=.* RewriteCond %{REQUEST_URI} !.*wp-admin.* RewriteRule .* http://www.mydoman.com%{REQUEST_URI}? [R=301,L] </IfModule>
No, it will not work. You pretty much will disable php to work on your site admin. On wp-admin there are files being executed when entering the admin side of the site.
First back up your database. It is always wise to do that before doing anything. Now download and install Velvet Blues Update URLs plugin. Enter your old URL (like http://example.se/www.example.se) and new URL (like http://www.example.com) and select all options and click Update. Also update your permalinks afterward. This should sort your problem
Try memory_limit = 128M in php.ini. Your syntax may be wrong. You can run a function called phpinfo to see what kind of memory allocation you really have. Make a plain text file and call it phpinfo.php and put just this line in it: <?php phpinfo(); ?> then put the file in the root of … Read more
Depending on what server setup you have (operating system, http server & control panel – if you have one), the main way to go would be to have separate DNS zones for each domain (with an A record for the domain name, then MX records, NS if you want the nameservers to be linked to … Read more
Finally fixed this errow after browsing for a couple of hours and trying many options. In this block in your Apache httpd.conf file, (located in my CentOS instance at $ sudo vi /etc/httpd/conf/httpd.conf) # # AllowOverride controls what directives may be placed in .htaccess files. # It can be “All”, “None”, or any combination of … Read more
.htaccess rules are interpreted and applied on every request, they don’t linger on server level and changes apply immediately. However if you had had 301 redirect set up then it can be cached by browser very aggressively. I do not observe redirect you are describing, so that is likely the case. Note that your home … Read more
Why do you want to use .htaccess to do this? Why not just move to the new URL? Alternatives include adding something similar to one of the following to your .htaccess file (note the 301 “permanently moved” code being sent back to the browser in both cases): RedirectMatch 301 /e /wp or <IfModule mod_rewrite.c> RewriteEngine … Read more
It is the way the .htaccess wordpress generatea instructs apache to work on the wordpress directories The relevant parts from the default .htaccess RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] The first line will cause the rewrite engine to bail out if there is a file with the same name as the … Read more