Hello,

Is there any way I can disable Content Localization altogether? I added 5 languages on top of the default one for testing purposes.

Disabling languages has not fixed the problems that came along with activating Content Localization.

I have a module that is displayed on all pages, that used to work fine  when I did not have content localization enabled.

Now I can't create new pages, because every time I try to add a new page, or copy an existing page, that module gets multiplied by 150 times or more on the same page, one below the other. (might be the number of pages on the site, I haven't tried counting them because i have +150 pages)

To make maters worse, I can't delete it from Recycle Bin either, because I get a timeout error.

If disabling Content Localization proves to be too difficult, is there a way of forcing DNN to do the Content Localization activation procedure, copying all the pages in my current default language to the other languages? (maybe fiddling with the DB)

The content localization activation has been don under DNN5. I want to give it another shot under DNN6.

Thanks!

Hi Sebastian,

Yeah, I expected it to be difficult. I noticed there are some serious issues when enabling content localization on a portal that has modules with "visible on all pages" enabled. I'm going to manually reference the modules instead. 

What about forcing DNN to recreate the content in the other pages? Is there a StoredProcedure I can call in the DB?

I can see a EnsureLocalizationExists SP and a InsertPortalLocalization SP. Can I/ should I attempt to use those?

I noticed there is a PortalLocalization Table and in PortalSettings table there is a SettingName called ContentLocalizationEnabled. Any chance I can accomplish anything by altering those values? 

Thanks!