Works with multisite in his own directory?

Hi. There is no known compatibility issues either in favor of or against Multisite Language Switcher. The Cloner will make a database-level identical copy of the original site that you specify and update the necessary thing for it to function as a new and separate site (like site name, home and site URL, upload location, etc.) Have you tested it yet for your scenario and run into any problems? Or are you just preemptively wondering if that will work? The ideal method to find out would be to replicate your scenario on a test environment and try it. But after taking backups of course, it’s always fairly safe to try on an existing network. If something goes wrong with the clone site due to environment / hosting settings or other plugin conflicts you can always delete the new clone test site. We have not experimented with the Multisite Language Switcher plugin and Cloner together.

Thanks for your fast response. Sorry I didn’t explain my self correctly. I read that you recently update your plugin for support both subdomain and subdirectory mode. And the first question was: Could I use NS Cloner – Site Copier with wp multisite installed in his own directory, with the index.php in the root?
The urls of site are subdirectory mode, for example: mysite.com/es, mysite.com/en and the url of the backend is mysite/wp/wp-admin/, having wp install its own directory but with index.php in the root, because I have an static site running in the root.
For the second question: I’m looking for the best workflow for a bilingual site were all the content and translations are all ready done in the static site waiting to upload to wp. No, I didn’t install yet your plugin. Simply wondering how the plugin manage the links between one site and his clone. Of course I can disable first Multisite Language Switcher, and enable when is all ready cloned.
Waiting for unswear. Thanks

Hi – thank you for the clarifications.

Some have reported issues running the Cloner with multisite installed in a subdirectory and running in subdirectory mode. We haven’t really been able to reproduce all the problems ourselves, but have made some fixes to support this. It should work in that setup. Sometimes issues with permalinks or .htaccess cause problems with this configuration. Generally, we don’t recommend running multisite installed in a subdirectory. Our opinion is that it’s better to always run multisite under a top level domain even if it means getting a different domain to host it. Things are much more straight forward when the root of a multisite network is installed at the root of a domain. But everyone has different needs.

In terms of the best workflow for translated versions of sites: the Cloner does not maintain any kind of link between a clone and it’s original site. Once the operation is complete, the new subsite is a completely independent set of the content. To provide an accurate answer I looked at how MSLS works and stores its data for post linking. It stores those in the wp_##_options table(s) per site. Knowing that, this would be my recommendation for workflow:

1) install / start with a blank network
2) build your initial “home” language template site – this will be the site you clone. Do not install, activate, or configure the MSLS plugin on it yet. For example this might be mysite.com/en with all content in English and the Language set to English in Settings > General. Get it exactly the way you want it with all plugins / theme / content / etc.
3) clone mysite.com/en to mysite.com/es (both will be in english at this point and /es will be a copy of /en.
4) change the language setting for /es.
5) install the MSLS plugin and configure the settings separately on both /en and /es… add the widget to each site, etc.
6) edit every post on /es individually and:
a. update the content to the translated content
b. use MSLS to map it to its translated equivalent post on /en

You can also clone sites after doing all that, but what will happen is that you will get a duplicate site for a particular language. That is ok, but you will still have to repeat steps 4-6 for any site cloned with MSLS active.

Also take note: even if you deactivate MSLS the configurations it makes (the post mappings and its settings) are still in the database and will still get copied in a clone. If you then activate the MSLS plugin on the clone everything from it’s origin site will be there too.

The best way to get a feel for all this is to play with it and experiment for yourself.

Regards.

Thanks for your response. I create the sites but they are empty. I was testing what themes and plugins will be best for my needs, so I welcome all your comments. I don’t mind to do a fresh install in the root if it avoids problems.
The main reason for install WPMS in a subdirectory was that I must preserve the static site alive during development period. I didn’t like all files mix up. But I’m not willing to pay the price of future problems for that.
Now I realized that is almost the same if I install WPMS in the root. The preferred server url is index.html, and I think I will have no problems to preview the home index.php of each one of the language sites. I don’t have technical skills to develop in one hosting and migrate to the production hosting when every thing is done.
Sorry if something is not clear, my main language is spanish. Thank you for your advise and detailed instructions.