Installing multiple different instances of wordpress on the same website - wordpress

I currently have a website up and running that is my freelancing website. What I wanted to do was create a testing subdirectory on the website.
So for example my site would be:
website.com
I want the testing site to be: website.com/test
I need this test to be private and require a password to view, as well as be a different installation of wordpress so I can manipulate it without editing my main website. Is this possible? Currently I have created a test directory from the cPanel that requires a password but it just brings me to a 404 not found page.
I would also like to create more, public, instances that I can use as a portfolio until I get more real clients. So for example I would like to have my site be: website.com/themeOne
Is any of this possible, or am I out of luck? Please let me know I would greatly appreciate any help. Anything I found found online thus far has either not been relevant or has not worked.

You can achieve this by setting up a wordpress multisite installation. I currently use this to host all my clients.
Will work like this.. Main site is website.com
Depending on how long you have had that site set up will determine whether your multisite install will be a subdirectory or a subdomain. If you have had your main site for a while it will be subdomains. ie. xyz.website.com
You will have to set up a wild card subdomain on your server though...so keep that in mind.
Here is the documentation on setting up a wordpress multisite
https://premium.wpmudev.org/blog/ultimate-guide-multisite/

You can install as many WordPress instances as you like in subfolders example.com/test/ or subdomains test.example.com in one hosting account; see http://codex.wordpress.org/Installing_Multiple_Blogs. (You are, of course, limited if your host does not support subdomains. And you may find lots of sites with lots of traffic will slow your whole hosting account.)
For these separate WordPress installs, you can use the same database; simply give each WordPress install a different database table prefix in wp-config.php. https://codex.wordpress.org/Editing_wp-config.php Or, give them all the installs a totally different databases, only limited by your hosting account.
To control access to a WordPress site, there is no need for access control in .htaccess or via Cpanel; use any one of a number of plugins that allow you to restrict access to anyone not logged into WordPress. See https://wordpress.org/plugins/search.php?type=term&q=password
And you can still control the user's role when they are logged into the site with one of those plugins, i.e. editor, administrator, etc., from within WordPress. That's because you want to give a client a Subscriber user level so they can simply login and view the site, rather than Administrator, who can see posts, plugins, etc. See https://codex.wordpress.org/Roles_and_Capabilities
There is no need for WordPress Multisite, unless you want to go that way: see https://codex.wordpress.org/Create_A_Network But be aware that MS requires more server and DNS configurations if you want to use Domain Mapping: https://wordpress.org/plugins/wordpress-mu-domain-mapping/

Related

WordPress multi-site in a subfolder on host

I'm wondering about a WordPress multi-site installation and nothing I've come across has clearly laid this out for me. I'm hoping to get a little more clarification on what exactly will happen in my WordPress/Server instance if I set up a multi-site.
I've currently got my actual site as a single instance Wordpress install at the root of my domain. I'd like to keep it that way.
I've set up a sub-folder on my site called "client-login" and it has it's own WordPress install. The idea is to make this WordPress instance a multi-site one. With the intent being that I can have multiple sites in there and give access to them as needed.
So far it all is making sense but when I go to actually complete the multi-site install it says the server address will be my domain at root level. It doesn't say domain/client-login.
My question is if I turn on the multisite will it take over the root of my domain and include my "real" site as part of it?
lets consider,
you have a main wordpress domain at public_html/
you have created a subfolder in host like public_html/client-login for another wordpress instance
these two will behave as a separate sites.
The wordpress multisite will work inside the public_html/mainsite not outside of it, and it wont affect the client-login subfolder.

Client transferred/changed domain names...how do I salvage the WordPress site

So I built this client a WordPress site and after if was completed and paid for he decided he didn't like his domain name. So he logged into HostGator and then bought/transferred to a new domain.
Then a day later he calls and wonders why his page isn't loading. I'm able to go into the FTP and save all the wp-content and every file that was originally there... My question is how do I get the WordPress site I built onto the new domain name?
I've read all kinds of tutorials about how to export/import but they require the site you're transferring from to be live.. I can't log into the wp-admin portion because it looks like the domain does not exist anymore.
I'm definitely not a back-end guy.. I've build a few sites off line with xamp but i have no idea what I'm doing when it comes to trying to salvage this site. Any help?
WordPress is flexible to handle situations like moving to another server. First back up your WordPress directory, images, plugins, and other files on your site as well as the database. The detailed steps on how to do it is well documented in the website https://codex.wordpress.org/Moving_WordPress.

Transferring Development Wordpress To Live Wordpress Without Issues

I am looking for a way to port one wordpress install across to another site.
For example, say I have:
development.example.com
example.com
I want to transfer everything from development.example.com to example.com
Transferring the domain name is always a pain for me and I am hoping someone can help me.
After transferring to a new domain and hosting, I normally have to go into the wordpress database into the options table and change two fields.
siteurl and home (I change these to my new domain name)
I can then run example.com/wp-admin and I will be able to login.
The above works fine on the basic setup, but the issue I am having is that when you have lots of different plugins all adding options and other fields to the database it turns into a bit of a nightmare.
I normally have to remove the plugin folder and reinstall them one by one, and then use a search and replace plugin to change all the options from.
search: development.example.com
replace: example.com
This all seems like a very long winded process considering when I build with codeigniter you only have to change the url in one place config.php and then just run a
cp -rf development.example.com/* example.com
Could someone advise me on how they normally run a transfer with wordpress where all this search replace and login issues aren’t needed.
You have all the details on the When Your Domain Name or URLs Change section in the Codex.
For replacing links, the Velvet Blues Update URLs plugin works well for me.

Externally managed htaccess-protected members area in WordPress with url rewriting?

I am considering converting a client project from a large number of hand-built web pages to a WordPress install. However, this client has a free area (site.com/) and a members area (site.com/members/). The members area is standard Apache .htaccess / htpasswd authentication. The authentication is handled by legacy billing software which we don't want to change at this time.
One thought is to put up two separate WordPress installs (or perhaps a MultiSite install?). One install sits on the domain root and the other sits at /members/. Thus neither install has to know anything about being password-protected. So long as the outer install cannot generate a url which includes /members/, I'm pretty sure the url-rewrite engines won't interfere with each other.
Another thought is to try to do everything in a single install, and expect the server to force authentication on any url that maps to /members/. But intuitively it feels like I'd have to go to a custom taxonomy to get "free area" category hierarchies separate from "member area" hierarchies.
Any WordPress plugins which I've found, and any related discussions, assume that the members are managed via WordPress. That's the issue: the members area is simply protected via old-school htaccess authentication.
I'm not sure that the WordPress url-rewrite mechanism would trigger the authentication part as intended, given that WordPress is sitting at the domain root, outside the members area.
On the other hand, running it as two WordPress installs, one inside the other, might be just what I need. Anyone have perspective on this? Anyone know of problems running WordPress "inside" WordPress as described?
Yes. Given my restrictions, a double install is the most reasonable solution.

Drupal installation and domain naming strategy?

I have a my main site, called "mysite.com" (for arguments sake). On this site, you will find my blog and everything I do. But I am starting another site that I want to run on my domain. However:
The other site must have it's down domain name: newsite.com
If people go to mysite.com/newsite it must redirec to newsite.com
If people go to newsite.com, it must show the content of what they would see if they had gone to mysite.com/newsite in the past
So basically, I want a "page" or actually a whole section ( mysite.com/newsite/* ) to appear as newsite.com in the browser.
Why?
I want both sites to run off one drupal installation
I want both sites to look basically the same
However, keep in mind that I don't want to use a multi-drupal solution. i.e. a module that allows for more than one copy of drupal to run off 1 installation.
http://drupal.org/project/domain allows you to configure various things based on the domain, for example accessible nodes.
You can probably do the redirect with a Rewrite Rule, outside of Drupal or write a simple module that does that.
Sounds simple to do. Just install the second site using a regular multi-site installation. (Google "drupal multi-site instructions"). Then install the Path redirect module and create the external redirect to the new domain. http://drupal.org/project/path_redirect

Resources