Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package creation with -recurse childitems #1323

Closed
PunjabSoftSolution opened this issue Mar 12, 2024 · 2 comments
Closed

Package creation with -recurse childitems #1323

PunjabSoftSolution opened this issue Mar 12, 2024 · 2 comments
Assignees
Milestone

Comments

@PunjabSoftSolution
Copy link

Expected Behavior
Package size should remain same with -recurse keyword.

Please describe the expected behavior.
When creating a package with Get-ChildItem -Path "master:/content/home", the package is created as expected. However, when using the -Recurse keyword, the package size doubles. Upon opening the package to investigate the difference, I observed that each folder item appears twice. Please investigate this issue. Thank you in advance.

Get-ChildItem -Path "master:/content/home" - This command works as expected.

Get-ChildItem -Path "master:/content/home" -Recurse - This command increases the package size to double. For example, if the package size is 1 MB with the top query, using this query results in a package size of 2 MB because it adds the same item twice in the folder.

Sitecore version 10.3 and SPE version 6.4.

@michaellwest
Copy link
Member

Can you provide a functioning script to reproduce the issue that works with the default home item? Perhaps a package with the test content too.

@michaellwest michaellwest added this to the User Support milestone Mar 12, 2024
@michaellwest michaellwest self-assigned this Mar 12, 2024
@AdamNaj
Copy link
Member

AdamNaj commented Jul 25, 2024

Those cmdlets are a thin coat over Sitecore APIs.
Closing as this seems like a problem with a clear workaround and a wrong usage of existing functionality rather than a bug + lack of reported response makes it unlikely that we will deal with it.

@AdamNaj AdamNaj closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants