[PUBLISHING-39] Former multisite-publishing behavior is not implemented: Publishing specific websites to dedicated public instances Created: 05/Feb/18 Updated: 29/Mar/22 Resolved: 21/Aug/18 |
|
| Status: | Closed |
| Project: | Publishing |
| Component/s: | None |
| Affects Version/s: | 1.0, 1.0.1 |
| Fix Version/s: | 1.0.6 |
| Type: | Bug | Priority: | High |
| Reporter: | Christian Ringele | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Epic Link: | Support | ||||||||||||||||
| Sprint: | Kromeriz 159 | ||||||||||||||||
| Story Points: | 5 | ||||||||||||||||
| Team: | |||||||||||||||||
| Description |
| Comments |
| Comment by Christian Ringele [ 03/Apr/18 ] |
|
mdrapela Form my testing I can tell you following: "The true setting [for \{{excluded}}] excludes the configured fromPath from publication. This property allows you to define exceptions such as "Publish everything in the website workspace except the about node and everything under it." -> this is true, BUT: If setting excluded=false then the whole configuration is ignored and treated as you would set enabled=false. So one case is not defined, and the system does not react to it, and to be honest I have no clue what this situation should be:
Or in other words:
The whole property excluded doesn't make any sense to me and form the tested behavior. |
| Comment by Christian Ringele [ 02/Aug/18 ] |
|
Yesterday I had another thought about the possible configuration (related to my last comment). I think this would be the most clear, easy to understand and most natural configuration and its behavior: Publish everything of a workspaceThe configuration:concreteReceiver -> does automatically behave like: Test result:Correct: Currently the system behaves this way. Publishing only a specific path/websiteThe configuration:concreteReceiver Test result:Bug: The system currently does NOT behave this way Exclude a complete workspaceThe configuration:concreteReceiver Test result:Currently the system behaves this way. Bug found on publication status and publication Action behavior: Workflow activation (Pages App): Direct activation (JCR App):
Suggested behavior: The 'publish Action' is not clickable Publish a workspace EXCEPT one path/websiteThe configuration:concreteReceiver Test result:Correct: Currently the system behaves this way. |
| Comment by Rajeev Singh [ 02/Aug/18 ] |
|
Hi Christian, Your most recent comment makes it a little bit easier. So, does the configs/properties work as you mentioned above or it is a proposal ?? Plz, comment. I must say this new property excluded is actually very confusing. Regards, |
| Comment by Christian Ringele [ 03/Aug/18 ] |
|
Hi rajeevsingh I have just updated my comment above. Regards, |
| Comment by Rajeev Singh [ 03/Aug/18 ] |
|
Hello Christian, most of the combinations work for me and thanks for the update. Reagards |
| Comment by Rajeev Singh [ 03/Aug/18 ] |
|
Ahhh, I see your updates, you have marked it as bug in comments. Let me know if you find solution for that. Thanks in advance. Regards, |
| Comment by Christian Ringele [ 05/Aug/18 ] |
|
Hi rajeevsingh, I have updated the ticket description and added all the information there, also the details of my last comment. Because we have seen that you, as a SLA3 customer has a problem with this bug, we now treat this ticket as it had an attached SLA3 support ticket in its priority of the back log. We will keep you informed if there is any change. Regards, Christian |
| Comment by Rajeev Singh [ 06/Aug/18 ] |
|
Hi Christian, Thank you for the updates on ticket info and example in comments. Example with 4 use cases makes it very clear. With this new concept we have to do lot of configurations mainly negate ones to exclude. But it is achievable. Just to add, my use case is, from assets workspace I used to publish specific content to some fronts(4 receivers) and whole assets from root to another set of receivers. I hope to have this fixed soon. Regards, |
| Comment by Rajeev Singh [ 07/Aug/18 ] |
|
Hi Christian; Should I be raising a separate support ticket or this( Regards, |
| Comment by Jan Haderka [ 17/Aug/18 ] |
|
regarding
This behaviour is consistent with previous implementation and will not be changed in bug fix ticket. If we are implementing this change, it would be feature request. |
| Comment by Milan Divilek [ 01/Oct/18 ] |
|
Release notes: Receive can be configured to publish only certain path(s) of the workspace. Set WorkspaceDefinition properties fromPath / toPath to /specificPath, workspace property to website and property excluded to false in receiver configuration. This receiver will publish only the /specificPath path of the website workspace and ignore the rest. |