Releasing a folder from content creator
Author: Srinivasarao_Ko
Publication Date: 12/21/2016 5:18
Hi,
Good morning.
we are using FS 5.2. we can release folders and pages from the siteArchitect. But from the Content Creator we can only release the pages. we dont have option to release the folders. Sometimes we are having a scenario to release the folder. So I wanted to know why folders can not be released from CC. is there any specific reason for that or it will be in future releases.
Anyone have idean on this pls comment here. Thanks.
Regards,
Srinivas.
Tags: contentcreator
-
Author: kohlbrecher - 12/21/2016 12:58
Hi Srinivas,
I think the main reason is explained here:
Actions on page objects: Unlike in SiteArchitect, the editor is largely unaware of the divisions between the individual stores in ContentCreator. As a result, editors see the page, page reference, referenced media, and datasets for a preview page as a single unit. In SiteArchitect, by contrast, these object types can be edited individually in the stores.
There would be many problems if the folder would be released automatically.
Can you give us some more details about your scenario? May a workflow can fix your problem.
Best regards
Jan
0 -
Author: Srinivasarao_Ko - 12/22/2016 4:18
Hello Jan,
Thanks for the reply. The scenario is editor can edit navigation of site. after editing the navigation he/she is expecting to release the same from CC.
Regards,
Srinivas.
0 -
Author: marza - 1/4/2017 10:53
Hi Srinivas,
this problem of yours is handled by the BasicWorkflows FirstSpirit module available at GitHub as source code. Using BasicWorklfows allows to release in CC at the same time elements from page and site store and make sure that the parent chain is intact.
Tipp: you can get a binary release of BasicWorkflows at our tech support for free.
If you have feature requests you can implement them yourself or modify and build the module to your (project) needs. Of cause pull requests are welcome if they are for common use.
Regards,
Marian
0 -
Author: tenter - 1/18/2017 15:53
Hello Srinivas,
do you need further help or did Marian's reply already help you? If so, it would be great if you marked his reply as "correct answer" so that other community users find the solution easily. If you have already found another solution by yourself, it would be very kind of you, if you posted it here.
Regards,
Hannes
0 -
Author: liam_davison - 1/24/2017 9:41
We have also had similar problems, particularly when moving pages in the navigation. The pages themselves don't change, so don't need re-releasing. But the folders are deleted-and-created during a move, and that needs a release. In our case, this broke publishing to JBoss Portal Platform and rendered our site unnavigable for several days.
I'd consider it a bug/failing of FirstSpirit not to ensure that the Page/PageFolder/PageRef/PageRefFolder are not kept in sync, especially as there is no way in ContentCreator to see that a PageFolder or PageRefFolder is not released when its Page/PageRef is.
Liam Davison
0 -
Author: pavone - 1/27/2017 13:05
Hello Liam,
if you move Pages or PageRefs, FirstSpirit considers them being changed (they should appear red in the tree view in the SiteArchitect). Therefore you do need to re-release them. If you're using AccessUtils.release, you can tell FirstSpirit to make sure that the element is accessible (that parent elements are released as well). You just need to set the 'ensureAccessibility' parameter to 'true'.
As Marian mentioned, the BasicWorkflows do this and should solve your problem. This module also implements a WebeditElementStatusProviderPlugin that checks if the parent is released as well. If not, you'll see this in the ContentCreator.
Regards,
Tim
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
6 Kommentare