Working with scenarios, with models that can receive many modifications in their rules or structures as development evolves, can create disruptions in the rescue process.
Following is the table structure
CREATE TABLE IF NOT EXISTS `tblgroups` ( `id` int(11) NOT NULL, `groupname` varchar(150) NOT NULL, `status` tinyint(1) NOT NULL DEFAULT '1' COMMENT '1=Acitve,2=Inactive', `date` datetime NOT NULL ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
Bootstrap tabs gets unselected/inactive when user navigates to other page and comes back. How to make bootstrap tabs remain active/selected after navigating to different web pages.
Welcome, all of you !
It is convenient to use the same identification attribute, say
info, in all of the active records of your application. It should be a virtual read-only attribute defined by a getter method, its label being the model name.
Using a version control system, like Git, is nice. However, when building an extension from scratch and loading it via Composer, it adds a lot of pain in the butt steps. You have to commit your changes, update composer to pull them over, then notice there is an error, fix, commit, update. repeat.. I don't want all my baby steps under Git. Sure, I could edit my commit history, but c'mon. Just let m...
I just chased my tail around for a bit today. I got lost with setting the status of all inputs, and banging my head on why the "validate" function just wasn't working.
If you want to give extra attention for some specific delete actions and you don't want to override whole yii.confirm JS method here is what you can do:
(I've only put the ActionColumn part of the GridView here to just give you the idea)
Assume we have many categories and many posts.
It's well known that there are Lazy Loading approach and Eager Loading approach in the relational query. But it's very important to know how the Eager Loading approach works in Yii 2. It has changed drastically from that of Yii 1.1, and there are common misunderstandings about it in the community.
I've read many comments that it's not possible to install Yii 2 advanced on a shared hosting environment, as it has two webroots. This is partially true.