Xpages - New version of CkEditor not load - ckeditor

Recently I decide to migrate my application from version 8.5.3 Lotus Notes to version 9.0.1. When doing this I needed to change the version of CkEditor from 4.4.7 to 4.5.3, so I changed the file in the \data \ domino\html\ckeditor folder, however when re-building my application I received the following error in browser console:
The file xsp/.ibmxspres/domino/ckeditor/plugins/ibmspellchecker/plugin.js not exists in the new version of ckEditor.
I realized this is because the application tries to fetch the javascripts files from the old version of CkEditor, as if it were cached.
I've tried everything specified here: http://www.intec.co.uk/dde-local-preview-ckeditor/ but nothing worked.
Does anyone have any ideas?

From what I understand: you are upgrading CKEditor by yourself instead of using the default version that is installed and doing this by installing a version of CKEditor that you have obtained from CKEditor directly.
If so, the problem may be that the xpages inputRichText control uses some CKEditor plugins that are provided by IBM e.g. ibmspellchecker, ibmxspimage and these won't be provided in the standard CKEditor distribution.
If these plugins are not present in your new CKEditor installation then the editor will not load properly.
You have 2 options
Ensure these IBM plugins are put back in the html/ckeditor/plugins directory (and hope they are still compatible with the CKEditor version)
Tell the inputRichText control not to load any of the ibm plugins. (but this means you will not be able to upload images)
To remove plugins from the editor config use the dojoAttribute 'removePlugins'
<xp:inputRichText id="inputRichText1">
<xp:this.dojoAttributes>
<xp:dojoAttribute name="removePlugins" value="ibmspellchecker,etc"></xp:dojoAttribute>
</xp:this.dojoAttributes>
</xp:inputRichText>

Related

How to install CKeditor on MediaWiki

I've installed
-Wysiwyg 1.5.6_0 [B551+09.02.2017], CKEditor 4.5.9 (revision a35abfe),
from https://github.com/Mediawiki-wysiwyg/WYSIWYG-CKeditor#short-installation-instructions
unto my server whose versions are
http://mediawiki-22652-48932-215666.cloudwaysapps.com/index.php/Special:Version
I've followed the instructions by
uploading the WYSIWYG folder into the extensions
replaced WikiEditor/modules/ext.wikiEditor.toolbar.js in the appropriate folder
Made sure the Preferences are correct
added all code that starts with "#02.07.16-> ,#Enable WYSIWYG- extension, MW >= 1.25....." to my LocalSettings.php without any changes
checked the versions and found that it was installed
When i want to edit the page, i dont see the WYSIWYG, is there something wrong with the installation steps?

Not able to add document property button in CKEditor 4

I have upgraded my CKEditor in my ajaxplorer project.
I want to add document property in ckeditor 4 and I have tried in all ways. by adding code in class.AjxpCkEditor.js aven ckeditor.js but yet succeed. There was no folder for document property as "docprops" which was having in older version. Then I have copied that folder and done some changes in class.AjxpCkEditor.js but its not working even I have done change in ckeditor.js but not working.
This plugin is not included in any of the 3 predefined presets, so you need to build your own version of CKEditor using the online builder.
Here's the plugin: http://ckeditor.com/addon/docprops and plugins installation instructions.

Internationalization of an Eclipse RCP 3.8 app: JFace dialog values not loaded

I want to translate an Eclipse RCP application based on Juno 3.8. For the Eclipse platform I downloaded the respective Babel language pack for German: BabelLanguagePack-eclipse-de_4.2.0.v20121120043402.zip.
Everything seems to work fine except for the buttons in the JFace dialogs: Cancel, Next etc. are not translated. The respective fragment (org.eclipse.jface.nl_de_4.2.0.v20121120043402.jar) which contains the translations is loaded correctly (I can see it in the plugin details) but the German values are not shown.
The bundle you have specified is for the version 4.2 (but you are using 3.8). This may be the problem.

Character Set Issues when Upgrading from Symfony 2.0.* to Symfony 2.1.*?

I have recently upgraded my staging test site to the latest version of Symfony and updated all the vendors using composer as instructed in the upgrade document that comes with the download.
Everything has all updated fine, but I have noticed now that some bits of HTML are not displaying in the Twig templates.
I did a comparison with the current live site and it appears to be a character set issue. As an example I had a drop down list that had the following value in:
Kitchen Ducting > Ducting Kits > Ducting Kit 4” / 100mm
In the updated site the drop-down list item just appeared blank. When I used Twig's raw function it then displayed the item again, but with the dreaded question mark in a black diamond.
Kitchen Ducting > Ducting Kits > Ducting Kit 4� / 100mm
Things that you should know that may help:
The staging test site and live site are both on the same server.
In my httpd.conf file I have 'AddDefaultCharset utf-8'.
In my php.ini file I have 'default_charset = "utf-8"'.
The HTML file served has the Content-Type meta tag 'content="text/html; charset=utf-8"'
My database is InnoDB and uses 'utf8' as the default character set and 'utf8_general_ci' as default collation. All tables in the database also use the defaults.
I looked into BOM with UTF8, but could not work out if that was a problem or not?
I managed to resolve the issue by editing the MySql config file on the server (/etc/my.cnf) and adding:
skip-character-set-client-handshake
collation-server=utf8_general_ci
character-set-server=utf8
That sorted it out for me. I'm not sure if it was something that had changed in Twig or Doctrine due to the upgrade to Symfony, but something in the upgrade caused the default charset to not work. The changes I made to the MySQL configuration meant that it will always fall back to UTF-8.

Firefox 6 Extension and Search Plugin bundle does not work

Adding a Search Plugin for Firefox Via Extension is done using bundles, putting your .xml OpeSearch in /searchplugins/ directory and Firefox will automatically add them when the Extension is installed.
See https://developer.mozilla.org/en/Bundles and also my own question Including a Search Plugin in my Firefox Extension
Well, it worked fine, until i started using Firefox 6. It seems that Firefox 6 does not read the /searchplugins/ directory anymore and does not add the Search Plugin. It might be also Firefox 4 and 5, i jumped from 3.6 to 6 directly.
Any idea if this is a bug in Firefox 6?
Any idea how to by pass it and install the SearchPlugin Anyway?
I think that the only relevant difference between Firefox 3.6 and Firefox 6 (Firefox 4 actually) is that by default extensions are no longer unpacked on installation, instead they are placed into user's profile as XPI files. This works for most extensions but particularly search plugins won't work from an XPI file. Which is why you have to add the unpack flag to your install.rdf file:
<Description about="urn:mozilla:install-manifest">
<em:id>...</em:id>
<em:unpack>true</em:unpack>
...
</Description>

Resources