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

HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...Localization across the site through SQLLocalization across the site through SQL
Previous
 
Next
New Post
8/13/2013 6:53 PM
 

We are trying to Localize all of the content on our website as a whole by exporting all the website content in the HTMLTEXT table and pair it with the corresponding language and location on the site per text object, modifying/translating what we need, then importing it back into the database. We're having to write a query that filters out the older versions of the text objects, and that links to two other tables (TabModules and Tabs) to get the language and the location. 

We think we got the information all together in the same table, but we're seeing multiple duplicates of text objects that are technically the same modules but that all have different tab names and different langauges. In the end, we don't quite understand the correct relationships between the tables, or what all the different terms mean (e.g. ModuleID, TabID, ItemID).

These are my questions:

First of all, is this even a feasible process, or are we better off sticking to manual modifications within the admin console?

What relationship does ItemID, or TabID have with the website?

Is Module ID the ID for the modules in the website, or does module in the database refer to something different? (if it is referring to the same thing, how do we filter out the modules that are primarily for the htmltext?)

Is there a better relationship we should use to query these tables?

Is there a schematics available for the SQL DB with DNN?

We don't expect answers for all of these. They are just questions we have. If there are answers, please pass them on to us!

 
New Post
8/14/2013 4:20 AM
 

tab = page, module = HTML instance, tabmodule = reference for a module instance on a page. ModuleId should be your unique key.

HTML modules will all have same ModuleDefId (see moduleDefinitions table).

Be aware, that HTML may store multiple versions of your content (depending on your settings).


Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/22/2013 6:16 PM
 

Is there a way to make it so the Database doesn't keep the older versions of the modules? I know that would be risky in case we ever wanted to restore from a previous version :O.   But by removing them, it could make it a lot easier to carry out this process we want to create.

 
New Post
8/23/2013 4:27 AM
 
You should be save to run a sql statement, which keeps latest version only. Make sure, to backup your database first, perform the delete, restart the app pool and test the website function, prior to proceeding.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...Localization across the site through SQLLocalization across the site through SQL


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

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.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out