Xinha - CMSMSLinker tree not building

[bertmelis]

I'm trying to get the wysiwyg-editor Xinha up and running. But when I try to use the CMSMSLinker the tree containing all the pages is not being build.

I've got this error:

Code: Select all

SyntaxError: missing } after property list

I've tried to uploed the files again, tried some svn-files but it keeps on sending me the error.

Can anyone point me at the cause, or even the solution?
Does anyone have the same problem?

[bertmelis]

I've managed to get it partly working. I disabled the linking capabilities for other cmsms-pages.

Now I can link to images and other uploads on the server. But i want it mainly for making links to other pages so...

anyone a clue?

[Dr.CSS]

Have you tried other WYSIWYG editor to make sure it works?

[bertmelis]

How's Xinha related to other editors? I know the image-browsers for TinyMCE and FCKEditorX are the same, but I think it is a complete own build.

[Dr.CSS]

I was just suggesting that you check to make sure it works at all, yes it was built/ported to CMSMS you may need to file a bug report for that module...

[paul]

I have the same problem. I am using the last version of cmsms and Xinha. I think it is because there is a new database layout. The file that causes the error is under modules/xinha/xinha/plugins/cmsmslinker/scan.php

[paul]

I found the issue in the modules/xinha/xinha/plugins directory you have to modify the scan.php. Replace RowCount with RecordCount. After this it will work. I think rowcount is not working any longer since the last version of CMSMS. but i dont know why 

[bertmelis]

Oh, didn't think of that. The Rowcount-function doesn't work anymore because the ADODB-library has been updated. In this updated lib, Rowcount has been replaced by Recordcount.

I've been using FCKEditorX for now because of the error described, but I think I will switch back.

[paul]

I saw that an other module had the same error so i was able to fix it in a couple of time. The module is not updated since january and at that time it was working i think. I have send an email to developer with the error description and the solution. I hope he will update the package soon.