CMS Made Simple Forums

I have quite the same problem on (only) one 2.1.6 site: on the frontend, what's in the global parameters disappears (like you I have "CMSMS site" instead of its name), and no admin user can access to the admin anymore. Then, with a cache cleared, everything's back to normal. I saw nothing ...

It seems it doesn't occur on all installations. I'm investigating to find out what could be the problem (a third party module, maybe?).

Edit: bug under MAMP on v2.1.1, ok on v2.1. Ok on a 2.1.1 LAMP.

archeo wrote:CMSMS is now unusable in French.

To be precise, in french and other languages using diacritics, so many of them.

How to reproduce: Try to create a page with a diacritic character either in the title or the menu text. Validate leads to a fatal error: PHP Fatal error: Maximum execution time of 30 seconds exceeded in .../lib/misc.functions.php on line 806 Same thing happens when trying to switch WYSIWYG off in th...

Thanks for your answer. A testing team could be a good idea, indeed. Wait and see then.

Hello, I was wondering why there is no beta version everytime a new version (with new features, like the 2.1) to test by users? For the version 2.0, I had the chance to test it quite early and find several bugs & propose UX suggestions. So could it be possible to release beta versions in a regul...

Nice, thank you!

I noticed a bug on V2.0.1.1 maybe only when upgrading from a V1.12.1. When you check the "Disable WYSIWYG editor on this page" (in options tab) during the edition of a page in the backend, the page used to reload and the WYSIWYG editor wasn't there anymore on V.1.12. Doing the same on V2 d...

hasanen wrote:I posted about that few hours after starting this thread, but strangely that post has been disappeared. Has it been removed by moderators?

I guess so.

I think the soon to be released 2.1 version will fix it. I installed a pre-release version that fixed it on one of my 2.0.1.1 site. Strangely enough, I have no problem with editing on some other 2.0.1.1 installations.

There's a bug (edit: 2 actually) for this problem opened a long time ago on the forge:
http://dev.cmsmadesimple.org/bug/view/10322
http://dev.cmsmadesimple.org/bug/view/9585

To be more precise: copy the CSS rule in the CSS attached to the template, and add float:right; to it.

I was just asking to know if you'd be able to edit the css.

You found the file, didn't you?

By adding float:right; to the .fc declaration in CSS, the calendar is back where it has to be.
Are you comfortable with CSS, btw?

Looks like a positioning problem, maybe CSS rules added by the new calendar?

Sorry to be this unprecise, but as you changed the display, we can't see the difference anymore, and I haven't installed the new version yet.