This is my target
=> use content_sync to export few nodes from A site, and Import these nodes into B site
This is how I encountered the problem
1) I use composer to download content_sync:2.x-dev
2) I go to /admin/modules to enable content_sync
3) drupal will enable the content_sync
4) drupal will export full site
5) due to there are some test contents in my A site(maybe there is wrong data in these content....), full site export will falt
But there is no wrong data in the nodes that I want to export, they are perfect.
So I delete the code of step 4) in "content_sync.install" file.
Hope this patch could help someone who has the same problem with me.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | content_sync-disable_export_aflter_install-3114243-3.patch | 432 bytes | shin.cho |
Comments
Comment #2
shin.cho commentedComment #3
shin.cho commentedthere is the patch.
Comment #4
guiu.rocafort.ferrerI am not completely sure I understand the issue.
If i am not mistaken, what you are describing is:
1. You enable content_sync through the UI.
2. The existing content snapshot is generated ( this is not an export, what content_sync is doing is create a current content snapshot in the database. This is what i believe you call "4) drupal will export full site"
3. Exporting full site content will fail.
The provided patch will disable the initial content snapshot generation. If you then make a full site content export, it would export no content at all. This suggest that there may be some issues with the existing content in Drupal instance.
Can you provide more info about the particular errors ?
Have you set the folder configuration variable in settings.php ? ( $content_directories ).
Marking this as needs more info because the issue cannot be properly reproduced.
Comment #5
blanca.esqueda commentedProbably @shin.cho is talking about export site using the UI option, the one that generates the entire site zip.
That one doesn't need the snapshot I think...
Comment #6
bluegeek9 commentedHello,
I found this issue looking for a way to disable the initial export when enabling the module. From the other replies it seems that it is building a current snapshot, not exporting content.
The batch begins executing after the module is installed, and the title of the page reads "Exporting content". Maybe the title can be change to something else, like "Building Snapshot".
Comment #7
shin.cho commented@guiu.rocafort.ferrer #4
Thank you for your replay!
I'm afraid I cannot provide detal-information about the error.
Because I deleted the TEST-Enviroment in my local.
What I want to say in this issue is
I don't think this is a good idea to 「Make a full site snapshot when Admin install content_sync through UI.」
Because It's not flexable to those guys who just want export few contents from A-Drupal to B-Drupal.
@bluegeek9 #6
I'm agree with you about change the title string from "Exporting content" to "Building Snapshot".
This is the reason that I used the wrong word 「 Full Site Export 」in this issuse title.
Comment #8
blanca.esqueda commentedUpdated the title string for the snapshot export to "Building Snapshot", commit included on 3.0.x-dev.
Marking this task as the part to remove the snapshot creation outside the install will be committed as part of another issue:
https://www.drupal.org/project/content_sync/issues/2979368
Comment #10
blanca.esqueda commented