if anyone has experienced and found a solution on this any help would be appreciated.
I have done some investigations, and it looks like the problem is caused by the way composer functions are associated with pages – composer doesn’t show any errors to the user, but using a custom tool to read the PageStructure of the affected page, it displays an exception caused by an incorrect DataFactory.Instance.GetPage call, e.g.:
Page 1864_4839 was not found
The 1864_4839 combination refers to a composer function which is associated with the affected page. Needless to say, page 1864 exists but version 4839 is not there…
Does anyone know how to find a solution (even a reactive one) to these errors, like rebinding the page-function association to an existing version of the function?
Hi all,
if anyone has experienced and found a solution on this any help would be appreciated.
I have done some investigations, and it looks like the problem is caused by the way composer functions are associated with pages – composer doesn’t show any errors to the user, but using a custom tool to read the PageStructure of the affected page, it displays an exception caused by an incorrect DataFactory.Instance.GetPage call, e.g.:
Page 1864_4839 was not found
The 1864_4839 combination refers to a composer function which is associated with the affected page. Needless to say, page 1864 exists but version 4839 is not there…
Does anyone know how to find a solution (even a reactive one) to these errors, like rebinding the page-function association to an existing version of the function?
EPiServer 6R2 + Composer 4R2
Many thanks
Fabio