First of all thanks for this extension, I am using it and it is very cool.
I want to share a very small idea that I had with the rest of the group, maybe someone will find it useful or maybe you include it in the extension. If this is not the correct place point me in the right direction. In the meantime I will explain.

I am doing a back-office interface in my native language, Romanian. My database is in Romanian as well so the plurals of the models sound ridiculous so I have to always change them after I re-generate with giix CRUD. I re-generate a lot since I am playing around with the templates. Now, the solution I found to not change manually the resulting names is to extend the pluralize method in GiixCrudCode.php with the following:

This will hard-code the translated plural in the resulting CRUD files, but that's exactly what I want to achieve. Of course you need to have internalization enabled in your project and an app.php file with the translations you want in the messages folder.

With a little change to the templates i18s support can be added so the plurals are taken from the messages files at runtime rather than generate time.

Aha. Well, seems like a workable solution, so there u go, people have two ways of solving the pluralize problem and maybe more. Plurals in English are easy but in Romanian it is hard to determine since they reply on the gender of the word. Very hard to determine, so it is much more easy to just provide it.
Hope this helps someone, I am trying to give something back to the Yii community since this is by far the best framework I have ever worked with. It has absolutely everything I need from a framework.

I also have a Problem with the create part. the relational data is not updated, yii stays on the create form pafe with no message and no error. the update function is working. any ideas?

I too am experiencing this problem. The root of the problem is that the id (primary key value) of the record that was just created is missing. I am investigating a solution. Anyone else already fix this?

I was able to fix the issue where saving a new record with related data was failing. For details and the patch, please check out the issue I created on the giix Google Code site: http://code.google.c...ues/detail?id=5

By the way, I created another issue because deletes would not work if you had foreign key constraints in your database. I wrote a beforeDelete function to automatically delete MANY_MANY, HAS_MANY, AND HAS_ONE related data so the main model record will delete without violating any foreign key constraints. You can get the patch here: http://code.google.c...ues/detail?id=4

just a hint to the developer: plese check if the performAjaxValidation catches the request or not. If not, this may be the solution to the mentioned duplicate entry Bug. I had this within the gii-template-collection, too.

I just used this extension recently it has few small bugs as I took code from repo , it really perform well with Many to Many.
it has issue with Form like it dont generate id to edit or view from grid and in views it creates issue with breadcumbs and menu(I just defined these varaibles in controler then it works smooth)

Dear,
I've been very busy lately, but I hope I can resume working in giix soon.
There are some pending bugfixes (some are already fixed in trunk, check there!) and the roadmap is huge. Great things will come.
Please keep the comments, suggestions and bug reports (and patches if you can) coming!

Several bugs were fixed (thanks for the reporters!) and some new functionality were added, including:

Native support for saving multiple (related or not) records with the new method GxActiveRecord::saveMultiple.
This method allows you to save many models at once, in a transaction (if you want) in a painless way. Try it!
It can even automatically detect all new active records having a BELONGS_TO relation and fill in the data for their FK. Awesome.

I have been using the extension and am very pleased.
I made some adjustments to suit me better. See below for their opinions on the possibility of deploying them officially:

- In the page of view's action, before listing the relations, with a tag <h2> highlight that these are dependent or related records.
- On the generation of CRUD, include two more fields. To enter a screen name in my language and the other for the plural name. You know in any language other than English you can not retrieve the correct name of the nomenclature of the database.
- For the same reasons, can not catch the names of the attributes directly from the data model. Then the method attributeLabes should not stay on the base file, since it must necessarily be changed. If he remains at the base, can not be the goal of these files remain intact.
- Many databases have fields in each table to log user actions. I then created a method (getEditableColumns) to always ignore them in loops over the columns of the table, not to create the inputs and validations on the form, for example.
- At least for me it was very important to change the method model->search() to do a merge with other default options passed as parameter.