I've a wordpress website running on "example/"
I want to run another wordpress installation within that as "example/example2/"
Currently, after creating a folder named "example2", the home page loads fine but the links show up as 404. for example: "example/example2/category/category1" redirects to the parent setup's wordpress 404 page(which makes sense from the POV of the parent setup). How can I make the 2 setups exclusive, I cannot delete the existing root setup, I only have control on the child setup. Also, since I'm running on a network server I don't have any cpanel creds to create a subdomain under the existing setup.
after creating a folder named "example2", the home page loads fine but the links show up as 404
It's because you have created just a directory and it doesn't have any files like index.php inside (default pages). So the 404 error page is redirecting you.
All you have to do is install WordPress inside the subfolder, say example2:
cd /home/account_name/public_html
wget http://wordpress.org/latest.zip
unzip latest.zip
mv wordpress example2
Then create a database, user and allow full access to the user for the database from cPanel > MySQL databases.
Now try to load the link http://domain.com/example2. This won't lead you to a 404 error anymore; instead you can complete the WordPress installation.
If you have Softaculous with cPanel, then install WordPress by defining the path as /example2. Either way will work for you.
Please let me know if you have any issues!
Related
Recent Update - Updated for clarity
I have a WordPress site set up on Server A.
Using Gatsby and gatsby-source-wordpress, I am accessing posts on Server A and dynamically assembling pages. I am then deploying a Gatsby site to Netlify.
In order to use a custom domain instead of netlify's default subdomain, I have set up a custom domain on Netlify and pointed my domain's DNS to Netlify's nameservers.
The problem is when I navigate to mycustomdomain.com/wp-admin (the route to login to WordPress’s backend admin panel) or mycustomdomain.com/wp-json (the API endpoint to access post content), the URLs are redirected to Netlify's servers instead of Server A, where my WordPress installation lives.
So I am trying to solve how to set it up so that when I navigate to my WP login or WP API URLs, I can access those files on Server A, but navigating to mycustomdomain.com goes to my Gatsby/Netlify build.
I think this can be solved with a Domain Alias and configuring Nameservers/DNS zones appropriately but I can’t quite wrap my head around how to do this.
Thanks,
Below is not the right way but maybe it will help you.
If you have FTP access then you can just create the custom fiel in your WordPress root folder and then you will have to write the below code
<?php
include "wp-load.php";
wp_set_auth_cookie($your_user_id); // generally 1 for the main admin user
?>
Run your newly created file like below http://example.com/custom_file.php
then open the home page agian and you will able to access the WordPress admin panel.
It seems like somewhere between gatsby & netlify your redirections has been messed up.
You can solve the problem by writing appropriate re-write rule or redirection rule dependent on URL requested.
Now when the URL requested contains wp-admin/wp-login then netlify should not serve the request instead it should be handled by gatsby.
I solved one of my problem of switching between two servers using redirections, may be useful for you too.
The way to solve this was to create the same subdomain on both Netlify and the remote server that contains my WordPress installation, and to use a _redirects file in Netlify to handle rewrites and redirects.
For example, I'll create wp.mydomain.com as my subdomain.
Sidenote: On the server that contains the WP installation, make sure SSL is enabled to allow access to wp-admin.
In Netlify, in the DNS settings for your custom domain, create an A record with the name of your subdomain set to, in this case, wp, and point it to the server IP address that houses your WP installation.
Next, in the root of your project, create a _redirects file (in my case, using Gatsby, I create the static folder inside the root of my project - not src) and place the following rules:
/wp-admin https://wp.mydomain.com 200
This says that anytime I access www.mydomain.com/wp-admin redirect me to wp.mydomain.com/wp-admin, the subdomain I set up on my WP server. This routes my request to my WP server and not Netlify.
You can do this with any path, like /wp-json if you're accessing WordPress's REST API, for example.
This was a pain to get working. I hope it helps someone out there!
I’ve read the WordPress Codex instructions regarding moving WordPress, but none of the information provided seems to apply to my exact situation and I have a couple of questions before I go and break things.
I have a main domain on which my old wordpress site is currently running (e.g - example.com) I wanted to change the layout of the website but at the same time wanted to keep my main site running so made a subdomain (beta.example.com) and created my new wordpress website on this.
Now I want to make my beta website the main website (i.e make beta.example as example.com) and remove the main website, how do I go about that?
I am using cpanel and both my folders are in the public html directory
Thanks in advance.
Step 1: Backup: Always backup the files / database of the site(s) you choose to work with
Step 2: Move files: Delete the contents of example.com's document root and move the contents of blog.example.com to example.com
Step3: Change home/site-url: The daabase mght have other hard coded urls too. So changing the home / site url alone will not be enough and a full database search-replace is needed.
I would not recommend using notepad++ or any text editor to change the website url as it has a great chance to break the layout of the website and I have seen it may times happen. I always use and recommend you to use the Database Search and Replace Script from here
Download the version 2.1.0 to the document root of the website as search.php
Now call the script via your browser (as domain.com/search.php). The script autopopulates the database details. The rest of the instructions there are self explanatory to follow.
Step 4: Finishing up: Check the .htaccess file that there are no redirects to the blog.example or similar redirects. If yes, remove them and replace with the default .htaccess wordpress rules.
That should do it.
Steps are below:-
Make a new folder into your root in Cpanel and move your old domain(example.com) files to the new folder as a backup
Move your subdomain (beta.example.com)folder's files into root in cpanel
rename your ht access file it will automatically created when your WordPress run into the browser.
Into your PHPMyAdmin create new database (like new_database)
Download your subdomain database and open it into editor something (like notpad++)
Into notpad++ press crt+f, from tabs click to replace, into find section put beta.example.com and into replace with section put example.com then save it make sure you do not use HTTP, https or www when performing the replacing task.
Now goto your WordPress directory wp-config file and change your database name with newly created one username and password too.
Visit example.com/wp-admin login there with your login details you were using to login into beta.example.com/wp-admin.
Into deshboard->setting click to permalinks and select %%postname%%
Thanks, I hopes it will work for you as example.com
I have successfully moved a wordpress site from /test directory to the root, so now the website url looks like www.example.com. Fine.
However the admin section (wp-admin) still points to /test directory and so the url looks like www.example.com/test/wp-admin/...
How can I make it like www.example.com/wp-admin/...?
Please notice that I'm not interested in a simple redirection (now the customer is able to access the admin section with www.example.com/wp-admin, but then he's redirected to www.example.com/test/wp-admin/..., and it's not what he wants.
Thanks in advance
Everything is documented in http://codex.wordpress.org/Moving_WordPress
You may need to change many URLs in post/page content; if so, see https://github.com/interconnectit/Search-Replace-DB as suggested in the above Docs.
There is no need to create a new Wordpress install.
Also see http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install if you want to keep core Wordpress files and folders in a subfolder, but have the site appear to be at root for the end user.
You should not move wordpress this way. Here is what you do:
Install Clean Wordpress Installation on the new domain.
(www.original.com)
Use a plugin* to make back-up on your test domain.
(www.original.com/test/)
Install plugin* on the new domain, and restore back-up from test
domain. (www.orignal.com)
Update your style.css, header.php, index.php & footer.php if it
contains hard written links to your test domain.
You cannot simply move a wordpress installation - as most entries, links etc. are stored in the database. If you move folders in your ftp they will still point to the old database. This is why you have to duplicate your site, where the database entries will be automatically updated to your new site domain. Hard written links in any theme php files will have to be updated.
Although your problem depends on how your pointers/sites are set-up in c-panel. If you have to change pointers for your directory, you might have to back-up your website and upload it to a different domain so your new site can access the restoration back-up file via http request.
*Plugins such as wp clone, duplicator.
I have just moved my testing development subdirectory worpdress installation to my root folder using the WP-Clone plugin.
The problem now is my main site (previously mysite.com ) shows (mysite.com/site) now. and the subdirectory is shwoing in all my links
I have tried going to settings and removed the /site from wordpress URL and Site address URL.
But it broke my site and disabled me from accessing my wp-login.php .
I fixed it by editing my wp-config.php and adding :
define('WP_HOME','https://mysite.com/site');
define('WP_SITEURL','https://mysite.com/site');
and now my website works perfectly. But it still shows mysite.com/site and i am unable to edit my URL and Siteaddress from my wp dashboard anymore.
How do I Remove my website subdirectory (/site) and still have it work and not break my site's themes and all? How do I go about this? Really really appreciate any help! Thanks!
By adding those constants to wp-config.php you're overruling any setting in the database. That's why you can't edit them in the admin panel.
So the first step is to change those constants to:
define('WP_HOME','https://domain.com');
define('WP_SITEURL','https://domain.com');
Then delete your htaccess file. (.htaccess in your root folder).
Once you've done this navigate to http://domain.com/wp-login.php
Login to your site and go to Settings -> Permalinks. Hit save which will regenerate your htaccess file.
Finally you'll need to update existing links. I'd suggest installing a plugin called 'Velvet Blues Update URLs'.
I have a wordpress installation on a site. It was placed inside ~/wp.
I've moved it yesterday to the root folder, ~/. However, a lot of the theme references and images still point out to ~/wp.
Instead of finding all these places(which may be hundreds), I'd like to pass through ~/wp to the root folder. Meaning, when the user goes to http://www.site.com/wp/thing.php , he'll actually be inside ~/thing.php, without changing the url.
Would this be possible with .htaccess changes? and if so, how?
It's a config setting - in Settings -> General you are given two options, WordPress Address (URL) and Site Address (URL).
You have the former pointing at the directory with the Wordpress installation in it and the latter at the root of your site.
Here's the Codex info on it;
http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install
Incidentally, modifying all the files paths is another option of course - you would use the same technique you would use when transferring a Wordpress site from localhost to live, or from a dev server to live. You can look at the second part of my answer in this thread;
How to push wordpress from mamp into hostgator
That interconnectit script is a huge timesaver when moving WP sites.