Hi Johan!

This would be a problem with the current implemention of EPiFields.

We did some work to get EPiFields own pagereference safe for mirroring, but that wont take care of any pagereferences the adapters maintains themselves.

But, it seems to me as if your adapter should render a linklist based on a PageReference, for example by listing children to the page.

If this is the case, I'd suggest you to instead of maintaining the PageId yourself, simply make the PageAdapter work for "any selected page" by simply overriding the method ActivateForPage and return true if the passed in PageReference is not EmptyReference.

By doing this, your adapter would appear in the list of available adapters when user selects a page in the tree, and your PageAdapter code then simply uses the property CurrentPageReference which will point to the page the user selected when adding the field.

This CurrentPageReference will be exported / imported correctly during mirroring (if you applied the latest hotfixes to both episerver 4 and epifields).

Regards,
Johan

Me again,

Heres the link to the EPiFields hotfix:
http://www.episerverworld.com/Download/Items/Hotfixes/EPiServer-CMS-461---EPiFields---Hotfix-1/

/johan

I'm not sure I'm following, does this mean that the Page where I insert the EPiField-linklist will have to serve as the container for the LinkList as well? If this is the case, it kind of defeats the purpouse with beeing able to have several different Link-lists in the same page since these lists then will be merged to one. Am I understanding this correctly?

 I have been giving it some thought and I think I may have found a plausible solution:

 I'll give all pagetypes a guid property and upon fetching the PageCreated event give them all a unique guid. I'll use this guid when saving the Link-list container in the EPiFields and then search on this pageproperty instead of pageid. This will definitly be much slower, but it should at least conserve this id through mirroring I guess. This should work, right?

> I'm not sure I'm following, does this mean that the Page where I insert the EPiField-linklist will have to serve as the container for the LinkList as well?

No, the page that you *insert* through epifields acts as the container.

Consider for example the following scenario:

1. Webeditor is editing Page A
2. Webeditor selects EPiField  dialogbox and from its navigation tree selects Page B
3. Webeditor selects your PageAdapter from the list of available adapters
4. Webeditor then clicks ok, and the epifieldobject is inserted

Now, Page B will act as the container for the linklist.

This would however require your pageadapter to be available regardless of what page(type) is selected, and that can be done as I said by overriding the ActivateForPage method.

Regards,
Johan