I have to move a WP site to another domain where I already have WP running in the root.
Because this is a temporary solution, I don't want to change the existing WP installation to multisite. I want to keep both sites and DBs separated as I'll move the site back later.
So, in a nutshell, I want to move site.com/wpsubdir/ to site-running-wp.com/wpsubdir/
I've tried a dozen different things, mostly around excluding that subdir from the root's rewrite rules but nothing works. The root's WP site still takes over and shows a 404 for every page, including static html ones.
Any suggestion?
Thanks!
Related
Context
Hi, I recently created a new wordpress site for one of my clients. I first created it in a subdomain of the target domain. before dragging it to the target directory via FTP. Once finished, I moved the content of the old site file (a prestashop) from the root (httpdocs) to another file on the server, then I finally dragged the new wordpress site before on this same root (httpdocs). All this was done via FTP. All this was done via FTP, but I had to restart the moves several times.
Problem
Wordpress Toolkit now detects two Wordpress sites (see 1 2) on the main domain and I observe some really strange behaviors, for example :
When I delete one of the two sites via the Toolkit, it then automatically returns to the list
Both sites have exactly the same data (status, plug-ins, databases, ...) in the Toolkit
Some changes made on Wordpress actually appear on the page in question, but when reloading, they go away, then come back, as if there were actually two sites that overlapped: one that is affected by the changes and the other that remains unchanged and that are randomly chosen to be displayed on my browser.
Another finding that supports this is that when I log out of the WordPress admin console, and then return to the site as a visitor, the admin banner is still there at the top of the page, proving that I am still logged in
So I don't know if it's a problem with the configuration of WordPress files like .htaccess/wp-config or if other files were corrupted by the FTP moves or even both cases. It seems to me that there is only one Wordpress in my httpdocs and I don't really know where to look...
I deleted all the files from the server, having first uploaded the folder containing my wordpress via FTP. I then recreated httpdocs again then uploaded the site, some files were no longer present and created some 404, I added them by hand based on an old version of the site that I had in backup.
I have a simple HTML microsite, which I want to put inside my wordpress website. For example: Wordpress website is: abc.com
I want to put my microsite inside this wordpress site. So URL becomes:
abc.com/microsite/
But, wordpress treats any url as its own. How can put "abc.com/microsite/" urls to Wordpress Ignore list. So that any pages inside microsite folder executes independently.
just put you folder 'microsite' in root(Where you find wp-admin,wp-content and wp-include folder). and
you are able to access the folder
"abc.com/microsite/ by this url
If you are still having issues with accessing the subfolder, try renaming the .htaccess to .htaccess-bak in order for WordPress to regenerate the file again. Understand that your website might temporarily go down.
I've found this solution to help in some cases, but I don't know exactly why, ergo I am not sure it will work. And if you feel uncomfortable editing the .htaccess file I suggest you learn more about it (as should I). It is a very powerful file and WordPress uses it a good deal.
P.S. The file is located in the same folder, WordPress' root folder where you find /wp-admin/, /wp-content/, etc. It is hidden by some hosting providers, but I've always been able to find them through FTP with the hosting companies I've used before.
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've been developing a wordpress website on the same place where it's supposed to go live, just in a /beta folder to keep it from regular visitors. Now it's done, I need to put it live, by moving the entire wordpress installment I have in the /beta folder, down into the root of the domain.
The problems I encountered when I first tried this were that everything automatically links back to the /beta folder, for example my stylesheets link to the right location but the /beta/ folder is included in the link, and I can't seem to find out where to change this. I've tried the Yoast wordpress move tutorial but that seems to be made for entirely different domains, and this is inside the same domain.
So, how would I change the automatic linking? It's not all in the .htaccess file, that's just for in-site permalinks.
The Wordpress Codex has a canonical document for this, Moving WordPress.
Whether you're moving from domain to domain, or inside the same domain, doesn't matter. The process is always the same.
Is it possible to have one WP instance run domain.com/articles and domain.com/tips while the rest of the site would be run by Zend Framework?
What you could do is setup a Wordpress MU site. have the install on domain.com/articles and domain.com/tips and then the rest of the site shouldn't cause any problems.
The only downside is that you basically have two sites for two sections of your site. I just did a Wordpress MU build and it got a little tricky but in the end it all worked and its pretty easy to update, just an extra click or two.
You can install Worpress in your root domain. Make the homepage of the Wordpress install the current homepage of your website with all of the links, layouts, and original site subfolders preserved. Then just have Wordpress take care of the other URLs that you defined above, making sure not to create any Wordpress directories that conflict with the current site directories.