What happened?

After releasing DNN 10.2.* and introducing recent changes in the Client Dependency Framework (CDF), resource files with specific naming patterns—such as *.rtl.css—are no longer being loaded.

This behavior breaks RTL support in projects that rely on these files (e.g. Persian and Arabic websites), while the same setup worked correctly in versions prior to 10.2.

The issue was discussed extensively in the following Pull Request on this repository:
#6622

As a result of that discussion, the necessary fix was implemented in the ClientDependency repository here:
dnnsoftware/ClientDependency#15

However, in the released DNN 10.2.* versions, the issue still exists, and resource files like *.rtl.css are not included in the output, suggesting that the fix may not be fully integrated or is not functioning as expected within Dnn.Platform.

Expected behavior

Resource files such as *.rtl.css should be loaded correctly, consistent with behavior prior to DNN 10.2.

Actual behavior

Files matching patterns like *.rtl.css are ignored and never loaded.

Environment

DNN Platform: 10.2.*

Browser: All

Affected feature: Client Dependency Framework (CDF)

Steps to reproduce?

In the path Portals/_default/Skins/Aperture/css, create a file named:

skin.min.rtl.css

Set the site (portal) language to an RTL language, for example Persian (fa-IR).

Load the site using this RTL language.

Expected Behavior

When the site is loaded in an RTL language, skin.min.rtl.css should be loaded instead of skin.min.css.

Actual Behavior

The RTL-specific stylesheet (skin.min.rtl.css) is not loaded, and skin.min.css is used instead.

Current Behavior

No response

Expected Behavior

No response

Relevant log output

Anything else?

No response

Affected Versions

10.2.0 (latest v10 release)

What browsers are you seeing the problem on?

Chrome

Code of Conduct

• I agree to follow this project's Code of Conduct