Learn More





Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...beware module "copy to all pages" bug with dnn 7.4 multi language localisationbeware module "copy to all pages" bug with dnn 7.4 multi language localisation
New Post
2/16/2015 11:45 AM

I noted dNN7.4.0 had some new localisation features, so I thought now would be good to see if the bug with "copy to all pages" on localized sites  raised last year had been fixed.

The answer is "no" and for the record here is the result of our tests today.

When building a DNN site, we normally have standard content that appears on all pages like a "contact us" box, "footer links", header  "phone number call now" etc. For simplicity we use the "copy to all pages" feature on the module settings to apply this content automatically on all existing and all new pages as they are created.

With multi-lingual sites, there is an extra degree of complexity that this "all page" content needs to be localised to each language.

 The new version of DNN 7.4.0 includes new features for localization so we tested it today. We set up an out of the box vanilla DNN 7.4 site. We created 1 extra page and localised the site to 4 languages. Works like a dream.

On the new localised page we added an HTML module on the UK Default language page and applied the "copy to all pages" setting on the module. As expected the "content" was copied to ALL  "UK" language pages only.  We then went to the "new page" on the FR version of site. We added an HTML module with French content. Again we ticked the "copy to all pages" and as hoped the content is copied to ALL French language pages only.

By completing the task for the other 2 languages, we end up with a multilingual site, in which the footers, headers and common content appear on all pages, but translated to the correct language with no duplication or errors.

Well done DNN - all this works perfectly.

 Now the bug........

 If we add another "new page 2" to the site, the key page localisation works fine, but the localised "copy to all pages" content from the UK default language side of the site is automatically copied over to the other 3 non-default language pages and NONE of the non-UK language localised content with "copy to all pages" appears on ANY of the non-default localised pages - or indeed the default page.

Ideally we would want the "copy to all pages" localised UK content to appear on UK localized page of the "new page 2" only  and  the "copy to all pages" localised FR content to appear on FR localized page of the "new page 2 only etc.

So adding a new page, now requires deletion of 5/6 modules from a non-default language page and manually adding 16-20 localised content modules copied over from another same language page. (very time consuming and error prone)

 The situation gets worse as the DNN 7.4 site becomes unstable.

 If you try to "untick" the "copy to all pages " feature on any non-default language content you get a DNN error

Message:Object reference not set to an instance of an object.
InnerMessage:Object reference not set to an instance of an object.
   at DotNetNuke.Entities.Tabs.TabChangeTracker.TrackModuleUncopy(ModuleInfo module, Int32 moduleVersion, Int32 originalTabId, Int32 userId)
   at DotNetNuke.Entities.Modules.ModuleController.UncopyModule(Int32 tabId, Int32 moduleId, Boolean softDelete, Int32 originalTabId)
   at DotNetNuke.Entities.Modules.ModuleController.DeleteAllModules(Int32 moduleId, Int32 tabId, List`1 fromTabs, Boolean softDelete, Boolean includeCurrent, Boolean deleteBaseModule)
   at DotNetNuke.Modules.Admin.Modules.ModuleSettingsPage.OnUpdateClick(Object sender, EventArgs e)

 Saying that the The change is applied. If you then re-recheck the box the "localised content" appears correctly across all pages in the chosen language.

Of note, having set up the above test environment and created several test pages, we decided to delete all pages and start again.  Having used the "copy to all pages" feature must have caused some inner corruptions, as the "empty recycle bin" does not work. We could delete pages and modules one at a time by accessing recycle bin on a per language basis and removing the pages and modules one at a time. (the order does matter - we got there by trial and error).

 My recommendation is do not use the "Copy to all Pages" feature in DNN7.4 with multi-lingual localisized sites.

 If someone has a suggested workaround - would be pleased to hear solutions. We have looked at using "template"   pages, but I cannot see how we get the non-default language templates to be applied under localization.

 John Warr


New Post
2/16/2015 12:33 PM
DNN-26183 had been closed and marked as duplicate of DNN-26056, which has been closed as fixed in DNN 7.3.2.
As far as I can read from your statement, the issue described in DNN-26056 has been fixed. Obviously you discovered another issue with localized modules on all pages, which needs to be logged in, so the developers may fix it.
There are other issues in DNN 7.4.0 regarding localization, the "Object reference not set to an instance of an object" might suffer from same cause as DNN-6601, but I'd ask you to log it as a separate issue and refer to DNN-6601, to get the fix tested for your situation as well.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...beware module "copy to all pages" bug with dnn 7.4 multi language localisationbeware module "copy to all pages" bug with dnn 7.4 multi language localisation

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out