Problem with export of content items

Dejan Caric

Vote:

Hi,

I'm using EPiServer 7.5.394.2

On some page types, I have the following property:

[CultureSpecific]
[BackingType(typeof(PropertyUrl))]
[Display(Name = "Website", Order = 210)]
public virtual Url WebsiteUrl { get; set; }

In edit mode, if I leave WebsiteUrl empty, export works fine. If I select an external link, then I get the following exception during export:

The following warnings have been generated:
[Exporting content 457] Failed to export property WebsiteUrl, exception: Object reference not set to an instance of an object.

Any suggestions?

#84696

Apr 04, 2014 14:36

Johan Björnfot

Vote:

I have reported a bug for this. The issue is that at during export it compares the url with SiteDefinition.Current.SiteUrl. And since the export package is created in a background thread it has no httpContext to resolve SiteDefintion from. It will then try to fallback to the SiteDefintion with wildcard host '*' but if no such host mapping exist it will get back a SiteDefintion where SiteUrl is null which cause the exception.

So a workaround for you is to add host '*' to any of your sites (in admin mode under "Manage WebSites".

#84766

Apr 07, 2014 13:19

Dejan Caric

Vote:

Hi Johan,

Unfortunately, I can't use this workaround because the client has purchased the license for only one website. I'm getting the following message under 'Manage Websites':

The number of licensed sites 1 has been reached, no more sites can be added without upgrading the license.

#84775

Apr 07, 2014 14:40

Johan Björnfot

Vote:

You do not have to create any new site. Just click Add under host section on your existing site, and fill in '*'.

#84778

Apr 07, 2014 14:42

Dejan Caric

Vote:

Ah, of course. Thanks.

That did the trick but now I'm getting another error message:

[Exporting content 269] Property "FacebookPage" has a value that is not a well formed URI: "http://www.facebook.com/pages/Ernö/190076057674790?fref=ts"

#84779

Apr 07, 2014 14:48

Johan Björnfot

Vote:

That should be just a warning message, the package should be ok anyway.

#84785

Apr 07, 2014 15:25

Dejan Caric

Vote:

Thanks!

#84790

Apr 07, 2014 16:15

Per Bjurström

Vote:

Fix released in EPiServer.CMS.Core 7.7.0

http://world.episerver.com/Documentation/Release-Notes/ReleaseNote/?releaseNoteId=113675

#85523

Apr 29, 2014 9:24