Today, after a long wait, PageLocalization 5.0 was released today. This version only supports DotNetNuke 5.0 and up. At the same time PageLocalization 3.0 is still available for sale, for everyone who has not upgraded to DNN 5.0 (the majority of my customers at this moment i think)

So, whats changed in this version?

• DotNetNuke 5 contains a few breaking changes compared to DNN 4, which cause PageLocalization 3.0 to fail in DNN 5. These issues were resolved.
• The DNN 5 caching mechanism was used to cache localized cache objects resulting in better performance.
• Major overhaul of included skinobjects, to bring them up to speed with current DNN versions. Most skinobjects use NavObjectBase now, resulting in simpler skinobject definitions. I’ve created my own NavObjectBase implementation, which inherits from the DNN core NavObjectBase and adds localization to it. You can now easily add localization support for your own navigation skinobjects (provided you already inherit from NavObjectBase) by just changing the inheritance to Apollo.DNN_Localization.Navigation
• DNN 5 packaged module. By its nature this version of the module cannot be installed in DNN 4 (i have not and will not test what happens if you do that.. I suggest you do the same ;) ). Packaging was a bit of an issue as some of the DNN 5 packaging options are not completely documented yet.
• New sample skin. The dowload package now contains a new sample skin, which is a modification of the DNN 5 default skin. By its nature the skin uses DNN NavMenu (Or rather its inherited version: Apollo MLNavMenu)

Anyhow, the module can be downloaded from SnowCovered. If you buy PageLocalization 3.0, version 5.0 should be free for you (I’ve added a 100% discount for PL 3.0 customers), also, if you buy PageLocalization 5.0, version 3.0 should be free for you.

(edit: originaly i linked to a post i thought was about DNN caching enhancements, which turned out to be an old post about dnn 4.4 enhancements. I will keep trying to find a correct link (if there is any), and update this post accordingly)

(edit2: any questions about the usage of this module will be deleted here, please use our forums instead!)