Hi Matthias,

It does work in CKeditor for me. If you downloaded mojoportal 2.3.3.2 right after it was released, you may try downloading and deploying it again. A few patches were applied to it in the days right after the initial release. On of the patches was related to CKeditor template/style integration.

So redeploying the files may fix it for you.

Alternatively, I'm thinking of putting out an interim build of the latest stable code so people can test the new File Manager improvements. If you would be interested in trying the new build let me know. It is also already deployed on demo.mojoportal.com so you can test the new file manager there as well.

Best,

Joe

I will post again later today when the build is available.

Best,

Joe

I believe this is a bug in CKeditor, I've reported it in their issue tracker.

Best,

Joe

Oh, and many thanks for the beer!

Cheers,

Joe

I've uploaded a new build to the Novell Forge download page, mojoportal-mssql-deploymentfiles-20100103.zip

If you already got yesterday's build, I think the only files you need to get the fixes are mojoPortal.Web.dll and mojoPortal.Features.UI.dll

Best,

Joe

Hi Matthias,

It does not generate a file, it uses a service url, the styles you define are stored in the db. As soon as you add a new one and go back into the editor it will appear.

That is strange that you would get a syntax error based on content because it is passed in as a parameter of type text, there is no string concatenation. Are you sure the table column you are saving to is configured for unicode?

If the table is not configured for unicode it will change unrecognized chars into ? in the db.

Best,

Joe

Hi Matthias,

The mojoPortal service for populating the CKeditor styles dropdown is implemented to return a json result containing the styles defined in the mojoPortal style system formatted according to the ckeditor documentation about custom styles.

When you created your MySql database, you had to choose an encoding and collation (or else a server default was used) and this is used when creating all tables and columns. If you chose something other than unicode/utf-8 then it may have a problem storing certain characters and possibly could cause the error you describe. I will test it on a local copy of my own site soon and see if I can produce the error. Depending on what MySql management tools you use, you can also inspect the tables and columns and see what encoding/collations are specified and change them to utf-8/unicode unicode_general_ci if needed.

Best,

Joe

Hi Matthias,

You should not modify any javascript files included with the editors. That file is not even used, that is the file that would be used if we were not overriding it to use our service url for styles.

If you want it to only use your custom styles you should add this to your user.config

<add key="AddSystemStyleTemplatesAboveSiteTemplates" value="false" />
<add key="AddSystemStyleTemplatesBelowSiteTemplates" value="false" />

for more info see Creating Content Style Templates.

Regarding the special characters errors, in my testing it works fine in MySql.

Does the problem occur in all features for you or only in specific content features?

Does using a different web browser make a difference?

Best,

Joe

Hi Matthias,

I suspect on the server where the error happens, there is something not correct in the charset and collation. I would inspect the charset and collation on the mp_HtmlContent table, specifically the column named "Body". It is possible that even if the table has the correct utf8/unicode setting that this column may have something different. I cannot produce the error with correct charset and encoding. 

Hope it helps,

Joe

Hi Matthias,

Check your connection string, make it like this:

<add key="MySqlConnectionString" value="Server=yourserver;Database=yourdatabase;Uid=youruser;Pwd=yourpassword;Charset=utf8;" />

Note the important part at the end is Charset=utf8;

Do you have that part?

Hope it helps,

Joe

Glad that fixed it!

Many thanks for the beers!

Cheers,

Joe