Move wp-admin to a subdomain on separate server wordpress - php

I have a wordpress site, foo.com. For various reasons, mainly caching, I need to move the wp-admin area to a subdomain admin.foo.com which is hosted on a separate server.
What's the best way to approach this, would a straight .htaccess rewirte work? I've seen that you can set WP_ADMIN_URL in wp-config.php but how do you separate the site in such a way that the amin sits on a different server than the rest of the site.

You can make use of two different installation of wordpress but the database will be same. One for staging and another for live

There isn't a way to separate the frontend and admin area of a Wordpress site onto two different servers. Wordpress is a web application. You get the whole thing as a package.
If you've seen something like this before, the site owner is doing one of two things:
They are running Wordpress on the admin site only, then using a plugin or some other technique to generate static HTML snapshots of the pages that form the public website.
They are using a staging site plus live site type architecture. Many of the new WP-specific hosting services include a staging site and a simple synchronization option.

Related

Resolving urls on a Wordpress server using React

I'm working on creating a new React-based site to replace an old WordPress site. I have been creating directories within the wordpress server for the new sections I have been making. domain.org/about, for example, will go to the react files stored in the about directory. No problems there. The issue I am having now is for more complicated urls. I have set up react-router to handle lots of events by using an id to pull in information on a specific event. domain.org/events/event123, for example, should display information on event123. In development this works fine, localhost:3000/events/event123 will display event123. On the wordpress server, however, I get an error. I realize that this is because there is no event123 directory within the events directory on the wordpress server.
How can I configure wordpress to handle these urls? I realize I need to set something up so that any url that begins with domain.org/events will go to the react files in the events directory, but how I go about doing this while still passing along the event123 I do not know. Any help is appreciated. Apologies if my description is a bit confusing.
EDIT: I should add that the old parts of the site and new parts of the site have no connection to each other, other than the fact that they are hosted on the same server. Once the new site has enough content on it it will be moved to a new server and the wordpress site will be shut down.

how to manage magento multi site in local and in live server

I am still new to magento. I have successfully installed magento ce on my local wamp server. I choose magento because I heard that it has multi site feature. My client have three separate website that are running on three domain name(www.sample1.com, www.sample2.com, www.sample3.com). I am planning to control them on one admin.
I would like to know how can I manage to create multi site on my local and how can I upload it on live server.
Also, can someone explain to me in simple the architecture of multi site of magento. If I'm not mistaken, I understood it this way.
admin -> my backend maybe running soon www.sample1.com that handles all my website.
website -> This is where I will give separate domain. for example website one is running on www.sample1.com. website two is running on www.sample2.com. and finally website three is running on www.sample3.com
store -> I don't have clear understanding of it.
store view -> this is the presentation layer. the most fron-end of the website where products, themes are displayed.
This is kind of stupid but i'm still new to magento.
Thanks!

Theme Not Working When Visited from Separate Computer on New Wordpress Blog

I am using WAMP with a new WordPress blog. I am hosting this on a local computer. Upon my arrival at this URL from a separate computer a lack of CSS appearance becomes evident. To clarify myself further, when I view this site on another computational device designed to compute the CSS that ought to load does not perform its designated task. Perhaps the scripts are not performing their tasks? PHP scripts that WordPress uses may have errors impairing the overall performance from an external device. My English, please excuse, and have my deepest respect comrades.
Maybe you installed your blog with an url like http://localhost/blog
In the WordPress database the url is used to find the link for CSS, theme files, etc...
Accessing from another computer with your ip address (let's say that is 192.168.1.5) will break the css, because, if you look at the code of your wordpress page you'll see links pointing to localhost, that has no meaning for the other machine (or better, for the other machine means "myself", so it will look for css on its filesystem and not on your remote pc).
Sorry for the bad english. :P

Can I run both my wordpress website and non-wordpress website on same domain?

I build a client website and business system using html+php+mysql and both runs on same domain.
Recently, I feel like it would be better to separate the website and use wordpress so that the client can update their own contents instead of me doing this everytime they need to change something.
As, my client is in low budget, I was thinking whether it would be possible to run both the wordpress and business solution on same domain. If I run the business solution under sub-domain will it solve the issue or wordpress’s front controller will pickup any request related to that domain?
Is it possible at all? My suggestion would be appreciated.
many thanks,
Mahbub
It's absolutely possible, yes. And there are many scenarios you can use depending on what you want to do:
Subdomains — install everything in different subdomains, or install one thing at the root and the others in different subdomains. The subdomains normally just map into directories on the same account, so you use the same FTP credentials and so on to transfer files.
Directories — like http://www.example.com/blog. Very easy to deploy a blog this way, and just put your other stuff in the root.
Intermingling — you can actually put files (.php, .html, etc.) in the same directory as WordPress, just as long as there are no name conflicts. The default redirection rules in .htaccess will ensure that those files will get served as usual without interfering with WordPress.
Not knowing anything about your code, if it's simple enough another approach would be to create custom page templates in WordPress that invoke your code. The nice thing about this is that your pages will always have the same look and feel as the other pages in the blog, i.e. if you change/update the theme. This may or may not matter to you.
Its possible. We have implemented it for multiple sites in the following ways
Elgg as Master
FluxBB / PhpBB for forum
Wordpress for blogs
You can then share the sessions between these systems. Just process your login/ registration through only one system.
Sure, you can set the wordpress site in for example: http://blog.example.com and the website in http://www.example.com without any problem. Just need to setup that in the web server.
I did it by putting the wordpress blog in a separate directory inside the large domain. wordpress do not interfere with other php sites on the same domain.
Yes, it's possible.
We'd used Drupal for main website, ELGG for social networking, PHPBB3 for forums and Wordpress for blogging on the same domain name. We did it by using different subdomains for each site.

Backend shared between sites - best method

I have a php backend which is to be used by multiple sites on a server I control. Now rather than having an individual copy in each web root, what is the best method to have each site work from 1 shared backend? (For easy updating of the backend, etc)
The site and backend are connected through the database. It doesn't matter where the backend and all your sites are located, as long as they all connect to the same database, they share the same information.
keep one copy of the core files that are common across all the sites. have all the sites link up to the core files. the non-core files can reside in its own sites folder. \

Categories