Mask My Domain Name - wordpress

I'm not sure if this is possible or what, I just thought about it.
I have a page in my site www.mysite.com/thispage
I want to change the whole URL of that page.
www.mysite.com/thispage to www.thispage.com without transfering and configuring another set of files and databases.. My site is in wordpress. Is this possible?

Sure - depending on your hosting settings. You can buy the domain name "thispage.com" and then ask your hosting company to set it up to be hosted in the folder "thispage".
Just a heads up - usually hosting companies charge more to host a domain name like this (or host multiple domain names).
Then you'll need to edit the settings within Wordpress to reflect the new domain name (under SETTINGS).

Related

pointing domain to wildcard sub sub domain

I have a multisite wordpress install at plataforma.vendamais.pt
And I have a wildcard for *.plataforma
So all new sites created have this url:
client01.plataforma.vendamais.pt
client02.plataforma.vendamais.pt
and so on.
I need to connect my client's domains to the correspondent website, so the url client01.plataforma.vendamais.pt wont be visible.
As a real case, I have a client's website here:
www.tancredoferrari.plataforma.vendamais.pt/
I need to have his domain tancredoferrari.pt pointing to that address, so his clients will navigate using tancredoferrati.pt and wont see any of the www.tancredoferrari.plataforma.vendamais.pt url.
Is it possible?
There's 2 options here:
Option 1
An CNAME record on the live domain's DNS should be sufficient to do this - so long as you're happy that the resource requests (images, scripts, styles and so forth) behind the scenes are going to the staging domain URLS (client02.plataforma.vendamais.pt and so forth).
Option 2
Check out the wordpress plugin WordPress MU Domain Mapping. With that you can map the site to multiple domains (and set the primary), which is a better approach.

Putting domain name for wordpress instead of Public domain given by in aws-ec2

I signed-up in AWS(Amazon Web server) for my Wordpress site. I also installed wordpress through AWS-ec2. I followed the steps inside AWs-ec2 documentation like LAMP and others needed.As I go through inside AWS-EC2 environment, I launched an instance where i can work for my Wordpress. Having an instance creates a default public domain name for my wordpress (http://ec2-xxx-xx-xxx-xx.us-west-2.compute.amazonaws.com/).
Now, my problem is I want to make our own domain name like example.com as our wordpress site instead of default domain name given by AWS-ec2. and, what are other requirements or tools needed to deploy it? We bought our domain name in GoDaddy.
Your answers will be highly appreciated.Thank you.
DNS
You need to start with setting up DNS. To do this you can use the service provided by Godaddy or use Route53 in amazon. You will set up records to point to your instance.
Apache
If you are using Virtualhosts, you will need to set up your Virtualhost to respond to the new domain name. If you are not using virtual hosting, it will return the same site regardless of which domain you used.
Wordpress
Wordpress does save the domain you installed it with in the settings. If you change the domain these settings may cause some issues. If you can't get into the Admin UI to fix this, update wp_options table in mysql.

Configure Drupal 7 using Domain Access module

I want to configure a Drupal 7 site using a domain and two subdomains with a single database.
domain.com
sub1.domain.com
sub2.domain.com
I am using Domain Access module for sharing content on these subdomains. I want to share some content and to be able to modify some content on each subdomain. The modified content must be viewed only on its subdomain (for example, a different image should appear on each subdomain).
The question is:
How can I share content between subdomains and also differentiate some content?
I tried different approaches, I modified the user's permissions and it is still not solving my problem.
I published a Basic Page on a subdomain and I can access this page from every subdomain, even if I unchecked the option "Send to all affiliates"
If I change the content from a page published on sub1.domain.com, that content appears modified everywhere
If I create a user or admin for a subdomain, he is able to login everywhere and I do not want that
Since you already can publishing in all domains and those changes are visible in all domains, I guess that you have the domains already well configured. This is, all domains pointing to the same Drupal project and using the same database.
So, you have three different questions:
DIFFERENTIATE THE CONTENT FROM EACH DOMAIN:
Assuming that you have the domains well configured, and the domain access module is installed correctly, you can publish to a specific domain by selecting which domain to publish the Basic Page, a domain access option now available.
(Be sure to test that with an user without permissions to see content from all domain - like the administrator).
CHANGE CONTENT FROM A DOMAIN AND AFFECT ONLY THAT DOMAIN:
If the content was published only to a specific Domain it should change only on that specific domain. The trick here is to have a different Theme for each Domain and make the change on the Theme corresponding to the subdomain you want to change.
USERS CAN ACCESS ANY SUBDOMAIN:
To control this you have to assign a domain to each user, go to admin/user and there under the AFFILIATE EDITOR OPTIONS tab, you can assign domains to users. (user's registered before the Domain Access module was installed doesn't have an associated domain).

Wordpress Multisite: Mixing IPs, domains and URL Proxies

Our company is trying to transition to WordPress Multisite but we have several issues working against us at the moment. We host WP outside our server environment (we use Amazon for our WP sites) so we actually have to use an URL proxy to our Amazon servers. The other issue is that we needed to install Multisite in the root of the folder so the domain is http://100.10.20.30/foldername but we can't proxy that to http://www.domain.com/foldername because that is a live site that we're not moving to WP any time soon. So, of course, the problem we're running in to is that the IP is showing up not only in the source code but in Google now as well (which we don't want).
Does anyone know of anything we can do to keep the IP out of the source code/Google? I was thinking about rewrite rules in the htaccess file but didn't want to do anything until I had some better ideas.
Also, I can't use the domain mapping plugin that everyone seems to suggest for this type of issue because our sites aren't hosted in the root of our server (a prerequisite for the plugin).
So to break it down, this is what we need:
Multisite Parent Blog <-- This has to be the IP address
Multisite child blogs <-- Domain name but when we set the actual proxied domain name in the settings we get a 404 error because it's not looking in the right place. It's looking for an actual folder on our internal servers.
Thanks!
Found the solution myself. Posted below:
In the Multisite dashboard, click on "All Sites" then administer the specific site.
Under the "Path" field, you'll need to deselect the "Update siteurl and home as well."
Save changes.
Click on "Settings" tab.
Change the URL in the following fields: "SiteURL" and "Home"
Save changes.
When all is said and done, the IP is showing in the "Info" tab but it changes the URL in the source code to your domain.

View a site without a domain WITHOUT updating hosts file?

I have a few sites I developed that I need to show my client for review. These are all redesigns of live sites, so they've had me upload them to their new hosting server, which is currently accessible via IP address because the domains are currently in use by the live sites.
I've set each site up as add-on domains in cpanel, and they all live in directories off the root, like 192.0.2.3/site1.example (for example).
However, these are Wordpress sites, and the database references the actual domain name (site1.example), so that it will be all set for launch when we update the DNS to point to this server. That means you can't actually see the site at that domain unless you update your hosts file. But there are lots of non-technical people that need to review the site, and updating their hosts file just isn't an option.
I'd rather not have to do a search and replace on the database to change the domain to 192.0.2.3/site1.example temporarily, just so they can view it. Because when we're ready for launch, I'll just have to do another search and replace to switch it back to the real URL. But it seems like that's my only option.
Is that correct, or is there another way they can view the site without me having to update all the URLs in the database?
The best solution here is to search and replace the URL just as you said

Resources