How should we prepare for CMSMS 2.0?

[JohnnyB]

What can a frontend developer do to be prepared? If I'm building a site today using CMSMS 1.11.10, is there anything I should do to be prepared for CMSMS 2.0?

Thanks!!

[calguy1000]

The biggest thing a frontend developer/site developer can do to prepare for 2.0 is be involved in the beta (coming soon).

There are lots of changes, and lots of new features. It will take a bit of time to wrap your head around them.

Also, some modules will be broken. If you are involved in the beta you can help find out which ones faster, and notify the developers of those modules to fix them. Hopefully with active community involvement the developers will be able to fix their modules before the final release.

BTW, I already know most of my modules that were broken, and have fixed most of them.

[Jos]

BTW, I already know most of my modules that were broken, and have fixed most of them.

I would also like to start fixing my modules before users complain... Is there a list I can work through?

[calguy1000]

The quick list of modules that were broken is:

a: Modules that created content types (should be easy fixes)
(AdvancedContent)
It took me less than an hour to fix FEU.

b: Modules that implemented WYSIWYG or syntax areas
(probably significant changes, but should be cleaner when done)
(TinyMCE, AceEditor, ....)
We completely rewrote MicroTiny for CMSMS 2.0.

c: Modules that work directly with the template API (very significant changes)
(TemplateExternalizer is definitely broken. Not sure about Archiver.
I have to fix or remove some stuff in CGContentUtils yet).

d: Modules that relied on deprecated, un-document, and/or internal API's or data structures.
If you used the old (internal) $gCms->variables stuff and/or other internal stuff you will have work to do.

[psy]

Thanks for the heads-up Calguy. Am keen to be part of the beta program and ensure my modules work with 2.0.

Is there somewhere module devs can pre-register? I searched but couldn't find anything.

[kraygoon]

TemplateExternalizer is definitely broken.

I'll fix it ASAP after the release of the beta.

[calguy1000]

Another thing... if you haven't noticed already is that we've upgraded the requirements.

Namely, you will need a reasonably recent version of PHP (5.4.4 minimum, but this is subject to change). You will also need to ensure that your version of PHP has most standard extensions enabled (like the fileinfo stuff).