Url Master Compatibility with DNN 7.4: What You Need to Know

Url Master Compatibility with DNN 7.4: What You Need to Know

The release of DotNetNuke (DNN) 7.4 introduced important changes to performance, multilingual handling, and system extensibility. For site administrators and developers using the iFinity Url Master module, understanding the compatibility updates is essential for a stable upgrade.

DNN 7.4 includes changes to the internal URL handling system, which may affect advanced rewriting logic. Fortunately, Url Master remains compatible, but certain environments—especially those using custom modules—should test thoroughly post-upgrade.

Key Compatibility Notes:

  • Core DNN changes in 7.4 affect how URLs are parsed and rewritten, which may impact older Url Master settings.
  • Some host-level configurations may need to be reset after applying the update.
  • Any overrides in web.config or custom URL patterns should be reviewed.

Upgrade Recommendations:
Before upgrading, back up your site and database, and apply the update in a staging environment. Disable third-party extensions temporarily, reinstall the latest Url Master version after the update, and clear the DNN cache before testing.

Thorough testing is critical to ensure that friendly URLs and redirects behave as expected.

Conclusion:
DNN 7.4 introduces several improvements, and Url Master continues to provide reliable functionality for managing clean URLs and redirects. However, given the architectural changes, a careful, staged rollout is essential to avoid disruption.

Using iFinity Url Master with DNN 7.3 A Technical Overview

Using iFinity Url Master with DNN 7.3: A Technical Overview

DNN 7.3 delivered a number of internal platform improvements aimed at performance and stability. These updates included enhancements to how portal aliases and site routing are processed. For sites using the iFinity Url Master module, it’s important to review its interaction with the new DNN routing engine.

The 7.3 release refined alias resolution and the internal handling of friendly URLs, especially for multi-portal configurations. Url Master continues to function reliably, but administrators should review any custom rewrite logic post-upgrade.

What’s Improved with DNN 7.3:

  • Better portal alias matching across multilingual setups.
  • Reduced reliance on legacy redirect methods.
  • Improved error logging and diagnostics, offering better visibility when debugging URLs.

Recommended Actions for Site Owners:

  • Review your portal alias configuration.
  • Check for duplicate or outdated rewrite rules.
  • Monitor for new 404 or redirect loops after upgrading.
  • Test with both clean and parameterised URLs.

Conclusion:
DNN 7.3 provides a more stable foundation for content management, and Url Master remains a useful tool for SEO-optimised URLs. By conducting proper testing and validation, your site can continue running cleanly with minimal disruption.

iFinity Url Master Module Retirement What It Means for Your DNN Website

iFinity Url Master Module Retirement: What It Means for Your DNN Website

In April 2014, we officially announced the retirement of the iFinity Url Master module. After many years of supporting clean URL rewriting and SEO control in DotNetNuke (DNN), the product has reached end-of-life and will no longer be updated or supported.

Why Was Url Master Retired?
The DNN platform has evolved significantly, with built-in routing features that now support most of the capabilities previously handled by Url Master. Rather than maintain a separate codebase, we’ve chosen to allow the module to sunset and focus our efforts on future-forward solutions.

What This Means for Current Users:

  • You may continue using Url Master with existing DNN versions, but no further patches or compatibility fixes will be released.
  • Newer versions of DNN are not officially supported and may break existing Url Master functionality.
  • Official support is discontinued, though archived documentation remains available.

Migration and Alternative Solutions:

  • Review your current URL rewriting logic and export all rules.
  • Evaluate the built-in Friendly URL Provider introduced in later DNN versions.
  • For complex routing needs, consider custom URL providers or working with a DNN consultant.
  • Avoid updating DNN core versions without validating Url Master behaviour in staging first.

Final Thoughts:
The Url Master module has served the DNN community for many years and helped thousands of websites achieve better SEO and usability. While the product is being retired, your website doesn’t need to lose those benefits. With planning and the right tools, you can continue to manage friendly URLs and redirects effectively going forward.