diff --git a/_config.yml b/_config.yml index 78727e9efe..56772ae980 100644 --- a/_config.yml +++ b/_config.yml @@ -1050,9 +1050,6 @@ navigation: "licensing": title: "Redistribution" position: 5 - "upgrade": - title: "Upgrade" - position: 6 "wpflab": title: "WPF Labs" position: 0 diff --git a/upgrade/images/upgrade-migrate-to-net-0.png b/getting-started/images/upgrade-migrate-to-net-0.png similarity index 100% rename from upgrade/images/upgrade-migrate-to-net-0.png rename to getting-started/images/upgrade-migrate-to-net-0.png diff --git a/upgrade/images/upgrade-migrate-to-net-1.png b/getting-started/images/upgrade-migrate-to-net-1.png similarity index 100% rename from upgrade/images/upgrade-migrate-to-net-1.png rename to getting-started/images/upgrade-migrate-to-net-1.png diff --git a/upgrade/images/upgrade-migrate-to-net-2.png b/getting-started/images/upgrade-migrate-to-net-2.png similarity index 100% rename from upgrade/images/upgrade-migrate-to-net-2.png rename to getting-started/images/upgrade-migrate-to-net-2.png diff --git a/upgrade/images/upgrade-migrate-to-net-3.png b/getting-started/images/upgrade-migrate-to-net-3.png similarity index 100% rename from upgrade/images/upgrade-migrate-to-net-3.png rename to getting-started/images/upgrade-migrate-to-net-3.png diff --git a/getting-started/installation/download-product-files-wpf.md b/getting-started/installation/download-product-files-wpf.md index a180e231e4..03b5de02bb 100644 --- a/getting-started/installation/download-product-files-wpf.md +++ b/getting-started/installation/download-product-files-wpf.md @@ -42,29 +42,25 @@ Below you could find a list of the available files separated by category. ## Available Files -The following section lists the files that can be download from the Telerik UI for WPF download page. The download separates the files in several categories - "Installation", "Other Setup Files", "Documentation", "Resources" and "Source Code". +The following section lists the files that can be downloaded from the Telerik UI for WPF download page. The download separates the files in several categories - "Installation", "Other Setup Files", "Documentation", "Resources" and "Source Code". -The following placeholder words will be used in the list to omit the need to add the concrete license type or product version: - -* `[license]`—Could be Trial or Dev depending on the license you have. - -* `[version]`—Replaces the version the file corresponds to. For example: "2024_2_423". +The `[version]` placeholder words will be used in the list to omit the need to add the concrete product version. #### Installation -* `Telerik_UI_for_WPF_[version]_[license].msi`—Automatic installation, check [Installing Telerik UI for WPF from MSI file]({%slug installation-installing-from-msi-wpf%}) for more details. +* `Telerik_UI_for_WPF_[version].msi`—Automatic installation, check [Installing Telerik UI for WPF from MSI file]({%slug installation-installing-from-msi-wpf%}) for more details. #### Other Setup Files -* `Telerik_UI_for_WPF_[version]_[license]_Dlls.zip`—Used for manual installation, for more details check [Installing Telerik UI for WPF from ZIP file]({%slug installation-installing-from-zip-wpf%}). +* `Telerik_UI_for_WPF_[version]_Dlls.zip`—Used for manual installation, for more details check [Installing Telerik UI for WPF from ZIP file]({%slug installation-installing-from-zip-wpf%}). * `Telerik_UI_for_WPF_[version]_Themes.zip`—Contains two folders containing the default styles and templates for the controls when using the [Xaml and NoXaml]({%slug xaml-vs-noxaml%}). -* `Telerik_UI_for_WPF_[version]_[license]_PDBs.zip` -* `Telerik_UI_for_WPF_[version]_[license]\_NuGet_Xaml.zip` -* `Telerik_UI_for_WPF_[version]_[license]\_NuGet_NoXaml.zip` -* `Telerik_UI_for_WPF_[version]_[license]\_NuGet_Separate_Packages_Xaml.zip` -* `Telerik_UI_for_WPF_[version]_[license]\_NuGet_Separate_Packages_NoXaml.zip` +* `Telerik_UI_for_WPF_[version]_PDBs.zip` +* `Telerik_UI_for_WPF_[version]_NuGet_Xaml.zip` +* `Telerik_UI_for_WPF_[version]_NuGet_NoXaml.zip` +* `Telerik_UI_for_WPF_[version]_NuGet_Separate_Packages_Xaml.zip` +* `Telerik_UI_for_WPF_[version]_NuGet_Separate_Packages_NoXaml.zip` -In versions prior Q1 2024, there is a .zip file with digitally signed version of the Telerik assembles - __Telerik_UI_for_WPF_[version]_[license]_Hotfix_DIGITALLY_SIGNED.zip__. With the Q1 2024 release __all Telerik dlls are digitally signed__ and there is no need of a separate package, which is why this .zip is no longer distributed. +In versions prior Q1 2024, there is a .zip file with digitally signed version of the Telerik assembles - __Telerik_UI_for_WPF_[version]_Hotfix_DIGITALLY_SIGNED.zip__. With the Q1 2024 release __all Telerik dlls are digitally signed__ and there is no need of a separate package, which is why this .zip is no longer distributed. >Check [Setting a theme]({%slug styling-apperance-implicit-styles-overview%}) topic for more information on the Xaml and NoXaml binaries. @@ -81,12 +77,12 @@ This section contains the offline help documentation as well as the API Referenc You could download the complete source code of the Telerik [WPF Demos application]({%slug installing-wpf-demos %}) as well as the provided sample applications. -* `Telerik_UI_for_WPF_[version]_[license]_Demos.msi` +* `Telerik_UI_for_WPF_[version]_Demos.msi` * `Telerik_UI_for_WPF_[version]_Demos_Source.zip` -* `CRM_WPF_[version]_[license]_Source.zip` -* `OutlookInspiredApp_WPF_[version]_[license]_Source.zip` -* `ColorThemeGenerator_WPF_[version]_[license]_Source.zip` -* `ERP_WPF_[version]_[license]_Source.zip` +* `CRM_WPF_[version]_Source.zip` +* `OutlookInspiredApp_WPF_[version]_Source.zip` +* `ColorThemeGenerator_WPF_[version]_Source.zip` +* `ERP_WPF_[version]_Source.zip` ### Source Code diff --git a/getting-started/installation/images/installation-installing-license-limitations-0.png b/getting-started/installation/images/installation-installing-license-limitations-0.png index 7718741422..bc846e4a8d 100644 Binary files a/getting-started/installation/images/installation-installing-license-limitations-0.png and b/getting-started/installation/images/installation-installing-license-limitations-0.png differ diff --git a/getting-started/installation/images/installation-installing-license-limitations-1.png b/getting-started/installation/images/installation-installing-license-limitations-1.png new file mode 100644 index 0000000000..0da9212f60 Binary files /dev/null and b/getting-started/installation/images/installation-installing-license-limitations-1.png differ diff --git a/getting-started/installation/installation-installing-license-limitations-wpf.md b/getting-started/installation/installation-installing-license-limitations-wpf.md index da5305e99f..670d311654 100644 --- a/getting-started/installation/installation-installing-license-limitations-wpf.md +++ b/getting-started/installation/installation-installing-license-limitations-wpf.md @@ -11,27 +11,19 @@ site_name: WPF # Trial License Limitations -The following topic will explain you the main differences between the licenses available for the Telerik UI for WPF and the limitations of the __Trial License__. +The following topic explains the main differences between the licenses available for Telerik UI for WPF and the limitations of the __Trial__ license. -Currently there are two types of licenses used for UI for WPF: +Currently there are two main types of licenses used for UI for WPF - __Developer__ and __Trial__. The license is applied through a license key installed on the developer's machine. See how to install a license key in the corresponding [help article]({%slug installing-license-key%}). -* __Developer License__ +The free __Trial__ license of Telerik UI for WPF gives access to all functionalities of the product and it will work for an unlimited time. However, once the trial period expires a trial message banner along with a watermakr overlay will be displayed. -* __Trial License__ +During the active trial the following popup will display on startup of the application. -## Developer License +![A picture showing the trial message dialon](images/installation-installing-license-limitations-0.png) -Developer licenses come with modified DLLs, which work without license keys. If you have a Developer license for one or more of the Telerik components, you only need to ensure that you are using the developer build when downloading the control(s). These builds have the __Dev__ abbreviation in their file names. +After the trial expires, the following message box and watermark overlay are displayed. -If your application is displaying a license key error, this means that you are using a trial version of the product. Log in to your [telerik.com](https://www.telerik.com/account/) account and download the developer build. To update your project, please take a look at the [Upgrading Trial to Developer License]({%slug installation-upgrading-from-trial-to-developer-license-wpf%})article. To get a license key, see the [Installing License Key]({%slug installing-license-key%}) article. - -## Trial License - -The free trial licenses of all Telerik products are fully functional and will work for an unlimited time but with a trial message displayed in a popup dialog and a watermark overlay banner that is displayed until the dialog is closed. - -The trial message states that the application uses a trial version of Telerik UI for WPF and prompts you to purchase a developer license. - -![A picture showing the trial warning dialong and the watermark](images/installation-installing-license-limitations-0.png) +![A picture showing the trial warning and watermark overlay](images/installation-installing-license-limitations-1.png) ## See Also * [Adding UI for WPF to the Visual Studio Toolbox]({%slug installation-adding-to-vs-2015-toolbox-wpf%}) diff --git a/getting-started/licensing/images/license-activation-errors-and-warnings-2.png b/getting-started/licensing/images/license-activation-errors-and-warnings-2.png new file mode 100644 index 0000000000..75b192bca1 Binary files /dev/null and b/getting-started/licensing/images/license-activation-errors-and-warnings-2.png differ diff --git a/getting-started/licensing/installing-license-to-ci-services.md b/getting-started/licensing/installing-license-to-ci-services.md index 2f93f6f7d1..a83a9d788b 100644 --- a/getting-started/licensing/installing-license-to-ci-services.md +++ b/getting-started/licensing/installing-license-to-ci-services.md @@ -48,11 +48,10 @@ The recommended approach for providing your license key to the `Telerik.Licensin 1. After running `npm install` or `yarn`, add a build step to activate the license: - #### __[YML]__ - {{region installing-license-to-ci-services-0}} + ```YML env: TELERIK_LICENSE: ${{ "{{ secrets.TELERIK_LICENSE }}" }} - {{endregion}} + ``` ## See Also * [License Activation Errors and Warnings]({%slug license-activation-errors-and-warnings%}) diff --git a/getting-started/licensing/license-activation-errors-and-warnings.md b/getting-started/licensing/license-activation-errors-and-warnings.md index 084ed0b931..8cb24ea2a2 100644 --- a/getting-started/licensing/license-activation-errors-and-warnings.md +++ b/getting-started/licensing/license-activation-errors-and-warnings.md @@ -18,6 +18,8 @@ A missing, expired, or invalid license will result in: * A modal dialog appearing on application startup. Clicking the __OK__ button of the dialog closes the dialog and removes the banner until the next application startup. + ![A picture showing the watermark and dialog that occurs when no valid license can be found](images/license-activation-errors-and-warnings-2.png) + * A warning message similar to the following appearing in the build log: ![A picture showing the license key errors in the Visual Studio Error List pane](images/license-activation-errors-and-warnings-0.png) @@ -46,12 +48,14 @@ When using Telerik UI for WPF in a project with an expired or missing license, t | Condition or Error | Message Code | Solution | | ------------------ | ------------ | -------- | -| `No license key is detected` | TKL002 | [Install a license key]({%slug installing-license-key%}) to activate the UI components and remove the error message. | -| `Invalid license key` | TKL003 | [Download a new license key]({%slug installing-license-key%}#downloading-the-license-key) and install it to activate the UI components and remove the error message. | -| `Your subscription license has expired.` | TKL103; TKL104 | Renew your subscription and [download a new license key]({%slug installing-license-key%}#downloading-the-license-key). | -| `Your perpetual license is invalid.` | TKL102 | You are using a product version released outside the validity period of your perpetual license. To remove the error message, do either of the following: | -| `Your trial license has expired.` | TKL105 | Purchase a commercial license to continue using the product. | -| `Your license is not valid for the detected product(s).` | TKL101 | Review the purchase options for the listed products. Alternatively, remove the references to the listed packages from `package.json.` | +| `No Telerik and Kendo UI License file found` | TKL002 | [Install a license key]({%slug installing-license-key%}) to activate the UI components and remove the error message. | +| `Corrupted Telerik and Kendo UI License Key content` | TKL003 | [Download a new license key]({%slug installing-license-key%}#downloading-the-license-key) and install it to activate the UI components and remove the error message. | +| `Unable to locate licenses for all products` | TKL004 | Your license is not valid for all Telerik and Kendo products added to your project. If you have already purchased the required license, then [update your license key]({%slug installing-license-key%}#downloading-the-license-key). | +| `Telerik UI for WPF is not listed in your current license file` | TKL101 | Review the purchase options for the listed products. Alternatively, remove the references to the listed packages from `package.json.` | +| `Your perpetual license is invalid` | TKL102 | You are using a product version released outside the validity period of your perpetual license. To remove the error message, do either of the following: | +| `Your subscription license has expired` | TKL103; TKL104 | Renew your subscription and [download a new license key]({%slug installing-license-key%}#downloading-the-license-key). | +| `Your trial license has expired` | TKL105 | Purchase a commercial license to continue using the product. | +| `No Telerik or Kendo UI product references detected in project` | TKL001 | If you use Telerik products and see this message, update the `Telerik.Licensing` package to version 1.4.6 or later. If you do not use Telerik products, remove the `Telerik.Licensing` NuGet reference from your project. | ## See Also * [Setting Up Your License Key]({%slug installing-license-key%}) diff --git a/getting-started/licensing/license-frequently-asked-questions.md b/getting-started/licensing/license-frequently-asked-questions.md index f6e424eb51..1c4521f562 100644 --- a/getting-started/licensing/license-frequently-asked-questions.md +++ b/getting-started/licensing/license-frequently-asked-questions.md @@ -36,7 +36,13 @@ This depends on your license type. See the [Invalid License]({%slug license-activation-errors-and-warnings%}#invalid-license) section for more information. -* __Subscription licenses__ will prevent you from building the application with an expired license key. Deployed applications will continue to function normally. +* __Subscription licenses__ used in deployed applications will continue to function normally. However, the following will happen if you rebuild the application with an expired subscription license: + + * A watermark appears on application startup. + * A modal dialog appears on application startup. + * A warning message is logged in the build log. + + See the [Invalid License]({%slug license-activation-errors-and-warnings%}#invalid-license) section for more information. * __Trial licenses__ will prevent the applications from functioning normally once the trial period has expired. The following will happen if you try to build or run the application: diff --git a/getting-started/licensing/licensing-versions.md b/getting-started/licensing/licensing-versions.md index 69eda85db5..18ae314d79 100644 --- a/getting-started/licensing/licensing-versions.md +++ b/getting-started/licensing/licensing-versions.md @@ -14,7 +14,8 @@ The Telerik UI for WPF assemblies depend on a specific version of the `Telerik.L | Telerik.Licensing Version | UI for WPF Version
(From) | UI for WPF Version
(To) | | ------------------------- | ----------------------------- | ---------------------------- | -| 1.4.6 | 2025.1.211 (latest) | N/A | +| 1.4.6 | 2025.1.211 | 2025.1.211 | +| 1.6.5 | 2025.2.520 (latest) | N/A | ## See Also * [License Activation Errors and Warnings]({%slug license-activation-errors-and-warnings%}) diff --git a/upgrade/upgrade-migrate-to-net.md b/getting-started/upgrade-migrate-to-net.md similarity index 95% rename from upgrade/upgrade-migrate-to-net.md rename to getting-started/upgrade-migrate-to-net.md index dd2f9233e1..ddcb9110f2 100644 --- a/upgrade/upgrade-migrate-to-net.md +++ b/getting-started/upgrade-migrate-to-net.md @@ -5,7 +5,7 @@ description: Check how to migrate a Telerik's WPF application from .NET 4.0 or 4 slug: upgrade-migrate-to-net tags: upgrading,telerik,ui,trial,to,telerik,ui,developer,license,or,newer,version,netframework published: True -position: 1 +position: 3 --- # Project Migration to .NET 4.6.2 and .{{ site.minimum_net_core_version }} @@ -14,46 +14,48 @@ With the 2024 Q2 release (from May 2024), the Telerik UI for WPF product no long This article describes how to migrate to a newer version of .NET. -## Migrating from .NET Framework 4.0/4.5 to .NET Framework 4.6.2 +> In case you are using .NET Framework, we recommend upgrading to .NET 8 or later in order to take advantage of the easier project maintenance and general .NET performance optimizations. -There is no difference in the APIs between the different types of Telerik dlls, so you need to only change the __Target framework__ of the project and the referenced Telerik dlls. +## Migrating from .NET Core 3.1 to .{{ site.minimum_net_core_version }} -1. Download and install the corresponding [.NET Framework developer pack](https://dotnet.microsoft.com/en-us/download/dotnet-framework/net462) (4.6.2 or later). +There is no difference in the APIs between the different types of Telerik dlls, so you need to only change the `TargetFramework` setting of the project and the referenced Telerik dlls. + +1. Download and install the corresponding [.NET developer pack](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) (.{{ site.minimum_net_core_version }} or later). 2. Right click on the WPF project in Visual Studio and select the __Properties__ option from the context menu. - ![](images/upgrade-migrate-to-net-0.png) + ![](images/upgrade-migrate-to-net-2.png) -3. In the __Target framework__ menu, select __.NET Framework 4.6.2__ or later version and save the project file. +3. In the __Target framework__ menu, select __.{{ site.minimum_net_core_version }}__ or later version and save the project file. - ![](images/upgrade-migrate-to-net-1.png) + ![](images/upgrade-migrate-to-net-3.png) 4. Update the referenced Telerik assemblies using the preferred installation approach. For example, via [NuGet]({%slug nuget-installation%}) or the [.msi installer]({%slug installation-installing-from-msi-wpf%}). 5. You may need to manually delete the __bin__ and __obj__ folders before rebuilding the project in order to ensure that any Visual Studio assemblies cache is cleared. -## Migrating from .NET Core 3.1 to .{{ site.minimum_net_core_version }} +## Migrating from .NET Framework 4.0/4.5 to .{{ site.minimum_net_core_version }} -There is no difference in the APIs between the different types of Telerik dlls, so you need to only change the `TargetFramework` setting of the project and the referenced Telerik dlls. +To migrate from .NET Framework to .NET, you can create a new .{{ site.minimum_net_core_version }} (or later) project and include the corresponding files from the .NET Framework project. Then, [install the Telerik .NET assemblies]({%slug installation-installing-which-file-do-i-need%}) in the new project. This approach is described in more detail in the [Migrating to .NET]({%slug netcore-support-migration%}) article. -1. Download and install the corresponding [.NET developer pack](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) (.{{ site.minimum_net_core_version }} or later). +## Migrating from .NET Framework 4.0/4.5 to .NET Framework 4.6.2 + +There is no difference in the APIs between the different types of Telerik dlls, so you need to only change the __Target framework__ of the project and the referenced Telerik dlls. + +1. Download and install the corresponding [.NET Framework developer pack](https://dotnet.microsoft.com/en-us/download/dotnet-framework/net462) (4.6.2 or later). 2. Right click on the WPF project in Visual Studio and select the __Properties__ option from the context menu. - ![](images/upgrade-migrate-to-net-2.png) + ![](images/upgrade-migrate-to-net-0.png) -3. In the __Target framework__ menu, select __.{{ site.minimum_net_core_version }}__ or later version and save the project file. +3. In the __Target framework__ menu, select __.NET Framework 4.6.2__ or later version and save the project file. - ![](images/upgrade-migrate-to-net-3.png) + ![](images/upgrade-migrate-to-net-1.png) 4. Update the referenced Telerik assemblies using the preferred installation approach. For example, via [NuGet]({%slug nuget-installation%}) or the [.msi installer]({%slug installation-installing-from-msi-wpf%}). 5. You may need to manually delete the __bin__ and __obj__ folders before rebuilding the project in order to ensure that any Visual Studio assemblies cache is cleared. -## Migrating from .NET Framework 4.0/4.5 to .{{ site.minimum_net_core_version }} - -To migrate from .NET Framework to .NET, you can create a new .{{ site.minimum_net_core_version }} (or later) project and include the corresponding files from the .NET Framework project. Then, [install the Telerik .NET assemblies]({%slug installation-installing-which-file-do-i-need%}) in the new project. This approach is described in more detail in the [Migrating to .NET]({%slug netcore-support-migration%}) article. - ## See Also * [Overview of porting from .NET Framework to .NET](https://learn.microsoft.com/en-us/dotnet/core/porting/) * [Migrate to .NET Framework 4.8, 4.7, and 4.6.2](https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/) \ No newline at end of file diff --git a/upgrade/images/Common_Installing_TrialVersionDescription_WPF.png b/upgrade/images/Common_Installing_TrialVersionDescription_WPF.png deleted file mode 100644 index 85be803991..0000000000 Binary files a/upgrade/images/Common_Installing_TrialVersionDescription_WPF.png and /dev/null differ diff --git a/upgrade/installation-upgrading-from-trial-to-developer-license-wpf.md b/upgrade/installation-upgrading-from-trial-to-developer-license-wpf.md deleted file mode 100644 index 4fde398ae8..0000000000 --- a/upgrade/installation-upgrading-from-trial-to-developer-license-wpf.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Upgrading Trial to Developer License or Newer Version -page_title: Upgrading Telerik UI Trial to Developer License -description: Check how you can upgrade your Trial assemblies to Telerik UI Developer License. -slug: installation-upgrading-from-trial-to-developer-license-wpf -tags: upgrading,telerik,ui,trial,to,telerik,ui,developer,license,or,newer,version -published: True -position: 0 -site_name: WPF ---- - -# Upgrading Telerik UI for WPF Trial to Developer License - -This article describes how to upgrade your Telerik references from trial to developer version. - -To upgrade you will need to replace the Telerik dlls referenced in the project and setup a license key. This can happen using any of the available [installation approaches]({%slug installation-installing-which-file-do-i-need%}). - -1. Install the new version of the Telerik UI for WPF product. - - * If you use assembly references in the project, you can [use the .msi installer]({%slug installation-installing-from-msi-wpf%}) or the [.zip archive with the dlls]({%slug installation-installing-from-zip-wpf%}). You can find these on the [Telerik UI for WPF download page](https://www.telerik.com/account/product-download?product=RCWPF). - - * If you are [using NuGet packages]({%slug nuget-package-source-setup%}), you can replace the Telerik NuGet packages that ends with `.Trial` with the ones which doesn't contain the trial postfix. For example: - - #### __[XML] Trial NuGet package__ - {{region installation-upgrading-from-trial-to-developer-license-0}} - - - - {{endregion}} - - #### __[XML] Developer NuGet package__ - {{region installation-upgrading-from-trial-to-developer-license-1}} - - - - {{endregion}} - - * If you prefer to use the __Visual Studio Extension__, you can use the automatic [Upgrade Wizard]({%slug radcontrols-for-wpf-vs-extensions-upgrading%}) which will allow you to download the developer licensed dlls and also to install a license key. - -2. [Download and install a license key]({%slug installing-license-key%}) in the Telerik's folder in the AppData directory or in the project's folder. - -3. If you hit any errors related to missing Telerik references, make sure that all required Telerik dlls (for the used UI components) are referenced, and also that all referenced Telerik dlls use the same version (ex: 2025.1.212). Additionally, you can delete the `bin` and `obj` folders of the project, and then Clean and Rebuild the project, in order to ensure that any project cache is cleaned. - -## Checking the Assemblies' Version - -To check what type of license the binaries you're using have, you can check the **Properties** of the **Telerik.Windows.Controls.dll** file. **Only this file** contains information for the dlls version in its metadata. To get this information use the following steps: - -1. Right click on the Telerik.Windows.Controls.dll file and select the __Properties__ options from the context menu. -2. Go to the __Details__ tab in the Properties window. -3. Check the __File description__ attribute. It will contain the **"Trial Version"** suffix if the dlls are trial. Otherwise, there will be only the dll's name. - -__Telerik.Windows.Controls.dll Properties__ - -![Telerik.Windows.Controls.dll Properties](images/Common_Installing_TrialVersionDescription_WPF.png) - -If your dll files contain this suffix in the description then they are of the trial version and you have to replace them with the licensed assemblies. - -## See Also - - * [Controls Dependencies]({%slug installation-installing-controls-dependencies-wpf%}) diff --git a/urlrewriter.config b/urlrewriter.config index 943e624a0c..e9701533d7 100644 --- a/urlrewriter.config +++ b/urlrewriter.config @@ -606,4 +606,6 @@ + +