Just learned your plugin does not work (i.e., translate) when a URL contains a “category” or pulls a URL from our archives.
Example:
Our Environment:
WordPress 6.7 (latest)
Avada 7.11.11 (latest)
PHP 8.4.0 (latest)
Translate WordPress 3.0.7 (latest)
What’s going on? Got fix?
Thank you!
]]>How can I clear cache via URL using a Page Subdirectory (not Post ID)?
Reason: Above method is a lot easier, faster that trying to determine or obtain the Post ID.
Once you share the solution, please update your documentation.
Thank you.
]]>When I try to create a multisite network to be able to translate my website without using a plugin (I’ve used several in the past), I only get the option to do this with subdomains, not subdirectories. I would like to use subdirectories as I think this option is clearer, allowing people to easily navigate between the two languages. I’ve read that it’s not possible to use subdirectories on websites that are older than 30 days, but I was wondering if there’s a way to still establish a multisite network with subdirectories.
Thank you in advance for any help you can give me.
Kind regards, Laura
]]>To run from the root (with a sub dir install), I add the subdir to the require statement in the index file at the root of the site.
/** Loads the WordPress Environment and Template */
require( dirname( __FILE__ ) . '/subdir/wp-blog-header.php' );
Unfortunately I need one that works on a subdirectory.
Any chances yours can work on a subdir?
Cheers from Argentina.
]]>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’m using the business version of TranslatePress.
The site is originally in Dutch.
Force language in custom links is on.
Use a subdirectory for the default language is on.
English is dragged to the top of the “All Languages” list, so international visitors land on the English translation.
When writing a new custom post, in the original Dutch,
I am adding an internal link to the paragraph.
Using the standard “Insert/edit link” WordPress menu, I type part of the post I want to link to, in the original Dutch language, upon which WordPress shows the Dutch post in the dynamic list.
Clicking that Dutch title post however inserts an English (translated slug) link, without the /en/ subdirectory in the url.
This is not the desired behaviour, as the link will now link to the English post from a Dutch page.
When I drag Dutch to the top of the “All languages” list in the TranslatePress settings, I can insert Dutch links (also without /nl/ subdirectory, but they work).
Disabling the “Force language in custom links” does not make a difference, it will still insert English slug links, without subdirectory /en/, into Dutch posts.
Is this a bug? I think it should default to inserting the original language link when writing a new post.
When I publish new post from ‘main website’ and ‘subdirectory website’ then main website post shown in search result within 30 minutes but subdirectory website’s posts not.
]]>