Hot answers tagged domain
7
This is because the URL settings inside WordPress are still pointing to the old WordPress site. In other words, you didn't read the Moving WordPress article in the documentation.
If your WordPress admin pages are still working, you can go to Settings → General, and change the WordPress URL and the Site Address to the correct values.
If your WordPress site ...
5
"example2.com
sub1.example2com"
Actually for subsites off of mapped sites, you want a multi network plugin.
Free - http://wordpress.org/extend/plugins/wp-multi-network/
Paid - http://wpebooks.com/networks/
5
Apparantly this happens with the newer version of domain mapping because sunrise.php itself needs to be updated. To solve it I:
Copy the new sunrise.php file from wp-content/plugins/wordpress-mu-domain-mapping/sunrise.php to wp-content/sunrise.php and you'll be fine.
And it works now.
5
You would just need to use the multisite functionality now in WordPress, see http://codex.wordpress.org/Create_A_Network. Setup the site to use the subdomain install. You would then setup the main blog to be your site, ignoring the posts section for that site. Then setup a new site within the Super Admin menu and set the subdomain for the new site to be ...
5
There's a pretty good step by step on moving WordPress in the Codex. It is what I follow when changing domains.
Moving the files is pretty straight-forward. It is the hard-coded references in the database that are tricky. However, serialized search and replace will take care of all database changes. I've used the Velvet Blues plugin in the past, but ...
4
for reference, see also:
How to use Multiple-Domains in one Multi-Site Installation?
301 Redirects for posts, category, pages from original domain to sub-domain of multisite
Full Domain Mapping with WP3 in Multiuser Mode
4
There are a number of ways to do this,
Install WordPress on new host, export, then import post data (via Dashboard) XML file
Install WordPress on new host, export, then import MySQL database file
Use a back up plugin that allows you to clone your site from host-to-host (1:1)
In both cases 1 and 2, you will need to;
copy your theme file folder to your ...
4
I had a similar issue with another client, entering something like projects/project1 would error as the / would fail validation.
After failing to find an override or filter, instead I found a loophole. If you make projectsproject1, then afterwards edit the site so its url is projects/project1 and save, update the homeurl etc, it works! You may need to make ...
4
I think you're confusing wordpress.org vs wordpress.com. If wordpress.com is what you're looking for, this isn't the place. Per the About page of WPSE,
Don't ask about... WordPress.com support issues
Now, if you're referring to using self hosted WordPress (wordpress.org) with a .edu domain, there are no limitation on domain extensions (afaik) and you ...
4
I utilize the awesome plugin Duplicator to complete this exact procedure on a regular basis.
http://wordpress.org/extend/plugins/duplicator/
The plugin is fully supported and there are great FAQ available here:
http://lifeinthegrid.com/labs/duplicator/
The plugin will create a .zip backup of both your database and files and an installer .php that you ...
3
Potential Issues
Google's Page Speed service does not work with "naked domains". That is, it will not work with just "example.com". The domain name must have a subdomain in front of it, such as "www.example.com".
This is due to a limitation on Google's implementation of the Page Speed service, which requires you to set up a CNAME record in your DNS. This ...
3
If you don't want to redirect your users from example.com to example.wordpress.com, but really want example.com to be new domain name for your WordPress.com blog, you can buy Domain Mapping for $12 per year if you already have your own domain.
3
This question has been discussed several times on the WordPress Hackers email list, I'd recommend Googling something like wp-hackers absolute relative to get an overview of the various lively debates that have taken place over the years.
Personally I use the searchreplacedb2 script whenever I migrate a database between URLs, e.g. from live to ...
3
You will have a few things to consider (later on the answer), I suggest the following steps:
Backup your Files and Database
This is pretty self-explanatory. You are going to do a lot of Data Manipulation, so be sure your original is safe.
Transfer your files
The fastest way to do this is to have a hoster where you can import directories from another ...
3
If you want sections in a subdomain and in subdirectories, use a multi-site installation. See Create a Network and our tag multi-site.
Then you set the the blog and the shop as separate sites, and the portfolio as a custom post type or as a regular page in the main blog.
2
You already get shortlinks of the form ?p=post_id, so http://nerdgap.com/?p=66 points to http://nerdgap.com/great-big-update-plus-giveaway/. You could exploit this by creating a simple redirection from http://g4p.it/{$post_id} to http://nerdgap.com/?p={$post_id}.
You can then integrate this in your editor (the "Get Shortlink" button) and add a <link ...
2
You will have to get a dedicated IP to make things simpler.
It works exactly like the domain mapping plugin, with the exception that you need to create a wildcard A record.
Unlike domain mapping, you can't get around the dedicated IP requirement by parking the domain, as parking will only cover the main 3.domain.com, and not any non existing ...
2
I recommend handling the 301 redirect in your web server rather than in WordPress. mod_rewrite or RedirectMatch will be much more efficient than spinning up WordPress to deliver a Location: header.
<VirtualHost *:80>
ServerName busted-cheap-url.com
# mod_alias
RedirectMatch permanent (.*) http://great-new-url.com$1
# OR mod_rewrite
...
2
You don't need a rewrite rule in .htaccess to add www back in. Remove the rewrite rule, remove all the defines in wp-config and try to login. If that doesn't work, delete permalinks in .htaccess to force them back to default.
After you're in, add the www in Dashboard>>Settings and save. Then reset permalinks.
2
I just did this on a client site. I set up my rules like this:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^(.*)fsdegrees.com [NC]
RewriteRule ^(.*)$ http://www.56degrees.co.uk/$1 [R=301,L]
The first rule checks the incoming domain and verifies that it is the old domain. The second sends a 301 redirect and visitors are sent to the corresponding page on the ...
2
There are some instances of serialized data in the database, notably in things like widget options, that become invalidated if you do a blind search-and-replace without accounting for different string lengths. You might try a tool like this one to do a search and replace that also handles serialized data: ...
2
Yes, i think you can work with 3 different ways.
use multisite and each blog in the network is an subdomain and his categories. Its great for maintenance and an default and also great for capabilities, no problems.
Use an custom pluign on filter pre_get_posts() and list in dependence on the url the categories for this url, only this. Filter the categories ...
2
You could check the contents of the $_SERVER['REQUEST_URI'] array when the site is loaded, by placing the conditional checking logic in your header.php file of your site and then redirect the user to the appropriate language from there.
For example in header.php add:
$incomingUrl = $_SERVER['REQUEST_URI'];
if($incomingUrl == 'mydomain.dk') {
...
2
Most probably, nothing went wrong, you just have to set some things to the new server.
Firstly, there are the home and site urls (to be found in the general settings).
Then, possible absolute links pointing to the old domain have to be adapted.
To change these links, you have to adapt the SQL table.
Update options (this can also be done via the general ...
2
The PHP is loading at the new domain, or else you would see no HTML. The issue seems to be that your WordPress Address (in Settings -> General) is not set for your new domain.
If you have access to the DB, look for the option with the name siteurl in wp_options. The value should be your new domain.
Quick and dirty solution: add this to wp-config.php:
...
2
What I basically did was the following:
Used Domain Mapping plugin
in wp-config.php - Changed
DOMAIN_CURRENT_SITE and NOBLOGREDIRECT to $_SERVER['HTTP_HOST'] as per what @toscho suggested
in wp-config.php - Added:
define('DOMAINMAPPING_ALLOWMULTI', 'yes'); // Allow sites to have multiple domains
define('SUNRISE', 'on'); // Domain mapping plugin ...
2
Its simple..
Export
Just check this page to export your blog data..
http://en.support.wordpress.com/export/
Import
Install a fresh wordpress.. Then import it..
http://en.support.wordpress.com/import/
Please note:
wordpress.com uses the same software downloaded from wordpress.org.. They just using it as multisite..
...
2
First off -- does your server allow overrides in .htaccess files? If not, you need to get that turned on. My server has AllowOverride All set in its config file, which then allows my .htaccess rules to function.
Does alias.com point to the same directory as actual.com? If not, then you need to put a .htaccess file in the alias.com root.
Also, if I ...
1
I think you should try to get it to work in some other way.
It's normal it doesn't work, since the url from the page can't be changed by the .htaccess, because the url is not your permalink but the new domain.
Why not set the name server of the new url, to the old one.
so they go to the same page.
Then change your .htaccess, accordingly to change to ...
Only top voted, non community-wiki answers of a minimum length are eligible
