multisite and site localization

Some people just can’t get the ‘hang’ of running a multisite but it can be easier than running a pair of sites on the same host as you can treat most of the multisite as one host.

On the twin hosts side, if you wish to go that route, you can place both database tables in the one database using the ‘table prefix’ to distinguish between the two and then you can share the user table of one site with the other. This is quite good unless you need the finer grained user control of the multisite.

You’ll find plenty of documentation for this by doing a Google Search. https://www.google.com/search?q=Sharing+a+user+data+table+with+two+WordPress+installs.&rlz=1CASUUV_enUS762US762&oq=Sharing+a+user+data+table+with+two+WordPress+installs.&aqs=chrome..69i57.23488j0j7&sourceid=chrome&ie=UTF-8

The problem with a multisite is the user integration isn’t an automatic process but you do get individual role control for each site with that if you really need it. I think there’s more info on this multisite user management issue over at https://premium.wpmudev.org/

So, if you need fine control over users at two sites then multisite might be what you need. As a secondary bonus, multisite might make things easier for adding sites later if needed.

The twin installs sharing a userbase is cool if you need to just let the exact same users make use of both sites with the same role capabilities. The Cookie domain settings can help maintain state between the two sites if you need that feature… in other words, a login on one site is an equivalent to a login on all sites using that single user base.