Update ckeditor???

PowerMessenger not working in IE 11 , ok in latest firefox.

I tried moving your EmailToken plugin toCKeditor 4.4.5 and it doesn't work :(

I was just wondering if you are planning to update PM or at least update the HTML Editor extension.

Just a thought... Do all extensions refer to 3.5.2 version? An update would be appreciated!

Tony

The latest version of Data Bridge and design Extender both use newer versions of the CKEditor.

When we release the next version of Power Messenger, it will be upgraded to use the latest CKEditor as well.

of now, you will need to manually upgrade the CKEditor version:
in the webassist/ folder, rename the ckeditor folder to ckeditor_bak

On this page:
download

click the button to launch CK Builder. Select to use the Full Preset, and the Kama Skin.

Copy the downloaded CKEditor folder to the webassist folder in your site.

from the ckeditor_back folder, copy the following three files:
ckeditor.php
ckeditor-php4.php
ckeditor-php5.php


and paste them in the new ckeditor folder.

you will need to clear the browsers cache to see the updates take effect.

Hey Jason,

The process you outline works for updating the editor, but with PowerMessenger it doesn't work, at least with ckeditor 4.4.5. PowerMessenger will show the editor but the tokens .png doesn't show, and when you click on the placeholder it does insert into the toolbar, the token dialog doesn't work :(
Just guessing, but it seems the plugin needs a re-write...

I'll have to wait for the update to PM, I hope it isn't to far away.

Appreciate your time
Tony

** Update **

Just a note.. if error reporting is set to "on" in php.ini the mailings list does not work in ANY browser.

Trying to use PM in a test environment and found that when these are set:
error_reporting = E_ALL | E_STRICT
display_errors = On

will not let mailings list populate

I'll need to troubleshoot directly, see the private message section.

  Trying to use PM in a test environment and found that when these are set:
error_reporting = E_ALL | E_STRICT
display_errors = On  

most likely because strict errors are enabled, it is really best not to have error reporting turned on in a production environment.

try disabling deprecated warnings:
error_reporting = E_ALL & ~E_DEPRECATED

Hey Jason,

thanks for the reply...

I really don't need to troubleshoot this one, it is still in a dev environment, and I thought it might just be beneficial to mention the "dev" environment issue with error reporting... for those who might decide to integrate PM into another site.

If I turn it off PM works OK.

Thanks,
Tony