ICEfaces
  1. ICEfaces
  2. ICE-4194

Cannot find custom toolbar for inputRichText

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Won't Fix
          • Affects Version/s: 1.8RC1
          • Fix Version/s: 1.8RC2, 1.8
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            All

            Description

            On load of the inputRichText with a custom toolbar defined an alert/error message is displayed in the browser stating "Toolbar set "MyToolbar" doesn't exist". This issue only occurs with ICEFaces 1.8 RC#1 and not ICEfaces 1.8 DR#2. Also this issue occurs in both Firefox and IE browsers.

              Activity

              Hide
              Permalink
              Adnan Durrani added a comment -

              Its due to the reason that, the .js file referenced using relative path:
              <ice:inputRichText customConfigPath="js/config.js" .... >

              Changing it to absolute fixes the problem.
              <ice:inputRichText customConfigPath="/js/config.js" ..... >

              The behaviour is changed due to the fix made under the following case:
              http://jira.icefaces.org/browse/ICE-4070

              Before the above fix, the component was returning the context path even if you use the relative path.

              As the config.js will be loaded by the FCKediter API, which reside under sub folders. So to load the custom config file its require absolute path.

              Show
              Adnan Durrani added a comment - Its due to the reason that, the .js file referenced using relative path: <ice:inputRichText customConfigPath="js/config.js" .... > Changing it to absolute fixes the problem. <ice:inputRichText customConfigPath="/js/config.js" ..... > The behaviour is changed due to the fix made under the following case: http://jira.icefaces.org/browse/ICE-4070 Before the above fix, the component was returning the context path even if you use the relative path. As the config.js will be loaded by the FCKediter API, which reside under sub folders. So to load the custom config file its require absolute path.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Arran Mccullough
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: