Yii2 $model->_attributes assignment does not work in new version












1















I inherited a project that was created with Yii2, ver. 2.0.4, with the task to update said project to a more current version of Yii2 (2.0.15) because of the incompatibility of the older one with PHP 7.2+.



I noticed that there is a lot of use of assigning arrays to a model:



$model->_attributes = $array;


With the new version this results in an exception



'yiibaseUnknownPropertyException' with message 'Setting unknown property: appmodelsmodel::_attributes'


For the time being I created a workaround with the following function:



function customSetAttributes(&$model, $array) {

    foreach($model->attributeLabels() as $model_key => $model_label) {

        if(!isset($array[$model_key])) continue;

        $model->$model_key = $array[$model_key];

    }

}


Also, the getter function now has a similar issue.



What I would like to know:




  • Was this type of assignment never intended in the first place (and I just haven't found the previous developer's code that enables it)? I skimmed over the Yii2 changelog but didn't notice anything related.

  • Is there a way to "salvage" the previous behaviour so I don't have to replace each occurence with my workaround function?






php yii2 getter-setter







share|improve this question























  • this was never used like above even in the version you specified are those actual controllers under the app/controllers directory

    – Muhammad Omer Aslam
    Nov 19 '18 at 18:02


















1















I inherited a project that was created with Yii2, ver. 2.0.4, with the task to update said project to a more current version of Yii2 (2.0.15) because of the incompatibility of the older one with PHP 7.2+.



I noticed that there is a lot of use of assigning arrays to a model:



$model->_attributes = $array;


With the new version this results in an exception



'yiibaseUnknownPropertyException' with message 'Setting unknown property: appmodelsmodel::_attributes'


For the time being I created a workaround with the following function:



function customSetAttributes(&$model, $array) {

    foreach($model->attributeLabels() as $model_key => $model_label) {

        if(!isset($array[$model_key])) continue;

        $model->$model_key = $array[$model_key];

    }

}


Also, the getter function now has a similar issue.



What I would like to know:




  • Was this type of assignment never intended in the first place (and I just haven't found the previous developer's code that enables it)? I skimmed over the Yii2 changelog but didn't notice anything related.

  • Is there a way to "salvage" the previous behaviour so I don't have to replace each occurence with my workaround function?






php yii2 getter-setter







share|improve this question























  • this was never used like above even in the version you specified are those actual controllers under the app/controllers directory

    – Muhammad Omer Aslam
    Nov 19 '18 at 18:02
















1












1








1








I inherited a project that was created with Yii2, ver. 2.0.4, with the task to update said project to a more current version of Yii2 (2.0.15) because of the incompatibility of the older one with PHP 7.2+.



I noticed that there is a lot of use of assigning arrays to a model:



$model->_attributes = $array;


With the new version this results in an exception



'yiibaseUnknownPropertyException' with message 'Setting unknown property: appmodelsmodel::_attributes'


For the time being I created a workaround with the following function:



function customSetAttributes(&$model, $array) {

    foreach($model->attributeLabels() as $model_key => $model_label) {

        if(!isset($array[$model_key])) continue;

        $model->$model_key = $array[$model_key];

    }

}


Also, the getter function now has a similar issue.



What I would like to know:




  • Was this type of assignment never intended in the first place (and I just haven't found the previous developer's code that enables it)? I skimmed over the Yii2 changelog but didn't notice anything related.

  • Is there a way to "salvage" the previous behaviour so I don't have to replace each occurence with my workaround function?






php yii2 getter-setter







share|improve this question














I inherited a project that was created with Yii2, ver. 2.0.4, with the task to update said project to a more current version of Yii2 (2.0.15) because of the incompatibility of the older one with PHP 7.2+.



I noticed that there is a lot of use of assigning arrays to a model:



$model->_attributes = $array;


With the new version this results in an exception



'yiibaseUnknownPropertyException' with message 'Setting unknown property: appmodelsmodel::_attributes'


For the time being I created a workaround with the following function:



function customSetAttributes(&$model, $array) {

    foreach($model->attributeLabels() as $model_key => $model_label) {

        if(!isset($array[$model_key])) continue;

        $model->$model_key = $array[$model_key];

    }

}


Also, the getter function now has a similar issue.



What I would like to know:




  • Was this type of assignment never intended in the first place (and I just haven't found the previous developer's code that enables it)? I skimmed over the Yii2 changelog but didn't notice anything related.

  • Is there a way to "salvage" the previous behaviour so I don't have to replace each occurence with my workaround function?






php yii2 getter-setter




php yii2 getter-setter






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 17:02









arkxlarkxl

83




83













  • this was never used like above even in the version you specified are those actual controllers under the app/controllers directory

    – Muhammad Omer Aslam
    Nov 19 '18 at 18:02





















  • this was never used like above even in the version you specified are those actual controllers under the app/controllers directory

    – Muhammad Omer Aslam
    Nov 19 '18 at 18:02



















this was never used like above even in the version you specified are those actual controllers under the app/controllers directory

– Muhammad Omer Aslam
Nov 19 '18 at 18:02







this was never used like above even in the version you specified are those actual controllers under the app/controllers directory

– Muhammad Omer Aslam
Nov 19 '18 at 18:02














1 Answer
1






active

oldest

votes


















3














ActiveRecord::$_attributes was always private and never should be used in this way. I guess that previous developer edited framework core files in vendor directory and make this property protected/public.



You may try to emulate this behavior by creating virtual attribute using getter and setter:



public function get_attributes() {

    return $this->getAttributes();

}



public function set_attributes($values) {

    $this->setAttributes($values, false);

}


But this will not always work and it is more like an ugly hack to make crappy code work. I strongly suggest to fix code to use setAttributes() instead of _attributes.



Also you should compare yii2 package from vendor directory with source from https://github.com/yiisoft/yii2-framework/releases/tag/2.0.4 - you may find more places where core was edited.






share|improve this answer



















  • 1





    Thanks, so far I got by using setAttributes() and getAttributes().

    – arkxl
    Nov 21 '18 at 9:01











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379451%2fyii2-model-attributes-assignment-does-not-work-in-new-version%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














ActiveRecord::$_attributes was always private and never should be used in this way. I guess that previous developer edited framework core files in vendor directory and make this property protected/public.



You may try to emulate this behavior by creating virtual attribute using getter and setter:



public function get_attributes() {

    return $this->getAttributes();

}



public function set_attributes($values) {

    $this->setAttributes($values, false);

}


But this will not always work and it is more like an ugly hack to make crappy code work. I strongly suggest to fix code to use setAttributes() instead of _attributes.



Also you should compare yii2 package from vendor directory with source from https://github.com/yiisoft/yii2-framework/releases/tag/2.0.4 - you may find more places where core was edited.






share|improve this answer



















  • 1





    Thanks, so far I got by using setAttributes() and getAttributes().

    – arkxl
    Nov 21 '18 at 9:01
















3














ActiveRecord::$_attributes was always private and never should be used in this way. I guess that previous developer edited framework core files in vendor directory and make this property protected/public.



You may try to emulate this behavior by creating virtual attribute using getter and setter:



public function get_attributes() {

    return $this->getAttributes();

}



public function set_attributes($values) {

    $this->setAttributes($values, false);

}


But this will not always work and it is more like an ugly hack to make crappy code work. I strongly suggest to fix code to use setAttributes() instead of _attributes.



Also you should compare yii2 package from vendor directory with source from https://github.com/yiisoft/yii2-framework/releases/tag/2.0.4 - you may find more places where core was edited.






share|improve this answer



















  • 1





    Thanks, so far I got by using setAttributes() and getAttributes().

    – arkxl
    Nov 21 '18 at 9:01














3












3








3







ActiveRecord::$_attributes was always private and never should be used in this way. I guess that previous developer edited framework core files in vendor directory and make this property protected/public.



You may try to emulate this behavior by creating virtual attribute using getter and setter:



public function get_attributes() {

    return $this->getAttributes();

}



public function set_attributes($values) {

    $this->setAttributes($values, false);

}


But this will not always work and it is more like an ugly hack to make crappy code work. I strongly suggest to fix code to use setAttributes() instead of _attributes.



Also you should compare yii2 package from vendor directory with source from https://github.com/yiisoft/yii2-framework/releases/tag/2.0.4 - you may find more places where core was edited.






share|improve this answer













ActiveRecord::$_attributes was always private and never should be used in this way. I guess that previous developer edited framework core files in vendor directory and make this property protected/public.



You may try to emulate this behavior by creating virtual attribute using getter and setter:



public function get_attributes() {

    return $this->getAttributes();

}



public function set_attributes($values) {

    $this->setAttributes($values, false);

}


But this will not always work and it is more like an ugly hack to make crappy code work. I strongly suggest to fix code to use setAttributes() instead of _attributes.



Also you should compare yii2 package from vendor directory with source from https://github.com/yiisoft/yii2-framework/releases/tag/2.0.4 - you may find more places where core was edited.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 19 '18 at 17:51









rob006rob006

9,89131133




9,89131133








  • 1





    Thanks, so far I got by using setAttributes() and getAttributes().

    – arkxl
    Nov 21 '18 at 9:01














  • 1





    Thanks, so far I got by using setAttributes() and getAttributes().

    – arkxl
    Nov 21 '18 at 9:01








1




1





Thanks, so far I got by using setAttributes() and getAttributes().

– arkxl
Nov 21 '18 at 9:01





Thanks, so far I got by using setAttributes() and getAttributes().

– arkxl
Nov 21 '18 at 9:01




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379451%2fyii2-model-attributes-assignment-does-not-work-in-new-version%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

這個網誌中的熱門文章

Tangent Lines Diagram Along Smooth Curve

圖片
7 1 I am trying to replicate a diagram and have a minimal example. I don't know how to add additional tangents between the specified points and preserve smoothness. documentclass{article} usepackage{tikz} usetikzlibrary{calc,intersections} begin{document} begin{tikzpicture} % Axes draw [->, name path=x] (-1,0) -- (11,0) node [right] {$x$}; draw [->] (0,-1) -- (0,6) node [above] {$y$}; % Origin node at (0,0) [below left] {$0$}; % Points coordinate (start) at (1,-0.8); coordinate (c1) at (3,3); coordinate (c2) at (5.5,1.5); coordinate (c3) at (8,4); coordinate (end) at (10.5,-0.8); % show the points foreach n in {start,c1,c2,c3,end} fill [black] (n) circle (2pt) node [below] {}; % join the coordinates draw [thick,name path=curve] (start) to[out=70,in=180] (c1) to[out=0,in=180]
閱讀完整內容

Yusuf al-Mu'taman ibn Hud

圖片
Main article: Taifa of Zaragoza Al-Mu'taman Ruler of Zaragoza Reign 1081–1085 Predecessor Ahmad al-Muqtadir Successor Al-Mustain II Born Zaragoza Died 1085 Full name Yusuf ibn Ahmad al-Mu'taman ibn Hūd House Banu Hud Yusuf ibn Ahmad al-Mu'taman ibn Hūd (Arabic: المؤتمن بالله يوسف إبن أحمد إبن هود ‎, al-Mutaman bi l-Lah , died c. 1085) was the third king of the Banu Hud dynasty who ruled over the Taifa of Zaragoza from 1081 to 1085. Yusuf al-Mutaman reigned during the height of power of Muslim Zaragoza , following the thriving period of his father Ahmad al-Muqtadir. He continued his father's efforts and created around him a court of intellectuals, living in the beautiful palace of Aljafería, nicknamed as "the palace of joy". Al-Mu'taman was also a scholarly king and a patron of science, philosophy and arts. As an example of a wise king, he knew astrology, philosophy, and especially mathematics, a discipline in which
閱讀完整內容

Zucchini

圖片
This article is about the vegetable. For other uses, see Zucchini (disambiguation). Zucchini (courgette) A striped and a uniform color zucchini Genus Cucurbita Species Cucurbita pepo Origin 19th century northern Italy The zucchini ( / z uː ˈ k iː n i / , American English) or courgette ( / k ʊər ˈ ʒ ɛ t / , British English) is a summer squash which can reach nearly 1 metre (100 cm; 39 in) in length, but is usually harvested when still immature at about 15 to 25 cm (6 to 10 in). [1] A zucchini is a thin-skinned cultivar of what in Britain and Ireland is referred to as a marrow. [2] [3] In South Africa, a zucchini is known as a baby marrow. Along with certain other squashes and pumpkins, the zucchini belongs to the species Cucurbita pepo . It can be dark or light green. A related hybrid, the golden zucchini, is a deep yellow or orange color. [4] In a culinary context, the zucchini is treated as a vegetable; it is usually cooked and presented as a savory dish o
閱讀完整內容