Account created on 18 February 2014, about 11 years ago
#

Merge Requests

More

Recent comments

πŸ‡ΊπŸ‡¦Ukraine nginex

Unfortunately I don't have a project hosted on Acquia to test it.

Do you import the zip file via UI or drush?

If UI, maybe it worth trying to replace

'#upload_location' => "temporary://import/zip",

by

'#upload_location' => "public://import/zip",

Then the issue might gone

πŸ‡ΊπŸ‡¦Ukraine nginex

@ashraf.hussain what is your temporary file path on prod and other envs? is there a difference?

πŸ‡ΊπŸ‡¦Ukraine nginex

> This is just menu_link_content, but for some reason it will load the whole referenced node and all its fields. Is it necessary to load all the embedded entities and their field values for links?

at the moment it exports full entity if it was not exported yet, otherwise it will export base fields only. So in your generated file you should not see the same entity exported multiple times including all fields.

Anyway, I really want to improve this in ✨ Allow to partially export content Active to reduce size of generated files and just export what is really needed instead of everything

πŸ‡ΊπŸ‡¦Ukraine nginex

yeah, makes sense, feel free to extend existing configuration form

πŸ‡ΊπŸ‡¦Ukraine nginex

Hey @murz,

The [drupal_root]/scs-export is a fallback path if you don't mention the custom one.

e.g.

drush content:export node /relative/output/path

πŸ‡ΊπŸ‡¦Ukraine nginex

Patch works like a charm, thanks

πŸ‡ΊπŸ‡¦Ukraine nginex

There are notes in MR that need to be taken into account

πŸ‡ΊπŸ‡¦Ukraine nginex

I provided a patch that extends logic of GenericContentEntity, so all base fields are taken into account with proper export and import logic.

Do not forget to clear cache before testing.

πŸ‡ΊπŸ‡¦Ukraine nginex

Added new events

πŸ‡ΊπŸ‡¦Ukraine nginex

After a second look I decided to refactor a bit of new event, so it's more logical to be used + updated readme

πŸ‡ΊπŸ‡¦Ukraine nginex

For user entity I would definitely try to find a user by username if no match by uuid.

The issue is that user entity should have a unique username and if user A was create on site A and the same user was manually created on site B, they do have different uuid but the same username

πŸ‡ΊπŸ‡¦Ukraine nginex

Refactored text, removed duplicates

πŸ‡ΊπŸ‡¦Ukraine nginex

Change order of the sections

πŸ‡ΊπŸ‡¦Ukraine nginex

Updated multiple texts

πŸ‡ΊπŸ‡¦Ukraine nginex

Changes headers

πŸ‡ΊπŸ‡¦Ukraine nginex

Added site uuid check explanation

πŸ‡ΊπŸ‡¦Ukraine nginex

Improve abilities

πŸ‡ΊπŸ‡¦Ukraine nginex

Thanks for your contribution

πŸ‡ΊπŸ‡¦Ukraine nginex

Adjusted the overview of abilities

πŸ‡ΊπŸ‡¦Ukraine nginex

Thanks for the patch, I fixed DI warning, looks good now!

πŸ‡ΊπŸ‡¦Ukraine nginex

Thanks for the patch!

I extended the logic a bit to work with any file schema not only private and public.

πŸ‡ΊπŸ‡¦Ukraine nginex

This is no longer needed, since 1.4.7 version all field types with simple get/set logic work out of the box

πŸ‡ΊπŸ‡¦Ukraine nginex

Thanks for checking the issue!

πŸ‡ΊπŸ‡¦Ukraine nginex

All the references to your page will be also automatically exported, it's a recursive process and that's the way how the module works. If your content contains links or entity references to other content, that content will be also exported to keep references in place and up to date.

So you did nothing wrong ;)

Anyway, I'm planning to implement this issue ✨ Allow to partially export content Active , so it will be possible to export content without references

πŸ‡ΊπŸ‡¦Ukraine nginex

did not know that block_id is a part of layout builder component, is it available out of the box in Drupal core or it's extra that is provided by some patch or contrib module?

πŸ‡ΊπŸ‡¦Ukraine nginex

Actually any field type should be automatically exported out of the box since 1.4.7

The simple field implementation will be removed since it's no longer needed. See πŸ“Œ Clean up SimpleFieldDeriver in favor to use GenericField Active

πŸ‡ΊπŸ‡¦Ukraine nginex

No way it’s not working out of the box in the latest module version, could you please check that?

πŸ‡ΊπŸ‡¦Ukraine nginex

updated my original comment #25, thanks for the suggestion @fabianfiorotto

Production build 0.71.5 2024