settings

The component has been updated to version 1.2 with some new goodies (see changelog) Please test it and report any bug you find. Thanks.

This would require to have some kind of registry to store permanently all the defined categories that are cached, and it might be a good thing to have something like:

Yii::app()->settings->clearCache(); //clear all the cached content  
Yii::app()->settings->clearCache('category'); // clear only this category cache.

So i'll take it into consideration and implement it :)

Can we have a method where clear the cache for all groups? (I have a migration that inserts some values into the settings table, and I would like to call a method after that to clear the cache.)

I opened a new topic here: http://www.yiiframework.com/forum/index.php?/topic/23075-extensionsettings/ , please add the file as an attachment there and i'll check it and in the end implement your changes.

please create a post to discuss about the extension.

I've made a modified version of the extension that I would like to share.

Basically what I've changed is that I added a public property named 'tableName' with default value '{{settings}}' so you can easiely change the name of the table to use and this change also removes the need to add tablePrefix if you don't use it.

I've also added a connectionId property that defaults to 'db' and a getDbConnection method, replacing all Yii::app()->db to $this->getDbConnection so you can use a different db connection.

And a couple more things

Btw, great extension.

Thanks

Just now i saw the comments, don't know why but the yii website doesn't send notifications anymore for comments on my extensions.

@Wiseon3 - the values shouldn't be manipulated directly from database. And i prefer to use the serialize/unserialize functions to store all kind of data in the database.
Anyway, glad to hear this isn't another bug:)

@yiqing95 - sorry, right now i don't have too much available time, but i will take it into consideration.

@twisted1919 It seems the problem I had was due to the fact that I inserted the values by hand in the db (using phpmyadmin) instead of using the functions provided by the extension, which serialize the values before saving them to the db. Sorry about that.

@twisted1919 I encountered the same bug as ryurhrt After looking trough the code, I found what the problem is: In the load() function you unserialize every corresponding key value from the database. If the value is a string then the function returns false as it is unserializeable. To fix it, simply replace:

foreach($result AS $row)
                $items[$row['key']] = @unserialize($row['value']);

with

foreach($result AS $row) {
                $value = @unserialize($row['value']);
                if ($value === false)
                    $value = $row['value'];
                $items[$row['key']] = $value;
            }

@twisted1919 : I am here again :)

now my situation is this: the table your provided is different from mine. but the

table fields have same semantics , only i need is tableName and table fields mapping.

so i need something like this:

public $tableName = 'settings'; /*default name is your name for those guys who           firstly use this setting feature,and use your schema above .*/
    public $idAttribute='id';
    public $categoryAttribute='category';
    public $keyAttribute='key';
        public $valueAttribute='value';

then in your code reference above values: {$this->tableName} , {$this->xxAttibute} , thus these extension can apply to the tables existing early ,

surely i can do it myself ,but if you can add it will be better :). best regards !

Good to hear, but don't worry, thanks to you the extension has been improved and some bugs were fixed, so you did a great job reporting all of these.

Hi,

Sorry for the false bugs report, as I actually code to read the configuration with a class of my own, and i forgot the switch the reading class to read from the settings, and it read back to the yii's settings, so even i reset the value, it still reading the wrong place.

sorry for that, but now the module work correctly without any problem, thanks.

Well, i cannot reproduce what you are saying, at least here is the test i made:

$settings=Yii::app()->settings;  
echo $settings->get('test','itemAlreadySet').'<br />';  
$settings->set('test','aNewItem','aNewValue');  
echo $settings->get('test','aNewItem').'<br />';  
$settings->set('test','aNewItem','aNewValueOverwritten');  
echo $settings->get('test','aNewItem').'<br />';  
$settings->set('test','itemAlreadySet','rewrite this value');  
echo $settings->get('test','itemAlreadySet').'<br />';

And the output of the above code:

valueAlreadySet  
aNewValue  
aNewValueOverwritten  
rewrite this value

Which seems correct to me.
Next step was just to retrieve the values i just set above:

$settings=Yii::app()->settings;
echo $settings->get('test','itemAlreadySet').'<br />';
echo $settings->get('test','aNewItem').'<br />';

Which outputs:

rewrite this value  
aNewValueOverwritten

So, once again, it is correct.

As you see, the code works exaclty as expected, that's the reason why i can't find any error.
I will gladly look into your issue, but please post some code so that i can run it in my backend and see if it fails or not.

Hi,

after tested the new code, i found that i can't set the settings, which means at the same page, i do set the value to another, but the get back the old value.

any idea?

Please ignore my above PHP code (not the cache advices) and try this version, just overwrite the component class with this one :
Paste Bin Code

@ryurhrt - thanks for your tests, i also appreciate your time .
Let's test a few things and see where we go next:
1) Change the get method like:

// line 49 
public function get($category='system', $key='', $default='')  
    {  
        if(!isset($this->_items[$category]))  
        {  
            $this->load($category);      
        }  
 
        if(!isset($this->_loaded[$category]))  
        {  
            $this->load($category);  
            $this->_items[$category]=array_merge($this->_loaded[$category],$this->_items[$category]);  
        }  
 
        if(empty($key)&&empty($default)&&!empty($category))  
            return isset($this->_items[$category])?$this->_items[$category]:null;  
 
        if(isset($this->_items[$category][$key]))  
            return $this->_items[$category][$key];  
        return !empty($default)?$default:null;  
    }

After doing the change, test it and see if the bug still persists, if it does, then let's do a more direct approach to the get function:

// line 49 
public function get($category='system', $key='', $default='')  
    {  
        if(!isset($this->_loaded[$category]))  
        {  
            $this->load($category);  
            $this->_items[$category]=array_merge($this->_loaded[$category],$this->_items[$category]);  
        }  
 
        if(empty($key)&&empty($default)&&!empty($category))  
            return isset($this->_items[$category])?$this->_items[$category]:null;  
 
        if(isset($this->_items[$category][$key]))  
            return $this->_items[$category][$key];  
        return !empty($default)?$default:null;  
    }

Also, what i would ask you to do in your tests, is to clear the cache folder before you do each test, because when you move the project to a new site the old cache might be invalidated and the tests will not be accurate.
So, clear the cache, run the test, see the restult, and repeat the steps each time.
Please let me know of your findings so that i can update the component if indeed what you just explained is a bug :)
Thank you for your time on this .

Hi, i finally repeated the bugs which return "false" value.

the bugs is occur in another testing server where the server do not call any "set" function yet, as all the settings had been called and saved using my development, so no matter how many times we called "get" function, the value return is "false", but after run at least once the "set" function, then all the "get" function works.

i would guess it happen because of caching not yet initialized? any idea to resolve this issue beside calling set function every time server reboot or implement to new machine?

Thanks.

@twisted1919

I had tested, I guess the bug is now fixed.

However, I am not so sure about it, because the 1st time when I run the test, it return a Boolean "false" for me, but once after I refresh it, it works without any problem, and I could not repeat the fault.

anyway, well done. Thanks. :D

I understood your requirement since first time, don't worry.
The thing is that, integrating this will make the component heavier, thing i don't want right now, i want to keep this as light as possible.
And yes, i agree with you that doing this in one of the way i shown you can be a bit hard with large sets of data, but it is doable, so for now, you'd have to work with it as it is.
In my projects, where the items need description, i use one of the two methods i shown, and i have no problems.
Of course, there is always the second option, modify the component to fit your needs, nobody says you cannot do this :)

It is nice that I can save complex data. But the descriptions I am refering would be set/retrieved rarely when the administrator edits in the CMS admin. The descriptions are used only for the admins and would describe what each value means, not used by the read/write mechanism. It would be too complex to store each value as an associative array, and have a value and a description field each time. It would make things harder when you need to display a value from the associative array. Is it clear the description requirement?

Another way, would be like:

$data=array(  
'phone'   =>   array(  
   'value'      =>'0123456789',  
   'description'=>'this is the phone number of the administrator',
),  
'email'   =>   array(  
   'value'   =>'admin@domain.com',  
   'description'=>'this is the email address of the administrator', 
)    
);  
Yii::app()->settings->set('admin',$data);  
//  
$phone=Yii::app()->settings->get('admin','phone');   
echo $phone['value'].' - '.$phone['description'];

As you see, we have some alternatives :)