CMS Made Simple Forums

I'm not sure the status of the dutch translation, but it can't hurt to join the translation project and check it out.

go here:  http://dev.cmsmadesimple.org/projects/dutch/  (you may need to register yourself with the forge if you haven't already), and request to join the project.

Then when you are added, you can go to http://translations.cmsmadesimple.org and sign in, and you'll be able to translate.

Once you've requested to join, pop into the IRC channel and I can approve you, or reneh can, or somebody.

I submitted some small patches today for Postgres compatibility. It would be great if those could go into 1.3.

http://dev.cmsmadesimple.org/tracker/?func=detail&aid=2282&group_id=6&atid=103
  =  /install/schemas/schema.php patch for clean installs.

http://dev.cmsmadesimple.org/tracker/?func=detail&aid=2281&group_id=6&atid=103
  =  /install/upgrades/upgrade.XX.to.YY.php patches for version upgrades.

By the way, remove_site_preference() in /lib/page.functions.php uses the non-portable REGEXP keyword :- I've filed that as a minor bug: it only affects cleanup when you uninstall a module.
http://dev.cmsmadesimple.org/tracker/?func=detail&aid=2283&group_id=6&atid=101

Hope this helps!  Thanks for all your hard work.  CMSMS is looking really powerful now, with all those nice Modules.

- Martin.

Here's the current list of what has changed in 1.3.... the first beta should be out sometime this afternoon (my time).

Version 1.3-beta1 "Cuba"
-----------------
- Massive updates to translations
- Includes TinyMCE 2.4.0b5
  (this should be a release version by the time 1.3 comes out)
- Includes FileManager 0.3.0b2
  (this should be a release version by the time 1.3 comes out)
- Includes News 2.8
  - Fixes for pretty urls
  - Adds news_extra and custom field support to the fesubmit action
  - Uses cms_html_entity_decode for php4 compatibility
  - Removes the News content type once and for all
- Includes Search 1.5
  - Adds the ability to change the search output on a per module basis
  - Adds an ability to track search words
  - Better templating for News
  - More
- Includes MenuManager 1.5
  - Pass all parameters to the menumanager template for easier customization
  - Fixes for has_children
  - Minor fixes
- Includes ModuleManager 1.1.6
  - Now indicates that a module available in the repository is incompatible
    with the current CMS version
  - A nice big notice on the top of the display about xml vs zip modules
  - Cleanup on uninstall
- Includes a new admin theme (NCleanGrey) generously donated by Nuno Costa
- All plugins are now translatable
- The title and sitename plugins now support the assign param
- Adds two new plugins (redirect_page and redirect_url)
- Debug mode now tweaks the display_errors and error levels
  in the admin section as well as in the frontend
- Listcontent is now cleaned-up and has better security checks
- Minor improvements to listmodules
- Admin templates are now override-able by creating a matching file in
  module_custom//templates/.tpl
- All language files are now override-able by creating a matching file in
  module_custom//lang/.php
- Adds a new PageLink content type to allow linking to an internal page
  easily
- The {sitemap} plugin is deprecated, and replaced by {site_mapper} which
  is just a simple wrapper around menumanager
- Fixes so that menumanager sets has_children properly
- Attempt to handle hosts that have disabled the readfile function
- Add cms_html_entity_decode which is php4 compatible as html_entity_decode
  may not be.
- Fix un-necessary queries in cms_selflink
- Fixes for bugs #2227, 2205, 2230, 2207
- Content type names are now translatab
- Replaced the 'select all' link in Listcontent with a checkbox which is a bit more standardish
- Cachable option is now off for 'additional editors' in editcontent, unless that person has additonal permissions.

WOW! That is a massive amount of changes.

Well done!

Nullig

Lots a nice changes.

one question; will the current admin theme still be default, or does the new theme replace the current one?

Good question.

The current admin theme will still be the default.
there'll just be another item in the dropdown.

Due to some potential problems or idiosyncrasies in TinyMCE and the FileManager Modules, I have decided to hold off the beta of 1.3 until such time as we can be reasonably assured that everything is working relatively well.

Sorry to dissapoint everybody,

But I don't want to have to run around like a headless chicken trying to fix problems after the beta comes out.  I'd rather have the beta as stable as possible.

Thank you.

Hello,

calguy1000 wrote: Sorry to dissapoint everybody,

You don't disapoint me. Opposite effect, indeed : I'm happy you care about quality (which is worth a little delay). Thank yoou for all this good, impressive work.

Pierre

Looks like a great release! Why not let some people try an Alpha so they can identify if there really are any issues with the modules you mentioned?

We aren't releasing an alpha simply because of this:
1) Traditionally, the effort in creating an alpha release isn't worth the amount of people that actually test it.
    (anybody that wants to test is welcome to install from svn at
            http://svn.cmsmadesimple.org/svn/cmsmad ... ches/1.2.x
2) We want this to be a short testing cycle.
    Thankfully we have a very active community this time that is willing to spend time testing things
    that concern them, and the things that have changed.    Included, these people are already familiar with
    working with svn, and are actively participating in fixing the problems with FileManager and Tiny.

When we think we're good... we'll release a beta for a week (NOTE 1 week)... and hopefully the beta testers will find everything will be smooth.
I pray there will be no need for a second beta.  At least that's what we're working towards.
 

I have two questions:
1) will 1.3 be directly compatible with sites built with 1.2.x or does it involve database changes? Reading the description I suppose it will be, but who knows...
2 actually more a (little) feature request rather than a question. CMSms has no core support fot the meta-description tag. It can be done with the tecnique shown in http://forum.cmsmadesimple.org/index.php/topic,16842.0.html which works but has to be put in every template. Given the importance of this tag in SEO terms, wouldn't it be better to put it in the core? Is it too late/too much work/inefficient for other reasons?

Thanks.

1.  There are no database changes in CMS 1.3, so everything should be compatible.

2.  It's simple enough to put a content block into your templates that provides a text area where you can fill in the
    meta description tag, or you can put it in the meta field on the options tab of each page... so there's no real
    need at this point

    Besides, doing that would be a database change, and then require more testing, etc, etc, etc... for a problem
    with a relatively simple workaround.

    Also, 1.3 is in feature-cutoff... just trying to resolve issues with FM and Tiny before the beta.

I can't add a intern link anymore. Where's that option in TinyMCE?

That was just a great option to select a page in the cms

The latest Tiny still has that option, it is the palmtree-with-chain button. In my 1.3SVN version, that one shows....

Ronny

I know how it looks .

http://dev.cmsmadesimple.org/frs/?group ... se_id=1312

In the first beta it's not there anymore 

Edit:
There's an error with TinyMCE when I go to advanced tab and i click on CMS-Linker style and change that. It don't work anymore. I get the html code instead of the wysiwyg style

And the cmslinker don't load

Edit again
I have to uninstall and then install TinyMCE again. Now it works Great new option with the internal links