Hi Sebastian,
I have just tried this again, accessing the site on the webserver itself.
When I clicked the Enable Content Localization link, the pop up opened, and I clicked the enable button. The pop up refreshed and then more or less straight away froze.
In the event log I had the following event details:
/Admin/Languages/tabid/47/ctl/EnableContent/mid/365/Default.aspx?popUp=true&RadUrid=72a46173-03b7-4a24-9317-65391eb4ecde
System.Threading.ThreadAbortException: Thread was being aborted.
at DotNetNuke.Modules.Blog.Business.InterfaceController.ExportModule(Int32 ModuleID)
at DotNetNuke.Entities.Modules.ModuleController.LocalizeModuleInternal(ModuleInfo sourceModule)
followed by
/Admin/Languages/tabid/47/ctl/EnableContent/mid/365/Default.aspx?popUp=true&RadUrid=72a46173-03b7-4a24-9317-65391eb4ecde
System.Threading.ThreadAbortException: Thread was being aborted.
at System.String.Concat(String str0, String str1)
at DotNetNuke.Modules.Blog.Business.InterfaceController.ExportModule(Int32 ModuleID)
The site has the standard blog module version 4.01 present.
I have now reverted to the my backup, but would really like to get this resolved.
Cheers,
Ian