Thanks for the quick answer Scott.Actually, since the replication agent is gone, how can I delete the queue? I looked for it in the job queue configurations, I cannot find it.We first thought that by disabling the replication agent it might also disable the job queues, but no. We still got the logs ...

We have this strange problem.  We had a flush cache replication agent on the author. It was disabled. But the associated job queue still accumulate a lot of job, these job obviously failed, and they seem to retry again and again.Here's a log entry:10.04.2015 00:00:29.640 *ERROR* [pool-6-thread-18-co...

When a tag is deleted on the author instance, it automatically gets removed from the publish instances.  I wanted to know if this was the normal behaviour? I haven't found documentation on this.Thanks.

Why, on my instances, don't I have access to the package share section?I have a 404 on /crx/packageshare/

will do. can you point me to where I should go to do such a thing? thanks.

Is there a tool OOTB (or not) to automate the purge of package versions, a bit like the content pages/assets?We have quite a few packages that are hefty, and they have been upgraded multiple times.  So I guess all these packages versions take space, tight? Thanks,JS.

thanks. we finally found out it was a resource resolver mapping that was interfering with the replication.

Although I have replication setup between author and a publish instance, when I activate something, it tells me the operation was successful, but nothing gets written on the publish instance.How can that be?  the transport user is «admin».When I launch the replication test, it tells me it succeeded....

... is this the intended behavior, or did I miss something?In the case where those links aren't getting updated, I guess I should then write my own rollout config?Thank you.

we had this working in 5.6:{ "jcr:primaryType": "sling:Mapping", "jcr:createdBy": "admin", "jcr:created": "Thu Jun 12 2014 21:19:45 GMT-0400", "sling:match": "55.55.55.55.4503", "sling:internalRedirect": "/content/oursite" }I would have expected that if we access: http://55.55.55.55:4503/en/home.htm...