Views: 4832
Number of votes: 0
Average rating:

Problem with constructing PageReferences in Page Providers

Recently I have spent some time implementing page providers for a customer. A couple of days ago I noticed that one of the page providers started to behave strange for one particular PageId. The PageReference for that page had RemoteSite set to null instead of the page providers ProviderKey. This means that the PageReference will point on a page in the LocalPageProvider rather than on my page in my custom page provider. After some investigation it was clear that this particular PageReference was equal to the PageReference of the page providers EntryPoint.

The problem seemed to be related to constructing the PageReference which was handled by the PageProviderBase.ConstructPageReference methods. Reflecting these methods with Reflector made it clear that PageReferences are constructed with RemoteSite set to ProviderKey only if PageId is not equal to EntryPoint.ID. The workaround is to construct the PageReference yourself and always set the ProviderKey part. Be careful though when you are constructing ParentLink for top-level pages because it in these cases is located on the LocalPageProvider.

Feb 08, 2010

(By jb, 9/21/2010 12:33:05 PM)

The reason for the behaviour for ConstructPageReference is to construct correct ParentLink for first level pages (that is children to entry point).
However this has shown to be confusing so in CMS6 we have added a new method ConstructLocalPageReference that always set RemoteSite part to ProviderKey.

(By morten.petersen, 9/21/2010 12:33:05 PM)

Is there a solution or workaround for this? My PageProvider works fine, except when creating a new element. When leaving NewPage.aspx the parentid is unfortunately translated to a LocalPageProvider id. Ie. '1__PositionProvider' is translated to '1'

Please login to comment.