alkemann - Project Hosting on Google Code

Earlier this year Jun 03, 2009 issue 32 (Option to save changes in serialized array) Status changed by alek.morland - This is part of your later update submission? I can close this now? Status: NeedMoreInfo This is part of your later update submission? I can close this now? Status: NeedMoreInfo Jun 03, 2009 issue 31 (The build in JSON class from Prototype conflicts with Mootoo...) Status changed by alek.morland - Commited your diff. Thank you for contribution. Status: Done Commited your diff. Thank you for contribution. Status: Done Jun 03, 2009 r232 (commit of jelle.henkens mooltools option) committed by alek.morland - commit of jelle.henkens mooltools option commit of jelle.henkens mooltools option Jun 03, 2009 issue 36 (Logable: Add an ability to temporary disable and reenable be...) changed by alek.morland - Thank you for contribution. Since all my tests bass, I commited your changes as version 2.2 and added your name to the contributor list. If you have created tests for your added logic, please submit them as well. Status: Done Owner: alek.morland Labels: Type-Enhancement −Type-Defect Thank you for contribution. Since all my tests bass, I commited your changes as version 2.2 and added your name to the contributor list. If you have created tests for your added logic, please submit them as well. Status: Done Owner: alek.morland Labels: Type-Enhancement −Type-Defect Jun 03, 2009 r231 (Commiting updates from Miha to implement enable/disable feat...) committed by alek.morland - Commiting updates from Miha to implement enable/disable feature and configurable model. Version 2.2 pass all tests, but new features has not been made tests for. Commiting updates from Miha to implement enable/disable feature and configurable model. Version 2.2 pass all tests, but new features has not been made tests for. Jun 02, 2009 issue 36 (Logable: Add an ability to temporary disable and reenable be...) reported by m...@nahtigal.com - Sometimes it is necessary to temporary disable logging. Here's an example: when user logs in, last_login field is updated. I don't want this change to be visible to front end users, not even admins (a change to a User model is logged after each successful login). So before saving last_login, I would like to disable Loggable and then reenable it. I've already implemented this functionality (alogside all other issues I've submitted here) and can be found in file attached below. Sometimes it is necessary to temporary disable logging. Here's an example: when user logs in, last_login field is updated. I don't want this change to be visible to front end users, not even admins (a change to a User model is logged after each successful login). So before saving last_login, I would like to disable Loggable and then reenable it. I've already implemented this functionality (alogside all other issues I've submitted here) and can be found in file attached below. May 27, 2009 issue 35 (sub domain issues) reported by adbrett - What steps will reproduce the problem? 1. standard "basic bar chart" example 2. standard cakephp app 3. installed on a subdomain http://xxx.myapp.com What is the expected output? What do you see instead? a graph, just a white square What version of the product are you using? On what operating system? latest Please provide any additional information below. there isn't any - uploaded all the provided files, copy + pasted example, nothing happens. What steps will reproduce the problem? 1. standard "basic bar chart" example 2. standard cakephp app 3. installed on a subdomain http://xxx.myapp.com What is the expected output? What do you see instead? a graph, just a white square What version of the product are you using? On what operating system? latest Please provide any additional information below. there isn't any - uploaded all the provided files, copy + pasted example, nothing happens. May 22, 2009 issue 34 (Bug fix X axis vertical) reported by deca.rox - What steps will reproduce the problem? 1. set the vertical X axis = true What is the expected output? What do you see instead? display the label X axis in vertical mode What version of the product are you using? On what operating system? 3.3.7 Please provide any additional information below. I fix the bug in the flashchart.php. I swapped the condition in line 876: the line, before verify if $options['vertical'] started, and your value = true. if (isset($options['vertical']) && $options['vertical'] == true) { it's not necessary when your value is true because the variable has started. the fix it's only ($labelsOptions['vertical'] == true) the correct variable is $labelsOptions["vertical"], because when your started your method, you send a vertical value in 3rd value ($labelOptions), not 2rd value($options) it's fix the problem. regards Anderson Alcantara What steps will reproduce the problem? 1. set the vertical X axis = true What is the expected output? What do you see instead? display the label X axis in vertical mode What version of the product are you using? On what operating system? 3.3.7 Please provide any additional information below. I fix the bug in the flashchart.php. I swapped the condition in line 876: the line, before verify if $options['vertical'] started, and your value = true. if (isset($options['vertical']) && $options['vertical'] == true) { it's not necessary when your value is true because the variable has started. the fix it's only ($labelsOptions['vertical'] == true) the correct variable is $labelsOptions["vertical"], because when your started your method, you send a vertical value in 3rd value ($labelOptions), not 2rd value($options) it's fix the problem. regards Anderson Alcantara Apr 27, 2009 issue 31 (The build in JSON class from Prototype conflicts with Mootoo...) changed by alek.morland - Status: Accepted Owner: alek.morland Labels: Type-Enhancement Project-FlashChartHelper −Type-Defect Status: Accepted Owner: alek.morland Labels: Type-Enhancement Project-FlashChartHelper −Type-Defect Apr 27, 2009 issue 32 (Option to save changes in serialized array) changed by alek.morland - Status: Accepted Owner: alek.morland Labels: Type-Enhancement Project-LogableBehavior −Type-Defect Status: Accepted Owner: alek.morland Labels: Type-Enhancement Project-LogableBehavior −Type-Defect Apr 27, 2009 issue 33 (Logable: Configurable filed names for model and model_id fie...) changed by alek.morland - Status: Accepted Owner: alek.morland Labels: Project-LogableBehavior Status: Accepted Owner: alek.morland Labels: Project-LogableBehavior Apr 27, 2009 issue 33 (Logable: Configurable filed names for model and model_id fie...) reported by m...@nahtigal.com - There are fixed field names for model and model_id fields. Please make them configurable. I've attached slightly modified version of your loggable behavior. There are three minor changes: 1. configurable field names for model and model_id 2. serialized option for changes 3. changed model instantiation (instead of App::import use ClassRegistry::init()) - I've had some problems because in my test cases testAction() use production database instead of test database; this doesn't happen when models are instanced via ClassRegistry::init() There are fixed field names for model and model_id fields. Please make them configurable. I've attached slightly modified version of your loggable behavior. There are three minor changes: 1. configurable field names for model and model_id 2. serialized option for changes 3. changed model instantiation (instead of App::import use ClassRegistry::init()) - I've had some problems because in my test cases testAction() use production database instead of test database; this doesn't happen when models are instanced via ClassRegistry::init() Apr 25, 2009 issue 32 (Option to save changes in serialized array) commented on by m...@nahtigal.com - And of course it concerns the Logable behavior. And of course it concerns the Logable behavior. Apr 25, 2009 issue 32 (Option to save changes in serialized array) commented on by m...@nahtigal.com - Sorry, this ticket should be marked as enhancement. Sorry, this ticket should be marked as enhancement. Apr 25, 2009 issue 32 (Option to save changes in serialized array) reported by m...@nahtigal.com - It would be useful to have an ability to fetch modified data in array (for custom display of changes) Sth like this (from line 377): {{{ if (isset($this->Log->_schema['change'])) { $logData['Log']['change'] = ''; $db_fields = array_keys($Model->_schema); $changed_fields = array(); foreach ($Model->data[$Model->alias] as $key => $value) { if (isset($Model->data[$Model->alias][$Model->primaryKey]) && !empty($this->old) && isset($this->old[$Model->alias][$key])) { $old = $this->old[$Model->alias][$key]; } else { $old = ''; } if ($key != 'modified' && !in_array($key, $this->settings[$Model->alias]['ignore']) && $value != $old && in_array($key,$db_fields) ) { if ($this->settings[$Model->alias]['change'] == 'full') { $changed_fields[] = $key . ' ('.$old.') => ('.$value.')'; } else if ($this->settings[$Model->alias]['change'] == 'serialize') { $changed_fields[$key] = array('old'=>$old, 'value'=>$value); } else { $changed_fields[] = $key; } } } $changes = sizeof($changed_fields); if ($changed_fields == 0) { return true; } if ($this->settings[$Model->alias]['change'] == 'serialize') { $logData['Log']['change'] = serialize($changed_fields); } else { $logData['Log']['change'] = implode(', ',$changed_fields); } $logData['Log']['changes'] = $changes; } $this->_saveLog($Model, $logData); }}} It would be useful to have an ability to fetch modified data in array (for custom display of changes) Sth like this (from line 377): {{{ if (isset($this->Log->_schema['change'])) { $logData['Log']['change'] = ''; $db_fields = array_keys($Model->_schema); $changed_fields = array(); foreach ($Model->data[$Model->alias] as $key => $value) { if (isset($Model->data[$Model->alias][$Model->primaryKey]) && !empty($this->old) && isset($this->old[$Model->alias][$key])) { $old = $this->old[$Model->alias][$key]; } else { $old = ''; } if ($key != 'modified' && !in_array($key, $this->settings[$Model->alias]['ignore']) && $value != $old && in_array($key,$db_fields) ) { if ($this->settings[$Model->alias]['change'] == 'full') { $changed_fields[] = $key . ' ('.$old.') => ('.$value.')'; } else if ($this->settings[$Model->alias]['change'] == 'serialize') { $changed_fields[$key] = array('old'=>$old, 'value'=>$value); } else { $changed_fields[] = $key; } } } $changes = sizeof($changed_fields); if ($changed_fields == 0) { return true; } if ($this->settings[$Model->alias]['change'] == 'serialize') { $logData['Log']['change'] = serialize($changed_fields); } else { $logData['Log']['change'] = implode(', ',$changed_fields); } $logData['Log']['changes'] = $changes; } $this->_saveLog($Model, $logData); }}} Apr 23, 2009 issue 31 (The build in JSON class from Prototype conflicts with Mootoo...) reported by jelle.henkens - What steps will reproduce the problem? 1. Load mootools 1.2 core with JSON 2. echo $flashChart->begin(); What is the expected output? What do you see instead? Because the json/json2.js tries to create itself which it cant, JSON.stringify will fail because that function doesnt exist in mootools's JSON. What version of the product are you using? On what operating system? version 3.3.8 Please provide any additional information below. Attached a patch to support mootools. Greetings, Jelle 'Lemon_BE' Henkens What steps will reproduce the problem? 1. Load mootools 1.2 core with JSON 2. echo $flashChart->begin(); What is the expected output? What do you see instead? Because the json/json2.js tries to create itself which it cant, JSON.stringify will fail because that function doesnt exist in mootools's JSON. What version of the product are you using? On what operating system? version 3.3.8 Please provide any additional information below. Attached a patch to support mootools. Greetings, Jelle 'Lemon_BE' Henkens Apr 14, 2009 ThumbviewHelper_1.0.rar (Add thumbnail and links to fullsize view of images) file uploaded by alek.morland - Labels: Featured Helper Beta Labels: Featured Helper Beta Mar 30, 2009 MultilingualBehavior (instructions on how to use Multilingual behavior) Wiki page edited by alek.morland Mar 30, 2009 MultilingualBehavior (instructions on how to use Multilingual behavior) Wiki page edited by alek.morland Mar 30, 2009 MultilingualBehavior (instructions on how to use Multilingual behavior) Wiki page added by alek.morland Mar 28, 2009 RevisionBehavior_2.0.4.rar (Version control of models, including features like habtm, wo...) file uploaded by alek.morland - Labels: Featured Behavior Labels: Featured Behavior Mar 27, 2009 RevisionBehavior_2.0.3.rar (Version control of models, including features like habtm, wo...) file uploaded by alek.morland - Labels: Featured Behavior Labels: Featured Behavior Mar 27, 2009 issue 30 (Revision Model incorrectly uses the same table as its Shadow...) changed by alek.morland - Thank you for your contribution. We decided to refactor the method to deal with several minor issues there. Please verify that this version works for you. Status: Fixed Owner: alek.morland Labels: Project-RevisionBehavior Thank you for your contribution. We decided to refactor the method to deal with several minor issues there. Please verify that this version works for you. Status: Fixed Owner: alek.morland Labels: Project-RevisionBehavior Mar 27, 2009 r227 (refactored createShadowModel to fix issue #30 concerning pre...) committed by alek.morland - refactored createShadowModel to fix issue #30 concerning prefix and suffix usage. refactored createShadowModel to fix issue #30 concerning prefix and suffix usage. Mar 26, 2009 issue 30 (Revision Model incorrectly uses the same table as its Shadow...) reported by pmcfern - What steps will reproduce the problem? 1. I am using the newest copy of the Revision behavior. 2. I attach the behavior to one of my model with no configurations. $actsAs = array('Revision'); 3. Tried to save new data, which should create a revision in the shadow table. What is the expected output? What do you see instead? A new record should be inserted in the shadow table for my model. Instead, the behavior tries to reinsert the data I just saved. I reviewed the code and the issue is the following: The $Model->ShadowModel is using the same table as the $Model. I narrowed the issue down to the function createShadowModel. Since I'm not using a prefix, the $shadow_table is still holding the original table name, not the complete table name as stored in $full_table_name, so when it comes time to create the new model, the incorrect table name is used, thus breaking the whole behavior. I was able to get my copy working if I used: $Model->ShadowModel = new Model(false, $full_table_name, $dbConfig); What steps will reproduce the problem? 1. I am using the newest copy of the Revision behavior. 2. I attach the behavior to one of my model with no configurations. $actsAs = array('Revision'); 3. Tried to save new data, which should create a revision in the shadow table. What is the expected output? What do you see instead? A new record should be inserted in the shadow table for my model. Instead, the behavior tries to reinsert the data I just saved. I reviewed the code and the issue is the following: The $Model->ShadowModel is using the same table as the $Model. I narrowed the issue down to the function createShadowModel. Since I'm not using a prefix, the $shadow_table is still holding the original table name, not the complete table name as stored in $full_table_name, so when it comes time to create the new model, the incorrect table name is used, thus breaking the whole behavior. I was able to get my copy working if I used: $Model->ShadowModel = new Model(false, $full_table_name, $dbConfig); Mar 19, 2009 LogableBehavior (Quickly add behind the scenes logging of your database chang...) Wiki page added by alek.morland Mar 19, 2009 LogableBehavior Wiki page deleted by alek.morland Mar 19, 2009 LogableBehavior (Quickly add behind the scenes logging of your database chang...) Wiki page added by alek.morland Mar 11, 2009 r223 (Handle revisions for models with useTable = false) committed by ronny.vindenes - Handle revisions for models with useTable = false Handle revisions for models with useTable = false Mar 09, 2009 r222 (removed drafted branch) committed by alek.morland - removed drafted branch removed drafted branch Mar 09, 2009 r221 (added drafted behavior) committed by alek.morland - added drafted behavior added drafted behavior Mar 06, 2009 issue 29 (Active matches only urls with parameters (MenuHelper)) Status changed by ronny.vindenes - Fixed in r220 by adding a 'strict' option, old behavior is preserved as default. Status: Fixed Fixed in r220 by adding a 'strict' option, old behavior is preserved as default. Status: Fixed Mar 06, 2009 r220 (Added 'strict' option to check full URL or only /:controller...) committed by ronny.vindenes - Added 'strict' option to check full URL or only /:controller/:action pair. Closes issue 29 . Added 'strict' option to check full URL or only /:controller/:action pair. Closes issue 29 . Mar 06, 2009 issue 29 (Active matches only urls with parameters (MenuHelper)) Owner changed by alek.morland - thank you Phally. Ronny is currently decodeing it :) Owner: ronny.vindenes thank you Phally. Ronny is currently decodeing it :) Owner: ronny.vindenes Mar 06, 2009 issue 29 (Active matches only urls with parameters (MenuHelper)) changed by alek.morland - Status: Accepted Owner: alek.morland Labels: Project-MenuHelper Status: Accepted Owner: alek.morland Labels: Project-MenuHelper Mar 06, 2009 issue 29 (Active matches only urls with parameters (MenuHelper)) reported by i...@frankdegraaf.net - What steps will reproduce the problem? 1. Url menu item: controller => users, 'action' => 'search' 2. PRG makes: /users/search/Phally 3. Item is not marked as active. What is the expected output? What do you see instead? The item isn't marked as active, but should in specific cases like this. What version of the product are you using? On what operating system? Latest. Please provide any additional information below. Added a patch. Only when 'active' => array('identical' => false), the active check will only focus on controller/action. Else the it will behave as before. What steps will reproduce the problem? 1. Url menu item: controller => users, 'action' => 'search' 2. PRG makes: /users/search/Phally 3. Item is not marked as active. What is the expected output? What do you see instead? The item isn't marked as active, but should in specific cases like this. What version of the product are you using? On what operating system? Latest. Please provide any additional information below. Added a patch. Only when 'active' => array('identical' => false), the active check will only focus on controller/action. Else the it will behave as before. Mar 06, 2009 r219 (Changed diff() to use consistent array keys) committed by ronny.vindenes - Changed diff() to use consistent array keys Changed diff() to use consistent array keys Mar 06, 2009 issue 28 (setToolTip not working on pie chart) Status changed by alek.morland - thank you for submitting a ticket. implemented in version 3.3.8 http://code.google.com/p/alkemann/source/detail?r=218 Status: Fixed thank you for submitting a ticket. implemented in version 3.3.8 http://code.google.com/p/alkemann/source/detail?r=218 Status: Fixed Mar 06, 2009 r218 (fixed tooltip for piecharts issue submitted by pascal.hartem...) committed by alek.morland - fixed tooltip for piecharts issue submitted by pascal.hartemink fixed tooltip for piecharts issue submitted by pascal.hartemink Mar 06, 2009 issue 28 (setToolTip not working on pie chart) changed by alek.morland - Status: Accepted Owner: alek.morland Labels: Project-FlashChartHelper Status: Accepted Owner: alek.morland Labels: Project-FlashChartHelper Mar 05, 2009 issue 28 (setToolTip not working on pie chart) reported by pascal.hartemink - What steps will reproduce the problem? 1.add tooltip to pie chart e.g.#val# van #total#<br>#percent# van 100% 2. 3. What is the expected output? What do you see instead? #val# van #total#<br>#percent# van 100% / #val# of #value# What version of the product are you using? On what operating system? 3.3.7 Please provide any additional information below. tooltip is not set in public function pie i added if (!empty($this->tooltip)) { $pie->set_tooltip($this->tooltip); } now it is working ok What steps will reproduce the problem? 1.add tooltip to pie chart e.g.#val# van #total#<br>#percent# van 100% 2. 3. What is the expected output? What do you see instead? #val# van #total#<br>#percent# van 100% / #val# of #value# What version of the product are you using? On what operating system? 3.3.7 Please provide any additional information below. tooltip is not set in public function pie i added if (!empty($this->tooltip)) { $pie->set_tooltip($this->tooltip); } now it is working ok Feb 27, 2009 issue 27 (Multiple selects on delete) Status changed by alek.morland - Status: Invalid Status: Invalid Feb 27, 2009 issue 27 (Multiple selects on delete) commented on by brenton.bartel - My apologies, I spoke too soon ... That call is getting it the first time; however, I then had a rogue 'belongsTo' association, and when a delete is performed it checks the associations for extra info. I missed that association when stepping through :( My apologies, I spoke too soon ... That call is getting it the first time; however, I then had a rogue 'belongsTo' association, and when a delete is performed it checks the associations for extra info. I missed that association when stepping through :( Feb 27, 2009 issue 27 (Multiple selects on delete) reported by brenton.bartel - Hey, me again ... quick question ... When I do a delete on an association, ex: $this->User->Webpage->delete(34); I'm getting 2 "SELECT" queries in a row, before the actual delete of the Webpage (and then followed by the insertion into the log). I suspect that one of these is due to line 305 in the `beforeDelete()` function: $Model->read(); But have no idea why it's being hit twice, any thoughts? Thanks Hey, me again ... quick question ... When I do a delete on an association, ex: $this->User->Webpage->delete(34); I'm getting 2 "SELECT" queries in a row, before the actual delete of the Webpage (and then followed by the insertion into the log). I suspect that one of these is due to line 305 in the `beforeDelete()` function: $Model->read(); But have no idea why it's being hit twice, any thoughts? Thanks Feb 26, 2009 issue 26 (Unexpected behavior on moves with newest cake version) Status changed by alek.morland - I need a test case or instructions on how to recreate. Status: NeedMoreInfo I need a test case or instructions on how to recreate. Status: NeedMoreInfo Feb 25, 2009 issue 26 (Unexpected behavior on moves with newest cake version) reported by alek.morland - I recently upgraded to CakePHP 1.2.1.8004 and also to OrderedBehavior 2.2.2 (from the google code site). I noticed that quite often now, when I do some random moving up and down (both move($id, true) and move($id, 1) types of calls) strange things happen. Some of the records (besides the $id being moved) get unexpectedly re-ordered. I'm assuming this happens because the algorithm is somehow assigning wrong positions to some records for some reason. I recently upgraded to CakePHP 1.2.1.8004 and also to OrderedBehavior 2.2.2 (from the google code site). I noticed that quite often now, when I do some random moving up and down (both move($id, true) and move($id, 1) types of calls) strange things happen. Some of the records (besides the $id being moved) get unexpectedly re-ordered. I'm assuming this happens because the algorithm is somehow assigning wrong positions to some records for some reason. Feb 25, 2009 FlashChartHelper_3.3.7.zip (Embed flash charts using this wrapper for the Open Flash Cha...) file uploaded by alek.morland - Labels: Featured Helper Labels: Featured Helper Feb 25, 2009 issue 25 ([OpenFlashChart] Accept width and height of chart in percent) Status changed by alek.morland - Closed by revision 217 : http://code.google.com/p/alkemann/source/detail?r=217 Status: Fixed Closed by revision 217 : http://code.google.com/p/alkemann/source/detail?r=217 Status: Fixed Feb 25, 2009 r217 (Closing issue 25, allowing chart widths and heights to be se...) committed by alek.morland - Closing issue 25 , allowing chart widths and heights to be set in percent Closing issue 25 , allowing chart widths and heights to be set in percent Feb 25, 2009 issue 24 (Update for barStack to support options/tooltips) Status changed by alek.morland - Status: Fixed Status: Fixed

issue 32 (Option to save changes in serialized array) reported by m...@nahtigal.com - It would be useful to have an ability to fetch modified data in array (for custom display of changes) Sth like this (from line 377): {{{ if (isset($this->Log->_schema['change'])) { $logData['Log']['change'] = ''; $db_fields = array_keys($Model->_schema); $changed_fields = array(); foreach ($Model->data[$Model->alias] as $key => $value) { if (isset($Model->data[$Model->alias][$Model->primaryKey]) && !empty($this->old) && isset($this->old[$Model->alias][$key])) { $old = $this->old[$Model->alias][$key]; } else { $old = ''; } if ($key != 'modified' && !in_array($key, $this->settings[$Model->alias]['ignore']) && $value != $old && in_array($key,$db_fields) ) { if ($this->settings[$Model->alias]['change'] == 'full') { $changed_fields[] = $key . ' ('.$old.') => ('.$value.')'; } else if ($this->settings[$Model->alias]['change'] == 'serialize') { $changed_fields[$key] = array('old'=>$old, 'value'=>$value); } else { $changed_fields[] = $key; } } } $changes = sizeof($changed_fields); if ($changed_fields == 0) { return true; } if ($this->settings[$Model->alias]['change'] == 'serialize') { $logData['Log']['change'] = serialize($changed_fields); } else { $logData['Log']['change'] = implode(', ',$changed_fields); } $logData['Log']['changes'] = $changes; } $this->_saveLog($Model, $logData); }}}

It would be useful to have an ability to fetch modified data in array (for custom display of changes) Sth like this (from line 377): {{{ if (isset($this->Log->_schema['change'])) { $logData['Log']['change'] = ''; $db_fields = array_keys($Model->_schema); $changed_fields = array(); foreach ($Model->data[$Model->alias] as $key => $value) { if (isset($Model->data[$Model->alias][$Model->primaryKey]) && !empty($this->old) && isset($this->old[$Model->alias][$key])) { $old = $this->old[$Model->alias][$key]; } else { $old = ''; } if ($key != 'modified' && !in_array($key, $this->settings[$Model->alias]['ignore']) && $value != $old && in_array($key,$db_fields) ) { if ($this->settings[$Model->alias]['change'] == 'full') { $changed_fields[] = $key . ' ('.$old.') => ('.$value.')'; } else if ($this->settings[$Model->alias]['change'] == 'serialize') { $changed_fields[$key] = array('old'=>$old, 'value'=>$value); } else { $changed_fields[] = $key; } } } $changes = sizeof($changed_fields); if ($changed_fields == 0) { return true; } if ($this->settings[$Model->alias]['change'] == 'serialize') { $logData['Log']['change'] = serialize($changed_fields); } else { $logData['Log']['change'] = implode(', ',$changed_fields); } $logData['Log']['changes'] = $changes; } $this->_saveLog($Model, $logData); }}}

Earlier this year