Ok, reply from DropIT was not so fun
Aparantly this is a bug in 2.6* that never got fixed before moving to 3.x so its not possible to move data between websites. Lucky we are not talking about hundreds of pages!
I only hope that there is support for it when upgrading to EPiServer 5. Does anyone know if the upgrade program written by EPi takes into consideration pages with extensions 2.x content? Would really love to hear if it does.
I got a very interesting upgrade project next year if it doesnt - this is a very complex enterprise solution with extension 2.x, imagevault 2.x and siteseeker that will all need upgrading. Cant wait to be honest!
/John
We have a site built on Episerver 4.5 and Extension 2.3 I think it is. I haven't heard of this "upgrade program" your talking about but according to DropIT there is no way to upgrade Extension 2.x to X3... I guess this is because 2.x uses it's entierly own database tables to store data and X3 stores it's data as episerver pages in the database.
I have a site with version 4.61.2.83 - just writing that makes me wonder if upgrading to .5 might fix this issue - however in the same thought I know that I have had similar problems on another 4.61.5 website running a similar setup for the same customer.
I hope anyway, that there is someone out there that still remembers 4.6x and extensions 2.6.2461.61102 and can shed a little light on this little problem. Could a simple upgrade to 2.7 fix this? - As I write this I await a phone call from DropIT support - so in the meantime here is the problem in full:
The problem is actually 2 fold, the 2nd part of which occured today during a live transfer of pages created from the test server to the production server - a simple export and import - or so I thought:
Problem 1 - copying a page that is created with exension 2.x and pasting the page anywhere in the tree creates an error in the top left section of the edit-mode. The frame that normally holds the buttons etc (eg dynamic properties etc)
This error is:
What is odd is that the copy/paste actually works. If i reload the page I see the newly copied page exists and seems to contain all the correct data. Not so much of a big deal but still irritating.
Problem 2 - exporting and importing pages or even tested with a single page with extensions functions doesnt work. When copying a bunch of pages the error I was get is:
When importing a single page I can get it to work without giving me an error but when I look at the created page there is no extensions content!! its empty!
The source and destination webs are actually copy of the same database originally so there shouldnt be any mismatches in pagetypes or properties missing etc - we set it up just so the customer could create new content on the test server and play around with some of the settings before publishing them to the production server.
Anybody got any clues what is going on? - Old bug in extensions maybe?
/John