Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Adding content staging to an existing site
Hello,
I'm working on a Liferay 6.1.20 EE environment that hosts ~150 sites and we're investigating enabling Content Staging on the majority of these sites. After reading through the user guide I saw that the recommendation is to only enable staging on new sites and ..."if you have already created a large amount of content you might not be able to enable staging on that site". I'd like to understand more about what's behind this statement. What is considered a large amount of content? What specific factors should we consider? Would the impact be a performance hit only to the initial setup of the staging copy or more broad than that?
There's a large disparity in the number of pages we have on each site (10-200 pages each) I'd just like to understand if/where we may have issues when turning this on.
Thanks!
-Jason
I'm working on a Liferay 6.1.20 EE environment that hosts ~150 sites and we're investigating enabling Content Staging on the majority of these sites. After reading through the user guide I saw that the recommendation is to only enable staging on new sites and ..."if you have already created a large amount of content you might not be able to enable staging on that site". I'd like to understand more about what's behind this statement. What is considered a large amount of content? What specific factors should we consider? Would the impact be a performance hit only to the initial setup of the staging copy or more broad than that?
There's a large disparity in the number of pages we have on each site (10-200 pages each) I'd just like to understand if/where we may have issues when turning this on.
Thanks!
-Jason
When you enable staging, Liferay must sweep through and duplicate all content (one for the staging side and one for the prod side). The more content you have, the longer this will take. And, of course, errors could arise that may be prohibitive if the logic for the staging has difficulty handling the split.
I don't know if this is a valid example, but consider if you have two web content articles pointed at the same image; when the logic is duplicating the first content it should duplicate the image (so you get the staging support). But when it comes time to duplicate the second content, what happens then? It's very own duplicate of the image, or will the system be able to find the staging image that was previously created?
Like I said, this may not be a good example of a possible failure because I haven't actually tried it. But it should point out, however, how this duplication process can lead to all kinds of odd outcomes.
I don't know if this is a valid example, but consider if you have two web content articles pointed at the same image; when the logic is duplicating the first content it should duplicate the image (so you get the staging support). But when it comes time to duplicate the second content, what happens then? It's very own duplicate of the image, or will the system be able to find the staging image that was previously created?
Like I said, this may not be a good example of a possible failure because I haven't actually tried it. But it should point out, however, how this duplication process can lead to all kinds of odd outcomes.
Good to know, thanks David. FWIW, based on some offline conversations, it sounds like Liferay carries out this staging by doing LAR export/imports behind the scenes.
Community
Company
Feedback