Hi Kautuk, how exactly this answers my question?

Hi Carey, unfortunately that was exactly how I created the link. The steps to reproduce are:IN PRODUCTION VERSION:1. Create two pages under the same node - 'Page A' and 'Page B'2. Add text component to Page A. Create a link using hyperlink dialog and use content finder to point link to Page B. No ty...

Hi All, I create content in the launch copy of the page and place a hyperlink to another page from the same launch. when launch is promoted, the link still points to the launch version of the page. Is there a solution to this issue? Regards,Nikolai

Logged as Admin, so there should be no ACL issues.No errors. New page promoted OK, just not added to a package. Launch pages that already had live copy source were added to package successfully.Is that a known defect? 

Hi all, I create new page in a launch, so there is no production copy. When I promote launch I add pages to a workflow package. My new page is promoted but not added to a package. Does anyone know solution to this?Regards,Nikolai

Thanks Jorg,Are you aware of the way to control permissions to annotations? Regards,Nikolai

Thanks Jorg,I see that works if user keeps numbering manually. As soon as you create a version without label it will be another 1.xx.I wonder is there way to make a true major version of the content, combined with publishing or launch?Regards, Nikolai

but not a 'major' version. The version numbering continues as 1.xx not 2.0

Hi, with page versions, how can I create a new major version, i.e 2.0 or 3.0?Thanks 

I reckon the question is - on what jcr node the ACL should be set? it definitely not on of the /content nodes.