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

Publishing renamed folder wrongly publishes subresources as well #632

Closed
kartobi opened this issue Feb 20, 2019 · 4 comments
Closed

Publishing renamed folder wrongly publishes subresources as well #632

kartobi opened this issue Feb 20, 2019 · 4 comments

Comments

@kartobi
Copy link
Contributor

kartobi commented Feb 20, 2019

Whenever a published folder gots renamed and published, all resources in that folder get published recursively, even if "Publish resources in folder" is not checked.

To repoduce in OpenCms 11_beta:

  1. Create folder, subfolder and index.html; just publish folder (subfolder and index.html still have state "new"):
    image
  2. Rename folder to folder-renamed and direct publish just this folder:
    image
  3. Subfolder and its index.html is published afterwards as well:
    image
    image
@gWestenberger
Copy link
Contributor

This is intentional. Renaming a folder means changing the paths for all resources underneath it, so if any of these resources already exist in the Online project (have been published previously), they need to be published so their paths get updated in the Online tables. In your case, this doesn't seem to make sense because all of the sub-resources are new, but currently the system does not make any distinction between resource states in this case.

@kartobi
Copy link
Contributor Author

kartobi commented Feb 21, 2019

It works when publishing "folder" when it is new (subfolders don't get published).
Just is buggy when "folder" had been published before.

A behaviour that is quite critical for us, as new resources must not be published when changeing a parent folder.

And as there's no possibility to "unpublish" resources, what would be a solution for this bug?

@kartobi
Copy link
Contributor Author

kartobi commented Jul 23, 2019

Any help on this problem/bug here?

@gWestenberger
Copy link
Contributor

Improved in branch_11_0_x: New subresources of moved folders are not automatically published any more.

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

2 participants