Distinction between ${framework} and ${frameworkDir} editor variables on Windows

[daliboris]

I found different behavior of ${framework} and ${frameworkDir} editor variables when I tried set path to document templates directory.

If ${frameworkDir} is used in framework extension file (.exf), templates from specified directory are shown in the list of the available templates.

frameworkDir.png

When I use ${framework} variable in framework extension file (.exf), templates from specified directory are not available in the list of the templates.

framework.png

When the framework is build (zipped) and delivered as an Add-on (via web page), all installed templates are shown when ${framework} variable is used.

[alex_jitianu]

Hello,

Thank you for reporting this issue. The problem is that document template folders must be specified as file system paths, not URLs, so $frameworkDir should be used. Unfortunately, there is no indication of this in the *.exf file. The tooltips suggest that either option can be used, which is misleading. I will open an issue to handle both variables properly.

When the framework is build (zipped) and delivered as an Add-on (via web page), all installed templates are shown when ${framework} variable is used.

Based on my tests, this does not appear to be the case. The $framework variable does not work, regardless of whether the framework is compiled at runtime or built in advance.

Best regards,
Alex