Custom Modules

Re: epiFrame - With IE6, I cannot get any autowidth/height to work...

Kabelsalat — Sat, 15 Jul 2006 20:05:15 GMT

Did your try entering a relative source url?

epiFrame - With IE6, I cannot get any autowidth/height to work...

mjz — Sat, 15 Jul 2006 19:11:08 GMT

The frame always says Page Blocked. I've tried what i believe to be just about all combinations of settings, but once I check the autoresize height/width, the frame is blocked.

This is on DNN4.3

Any ideas? What have I missed?

Thanks!

Re: epiFrame - Advanced iFrame module

Kabelsalat — Sun, 04 Jun 2006 19:52:22 GMT

After taking a detailed look at the mentioned localization issue, I found out, that Leupold actually was right. However the Asp.Net localization can be tweaked easily to fit the DNN-Localization. This was what I did after discovering the problems. It works pretty fine, but requires a few core-changes, therefor I recommend everybody to use 1.2.x instead, but maybe the core team likes the changes I proposed (I have been sending a working example of a custom ResourceProviderFactory and other parts needed to adapt the Asp.Net localization to Leupold).

Re: epiFrame - Advanced iFrame module

Kabelsalat — Mon, 15 May 2006 16:12:02 GMT

I could not find any information about this feature in DotNetNuke Localization.pdf. As I do not know what it does and how it works I cannot test it. It would be kind, if you could provide me with further information on how this works and what I should test.

Re: epiFrame - Advanced iFrame module

leupold — Sun, 14 May 2006 12:27:58 GMT

I forgot to mention one DNN localization function, that was implemented to support the developer and is also annonced to be used in planned module certification: the "show missing keys" switch in web.config. I f turned on, it will indicate by a special prefix, which texts don't have a localization (this is also improved in upcoming DNN 3.3/4.1)

Re: epiFrame - Advanced iFrame module

Kabelsalat — Thu, 11 May 2006 18:45:31 GMT

In some sub-forums (and as it seems also this one) I'm unmoderated, but editing still isn't possible. However, this doesn't concern the topic...

... Yepp, you're right with saying DNN and Asp.Net localization features are competing, but this does not mean they would not work together. Actually both do exactly the same, only the code-base is different. Both use the same naming-convention, fallback-mechanisms are the same (per default) and the .resx files use the same format. This is the reason why I do not see any problems with using both, Asp.Net and DNN localization together. When looking at Library/Components/Localization/Localization.vb you'll notice that DNN is implementing localization mostly the same way as the new .Net 2 features do.

PS: I'm using the Asp.Net forums, since I started this thread here and because of the "real" DotNetNuke forums loading slower and being harder to read (the design isn't that clear). However, it seems like I'll be forced to move to the new forums...

Re: epiFrame - Advanced iFrame module

leupold — Thu, 11 May 2006 17:56:35 GMT

Kabelsalat:
Sorry for this tripple-post, but editing has been disabled a long time a go :(

AFAIK editing is limited to unmoderated users only. You need a couple of posts to get unmoderated. Notice, that the DotNetNuke forums on ASP.Net will be closed in the future (no date fixed yet), please use the forums on DotNetNuke.com for announcements and discussions.

Re: epiFrame - Advanced iFrame module

leupold — Thu, 11 May 2006 17:52:27 GMT

have you checked the output of the resource verifier as well and creating a new language. I know, there are areas, where the language editor can be bitchy.

Re: epiFrame - Advanced iFrame module

leupold — Thu, 11 May 2006 17:49:23 GMT

Kabelsalat,

being the most experienced DNN translator, maybe I should explain saome details of the localization concept of DotNetNuke:

The localization solution consists of components for implicit and explicit translation of strings used in the core and all modules. This part competes with ASP.Net 2.0 localization. Both use resx files to store the resource keys and values per language. AFAIK they have different naming conventions for files and maybe fallback mechanisms. The base language resource files are created in the developement environment.

For translators of the core or modules, there are the following tools: language editor, resource verifier, resource pack generator and resource pack installer.

The language editor is for creating and editing localized resource files. It adds missing keys and removes obsolete one and you can optionally highlight pending translations. you can also use the editor to create portal individual adoptions of the language files.

The resource verifier compares translated resource files with the original ones and reports missing or outdated files and missing or obsolete keys.

The resource pack generator creates a language pack for the complete installation, the core framework, one or multiple modules and providers. Each language pack is language specific.

The resource pack installer import a resource pack and places the files into existing folders. It reports files, tha cannot be installed e.g. because of not installed modules or providers.

As a conclusion, DNN comes with a full set of tools for efficient translation of DNN and its components into any language.

Re: epiFrame - Advanced iFrame module

Kabelsalat — Thu, 11 May 2006 17:35:36 GMT

Sorry for this tripple-post, but editing has been disabled a long time a go :(

-> Tested using DotNetNuke 4.0.3 + epiFrame 2.0.0

Re: epiFrame - Advanced iFrame module

Kabelsalat — Thu, 11 May 2006 17:34:12 GMT

Even with version 2.0.0 (Asp.Net localization), the language editor is able to identify all resources correctly... works like a charm :)

Re: epiFrame - Advanced iFrame module

Kabelsalat — Thu, 11 May 2006 17:23:47 GMT

I'll definitely give the Language Editor a try...

Btw: The module is already translated into german. This was done using GlobalResource (http://www.everylittlething.net/GlobalResource/).

Re: epiFrame - Advanced iFrame module

leupold — Thu, 11 May 2006 17:16:58 GMT

IMHO, you should test translating your module with the language editor, if you want users to be able to use your module outside English tongued countries. Note that it is sensitive regarding location and names of the files, as well as their internal structure.

Re: epiFrame - Advanced iFrame module

Kabelsalat — Thu, 11 May 2006 16:21:39 GMT

The answer is simple: I do like the Asp.Net localization features more and furthermore I didn't see any drawbacks at the beginning. Actually the only Contra-Aspect of the Asp.Net localization in combination with DotNetNuke I figured out till now, is that the default web.config disables the .resx BuildProvider which is neccessary to use Asp.Net localization. After reenabling it everything worked as desired and I wasn't able to notice any side-effects (see related bug-report mentioned in my previous post). Anyhow, requiring changes to the default web.config is always problematic for a module, therfor I made the 1.2.x-Version tree which only uses the localization features offered by DNN (additionally this made converting the module back to DNN3 somewhat easier).

PS: I never tested the integrated Language Editor, but I cannot imagine of any problems related to Asp.Net localization: Only the way the .resx files are accessed changes, not the files itself and what else does the Language Editor do than editing .resx files below the App_LocalResources folders?

Re: epiFrame - Advanced iFrame module

leupold — Thu, 11 May 2006 15:42:57 GMT

Kabelsalat,

can you please explain your reasons for using ASP.Net 2 localization in you 2.0 module? AFAIK this is not supported by the DNN built in language editor, so translator will need extra tools to create installable lanugage packs. Thank you.