We are currently working on a 1.1 release (to tie everybody over till the 2.0 release comes out).  Our intentions are to release this version, and then hopefully focus as much time as possible on the 2.0 release.  This version should be available within the next two weeks.

Some (but not all) of the things that will be in the 1.1 release are:
  a) Up-to-date version of smarty
  b) Up-to-date version of adodb_lite
  c) Significant tweaks to the news module
  d) The ability to select a 'syntax hiliter' module for stylesheets, UDT's, and templates
  e) Improvements to EditContent and EditTemplate
  f) Significant improvements to the News module
  g) A date format preference for admin side date formatting
  h) Significant efforts against any potential XSS vulnerabilities

Here is how it will work:  We will release a release candidate (RC1), and give exactly one week for feedback.  Any bugs reported after the release candidate comes out will go into SVN and will not be released.  If however, a significant, and critical bug is discovered by people testing the release candidate, we may then decide to release a second release candidate, for yet another week (depending upon the amount of changes that are needed to fix the issue).

We are hoping that as many people as possible will volunteer to TEST the 1.1 release candidate on their test, or pre-release setups, NOT their production servers. This will save us from having to panic, have heart attacks, then diagnose, fix, debug, release and support yet another release before the 2.0 release.  The more time you people can work on testing the 1.1 release (and there are many more of you, than there are of us), then the more time we can spend on the 2.0 series.

When released, we'll be looking for critical issues, or issues specifically related to what we have worked on.  Not necessarily bugs that have been in the tracker for some time (again, unless they are critical).  We are not intending to fix every bug, or implement every feature request, but to provide a significant improvement, and to give us time to work on 2.0

If you have any questions....

_________________
Follow me on twitter
--
if you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
----------------
Don't make me angry..... you won't like me when I'm angry....

Woot! I'll test it.

Please don't forget an up-to-date version of Scriptaculous - current version is 1.7.0, not 1.5pre1 .

And now, as we have a smarty based install procedure, the possibility of localizing would be a great feature ...

I`ll test happily ! 

When working on the News Module, will that include improvements on Rss feed?

Now when your feeds come in its 1 big pile of text instead of normal paragraphs?

Nice news !-)
I will test the 1.1-RC1. I hope I will give usefull feedback.
Pierre M.

_________________
-- Pierre, support team member. comodérateur du forum francophone.
Please read "how to submit installation/support requests" before posting. Don't send private messages to ask for support.
Want to contribute to CMSms ? Improve the wiki with your forum account.

Hi,

I test the last svn yesterday
I have many problems see  my message
So the last svn today 3918  + news 169
I have the same problems and into Tiny and Fck

_________________
Jean-Claude Etiemble  1.11.6-Fr

Thanks for the reminder cyberman.

_________________
Follow me on twitter
--
if you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
----------------
Don't make me angry..... you won't like me when I'm angry....

Please 'don't expect a working system' when you test SVN.  It's state at any point in time may be broken.  So take whatever you see there with a considerable amount of salt, and usually it's best to wait a day or two and/or mention something in the IRC channel if you see a problem with the SVN version, rather than polluting the forum or the tracker. 

That said.  Most of your problems are with Wysiwyg editors (and whilst I personally stay as far away from them as I can get), others work quite often in them.  You should contact the main module administrator (especially if you're working on the SVN version) to discuss issues. 

We will also be replacing FCK with TinyMCE in the 1.1 release.

_________________
Follow me on twitter
--
if you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
----------------
Don't make me angry..... you won't like me when I'm angry....

I would love to test this new version.

Where can I download it? 

Attention - there's a new release of TinyMCE outside since yesterday:

http://tinymce.moxiecode.com/punbb/view ... hp?id=6939

I'll be happy to test it for you

What kind of improvements?

_________________
Daniel15

I'll test of course, but hope it includes removing 'name' element on just the form element which prohibits XHTML 1.0 STRICT validation

This is in modform.inc.php, this was a page with the standard Search form on using 1.0.6.

From the validator….
”
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead)… ”

I know that removing it may cause problems with other modules, last time I looked for example the Album, module had problems when editing, but surely there must be a solution?

Russ

I've implemented:
* Pagination in the admin section
* Pagination in the frontend summary view
* Multiple Database Templates for the Detail and Summary views
* A Permission to approve news items for frontend display

_________________
Follow me on twitter
--
if you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
----------------
Don't make me angry..... you won't like me when I'm angry....

This is GREAT news! I'll be more than happy to give the news module changes some extensive testing!

We've now entered a week of internal testing of the 1.1 release.  We're going to try to limit any futher commits to only those that are
  a) Verified as reasonable by another developer
  b) Considered critical, or
  c) Fix a flaw in some of the stuff we've already committed for 1.1
We probably won't be adding any/many new enhancements, or fixing other existing bugs in an attempt to make this release stable, and keep it that way.

After that week of internal testing, the release candidate will come out for a week.  and we encourage as many people to test it as possible.

Here's the changelog of what we have done so far.  The hope is, that this won't change too much.

* Significant efforts against any potential XSS vulnerabilities
  ** The module api has been modified to clean much of the output
  ** The core has been modified such that most parameters relative
    to the core are cleaned on input.
* Added page_alias field to the link content type
* Rationalizing of the duplicated (incorrectly) code from the menu,search and cms_module tags.
* Module API Changes
  ** The RegisterModulePlugin() method allows modules to register themselves
    as plugins, without having to use {cms_module...}
  ** The SetParameterType method is used to register the type of an incoming
    parameter, to apply some cleaning to that incoming value
  ** The RestrictUnknownParams() method is used to tell the core that
    it should drop any unregistered parameters for that module.
* Copy the buttons from the bottom to the top of the edittemplate form
* Add An "Apply" Button to the UDT edit Page
* Add invalid character checks for usernames.
* Add sitename to the admin title and header text
* Added the concept of a syntax hiliter module which is used for templates, udts and stylesheets.
* The encoding dropdown on the template page is now hidden by default
* Added a date format user preference for use in the admin side.  Currently used in the admin log and the News Module
* Show the last modified date and time for templates, css and content
* Use root url for default content on links
* Add more information to the confirm message when deleting items in the admin
* Apply now uses Ajax (if available) in editcss, and editcontent.
* Add the sender IP to the contact for message.
* Add Execute('set names utf8') to the the database connection
* Add a site preference to disable the safe mode warning in the admin
* Add a site preference to disable warnings if RestrictUnknownParams is not
  enabled.  This will eliminate the warnings generated by the core from old
  modules that have not been updated.
* Installer tweaks
* Allow people with 'Modify Any Position' to also be able to activate/deactivate pages
* Upgrades Smarty to the latest version
* Upgrades adodb_lite to the latest version
* TinyMCE is now the default WYSIWYG editor
* Significant News changes
* News Module Changes
  ** Multiple database templates (Now have multiple summary and detail templates, all of which are stored in the database).
  ** Frontend Pagination
  ** Backend Pagination and sorting
  ** Modify the article list to illustrate expired articles
  ** Modify the article list to illustrate published/draft articles
  ** Add a new permission to restrict changing articles from draft to published

_________________
Follow me on twitter
--
if you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
----------------
Don't make me angry..... you won't like me when I'm angry....