search

craftcms / cms

Build bespoke content experiences with Craft.
https://craftcms.com
Other
3.25k stars 629 forks source link

Category assets not copied to new languages #4391

Open alanski66 opened 5 years ago

alanski66 commented 5 years ago

Description

Add two sites same domain, two languages for spanish and french. Oriiginal english category image asset field is not copied to new category image asset. But they appear to be for entries.

Steps to reproduce

[assumes categories have no urls]

  1. Add image asset field to category.
  2. Add icon to category image field
  3. Add two new sites french and spanish for same domain
  4. OPen category and edit in french - no original english asset is present or copied acorss
  5. There appears to be no way to trigger this

Additional info

Element API 2.5.4 Feed Me 4.1.0 Form builder 2.5.24 Freeform Pro 2.5.24 Guest Entries 2.2.3 Iconpicker 1.0.5 Imager v2.1.10 MobileDetect 1.0.2 pdfthumbnailer 1.0 Position Fieldtype 1.0.14 Readability 1.0.4 Redactor 2.3.3.2 Redactor Font Awesome 2.1.0 Retour 3.1.15 Section Field 1.1.0 SEOmatic 3.2.7 Splashing Images 1.2.0 Super Table 2.1.20 Template Select 2.0.2 Typogrify 1.1.18

brandonkelly commented 5 years ago

After creating a new site, there will be a few “Resaving elements” background jobs that begin working. Did you ensure that those were completed first?

In your Assets field settings, under “Advanced”, do you have the “Manage relations on a per-site basis” checkbox ticked? If so this would be expected behavior.

alanski66 commented 5 years ago

They didn't seem to trigger properly. I added a new italian site and can see that some propagation of assets and category elements takes place. "manage relations" is not ticked. Checking category language assets still shows them not copied across. Is this because they might have been edited which would stop them from copying across?

brandonkelly commented 5 years ago

If a category was edited that should have just pushed its propagation to the front of the list.

If you send in your composer.json and composer.lock files, and a database backup, over to support@craftcms.com, plus steps to reproduce the issue, we can look into it from there.