8 – Can I translate nodes and then grant access to their translated content without the need for a site-wide language switcher?

Wanted behavior / question

  1. The writer creates / node / 5001
  2. The translator translates / node / 5001 into French, using all subtleties of the content translation backend system
  3. The visitor switches to / node / 5001 and sees a link to the French version in the sidebar
  4. The visitor arrives in / fr / node / 5001, reads it and then clicks away via one of the main menu links
  5. The visitor now browses the site in English, as this is the main language of the site and the language menu links are written. The display of translated content behaves like any other page on the site. it does not change the language forever.

An error has occurred between steps 4 and 5 because in step 4 the Web site is put into French mode. This means that all menu links point to French versions of the content. All subsequent browsing is theoretically done in French (not what I want), but in practice the language changes between French and English, depending on the availability of the translations (even worse), and the URL contains the / fr / Prefix, no matter what is actually displayed.

Is there a practical solution for this?

Background / supplement

I have enabled the Drupal 8 content translation and language modules. Speech recognition and selection is done through the standard mechanism that recognizes language code prefixes in the first component of the website path (eg. / fr / node / 1, for the French version of node 1).

I am now wondering if there is a way to ONLY translate the content of selected pages, but NOT the entire site, without compromising with the Drupal boss, so the content is made available through links on my site, using the Default language is restored to English when navigating away from the same pages?

It is intended to use Drupal's built-in translation management capabilities (although other suggestions are not welcome) to create and maintain subordinate multilingual content in the backend, and then, on a case-by-case basis, to access these translations via links in a block without having this navigation Actions trigger persistent language selection Events (from the user's perspective) where all matching menu URLs are rewritten.

Basically, I'm trying to get something running that corresponds to the Content Translation module, which is a bundle of multilingual PDFs attached to a single English content. Except that I do not want to create links to PDFs, I want to create links to normal websites. The only real difference is that they are written in a different language and linked behind the scenes with an English version.

Am I wasting my time with this, or is there a way to translate only part of my content, with access to those translations from the English website, minus the perseverance of a fully engaged language change for the rest of the surfing session?

8 – Site-wide settings versioned and deployed

I am developing a decoupled site and there are some site-wide settings, such as: For example, logo, social links, and others that appear in multiple places, so we want one central location for everyone. We also want this to be versioned potentially, but in any case using the upcoming Workspaces module. How would we do that best? Creating a custom settings page is my first thought, but how would I use it with workspaces and hopefully versioning? Or would another method be better?

PHP server-wide or site-wide?

PHP server-wide or site-wide? | Web Hosting Talk

& # 39);
var sidebar_align = & right; & # 39 ;;
var content_container_margin = parseInt (& # 39; 350px & # 39;);
var sidebar_width = parseInt (& # 39; 330px & # 39;);
// ->

  1. PHP server-wide or site-wide?

    Hello, I have a VPS with an outdated version of PHP, while I've just upgraded PHP to the latest version for a single site. Does it affect the performance of this website to make PHP server outdated and just to update the site?

  2. If you only have one website, you can do so server-wide. This has no effect. However, if you add sites in the future, they all will run with the same settings.

    TrentaHost INC. | 7 years in operation | DDOS-protected network | Multiple locations | Support around the clock
    DDOS protected Web / Reseller / Master – DEDICATED IP | LETTER CHANNELS | CloudFlare | LiteSpeed ​​| CloudLinux
    DDOS protected KVM Windows and Linux VPS | Fully managed | Cpanel included | 20 GBPS DDOS protection
    DDOS protected Dedicated server | 20GBPS DDOS protection | Control Panel | Price Guarantee *

  3. There is no problem with updating the PHP version for a single site on a server, keeping the outdated version as the main PHP.

Similar topics

  1. Reply: 2

    Last contribution: 02-03-2006, 07:50 clock

  2. Reply: 0

    Last contribution: 19.01.2004, 23:39 clock

  3. Reply: 5

    Last contribution: 09-10-2003, 11:41 clock

Tags for this thread

booking permissions

  • you not allowed post new threads
  • you not allowed post reply
  • you not allowed Post attachments
  • you not allowed Edit your posts

DreamProxies - Cheapest USA Elite Private Proxies 100 Private Proxies 200 Private Proxies 400 Private Proxies 1000 Private Proxies 2000 Private Proxies ExtraProxies.com - Buy Cheap Private Proxies Buy 50 Private Proxies Buy 100 Private Proxies Buy 200 Private Proxies Buy 500 Private Proxies Buy 1000 Private Proxies Buy 2000 Private Proxies ProxiesLive Proxies-free.com New Proxy Lists Every Day Proxies123