where is the export directory?

It is exporting from entities to configuration
You have to export your configuration to be able to commit the changes etc

drush @site cex

thank you @louis-cuny

i did a cex in dev and it did generate structure_sync.data.yml

i took following to staging:
block.block.header_content.yml
block.block.workingforyou.yml
block.block.homepagevideo.yml
structure_sync.data.yml

and ran drush @mysite config:import in staging.

Import the listed configuration changes? (yes/no) [yes]:
> yes

[warning] The "block_content:f1b676ae-e826-4f05-a9cb-65f09e01cf03" was not found
[notice] Synchronized configuration: create block.block.header_content.

[warning] The "block_content:7c3ff773-a3cf-428f-ab46-4b6b2b417dd3" was not found
[notice] Synchronized configuration: create block.block.workingforyou.

[warning] The "block_content:f77fa748-663e-4fbd-ad56-e68318333044" was not found
[notice] Synchronized configuration: create block.block.homepagevideo.

[notice] Synchronized configuration: update structure_sync.data.
[notice] Finalizing configuration synchronization.
[success] The configuration was imported successfully.

but i don't see the new custom blocks on the staging site.
am i missing something obvious?

The exported config did export correctly to structure_sync.data.yml
When importing in staging, with drush cim you are only importing the config, not the actual blocks, taxonomies etc

You need additionnaly to drush ib for blocks for example

This is not a bug, I close the issue

thanks again,
now i am stuck behind php_8.1 issues:
#1 ($value) must be of type Countable|array, null given in count() (line 343 of /var/www/web/modules/contrib/structure_sync/src/Controller/BlocksController.php)
I'll check the issue queue ...

Hi @louis-cuny ,
Thank you for answring my questions.
I owe you a documentation patch:

Thank you, I will review your patch

The exported config did export correctly to structure_sync.data.yml
When importing in staging, with drush cim you are only importing the config, not the actual blocks, taxonomies etc

You need additionally to drush ib for blocks for example

Can you explain this further? Are you saying that it's in the config table of the database? Can you please explain how to export this export one it's run? Also, is there a reason it's not saved to a file?

@salientknight
Yes
It's the design choice of this module to use configurations

You can export your configs in Back office Config/Development/Export Config
Or with drush cex

@salientknight
Yes
It's the design choice of this module to use configurations

You can export your configs in Back office Config/Development/Export Config
Or with drush cex

@ccarnnia
Could you use the Merge Request tools for your patch please ? It will be easier for us to review

💬 Export Menu Not Working Closed: works as designed provides another example of the confusion raised in this ticket; mentioning here for reference when reviewing the patch

I reviewed the patch and it is applying properly. Thanks @ccarnnia. Added typo correction and line breaks in the patch.
please review.

Structure Sync is using Drupal's default storage location of the sync directory → , except if it's overridden by the user.

For the export and import process, see https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →

Updated the title to reflect that this has changed from a support request to a feature request.

I'm going to ignore the patch in #12: it changes the README.md back to a README.txt format, which isn't helpful; and thus I am not going to grant credit for #12. Please refer the documentation on Abuse of the Contribution Credit System for more information → .

I have created a merge request from the patch in #6.

I accidentally pushed the commit to 2.x HEAD in commit 2caf7e0 then reverted it in be23c4b - sorry for the noise.