[CQ5] - Publisher enviornment is having stale/old content | Adobe Higher Education
Skip to main content
N
niks1
Level 2
April 2, 2021
解決済み

[CQ5] - Publisher enviornment is having stale/old content

  • April 2, 2021
  • 1 の返信
  • 1685 ビュー

Due to some reason , we need to bring our few publisher down. Now when i am trying to bring those back it is having old data or stale data which was published before we brought them down.

 

Can you please help me, how we can have the latest data on the publisher server.

 

Also, how i can setup parallel author instance and move content from one server to other.

このトピックへの返信は締め切られました。
ベストアンサー bilal_ahmad

Hey @niks1 you need to republish that content(if you know the pages/paths/assets) again.

 

If you don't know the exact path(s) then you may need to run query to figure out the content (cq:Page/dam:Asset etc) which got added/modified and ten create a package using the same script(from groovyscript) and then getting it installed on publish server. I have not mentioned replicating those pages through programmatically replicating them because if the number of paths are way too many then it might slow down your instance(too many in replication queue), so I'd recommend creating a package and installing it on publish.

 

One drawback would be - that you'd end up losing the version in package creation.

 

Thanks,

Bilal.

1 の返信

bilal_ahmad
bilal_ahmad回答
Level 5
April 2, 2021

Hey @niks1 you need to republish that content(if you know the pages/paths/assets) again.

 

If you don't know the exact path(s) then you may need to run query to figure out the content (cq:Page/dam:Asset etc) which got added/modified and ten create a package using the same script(from groovyscript) and then getting it installed on publish server. I have not mentioned replicating those pages through programmatically replicating them because if the number of paths are way too many then it might slow down your instance(too many in replication queue), so I'd recommend creating a package and installing it on publish.

 

One drawback would be - that you'd end up losing the version in package creation.

 

Thanks,

Bilal.

    bilal_ahmad
    bilal_ahmad
    Level 5
    April 19, 2021

    Hi @niks1 for pages that got published on/after 1'Oct 2020 you can replace the existing query in the snippet I provided with this:

     

    SELECT * FROM [cq:Page] AS page WHERE ISDESCENDANTNODE ([/content]) AND page.[cq:lastReplicated] >= CAST("2020-10-01T00:00:00.000+05:30" AS DATE) ORDER BY page.[cq:lastReplicated] DESC

     

     

    It worked for me.

     

    Thanks,

    Bilal.

    契約条件Accessibility statement

    Loading footer...