Ionize, creative CI CMS to be released very very soon !

[eluser]Michel-Ange[/eluser]
@Robert.dejesica, @Kip zonder Kop :

If you use PHP 5.3 you can set the Kip zonder Kop solution directly in you php.ini.

[eluser]robert.dejesica[/eluser]
yeah it works by adding Kip zonder Kop code..

[eluser]moykan[/eluser]
@Michel-Ange:
you done a really nice work, i give you my compliments.
I'm so curious about a thing...
In this image: http://www.partikule.net/files/pictures/...e_menu.jpg
the ionize version is 1.1, there are a lot of difference between the open source version (v0.90)
Do you think to add that features in the future?

Another question, that i think will be really important for SEO
I saw that there is a complete support for multilingual, but it's not possible to translate the URL name...
Esample
Page ID: home
eng url: www.yoursite.com/en/home
fr url: www.yoursite.com/fr/home

do you think in the future will be possible to name its like that?
Page ID: home
eng url: www.yoursite.com/en/home
fr url: www.yoursite.com/fr/maison

thank you

[eluser]Michel-Ange[/eluser]
@moykan : Thanks for the compliment !

I apologize, I didn't had time to update partikule.net, which show the very old version of Ionize (I call it "historical version"). Lot of my clients are using this version, but it will never be Open Source as the new version is a complete rewrite.

Your idea about URL is good. It suppose each article / page should have a translated "url" field.
So the article model query should be based on the translated url.
Why not. Will think about.

In the version 0.92, it will be possible to do that by creating 2 pages : One called "maison" with an offline english translation and idem for the "home" page, offline in french. The inconvenient of this approach is that you will have 2 pages for, in fact, one translated content...
Have really to think about...

[eluser]Référencement Google[/eluser]
A translation concept I've seen on Joomla with the component Joomfish is not bad. In you create a base language version of your website in Joomla and you can choose what to translate in Joomfish, you can really translate all even the url, even the date of the article etc.

I think it's better to go this way instead of having all translation tools aside the article creation. Let's say a kind of decentralized translation center. Discussion opened, tell us what do you think.

[eluser]moykan[/eluser]
I really like the solution for multilingual in ionize, aside the article.

I used joomla and joomfish too, i think it will be nice for people that are more technical, I mean it's not a simply system to give to customers that are always looking for something easy...

The only problem that maybe will be in the multilanguage aside article it's if the languages are about 6 or 7 different, but probablly it can be solved using a drop-down list with ajax reload and not a tab as it's right now.

I think using multilanguage inside article and not as separated module it's a better and easy to use solution.

[eluser]Référencement Google[/eluser]
It could be interesting to look also what they did in Expression Engine to handle the multilingual content. Anybody?

[eluser]abmcr[/eluser]
I have try to download from svn at http://code.assembla.com/ionize/subversion/nodes
but a user/password are required....
Thank you

[eluser]Michel-Ange[/eluser]
@abmcr : Di you register to Assembla ?

[eluser]JasonS[/eluser]
First of all I have to say that it is looking good, it runs smoothly. Its a nice achievement.

However there are a couple of issues. First of all it isn't very intuative.

For example. Specifying an ID when creating a new page? Say what? I thought this was just an integer to go into the database. 'Page Title' appears to be far more relevant. Then there is a checkbox called online? Online? What does this mean? Does this mean publish? I just don't know.

You then have templates and 'default view'. I just installed the system. I have no idea what the default view is. Surely the default view is in the list. Why not just have that selected?

There is then a box called Link...

I am sure you get the idea. I am sure that all of this is covered in the documentation but to be honest, making pages and adding articles shouldn't require a manual. If I gave this to a client I would be pestered no end about these things.

All that I can see that needs doing is some usability testing. Add some question marks near fields which show tips when you move the mouse across them and tidy up some of the terminology. These things would make the CMS far far better.