My client’s websites are currently setup up as WordPress multisite using subdirectories for subsites. The primary website and subsite URLs are accessed using the format:
https://domainname-primary-site/
https://domainname-primary-site/subsite1
https://domainname-primary-site/subsite2
https://domainname-primary-site/subsite3
The client has had another firm develop a new primary website. This new site will be installed as a standalone website, but still using the existing Primary URL (i.e. outside of WordPress but still on the same server).
All the subsites will be remaining in the existing WordPress multisite installation. They need to continue using their existing URLs (as shown above).
If the primary domain url points to the new standalone website, how/what do I need to set up on the server to point requests to the subsites to the correct place?
]]>First off, beware of trying to back out of using Gtranslate, once implemented. It’s kind of like trying to leave Scientology, or the mob. It’s very messy, once you have all that translated content indexed by Google.
Especially beware, ever since Google search’s most recent CORE UPDATE, which started early this March (2024), sites using machine-generated content (which is what Gtranslate stuff is), are being literally “destroyed” overnight; meaning, basically wiped off of Google’s search map. (Not always de-indexed, but certainly “massively de-ranked.”)
For info on this core Google update of early March, and how it is affecting sites that use machine-generated language translations, please see the following article. There are many other places online discussing this hot issue, but I found this article to be the best so far (in my own research):
https://www.managedserver.eu/google-core-update-of-march-2024-gtranslate-automatic-translations-and-seo-penalties/
WHY I NEED THAT LIST OF SUB-DIRS:
I’m in the process of cleaning up my website from all vestiges of having previously used Gtranslate. (Just FYI, after leaving the Gtranslate family, lol, I was forced to add a global regex-based redirect, that sends all requests for <my site’s url>/<2-char language subdir>/<translated page>, over to my original, non-translated pages — Why? This has allowed me to circumvent Gtranslate’s self-serving 402 “non-payment” redirects, affecting all previously translated pages on any previously paid website, which they automatically put in place. These 402 redirected pages include the URL of Gtranslate’s site. The result is that your site’s reputation is trashed, with a “this site is no longer paying us” message on the 402 page, and, their site is promoted, at the same time. Never try to leave the family. We will tell anyone who is trying to visit a previously translated page of ours, that your pitiful website is not paying us. And we will, of course, put the URL of our website on the 402 page. Hey, it couldn’t hurt, eh?
BOTTOM LINE: Now, as a follow up, so that maybe Google will stop punishing my site for Gtranslate’s machine-generated content (ever since Google’s March core update), I want to clear all my translated pages from Google’s index, by way of manually-submitted content removal requests. ALL I NEED NOW is a complete list of all two-character subdirectories that Gtranslate uses. Examples are <site url>/de, <site url>/it, and all the rest. The list I’m seeking would be all those subdirs. Can anyone help me get that list? Gtranslate support does not want to help, since I am no longer a paying customer. I tried.
]]>I tried GTranslate a few days ago, and it worked fine but I found an option that better meets my requirements and I proceeded to uninstall Gtranslate from my WordPress Network, now I’m using this new plugin and I found out that all the languages subdirectories are still reserved by GTranslate even after I uninstalled the plugin. What should I do?
Thanks in adavance for your help!
]]>I’m using
WordPress Version: 5.9.3
Theme: Twenty Twenty-Two
WordPress Settings: Permalink Settings > Post name
TranslatePress: languages > German + Turkish
TranslatePress: Native language name > Yes
TranslatePress: Use a subdirectory for the default language > Yes
TranslatePress: Force language in custom links > Yes
After installing and activating the WPS Hide Login my settings www.mysite.com/[something other than wp-admin e.g. LOGIN]
change to www.mysite.com/de/login
. Then I am redirected to the 404 page so I can no longer log in.
How can I get your plugin work with WPS Hide Login and subdirectories?
Or can you recommend another plugin with the same range of functions?
? 5 stars for the EXCELLENT plugin features
? 5 more stars for the EXCELLENT customer support
TEN (10) STARS!
ORIGINAL REVIEW posted months ago:
It’s hard to believe the basic capability to create subdirectories in the Media Library STILL does not exist in WordPress. The first version of DOS enabled subdirectories forty years ago! I’m using the free version of Folders for now. If the author(s) continue to update it properly, and if my site does well, I’ll likely update to the Pro version. So far, everything about Folders works.
Example:
www.mydomain.com
root folder
Install1
Install2
The root folder does not contain a WordPress installation or anything else executable.
Requests to the root domain should all go to Install1 directory unless the URL specifically requests www.mydomain.com/Install2
, at which point the second full installation is utilized including wp-admin
The htaccess file should also redirect requests to the www form of the domain and the https protocol, along with index.php if no file or folder is specifically requested.
I have found information on redirecting an installation to a subdirectory, but not the specific case of two subdirectory installations, and combined with www and https directives.
Any help is appreciated,
Bill
I’ve used your excellent plugin to clean up some of my sites, I have a doubt can you please let me know how to Scan sub directories in of primary domain. Those subdirectories are placed outside public_html. Looking forward for the reply.
TIA
]]>For example, I’ve excluded
/home/customer/www/domain.com/public_html/excluded/, but files in /home/customer/www/domain.com/public_html/excluded/subdir/ are being flagged.