1) Extract the directory "AweCrud" (case-sensitive) from the downloaded archive into your application's protected/extensions directory.
2) Configure the gii generator path in your application, like:
'modules' => array( 'gii' => array( 'class' => 'system.gii.GiiModule', 'generatorPaths' => array( 'ext.AweCrud.generators', // AweCrud generators ), ), ),
3) Configure your application to automatically load the AweCrud component classes when needed, like:
'import' => array( ... 'ext.AweCrud.components.*', // AweCrud components ),
4) Register the AweCrud messages directory, like the example below.
'components' => array( ... 'messages' => array ( 'extensionPaths' => array( 'AweCrud' => 'ext.AweCrud.messages', // AweCrud messages directory. ), ), ),
This extension is a kind of merge among several Gii extensions, looking for simplicity for Gii and a powerful code generator integrated with Cruge.
This extension borrows some ideas and code from other extensions like iCrud, GTC, Yii-Booster, GiiX, AweGen, Yii-Bootstrap and mix them all making a much simpler but powerful Gii extension plus Bootstrap look-and-feel.
Total 12 comments
@aleksdj Could you please report the bug in the forum? Including the details of the error and structure of the class inheritance?
Im having some problems. -Some of your classes dont import all the components clases inside ext.awecrud.components and fails. -LoadModel and perform ajax validation functions of generated controllers is not compatible with father class "AweController" meaning signature is different -I downloaded last 1.12 version of yii but the problems with messages using yii:t('Awecrud.app') still persists
@aleksdj @rosoft2001 It's not a matter o bad practices, it is a matter of taking advantage of future features and moving forward with "Yii-trend". If you don't want to use i18n feature, just skip it and use the extension without it ;)
You cannot base an extension in a development Yii version, I think is a matter of best practices... any solution for yii stable 1.1.12 version?
Even if it's cool to use the latest features from the development yii version, I can't chase this, mostly because of my limited knowledge.
I will wait until this work out of the box with the yii released version.
Just post a comment when this would happen and I will try it again.
Thanks
For those who are experiencing issues with "extensionPaths" parameter(Property "CPhpMessageSource"."extensionPaths" is not defined), please download the latest dev version of Yii from Yii GitHub official repository
@rosoft2001 Please check you're using Yii 1.1.12. That property has been inherited from CodeModel (a Gii core class).
installed, generated model and crud for a table, then i get this error can't get out of it.
(regular model crud still working)
@WebDevPT I hope to upload a screenshot soon!
@schmunk No, this extension just borrows some ideas from Awegen (and some other extensions)... but looking a more "bootstrap-purist" way.
Is it related to http://www.yiiframework.com/extension/awegen?
Hi! Looking forward to test this, but please consider adding a screenshot or a demo here.
Leave a comment
Please login to leave your comment.