search

dgrigg / craft-migration-assistant

Migration Manager for Craft CMS
Other
27 stars 10 forks source link

Entries not inserted in non-translatable entries field in multilingual website #13

Closed timbertens closed 5 years ago

timbertens commented 5 years ago

My setup

the entries that can be linked are products and have of all translatable fields, including of course a multilingual slug

In the section mentioned above the field that holds the links to the other entries (products) are not filled. The setup I have is evolving (being the translation for the products are only recently added) and before the products all had the same slug (incorrect of course but at that time the site was just single language). In that version the slug of the linked entries were all the same for the different languages and then the migration worked fine.

So I believe that the process is going wrong because the slug of the linked entries are different for each language as of now (and that is of course how it should be)

I hope my explanation is clear, if not let me know !

Versions Application Info

PHP version 7.3.1 OS version Linux 4.15.0-45-generic Database driver & version MySQL 5.7.25 Image driver & version GD 7.3.1 Craft edition & version Craft Pro 3.2.10 Yii version 2.0.21 Twig version 2.11.3 Guzzle version 6.3.3 Imagine version 1.2.3-dev Plugins

Activity Log 1.0.1 CodeMirror 1.0.1 CP Field Inspect 1.0.6 Do It Yourself widget 2.0.1 Field Manager 2.1.0 GeoField 1.0.0 Matrix Toolbar 1.0.6 Migration Assistant 3.1.3 Redactor 2.3.3.2 SEOMate 1.1.0 Site Switcher 2.1.0 Stamp 2.1.0 Table Maker 2.0.1 Two-Factor Authentication 2.2.0 Typed link field 1.0.19 Wheel Form 2.2.3 Wordsmith 3.0.5

timbertens commented 5 years ago

Just a quick update. Because we were stuck at this point, we had to look for a workaround to keep the deployment proces going. What we've done is

When running both migrations, things are how they should be.

dgrigg commented 5 years ago

Hi @timbertens reading over this I want to clarify a few things: The matrix field has a block with 3 fields in the block:

When you run a 'content migration' the values in the header and text fields are populated correctly in their respective language entry. The link field value does not populate for any of the language entries.

Is that correct?

timbertens commented 5 years ago

yes, exactly. The content of the migration file is correct (referencing the correct entries, each in their own language) as far as I can tell, but on running it I end up with no entries in the third field

dgrigg commented 5 years ago

@timbertens do the entries that the third field is linking to exist in the destination site before the migration is run?

timbertens commented 5 years ago

yes, the linked entries (being products) are created first and afterward the section (there are 3 in fact) that links to those products is migrated

dgrigg commented 5 years ago

ok, I will dig into this one

dgrigg commented 5 years ago

@timbertens trying to figure this out. I setup similar fields/sections locally and everything is working correctly.

I created a single landing page section with a matrix field with one block, block has 3 fields, 2 text fields that are translatable, one entry field that can link to an entry (product entries) that is not translatable. Screen Shot 2019-09-02 at 11 17 45 AM

The product entries are translatable. I created multiple products in different languages. I made sure all the product entries were exported/imported before migrating the landing page. After that I can select any product on the landing page, create a migration and then run in the destination site and everything is correct.

timbertens commented 5 years ago

Do your products have a different slug per product per language?

dgrigg commented 5 years ago

no, the products have the same slug

timbertens commented 5 years ago

Make them different and you should start having the issue too

dgrigg commented 5 years ago

Still working correctly. Can you send me a copy of the migration that was causing the issue.

timbertens commented 5 years ago

in your mailbox !

dgrigg commented 5 years ago

release version 3.1.4 should resolve this issue.

timbertens commented 5 years ago

yes, it does! many thanks