Had a client request to be able to, via the gui, export a piece of content and it's related content to an archive,
and then upload an import that content to another instance of the site.

This bypasses version control and such, but it's the requirements I was given. And it does come in handy.

Here is a work in progress but working patch to provide such functionality to default_content_deploy.

CommentFileSizeAuthor
#2 3070222-2.patch36.38 KBthursday_bw
#3 3067539-3.patch12.42 KBthursday_bw
#4 3070222-4.patch37.58 KBthursday_bw
#8 import.jpg59.21 KBkevinfunk
#8 export.jpg80.17 KBkevinfunk
#8 entity-type-export-config.jpg51.51 KBkevinfunk
#8 entity-export-01.jpg33.27 KBkevinfunk
#8 entity-export-02.jpg24.85 KBkevinfunk
#8 3070222-8.patch33.8 KBkevinfunk

Comments

thursday_bw created an issue. See original summary.

thursday_bw’s picture

thursday_bw commented
StatusFileSize
new 3070222-2.patch36.38 KB
thursday_bw’s picture

thursday_bw commented
StatusFileSize
new 3067539-3.patch12.42 KB

This new patch adds to the existing patch. It imports the tar extract to a private temp store instead of overwriting the files in the deployed content directory.

(I am thinking that this should be it's own module instead of patch, as it seems default_content_deploy's use case is git managed deploy files.
whereas this bypasses git and deploys files manually).

In any case, this patch allows importing without needing to configure a content sync directory as the import is written temporally to the DB.

thursday_bw’s picture

thursday_bw commented
StatusFileSize
new 3070222-4.patch37.58 KB

wrong patch :(

again:
This new patch adds to the existing patch. It imports the tar extract to a private temp store instead of overwriting the files in the deployed content directory.

(I am thinking that this should be it's own module instead of patch, as it seems default_content_deploy's use case is git managed deploy files.
whereas this bypasses git and deploys files manually).

In any case, this patch allows importing without needing to configure a content sync directory as the import is written temporally to the DB.

ivnish’s picture

ivnish
he/him
commented
Status: Active » Needs review
miroslav-lee’s picture

miroslav-lee
Location Krakow
commented
Status: Needs review » Needs work

Patch did not apply.
Could you rework, please?

ivnish’s picture

ivnish
he/him
commented

And we added tabs to configuration. Needs add new tab for "export"

kevinfunk’s picture

kevinfunk
he/him
commented
StatusFileSize
new 3070222-8.patch33.8 KB
new entity-export-02.jpg24.85 KB
new entity-export-01.jpg33.27 KB
new entity-type-export-config.jpg51.51 KB
new export.jpg80.17 KB
new import.jpg59.21 KB

Patch adds export form and export entity form with option to export as a tarball. It also adds the option to import from a tar file.

kevinfunk’s picture

kevinfunk
he/him
commented
Status: Needs work » Needs review
miroslav-lee’s picture

miroslav-lee
Location Krakow
commented
Status: Needs review » Needs work

Thank you a lot for your patch. This functionality is very cool.
But this patch has several problem:

1. The patch does not apply
2. Why did you add the default_content_deploy.settings.yml file?
You can use the getContentEntityTypes method of the DeployManager class
3. Why 2 routers (default_content_deploy.export_download and default_content_deploy.export)?
I think it can be combined.

kevinfunk’s picture

kevinfunk
he/him
commented

1. The patch does not apply
2. Why did you add the default_content_deploy.settings.yml file?
You can use the getContentEntityTypes method of the DeployManager class
3. Why 2 routers (default_content_deploy.export_download and default_content_deploy.export)?
I think it can be combined.

  1. Yeah, it needs a reroll with the latest changes. My composer file is set to drupal/default_content_deploy": "1.x-dev#97ea1ae as 1.x-dev" right now. I'll work on it as soon as I can.
  2. I need a way to limit the entity types shown on the export list but have to option to show more if needed. See Limited export and Update export list
  3. You're right. I can and should be one.

Default Content Deploy is an integral part of my workflow and I plan to give back as much as possible.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue tags: +Needs reroll
miroslav-lee’s picture

miroslav-lee
Location Krakow
commented
Status: Needs work » Fixed

Default Content Deploy is an integral part of my workflow and I plan to give back as much as possible.

@kevinfunk That's great!
I plan to develop this module as much as possible.

In the last commit, I implemented export from the admin panel and upload it to the archive.
It remains to implement the import from this archive. And it will be ready very soon.

I invite you to our slack channel.
There we will be able to discuss this module in a fast format.

  • miroslav-lee committed e77ea7c on 8.x-1.x 
    Issue #3070222 by thursday_bw, kevinfunk, miroslav-lee, ivnish,...
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue tags: -Needs reroll

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

dexiecarla’s picture

dexiecarla commented

Patch #8 cant be applied to latest version.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

@dexiecarla The 8.x-1.0-beta2 version doesn't need the patch, as it has been created after the patch was committed.