-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hardcoded usage of /otobo-web in Framework.xml #3151
Comments
The three cases are not covered by the automatic replacement of '<OTOBO_CONFIG_SettingName> in Kernel/Config/Defaults.pm. Only the top level strings are replaces. That's likely the reason why the variable was not already used. So let's do the same thing as in otobo/Kernel/System/Calendar/Plugin.pm Line 78 in fb6f40d
|
explicitly mention the <OTOBO_CONFIG_SettingName> pattern
in the SysConfig. For this two additional cases where <OTOBO_CONFIG_SettingName> are replaced had to be added.
explicitly mention the <OTOBO_CONFIG_SettingName> pattern
in the SysConfig. For this two additional cases where <OTOBO_CONFIG_SettingName> are replaced had to be added.
Made the changes and did a quick manual test. The customer interface still looks fine. Closing this issue. |
While testing #2886 I noticed that there are some hard coded references to /otobo-web in Framework.xml .
These images are not found when the static assets are not available in /otobo-web . They should be changed to look like e.g.
The text was updated successfully, but these errors were encountered: