Page 1 of 1

[SOLVED] New install version 2.x

Posted: Fri Oct 09, 2015 4:26 pm
by rooon
Hello,

The main reason to use CMSMS 2.x is MicroTiny. My customers campared the MicroTiny in CMSMS 1 with Notepad :(
I did a clean install of CMSMS 2.0.1.1 and after that a verification. Hmm, "426 files not found", but it were all language files (why report this, I did choose only 1 extra language?). Futhermore, I had to upload 2 missing icon files manually.

First impression... it looks and feels good.

I have a question: in Internet Explorer I get an error when I hit the Cancel or Submit button in Edit Content, Edit Template, or Edit Stylesheet. In Chrome I do not get this error. The error says:
got error cmsnolockexception // Could not find a lock with the specified identifiers

Note: this error is not shown in Edit Design, Edit Category, Edit Article (News).

Does anyone know what's happening here and how to solve it?

Greetz, Ronald

Re: New install version 2.x

Posted: Tue Oct 13, 2015 1:11 am
by JohnnyB
in Internet Explorer I get an error when I hit the Cancel or Submit button in Edit Content, Edit Template, or Edit Stylesheet.
Which version of Internet Explorer? Which Windows version?

Re: New install version 2.x

Posted: Tue Oct 13, 2015 1:21 am
by JohnnyB
I think I was able to reproduce while in the Content Editor -- are you getting the same alert box as the attached image?

Re: New install version 2.x

Posted: Tue Oct 13, 2015 12:24 pm
by rooon
Yep, exactly the same error.
My pc is running Win 8.1 and IE 11 with latest updates.

I'll like to offer customers the MicroTiny2 editor but sometimes they have to use cmsms1 because the server does not match the minimum requirements of cmsms2.

Q: is it possible to use MicroTiny2 in some way on cmsms1? I'll think many users will be happy with this feature.

Greetz, Ronald

Re: New install version 2.x

Posted: Tue Oct 13, 2015 3:26 pm
by JohnnyB
The annoying IE alert box will be fixed in an upcoming release. It is not an error but how IE handles a deprecated ajax setting. All other browsers handle it silently... It is ok to ignore for now.