I will answer to my best ability point by point. Yes, wp multisite would be ideal for this and it will all be in one database. Not easy to do without a plugin, but yes there are plugins available for translations. However issues might arise, especially with regards to the customer’s expectations. a) This can … Read more
When loading blog B (thankfully) it doesn’t load plugins which are active on blog A only, and switch_to_blog() (thankfully) doesn’t do that either. You could trigger the update by using something like the JSON API (or XML-RPC, ewwww), or you could make sure the post type is registered both on blog A and blog B. … Read more
The simplest way is to use WordPress plugins. For example: 301 SEO Redirection 301 Redirects Or use .htaccess file
You just create must-use plugin for your multisite instalation (https://codex.wordpress.org/Must_Use_Plugins), hook to post save action there (https://codex.wordpress.org/Plugin_API/Action_Reference/save_post), and inside action callback check if current user is admin/super admin (https://codex.wordpress.org/Function_Reference/is_super_admin), if so, you find current blog user with ‘author’ role (https://codex.wordpress.org/Function_Reference/get_users) and update post (https://codex.wordpress.org/Function_Reference/wp_update_post) with his ID as author ID. At least it is first, … Read more
A wordpress network is exactly what you are looking for if no one needs FTP access. The only way to truly separate user info (high paranoia mode) is to have each site on a different server. Otherwise whatever information leakage that might be should be easily solvable with something that will let some of the … Read more
There is no built-in way to do it. The .htaccess is “printed in the screen” of the wp-admin ones you are setting up the multisite (the same for wp-config.php). That info is never write directly in .htaccess file like the single site. The wordpress core code for multisite / htaccess is here: https://github.com/WordPress/WordPress/blob/703d5bdc8deb17781e9c6d8f0dd7e2c6b6353885/wp-admin/includes/network.php#L543
To post most HTML tags (such as <script> and <iframe>), the user requires the unfiltered_html capability. In WordPress Multisite, this capability is (by default) assigned only to Super Admins (ie, those that can administer the entire network). This is by design, and is due to security concerns, among other things: Note: Enabling this option for … Read more
I am not sure how you are activating theme on Network but here I am considering a case of installing fresh theme on a existing Network. Activating theme on any single site will insert the term for every site in Network but yes of course taxonomy registration code should be there already. Consider this example … Read more
After a bit of debugging, I was able to narrow this down to the following: The menu that I had created to display across each site in the network was comprised of Custom post types that were not registered on any other subsite, only the main site (1). For whatever reason the custom post type … Read more
You’re close. I added a few more places to capture more scenarios and used the HTTP_HOST variable in the rule. The $1 is not needed in the condition as that would match what’s captured in the above condition. <IfModule mod_rewrite.c> RewriteEngine On Rewritecond %{HTTP_HOST} !^www\.(.*)$ [NC] RewriteCond %{REQUEST_URI} ^/subsite/? [NC] RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [L,R=301] </IfModule> … Read more