#1 2013-05-31 10:49:54

Michel-Ange
Ionize Core Team
From: Paris, France
Registered: 2010-03-22
Posts: 927
Website

IMPORTANT : Ionize 1.0 and upgrade

Issues during migration

ionize 1.0 was launched a lit bit quickly.

We discovered one important migration issue from 0.9.9 to 1.0.x, previous versions migration are not impacted.

We just launched ionize 1.0.2, which corrects this migration issue.

Documentation & Modules

The documentation is not up to date and most of you are complaining about modules, which seems to not work.
We will update very quickly the documentation and correct the "Module tutorial".
This post will be edited as soon these tasks are done.

Modules corrections

In the mean time, these things changed for modules :

The data of the config.xml file moved to the config/config.php file of the module.
This files contains now all needed data for the module installation, except the database install script, which stays in database.xml.

Here is the example from Demo module :

<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed');

$config['module']['demo'] = array
(
	'module' => "Demo",
        'name' => "Demo Module",
	'description' => "Demo module. Manage articles's authors.",
	'author' => "Partikule",
	'version' => "1.0",

	'uri' => 'demo',
  	'has_admin'=> TRUE,
	'has_frontend'=> TRUE,

        // Array of resources
        // These resources will be added to the role's management panel
        // to allow / deny actions on them.
        'resources' => array(
               /*
                 * Default added resource : 'module/<module_key>'
                 *
	         * Default resource corresponding rule : 'access'
	         * Usage : Authority::can('access', 'module/<module_key>')
	         *
	         * Actions based rules (Added with this config file) :
                 * '<resource_key>' => array(
	         *		'title' => 'Resource title',
                 *		'actions' => '<action_key_1>, <action_key_2>, <action_key_3>',
	         *		'description' => 'Description of the resource in the role panel'
	         * )
		 * Usage : Authority::can('<action_key_1>', 'module/<module_key>/<resource_key>')
		 */
		// Authority::can('access', 'module/demo/admin')
		'admin' => array(
			'title' => 'Demo Module Administration'
		),
		'do_something' => array(
                       // Title of the resource
			'title' => 'Do something',
                       // Can be 'edit', 'eat_cheese', what you want
			'actions' => 'action_key_1,action_key_2',
		),
		'language/translate' => array(
			'parent' => 'language',
			'title' => 'Translate',
                        // No action means "access" : Authority::can('access', 'module/demo/language/translate'
			'actions' => '',
		),
	),
);

return $config['module']['demo'];

We apologize about these issues.


Inspiration & Innovation : Websites by Partikule, Agence Web Paris

Offline

#2 2013-05-31 18:14:38

GWR
Member
Registered: 2013-02-25
Posts: 125

Re: IMPORTANT : Ionize 1.0 and upgrade

edit3: ok, no problem with tags, just forgot to update my development environment to the current state so it includes my fixbranch big_smile

Is there interest in adding my hardened password class? (I would rebranch it for a cleaner push) This would modify the users table (no need for salt but adding forgotten_password_codes etc.). This would get rid of the "request new password for other users"-problem.

PS: your link to "launched 1.0.2" just points to the ionize website...


bye
Ron

Last edited by GWR (2013-05-31 18:32:40)

Offline

#3 2013-06-02 17:52:39

Michel-Ange
Ionize Core Team
From: Paris, France
Registered: 2010-03-22
Posts: 927
Website

Re: IMPORTANT : Ionize 1.0 and upgrade

Hi Ron,

Yes, we're interest about it, but as it was developed for the 0.9.x branch, of course we're waiting for the 1.0 version :-)


Inspiration & Innovation : Websites by Partikule, Agence Web Paris

Offline

#4 2013-06-03 20:37:32

GWR
Member
Registered: 2013-02-25
Posts: 125

Re: IMPORTANT : Ionize 1.0 and upgrade

There you go: Patch

Please test it on a local installation if it works flawlessly (I modified the Installer). also pay attention to the patch's annotations.

Hope I did not miss important changes happened since 0.9.9 - but I got no errors during login etc.
In generally I just migrated my master branch to your current commit, merged back my changes by hand (block by block).

There was a small bug in your current code - you still use "Connect()" instead of "User()" in 3 lines or so - if you decline my patch, do not forget to change that lines.


bye
Ron

Offline

#5 2013-06-04 05:11:07

aagii
Member
Registered: 2012-05-16
Posts: 48

Re: IMPORTANT : Ionize 1.0 and upgrade

I was waiting its new feature Roles Management. I did a test on demo create editor user and set permission on editors. There are many same confusing names. There should be descriptions on each checkbox how to use and where it affects.
I've tried to set only article create and edit permission. And disable all other things. No menu.
When page and article(partial) disabled and Add article checked on Pages in Tree(partial), there is no save article button.

Is it possible to set permission show/hide on (just specifiec) page.

Last edited by aagii (2013-06-04 05:15:53)

Offline

#6 2013-06-04 09:11:23

Michel-Ange
Ionize Core Team
From: Paris, France
Registered: 2010-03-22
Posts: 927
Website

Re: IMPORTANT : Ionize 1.0 and upgrade

@aagii : yes you can set permission only on one page :
In the page edition panel, logged as super-admin (or admin with the permission to), you can set both the frontend and backend permission for roles.

In case of frontend permission, you must set the frontend behavior in case one page is restricted :
- Must login : will tell the user he has to login to see this page
- Forbidden : will tell the user he has not the permission to see this page
- Not found : will not display this page in the menu and display one standard 404 page

In case of backend permission :
The restriction is only set if you set at least one role who has the permission to do something.


Inspiration & Innovation : Websites by Partikule, Agence Web Paris

Offline

#7 2013-06-04 10:57:28

aagii
Member
Registered: 2012-05-16
Posts: 48

Re: IMPORTANT : Ionize 1.0 and upgrade

Thank you for you reply. I've tried on only demo.

When i install 1.0.2, here is a error "Connection to the database fails with the provided settings".
Then i tried to install 0.9.9.5 succesfully. What is wrong on 1.0.2 ?

Offline

#8 2013-06-06 09:45:03

aagii
Member
Registered: 2012-05-16
Posts: 48

Re: IMPORTANT : Ionize 1.0 and upgrade

i found the way to fix the problem. Before installation, database must be created.

Previous version installs automatically create database. I didn't remember check that.

Sorry guys and thanks a lot.

Offline

#9 2013-06-09 17:23:03

hoaxer
Member
Registered: 2013-06-04
Posts: 2

Re: IMPORTANT : Ionize 1.0 and upgrade

can somebody explain what does the 'resources' block in module's configuration file?
can module export different actions for modules menu?
can you please give more updated module examples for the latest version? I would like to write something like existing "eventscalendar" module but can't find any decent example.

I think your CMS has a big potential but what it lacks is a knowledgebase (because current structure of cms, although "clean", is complicated to understand at the first glance) - and in documents section you have only one module tutorial!!!

imagine, I have a mid term more-less complex project to make (approx. 2 months) and I have to decide what will serve as a base - my own "cms", my new CI "cms" based off on one of the old projects, or something new as Ionize. Lack of good examples forces me to opt for one of the first two solutions hmm

Offline

#10 2013-06-16 12:10:48

budi
Member
Registered: 2013-06-16
Posts: 1

Re: IMPORTANT : Ionize 1.0 and upgrade

I just installed 1.0.2, here what i got :

1. Installer still displayed version 1.0.0
2. When i go to blog page (such as blog/article-1) i found a small warning in archive side bar :

Tag missing: active_class, scope: archives.
" href="http://localhost/ionize-102/blog/archive/2012">2012

Just a small thing to fix in next minor version smile

Offline

#11 2013-06-25 17:00:29

virtualgadjo
Member
Registered: 2011-01-04
Posts: 7

Re: IMPORTANT : Ionize 1.0 and upgrade

hello,

soooooooooo glad to hear that an xml file has been replaced by a php one smile
great news!

Offline

#12 2013-10-08 09:02:01

fbamber
Member
Registered: 2013-10-08
Posts: 1

Re: IMPORTANT : Ionize 1.0 and upgrade

I think we should focus on these things .

Offline

What's Ionize ?

Ionize is an Open Source Content Management System created by webdesigners for webdesigners.

Created and maintained by Partikule and Toopixel, Ionize wants to be the easiest and most powerful CMS.

Can I help ?

Because talent is nothing without involvement, we are looking for motivated coders and webdesigners to join the project team.

Resources

Website : ionizecms.com
Documentation : doc.ionizecms.com

Development : Ionize on GitHub
Translations : Ionize Translations