After reading a lot of forum posts, I can see that Typeahead and CJuiAutoComplete were not designed to work with "value and display" attributes of related models so you can use the required value/id of a selected display/name to submit for model creation/update.

Typeahead and CJuiAutoComplete seem to behave like "simple" autocomplete textboxes and I couldn't see an easy way to implement the value/display attributes behavior.

Fortunately for me, I found the select2 extension and it was as simple as copying the extension folder and using the following in a view:

Awesome extension man, this has the potential to take my project to the next level and I really appreciate all the work both you and Chris have put into it.

Regarding StickyTableHeaders (with filters),

My tbody collapses when the sticky header is active. I also noticed that the booster site has the same problem. You know a way to fix this? I tried tbody: min-width and width, neither seems to affect the collapsing problem.

Thanks again for all your hard work.

Could you tell me what is the browser you are using? I found my self having to modify some of the jquery plugins used, maybe this is one of the cases

¿How long would it take for you to understand that you own nothing in this world?

After reading a lot of forum posts, I can see that Typeahead and CJuiAutoComplete were not designed to work with "value and display" attributes of related models so you can use the required value/id of a selected display/name to submit for model creation/update.

Typeahead and CJuiAutoComplete seem to behave like "simple" autocomplete textboxes and I couldn't see an easy way to implement the value/display attributes behavior.

Fortunately for me, I found the select2 extension and it was as simple as copying the extension folder and using the following in a view:

Wonder if anyone else has had a similar issue. I am using An TBEditableField within a CGridview (using renderpartial) which is working fine. However I also have a dropdown box and AJAX button which add an item to the Gridview and causes the Gridview to refresh. When this happens the TBeditableFields stop working until you manually reload the page using F5. I have attached screenshot of what happens.

I can see from firebug that when the Gridview refreshes the items lose the editable attributes

Wonder if anyone else has had a similar issue. I am using An TBEditableField within a CGridview (using renderpartial) which is working fine. However I also have a dropdown box and AJAX button which add an item to the Gridview and causes the Gridview to refresh. When this happens the TBeditableFields stop working until you manually reload the page using F5. I have attached screenshot of what happens.

I can see from firebug that when the Gridview refreshes the items lose the editable attributes

Thank you so much for your wishes... my son came out great... everything went fine...

I am sorry but it seems there is an issue with the CSS... will talk to the designer at the company trying to figure out what is the reason of such behavior. If you could provide some example code for us, would be highly appreciated.

Thanks!

¿How long would it take for you to understand that you own nothing in this world?

Would you please specify in the YiiBooster documentation the options available for 'select2'? I mean the options that you made available in your YiiBooster implementation and that there are not documentation available elsewhere (e.g. 'asDropDownList' property), not the full set of options that we can set in the 'options' property (which we can read in the 'select2' official documentation). It would be a great plus for the documentation of YiiBooster to have something like this for every component.

Of course, only if there are new options/properties introduced by you in your YiiBooster implementation. Those are the options that I'm referring to, that I think it's a good idea to list and document in every component.

Would you please specify in the YiiBooster documentation the options available for 'select2'? I mean the options that you made available in your YiiBooster implementation and that there are not documentation available elsewhere (e.g. 'asDropDownList' property), not the full set of options that we can set in the 'options' property (which we can read in the 'select2' official documentation). It would be a great plus for the documentation of YiiBooster to have something like this for every component.

Of course, only if there are new options/properties introduced by you in your YiiBooster implementation. Those are the options that I'm referring to, that I think it's a good idea to list and document in every component.

I am planning to create a new repository at git, to work for the API Docs. I am so busy right now that is nearly impossible to do it alone and keep up with new versions.

Will let you know when it happens

Thanks

¿How long would it take for you to understand that you own nothing in this world?

you didn't include TbExtendedFilter in version 1.0.4. I was really looking forward to it... bummer!

An observation: Shouldn't the input for TbSelect2 have round corners, too?

Another question: Is there any way to omit the highlighting of errors in forms? It would be quite useful if there were the following boolean options: highlightErrorsOnLabels, highlightErrorsOnInputs, highlightErrorsOnHelpers. Of course the default is true. When set to false the element will not be highlighted red if there is any error.

Edit: The original option "errorMessageCssClass" gets overwritten in TbActiveForm and it would only effect the help-block (not the label and input) hence the overwrite.