I tried to find a similar issue, but I did not find it. It may be I am inexperienced, so if there is such a topic I apologize and please add my question to existent issue.
Backdrop now has the ability to specify the language of taxonomic terms. This is especially useful with the correct transliteration of URL address of the page of the corresponding taxonomy term in different languages.
A problem, however, is that when you are on a term for one language, switching languages does not switch to translating the term to another language even though such translated term page exists.
As far as I understand, this is due to the fact that we can now set the language of the terms, but we cannot create translations and translation links between the translated terms.
There is also a problem with indexing pages of taxonomy terms in search engines. For example, you have a term in English, this page is indexed by Google and shown in search results, but when you visit the term page in English, the interface of the site is shown often in a different language. Not always, but very often. This seems to depend on the language in which the site was active before opening the link in the search results.
Is there a Drupal or Backdrop contributed module that accomplishes this?
In Drupal 7 i18n manages such problems correctly with a submodule.
I am not able to offer a solution, I am just reporting the problem.
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists