Bug with multisite:sync content and taglist

Need Help
#1

Hello,

I discovered a bug with multisite:sync content and “entries” type tailor field with displayMode taglist.

To reproduce :

handle: Prestations\Prestation
type: structure
name: Prestations
drafts: false
multisite: sync

structure:
    maxDepth: 1

navigation:
    icon: icon-briefcase
    parent: Prestations\Realisation
    order: 20

And the other blueprint :

handle: Prestations\Realisation
type: structure
name: Réalisations
drafts: false
multisite: true
  
structure:
    maxDepth: 1
  
primaryNavigation:
    label: Réalisations
    icon: icon-rocket
    order: 17000
  
navigation:
    icon: icon-rocket
    parent: Prestations\Realisation
    order: 10
  
fields:
    prestation:
        label: Prestation
        type: entries
        displayMode: taglist
        source: Prestations\Prestation
        placeholder: Choisissez
        span: auto

Now, try to create a Réalisation, choose one or several prestations, you will see that values will not be saved (october CMS 3.5)

The problem is related to the taglist display mode, choose “relation” display mode, it works

#2

Hi,

I have the exact same problem in version up to 3.7.1.

I have a field of type “entries” that not translatable, since the list itself contains its own translations, and whenever I modify the synchronized record in the other site (English), the list clears itself. I have to go back in the primary site (French), put the elements back, and save again for them to reappear.

Here’s the YAML excerpt:

uuid: cfa5c7a5-6e2c-4cc7-8620-702ff3c9640e
handle: Site\Models
type: structure
name: Modèles de maisons
drafts: false
multisite: sync
pagefinder: item

fields:
    features:
        label: Inclus
        type: entries
        source: Lists\Features
        conditions: always_included = false
        displayMode: taglist
        translatable: false

As shown, multisite is synchronized and the displayMode is taglist. The condition doesn’t work but that’s another issue.

As per your suggestion, @Zmove, if I change the displayMode to relation, the problem goes away and my saving in either site does not affect the values in the features field.

#3

Hey all,

I can’t reproduce both of these issues.

In the first example: Each Prestation can be stored individually for each Realisation and it works toggling between English and French. There is no sync mode, so switching to French did ask if I wanted to created a record, as expected.

In the second example: The records and fields are both synced, so changing the taglist on the English site will update the French site, and vice versa.

I could not see where values are not saved, where they disappear, or any difference between displayMode: relation.

This is tested on v3.7.1.

More detail might be needed here with exact steps for reproducing it. Sometimes the devil is in the details!