Skip to content

Commit 58753dd

Browse files
kendo-botkendo-bot
committed
Sync with Kendo UI Professional
1 parent 1d62c78 commit 58753dd

File tree

8 files changed

+320
-16
lines changed

8 files changed

+320
-16
lines changed

‎docs-aspnet/installation/upgrading/upgrade-troubleshooting.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: Upgrade Troubleshooting
3+
page_title: Upgrade Troubleshooting
4+
description: "Learn how to troubleshoot your application if you encounter any issues when upgrading to new {{ site.product }} versions."
5+
slug: upgrade_aspnetcore_troubleshooting
6+
position: 3
7+
---
8+
9+
# Upgrade Troubleshooting
10+
11+
The new and improved versions of the UI components sometimes bring changes that require you to take additional steps during or after the upgrade.
12+
13+
This document describes how to troubleshoot your application and what to be wary of when upgrading to new {{ site.product }} releases.
14+
15+
## 2023 Yearly Releases
16+
17+
The issues listed below are common when upgrading to {{ site.product }} versions released in 2023. Follow the link next to each problem to find the solution.
18+
19+
* A `License Activation failed` warning appears in the browser's console, as a banner, and as a watermark for the components—The solution is [to generate a license file]({% slug remove-license-warning-message %}) that will remove the warning from the application.
20+
* The Kendo CDN links for the CSS and JS files are obsolete and you cannot access these files on `kendo.cdn.telerik.com`—These URLs have changed due to a shift in the naming convention and the solution is to [use the new URLs]({% slug cdn-naming-convention-change %}).
21+
* The files for the Less themes are missing after upgrading to a new {{ site.product }} version—The {{ site.product }} components [no longer support Less themes]({% slug missing-less-files %}) and Telerik recommends migrating to Sass-based themes.
22+
* Font icons are missing and their classes are not applied—Starting with version `R3 2023`, the {{ site.product }} UI components use SVG icons by default. Nevertheless, you can [revert to font icons]({% slug missing-font-icons %}).
23+
* The previously included jQuery CDN from Kendo is now missing with new versions—Starting with version `R3 2023`, the {{ site.product }} library has [discontinued shipment of the jQuery library](https://docs.telerik.com/{{ site.platform }}/installation/system-requirements/jquery-support).
24+
25+
## See Also
26+
27+
* [Telerik UI for {{ site.framework }} Breaking Changes]({%slug breakingchanges_2023%})
28+
* [Telerik UI for {{ site.framework }} Knowledge Base](https://docs.telerik.com/{{ site.platform }}/knowledge-base)

‎docs-aspnet/installation/upgrading/upgrade.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,14 @@ To upgrade your project with the Upgrade Project Wizard, refer to the following
112112
113113
## See Also
114114
115+
* [Upgrade Troubleshooting]({% slug upgrade_aspnetcore_troubleshooting %})
115116
* [Telerik UI for ASP.NET MVC Download and Installation]({% slug downloadinstall_aspnetcore %})
116117
* [Telerik UI for ASP.NET MVC Fundamentals]({% slug fundamentals_aspnetmvc %})
117118
118119
{% endif %}
120+
121+
122+
## See Also
123+
124+
* [Upgrade Troubleshooting]({% slug upgrade_aspnetcore_troubleshooting %})
125+
* [Telerik UI for ASP.NET Core Download and Installation]({% slug downloadinstall_aspnetcore %})

‎docs-aspnet/knowledge-base/cdn-naming-convention-change.md‎

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: CDN Naming Convention Change
3+
description: "Learn about the new CDN URLs naming convention changes for the required JavaScript and CSS resources in the {{ site.product }}."
4+
page_title: CDN Naming Convention Change
5+
slug: cdn-naming-convention-change
6+
tags: cdn, url, change, upgrade, troubleshoot, application, naming, convention
7+
res_type: kb
8+
---
9+
10+
## Environment
11+
12+
<table>
13+
<tr>
14+
<td>Product</td>
15+
<td>{{ site.product }}</td>
16+
</tr>
17+
<tr>
18+
<td>Progress {{ site.product }} version</td>
19+
<td>2023.1.314</td>
20+
</tr>
21+
</table>
22+
23+
## Description
24+
25+
26+
I was using the following Kendo JS and CSS links before upgrading {{ site.product }}:
27+
28+
```
29+
https://kendo.cdn.telerik.com/2022.2.802/styles/kendo.bootstrap-main.min.css
30+
```
31+
32+
However, as of the the latest `R1 2023 SP1` release, these resources seem to be obsolete. How can I reference the themes from the CDN?
33+
34+
## Solution
35+
36+
As of version `R1 2023 SP1`, the CDN has a new structure where it is composed of:
37+
38+
* Theme version&mdash;for example, `7.0.2`.
39+
* Theme name&mdash;for example, `default`, `bootstrap`, `material`, and so on.
40+
* File name&mdash;is the name of the theme.
41+
42+
The following example shows the new structure of the Kendo CDN resources:
43+
44+
```
45+
<link rel="stylesheet" href="https://kendo.cdn.telerik.com/themes/7.0.2/bootstrap/bootstrap-main.css" />
46+
```
47+
48+
## See Also
49+
50+
* [Upgrade Troubleshooting]({% slug upgrade_aspnetcore_troubleshooting %})
51+
* [Telerik UI for {{ site.framework }} Breaking Changes]({%slug breakingchanges_2023%})
52+
* [Telerik UI for {{ site.framework }} Knowledge Base](https://docs.telerik.com/{{ site.platform }}/knowledge-base)

‎docs-aspnet/knowledge-base/missing-font-icons.md‎

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
title: Missing Font Icons
3+
description: "Learn more about the new icon rendering and how to revert back to the old font icon rendering in a {{ site.product }} application."
4+
page_title: Missing Font Icons
5+
slug: missing-font-icons
6+
tags: font, icons, backward, compatibility, upgrade, troubleshoot, application, missing
7+
res_type: kb
8+
---
9+
10+
11+
## Environment
12+
13+
<table>
14+
<tr>
15+
<td>Product</td>
16+
<td>{{ site.product }}</td>
17+
</tr>
18+
<tr>
19+
<td>Progress {{ site.product }} version</td>
20+
<td>2023.1.314</td>
21+
</tr>
22+
</table>
23+
24+
25+
## Description
26+
27+
In some components, we often use commands with `IconClass()` to display icon buttons for the majority of the components. However, after updating we noticed that the font icon classes are no longer applied.
28+
29+
## Solution
30+
31+
As of the `R3 2023` release, the Telerik UI toolset supports rendering of SVG icons instead of the traditional Font icons.
32+
33+
Although the SVG icons are used as the predominant font toolset for the suite, this does not stop you from reverting to the Font icons:
34+
35+
{% if site.core %}
36+
* Configure the added server-side Kendo service in the `Program.cs` class:
37+
```
38+
builder.Services.AddKendo(options =>
39+
{
40+
options.IconType = Kendo.Mvc.IconType.Font;
41+
});
42+
```
43+
44+
{% else %}
45+
* Configure the added server-side Kendo service in the `Global.asax` class:
46+
```
47+
KendoMvc.Setup(x=>
48+
{
49+
x.IconType = IconType.Font;
50+
});
51+
```
52+
{% endif %}
53+
54+
* Invoke the `Html.Kendo().DefaultSettings()` method within the `_Layout.cshtml` of the application in order for the components to utilize font-icon rendering:
55+
56+
```
57+
@Html.Kendo().DefaultSettings()
58+
```
59+
60+
## See Also
61+
62+
* [Upgrade Troubleshooting]({% slug upgrade_aspnetcore_troubleshooting %})
63+
* [Telerik UI for {{ site.framework }} Breaking Changes]({%slug breakingchanges_2023%})
64+
* [Telerik UI for {{ site.framework }} Knowledge Base](https://docs.telerik.com/{{ site.platform }}/knowledge-base)

‎docs-aspnet/knowledge-base/missing-less-files.md‎

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
title: Missing Less files
3+
description: "Learn why the LESS Distribution files have become obsolete when upgrading to new {{ site.product }} versions."
4+
page_title: Missing Less files
5+
slug: missing-less-files
6+
tags: less, missing, files, structure, upgrade, troubleshoot, application
7+
res_type: kb
8+
---
9+
10+
## Environment
11+
12+
<table>
13+
<tr>
14+
<td>Product</td>
15+
<td>{{ site.product }}</td>
16+
</tr>
17+
<tr>
18+
<td>Progress {{ site.product }} version</td>
19+
<td>2023.1.314</td>
20+
</tr>
21+
</table>
22+
23+
24+
## Description
25+
26+
I am upgrading my project to a {{ site.product }} version later than `R1 2023 SP1`. Where can I find the `kendo.common.min.css` file and the `Images` folder of the distributions?
27+
28+
29+
## Solution
30+
31+
As of the {{ site.product }} `R1 2023 SP1` release, the {{ site.product }} components no longer support Less themes and they will no longer be shipped with the component distribution packages.
32+
33+
The `kendo.common.min.css` file and `Images` folder which were a part of the Less themes' distribution have also been deprecated.
34+
35+
Telerik recommends using Sass-based themes going forward as suggested in the [Less to Sass Theme Migration](https://docs.telerik.com/{{ site.platform }}/styles-and-layout/less-themes/less-themes-migration#less-to-sass-theme-migration) article.
36+
37+
This article also includes the mapping between the dropped Less thems and their respective Sass counterparts.
38+
39+
## See Also
40+
41+
* [Upgrade Troubleshooting]({% slug upgrade_aspnetcore_troubleshooting %})
42+
* [Telerik UI for {{ site.framework }} Breaking Changes]({%slug breakingchanges_2023%})
43+
* [Telerik UI for {{ site.framework }} Knowledge Base](https://docs.telerik.com/{{ site.platform }}/knowledge-base)

‎docs-aspnet/knowledge-base/remove-license-warning-message.md‎

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: Removing the Kendo License Warning
3+
description: Learn how to omit the License Warning in a {{ site.product }} application.
4+
page_title: Removing the Kendo License Warning
5+
slug: remove-license-warning-message
6+
tags: license, warning, core, aspnet, mvc, message, upgrade, troubleshoot, application
7+
res_type: kb
8+
---
9+
10+
## Environment
11+
12+
<table>
13+
<tr>
14+
<td>Product</td>
15+
<td>{{ site.product }}</td>
16+
</tr>
17+
<tr>
18+
<td>Progress {{ site.product }} version</td>
19+
<td>2022.3.913</td>
20+
</tr>
21+
</table>
22+
23+
## Description
24+
25+
After upgrading, there is a warning in the console stating the following:
26+
27+
```
28+
License Activation failed for @progress/kendo-ui
29+
No license found
30+
```
31+
A watermark for the component I have been using:
32+
33+
![Watermark over Grid with Light Theme](../installation/images/watermark-light-theme.png)
34+
35+
And a banner which indicates that my license is not found:
36+
![Banner](../installation/images/banner.png)
37+
38+
The application seems to be running. How can I remove the warning, watermark, and banner?
39+
40+
## Solution
41+
42+
The license warning will surface because of the [new licensing mechanism](https://docs.telerik.com/{{ site.platform }}/installation/adding-client-side-resources/using-license-code) introduced with the `R3 2022` release. To remove the warning:
43+
44+
* Generate a [license file](https://docs.telerik.com/{{ site.platform }}/installation/adding-client-side-resources/using-license-code#step-1-get-the-license-file).
45+
* Add the license file after the CDN reference to `kendo.all.min.js` and `kendo.aspnetmvc.min.js`.
46+
```
47+
<script src="https://kendo.cdn.telerik.com/***/kendo.all.min.js"></script>
48+
<script src="https://kendo.cdn.telerik.com/***/kendo.aspnetmvc.min.js"></script>
49+
<script src="~/kendo-ui-license.js"></script>
50+
51+
<!-- Rest of the HTML -->
52+
```
53+
54+
> The license file mechanism does not break any builds and does not affect existing applications. It acts as verification when the CDN or NPM distribution channel is utilized for the client-side resources.
55+
56+
57+
## See Also
58+
59+
* [Upgrade Troubleshooting]({% slug upgrade_aspnetcore_troubleshooting %})
60+
* [Telerik UI for {{ site.framework }} Breaking Changes]({%slug breakingchanges_2023%})
61+
* [Telerik UI for {{ site.framework }} Knowledge Base](https://docs.telerik.com/{{ site.platform }}/knowledge-base)

‎docs/api/javascript/ui/textarea.md‎

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -12,21 +12,6 @@ Represents the Kendo UI TextArea widget. Inherits from [Widget](/api/javascript/
1212

1313
## Configuration
1414

15-
### cols `Number` *(default: 20)*
16-
17-
The visible width of the text control, in average character widths.
18-
19-
#### Example - specify width
20-
21-
<textarea id="description"></textarea>
22-
<script>
23-
$("#description").kendoTextArea({
24-
rows:20,
25-
cols:30,
26-
resizable: "vertical"
27-
})
28-
</script>
29-
3015
### enable `Boolean` *(default: true)*
3116

3217
If set to `false`, the widget will be disabled and will not allow user input. The widget is enabled by default and allows user input.
@@ -37,7 +22,6 @@ If set to `false`, the widget will be disabled and will not allow user input. Th
3722
<script>
3823
$("#description").kendoTextArea({
3924
rows:20,
40-
cols:30,
4125
enable: false
4226
})
4327
</script>

‎docs/knowledge-base/treeview-restrict-drag-within-parent.md‎

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: Restrict a Dragging Node Only Within Its Parent in the TreeView
3+
description: Learn how to restrict a dragging of a node only within its parent in the Kendo UI TreeView widget.
4+
type: how-to
5+
page_title: Restrict Dragging Node Within Parent - Kendo UI TreeView for jQuery
6+
slug: treeview-restrict-drag-within-parent
7+
tags: treeview, restrict, drag, parent
8+
res_type: kb
9+
component: treeview
10+
---
11+
12+
## Environment
13+
14+
<table>
15+
<tr>
16+
<td>Product</td>
17+
<td>Progress® Kendo UI® TreeView for jQuery</td>
18+
</tr>
19+
</table>
20+
21+
## Description
22+
23+
I want to allow the user to drag nodes but only within the parent of the node. I want to prevent the user to drag a node to a different parent or different level.
24+
How can I achieve that?
25+
26+
## Solution
27+
28+
Handle the [`drag`](/api/javascript/ui/treeview/events/drag) event of the TreeView. In that event handler, check for the hierarchy of the dragged and target node and deny dragging if necessary.
29+
30+
```dojo
31+
<div id="treeview"></div>
32+
33+
<script>
34+
$(document).ready(function() {
35+
$("#treeview").kendoTreeView({
36+
checkboxes: true,
37+
sortable: true,
38+
editable: {
39+
move: true
40+
},
41+
dataSource: [
42+
{ text: "Furniture", expanded: true, items: [
43+
{ text: "Tables & Chairs" },
44+
{ text: "Sofas" },
45+
{ text: "Occasional Furniture" }
46+
] },
47+
{ text: "Decor", items: [
48+
{ text: "Bed Linen" },
49+
{ text: "Curtains & Blinds" },
50+
{ text: "Carpets" }
51+
] },
52+
{ text: "Storage" }
53+
],
54+
55+
sortable:true,
56+
dragAndDrop: true,
57+
drag: function(e) {
58+
if(e.sourceNode.parentNode != e.dropTarget.closest("ul") || e.statusClass === "plus") {
59+
e.setStatusClass('cancel');
60+
}
61+
},
62+
});
63+
});
64+
</script>
65+
```

0 commit comments

Comments
 (0)